GeoTagger Definitions disappearing in GeoEvent

Question

Having a really hard time working with some GeoTaggers in GEP (v. 10.5).  The generated definitions from the GeoTagger take a while to become accessible (via a field mapper, for example), sometimes never appear, and sometimes disappear (usually after making an edit to the GE Service).

I found this thread, which describes very similar behavior but for 10.3.1 version of GEP:

https://community.esri.com/message/525325?q=GeoTagger

This issue is only for GeoTagger-generated definitions, any other system- or user-generated/owned definitions seem to be fine and reliably available.

We are going to significantly bump up the CPU/RAM on the hosting server (it's Virtual, with 1 core and 8GB currently but doesn't have huge amounts services with huge amounts of data running - yet), as it is under-powered currently, so I cannot rule that out as the culprit here but wanted to see if this issue has cropped up for anyone working in 10.5 GEP.

Thanks -

Allen

AllenScully · Answer

Hi Chris -

We have just upgraded the Geoevent server in question, and the behavior seems better - no longer just dropping or refusing to generate GeoTagger definitions.  It's a little bit clunky - for example if you modify the GeoTagger at all, you need to publish and start the GeoEvent Service (and make sure the input is started) in order for the changes to to reflect in the Definition, but this is not a huge deal.

Now I just need to figure out why the GeoFence name is not making it into the specified field in the Output feature class...

Thanks -

Allen

ChrisBeyett · Answer

Hi Allen,

I just wanted to follow up on if you had made any progress with updating the server resources? Did this resolve the behavior or are you still experiencing it?

- Chris