Web conference notes, 2024.09.26 (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

Road Safety in MDS - Crashes and Incidents

Conversation about the art of the possible around safety, crashes, and incident information with shared vehicles in the public right of way. Use cases, needs, who is having these discussions now, who needs this data? What level of detail, timeliness, and accuracy is needed? What are the higher level data needs around safety for Vision Zero programs? Who will be champions for this, leaders on the discussion, and drive the work?

Intro and announcements (5 min)
Road Safety in MDS - Crashes and Incidents
1. Safety Data for Shared Vehicles (10 mins)
2. Crash/Incidents in MDS #613 (5 mins) - Michael Schnuerle, OMF and Vianova
3. Safety Data in Cities Now (5 mins) - INRIX
4. Targeted discussion and questions (30 min)

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

Leave your crash/incident comments and use cases now on #613
Invite relevant colleagues to the MDS mailing list
Reach out to the OMF with questions or thoughts
OMF Summit agenda is live, register now

Minutes

63 Attendees
OMF Slides
Recording - Password G0U=.LT3

Notes

OMF and MDS Overview

OMF is a global organization
MDS is a blueprint for data sharing between mobility companies and governments
MDS fully supports regulating two way data sharing for scooter, bikeshare, (robo)taxi, TNC, CTA, PHV, ride hail, delivery robot, car share, paratransit
Cities can write MDS data sharing requirements into operating permits for privately-owned shared mobility services in the public right of way.
LADOT is using MDS focused on integrating the taxi (including some TNCs) industry with MDS 2.0.
see slides for links and details

SAFETY DATA FOR SHARED VEHICLES

Conversation about the art of the possible around safety, crashes, emergency stopping, and incident information with shared vehicles in the public right of way.
- Use cases, needs, who is having these discussions now, who needs this data?
- What level of detail, timeliness, and accuracy is needed?
- What are the higher level data needs around safety for Vision Zero programs?
- Who will be champions for this, leaders on the discussion, and drive the work?
Problem: cities already get detailed crash reports internally via their city police, but it’s not standardized digitally, timely, or tied directly to other information in MDS like trips.
- Discussions started in 2021 for scooter share, because cities were asking.
- At the time there was not a reliable way for micromobility companies to comprehensively know about all crashes and incidents.
- Cities already received monthly aggregate crash data, and still do, but it was not tied to MDS trips or locations, and didn’t have any crash details.

Vianova

Vianova created discussion issue #613
Cities asking for scooter and bikeshare crash data in Europe and now other modes and around the world
Focus now on all kinds of safety data in cities
Merging with other data sources and making that easy
Connected vehicles, fleets, heavy braking data, ped/bike data, and comparing and adding to privately permitted fleets
Recency and real time of this data is important for city operations and emergency responses
Should be a vehicle element with a telemetry point with details about the incident

INRIX

Already getting incident data on shared and connected vehicles, need a standard like MDS
Should eventually apply to all automakers
Getting data from GM fleet, risk score from that, risky maneuvers, near miss detection
Timespan for aggregated data, year or more for hotspot analysis
Mapping this data and looking at standardizing these fields:
- Event Type Timestamp
- Location
- Detected Object
- Driver Attention Status
- Vehicle Body Type
- Direction
- Max Speed
- Max Closing Speed
- Minimum Time to Collision
Had to develop own schema, would rebuild theirs to MDS when ready

Q&A

What are the use cases and needs for crash / incident / emergency stopping data to be:
- as real-time as possible, or when available vs monthly reports
- granular and verifiable, attached to a trip and location vs aggregated reports and metrics
Becky Edmonds - real time in Seattle might not be helpful from a planning and program level and trends, would like historic data for vision zero. Granularity level appropriateness for crashes and incidents
- City may not need detail, but a vendor like INRIX might to create the right hotspot and report data
- MDS won't have all the data that crash reports have
Vlad LADOT - Having incident info as quickly as possible is important to start to take action, needs some granularity and can't wait for monthly reports
- Near miss data is essential to know how to improve infrastructure and talk to companies, even if they don't love sharing for competitive concerns, it's for the greater safety of road users
Jesse Mintz-Roth, Vision Zero San Jose - operations look at historic reports, and event centers use real time data
- Need standard report schema for all types of vehicles, vehicle types are important
- Classification of vehicles is hard, but want to know weight and height of vehicles in data
Jeremy, HAAS Alert - Info has to be as real time as possible to alert active drivers in the area and network. Real time safety network to prevent minor crashes to become major
- MDS can be real time, but doesn't have to. A vendor could get it sooner than a city department, up to permitting language.
Claudio Badea, city - The more we can standardize the better for everyone
- MDS has make model, so you can lookup other things, but for this we might want to add some optional fields for this, many fleet operators have this
What information should be included in this data?
- Exact location, vehicle information, exact location, non-identifying passenger information, severity, speed, injuries, fatalities, ped/bike?
- Other types of incidents like near misses, vandalism, assaults?
Jesse - non identifying passenger info. Maybe age?
- MDS currently count of passengers, accessibility device use. Might need to cross reference from police reports
Alex - assume that we can't get too much detail on passengers, count might be enough. Could cross reference with police report number.
- Lots of optional fields in MDS, like license plate, random driver identifier to cross reference. Some cities get this already, many don't want it, up to city. Everything will be optional.
Nat - instead of incidents, think of hierarchy of safety events: harsh acceleration, near miss, crash.
- What detail do you want for each level, like with crash severity level
- hard braking mid block vs intersection has different interventions
Jesse - vulnerable road users, age is important, weight like EVs and trucks. Homelessness people are at risk.
Christopher Rider LADOT - wants data that police departments have and send to state in data format, to compare MDS data to these reports, and what data we are lacking
- Police report number.
- Crash report standard, US and Europe, global?
William - Most incidents don't generate a police report, need this data. Especially no fault states
- Conversation started in micromobility, lots of incidents not reported

What's next

Meeting recording, slides, notes, and action items will be emailed to all attendees.
Comment on our public discussion area with your needs and use cases, to help prioritize and move this work forward.
Invite relevant colleagues to the MDS mailing list.
Reach out to the OMF with questions or thoughts, or if you’d like to join, which is free for cities, MPOs, governments.

Zoom Chat

00:02:59 Tim Adams: Tim Adams - HAAS Alert
00:03:14 Jeremy (HAAS Alert): Jeremy Agulnek - HAAS Alert
00:03:41 Nat Gale | INRIX: Nat Gale - INRIX Head of Product for Safety and Traffic
00:03:43 Michael Schnuerle (OMF): Michael Schnuerle, Open Mobility Foundation, organizer of this meeting on behalf of our MDS steering committee
00:04:04 Jesse Mintz-Roth - Vision Zero San Jose: Jesse Mintz-Roth - San Jose Vision Zero
00:04:07 Christopher Rider LADOT: Chris Rider, LADOT
00:04:23 Tina Williams ITS America: Tina Williams, ITS America
00:04:25 Marco Gorini: Marco Gorini, Philadelphia Vision Zero
00:05:11 Uyen [win] Ngo (SFMTA) | she/her: Morning all. Uyen Ngo from SFMTA
00:05:30 Crystal Killian: Crystal Killian, LADOT
00:05:46 Raquel Corchado: Raquel Corchado, CDOT
00:05:50 Vladimir Gallegos LADOT:: Vladimir Gallegos LADOT: Commercial Ride Share & Mobility (CRM).
00:05:58 Ted Randell: Ted Randell, District Department of Transportation
00:06:16 Fielding Hong, NACTO (he): Fielding Hong, NACTO
00:06:18 Michael Lawrence Evans: Michael Lawrence Evans, Office of Emerging Technology at the City of Boston
00:06:58 Angela Giacchetti (OMF): https://www.openmobilityfoundation.org/omf-summit-2024/
00:07:37 Raquel Corchado: Is some of the summit virtual or are we able to attend some of the talks virtually? Thanks!
00:09:40 Angela Giacchetti (OMF): It’s a fully in-person event. We do make recordings of the sessions available post-event but it’s designed to be experienced live 🙂
00:11:29 Raquel Corchado: Thanks!
00:12:55 Andrew Glass Hastings (OMF): Hi all - great to see so many new folks joining us from Vision Zero and traffic safety programs. It is great to have you! If you leave the call today wanting to know more or wanting to further engage please don’t hesitate to be in contact. Your participation is key to making MDS a more valuable tool for information sharing about crashes and incidents!
00:15:45 Andrew Glass Hastings (OMF): Replying to "It’s a fully in-pers..."
- It will be a great event that brings our community together! If you are in or can get to LA the Summit (as well as CoMotion immediately following) is free to attend for OMF member city staff (and OMF commercial member teams)!
00:21:30 Michael Schnuerle (OMF): The 2021 issue of crash data in MDS, that now has grown to more incidents and more modes as part of this larger discussion from MDS 2.1. https://github.com/openmobilityfoundation/mobility-data-specification/issues/613
00:30:21 Jesse Mintz-Roth - Vision Zero San Jose: Could vehicle body type be broken down to weight, height, length?
00:31:46 Christopher Rider LADOT: I'd like to see an industry standard set for levels of Hard Braking and Hard Acceleration. So far various companies/platforms have different definitions.
00:32:37 Mollie D'Agostino: Will these slides be posted?
00:33:14 Nat Gale | INRIX: Couldn't agree more, Chris! There is some research on what the thresholds are, but this schema would be a good place to establish accepted minimums
00:33:34 Brooks Jessup: Nat - is that near miss data from GM available to cities?
00:34:45 Mitch Vars | OMF: Replying to "Will these slides be..."
- Slides are on the agenda page here: https://github.com/openmobilityfoundation/mobility-data-specification/wiki/Web-conference-notes,-2024.09.26-(MDS-Working-Group)
00:34:48 Nat Gale | INRIX: Hey Brooks! Yes - cities are the main users of Safety View. Feel free to reach out to me at nat.gale@inrix.com and we can chat more
00:36:38 Gene Leynes: Although the history is a critical use case, real time is also valuable. We integrate several data sources into our situational awareness platform, which has controlled access.
00:36:48 Alex Pazuchanics (Vianova): Re: harsh braking, definitely agree. We see certain OEMs report harsh braking based on actual braking pressure, but we also use a deacceleration rate from FHWA
00:36:52 Uyen [win] Ngo (SFMTA Vision Zero) | she/her: real-time use case: for rapid response/engineering recs for fatalities or newly installed project compliance (turn calming, no turn on red signs, etc)
00:36:54 Michael Schnuerle (OMF): Replying to "Will these slides be..."
- We will incorporate the Vianova and INRIX slides into these OMF slides in the final version emailed out too.
00:38:32 Alex Pazuchanics (Vianova): Replying to "real-time use case..."
- in london, we use the data from changes in speed and braking to evaluate the effectiveness of the speed reduction programs- when compared to collision data, it's generated much more actionable feedback faster
00:39:01 Marco Gorini: Replying to "real-time use case: ..."
- agree with these. also for community engagement to be aware of what has occurred there most recently (mostly around fatalities or severe crashes)
00:40:32 Uyen [win] Ngo (SFMTA Vision Zero) | she/her: granular data use case for similar reasons: for proactive/reactive engineering treatments in response to fatal/severe crashes (e.g. is it the northbound or eastbound direction at this intersection that is problematic? are we seeing more close contacts at this intersection at this time of day/school pick up etc.)
00:40:33 Becky Edmonds: Another thought re: investigations - we do have a team that investigates fatalities, but one concern around getting even more incident data is frankly not currently having enough staff to actually be able to thoroughly investigate each one
00:40:47 Becky Edmonds: (also sorry for not raising my hand, I couldn't figure out where the button was??? but now I know. thanks all.)
00:41:24 Aylene McCallum (OMF): Replying to "Another thought re: ..."
- Perhaps with more easily accessed data, you could use that as part of the justification for more staff to support investigation
00:41:26 Alyssa Pichardo (City of Portland Bureau of Transportation): Location-based need: From a Vision Zero program perspective in a city with limited resources (Portland) our biggest issue is that we have a large data gap. In the case of Portland only Police-investigated crashes have detailed reports, they're shared to the State DOT. But the vast majority of crash reports are self-reported on a standard form to DMV. Neither is digital and need to be digitized by state DOT staff. While there is a delay in data (18 months) just having the location-based information is most important. Particularly for bike/ped. Knowing where bike and pedestrian crashes happened is the largest gap because minor crashes aren't often reported. The Oregon process isn't set up for self-reported crashes by pedestrians or people biking. It's on the driver to report. We're seeing a lot of ped / bike crash underreporting when comparing to hospital records from the county health dept. Health department can't share location because of HIPAA.
00:43:39 Aylene McCallum (OMF): Loving these comments and questions in the chat and in the meeting - please feel free to keep them coming!
00:43:45 Becky Edmonds: Replying to "Another thought re: ..."
- Yeah, though I'd say we largely have some solid maps of places we know we need to make improvements on, and I think possibly the staffing need might be better used on engineers to redesign and crews to implement the improvements.
00:48:05 Julia Friedlander: What do you imagine would be the source of information about injuries and how would it be collected?
00:48:30 Becky Edmonds: Replying to "Location-based need:..."
- Uff. That is tough. our police reports are at least available within a couple of months, but also find that they are sometimes hand written and inconsistent in how they describe especially newer modes of transport, generally need to be manually reviewed to determine more about what really happened. Also don't get many self-reported crashes for people walking and biking, and anecdotally have found that there are many reasons people don't want incidents reported.
00:50:20 Gene Leynes | Chciago | he/him: Our current crash data is organized in tables for crashes, people, and vehicles. This has been very helpful over the years because of the many to one relationships
00:51:02 Andrew Glass Hastings (OMF): Hi all - great discussion! Today the OMF launched a new individual membership program for consultants. Please see the link below if interested. And if not a consultant please do share with your networks. https://www.openmobilityfoundation.org/individual-membership-announcement/
00:51:54 Gene Leynes | Chciago | he/him: Replying to "Our current crash da..."
- I should add that even if it's redacted, its' useful. For example if minors were involved, if people were intoxicated, etc.
00:52:01 Vladimir Gallegos LADOT:: knowing if an incident was between different modes, or same modes, would be helpful.
00:52:04 Gene Leynes | Chciago | he/him: Replying to "Our current crash da..."
- car seats...
00:52:17 Uyen [win] Ngo (SFMTA Vision Zero) | she/her: SF references to see what kind of info we collect for VZ fatals - our public fatality tracker: https://app.powerbigov.us/view?r=eyJrIjoiMGNmMDdmNmQtMTA1Ni00NTFmLWI5YmQtNzZiNDU0YWE4NmJmIiwidCI6IjIyZDVjMmNmLWNlM2UtNDQzZC05YTdmLWRmY2MwMjMxZjczZiJ9
Our VZ website where we publish monthly and annual fatality reports: https://www.visionzerosf.org/maps-data/
00:53:37 Vladimir Gallegos LADOT:: we have had collisions between robots and Autonomous Vehicles.
00:54:03 Becky Edmonds: hand raising is now in the "react" menu! so confusing!!!!
00:54:26 Aylene McCallum (OMF): I'll also add that this is clearly very early in this conversation - please stay engaged as we continue to flesh this out.
00:55:53 Nat Gale | INRIX: Replying to "hand raising is now ..."
- ack! thank you found it now! haha
00:56:23 Nat Gale | INRIX: +1 on the vulnerable road user data, definitely ped and bike identification is critical
00:57:13 Alyssa Pichardo (City of Portland Bureau of Transportation): Replying to "Location-based nee..."
- We're running into an issue now that Tier 3 e-bikes are being classed as Motorcycles in crash data in Oregon per the standards set by ANSI D16-2017 definition 2.2.9. for any ebike that can reach 28 mph. That nuance of micromobility vehicles is going to be lost with this change.
01:01:52 Angela Giacchetti (OMF): Thanks for the great discussion!
01:01:55 Michael Schwartz (INRIX), he/him: Thanks!
01:01:57 Alyssa Pichardo (City of Portland Bureau of Transportation): Thanks!