Hi geoevent team,
I have a very simple geofencing service that calculates the time police officers spent inside a geofence. The geofence is setup as cumulative. Everything works ok, I'm getting the time they spent inside the geofence in miliseconds. I'm using the default geoevent definition called "incident" and the time spent inside the geofence is recorded in a field called "duration" in milliseconds.
Since I need the time in minutes, I added a new step in the process that converts the time recorded in the field "duration" into seconds just by adding a new geoprocessor "field calculator" that converts milliseconds into minutes.
I set the new field that will hold the minutes as float but I have tested with double too - and got exact the same result.
The problem is, the process works and the conversion happends however, for some reason the field calculator processor rounds up the results removing all decimals. Anything less than 1 min gets rounded up to 0 minutes which in turn makes us undercalculate the time spent inside the geofences.
Why is this happening? is there any workaround or a different way to perform the conversion?
PS: Tested in 10.8 and 10.8.1 with the exact same results.
@RJSunderman