Work Zone Data Exchange (WZDx) Specification

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 seeks to be a common language for describing road events, simplying the design process for producers and the processing logic for consumers, and making work zone data more accessible.

Repostitory Organization

The WZDx Specification repository contains two main subdirectories, each containing their own README file with additional information about the purpose and files within:

1. create-feed, which contains information regarding the creation of a WZDx feed, including feed format, example feeds, JSON schemas, and validation tools.
2. spec-content, which details the data content of the WZDx specification, including objects, property names and types, and enumerated types.

Two additional directories, images and documents, contain the images that are referenced throughout the repository and PDF and Word documents such as the WZDx Early Adopter's Guide and WZDx Data Feed Self Validation Checklist.

Contents

• Creating a WZDx Feed
  • Example Feed GeoJSON Files
    • LineString Examples
      • Comprehensive
      • Local Access Only (bidirectional)
      • Simple Work Zone
      • Lane Shift
      • Shoulder Closure (bidirectional)
      • Detour
      • Recurring Work
    • MultiPoint Examples
      • Comprehensive
      • Local Access Only (bidirectional)
      • Simple Work Zone
      • Lane Shift
      • Shoulder Closure (bidirectional)
      • Detour
      • Recurring Work
  • JSON Schemas
    • WZDx v2.0 Feed
    • WZDx v3.0 Feed
    • WZDx v3.1 Feed
    • WZDx v4.0 Feed
• Specification Content
  • Objects
    • WZDXFeed
    • RoadEventFeedInfo
    • RoadEventDataSource
    • RoadEventFeature
    • RoadEvent
    • TypeOfWork
    • Lane
    • LaneRestriction
    • Relationship
  • Enumerated Types
    • Direction
    • EventStatus
    • EventType
    • LaneRestrictionUnit
    • LaneStatus
    • LaneType
    • LocationMethod
    • RoadRestriction
    • SpatialVerification
    • TimeVerification
    • VehicleImpact
    • WorkTypeName
• Images Used throughout the Specification
  • Object Diagram
    • Object Diagram editable draw.io file

README Outline

• Work Zone Data Exchange (WZDx) Specification
  • Repository Organization
  • Contents
• README Outline
• Project Description
• Contact Information
• Release Notes
  • [Release v3.1 (Apr 2021)]
• Getting Started
• Contributions
• Versioning
• License

Project Description

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 is WZDx being developed? Improving access to work zone data is 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. Longer-term, the goal is to enable collaborative maintenance and expansion of the specification to meet the emerging needs of ADS.

Who is 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.

Several data producers and data users voluntarily developed v1.1 of the specification in collaboration with USDOT, and 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 currently include: Texas Department of Transportation (TxDOT), Massachusetts Department of Transportation (MassDOT), Maricopa County Department of Transportation (MCDOT), and Iowa Department of Transportation (IDOT).

Going forward, the Work Zone Data Working Group (WZDWG), established under the Federal Geographic Data Committee (FGDC) Transportation Subcommittee (TSC) will maintain the WZDx Specification with the goal of publishing incremental updates to refine the features, attributes, and vocabulary needed to model work zone activity data.

How can I get help with implementation? This project repository will be continually updated with resources to help with implementation - in the meantime, please make a GitHub issue or discussion entry if you need help implementing the WZDx Specification or have questions.

The Federal Highway Administration is leading 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 have been 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 Information

Contact Name: ITS JPO

Contact Information: avdx@dot.gov

Release Notes

Release v3.1 (April 2021)

Following the major v3.0 release, the changes for the v3.1 release were developed with the goal enhancing and cleaning up the spec without making major changes or breaking backwards compatibility. Thus, in v3.1 many enumerated type values or object properties were deprecated rather than removed. Most if not all of these deprecated values will be removed in the next major release.

This repository was also renamed from jpo-wzdx to wzdx on 2021-04-05. All links pointing to jpo-wzdx will automatically redirect to the new URL.

Features

• Add local-access-only restriction
• Add license property to the RoadEventFeedInfo object

Refactoring

• Refactor LaneType enumerated type to deprecate values that can be determined from other properties of the Lane object, such as order, status, and lane_restrictions
• Add value alternating-flow to LaneStatus enumerated type and deprecate alternating-one-way
• Add road_names property to the RoadEvent object and deprecate road_name and road_number
• Deprecate the total_num_lanes property on the RoadEvent object as the RoadEvent's lanes array can be used to determine the number of lanes

Fixes

• Add optional bbox property to allow providing a GeoJSON Bounding Box for the WZDxFeed and RoadEventFeature objects
• Add an id property to the RoadEventFeature object for providing the a road event's identifier to better follow GeoJSON ID recommendations

Getting Started

The WZDWG welcomes feedback and comments on the WZDx 3.1 Specification. Comments can be made by posting a GitHub Issues or Discussions, while suggested changes can be made using a Pull Request.

1. Read about WZDWG activities Wiki and the WZDx Early Adopter's Guide
2. Learn about using GitHub as a tool for collaboration and support.
3. Use Specification Content page to understand the data components of the specification.
4. Create your own feed using example feeds and follow the business rules.
5. Validate your feed output using the WZDx v4.0 Feed JSON Schema
6. Publish your feed and tell us about it via avdx@dot.gov.

Contributions

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 GithHub 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.

Versioning

The WZDx specification uses a major.minor versioning scheme, similar to SemVer. The rules are as follows:

1. 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.
2. The major version number must be incremented if any backwards incompatible changes are introduced.
3. 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.

License

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.