1.2.0

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.

LICENSE and DISCLAIMER

Use of OMF Releases are bound by the OMF License and Disclaimer.

RELEASE PLAN

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.

UPGRADING

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.

CHANGES

See the closed PRs tagged with Milestone 1.2.0 and Issues for a full list of changes.

General MDS

• Richer telemetry data, including 616, 73, 51
• Add cargo_bicycle vehicle type

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.

  • Ability to express data sharing requirements in Policy
  • Method to Exclude some Provider Fields from Response
  • Retrieve operational zones from operators
  • Make Trip 'route' field optional for privacy

• Multiple options added to Policy

  • Add rate options to other rules types
  • Support parking fees by duration
  • Min and max clarity on Rules
  • Add a "rate applies when" field to Rules

Provider

• Vehicles out of beta
• Clarify use cases between MDS Vehicles and GBFS

Minor Updates

• Clarify single object response on policy/geography
• Schema updates, including 645, 687, 683, 712, 713, 716, 717, 718
• Add VeoRide, Boaz Bikes, and update Superpedestrian provider IDs

ACKNOWLEDGEMENTS

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.