Web conference notes, 2025.06.05 (MDS Working Group)

MDS Working Group

• Monthly on Thursday at 9am PT, 12pm ET, 5/6pm CET - open to the public
• Zoom Registration and Join Link: https://us02web.zoom.us/meeting/register/tZAscOmhpjIuHNakPx6CNbACpjUjw1Gsucr4
  • One tap mobile: +19294362866,,84170989462#,,,,*612987# US (New York)
• Signup to the Mailing List for emails and calendar invites

Agenda

MDS 2.1 Issues, CDS, AVs, AAM

1. Intro and announcements (5 min)
   1. MDS 2.0.2 Patch Release - release notes
2. MDS 2.1 Issues (50 mins)
   1. CDS Connection #731, external references CDS proposal
   2. AV trip type for testing #905
   3. AV unplanned stopping events - clarification #758 - unplanned stops #905
   4. Advanced Air Mobility #896 - LADOT Update

Next month we will facilitate a conversation about crash data from DC's needs, following up on a prior Road Safety discussion, and make sure it's applicable to other jurisdictions.

WGSC Meeting Organizers

• Host: Pierre Bouffort, Blue Systems
• Facilitator: Michael Schnuerle, OMF
• Preparation: Michael Schnuerle, OMF
• Outreach: Michael Schnuerle, OMF
• Note taker: Michael Schnuerle, OMF

Action Items and Decisions

1. Updates to External Resources proposal (complete)
2. Leave your comments on incidents and crashes proposal and add to discussion happening
3. Advanced Air Mobility will be in a future release instead of 2.1

Minutes

• 49 Attendees
• OMF Slides
• Recording - Password *R!j8ubT

Notes

MDS 2.0.2 Patch release complete and live on MDS home page.

• 2.0.2 Patch Release
• Release notes

CDS Connection #731, external references CDS proposal

• Can align MDS/CDS with any other specs by external reference with a URL and ID connections

• Chicago sees value and will provide feedback

• LADOT sharing screen about Traffic Management Plan TMP - printed and handed out now

• Digital and immediate need for this now, what data systems are used internally, how to improve this process

• Currently using RapidPlan to generate these images now

• 1. detailed plan of the TMP does not have a full spec now
• 2. MDS can setup geofence in Policy data feed require people to use it
• 3. link to a digital policy with this new external reference

• Action item: Make data feed more generic, like a website or document, ids optional

AV trip type for testing #905

• DC using MDS for AV pilot, but needs testing trip type.
• Delivery robot setting for roaming using that trip type in DC
• Fluid movement between goods and passenger movements...
• MDS doesn't support all types of delivery b/c of complexity of goods/passengers and self/driver/AV/remote control, maybe all Delivery in 3.0
• Maybe need 'trip_purpose' custom attribute to define something like 'mapping' as part of a testing trip type

AV unplanned stopping events - clarification #758 - unplanned stops #905

• Part of incidents, lots of things to track: crashes, unplanned stops, harsh stopping/starting, vandalism, tip over, impact...

• AV 'disengagements'

• New incident event type in telemetry - time and location, id, object relevant to this object (id, type, severity, report id, type of report, contact info, more crash data like property/injury/alcohol/ped/vehicles)

• incident object gets at capturing DC's needs

• How does this get updated later at the point of impact? Can update Provider feed later historically in MDS later. Over the course of 12 hours as required they get updated with more details

• The more we flesh this out, the more valuable MDS can be for Vision Zero and reducing injuries/deaths on our roads

• DC has specific needs, so let's get started with that and have community chime in to implement. Real need at a real time now

• LADOT congestion issues sometimes, prefer robots to cars sometimes, change policy, send right mode.

• Can apply to all modes

• Chicago notes that police info is very specific and there are lots of edge cases police have to think of when creating report. Less chance for risk if it's more vague in MDS.

• Proposal includes link to a police report, where more details can be found. One reason this started in 2011 and hasn't come to fruition is the complexity and legality and variety of crash data and definitions.

• Should detailed data come in MDS, or in linked police report? Could be multiple reports like an additional one for fatalities.

• Many police reports never get edited and have mistakes, on purpose to record what was observed at the time.

• DC whether it comes in MDS or another format, by law reporting requirement details need to come through in 12 hours. Level of injury can be fluid.

• DC keep this at bare minimum for not, with option to add more details later. Don't have it in each other mode now, but would love to add that now.

• Brooks from SFMTA question: DC is requiring MDS for Waymo with permits for this new program. There was a preexisting texting clause in the law with just notification for now, crashes, limits, etc. At the moment they can come in with no data, but once permitting and rulemaking is final, MDS will be required with the permit.

• Next meeting is a deep dive on crash data in MDS!

Advanced Air Mobility #896 - LADOT Update

• Archer Aviation in CA signed an air taxi partnership with LA28 Olympics group organizing the 40 sites. Pending FAA approval at some point, LA is vested in knowing what is out there and coordinating internally (planning, world airport, LADOT, public safety divisions). There may be some air mobility, but demo level or passenger travel, unsure. Data component for any mode and integration is essential for LADOT.
• This might not make 2.1 cut off, but if FAA approval comes, then could be put into 2.2 or 3.0.

Chat

• 00:04:24 Ken Yang: Ken Yang, AECOM ([email protected])

• 00:04:25 Mike Manzella: Hi everyone, Mike Manzella - Director of Transportation Planning, City of Jersey City, NJ - happy to listen in!

• 00:04:33 Kristian Sims: Hi! First meeting. Kristian Sims - Columbus, OH

• 00:04:36 ramses madou: Hi all. Ramses Madou here from City of San Jose and Chair of the OMF board. Looking to deepen my understanding of what we are working on at the moment.

• 00:04:55 Chad Agate (Autolane): Hello everyone. First time coming to a meeting, Chad Agate, Autolane. [email protected]

• 00:05:16 Andrew Glass Hastings (OMF): Hi @Chad Agate (Autolane) - great to see you! Welcome!

• 00:05:28 Andrew Glass Hastings (OMF): @Ramses Madou, San Jose thanks for being here!

• 00:05:30 Michael Schnuerle (OMF): Agenda: https://github.com/openmobilityfoundation/mobility-data-specification/wiki/Web-conference-notes,-2025.06.05-(MDS-Working-Group)

• 00:05:41 Hrishikesh Ballal (Openskies): Hello All, Hrishikesh from Openskies, we work on drone traffic management and interested in AAM

• 00:05:59 Andrew Glass Hastings (OMF): Replying to "Hi everyone, Mike Ma..."

• Welcome Mike - great to have your join! Don’t hesitate to ask any questions!

• 00:06:08 Andrew Glass Hastings (OMF): Replying to "Hi! First meeting. K..."

• Hi Kristian - welcome!!

• 00:06:28 Andrew Glass Hastings (OMF): Replying to "Hello All, Hrishikes..."

• Welcome!

• 00:08:17 Michael Schnuerle (OMF): Patch release notes https://github.com/openmobilityfoundation/mobility-data-specification/releases/tag/2.0.2

• 00:10:49 Michael Schnuerle (OMF): External spec alignment https://github.com/openmobilityfoundation/curb-data-specification/pull/96

• 00:14:10 Michael Schnuerle (OMF): External Reference object https://github.com/openmobilityfoundation/curb-data-specification/blob/79166dec742fe755769626b89592841462c6c8ab/data-types.md

• 00:14:46 Zackary Campos: Reacted to "External Reference o..." with ❤️

• 00:15:51 Michael Schnuerle (OMF): Replying to "External spec alignm..."

• Leave your comments and feedback here on this Issue now or after the call.

• 00:22:20 Andrew Glass Hastings (OMF): @Vladimir Gallegos he/him (LADOT) This is a great use-case for MDS and CDS!

• 00:23:12 Andrew Glass Hastings (OMF): If you aren’t familiar with this project we just started with Seattle to communicate in real-time emergency repose zones via MDS Policy API to AVs, connected fleets, transit, etc

• Blog post: https://sdotblog.seattle.gov/2025/05/28/connected-vehicles-technology-pilot-program/

• Project website: https://www.seattle.gov/transportation/projects-and-programs/programs/digital-conflict-area-awareness-management-program

• 00:24:08 Armand Shahbazian: Reacted to "If you aren’t famili..." with ❤️

• 00:26:50 Michael Schnuerle (OMF): Reacted to "If you aren’t famili..." with ❤️

• 00:29:59 Aylene McCallum (OMF): I really like advancing this idea - it demonstrates how MDS helps with the robust testing process that these vehicles will be going through

• 00:31:43 Michael Schnuerle (OMF): Reacted to "I really like advanc..." with 👍🏼

• 00:33:12 Zackary Campos: Reacted to "If you aren’t famili..." with ❤️

• 00:34:48 Aylene McCallum (OMF): Good point Stephanie

• 00:36:36 Michael Schnuerle (OMF): Incidents https://github.com/openmobilityfoundation/mobility-data-specification/issues/613#issuecomment-2942595074

• 00:38:27 Salvador Gutierrez (LADOT): Reacted to "If you aren’t famili..." with ❤️

• 00:41:45 Aylene McCallum (OMF): What aspects of this need to be standardized and maybe which fields should be prioritized?? This could be a huge improvement / update to MDS and there are so many fields that could be added, so maybe first focus on what to focus on first?

• 00:49:56 Bryan Ovalle (Hello Llama AI): Great insight!

• 00:50:44 Aylene McCallum (OMF): This is definitely going to be hard, fleshing out the right way and the right format for collecting data

• 00:54:48 Alex Demisch (SFMTA): Do we want to separate out into two endpoints: (1)the info that could be reported in real time, e.g., there was an incident in /Events, from (2) things that comes much later after further investigation (whether 12 hours or every month) like type of crash, who was involved, police report ID, into something like the /Reports endpoint?

• 00:54:59 Michael Schnuerle (OMF): Yes maybe that’s a good idea. It could be in those two areas.

• 00:55:18 Aylene McCallum (OMF): Reacted to "Do we want to separa..." with 👍🏻

• 00:56:14 Aylene McCallum (OMF): Replying to "Do we want to separa..."

• Is there a way to have an on/off feature where an agency can identify what fields are required to report (per Stephanie's comments)?

• 00:57:35 Michael Schnuerle (OMF): Replying to "Do we want to separa..."

• Yes this can be done in the MDS Policy Requirements file the city provides.

• 00:57:55 Armand Shahbazian: Apparently City of Redmond, WA received interest from Zipline to do drone delivery - I'm meeting with them in a couple weeks and may have some more to share: Pagliacci Pizza | Elevating Our Game: Sustainable Pagliacci | Pagliacci Pizza

• 00:58:14 Bryan Ovalle (Hello Llama AI): Reacted to "Apparently City of R..." with 👍

• 00:58:48 Michael Schnuerle (OMF): Reacted to "Apparently City of R..." with 👀

• 00:58:49 Aylene McCallum (OMF): Replying to "Apparently City of R..."

• Of course it is a pizza company innovating delivery

• 00:59:02 Aylene McCallum (OMF): Reacted to "Apparently City of R..." with 🍕

• 00:59:49 Armand Shahbazian: Reacted to "Of course it is a pi..." with 😆

• 01:00:04 Aylene McCallum (OMF): Don't forget to add comments / questions / ideas in GitHub and feel free to continue the conversation on the OMF's Slack for OMF members.

• 01:00:51 Chay Mosqueda | WFRC: Thank you!