2021 06 30 WZDx Specification Update Subgroup meeting

Specification Update Subgroup meeting
June 30, 2021 at 1:00 pm ET

Purpose

• Review outstanding GitHub issues
• Discuss potential approaches to address issues
• Discuss prioritization of issues for next version of WZDx spec
• Identify member advocates for prioritized issues

Agenda

• Sign-in and Welcome
• Review and Discuss Open Issues
• Discuss Issue Prioritization
• Action Items and Next Steps

Notes

Open Issues

Don't Require Discussion

#	Description	Proposed Resolution
#128	Content/value of lrs_type unclear – could refactor into an object or retire if unused	Deprecate property - no producers are using, does not provide clear value
#153	Lane_number redundant with order in Lane object	Deprecate property
#154	Require providing lane level info?	Closed issue – not all data producers can provide lane-level info.
#156	Specifying lane width on lane object as optional property	Closed issue – Lane width belongs in an “asset” layer. Could be addressed by Spec. Extension Subgroup.

Lanes issues

• Exit lane type enumerations - #5
  Currently, the spec has four lane types for exits:

lane type	description
right-exit-lane	A lane with an egress on the right
left-exit-lane	A lane with an egress on the left
right-exit-ramp	An exit ramp with an egress on the right in the direction of flow at an interchange
left-exit-ramp	An exit ramp with an egress on the left in the direction of flow at an interchange

It's not clear when to use exit-ramp vs. exit-lane
Does direction of egress matter to consumers? Most right/left values were deprecated in v3.1

• New lane types - #149
  Lane type is an attribute of the base lane that doesn't change and is used to clearly indicate lane impacts.

Restrictions and Impacts

• Additional vehicle_impact to enable real time field data - #159
  New road level impacts to communicate better road information

Verification issues

• Improve machine-usability of location_verify_method - #129
  Information could be added to the road_event_data_source to make it more machine readable

Recurring Events

• Recurrent Events - #6
  Proposals for how to include recurring events
• Mobile Work Zones - #125
  Determining the approach to integrating mobile work zones

Being Addressed by Other Subgroups

• Workers Present Data Field - #39
• Conditions for breaking a work zone into multiple road events - #78
• Technical Support for is_architectural_change - #96
• New event types - #139
• Worker Presence: humans, equipment, or both? - #173

Issue Prioritization

Action Items

Next meeting tentatively scheduled for Thursday, July 30
Action items before next meeting:

1. Participate in discussion on existing issues on GitHub related to the WZDx Specification and add suggested updates, comments, and any other feedback
2. Draft suggested specification changes on new branches
3. Create pull requests to discuss draft changes

Attendees

Name	Organization
Dave Craig*	GM
Skylar Knickerbocker*	Iowa State University
Jacob Brady*	IBI Group
Jingwei Xu*	HERE
Pat Zelinski	AASHTO
Adam Carreon	Arizona DOT
Joe D'Ginto	Aurora Innovation
Luke Urie	Austin Transportation Department
Mahsa Ettefagh	Booz Allen Hamilton
Eric Kolb	Google
Jeremy Agulnek	HAAS Alert
Todd Hartnett	Hill and Smith
Michelle Boucher	IBI Group
Ross Sheckler	iCone
Avery Ash	Inrix
Jim Williams	Inrix
Dan Sprengeler	Iowa DOT
Neil Boudreau	Massachusetts DOT
Vinod Chandran	Navjoy
Frank Winters	New York State Geographic Information Office, NSGIC President
Justin Anderson	Noblis
Kellen Shain	Noblis
Adam Graham	one.network
Chad Mann	Oregon DOT
Ryan Blake	Panasonic Cirrus
Sabrina Mosher	Southwest Research Institute
Rob Hoyler	TomTom
Joe Hunt	TxDOT
Yang Cheng	Univeristy of Wisconsin-Madison
Derald Dudley	USDOT Bureau of Transportation Statistics
Paul Jodoin	USDOT Federal Highway Administration
David Johnson	USDOT Federal Highway Administration
Mark Mockett	USDOT Volpe Center
Molly Behan	USDOT Volpe Center
David Rush	Virginia DOT
Tony Leingang	Washington State DOT
Tom Stidham	Washington State DOT
Erin Schwark	Wisconsin DOT