DTCD publishes real-time work-zone data in every major industry standard — WZDx, CWZ, CIFS, DATEX II, and V2X. All feeds are public, GeoJSON or XML, validated against published schemas, and available with no API key for testing or low-volume use.
Every closure published from DTCD is automatically expressed in six output formats. Each format is generated from the same source data — a date-stamped, GPS-tagged contractor diary entry — so consumers see consistent information regardless of the format they ingest. Mobile-operations feeds (striping, sweeping, mowing, plowing) are updated in real time as field GPS positions advance; static feeds (closures) update on every published change.
One canonical feed in CWZ v1.0 — a strict superset of USDOT WZDx 4.2. Stationary closures and mobile operations (striping, mowing, sweeping, plowing) appear in the same payload. Mobile features carry work_zone_type: "moving" and is_moving: true so consumers can filter or treat them differently. Validated against the official CWZ schemas.
The ITE/AASHTO/NEMA Connected Work Zone v1.0 standard, a strict superset of WZDx 4.2 — same feed_info shape, same feature shape, additional optional fields filled in for connected-vehicle and AASHTO infrastructure consumers. Federally registered.
For consumers that prefer the formats Waze, Google Maps, and other consumer navigation services already ingest natively.
Waze / Google Closure and Incident Feed Specification. Provides closures and incidents in the format Waze and Google Maps ingest directly via partner integrations.
For consumers operating under European traffic data exchange standards — useful for international DOT partnerships and CEN-aligned ITS deployments.
The European Committee for Standardization's traffic information exchange format. Used by European DOTs, traffic operators, and ITS service providers. Useful when an agency or contractor partner standardizes on CEN.
Optimized for vehicle-to-everything (V2X) consumers — connected-vehicle platforms, OEM telematics, and roadside-unit (RSU) broadcasts.
A connected-vehicle-optimized projection of work-zone data, including geometry simplified for in-vehicle processing, projected route ahead for mobile operations, and lane-level impact descriptors. Compatible with major OEM CV platforms and RSU broadcast formats.
All feeds are public — no API key required for development, testing, or low-volume use. Rate limits apply per IP/API key:
For higher rate limits or guaranteed SLA, request an API key at matthew@purposebuilt.systems with subject line "API Key Request" and a brief description of your integration.
Use of PurposeBuilt Systems' apps (including DTCD) by Iowa DOT, by contractors and consultants subject to Iowa DOT regulatory authority, and by engineering and consulting firms holding active Iowa DOT contracts is unauthorized. Iowa-regulated entities are not paid customers; their work zone data does not appear in these feeds.
Whether your organization falls within the excluded class is determined under Iowa Code Chapter 68B by the Iowa Ethics & Campaign Disclosure Board or Iowa DOT, not by PurposeBuilt. If uncertain, contact the Iowa Ethics & Campaign Disclosure Board (ethics@iowa.gov, 515-281-4028) or Iowa DOT directly before installing or subscribing. For background, see the Iowa standards page.
The DTCD feed is registered with the U.S. Department of Transportation as an active national-coverage WZDx-compatible feed. Issuing organization: PurposeBuilt Systems, LLC. Format: GeoJSON · Version: CWZ 1.0 · Active since 2026-04-21.
The feed is also discoverable through this page, the site sitemap, and links from federal/state transportation registries.
Need help integrating, want a custom format, or interested in a higher-rate-limit API tier? PurposeBuilt Systems offers integration scoping for traffic management centers, federal partners, navigation providers, and connected-vehicle platforms.