SnowOps data, live in your ArcGIS.
Already invested in ArcGIS Enterprise, Portal, or ArcGIS Online? SnowOps publishes native ESRI-equivalent REST endpoints so your live winter-operations data flows straight in — consumed unchanged by ArcGIS Pro, ArcGIS Dashboards, and the ArcGIS JS API StreamLayer. No nightly copy, no sync lag.
One data source, two ways to use it
SnowOps is the system of record for live winter ops. But your GIS team lives in ArcGIS. Rather than forcing a choice, SnowOps publishes ESRI-equivalent services from the same PostGIS-backed pipeline — so ArcGIS clients see SnowOps data as if it came from an ArcGIS Server.
FeatureServer — in, or out
SnowOps publishes ESRI-compatible REST
FeatureServerJSON (ArcGIS FeatureSet) for drop-in consumption in Pro, Online, and Dashboards — and can also consume your FeatureServer layers via the ArcGIS Bridge.VectorTileServer
PostGIS-backed vector tiles are re-exposed as native ESRI
VectorTileServerendpoints, so ArcGIS clients render your road network and live features unchanged.StreamServer (live vehicle stream)
Live positions push to ArcGIS clients over WebSocket — consumable natively by the JS API
StreamLayer, Pro, and Enterprise. A 30-minute recent-history snapshot is included on connect.Anonymous + redacted surface
The ESRI-equivalent endpoints expose hashed vehicle IDs and positions only — no real IDs, speed, material, or operator identity.
How the live stream works
A Postgres NOTIFY vehicle_positions event is captured by the public service (LISTEN) and fanned out as bare ESRI features over WebSocket — emulating an ArcGIS /arcgis/rest/services/vehicle_live/StreamServer. No polling, sub-second.
No copy. No sync lag. No double storage.
ArcGIS reads SnowOps live. Your GIS stays the presentation layer; SnowOps stays the operational system of record.
Consume in your ArcGIS JS API app
const layer = new StreamLayer({
url: "https://snowops.techmaven.net/arcgis/rest/"
+ "services/vehicle_live/StreamServer",
// renders & updates live, no polling
});
map.add(layer);What SnowOps publishes — and the ESRI service it replaces
| SnowOps endpoint | Open standard underneath | ESRI equivalent it replaces | Consumed by |
|---|---|---|---|
| FeatureServer | OGC API Features | ArcGIS FeatureServer / MapServer | Pro, Online, Dashboards |
| VectorTileServer | OGC API Tiles / MVT | ArcGIS Vector Tile Server | Pro, Online, JS API |
| StreamServer | WebSocket / SignalR | ArcGIS StreamServer / GeoEvent | JS API StreamLayer, Pro, Enterprise |
SnowOps also flows inbound: the GeoLibre ArcGIS Bridge consumes your private FeatureServer layers (with their renderer & labels) into the SnowOps map. See the full open-services picture →
And it goes both directions
Data flow into ArcGIS is half the story. The GeoLibre ArcGIS Bridge also lets the SnowOps map client securely consume your ArcGIS Enterprise or Online FeatureServer layers — converting ESRI drawingInfo.renderer and labelingInfo into MapLibre styles, with all ESRI credentials kept server-side behind a staff-JWT-gated token proxy.
ArcGIS interop without ArcGIS licensing — in whichever direction you need it.
Bridge workflow
- Staff logs in.
- Browse the connection catalog.
- Enumerate FeatureServer layers (
?f=json) with paginatedquery. - Converter-wired
addLayer— geometry + labels rendered in MapLibre.
The plugin never sees an ESRI token — all credentials stay server-side.
Keep your ArcGIS. Add live winter ops.
See SnowOps data stream into your ArcGIS Dashboards and Pro sessions in real time.
Request a demo →