After many many attempts, I am unable to replicate the functionality of idle Detection in geoEvent within Velocity. We have tried any number of nodes and combination of nodes with no luck. CalaculateMotionStatics comes the closest but does not really provide the same functionality and the documentation for this node is ambiguous at best.
Has anyone else found any good solutions?
https://hub.arcgis.com/documents/5d8e3446736d4df299c7c96bc275d561/explore
The Track Idle Detector Processor is a supported add-on processor that can be added to a GeoEvent Service that detects if a unique TRACK_ID has moved more than a specified amount within a given time. For example, if a delivery van is expected to make delivery stops that will not exceed 120 seconds, a Track Idle Detector could be used to alert dispatch personnel if a van is stuck in a single location for more than two minutes (e.g. if they are stuck in traffic or the vehicle has mechanical problems).
Have you looked at Find Dwell Locations ?
No, I have not as it's not an option in my Velocity RealTime Analytic only in Big Data Analytics -- Find Locations -
https://doc.arcgis.com/en/iot/analyze/find-dwell-locations.htm
@JeffSilberberg Ideally the Calculate Motion Statistics tool would be the right choice at this point to achieve what I am understanding you are asking.
Assuming you have location updates coming in (people, vehicles, object in motion) and want to know when that entity is idle and not moving:
This tool will generate the following attributes then related to idling:
Idling | Specifies whether the track is idle based on a distance and time threshold from the previous observation | Boolean |
TotalIdleTime | Cumulative amount of time for which idling was detected | Float64 |
PercentageIdleTime | Percentage of time for which idling was detected | Float64 |
I have been fighting with that node for almost a year now with zero success. I was told that the documentation does not match the implementation. This is why I posted to see if others have maybe found a better way.
@JeffSilberberg The documentation for all Velocity tools matches the implementation - please feel free to reach out to me directly over email (pnasuti@esri.com) and we will get a member of the product team assigned to investigate your reported issues with the Calculate Motion Statistics tool directly.
PM Sent --
To follow up on this thread for future community reference: