What's new

The September 2021 update of ArcGIS Velocity includes enhancements and quality improvements. Highlights are provided below.

General

  • Real-time data velocity metrics were updated to display data rate in KB/s across all areas of the app to better communicate alignment with subscription velocity limits.
  • Notification patterns were enhanced in several areas of the ArcGIS Velocityapplication.
    • All organization administrators designated as points of contact will now receive notifications in advance of ArcGIS Velocity upgrades as well as storage consumption warnings.
    • Additionally, administrators have new preference settings to control the rate at which storage notifications are sent.
    • All notifications now include information about the ArcGIS Online subscription the notification is referencing.
  • The analytic editor was updated with additional layout and visualization elements. A new smart layout option now allows you to automatically apply horizontal or vertical arrangements as you build an analysis process. Additionally, the animated lines that display when an analytic is actively running can be toggled off according to user preference. For more information, see Author an analytic.
  • A variety of enhancements were made to the Velocity application to improve resiliency and consistency.
  • Significant enhancements were made to the Velocity cloud architecture which enable more efficient feature storage and the ability to upgrade with minimal downtime.

Feeds, data sources, and outputs

  • The Kafka feed type was enhanced to support Confluent Kafka, broadening support for receiving high velocity streaming data from cloud messaging systems.
  • When defining a feed or data source, sampling data for the schema has been enhanced to support files up to 16MB in size. For more information, see the Website (Poll), RSS, and Simulator feed types.

Analytics

  • Dynamic joins are now supported in real-time analytics for joining streaming spatial data with streaming tabular data. This enables enrichment of asset tracks with related information from other real-time systems. For more information, see Join Features.
  • Dynamic spatial joins and dynamic geofencing continue to be beta capabilities and should not be used in production workflows. For more information, see Geofencing analysis. Additional enhancements to dynamic joins and geofencing include:
    • Improvements to time handling for join or geofencing feature expiration. When a geofence or join feature is received, it will be held in cache according to the Time Window parameter of the tool. The start time of the feature will be either the attribute designed as the start time. If start time is not designated or is NULL, the time the feature is received will be used. The feature will be retained in cache until the time window passes, or until the feature's designated end time passes, whichever is earlier.
    • Feeds that are used as join data for dynamic joins or geofences are required to have one of the data's incoming attributes configured as a TRACK_ID. If the value of the field designated as the TRACK_ID is NULL, the feature is dropped and not included in the join or geofencing analysis.
  • The Calculate Journeys tool was enhanced with new optional parameters to improve handling of minor dwell locations. This reduces over-identification of minor dwells that can result from data produced by some mobile app SDK's and API's where track features are sent with the same geometry in rapid succession.
  • An issue with the Snap to Network tool was fixed such that the ID field of the line segment to which the observation is snapped is returned in the same output data type as the field in the source network features.
  • Improved logging for cases where a big data analytic run encounters issues in execution.

Data management and visualization

  • Enhancements were made to improve the creation of views on spatiotemporal feature layers. Feature layer views now inherit the following from their source spatiotemporal feature layer:
    • Pop-up information
    • Tags and categories
    • Rendering styles
    • Spatial extent
  • Enhancements were also made to standardize spatiotemporal feature layers REST capabilities in terms of supported endpoints such as the Info endpoint.
  • Issues with querying were fixed such that feature layers return expected results when applying grouped count analysis and splitting query results by field. These fixes improve compatibility with widgets in ArcGIS Web AppBuilder and ArcGIS Dashboards.