WZDx v3 Specification Update Subgroup Meeting Notes, 2020 06 02 - usdot-jpo-ode/wzdx GitHub Wiki

Virtual Attendees

  • Michael Hanowsky - Woolpert
  • Sabrina Mosher - SwRI
  • Rachel Ostroff - ICF
  • Adam Carreon - ArizonaDOT
  • Jingwei Xu -
  • Tom Stidham - WA DOT
  • Rob Hoyler - TomTom
  • Nisar Ahmed -
  • Weimin Huang - HERE
  • Mark Mockett
  • kristin virshbo, castle rock associates
  • Yang Cheng
  • Craig Moore - Seattle DOT
  • Rashmi Brewer - MnDOT CAV-X
  • Erik Davis
  • Erin Schoon - WisDOT
  • Kali Fogel
  • Michelle Boucher - IBI Group
  • Marysa Myers - Uber ATG
  • Sabrina Mosher - SwRI
  • Aaron Antrim - Trillium
  • Pier Castonguay -Ver-Mac
  • Hua Xiang - Maryland DOT
  • Drew Clark - Kentucky
  • Kellen Shain - Noblis
  • Wesley Alford - USDOT Volpe
  • David Craig - GM
  • Chuck Felice - UDOT
  • Jacob Brady - IBI Group
  • Polly Okunieff -ICF
  • David Rush
  • Skylar Knickerbocker -Iowa State
  • Eric P Ricciardi - Booz Allen
  • Derald W Dudley - USDOT
  • Mahsa Ettefagh - Booz Allen
  • chris brookes - MDOT
  • Nate Deshmukh Towery, USDOT

Purpose and Intended Outcomes:

  • Discuss prioritized list of issues and new pull requests
  • Gather group feedback on the proposed solutions for consideration in v3
  • Finalize pull requests for prioritized issues by June 15th
  • Provide feedback on pull requests

Agenda

  • Sign-in and Welcome
  • JSON Schema
  • Prioritized Issues and New Pull Requests for v3 Specification
  • Action Items and Next Steps

Discussion Summary

Prioritized issues and new pull requests to be considered in v3 specification were presented to the members and feedback was requested. There prioritized issues and comments received from attendees during the meeting are listed below.

  • Issue #82 - Include Detour Information for a Road Event

    • No feedback from members.
    • Moving forward with suggested solution #3: Create a new entity for detour information which includes a linestring geometry for the detour and/or other mapping/machine-focused detour information. Duplicate existing geometry; leverage existing lane modeling. Include only the fields needed to describe detours

  • Issue #10 – Metadata File

    • Single source feeds was proposed as a solution
    • Sabrina Mosher (SwRI): Right now the metadata field is optional, would the required elements of the metadata field become required in the info?
    • Kali Fogel: The metadata is agency information. It should be for a workzone contact.

  • Issue #66 - Including lane_edge_reference on every lane in a road event is confusing

    • Pier Castonguay (Ver-Mac): Agreed with setting lane edge reference at higher level
    • Kali Fogel: Could there be a default? Don't most people in the US designate from center lane, which would be left to right?
    • Jacob Brady: In the last meeting, we agreed that the left edge is lane number 1.
    • Jacob – we left it like this so data producers could choose their preference, but we can consider standardizing going forward
    • Polly Okunieff (ICF): What is the business rule for when driving is permitted on the shoulder?
    • Nate Deshmukh Towery: Kali we've heard that some cities number from right to left, which is why this was designed to be flexible upfront
    • Kali Fogel: Default is an example in the specification that does not make it required.
    • Michael Hanowsky (Woolpert): How would roadways with a center express lane be handled? Eg. center express lanes on 90/94 in Chicago?

  • Issue #67 - Change lane_number to lane_index; clarify/standardize first value

  • PR #87 - Require restriction_type for a lane_restriction

  • PR #89 - Require major.minor Format for road_event_feed_info Version Field

  • PR #88 - Lowercase Time and Spatial Verification Enumerated Type Values

  • PR #94 - Clarify Lane Types & Usage of Lanes Table

    • Polly Okunieff (ICF): Or what happens when a lane crosses the median? how is that enumerated?
    • Kali Fogel: Center lanes could be designated as separate roadways and the numbering would reflect those roadways. In LA we designate HOV and HOT lanes as separate roadways.
    • Erik Davis: Similar question. Are we at a point where we would want to introduce how to handle reversible, contra-flow, and zipper lanes when discussing lane counts, etc?
    • Craig Moore: Your right or left reference should orient in relation to the direction of the geometry used for the closure.
    • Polly Okunieff (ICF): When a lane is shifted, does it continue with the same number?
    • Kali Fogel: I have not seen lanes designated to include shoulders and it is odd. There should be a lane description.
    • Polly Okunieff (ICF): What happens when there is a widening of the road, and a lane is added?
    • David Craig detailed the lane types’ and usage of lanes proposed solution
    • Nisar Ahmed: I have seen temporary lanes get added away from the main roadway. Would that a detour or new lanes?
    • Polly will follow up with David Craig offline to discuss further, she couldn’t unmute during the meeting Clarify and get back to the v3 Subgroup about how business rules will be handled on GitHub – part of larger discussion probably, as Wes noted.

Action Items and Next Steps

  • Provide feedback on the prioritized issues and pull requests discussed today (these will have the green ‘v3’ or ‘v3 Candidate’ tags on GitHub)
  • Create final pull requests for consideration in next version of the spec. by June 15th