I have some data coming through a Velocity RTA. When the RTA Detects an INcident (Started or Ongoing) the data is sent through a Stream Layer and appears on a Map which is used in a Dash Board and an Experience Builder App.
Started and Ongoing events render correctly, but when the Incident transitions to Ended and then disappears from the Stream Layer completely, the Point that was last rendered seems to stay on the Map until reloaded!
I have tried Filtering on the IncidentStatus but that does not seem to be the answer.
TIA, for any pointers/direction.
Try setting up "auto refresh" for that data layer?
So I am dealing with a Stream Layer not a Feature layer.. Refreshing, F5, loses everything pending new transactions.
I'm not familiar with a Steam Layer.
This "auto refresh" won't refresh the whole page, only the widgets (such as a map or a table) will reload the data with "auto refresh" enabled.
Is the widgets reloading data affect the Steam Layer's pending transactions?
Stream Layers from Velocity or geoEvent are much different as they are basically an open socket and once the data is received it is no longer available and there is nothing available prior to the Web Map (Socket) being opened.
So if the Map or Map Layer is refreshed, everything from the Stream layer previous to the refresh is lost. NOT what we want; we just need to remove a single point (transaction/Incident).
Hi @JeffSilberberg,
Could you share your data and app with me for troubleshoot? My username is ke13810.
Thanks,
Ke
So looking at this again yesterday. The Stream file comes out of Velocity. An contains data including IncidentStatus from an Incident Detector Node. The Web map is set to display this Stream Layer, track Id on the Map, if the Filter of IncidentStatus is not equal to "Ended".
The expectation is that anything that comes through the stream will get mapped as a Point with the appropriate style, and then when the "Ended" transaction comes through the item will be removed from the Map display. However, this does not appear to behave this way ??
TIA --
Update --
This same functionality appears to working as a Feature Layer, just not as a Stream Layer.