Geotagger not Tagging due to Geofence CRS importing to 3857 (10.7.1)

156
1
Jump to solution
01-13-2021 10:37 AM
DeanMoiler
New Contributor III

Hey everyone,

I'm having an issue with a GeoTagger not tagging a point event feature WITHIN_ANY geofence polygon on a 10.7.1 instance.

DeanMoiler_0-1610540407476.png

 

I have created the geofence polygon such that if the inbound event point feature is not within one of the Allowed areas, it will be tagged with the inverse larger area geofence called None. A GeoTag value should always be applied to the point event features, though this does not appear to be consistently working near the western and eastern extremities of the largest geofence. The inverse None geofence is also not being tagged, which is the most surprising part.

My GeoFence polygon features are synchronised with a feature service that is in a projected CRS, though when it imports, it imports geofence coordinates to Web Mercator, which likely uses a default transformation rather than the transformation required, being a likely culprit for this issue to occur :

DeanMoiler_1-1610541490377.png

If I manually update the geofence polygon coordinates with projected CRS coordinates, the GeoTagger  tags correctly. The problem here being that I must then switch off the geofence synchronisation and update the geofence coordinates manually for it to work, which is far from ideal.

Is there some way to have them imported in the CRS specified either in the Synchronisation Rule or the Map/Feature service, or something that I'm missing?

Thanks!

Dean

 

 

 

0 Kudos
1 Solution

Accepted Solutions
DeanMoiler
New Contributor III

Just as an update on this in case anyone else has the same issue, I resolve this by doing the following:

  1. Delete all Geofences
  2. Export geofences in correct CRS using {serviceURL}/MapServer/dynamicLayer/query?layer=xxxxxx in JSON format
  3. Selective Export GeoEvent Configuration Store (GeoFences)
  4. Manually update geofences with exported JSON rings
  5. Selective Import GeoEvent Configuration Store (GeoFences)

Something was causing GeoEvent to always use 3857 to either import or synchronise from this same service and this solved that problem, short of cleaning out the whole site.

GeoFence synchronisation now seems to work and synchronise as needed.

View solution in original post

0 Kudos
1 Reply
DeanMoiler
New Contributor III

Just as an update on this in case anyone else has the same issue, I resolve this by doing the following:

  1. Delete all Geofences
  2. Export geofences in correct CRS using {serviceURL}/MapServer/dynamicLayer/query?layer=xxxxxx in JSON format
  3. Selective Export GeoEvent Configuration Store (GeoFences)
  4. Manually update geofences with exported JSON rings
  5. Selective Import GeoEvent Configuration Store (GeoFences)

Something was causing GeoEvent to always use 3857 to either import or synchronise from this same service and this solved that problem, short of cleaning out the whole site.

GeoFence synchronisation now seems to work and synchronise as needed.

View solution in original post

0 Kudos