topic Re: Looking for some input on RTA. in ArcGIS Velocity Questions

Looking for some input on RTA.

JeffSilberberg — Mon, 17 Nov 2025 16:05:07 GMT

Morning,

I am looking for some general input with regard to a fairly complicated RTA.

I have some 1,500 devices reporting location and device health every 30 seconds, as well as on specific events, so sometimes much more often between the periodic reports. The issue I have is that Time to First Lock can vary, and it's feasible to see numerous reports at different times of the day with a null Lat/Lon/Alt/GPS Time in the transaction.

So, I have removed the geometry calculation from the Feed and do it in a calculation node inside the RTA if LAT is not null. The enriched schema is then carried with the transaction through a couple of different logic streams, one of which does an Incident Detect and then a dynamic geoFence.

Now my issue, if I get a PwrDwn event from a device (end of shift), there is no location data, but one of the close conditions for the Incident is PwrDwn, which is currently never seen as the LAT filter eliminated the transaction.

So my question is: is there any reference documentation on which processing nodes can be in a logic stream even if there is no geoLocation in the schema, and which will throw an error, crash the RTA, and result in potential data loss?

Note the new Choice (Route by expression) makes the initial logic much cleaner and easier to implement. So it's which nodes have a dependency on geometry that I need to understand.

TIA --

Re: Looking for some input on RTA.

PeterNasuti — Tue, 18 Nov 2025 15:37:22 GMT

Hi @JeffSilberberg the following tools do and do not have a geometry configuration requirement. I'll add an item for us on the product side to update documentation to make it more clear for each tool when geometry is required. For any circumstances where you see an analytic crash as opposed to a feature being skipped for processing with a corresponding and explanatory log message thrown, please log a support bug so that Velocity can continue to be enhanced for all these conditions.

Require geometry:
Create Range Fans
Add XYZ Values
Calculate Distance
Calculate Motion Statistics
Create Buffers
Feature to Point
Filter by Geometry
Project
Snap to network

Do not require geometry:
Calculate Fields
Control Event Volume
Delay and Reorder Tracks
Detect Incidents (assuming no spatial condition configured)
Detect Gaps
Filter by Expression
Filter by Time Range
Join Fields (assuming no spatial join configured)
Map Fields
Merge
Multi-merge
Route by Expressions
Select Fields

Re: Looking for some input on RTA.

JeffSilberberg — Tue, 18 Nov 2025 15:43:23 GMT

Thank you!

One follow-up question. If the Detect Incidents Close (exit) condition is based on an Arcade or a Spatial Condition and the Arcade condition is TRUE, does the node still try to use the Spatial Condition?