"name": "Some name...",
"date": "2/17/2014 15:31:45"
"name": "Some name...",
Will you be able to help me with creating a calculated field for the following input?
I am polling an external website for a json, here is the format of the input and the geodefinition that created by default.
I've created a flat geoevent definition but I am not sure how to map the data to the new definition and the expression in the calculated field to build the geometry.
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
Thanks, I will try that.
Do you recommend creating a flat geoevent definition and using a field mapper?
Which output connector works the best? I used "Update a Feature in a Spatiotemporal Big Data Store" .
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.
I used the output: "Add a Feature to a Spatiotemporal Big Data Store", count is increasing in Geoevent manger/ monitor, but there is no data when I view the feature class in portal/ content page.
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.
It's captured in logs for both outputs I created, Spatiotemporal and stream service:
"The GeoEvent received contains an incompatible GeoEvent Definition (Bird-Status-Changes-Created) than the schema of the destination Spatiotemporal Big Data Store Service (BirdAPI-StatusChanges-Flat)."