Latest Contributions by Stefan_Jung

First of all i would check the log-files if you find any error trying to write to the output. Maybe there is a missmatch of the geoevent defnition that has been used for publishing the service and is now used to write. For debugging I would also suggest you to create a new output connector: Push Text to an External TCP Socket and use the GeoEvent Logger (installed with GeoEvent Server) to see what data is send to the output. ... View more

Creating a flat geoevent definition is always a good idea if the data will be used in a relational table.  Just be careful if you have fields with Cardinality many. And which output connector works best depends on what are you planning to do with the data. There is not just one correct answer. If you want to save all the incoming data for analysis and if you receive a lot of data than the Spatiotemporal Big Data Store might be best for you. If you want save and update the last location of your incoming vehicles the Standard Data Store might be enough. If you want to have a smooth visualization of the current position of each vehicle maybe Stream Service is your choice. Best Stefan ... View more

Hi Sara Abasi‌, the easiest way would be to use "Construct Geometry From Fields" in your input connector. This will work pretty fine if you always have the same JSON structure that contains a geometry. Just add a new field to your geoevent definition with the Type Geometry and the Tag GEOMETRY  In the Advanced section if your input configuration you can try this: That should work Best, Stefan ... View more

Hi Hanoch Kalmanovich, yes you got me. Currently ArcGIS Enterprise is 10.7.1 but GeoEvent is still 10.6.1. This is because we had to roll back GeoEvent cause of some issues and we currently wait for the 10.7.1 Patch, that should be released soon. Next time I will mention the version numbers, my fault - but thanks a lot. So this two versions are not compatible in that way.  Best Stefan ... View more

Hi James Madden‌, your GeoEvent Input will always return a status code 200 as long as the REST Endpoint is running and GeoEvent is able to parse the incoming JSON. In this case the JSON is now converted to a "GeoEvent-Object" for internal processing in the GeoEvent Service. So the Client will not get any feedback if further processing in the GeoEvent is successful or not. Now your output connector is trying to write the data to the feature service. This is also more or less stateless. So it is possible that even the output connector cannot tell you if the feature was written successfully. The connector is sending a request to REST API of the ArcGIS Server to write the features. Now it is up to ArcGIS Server to write the features into the database. If ArcGIS Server is returning a error message to the GeoEvent you should find it in the logfiles of the GeoEvent. But as far as i know there will not be a second attempt from GeoEvent in this case. Long story short, i don't know if the insert is going to fail while recycling. But i still hope the understanding how GeoEvent behaves in this case helps you a little bit   Best Stefan ... View more

Hi Jeremy Roberts‌, you are absolutely right, that would be nice to do this on server side. As far as I know there is currently no way to do this to filter it on the server using Stream Layer or the out of the box websocket output. Sure you could create a few outputs and filter which data will be send via which output, but an output will always send all data it receives regardless of the client. Best Stefan ... View more

Any updates here Kerry Robinson‌? ... View more