https://www.transportation.gov/av/dataU.S. Department of Transportation
Office of the Assistant Secretary for Research and Technology https://www.transportation.gov/av/data 1
Work Zone Data Exchange (WZDx) Specification Update Subgroup
August 5th, 2019
Ariel Gold Data Program Manager
ITS Joint Program Office
U.S. Department of Transportation
Derald DudleyNSDI Transportation Theme Lead
Bureau of Transportation Statistics
U.S. Department of Transportation
https://www.transportation.gov/av/data
Purpose of Today’s Session
2
Purpose:
• Formalize Work Zone Data Exchange (WZDx) Specification Update Subgroup and begin
development of v.2 WZDx spec
• Discuss Subgroup Charter, activities, meeting cadence
• Nomination of Subgroup Co-Chairs
• Clarify roles and responsibilities and next steps
https://www.transportation.gov/av/data
Agenda
• Sign in and Welcome
• Work Zone Data Exchange Specification Update Subgroup Charter – (15 mins)
• Co-Chairs Nominees – (5 mins)
• WZDx Data Feed Demo – (5-10 mins)
• WZDx Specification and GitHub Collaboration Overview – (20 mins)
• Action Items and Next Steps – (5-10 mins)
3
https://www.transportation.gov/av/datahttps://www.transportation.gov/av/data 4
WZDx Specification Update Subgroup Charter
https://www.transportation.gov/av/data
Subgroup Purpose and Scope
Purpose
• Formed under the broader WDZWG, the WZDx Specification Update Subgroup will:
• Make changes to the baseline WZDx Specification
• Manage future development(s) and publications of the specification
Scope
1. Review the current version of the WZDx Specification;
2. Identify how the specification may be expanded or contracted to better meet
stakeholder needs;
3. Recommend specification changes to the broader WZDWG.
5
https://www.transportation.gov/av/data
Subgroup – Objectives
Objectives
1. Review current v1.1 WZDx Specification and any comments received from data
producer/users and new participants;
2. Recommend incremental changes to the current WZDx Specification that will better
meet current needs while advancing toward future needs;
3. Groom the backlog of potential future changes and sources of technical input;
4. Identify a harmonized process for updating, testing, and publishing future versions of
the WZDx Specification;
5. Support open scalable standards that accommodate diverse mission needs for
consuming, mapping, and analyzing work zone event information.
6
https://www.transportation.gov/av/data
Subgroup – Activities & Milestones
Activity / MilestoneTarget Date
(tentative)
• Elect a chair and establish roles, responsibilities and objectives of the Subgroup
• Review WZDx GitHub and collaboration on its wiki page
• Review the specification, Maricopa County DOT data feed demo
August 5, 2019
• Review comments/questions received from early adopters and new participants, and potential
new WZDx v2 data elements/features that have been prototyped and tested.
August 29, 2019
• Agree on short list of new elements and clarifications to add to WZDx v2, using WZDI data
dictionary and framework as a reference; agree on ownership of drafting updates.
September 19, 2019
• Review WZDx v2 specification draft with reference implementation, addressing identified
capability gaps and needs.
October 10, 2019
• Present the draft WZDx v2 to WZDWG and release for voting 10 business days.
- Coincides with full WZDWG bi-annual meeting
October 31, 2019
• Make necessary adjustments and publish final WZDx v2 specification. November 30, 2019
7https://github.com/usdot-jpo-ode/jpo-wzdx/
https://www.transportation.gov/av/data
Subgroup – Membership and Voting
Membership
• Open to all members of Work Zone Data Working Group
• Requires more active engagement and frequent meetings
Voting
• Voting may take place in-person or via email
• All members to vote on whether to recommend any proposed changes to WZDx
Specification for WZDWG review and approval
• Decisions shall be based on majority voting results
8
https://www.transportation.gov/av/datahttps://www.transportation.gov/av/data 9
Subgroup Co-Chairs Nomination
https://www.transportation.gov/av/data
Co-Chairs Nominees
• Nominees Introduction
1. Skylar Knickerbocker – Iowa State University, Institute for Transportation
2. Craig Moore – Seattle DOT
• Additional nominees are welcome
• Voting via follow-up email ballot
10
https://www.transportation.gov/av/datahttps://www.transportation.gov/av/data 11
WZDx Data Feed Demo
https://www.transportation.gov/av/data
Work Zone Data Exchange (USDOT WZDx) MC-85 Project
Tomas Guerra
OZ Engineering
Faisal SaleemMaricopa County DOT
https://www.transportation.gov/av/data
Regional WZ Data Processing
https://www.transportation.gov/av/data
Goal
14
Freight Vehicles
- WZDx format- In-vehicle displaysSmart Work Zone
- Dynamic Message Signs- Travel Times- Speed Warning- Camera Feed (TMC only)
WZDx
Info Generators Info Consumers
TMC
- Data entryTCP Plans
Construction
TMDD511 & ISPs
- TMDD format
RA
DS
Automated Vehicles
- WZDx format- In-vehicle displays
WZDx
https://www.transportation.gov/av/data
Demo Project Area
15
• Major Freight Corridor
• Long Project Duration
• Available Alternate Routes
• Challenging Industrial Area
I-10
L-101107th Ave
95thAve
75th Ave
PHASE 2PHASE 1
MC-85(Buckeye Rd)
99thAve
91st Ave 83rd Ave
https://www.transportation.gov/av/data
Traffic Control Plans
• January 2019 to June 2020, to widen MC-85 to a total of 5 lanes; storm drains, sidewalk, lighting, irrigation.
• Minimum of 1 lane in each direction open, shifting all traffic to opposite side of road, first south half, then north half.
• 24 x 7 restrictions, workers on-site M-F 8 AM to 5 PM.
16
https://www.transportation.gov/av/data
Smart Work Zone Components
ITS Components:
• Detection (Speed, Occupancy, Volume)
• ARID readers calculate travel times
• Displayed DMS content varies depending on travel times
• Excessive speed feedback signs
• CCTV Cameras
• RSU
CONST
NEXT
4 MILES
TIME TO
75TH AVE
XX MIN
CONST
NEXT
3 MILES
TIME TO
75TH AVE
XX MIN
CONST
NEXT
4 MILES
TIME TO
99TH AVE
XX MIN
CONST
NEXT
3 MILES
TIME TO
99TH AVE
XX MIN
https://www.transportation.gov/av/data
USDOT WZDx v1.1
• Work Zone Data Exchange (WZDx)• Common Core Data Specification Reference Document
• https://www.transportation.gov/av/data
https://www.transportation.gov/av/data
Sample WZDx Data FrameTraffic Control Plan #12 Eastbound
Tag Value Notes/Comments
identifier Maricopa.gov.2019012001
subidentifier TT0345;TCP_12;eastbound Use Project # and TCP #. A single TCP could generate two restrictions, one in each direction.
StartDateTime startDateTime-ver:
2019-01-20T06:35:00-07:00
By convention, we will include timezone value (-07:00) since AZ does not recognize DST; could also use UTC (Z). Suggest this be a convention for all.
EndDateTime endDateTime-est:
2019-08-20T23:59:59-07:00
How would day-time construction (8 AM to 5 PM, M-F) be represented? Make five entries?
BeginLocation roadName: MC-85 (Buckeye Rd)
roadDirection: eastbound
latitude-est: 33.435795
longitude-est: -112.259716
crossStreet: 91st Ave
EndLocation latitude-est: 33.437151
longitude-est: -112.224501
crossStreet: 79th Ave
wz_status active Could this field include a separate Date/Time field if Work Zone will only be set up during off-peak hours during an extend time period?
totalLanes 2
https://www.transportation.gov/av/data
Sample WZDx Data FrameTraffic Control Plan #12 Eastbound (Continued)
https://www.transportation.gov/av/data
Representing left turning lanes
• Shared two-way left turn center lane
• Center two-way left turn lane on an arterial
https://www.transportation.gov/av/data
MCDOT WZDxJSON API(https://api.mcdot-its.com/WZDx/Activity/Get)
https://www.transportation.gov/av/data
In-Truck Demonstration
• Drivewyze uses WZDx API and defines geo-fenced events within their product
• Swift Trucking company in-vehicle ELD automatically receives workzone notifications
https://www.transportation.gov/av/datahttps://www.transportation.gov/av/data 24
WZDx Specification GitHub Overview
https://www.transportation.gov/av/data
V1.1 WZDx Specification
• Version 1.1 of the WZDx Specification is
available for IOOs to stand up data feeds:
https://github.com/usdot-jpo-
ode/jpowzdx/blob/master/full-spec/full-
spec.md
• Feedback or comments on Specification
is submitted through the WZDx
GitHub/Issues
• Changes to Specification are
recommended through the WZDx
GitHub/Pull request
25https://github.com/usdot-jpo-ode/jpo-wzdx/
https://www.transportation.gov/av/data
V1.1 Specification Walk-Through
1. WZDx Project Repo
2. Full Specification
• Pull Requests
• Issues
3. Data Tables
4. Data Feeds
5. Data Validation Tool
https://www.transportation.gov/av/data
WZDx GitHub Wiki Overview
The following will be hosted on the WZDx GitHub Wiki page:
• Latest version of the Specification
• Reference documents (charters, roster, technical resources, etc.)
• Chair/Co-Chair announcements
• FAQs
• Meeting cadence
• Meeting minutes and recording
27
https://www.transportation.gov/av/datahttps://www.transportation.gov/av/data 28
Action Items & Next Steps
https://github.com/usdot-jpo-ode/jpo-wzdx/
https://www.transportation.gov/av/data
Subgroup Meeting #2
Next meeting tentatively scheduled for:
• August 29, 2019
• Doodle poll to be emailed out for voting
Action items before next meeting:
1. Respond to follow up email and vote on co-chairs
2. Review existing issues on GitHub/issues related to the v1.1 Specification and prepare individual lists of suggested updates
3. List out potential new WZDx v2 data elements/features
4. Recommend additional technical resources
29
https://www.transportation.gov/av/data
• WZDx Version 1.1. Common Core Data Specification
• WZDx GitHub Wiki (Day-to-Day Working Group Activities)
• FHWA WZDI Data Dictionary
• General Transit Feed Specification
• WAZE Road Closure Feeds
• Traffic Management Data Dictionary (TMDD)
• WZDx Data Validation Tool
The following are key resources for the WZDx Specification Update Subgroup:
For more information on the WZDx project or anything else related to Working Group, contact [email protected]
30
Resources
https://github.com/usdot-jpo-ode/jpo-wzdx/
https://www.transportation.gov/av/datahttps://www.transportation.gov/av/data 31
Appendix
https://github.com/usdot-jpo-ode/jpo-wzdx/
https://www.transportation.gov/av/data
Subgroup - Procedures
Procedures
1. Subgroup meetings held at the decree of the Co-Chairs and conducted as needed to meet Subgroup objectives
2. Meetings held virtually or in person
3. Agenda items will be available at least five days in advance of meeting
4. Subgroup charter reviewed and updated as needed
5. Decisions based on majority voting results
6. Issues to be resolved with the WZDWG Chair
7. Subgroup may establish additional rules and procedures for conducting business
32
https://www.transportation.gov/av/data
Subgroup - Reports
Reporting
• Subgroup shall develop an annual summary of accomplishments and planned activities
• Subgroup shall publish information about its activities on the Work Zone Data Exchange GitHub wiki page
33https://github.com/usdot-jpo-ode/jpo-wzdx/
https://www.transportation.gov/av/data
Subgroup - Approvals
Charter Approval
• This Charter will remain in effect until amended, replaced, or terminated by the WZDWG
Chair, the Transportation Subcommittee Chair, the FGDC Steering Committee, or the
FGDC Coordination Group.
• This Charter shall be posted on the GeoPlatform Communities web site at
https://communities.geoplatform.gov/ngda-transportation/work-zone-data-working-group/
as well as the Work Zone Data Exchange GitHub wiki page (https://github.com/usdot-jpo-
ode/jpo-wzdx/wiki).
34https://github.com/usdot-jpo-ode/jpo-wzdx/