-
Notifications
You must be signed in to change notification settings - Fork 5
MDS
The Mobility Data Specification (MDS) helps cities interact with companies who operate vehicles in the public right-of-way. MDS is a key piece of digital infrastructure that supports the effective implementation of mobility policies for over 115 cities around the world.
MDS has described the endpoints for cities and mobility providers. The mobility provider has a 'provider' module, and the city ('regulatory agencies') has the other modules: 'agency', 'policy', 'geography', 'jurisdiction' and 'metrics'.
Provider
| Concept | Remark |
|---|---|
| trips | A trip represents a journey taken by a mobility as a service customer with a geo-tagged start and stop point. |
| routes | Geographical representation of the trip |
| status changes | The status of the inventory of vehicles available for customer use. |
| reports | aggregated monthly file |
| special groups | to be used in the reports |
| events | The /events endpoint is a near-realtime feed of status changes, designed to give access to as recent as possible series of events. |
| stops | Stop information should be updated on a near-realtime basis by providers who operate docked mobility devices in a given municipality. |
| vehicles | The /vehicles is a near-realtime endpoint and returns the current status of vehicles in an agency's Jurisdiction and/or area of agency responsibility |
Agency
| Concept | Remark |
|---|---|
| vehicles | administer vehicles |
| telemetry | locations of vehicles |
| Stop | registration of city-managed stops |
Policy
| Concept | Remark |
|---|---|
| Policy | |
| Geography | |
| Requirement | |
| Rule (&types & units) |
Jurisdiction
| Concept | Remark |
|---|---|
| Jurisdiction |
When an asset changes state, it reports it using this endpoint. The asset has a fixed ID, so it can be traced. Pseudo personal information.
When an asset changes state, it reports it using this endpoint. The asset has no fixed ID. It is possible to find out where assets are starting a rental or returned.
Completed trips are reported using this endpoint. It are personal movements (even trackable due to the fixed ID) and thereby personal information.
Similar to the previous one, but now completely stripped.
All known modifications are due to GDPR compliance
- provider/status_change : without IDs
- provider/trips:
- without IDs and without route
- without IDs and blurred start and end location in route only
- without IDs and start and end location in route only
- provider/vehicles:
- only non-booked
- without IDs and non-booked
- without IDs
The fields in the JSON are described here, but only those that need explanation. The values in the building block, are fixed, unless they are between square brackets ([]).
| name | required | value | description |
|---|---|---|---|
| version | * | [version] | The allowed version(s), comma separated. Replace this value by f.x. "1.2,2.0,2.1" |
| url | * | [url] | The URL where this file (or endpoint) can be found, f.x. "https://example.transporter.com/gbfs/system_regions.json" |
| refreshRate | [refresh rate] | The refresh frequency. Specified in 8601 Duration (see https://en.wikipedia.org/wiki/ISO_8601#Durations). f.x. "PT5M" for 5 minutes. |
| name | value | argumentation |
|---|---|---|
| privacy | A | for all endpoints containing data without the combination location/timestamp |
| B | for all endpoints containing data with location/timestamp | |
| implementationEffort | D | When it is implemented as separate files, it is the simplest implementation, an A. This limits also the possibility to authenticate, and the available assets files more or less require an API endpoint solution. Therefore it is marked as a D. |
| reusability | E | This is a domain-specific interface, with very limited possibilities to use outside the scope of city-mobility provider |
| interoperability | A | This is a worldwide standard (A). |
| domain | A | Applied in the domain city-transport operator, it is absolutely an A |