mobility-data-specification
mobility-data-specification copied to clipboard
A data standard to enable right-of-way regulation and two-way communication between mobility companies and local governments.
The Reports endpoint provides a useful way to aggregate information that otherwise shouldn’t be provided in a raw form. This has been a helpful way for SFMTA to gather information...
Now that the `policy` API is live, I'm curious about interest in having a tool to build simple, static expressions of a policy endpoint. For example, something that could convert...
Apologies for the lack of detail but, having taken a look at schemas here, I wonder if there is interest in a schema for different types of transport interventions? See...
### Is your feature request related to a problem? Please describe. See https://github.com/TOMP-WG/TOMP-API/issues/485 It is not really a problem, but it's more about efficiency and ease of implementation. If the...
### Is your feature request related to a problem? Please describe. Yes. As more mobility providers add infrastructure in the ROW, the City of Minneapolis has been having challenges understanding...
**Note:** See the [Adding an MDS Agency ID](https://github.com/openmobilityfoundation/mobility-data-specification/wiki/Adding-an-MDS-Agency-ID) page for more help. Opening this issue will allow you as a city or governmental agency get an official agency ID for...
### Idea for an exchange I think you are doing a pretty good job and putting mobility standards on a more stable footing. We have a similar activity in Europe,...
### Is your feature request related to a problem? Please describe. As discussed during the 30 April city-services working group session, it would be very helpful for providers to analyse...
### Is your feature request related to a problem? Please describe. Currently, there are two fields in MDS to cover the cost of trips, which are optional. They are `actual_cost`...