Geoevent Point Logging Parody

AKRRMapGuy

I am trying to achieve parody with Geoevent Server so we can migrate fully to Velocity for Enterprise(12.1). 

The lack of a geotagger is really causing a problem for me. The issue I am having with Velocity is the join keeps logging points every 10 seconds(source refresh rate) despite the join criteria being set to 'enter'. It keeps logging points even though the train never 'exited' the geofence. I need it to log one point for entering and one for exiting just like Geoevent does. I tried using 'incident' detection but I can't get that to log anything at all using the same logic, but on a stop even the 'closing' event is enters and speed == 0.

Here is what I am trying to replicate. The Geotaggers are using 'enter any' and 'exit any' respectively. They correctly only generate one point a piece. The filters you see on the geoevent process after the feed are combined into one filter in the velocity process after the feed. 

Here is what I have for just stops:

It's worth noting I am using the same exact sites and services to input and output between the 2 products for these processes. What am I missing, or can Velocity just not do what Geoevent can?

Jeff_G

@JeffSilberberg Detect Incidents would still give us a similar behavior to Join Features since its built-in Enter/Exit logic treats the polygon layer as a single dataset. For example, if geofences A, B, C, and D are connected to each other, a point moving from geofence A to geofence C may not trigger a new Enter event because the train never actually exits the overall states dataset.

@AKRRMapGuy I'm not sure why your Join Features logic is giving you a feature for every observation with your current configuration. I'd have to take a look at your analytic configuration and feed/source datasets to see what's going on. Feel free to send me a direct message with your contact info, and I'd me more than happy to get on a call with you.

As a workaround for the current Detect Incidents/Join Features Enter/Exit behavior, I was able to use an Arcade expression in a Calculate Fields tool.

In this example, I have a point moving from Florida to Virginia. The point is geotagged with the state name using Join Features. It uses an Intersects operation.

 

After the Join Features, I have a Calculate Field configured with the following Arcade expression. If our point moves from Florida to Georgia, it will detect that change and the expression will return true in new field I called "state_changed".

// 1. Fetch the previous state name array from the history cache
var priorStateArray = TrackFieldWindow('STATE_NAME', -1, 0);

// 2. If it's the initial record (no history), mark it true so we keep it
if (IsEmpty(priorStateArray) || Count(priorStateArray) == 0) {
    return true; 
}

// 3. Extract the previous text value from the array and grab the current one
var previousValue = priorStateArray[0];
var currentValue = $feature.STATE_NAME;

// 4. Returns true if it changed, false if it is identical
return previousValue != currentValue;

 

Downstream I have a Filter by Expression to only give me records where state_changed = true:

 

With this setup, I'm able to get point data every time our moving point enters a new polygon or exits the polygon dataset altogether.