You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
As a city, I would like to get insights into the intermediate destinations of station-based assets. In most cases, station-based assets are returned to the original station.
ha ha ha! They are already added on the 25th of April by Kegan. What's the formal process? Should I close this issue?
btw. what's the difference between 'trip_end' and 'trip_stop'?
It's not totally clear in the descriptions, but I think it is in each mode. trip_stop is a temporary vehicle full stop, and trip_pause is some reason the trip needs to be paused for some mode. Really I do think this is confusing and either needs to be clarified or consolidated into just trip_pause...
Is your feature request related to a problem? Please describe.
As a city, I would like to get insights into the intermediate destinations of station-based assets. In most cases, station-based assets are returned to the original station.
Describe the solution you'd like
These movements can only be detected by tracing where the assets are locked (=pauzed) during the trip.
Add at least 'pauzed' to the vehicle_event:
https://github.com/openmobilityfoundation/mobility-data-specification/blob/main/general-information.md#event-types
Is this a breaking change
Impacted Spec
provider
Describe alternatives you've considered
Demand in the trips endpoint that locations that are used as stops, must be provided in the
route
field.The text was updated successfully, but these errors were encountered: