Technical deep-dives into traffic data, API architecture, and the challenges of normalizing 57 jurisdictions.
A from-scratch walkthrough: live incidents, camera popups with images, and road condition overlays in under 100 lines of JavaScript — powered by Road511’s GeoJSON API.
Normalized spring weight restrictions from MN, WI, MI, ON, QC, and NS — polyline geometry, active date ranges, and a corridor endpoint that flags every restriction your load would violate along a planned route.
Standard RFC 7946 GeoJSON for every traffic event, camera, sign, and POI — bounding box and radius queries that drop straight into Leaflet, Mapbox, MapLibre, ArcGIS, and QGIS. PostGIS-backed, no XML wrangling.
Live messages from every Dynamic Message Sign across 30+ US states and Canadian provinces. One API, normalized text, GeoJSON output, and a historical archive of message changes nobody else publishes.
Every US state and Canadian province runs its own 511 system with a different format. Here's how the adapter registry pattern normalizes Transnomis JSON, ArcGIS, GraphQL, WZDx, protobuf, and more into one schema.
10,000+ live camera feeds from 40+ states with direct image URLs. No other API provides this — here's how to use it in your app.
FHWA National Bridge Inventory — height clearances, weight ratings, posting status. Query by corridor with PostGIS spatial search.