Introduction
The Mobility Data Specification helps cities interact with companies who operate dock-less scooters, bicycles and car-share in the public right-of-way. MDS is a key piece of digital infrastructure that supports the effective implementation of mobility policies in cities around the world.
Regulatory agencies require to be provided with API endpoints that provide information about the businesses operations within their jurisdiction in the Mobility Data Specification (hereinafter MDS) format. If the business does not meet the agencies' requirements then it may be banned from operating in that jurisdiction.
The provider component is intended to be implemented by the mobility providers
and consumed by the regularly agencies, so this is the focus of this
documentation.
The agency and policy components are both intended to be implemented by
regulatory agencies (external - Department for Transit) and consumed by the
mobility providers (Dott).
Currently Dott supports the following versions of MDS:
Version 0.4.1 has been deprecated and it should be only used by legacy
systems.
See MDS releases for more information.
About municipalities boundaries
Municipalities requiring MDS Provider API compliance should provide an unambiguous digital source for the municipality boundary. This boundary must be used when determining which data each provider API endpoint will include (see more here).
In the actual specification, there is no /municipalities-boundaries endpoint,
however it was added to the service as an extra for the convenience of the
service consumers. Mainly, due to the fact that none of the cities has provided
the aforementioned boundaries. In absence of it the service has defaulted this
to Dott's own operational zone (this is different depending on the consumer,
i.e. Paris municipality gets Dott's operational zone for Paris).