Support Publishing GeoEvent Server Outputs as OGC SensorThings API Endpoints

[kntr]

GeoEvent Server should support publishing real-time and analytic outputs as OGC SensorThings API endpoints. This would allow organizations to share IoT and real-time geospatial data using open standards and improve interoperability with external IoT platforms and open data ecosystems.

Many government and enterprise organizations are adopting open geospatial and IoT standards to support smart city, digital twin, and national data platform initiatives. OGC SensorThings API is widely used as a standard interface for IoT sensor data exchange.

Currently, GeoEvent supports strong real-time ingestion and analytics capabilities, but does not natively support publishing outputs using SensorThings API. Organizations that require this must build custom middleware to translate GeoEvent outputs into SensorThings format.

Example Use Cases

• Smart city sensor data sharing (traffic, environmental sensors)

• National environmental monitoring platforms

• Utility infrastructure monitoring across multi-vendor systems

• Open IoT data portals

[JeffSilberberg]

@kntr 

     Sorry to jump in here, but I am confused and hope to learn something new here.  In fact, I already have, as I was not awareof this specific standard.   

    But, I have to ask, other than maybe a toJSON() function to complement the fromJSON() capability, which would take a dictionary and build a JSON string, what is missing?  Both geoEvent and Velocity have an HTTP output node already that can post JSON built in Arcade to an output.  I use this often after manually assembling and returning the JSON string in Arcade.

https://developers.sensorup.com/docs/