A data standard to enable two-way communication between mobility companies and local governments.
The Mobility Data Specification (MDS), a project of the Open Mobility Foundation (OMF), is a set of Application Programming Interfaces (APIs) focused on shared mobility services such as dockless scooters, bicycles, mopeds, and carshare, and inspired by projects like GTFS and GBFS. MDS is a digital tool that helps cities better manage transportation in the public right of way, standardizing communication and data-sharing between cities and private mobility providers, allowing cities to share and validate policy digitally, and enabling vehicle management and better outcomes for residents.
MDS is a key piece of digital infrastructure that supports the effective implementation of mobility policies in cities around the world. For a high level overview and visuals, see the About MDS page on the OMF website.
MDS is an open-source project originally created by the Los Angeles Department of Transportation (LADOT). In November 2019, stewardship of MDS and the ownership of this repository were transferred to the Open Mobility Foundation. GitHub automatically redirects any links to this repository from the
CityOfLosAngelesorganization to the
openmobilityfoundationinstead. MDS continues to be used by LADOT and many other municipalities and companies.
MDS is comprised of six distinct APIs, with multiple endpoints under each API:
MDS is designed to be a modular kit-of-parts. Regulatory agencies can use the components of the API that are appropriate for their needs. An agency may choose to use only
policy. Other APIs like
metricscan be used in coordination as described with these APIs or sometimes on their own. Or agencies may select specific elements (endpoints) from each API to help them implement their goals. Development of the APIs takes place under the guidance of the OMF's MDS Working Group.
Many parts of the MDS definitions and APIs align across each other. In these cases, consolidated information can be found on the General Information page.
You can read more in our Understanding the different MDS APIs guide.
All MDS compatible Provider feeds must also expose a public GBFS feed. Compatibility with GBFS 2.0 or greater is advised due to privacy concerns and support for micromobility. See our MDS Vehicles Guide for how MDS Provider
/vehiclescan be used by regulators instead of the public GBFS
/free_bike_status. Additional information on MDS and GBFS can be found in this guidance document.
The Mobility Data Specification is an open source project with all development taking place on GitHub and public meetings through our MDS Working Group. Comments and ideas can be shared by starting a discussion, creating an issue, suggesting changes with a pull request, and attending meetings. Before contributing, please review our OMF CONTRIBUTING and CODE OF CONDUCT pages to understand guidelines and policies for participation.
Read our How to Get Involved in the Open Mobility Foundation blog post for more detail and an overview of how the OMF is organized.
For other questions about MDS or media inquiries please contact the OMF directly on our website.
OMF Members (public agencies and commercial companies) have additional participation opportunities with leadership roles within our OMF governance:
MDS has a current release (version 1.2.0), previous releases (both recommended and longer recommended for use), and upcoming releases in development. For a full list of releases, their status, recommended versions, and timelines, see the Official MDS Releases page.
The OMF provides guidance on upgrading for cities, providers, and software companies, and sample permit language for cities. See our MDS Version Guidance for best practices on how and when to upgrade MDS as new versions become available. Our complimentary MDS Policy Language Guidance document is for cities writing MDS into their operating policy and includes sample policy language.
More than 150 cities and public agencies across 6 continents around the world use MDS, and it has been implemented by most major mobility service providers.
- See our list of cities using MDS with links to public mobility websites and policy/permit documents.
Please let us know via our website or in the public discussion area if you are an agency using MDS so we can add you to the city resource list, especially if you have published your policies or documents publicly.
Over two dozen mobility service providers (MSPs) around the world use MDS, allowing them to create tools around a single data standard for multiple cities.
An open source approach to data specifications benefits cities and companies by creating a space for collaborative development, reducing costs, and nurturing a healthy, competitive ecosystem for mobility services and software tools. The open model promotes a competitive ecosystem for software tools built by dozens of software companies providing their services to cities, agencies, and providers.
Please let us know if you are using MDS in your company so we can add you to the list.
MDS includes information about vehicles, their location, and trips taken on those vehicles to allow agencies to regulate their use in the public right of way and to conduct transportation planning and analysis. While MDS is not designed to convey personal information about the users of shared mobility services, data collected about mobility can be sensitive. The OMF and MDS community have created a number of resources to help cities, mobility providers, and software companies handle vehicle data safely:
The OMF’s Privacy, Security, and Transparency Committee creates many of these resources, and advises the OMF on principles and practices that ensure the secure handling of mobility data. The committee – which is composed of both private and public sector OMF members – also holds regular public meetings, which provide additional resources and an opportunity to discuss issues related to privacy and mobility data. Learn more here.
How cities use MDS depends on a variety of factors: their transportation goals, existing services and infrastructure, and the unique needs of their communities. Cities are using MDS to create policy, enforce rules, manage hundreds of devices, and ensure the safe operation of vehicles in the public right of way. Some examples of how cities are using MDS in practice are:
A list of use cases is useful to show what's possible with MDS, to list what other cities are accomplishing with the data, to see many use cases up front for privacy considerations, and to use for policy discussions and policy language. More details and examples can be seen on the OMF website and our Wiki Database.
Please let us know if you have recommended updates or use cases to add.
Community projects are those efforts by individual contributors or informal groups that take place outside Open Mobility Foundation’s formalized process, complementing MDS. These related projects often push new ideas forward through experimental or locally-focused development, and are an important part of a thriving open source community. Some of these projects may eventually be contributed to and managed by the Open Mobility Foundation.
Please let us know if you create open source or private tools for implementing or working with MDS data.