The February 2026 update includes quality improvements, enhancements, and new functionality throughout ArcGIS Velocity. Highlights are provided below. For details, refer to the What's new in ArcGIS Velocity ArcGIS Blog article.
General
General improvements include the following:
- Enhanced security with dual authentication mechanisms by offering a new ArcGIS API key authentication mechanism in addition to the existing refresh token authentication.
- Numerous accessibility enhancements.
- Updates to back-end libraries and dependencies.
- Improved analytic stability and performance with additional validation for stateful analytic workflows. This enhancement introduces a new guardrail that ensures required identifiers are explicitly defined to prevent unstable or unintended analytic behavior.
Feeds
The following are the enhancements to feeds of Velocity:
- The following are the new feeds supported by Velocity:
- The ADS-B Exchange feed type in Velocity connects to the ADS-B Exchange API and returns real-time live global flight data.
- The Kpler feed type in Velocity connects to Kpler to ingest automatic identification system (AIS) data, providing real-time visibility into global maritime vessel movements.
- When user credentials are invalid, the following feeds retry the connection up to three times, log the errors, and then automatically restart after a delay based on the recurrence schedule:
Output
Two new parameters, Work Order Entity Type and Work Order Entity UID, have been added for work order creation in the Trimble Unity Maintain output.
Analytics
The following enhancements have been made to analytics:
- Creating a spatiotemporal feature layer directly from the Layers page without running a real-time or big data analytic. This capability is useful when you only need a stand-alone Velocity-hosted feature layer without analytics.
- Updated the feeds and analytic management page to clarify that the Organization Content tab in Velocity is visible only to users with the default Administrator role and is not available to users with custom roles, even if those include administrative privileges.
- The Velocity help site for analytic tools clarifies whether tools require geometry.
- The analytic stability and performance has been improved. Feeds connected to the join input of stateful analytic tools are now required to have a designated Track ID field. This means that any real-time analytic using stateful tools, such as Detect Incidents, Calculate Distance, Join Features, or Filter By Geometry, must include a Track ID field on the feed connected to the tool’s join input. If a feed on a stateful tool’s join input does not have a Track ID field specified, the analytic fails and stops running. In such cases, an error message prompts you to provide a Track ID field before restarting the analytic.
Note:
To resolve a failed analytic due to a missing Track ID field, you can update the feed’s configuration to set an existing field as the Track ID. Optionally, insert the Map Fields tool into the analytic workflow before the stateful tool to create or assign a unique identifier field as the Track ID for the join feed. Track IDs on join feeds serve as a new guardrail that ensures each trackable entity is properly identified, enhancing the reliability and performance of stateful analytic workflows in Velocity.