A data standard to enable right-of-way regulation and two-way communication between mobility companies and local governments.
Release 2023-12-18
The 2.0.1 release fixes some minor issues and typos to help make the specification clearer.
See the closed PRs tagged with Milestone 2.0.1 and Issues for a full list of changes.
Minor updates
Typos and wording clarifications
Identifier updates
Thank you to our current and past steering committee members, GitHub pull request creators (Populus, Ride Report, Transbits, Whoosh), issue creators (City of Bergen, Nextbike, Populus, Ride Report, SFTMA, Transbits) for this release, and for the organizations that participated on our weekly working group calls.
Full Changelog: https://github.com/openmobilityfoundation/mobility-data-specification/compare/2.0.0...2.0.1
The 2.0.0 major release includes support for new mobility modes, enhancements around Policy, and the alignment of the data and structure of Agency and Provider, among many other features.
Use of OMF Releases are bound by the OMF License and Disclaimer.
Our 2.0.0 Release Plan page has more information about this history of this release, and includes a history of our public meetings with minutes.
For guidance on when to upgrade and how to discuss MDS versions in city regulations, see our MDS Policy Language Guidance and MDS Version Guidance documents.
See the closed PRs tagged with Milestone 2.0.0 and Issues for a full list of changes.
Passenger Services
Delivery Robots
Car Share
Work to bring modes together
A reimagining of Policy, including top ten most common policies are clearly defined, edge cases (dwell time, trip definition, rule units, updating/ending policies, lookback periods) are clarified, Stops is out of beta, and Policy feeds are public
Policy Requirements
Requirements now supports linking to external use cases, and is moved out of beta because of adoption.
The difference between Agency and Provider is that with Agency operators PUSH data to cities, and with Provider cities PULL data from operators. Both share the same data types, referenced in a new file, with the same endpoints and fields available.
Reports have a new adaptive scooter special group type, and improved formatting.
As part of the OpenAPI schema work, a number of technical updates were made to ensure the spec was internally consistent. A full list can be found for all issues and PRs in this date range.
mds-openapi
repoThank you to our current and past steering committee members, GitHub pull request creators (BCycle, BIRD, Compiler, Helbiz, Lacuna, Leo&Go, Nicolai Heilbuth, Poppy Mobility, Populus, Ride Report, SFMTA, Tembici, Troopy, Whoosh, Yego, Zig Zag), issue creators (ATOM Mobility, Blue Systems, Compiler, DB Systel GmbH, Drover, Lacuna, Lime, Miami-Dade, Ning Shi, OpenBikeShare, OpenMobility.be, Populus, Ride Report, San Francisco County Transportation Authority, Telofun, TukTuk) for this release, and for the scores of organizations that participated on our weekly working group calls.
/reports
column names by @wellorder in https://github.com/openmobilityfoundation/mobility-data-specification/pull/807
Full Changelog: https://github.com/openmobilityfoundation/mobility-data-specification/compare/1.2.0...2.0.0
The 2.0.0 major release includes support for new mobility modes, enhancements around Policy, and the alignment of the data and structure of Agency and Provider, among many other features.
Use of OMF Releases are bound by the OMF License and Disclaimer.
Our 2.0.0 Release Plan page has more information about this history of this release, and includes a history of our public meetings with minutes.
For guidance on when to upgrade and how to discuss MDS versions in city regulations, see our MDS Policy Language Guidance and MDS Version Guidance documents.
See the closed PRs tagged with Milestone 2.0.0 and Issues for a full list of changes.
Passenger Services
Delivery Robots
Car Share
Work to bring modes together
A reimagining of Policy, including top ten most common policies are clearly defined, edge cases (dwell time, trip definition, rule units, updating/ending policies, lookback periods) are clarified, Stops is out of beta, and Policy feeds are public
Policy Requirements
Requirements now supports linking to external use cases, and is moved out of beta because of adoption.
The difference between Agency and Provider is that with Agency operators PUSH data to cities, and with Provider cities PULL data from operators. Both share the same data types, referenced in a new file, with the same endpoints and fields available.
Reports have a new adaptive scooter special group type, and improved formatting.
Thank you to our current and past steering committee members, GitHub pull request creators (BCycle, BIRD, Helbiz, Lacuna, Leo&Go, Nicolai Heilbuth, Poppy Mobility, Populus, Ride Report, SFMTA, Tembici, Troopy, Whoosh, Yego, Zig Zag), issue creators (ATOM Mobility, Blue Systems, DB Systel GmbH, Drover, Lacuna, Lime, Miami-Dade, Ning Shi, OpenBikeShare, OpenMobility.be, Populus, Ride Report, San Francisco County Transportation Authority, Telofun, TukTuk) for this release, and for the scores of organizations that participated on our weekly working group calls.
/reports
column names by @wellorder in https://github.com/openmobilityfoundation/mobility-data-specification/pull/807
Full Changelog: https://github.com/openmobilityfoundation/mobility-data-specification/compare/1.2.0...2.0.0-rc1
The 1.2.0 minor release adds digital program Requirements, new options for policies, better GPS telemetry data, and moves Provider Vehicles out of beta. Review the Release Plan, and browse the full specification.
Use of OMF Releases are bound by the OMF License and Disclaimer.
Our 1.2.0 Release Plan page has more information about this history of this release, and includes a history of our public meetings with minutes.
For guidance on when to upgrade and how to discuss MDS versions in city regulations, see our MDS Policy Language Guidance and MDS Version Guidance documents. Also see our Upgrading to 1.0.0 guide which may be helpful if you are on an older MDS version.
See the closed PRs tagged with Milestone 1.2.0 and Issues for a full list of changes.
General MDS
Policy
Program Requirements - For agencies to describe program requirements digitally to allow providers and the public to see what MDS and GBFS versions, APIs, endpoints, and fields are required, and communicate available MDS agency information to providers.
Provider
Minor Updates
Thank you to GitHub pull request creators (Blue Systems, Compiler, E&A, Populus, Superpedestrian), issue creators (Ride Report, Populus, SPIN, Vianova), and commenters (City of Austin, Blue Systems, Compiler, E&A, Hyperknot, City of Los Angeles, MobilityData, Nivel, Populus, Ride Report, Seattle DOT, SFMTA, SPIN, Superpedestrian, Vianova) for this release, and for the dozens of organizations that participated on our weekly working group calls.
The 1.2.0 minor release adds digital program Requirements, new options for policies, better GPS telemetry data, and moves Provider Vehicles out of beta.
Use of OMF Releases are bound by the OMF License and Disclaimer.
Our 1.2.0 Release Plan page has more information about this history of this release, and includes a history of our public meetings with minutes.
For guidance on when to upgrade and how to discuss MDS versions in city regulations, see our MDS Policy Language Guidance and MDS Version Guidance documents. Also see our Upgrading to 1.0.0 guide which may be helpful if you are on an older MDS version.
See the closed PRs tagged with Milestone 1.2.0 and Issues for a full list of changes.
General MDS
Policy
Program Requirements - For agencies to describe program requirements digitally to allow providers and the public to see what MDS and GBFS versions, APIs, endpoints, and fields are required, and communicate available MDS agency information to providers.
Provider
Minor Updates
Thank you to GitHub pull request creators (Blue Systems, Compiler, E&A, Populus, Superpedstrian), issue creators (Ride Report, Populus, SPIN, Vianova), and commenters (City of Austin, Blue Systems, Compiler, E&A, Hyperknot, City of Los Angeles, MobilityData, Nivel, Populus, Ride Report, Seattle DOT, SFMTA, SPIN, Superpedestrian, Vianova) for this release, and for the dozens of organizations that participated on our weekly working group calls.
The 1.1.1 support release fixes the version validation for MDS 1.1.0 in the JSON schema, and adds comms_restored to removed state.
NOTE: See the 1.1.1 support release for the latest code that includes schema fixes.
The 1.1.0 minor release adds new top level APIs (geography, jurisdictions, metrics), privacy options (provider reports, geography-driven events, metrics), and transparency features (public endpoints). Review the Release Plan, browse the full specification, and read our blog post.
Use of OMF Releases are bound by the OMF License and Disclaimer.
Our 1.1.0 Release Plan page has more information about this history of this release, and includes a history of our public meetings with minutes.
For guidance on when to upgrade and how to discuss MDS versions in city regulations, see our MDS Policy Language Guidance and MDS Version Guidance documents. Also see our Upgrading to 1.0.0 guide which may be helpful if you are on an older MDS version.
See the closed PRs tagged with Milestone 1.1.0 and Issues for a full list of changes.
MDS
Minor Updates
Provider
Agency
Policy
Geography
Metrics
Jurisdiction
Thank you to GitHub pull request creators (Blue Systems, E&A, Populus, Ride Report, SFMTA), issue creators (E&A, Nivel, Pixelarbeit, Ride Report, SPIN), and commenters (Austin, Blue Systems, Chicago, DC, Deutsche Bahn DB Systel GmbH, Dott, E&A, Interline, Ride Report, SFMTA, SPIN) for this release, and for the dozens of organizations that participated on our weekly working group calls.
The 1.1.0 minor release adds new top level APIs (Geography, Jurisdiction, Metrics), privacy options (Provider Reports, geography-driven events, Metrics), and transparency features (public endpoints). Review the Release Plan, browse the full specification, and read our blog post.
Use of OMF Releases are bound by the OMF License and Disclaimer.
Our 1.1.0 Release Plan page has more information about this history of this release, and includes a history of our public meetings with minutes.
For guidance on when to upgrade and how to discuss MDS versions in city regulations, see our MDS Policy Language Guidance and MDS Version Guidance documents. Also see our Upgrading to 1.0.0 guide which may be helpful if you are on an older MDS version.
See the closed PRs and Issues tagged with "Milestone 1.1.0" for a full list of changes.
MDS
Minor Updates
Provider
Agency
Policy
Geography
Metrics
Jurisdiction
The 1.0.0 release reconciles and aligns many parts of the MDS specification and adds features and updates requested by the community, including many new detailed vehicle states and event types, support for Stops (for docked vehicles, dockless corrals, parking areas), and adding rates (fees/subsidies) to Policy.
Use of OMF Releases are bound by the OMF License and Disclaimer.
Our 1.0.0 Release Plan page has more information about this history of this release, and includes a history of our public meetings with minutes.
See our Upgrading to 1.0.0 guide for some on upgrading.
See the closed PRs tagged with Milestone 1.0.0 for a full list of changes.
MDS
Adding Stops - Beta
Minor Updates
Provider
Agency
Policy
The 1.0.0 release reconciles many parts of the MDS specification and adds features and updates requested by the community, including support for Stops (for docked vehicles, dockless corrals, parking areas) and adding rates to Policy.
Use of OMF Releases are bound by the OMF License and Disclaimer.
The 1.0.0 branch is available for review. See Issues and PRs tagged with Milestone 1.0.0 open, closed for a full list of changes.
MDS
Adding Stops - Beta
Minor Updates
Provider
Agency
Policy