Import GeoFence changes string values by adding underscores for spaces (and other characters) which then causes the GeoTagger to add new field with a string value that the Field Enricher (from the same Feature Service that was used to import the geofences) to not work because the field values no longer match. Any suggestions on how to workaround this issue?
Thanks for your feedback. We currently modify the original values for internal-use by the GeoEvent Processor, yet do not map them back to their source. We will consider this for a future release. Again, thanks for your feedback John.