Parse a live state DOT Work Zone Data Exchange (WZDx) v4.2 Work Zone Feed to extract active paving/road-construction lane closures.
domain: github.com/usdot-jpo-ode/wzdx · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Retrieve the target agency's live WZDx feed URL (e.g., via the Feed Registry)
Validate the FeatureCollection against the WZDx v4.2 WorkZoneFeed JSON Schema (schemas/4.2/WorkZoneFeed.json in the usdot-jpo-ode/wzdx repo)
Read each RoadEventFeature's core_details.event_type (e.g. 'work-zone'), types_of_work, and vehicle_impact
Extract the lanes array's LaneStatus (open/closed/shift-left/shift-right) per road event to determine paving-related closures
Use beginning_accuracy and the event geometry to map the event to a route/mile marker
Known gotchas
Multiple WZDx major/minor versions (2.0-4.2) are live simultaneously across agencies with differing schema fields — always check road_event_feed_info.version before assuming v4.2 structure
The Device Feed (field devices) and Work Zone Feed are separate GeoJSON documents with separate schemas — do not conflate them
types_of_work is not always populated by producers, so filtering strictly on 'paving'/'resurfacing' work type will under-return; fall back to matching event description text
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?