Increasing an integer field with incoming events

Question

Original User: tommigro

Hello

we would like to realize the following idea: with every incoming event we would like to increase the value of an integer field of a feature service.

What would be the best approach for that?

We checked how this could be done using the field enricher. I did not seem appropriate.

Thanks
Thomas

basic_raster.png

baisc_with_damm.png

damm.png

reclass.png

Justin_Greco_0-1733766635903.png

Laura_1-1733766347583.png

Laura_0-1733766271289.png

img71.jpg

KDeVogelaere · Answer

Thank you RJ for posting a solution to this, is the prototype custom processor you spoke of available in 10.2.2?  I am also interested in a solution for calculating EventCounts using multiple key fields (eg. ID + StartTimestamp + EndTimestamp) to increment the count. Thanks!

RJSunderman · Answer

Thomas -

As it turns out, a couple of developers on the team are working to prototype a custom processor which might do what you're looking for, but the proof of concept is not working properly yet, so it's not something I can share.

So, let's see what we can do with what we have available out-of-the-box...

I changed my FieldEnricher to enrich events received from the feature service's feature class, rather than the non-spatial table.

[ATTACH=CONFIG]33128[/ATTACH]

The two filter elements are branching the event flow one way if the EventCount field exists in the received event (bottom branch) and the other way if the field is not included in the event's attributes. Notice that one filter specifies 'AND' while the other filter specifies 'NOT'.

[ATTACH=CONFIG]33130[/ATTACH]

I've attached a 10.2.1 product configuration I exported which defines all of the various elements I created for this exercise. I had to wrap it up in a ZIP to get the forum to allow me to attach it. You should be able to unzip and import it into your GeoEvent Processor to create the Inputs, Outputs, GeoEvent Service, and GeoEvent Definitions needed - along with a registered Data Store pointing to LOCALHOST where the feature service is assumed to have been published. The GeoEvent Definition trail is especially important to getting the event flow to work. I didn't use any Field Mapper processors to ensure that the event schemas matched what was needed to update the feature service. You will want to look at the GeoEvent Definitions being created by the Field Reducer, Field Enricher, and the Field Calculator named 'ResetField' which creates a field named EventCount if the received event does not already have that field.

I included some sample JSON data in the ZIP archive with the product configuration.

- RJ

EventCount-GEP-10.2.1.zip

EnrichEventWithCount.png

FieldExistsFilters.png

Anonymous User · Answer

Original User: tommigro

Hello RJ

Thanks for your help. I tried to follow your instruction for several hours now but didn't manage to get the problem solved. Could you please give me insight into your Field Enricher Processor and your Filters (screenshots)? I would like to compare them with mine.

Thank you.

Regards
Thomas