nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Support Publishing ArcGIS Velocity Outputs as OGC SensorThings API Endpoints

kntr

ArcGIS Velocity 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, ArcGIS Velocity 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 Velocity 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

Find more posts tagged with

Stream Layers

Under Consideration

Status: Under Consideration

Comments

kntr

Many thanks for the update @PeterNasuti. I look forward to seeing new, exciting updates to Velocity in future releases. I will try to find a sample API and get back to you with updates.

Cheers,

Kanin

PeterNasuti

Thanks @kntr for this idea - we have already been discussing and looking into OGC SensorThings support as a feed type. It's under consideration at this time.

For an output, Velocity would likely take the initial approach of supporting POSTing to an existing OGC SensorThings server API. We can further explore the feasibility of extending ArcGIS Velocity to function as an OGC SensorThings API for downstream client consumption as well.

If you can provide samples or API access to the OGC SensorThings data you are working with, we can incorporate that into feature design and testing.