Is your feature request related to a problem? Please describe.

Several cities are inquiring about crash data. We have been supporting them in linking this data with street usage and existing infrastructure. Crash data are today issued from manual reporting at hospitals. It provides timestamp, location and type of vehicles. This data however is not of high quality, and it is difficult to make meaningful statistics out of it and hence support decision-making on infrastructure or policies.

Describe the solution you'd like

I believe it could be valuable to add this to the /status_changes endpoint. For example, I would see a transition from on_trip to unavailable with event_type = accident/crash.
I don't know to which extent providers can obtain this information "live". Clearly a survey just after a crash is difficult. Some providers have reporting process through the website. I wonder whether the (next generation) vehicles are (will be) able to detect crash with accelerometer & speed data. A good question to operators.
Ideally this would be part of the /status_changes endpoint. However we could also imagine a separate reporting but it may add complexity.

Today, this would be very useful as historical data to get analytics on crash for shared micro-mobility and link it to street segment. However, tomorrow, in a broader context, I believe this is a great step for connected vehicles to report 'live' crash to roadway authorities and emergency services.

Is this a breaking change

I don't believe this is breaking.

Impacted Spec

Provider

Describe alternatives you've considered

An alternative could again be separate monthly reporting in csv by providers where we would see the number of crashes. However this would be left to goodwill reporting by users & providers.