Geoevent Processor - Incident Detector. Incidents not reporting as 'Ended'

JohnEvans6 · ‎12-23-2019

Hi,

I am on Geoevent Server 10.5 Patch 2. My configuration looks a bit weird only because I have been trying to troubleshoot and ended up creating 2 separate threads from the same event trigger. In reality the 'Is event Ended' filter connects to the bottom field enricher, I set a flag to N, map to the same geoevent definition, and update the same output map layer.

The Facilities_4326 input is a collection of points. I compare these points against specific National Weather Service Polygons:

The Geometry Inside ANY works well. As soon as a point is detected and goes through the process, I re-enrich, set my field, map to an AGOL map layer, set my display flag to Y, and end up showing only those facilities inside a geometry on my map:

nws-incident-field-reducer-DASH-END,Started,EAT Airport,"-120.20573741699997,47.398089250000055",Y

My incidents never end:

nws-incident-field-reducer-DASH-END,Ongoing,EAT Airport,"-120.20573741699997,47.398089250000055"
nws-incident-field-reducer-DASH-END,Ongoing,GTF Airport,"-111.37061002799999,47.48265391700005"
nws-incident-field-reducer-DASH-END,Ongoing,OTH Airport,"-124.24702777799996,43.41694444400008"
nws-incident-field-reducer-DASH-END,Ongoing,15OR Military Tower,"-123.93136102099999,46.11593221000004"
nws-incident-field-reducer-DASH-END,Ongoing,GTF Combined Tower/Approach,"-111.35959746699996,47.48005864400005"
nws-incident-field-reducer-DASH-END,Ongoing,OTH Federal Contract Tower,"-124.24799232899994,43.41795984100003"
nws-incident-field-reducer-DASH-END,Ongoing,EAT Airport,"-120.20573741699997,47.398089250000055"
nws-incident-field-reducer-DASH-END,Ongoing,GTF Airport,"-111.37061002799999,47.48265391700005"
nws-incident-field-reducer-DASH-END,Ongoing,OTH Airport,"-124.24702777799996,43.41694444400008"
nws-incident-field-reducer-DASH-END,Ongoing,15OR Military Tower,"-123.93136102099999,46.11593221000004"
nws-incident-field-reducer-DASH-END,Ongoing,GTF Combined Tower/Approach,"-111.35959746699996,47.48005864400005"
nws-incident-field-reducer-DASH-END,Ongoing,OTH Federal Contract Tower,"-124.24799232899994,43.41795984100003"
nws-incident-field-reducer-DASH-END,Ongoing,EAT Airport,"-120.20573741699997,47.398089250000055"

Questions:

1. Will it never evaluate the 'All these are TRUE' if the geometry does not exist as a geofence?

2. I have tried EXIT, but that does not work either. Neither my points nor my geometries really move. My geofences eventually delete, and my point should evaluate as inside until that geofence is removed. EXIT doesn't set my 'Ended' flag.

3. If I set it to ANY of these are true, it does end up triggering an 'Ended' condition correctly, but that's not the logic I need.

4. I set the expiry time to 6400 seconds to just straight up end incidents and they still never get reported as 'Ended' in my output.

Any thoughts? I am open to anything. Going nuts with it feel like I'm missing something crazy obvious.

Appreciate your time

John

JohnEvans6 · ‎12-26-2019

So Incidents do get tagged as ended if I remove all closing conditions: Incident Detector Processor—Process Event Data(10.7.1) | ArcGIS Enterprise

When configuring Incident Detector, you must specify an opening condition; a closing condition, however, is optional. If a closing condition is not specified, the processor will use a logical negation of the opening condition as an implicit closing condition.

It doesn't close on the logical negation; but it does now close based on the expiry time, which isn't a 100% solution but it's better than not being flagged at all.

I keep coming back to my #1 question above relating to the 'All these are true' closing condition. Does that geometry have to exist as a geofence in order to evaluate as TRUE? I get the feeling it does but would love someone more seasoned to set me straight.

Thanks!