WZDx Specification Update Subgroup Meeting #4, 2021 02 04

Virtual Attendees

• Arizona Department of Transportation - Adam Carreon
• Aurora Innovation - Marysa Myers
• Austin Transportation Department - Luke Urie
• Bentley Systems - Lee Jackson
• Booz Allen Hamilton - Eric Ricciardi
• Booz Allen Hamilton - Mahsa Ettefagh
• Bureau of Transportation Statistics/USDOT - Derald Dudley
• Bureau of Transportation Statistics/USDOT - Kenneth Steve
• Ceve - David Aylesworth
• Federal Highway Administration (FHWA) - Todd Peterson
• General Motors - David Craig
• GEWI North America – Eli Sherer
• Global Nomad GIS Services - Nazih Fino
• HAAS Alert - Jeremy Agulnek
• HERE Technologies - Weimin Huang
• Hill and Smith - Todd Hartnett
• IBI Group - Jacob Brady
• IBI Group - Michelle Boucher
• Institute of Transportation Engineers (ITE) - Siva Narla
• Iowa Department of Transportation - Dan Sprengeler
• Iowa Department of Transportation - Sinclair Stolle
• Iowa State University - Skylar Knickerbocker
• Maricopa County Department of Transportation - Faisal Saleem
• Metropolitan Transportation Commission (Bay Area) - Nisar Ahmed
• Noblis - Justin Anderson
• Noblis - Kellen Shain
• Panasonic - Lauren Cordova
• Panasonic - Ryan B.
• Regional Transportation Commission of Southern Nevada - Eneliko Mulokozi
• Seattle Department of Transportation - Craig Moore
• Southwest Research Institute - Sabrina Mosher
• Texas Department of Transportation - Jianming Ma
• University of Wisconsin - Yang Cheng
• Utah Department of Transportation - Chuck Felice
• Ver-Mac - Pier Castonguay
• Volpe - Nate Deshmukh-Towery
• Volpe - Wesley Alford
• Waze - Andrew Stober
• Woolpert - Michael Hanowsky
• Woolpert - Qassim Abdullah

Purpose and Intended Outcomes:

• Discuss the list of draft pull requests (PRs) on GitHub
• Gather member feedback on the proposed solutions for possible inclusion in the next version release of the WZDx Specification

Agenda

• Sign-in and Welcome
• Group Discussion - led by the Specification Update Subgroup Co-Chairs
  • Draft pull requests for the current cycle of specification development
• Action Items and Next Steps

Discussion Summary

• David Craig opened the meeting by going through the introductory slides and agenda.

• PR #157: Add license property to RoadEventFeedInfo

  • Derald Dudley explained the Pull Request, with supplemental detail from Jacob Brady on the licensing “string” that comprises this PR/solution.
  • Jeremy Agulnek – does all WZDx data fall under this?
    • Yes, if they agree to it, all data underneath the specification would fall under the CC0 license
    • This licensing is "optional" for now to support backwards compatibility, in the next cycle it'll likely become "required"

• PR #145: Allow specifying a GeoJSON Bounding Box for the WZDx Feed and RoadEventFeature objects

  • Jacob Brady - no changes to this PR since last time, remains as optional/up to the producer.
  • No other comments from the membership, move forward with the proposed solution.

• PR #146: Move road event ID from RoadEvent "road_event_id" to RoadEventFeature "id"

  • Jacob Brady - no changes to this PR since last time, remains as optional/up to the producer.
  • No comments from the membership, move forward with the proposed solution.

• PR #147: Refactor LaneType enumeration to deprecate values that can be determined from other properties (i.e., order/status)

  • Jacob Brady walked through pull request and the new, assembled list of lane types being changed and lane status being changed.
  • Goal of this change wasn’t to be a comprehensive review of all the lane types/remove those without value, that will still happen in the future.
    • This change specifically was just intended to clean up lane types to remove values that don’t add substance on their own – e.g., can’t be indicated by the lane’s order, status, or restrictions.
    • Mainly a PR to clean up certain values.
  • More work will be done on this pull request in the future/subsequent development cycle.

• PR #148: Deprecate the total_num_lanes property on the RoadEvent object

  • Jacob Brady walked through pull request – how to use number of items in the array to determine road event, etc.
  • Essentially, this change simplifies the specification by deprecating a field whose values is ambiguous.
    • Also creates a business rule where if lane information is provided, there must eb an entry in the lanes array for every lane in the road event, removing that ambiguity.

• PR #150: Add road_names property, deprecate road_name and road_number

  • Most clear if there’s one road property where they could add specificity to determine which highway/road name is being referred to.
  • Another change to help preserve backwards compatibility, keeping this optional to allow data producers time to make the change when this becomes “required”.

• PR #152: Local Access Only *Craig covered the proposed solution about adding a new enumerated type to the ‘RoadRestriction’ values named ‘local-access-only’.

  • This was the best-determined proposed solution coming out of the last subgroup meeting where we proposed several resolutions.

• Action Items and Next Steps

  • We will continue our discussion on the following issues during the next 6-month development cycle of the WZDx/WZDWG Specification Update Subgroup:
    • Lane type and lane status
    • Recurrent events
    • Worker presence
    • Deletion of deprecated values
  • Subgroup membership Plan on attending the March Semi-Annual WZDWG meeting where we’ll proposed these changes/PRs for voting/inclusion in the upcoming version release of the WZDx Specification.