Releases: openmobilityfoundation/mobility-data-specification
Release list
2.1.0 Release Candidate
Top Features
- Modes Overhaul: Clear support for many existing and new services, modes, vehicles, and programs
- Incidents and Crashes: New endpoint to capture crashes and incidents like unplanned stops, remote takeovers, ADS dis/engagement, tip overs, harsh braking/acceleration, near misses, vandalism, and theft
- Delivery: Full support for delivery of goods, food, packages, and freight, including sidewalk robots and app/gig deliveries
- Transit fixed route: Support for bus/shuttle/fixed route/fleets and connecting to GTFS trips, stops, and schedules
- For-hire Autonomous Vehicles: Clearer that MDS fully supports autonomous for-hire services (robotaxis), both sending and receiving data, and special understanding stopping and operational events
- Real-time Digital Policy: Better real-time solutions and geofencing down to the second, and a new push option
- Enforcement and Violations: Understand, record, and connect to reports and resolutions
See our Release Plan for more details and links.
Version
According to our semantic versioning, this is a minor release and includes items that will not break the previous functionality of 2.x.
Features
The 2.1.0 release may include the following features.
General
- Connections to CDS and other specs with External References #731, PR #946
- Move 2021 Stops, Metrics, Jurisdiction out of Beta #638, #671, #673
- Custom Attributes #984
Provider/Agency
- Add lifecycle operations service start and end to Vehicles #899, PR #931
- Clarify start, stop, cancel, end events #758
- Clarify relationship between Vehicles and Vehicles/status #955
- Multiple /vehicles requests at once #924
New Feature
- Incident and crash information, both historic and real-time, for all Modes #613, PR #944
- Includes enforcement and violation information if relevant
Policy
- Improved support for real-time Policy for emergency response #906
- Clarify Policy can require Authorization #915, PR #949
- Rule unit of distance travelled #908, PR #950
- Add geographies to Policy Requirements #873, PR #930
Passenger Services
- Clearer support for AV taxis (aka robotaxis) within Passenger Services mode #905
- Support for busses, commuter shuttles, fixed route operations, fleets #927
Car Share
Delivery
Modes
- Clearly defining and expanding scope of modes to various services. Includes new mode names: Micromobility, Passenger, Fleet, and Delivery.
These improvements stem from on-the-ground experience, learnings, and needs of OMF member cities and companies.
Meetings
Full details are in the Working Group Meetings agendas, and topics are listed in the description of each OMF public calendar event.
See a full list of all release meetings.
What's Changed
- Admin patch 2.0.2 dev by @schnuerle in #943
- Externally Reference Overlapping Data Sources (WZDz, CWZ, CDS, MDS, GBFS, GTFS, 311, Police Reports, etc) by @schnuerle in #946
- Add New SFMTA shuttle operators by @MarcusVerdoza in #945
- Add external references to MDS objects by @schnuerle in #952
- Creating an option to Push Policies by @schnuerle in #951
- Adding distance rule types and relevant rule units to policy documentation by @pierre-bouffort in #950
- Add Incidents by @schnuerle in #944
- Update providers.csv with Track My Shuttle by @MarcusVerdoza in #956
- Clarify relationship between /vehicles and /vehicles/status by @jiffyclub in #955
- Update Policy Authorization description to allow authentication by @pierre-bouffort in #949
- Add Greenwheels, update nextbike by @schnuerle in #961
- Add Sixt car-share provider to providers.csv by @bruno-cardenas in #958
- Delivery: Goods, Food, Packages, Freight by @schnuerle in #959
- Moving Metrics, Jurisdictions, Stops, and GDE out of beta by @schnuerle in #964
- Add Getaround car-share provider to providers.csv by @ThomPouillevet in #966
- Add Getaround GBFS link by @ThomPouillevet in #967
- Add service_start and service_end to Vehicle object in Provider and Agency APIs by @Mu-yi-Zhou in #931
- Update Getaround GBFS URL in providers.csv by @ThomPouillevet in #968
- MDS 2.1 Cleanup and prep by @schnuerle in #965
- Vehicle properties and maintenance by @schnuerle in #969
- Update providers.csv with Transwest by @MarcusVerdoza in #970
- Add Drop Mobility to listed providers by @philteigne in #971
- Added DoorDash as a MDS provider by @josephlaidoordash in #976
- Update fare_attributes object for micromobility mode to include rate_id by @mschwartzie in #975
- Update providers.csv with Peak Transit by @MarcusVerdoza in #978
- Feedback and Cleanup ahead of MDS 2.1 release by @schnuerle in #977
New Contributors
- @MarcusVerdoza made their first contribution in #945
- @pierre-bouffort made their first contribution in https://github.com/openmobilityfoundati...
Contributors
Assets 2
2.1.0
Top Features
- Modes Overhaul: Clear support for many existing and new services, modes, vehicles, and programs
- Incidents and Crashes: New endpoint to capture crashes and incidents like unplanned stops, remote takeovers, ADS dis/engagement, tip overs, harsh braking/acceleration, near misses, vandalism, and theft
- Delivery: Full support for delivery of goods, food, packages, and freight, including sidewalk robots and app/gig deliveries
- Transit fixed route: Support for bus/shuttle/fixed route/fleets and connecting to GTFS trips, stops, and schedules
- For-hire Autonomous Vehicles: Clearer that MDS fully supports autonomous for-hire services (robotaxis), both sending and receiving data, and special understanding stopping and operational events
- Real-time Digital Policy: Better real-time solutions and geofencing down to the second, and a new push option
- Enforcement and Violations: Understand, record, and connect to reports and resolutions
See our Release Plan for more details and links.
Version
According to our semantic versioning, this is a minor release and includes items that will not break the previous functionality of 2.x.
Features
The 2.1.0 release includes the following features.
General
- Connections to CDS and other specs with External References #731, PR #946
- Move 2021 Stops, Metrics, Jurisdiction out of Beta #638, #671, #673
- Custom Attributes #984
Provider/Agency
- Add lifecycle operations service start and end to Vehicles #899, PR #931
- Clarify start, stop, cancel, end events #758
- Clarify relationship between Vehicles and Vehicles/status #955
- Multiple /vehicles requests at once #924
New Feature
- Incident and crash information, both historic and real-time, for all Modes #613, PR #944
- Includes enforcement and violation information if relevant
Policy
- Improved support for real-time Policy for emergency response #906
- Clarify Policy can require Authorization #915, PR #949
- Rule unit of distance travelled #908, PR #950
- Add geographies to Policy Requirements #873, PR #930
Passenger Services
- Clearer support for AV taxis (aka robotaxis) within Passenger Services mode #905
- Support for busses, commuter shuttles, fixed route operations, fleets #927
Car Share
Delivery
Modes
- Clearly defining and expanding scope of modes to various services. Includes new mode names: Micromobility, Passenger, Fleet, and Delivery.
These improvements stem from on-the-ground experience, learnings, and needs of OMF member cities and companies.
Meetings
Full details are in the Working Group Meetings agendas, and topics are listed in the description of each OMF public calendar event.
See a full list of all release meetings.
What's Changed
- Admin patch 2.0.2 dev by @schnuerle in #943
- Externally Reference Overlapping Data Sources (WZDz, CWZ, CDS, MDS, GBFS, GTFS, 311, Police Reports, etc) by @schnuerle in #946
- Add New SFMTA shuttle operators by @MarcusVerdoza in #945
- Add external references to MDS objects by @schnuerle in #952
- Creating an option to Push Policies by @schnuerle in #951
- Adding distance rule types and relevant rule units to policy documentation by @pierre-bouffort in #950
- Add Incidents by @schnuerle in #944
- Update providers.csv with Track My Shuttle by @MarcusVerdoza in #956
- Clarify relationship between /vehicles and /vehicles/status by @jiffyclub in #955
- Update Policy Authorization description to allow authentication by @pierre-bouffort in #949
- Add Greenwheels, update nextbike by @schnuerle in #961
- Add Sixt car-share provider to providers.csv by @bruno-cardenas in #958
- Delivery: Goods, Food, Packages, Freight by @schnuerle in #959
- Moving Metrics, Jurisdictions, Stops, and GDE out of beta by @schnuerle in #964
- Add Getaround car-share provider to providers.csv by @ThomPouillevet in #966
- Add Getaround GBFS link by @ThomPouillevet in #967
- Add service_start and service_end to Vehicle object in Provider and Agency APIs by @Mu-yi-Zhou in #931
- Update Getaround GBFS URL in providers.csv by @ThomPouillevet in #968
- MDS 2.1 Cleanup and prep by @schnuerle in #965
- Vehicle properties and maintenance by @schnuerle in #969
- Update providers.csv with Transwest by @MarcusVerdoza in #970
- Add Drop Mobility to listed providers by @philteigne in #971
- Added DoorDash as a MDS provider by @josephlaidoordash in #976
- Update fare_attributes object for micromobility mode to include rate_id by @mschwartzie in #975
- Update providers.csv with Peak Transit by @MarcusVerdoza in #978
- Feedback and Cleanup ahead of MDS 2.1 release by @schnuerle in #977
New Contributors
- @pierre-bouffort made their first contribution in #950
- @bruno-cardenas made their first contribution in https://github.com/openmobilityfoundation...
Contributors
Assets 2
2.0.2
Release 2025.06.04
The 2.0.2 release fixes some minor issues and typos to help make the specification clearer.
CHANGES
See the closed PRs tagged with Milestone 2.0.2 and Issues for a full list of changes.
- Update mailing list link
- Update GBFS recommendation to 3.0
- Multiple new provider IDs added
- Fix trip_stop event for two modes
- Include stop_id in Events as intended
- Conditionally Require three fields in Stops, if part of SLA
- Define Conditionally Required, Optional, and Required if Applicable fields
ACKNOWLEDGEMENTS
Thank you to our current and past steering committee members, GitHub pull request creators (INRIX, SFMTA, Populus), issue creators (INRIX, SFMTA, Populus, DeutscheBahnConnect, Starship, MyWheels, Flamingo, MobilityData, GoSharing, HelloRide, Scooty) for this release, and for the organizations that participated on our weekly working group calls.
What's Changed
- Release 2.0.1 from main to dev by @schnuerle in #894
- Identifier for Starship Technologies by @schnuerle in #898
- Add DeutscheBahnConnect by @franping in #900
- Added MyWheels by @schnuerle in #902
- Add Flamingo by @mplsmitch in #909
- Update recommended GBFS version to v3.0 by @richfab in #910
- Add 3KM provider ID by @mplsmitch in #913
- Update providers.csv with GoSharing by @selcuk-karanuh-alg in #923
- Add SFMTA shuttle operators by @mplsmitch in #921
- Update Passenger Services Mode for new commuter shuttle fields by @matthewmarwedel in #927
- HelloRide update provider info by @zhaoshuci in #916
- Remove README reference to MDS-Announce mailing list by @mplsmitch in #926
- Register Scooty as a Provider by @magnushub-ltd in #933
- Fix vehicle status payload key by @jiffyclub in #935
- Return only relevant geographies in Provider Reports by @alexdemisch in #930
- Update GTFS Fixed Route data types by @schnuerle in #937
- Real-time Policy Improvements and Clarifications by @schnuerle in #928
- Conditionally Require Fields in MDS Stops Endpoint Related to Station Based Program/SLA Metrics by @mschwartzie in #934
- Trip Stop Clarifications by @schnuerle in #938
- Conditional and Optional field definitions by @schnuerle in #939
- Release 2.0.2 by @schnuerle in #940
New Contributors
- @franping made their first contribution in #900
- @mplsmitch made their first contribution in #909
- @richfab made their first contribution in #910
- @selcuk-karanuh-alg made their first contribution in #923
- @matthewmarwedel made their first contribution in #927
- @zhaoshuci made their first contribution in #916
- @magnushub-ltd made their first contribution in #933
- @mschwartzie made their first contribution in #934
Full Changelog: 2.0.1...2.0.2
Contributors
Assets 2
2.0.1
2.0.1
Release 2023-12-18
The 2.0.1 release fixes some minor issues and typos to help make the specification clearer.
CHANGES
See the closed PRs tagged with Milestone 2.0.1 and Issues for a full list of changes.
Minor updates
- #879 Clarify which vehicles are included in the MDS 2.0 /vehicles endpoint
- #868 Correction of description vehicle events (car sharing) bug Car Share
Typos and wording clarifications
- #880 Remove word "data" from provider response payload descriptions
- #894 Fixing broken links in data-types markdown document
- #876 Reports endpoint - START_DATE clarification
- #884 Fix JSON key in /vehicles/status example response
- #878 Update "status changes" to "events" in provider
Identifier updates
ACKNOWLEDGEMENTS
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.
What's Changed
Full Changelog: 2.0.0...2.0.1
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.
LICENSE and DISCLAIMER
Use of OMF Releases are bound by the OMF License and Disclaimer.
RELEASE PLAN
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.
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.
CHANGES
See the closed PRs tagged with Milestone 2.0.0 and Issues for a full list of changes.
Admin/General Changes
- Update state machine diagrams and create 3 new diagrams for each new modes
- Remove Schema and instead link to OpenAPI repo
- OpenAPI support in place of JSON Schema allows easier building of real-time MDS endpoint validation, and interactive documentation on Stoplight.
- Remove Geography from Policy
- Authorization consistency across MDS
- Make GBFS optional for some modes
- Align vehicle types to GBFS
- Updated MDS alignment with GBFS to include all of their vehicle types (including seated scooter) and the addition of new ones for modes (bus, truck, delivery robot, motorcycle), all propulsion types, and to require GBFS for only micromobility and car share (delivery robots and passenger services are option, but not well supported in GBFS).
- Added maintenance_pick_up event for out of PROW work
- Ability to send tip overs, surface type, and parking validation data if available from sensors
- New optional fields to include sensors now available and in use in the field by many micromobility companies for tip overs, surface type, and parking validation.
- Vertical accuracy for GPS telemetry
- All vehicle states are now clearly in or out of the right of way, no unknown state
- Many new provider IDs added
Modes Architecture
- Support for multiple modes/services in MDS
- Updates the base of MDS to have some shared objects and fields, and specific fields as needed for each mode.
- Adds specific modes to MDS, with help from Member Networks, and existing real world data exchanges between operators, agencies, and solution providers.
- Operators must register a unique UUID for each mode they operate under.
Passenger Services
Delivery Robots
Car Share
Work to bring modes together
- Add a "Data Provider UUID" to MDS
- New data provider id allows endpoints to include who is producing and serving up the data. Software companies and solution providers are encouraged to register for their own global UUID now to serve up operator or agency data with MDS.
- Support for Modes in Policy - specify which mode your policy applies to
Policy Reimagining
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
- Multimodal support in Policy
- Clarification on dwell time duration
- Clarification on possible values of rule_units
- Move Stops out of beta
- Policy is now public
- Updating and ending policy clarification
- Lookback period clarification
Policy Requirements
Requirements now supports linking to external use cases, and is moved out of beta because of adoption.
Agency/Provider Unification
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.
- MDS Agency and Provider Unification
- Endpoints are now identical
- Data objects are now identical, referenced in new data-type.md file
- Distinction between Agency and Provider is now simply pushing data to agencies, or pulling data from operators
- Adding trips endpoint to Agency
- Adding trip metadata to Agency
- Trip telemetry points are no longer in the trips endpoint directly, instead referenced in their own telemetry endpoint. Start and end location only is available in trips.
Provider
Reports have a new adaptive scooter special group type, and improved formatting.
- Updates to provider reports including header, date format, column names, and adaptive scooter special group type
Geography
Jurisdiction
Technical Updates
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.
- OpenAPI Schema definitions, created in
mds-openapirepo - HTTP error and bulk responses
- Accessibility 'options' renamed to 'attributes' for consistency
- Add missing event types from main list
- Fix car share event types
- Updated fare_attributes.payment_type list
- [Use last_updated consistently](https://github.com/openmobilityfoundation/mobility-data-specifica...
Contributors
Assets 2
2.0.0 Release Candidate 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.
LICENSE and DISCLAIMER
Use of OMF Releases are bound by the OMF License and Disclaimer.
RELEASE PLAN
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.
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.
CHANGES
See the closed PRs tagged with Milestone 2.0.0 and Issues for a full list of changes.
Admin/General Changes
- Update state machine diagrams and create 3 new diagrams for each new modes
- Remove Schema and instead link to OpenAPI repo
- OpenAPI support in place of JSON Schema allows easier building of real-time MDS endpoint validation, and interactive documentation on Stoplight.
- Remove Geography from Policy
- Authorization consistency across MDS
- Make GBFS optional for some modes
- Align vehicle types to GBFS
- Updated MDS alignment with GBFS to include all of their vehicle types (including seated scooter) and the addition of new ones for modes (bus, truck, delivery robot, motorcycle), all propulsion types, and to require GBFS for only micromobility and car share (delivery robots and passenger services are option, but not well supported in GBFS).
- Added maintenance_pick_up event for out of PROW work
- Ability to send tip overs, surface type, and parking validation data if available from sensors
- New optional fields to include sensors now available and in use in the field by many micromobility companies for tip overs, surface type, and parking validation.
- Vertical accuracy for GPS telemetry
- All vehicle states are now clearly in or out of the right of way, no unknown state
- Many new provider IDs added
Modes Architecture
- Support for multiple modes/services in MDS
- Updates the base of MDS to have some shared objects and fields, and specific fields as needed for each mode.
- Adds specific modes to MDS, with help from Member Networks, and existing real world data exchanges between operators, agencies, and solution providers.
- Operators must register a unique UUID for each mode they operate under.
Passenger Services
Delivery Robots
Car Share
Work to bring modes together
- Add a "Data Provider UUID" to MDS
- New data provider id allows endpoints to include who is producing and serving up the data. Software companies and solution providers are encouraged to register for their own global UUID now to serve up operator or agency data with MDS.
- Support for Modes in Policy - specify which mode your policy applies to
Policy Reimagining
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
- Multimodal support in Policy
- Clarification on dwell time duration
- Clarification on possible values of rule_units
- Move Stops out of beta
- Policy is now public
- Updating and ending policy clarification
- Lookback period clarification
Policy Requirements
Requirements now supports linking to external use cases, and is moved out of beta because of adoption.
Agency/Provider Unification
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.
- MDS Agency and Provider Unification
- Endpoints are now identical
- Data objects are now identical, referenced in new data-type.md file
- Distinction between Agency and Provider is now simply pushing data to agencies, or pulling data from operators
- Adding trips endpoint to Agency
- Adding trip metadata to Agency
- Trip telemetry points are no longer in the trips endpoint directly, instead referenced in their own telemetry endpoint. Start and end location only is available in trips.
Provider
Reports have a new adaptive scooter special group type, and improved formatting.
- Updates to provider reports including header, date format, column names, and adaptive scooter special group type
Geography
Jurisdiction
ACKNOWLEDGEMENTS
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.
What's Changed
- Release 1.2.0 to dev by @schnuerle in #720
- Added LEO and ATOM by @schnuerle in #725
- Add TukTuk provider by @schnuerle in #730
- Adding Helbiz to providers.csv by @milos-ljubinkovic in #732
- Update providers.csv by @sonnessa in https://...
Contributors
Assets 2
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.
Provider
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.
1.2.0 Release Candidate 1
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.
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.
Provider
Minor Updates
- Clarify single object response on policy/geography
- Schema updates, including 645, 687, 683
- Add VeoRide, Boaz Bikes, and update Superpedestrian provider IDs
ACKNOWLEDGEMENTS
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.
1.1.1
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.
CHANGES
1.1.0
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.
LICENSE and DISCLAIMER
Use of OMF Releases are bound by the OMF License and Disclaimer.
RELEASE PLAN
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.
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.1.0 and Issues for a full list of changes.
MDS
Minor Updates
- Unregistered error
- Geography updates
- Stops updates
- Response time expectations
- Geography publish date field consistency
- Adding more cities using MDS
- Adding more providers using MDS
- Added a section for third party software companies using MDS and cleaned up home page, moving list content to the OMF website
- Update geography_json field type
Provider
Agency
- N/A
Policy
Geography
Metrics
Jurisdiction
ACKNOWLEDGEMENTS
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.