WZDx Specification Subgroup Meeting Notes, 2019 08 05 - usdot-jpo-ode/wzdx GitHub Wiki

In-person Attendees

  • USDOT ITS JPO - Ariel Gold
  • USDOT BTS - Derald Dudley
  • Booz Allen Hamilton - Ashley Spurlock
  • Booz Allen Hamilton - Mahsa Ettefagh

Virtual Attendees

  • AASHTO - Venkat Nallamothu
  • AASHTO - Patrick Zelinski
  • Booz Allen Hamilton - Eric Ricciardi
  • City of Austin - Jason JonMichael
  • City of Austin - Ryan Ward
  • City of Austin - Luke Urie
  • City of Detroit - Mark de la Vergne
  • City of Detroit - Sam Krassenstein
  • Colorado DOT - Manjari Bhat
  • Colorado DOT - Charles Meyer
  • DeepMap - Chris Stapleton
  • FAST at Regional Transportation Commission of Southern Nevada - Theresa Gaisser
  • General Motors - David Craig
  • Google Maps - Sandra Tseng
  • ICF - Polly Okunieff
  • ICF - Rachel Ostroff
  • INRIX - Avery Ash
  • Iowa DOT - Sinclair Stolle
  • Iowa DOT - Willy Sorenson
  • Iowa DOT - Dan Sprengeler
  • Iowa DOT - Adam Shell
  • Iowa State University - Skylar Knickerbocker
  • ITE - Siva Narla
  • Los Angeles Metropolitan Transportation Authority - Kali Fogle
  • Mapbox - Thomas Lee
  • Maricopa County DOT - Faisal Saleem
  • Massachusetts DOT - Neil Boudreau
  • Massachusetts DOT - Michelle Boucher, KCUS (Consultant for MassDOT)
  • Michigan DOT - Chris Brookes
  • Michigan DOT - Elise Feldpausch
  • Minnesota DOT - Rashmi Brewer
  • Noblis - Kellen Shain
  • OZ Engineering - Tomas Guerra
  • Seattle DOT - Craig Moore
  • SharedStreets - Kevin Webb
  • SharedStreets - Indraneel Purohit
  • Texas DOT - Cassie Jordan
  • Trillium Transit - Aaron Atrim
  • Uber - Miriam Chaum
  • Uber ATG - Sammy Ghorbanian
  • USDOT FMCSA - Thomas Kelly
  • Utah DOT - Blaine Leonard
  • Utah DOT - Chuck Felice
  • Ver-mac - Serge Beaudry
  • Ver-mac - Todd Foster
  • Ver-mac - Stephane Lapierre
  • Volpe - Leah Pickett
  • Volpe - Nate Deshmukh Towery
  • Washington State DOT - Tony Leingang
  • Washington State DOT - Steve Haapala
  • Woolpert - Daniel Michalec
  • Woolpert - Michael Hanowsky
  • Woolpert - Qassim Abdullah

Presentation Slides can be accessed here

Purpose and Intended Outcomes:

  • 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

Agenda

  • Sign in and Welcome
  • Work Zone Data Exchange (WZDx) Specification Update Subgroup Charter
  • Co-Chairs Nominees
  • WZDx Data Feed Demo
  • WZDx Specifications and GitHub Collaboration Overview
  • Action Items and Next Steps

Discussion Summary

The WZDx subgroup was presented with slides discussing the following topics:

  • Subgroup Purpose and Scope – The purpose of the WZDx Specification Update Subgroup was declared to be: Making changes to the baseline WZDx Specifications and to manage future developments and publications of the specification. It was further established that the scope of the group would be to review the current version of the WZDx specification, identify how the specification may be expanded or contracted to better meet stakeholder needs, and to recommend specification changes to the broader WZDWG
  • Subgroup Objectives – The objectives of the subgroup were specified to be:
  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

  • Subgroup Activities & Milestones – The major milestones and upcoming activities were discussed. We anticipate holding a meeting every three weeks. The tentative target dates and milestones are as follows:

    • August 29, 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
    • September 19, 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
    • October 10, 2019: Review WZDx v2 specification draft with reference implementation, addressing identified capability gaps and needs
    • October 31, 2019: Present the draft WZDx v2 to WZDWG and release for voting 10 business days (coincides with full WZDWG bi-annual meeting)
    • November 30, 2019: Make necessary adjustments and publish final WZDx v2 specification

  • Subgroup Membership and Voting – The membership in this subgroup is open to all members of Work Zone Data Working Group but requires more active engagement and frequent meetings. All members can make recommendations for change to the specification. Final review and approval of those changes will be done by the voting members of the WZDWG. The voting to those changes may take place in-person or via email. Decisions and final results will be based on majority voting.

  • Subgroup Co-Chairs Nomination – The nomination of Skylar Knickerbocker and Craig Moore as co-chairs was announced. The group is open to other additional nominations which can be achieved by sending an email to Ariel Gold. The ballots for the co-chairs will be sent out via follow up email for members to vote on. The goal is to have a minimum of 2 and maximum of 4 co-chairs who are willing to commit a few hours a week to this task. *** WZDx Data Feed Demo** – An overview of how Maricopa County went about implementing the WZDx standards to get up a feed was presented. Some of the challenges that are based on regional WZ data processing and how it was solved was explained. Over 10,000 work zone data elements are currently being processed in Maricopa County, of which a small subset are currently being tested with the WZDx specification. The goal is to translate all 10k data points to the WZDx standard. Currently a two year construction in two phases on MC85 (Buckeye Road) is being used for the WZDx Specifications pilot. This work zone is being also implemented as a smart work zone including sensors for speed detection, ARID readers, CCTV cameras, feedback signs and more. While implementing the standards the team encountered challenges with specific situations that were not handled by the v1.1 of the specification. In order to solve these there will is a need to not only solve situations on freeways but also on surface streets that require more detailed data elements. With the current implementation they have created a parallel web service to address these additional situations, while keeping the data for WZDx specifications for v1.1 as is. The json sample data for this pilot can be found at: https://api.mcdot-its.com/WZDx/Activity/Get

  • WZDx Specification GitHub Overview - an overview of WZDx Repo and full specification was given to the team along with how to create issues and open pull requests.

Action Items and Next Steps

  • Review existing issues on WZDx GitHub Repo related to the v1.1 Specification
  • Prepare individual lists of suggested updates to v1.1. Specification
  • List out potential new WZDx v2 data elements/features
  • Recommend additional technical resources