Detect Incidents - Time on Site Calculations

MuneerMajid

As we know, Detect Incidents for Geofences reports the results with a Status flag ('Started', 'Ongoing', 'Ended'). There is also an accompanying Incident Duration Field along with other joined fields that come out of your Geofence/polygon layers. 

There is no slick way (that I am aware of) of reporting time on site against each geofence using this information. The incident status 'Ended' field should typically have the total time spent on site, but since this observation was recorded outside of the geofence, it doesnt include any information from the join fields and leaves them blank. If this wasnt the case, you could simply have a filter for IncidentStatus = Ended and could have reported each Geofence incident with the Track ID, Geofence Name/ID (from Join Field) and time on site. 

I have tried to figure out an efficient way within arcade to isolate this information, but havent been able to figure this out yet. Anyone who has been able to effectively translate this info directly from the Detect Incidents Output table, appreciate if you can shed some light on your observations/learning. 

Joanna_Nishimura

I wanted to provide an update on this issue and provide info that may be helpful for others:

I worked with MuneerMajid to further investigate this issue. In MuneerMajid's workflow, the Detect Incidents tool was being used in a Real-Time analytic.  Even though fields were specified in the Join Field parameter of the tool, those fields and their values were not being populated in the final incident point (the incident point that had a  status of “Ended”). 

The Detect Incident tool had an Open Condition spatial relationship of “Intersects” and did not use a Close Condition spatial relationship. Without a Close Condition relationship set, the tool will use the logical opposite of the Close Condition relationship.  The opposite of “Intersects” is “Disjoint,” and when “Disjoint” is used as a spatial relationship, then the Join Field values are expected to be null. 

To address this issue, we set the Close Condition spatial relationship to “Exit,” and saw the Join Field values populate.  We will be updating the documentation to address this nuance.