what is the recommended service configuration for populating existing fields in a geoEvent based on location?
From the ootb processors I see geofencing + GeoTag+Table Join as the only method. Kinda clunky
I have 2 spatially dependant attributes that exist in the schema but are blank in the incoming geoevent (District,DistrictSupervisor) and want
I would have to first load districts as geofences (possibly many thousands)
Then I have to GeoTag to get the geofence name, then do a separate Join to get the DistrictSupervisor.
Ideally I am looking for a processor that queries a FS layer or shapefile by the location of the geoEvent and populate one or more attributes in the same manner as the join.
Is this something we have sitting around somewhere?
Why is this not a standard processor?