WZDx, CWZ, and V2X: A Plain-English Guide to Work-Zone Data Standards
WZDx, CWZ, and V2X get thrown around together, but they're distinct pieces of the same pipeline: a shared vocabulary for describing a work zone, a richer successor to it, and the channel that carries it to vehicles. Here's the plain-English version.
WZDx — the Work Zone Data Exchange
WZDx (currently v4.2) is a USDOT-initiated specification: a common, machine-readable format for describing work zones — where they are, which lanes are affected, what the restrictions are — so that 511 systems, navigation apps, and connected-vehicle platforms can all consume the same data. Before WZDx, every agency's work-zone data looked different; WZDx made it interoperable.
CWZ 1.0 — Connected Work Zone
CWZ 1.0 (Connected Work Zone, from ITE/AASHTO/NEMA) is the standardized successor that extends WZDx with the typed fields real V2X consumption needs — validated lane impacts, restrictions, and worker-presence signals, with first-class enums instead of free text. A CWZ feed is a strict superset of WZDx 4.2, so it stays backward-compatible while carrying more.
DTCD publishes both formats, listed in the USDOT Work Zone Data Feed Registry — the same registry the downstream ecosystem sources from.
V2X — getting it to the vehicle
V2X (vehicle-to-everything) is the delivery layer: the channel that carries work-zone information into connected vehicles and the navigation platforms that reach unequipped ones. WZDx/CWZ describe the work zone; V2X is one of the ways that description reaches a driver in time to matter. The whole point of low-latency, field-captured data is that a warning arriving after the queue forms mitigates nothing.
How they fit together
- Capture — the crew documents the work zone in the field (this is the part most of the ecosystem is missing).
- Describe — that capture becomes a WZDx / CWZ feed: standardized, machine-readable.
- Deliver — the feed flows to 511s, maps, TMCs, and V2X channels that reach vehicles.
Standards solve the middle. The gap has always been the first step — clean data captured where the work happens. That's the layer DTCD is built on.
For platforms and OEMs
If you consume work-zone data, DTCD's free public feeds (WZDx, CWZ, CIFS, DATEX II) and a premium low-latency V2X API deliver source-captured data in the standards you already parse — including moving operations that planning-based feeds can't see.
DTCD turns the diary you already keep into a stronger record — and a live data feed. Capture the work zone once, in the field; get the DOT-ready daily diary plus a WZDx/CWZ work-zone feed automatically.
See pricing — $9.99/user all-in → · Founding Contractor Program → · Your state's requirement →