The Work Zone Data Exchange (WZDx) Specification aims to make harmonized work zone data provided by infrastructure owners and operators (IOOs) available for third party use, making travel on public roads safer and more efficient through ubiquitous access to data on work zone activity.
The goal of WZDx is to enable widespread access to up-to-date information about dynamic conditions occurring on roads such as construction events. Currently, many IOOs maintain data on work zone activity. However, a lack of common data standards and convening mechanisms makes it difficult and costly for third parties such as original equipment manufacturers (OEMs) and navigation applications to access and use these data across various jurisdictions. WZDx defines a common language for describing work zone information. This simplifies the design process for producers and the processing logic for consumers and makes work zone data more accessible.
Specifically, WZDx defines the structure and content of several GeoJSON documents that are each intended to be distributed as a data feed. The feeds describe a variety of high-level road work-related information such as the location and status of work zones, detours, and field devices.
- Data Feeds
- Repository Organization
- Project Description
- Contact Information
- Release Notes
- Getting Started
- JSON Schemas
- Contributions
- Versioning
- License
WZDx defines the structure and content of multiple distinct data feeds. Each feed is distributed as a single GeoJSON file and is represented by both human-friendly documentation in the spec-content directory and a JSON Schema in /schemas. Each feed is designed for a specific use case.
| Feed Name | Description | Producer | Consumer | Uses | Content |
|---|---|---|---|---|---|
| Work Zone Feed | Provides high-level information about events occurring on roadways (called "road events") related to work zones that impact the characteristics of the roadway and involve a change from the default state (such as a lane closure). The Work Zone Feed is the original work zone data exchange feed and was previously named "WZDxFeed". | Agencies responsible for managing roadways and road work, typically state and local DOTs. | Traveling public via third parties such as mapping companies and CAVs. | Route planning; increased awareness; "put work zones on the map". | Work zone and detour road events (see WorkZoneRoadEvent and DetourRoadEvent). |
| Device Feed | Provides information (location, status, live data) about field devices deployed on the roadway in work zones. | Work zone equipment manufacturers or vendors. | Agencies responsible for managing roadways and permitting work, typically state and local DOTs. Third parties such as mapping companies and CAVs may also be interested in field device information. | Simplifies design process for agencies wanting to interface with equipment manufacturers; aids in dynamically generating a Work Zone Feed with accurate information; reduces effort for manufacturers to conform to different agencies requirements. | Field devices (see FieldDeviceFeature). |
The WZDx Specification has also been extended to define data feeds for representing other types of road events, such as restrictions (included in WZDx v4.0 as the RoadRestrictionFeed), crashes, disasters, and strong winds. The specification for those feeds is available at the Transportation Data Exchange (TDx) GitHub site.
The WZDx Specification repository contains several files and subdirectories.
- documents: supplementary PDF and Word documents such as the WZDx Early Adopter's Guide and WZDx Data Feed Self Validation Checklist.
- examples: example GeoJSON documents from WZDx data feeds. examples/README.md describes the content of this directory in detail.
- images: the images that are referenced by other Markdown files in the repository.
- schemas: contains JSON Schemas for each of the feeds defined by WZDx for feed validation.
- spec-content: details the data content of the WZDx specification, including objects, property names and types, and enumerated types. spec-content/README.md describes the content of this directory in detail.
- Creating_a_WZDx_Feed.md: information to assist in creating a WZDx data feed, such as the feed format, business rules, and validation tools.
- LICENSE: the Creative Commons Zero v1.0 Universal license that the repository is licensed under.
- README.md (this document): information about the WZDx effort and navigating the repository.
- RELEASES.md: detailed information about every release of the WZDx specification.
What is the WZDx Specification? The Work Zone Data Exchange (WZDx) Specification enables infrastructure owners and operators (IOOs) to make harmonized work zone data available for third-party use. The intent is to make travel on public roads safer and more efficient through ubiquitous access to data on work zone activity. Specifically, the project aims to get data on work zones to vehicles to help automated driving systems (ADS) and human drivers navigate more safely.
Why was WZDx developed? Improving access to work zone data was one of the top needs identified through the US Department of Transportation (USDOT) Data for Automated Vehicle Integration (DAVI) effort.
Up-to-date information about dynamic conditions occurring on roads – such as construction events – can help ADS and humans navigate safely and efficiently. Many IOOs maintain data on work zone activity. However, a lack of common data standards and convening mechanisms makes it difficult and costly for third parties – including original equipment manufacturers (OEMs) and navigation applications – to access and use these data across various jurisdictions.
Inspired by GTFS, USDOT launched WZDx to jumpstart the voluntary adoption of a basic work zone data specification through collaboration with data producers and data users.
Who was involved in developing WZDx? The Federal Highway Administration (FHWA) and Intelligent Transportation Systems Joint Program Office (ITS JPO) co-led the early stages of the WZDx project and remain actively involved along with the Bureau of Transportation Statistics (BTS), Federal Motor Carrier Safety Administration (FMCSA), and others in the USDOT.
Many data producers have set up data feeds based on the specification. These WZDx-compliant feeds and their links can be found in the Work Zone Data Exchange Feed Registry. Data producers with feeds in the registry as of February 2023 include:
- Colorado Department of Transportation
- Florida Department of Transportation
- Iowa Department of Transportation
- Massachusetts Department of Transportation
- Maricopa County Department of Transportation
- Maryland Department of Transportation
- Metropolitan Transportation Commission (California)
- Minnesota Department of Transportation
- National Park Service
- North Carolina Department of Transportation
- Oklahoma Department of Transportation
- Texas Department of Transportation
- Utah Department of Transportation
Development of WZDx versions 2.0 through 4.2 was overseen by the Work Zone Data Working Group (WZDWG), established under the Federal Geographic Data Committee (FGDC) Transportation Subcommittee (TSC) to maintain and update the WZDx Specification.
What is happening with WZDx now? The U.S. DOT’s ITS Joint Program Office has engaged ITE and SAE on a new effort that will standardize the WZDx Specification and harmonize multiple work zone-related standards. The project began in late 2022 with public facing portions beginning in early 2023. The published standard will be freely available at the conclusion of the project.
How can I get help with implementation? Review Creating_a_WZDx_Feed.md which contains information to assist in creating a WZDx data feed, such as the feed format, business rules, and validation tools.
The project repository will be updated with resources to help with implementation. If you have implementation questions, please make a new GitHub discussion if you need help implementing the WZDx Specification or have questions.
The Federal Highway Administration led efforts, via the Work Zone Data Initiative (WZDI), to develop a standard approach for collecting, organizing, and sharing data on the “when”, “where,” and “how” of work zone deployment. As part of this effort, key documents were developed and made publicly available:
- WZDI Framework provides a conceptual architecture for work zone data systems for collecting, storing, disseminating, managing, maintaining and archiving work zone activity data.
- WZDI Data Dictionary provides digital descriptions of work zone activities that enable and support transportation agencies and third party providers to describe and communicate work zone-related information to agency, private sector, and public users timely and seamlessly across multiple jurisdictions and regions.
Contact Name: ITS JPO
Contact Information: [email protected]
- Add
impacted_cds_curb_zonesproperty to the WorkZoneRoadEvent object to allow indicating if any Curb Data Specification curb zones are impacted by the work zone using new CdsCurbZonesReference object. - Add
work_zone_typeproperty to the WorkZoneRoadEvent object to allow indicating if a work zone road event represents a planned moving operation, an active moving operation, or a standard static work zone. - Add the following values to the Direction enumerated type:
inner-loopouter-loop
- Add
velocity_kphproperty to the FieldDeviceCoreDetails object to allow indicating the velocity of a field device. - Add
work-truck-with-lights-flashingto the MarkedLocationType enumerated type.
No properties were deprecated or removed in WZDx v4.2.
- Expand the description of the
geometryproperty on the RoadEventFeature object to clarify how geometry should be used to represent a road event. - Update the description of the
openandclosedenumerations of the LaneStatus enumerated type. - Update the description of the FlashingBeacon object to clarify that it should only be used as a flashing warning beacon mounted on a temporary traffic control device.
The WZDWG welcomes feedback and comments on the WZDx v4.2 Specification. Comments can be made by posting a GitHub Issue or Discussion, while suggested changes can be made using a Pull Request.
- Read about WZDWG activities Wiki and the WZDx Early Adopter's Guide.
- Learn about using GitHub as a tool for collaboration and support.
- Read Creating a WZDx feed which contains information about creating a WZDx data feed, such as the feed format, business rules, and validation tools.
- Use the Specification Content page to understand the data components of the specification.
- Consider using the IBI.WZDx .NET class library to facilitate development of a feed.
- Validate your feed output using the respective JSON Schema.
- Publish your feed and tell us about it via [email protected].
The WZDx Specification defines a JSON schema for each feed within the schemas directory. Schemas can be used to validate a WZDx feed document for compliance to the specification. The repository contains schemas for the following feeds:
- WZDx v4.1 Work Zone Feed
- WZDx v4.1 Device Feed
- WZDx v4.0 WZDxFeed
- WZDx v4.0 SwzDeviceFeed
- WZDx v4.0 RoadRestrictionFeed
- WZDx v3.1 WZDxFeed
- WZDx v3.0 WZDxFeed
- WZDx v2.0 WZDxFeed
How do I contribute to the WZDx Specification?
- Report bugs and request features via GitHub Issues.
- Ask the WZDx community for input on a question or propose an idea you have via GitHub Discussions.
- Create a GitHub Pull Request that implements new functionality or fixes a bug.
- Review and provide feedback on update issues/discussions/pull requests created by other users.
- Alternatively, email us with any questions.
- Help us improve our best practices and formatting on GitHub.
The WZDx specification uses a major.minor versioning scheme, similar to SemVer. The rules are as follows:
- The minor version number must be incremented if new, backwards compatible fields/entities/enumerations are introduced or if any existing fields/entities/enumerations are marked as deprecated.
- The major version number must be incremented if any backwards incompatible changes are introduced.
- Neither version number shall be incremented for documentation changes/clarifications that have no effect on either the specification schema or the content or structure of a GeoJSON feed file which conforms to the specification.
To view available versions, refer to the tags section of this repository.
The WZDx project is in the worldwide public domain (i.e., in the public domain within the United States - copyright and related rights in the work worldwide are waived through the CC0 1.0 Universal public domain dedication). All contributions to this project will be released under the CC0 dedication. By submitting a pull request, you are agreeing to comply with the waiver of copyright interest. see License for more details.