WZDx Specification Subgroup Meeting Notes, 2019 09 20

Virtual Attendees

• Eric Ricciardi - Booz Allen
• David Craig - GM
• Polly Okunieff, ICF
• Mahsa Ettefagh, Booz Allen
• Nate Deshmukh Towery, Volpe
• Ashley Spurlock, Booz Allen Hamilton
• Leah Pickett, Volpe Center
• Kellen Shain, Noblis
• Tom Lee, Mapbox
• Neil Boudreau, MassDOT
• Cassie Jordan, TxDOT
• Derald Dudley - BTS
• Daniel Farley, PennDOT
• Serge Beaudry- Ver-Mac
• Chuck Felice - Utah Dept. of Transportation
• Rachel Ostroff, ICF
• Craig Moore, Seattle DOT
• Indraneel Purohit, SharedStreets
• Jacob Brady, KCUS (Consultant to MassDOT)
• Jim Williams, INRIX
• Michelle Boucher, KCUS, Consultant for MassDOT
• Kali Fogel: RIITS
• Todd Peterson, FHWA
• Aaron Antrim, Trillium, consultant to BAH/USDOT
• Skylar Knickerbocker, Iowa State University
• Sinclair Stolle, Iowa DOT
• Joseph Kuenzi Joseph Kuenzi, Oregon DOT
• Ssammy Ghorbanian, uber ATG
• Tomas Guerra (OZ)
• Rashmi Brewer, MnDOT
• Manjari K. Bhat, Colorado Department of Transportation
• Dan Sprengeler, Iowa DOT
• Ryan Ward, City of Austin
• Sandra Tseng, Google

Presentation Slides can be accessed [here]

Purpose and Intended Outcomes:

• Discuss prioritized list of pull requests and issues on GitHub
• Identify advocates for all prioritized issues and pull requests
• Finalize next steps for several issues
• Create pull requests for prioritized issues
• Prepare to vote on prioritized pull requests

Agenda

• Sign in and Welcome
• Seattle DOT and Google Data Feed Demo
• Group Discussion –Pull Request/Issues
• Action Items and Next Steps

Discussion Summary

Seattle DOT and Google Data Feed:

• SDOT built a closure API sitting on existing in-house ArcGIS server infrastructure - events, incidents, movable bridges, railroad crossings
• Google pulls feed every 5 minutes
• Events (eg: road closures, construction, incidents) are reflected on Google Maps in ~minutes

Prioritized Pull Requests and Issues: The following issues and pull requests are scored and prioritized by the Subgroup Co-Chairs to be considered for v2 of WZDx spec.

1. PR#40 - Add Support for Location Geometry
   • Aaron Antrim: Can the SharedStreets linear reference system be useful here? for clarity: "here" means targeting street segments across different base maps with a minimum number of points.
   • Indraneel Purohit (SharedStreets): Aaron: Thanks for the clarification. Yes, the SharedStreets referencing system could be useful for closures. Provided that segments have a SharedStreets reference ID, they can be translated across basemaps. So in the example mentioned, SDOT could use some of the tools we've built to generate data w/ those ref IDs
   • Tom Lee (Mapbox): but big +1 from Mapbox to GeoJSON adoption. The point about futureproofing is well-taken, but I don't think it's a reason to delay solving the rendering problem now. GeoJSON is an IETF standard and embraced as a lingua franca by pretty much every new geo tool being written today
   • sammy ghorbanian: +1 to GeoJSON from Uber ATG as well.
   • Cassie Jordan: +1 GeoJSON
2. PR#16 - specify EPSG:4326 datum for coordinates
3. PR#33 - Add workType field to activity definition common core data
4. Issue 9 - Work Zone Projects per Feed; Issue 12 - Multiplicity values within xsd file; Issues 29 - bi-directional; PR#38 - Update Full Spec
   • simple documentation update
5. Issue#43 - Mobility Impact as a Higher Level Attribute
6. Issue #4 - Multiple Lane Type Enumerations
7. Issue#7 - Restrictions

Action Items and Next Steps

• Participate in the GitHub discussions and provide feedback on the issues/pull requests by October 7th.
• Cast your ‘yes/no/neutral’ votes on GitHub once announcement emails go out (exact voting period will be specified in the email) by October 14th.