The March 2022 update of ArcGIS Velocity includes enhancements and quality improvements. Highlights are provided below.
General
- Expansions to the maximum number of running items for Standard and Advanced subscriptions. For details, see Licensing.
- Standard subscriptions can now run up to 10 feeds and analytics (previously 5).
- Advanced subscriptions can now run up to 15 feeds and analytics (previously 10).
- Improved notifications for feed data rates to include information on the specific feeds that are exceeding subscription data rates.
- Improved notifications for compute usage on Dedicated subscriptions, including the ability of the administrator to set the cadence of compute notifications.
- Autoscaling enhancements for lower velocity feeds and real-time analytics. For example, avoiding over-scaling when data is ingested in larger, infrequent batches such as when polling an API.
Feeds, data sources, and outputs
- The gRPC feed type is out of beta and fully supported. gRPC (Generic Remote Procedure Call) enables a client/server paradigm in which real-time data can be pushed into ArcGIS Velocity either transactionally or in a streaming approach. This broadens extensibility by enabling developers and partners to build integrations for sensor or Internet of Things (IoT) systems that are not supported as out-of-the-box feed types.
- The Feature Layer (new) output has been enhanced to support writing output data to ArcGIS Online hosted feature layers from big data analytics. As with real-time analytics, there are limits on the supported output rates to hosted feature layers.
- The Geotab feed type was enhanced to allow the user to specify additional attributes from the Geotab database for ingestion such as driver data.
- The Kafka feed type's authentication options have been enhanced to support SASL PLAINTEXT (non SSL) in addition to SASL PLAIN.
Analytics
- Dynamic geofencing and dynamic joins in real-time analytics are out of beta and fully supported. Dynamic geofencing and joins enable you to find relationships between two sets of data that are changing in real-time, and can be configured by using two feeds together in tools such as Filter by Geometry, Join Features, and Detect Incidents. See Geofencing analysis for more information including limitations on the maximum size of geofences for the different subscription levels.
- New analytic metrics are available in the analytic editor when analytics are actively running. This includes the data rate in bytes per second, counts of features without geometry or time information, and for tools that operate on two datasets or data streams, the size of join or geofence data. This additional information helps when troubleshooting and understanding if an analysis process is working as expected. For details, see View analytic details and status.
- Join Features was enhanced to allow the target feature's geometry to be replaced with the geometry of the join feature. This supports use cases such as infrastructure hazard monitoring by allowing the affected infrastructure features to be returned and visualized immediately.
- Detect Incidents was updated for use in real-time analytics to return incident duration in milliseconds instead of seconds, to align with the tool specification.
- The analytic editor was enhanced for real-time analytics to display additional information on input feeds such as the recurrence setting for feeds that poll regularly for data.
- Other minor enhancements include improvements to several analytic tools to standardize the spatial disjoint operator and additional logging for Snap to Network to report when features must be discarded.
Data management and visualization
- New user experience for setting default symbology for output stream layers including simple, unique value, and class break rendering. This broadens the ability to use stream layers in the new ArcGIS Online map viewer with user-defined rendering. For details, see Visualize stream layers.
- Enhancements to spatiotemporal feature layer views so that item details display the relationship between a view and its source feature layer, and so that view definitions can be set properly in the new ArcGIS Online user experience.
- Improved standardization of the stream service specification as well as fixes for scenarios when the service is configured to store the latest feature in an associated feature layer and when associating a reference feature layer to provide geometry for incoming data.