Latest Contributions by MassimoDragan1

Thanks Adam, I had a look at that approach and understand the logic. In our use case though there is an additional nuance, besides counting how many points intersect the geofences we need to compare the values with thresholds and aggregate based on the level they fall into. So a possible workaround may be to first poll the input point values, use a geoevent service to categorize the risk value of each point (let's say low, medium, high), add this "augmented" layer to the geofence synchronization and only at this point intersect the polygons with these geofence points to perform the count (with another geoevent service). Tough points I see are: - how do I make sure that the sequence of 1) polling 2) categorizing 3) syncing the geofences follows a set order - is there a smart way to do this without having to develop a workflow for each category of risk, taking into consideration that the output service should be an email that provides a synthesis of the overlay like this:                3 points of risk low fall in polygon x                6 points of risk medium fall in polygon x                2 points of risk high fall in polygon x Happy to hear ideas on how to approach this, thanks again and in advance Massimo ... View more

thanks Stefan! I've tried again and can now poll the service, it takes a (long) while to update the data store catalog but eventually I can select the services. The first time I tried ita gave me a weird error on a name field, but today at a second attempt I've been able to poll features from the service, thank you for taking the time to test it, kind regards Massimo ... View more

thanks for the immediate response Jake, much appreciated so, I had actually setup a first version with the following: - poll the flooding service with Get Incremental Updates set to Yes - this assumes that if LastUpadates changes, the site will fetch these features - filter that service with the query, to only focus on actual flood events - use the Intersector processor to apply a geofence (as that may change overtime and we can't filter the stations in a static way) - send the output of the Intersector to email notification and in parallel to a feature service with the same schema of the inbound service, in order to webmap on AGOL the stations that are "currently" flooded AND within the "current" geofence would you see disadvantages in this approach versus the Incident Detector ? thanks if you have the time to review this additional note, have a great day Massimo ... View more

Hi Jake thanks for the comprehensive explanation on how to setup this notification service. I have a quick question concerning the setting used in the Input service, specifically the "Get Incremental Updates" option, where in your example this is set to "No". Can you please explain the rationale behind using Yes vs No and the use cases where either option is preferrable ? In my example, I have a fixed network of stations (so if I understand correctly Track_ID would be associated with the StationID ?) that can record a flooding status and whose attributes change over time according to the status. A new timestamp is used to register the status change for a given station and stored in a LastUpdated field. So given this scenario, I was planning on using Get Incremental updates set to "Yes" to trigger only changes in the status of the flooding for a station. any comment or suggestion would be highly appreciated, thanks massimo ... View more