https://community.esri.com/t5/arcgis-geoevent-server-ideas/support-publishing-geoevent-server-outputs-as-ogc/idi-p/1684538 <P>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.</P><P>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.</P><P>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.</P><H2>Example Use Cases</H2><UL><LI><P>Smart city sensor data sharing (traffic, environmental sensors)</P></LI><LI><P>National environmental monitoring platforms</P></LI><LI><P>Utility infrastructure monitoring across multi-vendor systems</P></LI><LI><P>Open IoT data portals</P></LI></UL> Mon, 16 Feb 2026 07:57:33 GMT kntr 2026-02-16T07:57:33Z https://community.esri.com/t5/arcgis-geoevent-server-ideas/support-publishing-geoevent-server-outputs-as-ogc/idi-p/1684538 <P>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.</P><P>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.</P><P>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.</P><H2>Example Use Cases</H2><UL><LI><P>Smart city sensor data sharing (traffic, environmental sensors)</P></LI><LI><P>National environmental monitoring platforms</P></LI><LI><P>Utility infrastructure monitoring across multi-vendor systems</P></LI><LI><P>Open IoT data portals</P></LI></UL> Mon, 16 Feb 2026 07:57:33 GMT https://community.esri.com/t5/arcgis-geoevent-server-ideas/support-publishing-geoevent-server-outputs-as-ogc/idi-p/1684538 kntr 2026-02-16T07:57:33Z https://community.esri.com/t5/arcgis-geoevent-server-ideas/support-publishing-geoevent-server-outputs-as-ogc/idc-p/1684596#M170 <P><a href="https://community.esri.com/t5/user/viewprofilepage/user-id/736370">@kntr</a>&nbsp;</P><P>&nbsp; &nbsp; &nbsp;Sorry to jump in here, but I am confused and hope to learn something new here.&nbsp; In fact, I already have, as I was not awareof this specific standard.&nbsp; &nbsp;</P><P>&nbsp; &nbsp; 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?&nbsp; Both geoEvent and Velocity have an HTTP output node already that can post JSON built in Arcade to an output.&nbsp; I use this often after manually assembling and returning the JSON string in Arcade.</P><P><A href="https://developers.sensorup.com/docs/" target="_blank">https://developers.sensorup.com/docs/</A></P><P>&nbsp;</P><P>&nbsp;</P><P>&nbsp;</P> Mon, 16 Feb 2026 19:02:20 GMT https://community.esri.com/t5/arcgis-geoevent-server-ideas/support-publishing-geoevent-server-outputs-as-ogc/idc-p/1684596#M170 JeffSilberberg 2026-02-16T19:02:20Z