mobility-data-specification - 2.0.2 Release

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 https://github.com/openmobilityfoundation/mobility-data-specification/pull/894
• Identifier for Starship Technologies by @schnuerle in https://github.com/openmobilityfoundation/mobility-data-specification/pull/898
• Add DeutscheBahnConnect by @franping in https://github.com/openmobilityfoundation/mobility-data-specification/pull/900
• Added MyWheels by @schnuerle in https://github.com/openmobilityfoundation/mobility-data-specification/pull/902
• Add Flamingo by @mplsmitch in https://github.com/openmobilityfoundation/mobility-data-specification/pull/909
• Update recommended GBFS version to v3.0 by @richfab in https://github.com/openmobilityfoundation/mobility-data-specification/pull/910
• Add 3KM provider ID by @mplsmitch in https://github.com/openmobilityfoundation/mobility-data-specification/pull/913
• Update providers.csv with GoSharing by @selcuk-karanuh-alg in https://github.com/openmobilityfoundation/mobility-data-specification/pull/923
• Add SFMTA shuttle operators by @mplsmitch in https://github.com/openmobilityfoundation/mobility-data-specification/pull/921
• Update Passenger Services Mode for new commuter shuttle fields by @matthewmarwedel in https://github.com/openmobilityfoundation/mobility-data-specification/pull/927
• HelloRide update provider info by @zhaoshuci in https://github.com/openmobilityfoundation/mobility-data-specification/pull/916
• Remove README reference to MDS-Announce mailing list by @mplsmitch in https://github.com/openmobilityfoundation/mobility-data-specification/pull/926
• Register Scooty as a Provider by @magnushub-ltd in https://github.com/openmobilityfoundation/mobility-data-specification/pull/933
• Fix vehicle status payload key by @jiffyclub in https://github.com/openmobilityfoundation/mobility-data-specification/pull/935
• Return only relevant geographies in Provider Reports by @alexdemisch in https://github.com/openmobilityfoundation/mobility-data-specification/pull/930
• Update GTFS Fixed Route data types by @schnuerle in https://github.com/openmobilityfoundation/mobility-data-specification/pull/937
• Real-time Policy Improvements and Clarifications by @schnuerle in https://github.com/openmobilityfoundation/mobility-data-specification/pull/928
• Conditionally Require Fields in MDS Stops Endpoint Related to Station Based Program/SLA Metrics by @mschwartzie in https://github.com/openmobilityfoundation/mobility-data-specification/pull/934
• Trip Stop Clarifications by @schnuerle in https://github.com/openmobilityfoundation/mobility-data-specification/pull/938
• Conditional and Optional field definitions by @schnuerle in https://github.com/openmobilityfoundation/mobility-data-specification/pull/939
• Release 2.0.2 by @schnuerle in https://github.com/openmobilityfoundation/mobility-data-specification/pull/940

New Contributors

• @franping made their first contribution in https://github.com/openmobilityfoundation/mobility-data-specification/pull/900
• @mplsmitch made their first contribution in https://github.com/openmobilityfoundation/mobility-data-specification/pull/909
• @richfab made their first contribution in https://github.com/openmobilityfoundation/mobility-data-specification/pull/910
• @selcuk-karanuh-alg made their first contribution in https://github.com/openmobilityfoundation/mobility-data-specification/pull/923
• @matthewmarwedel made their first contribution in https://github.com/openmobilityfoundation/mobility-data-specification/pull/927
• @zhaoshuci made their first contribution in https://github.com/openmobilityfoundation/mobility-data-specification/pull/916
• @magnushub-ltd made their first contribution in https://github.com/openmobilityfoundation/mobility-data-specification/pull/933
• @mschwartzie made their first contribution in https://github.com/openmobilityfoundation/mobility-data-specification/pull/934

Full Changelog: https://github.com/openmobilityfoundation/mobility-data-specification/compare/2.0.1...2.0.2

Published by schnuerle 9 months ago

mobility-data-specification - 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

• #872 Add GBFS endpoint for Whoosh
• #890 Add Nextbike

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: https://github.com/openmobilityfoundation/mobility-data-specification/compare/2.0.0...2.0.1

Published by schnuerle about 2 years ago

mobility-data-specification - 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 maintenancepickup 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 - Passenger services/TNC/taxi support

Delivery Robots - Support for vehicles like delivery robots

Car Share - Carshare Support

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.

• Support to reference external use cases
• Move out of beta

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

• Geography is now public, and removed from Policy

Jurisdiction

• Jurisdiction is now public

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-openapi repo
• 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 fareattributes.paymenttype list
• Use last_updated consistently across responses
• Remove extra 'data' hierarchy in responses in some endpoints

ACKNOWLEDGEMENTS

Thank 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.

What's Changed

• Release 1.2.0 to dev by @schnuerle in https://github.com/openmobilityfoundation/mobility-data-specification/pull/720
• Added LEO and ATOM by @schnuerle in https://github.com/openmobilityfoundation/mobility-data-specification/pull/725
• Add TukTuk provider by @schnuerle in https://github.com/openmobilityfoundation/mobility-data-specification/pull/730
• Adding Helbiz to providers.csv by @milos-ljubinkovic in https://github.com/openmobilityfoundation/mobility-data-specification/pull/732
• Update providers.csv by @sonnessa in https://github.com/openmobilityfoundation/mobility-data-specification/pull/729
• Added PBOT Requirements API url by @quicklywilliam in https://github.com/openmobilityfoundation/mobility-data-specification/pull/738
• Adding Yego operator by @guiguille in https://github.com/openmobilityfoundation/mobility-data-specification/pull/743
• Add Leo&Go provider by @jkurzanski in https://github.com/openmobilityfoundation/mobility-data-specification/pull/751
• Add Provider Kiwibot by @schnuerle in https://github.com/openmobilityfoundation/mobility-data-specification/pull/741
• Refactoring MDS in preparation for new modes by @marie-x in https://github.com/openmobilityfoundation/mobility-data-specification/pull/745
• Add Scoot and Revel to providers.csv by @alexdemisch in https://github.com/openmobilityfoundation/mobility-data-specification/pull/754
• Fixes to Requirements documentation by @quicklywilliam in https://github.com/openmobilityfoundation/mobility-data-specification/pull/744
• Add passenger-services to feature-modes branch by @avatarneil in https://github.com/openmobilityfoundation/mobility-data-specification/pull/735
• Request to add Troopy by @jkurzanski in https://github.com/openmobilityfoundation/mobility-data-specification/pull/768
• Update agencies.csv to include SFMTA requirements URL by @alexdemisch in https://github.com/openmobilityfoundation/mobility-data-specification/pull/776
• Request to add BCycle to Providers list by @johnadali in https://github.com/openmobilityfoundation/mobility-data-specification/pull/783
• Issue 757 publish date vs published date by @schnuerle in https://github.com/openmobilityfoundation/mobility-data-specification/pull/784
• Feature modes passenger services by @schnuerle in https://github.com/openmobilityfoundation/mobility-data-specification/pull/763
• Extending MDS to Multiple Modes - Spec Infrastructure by @schnuerle in https://github.com/openmobilityfoundation/mobility-data-specification/pull/733
• Bringing Delivery work into Delivery Robots by @schnuerle in https://github.com/openmobilityfoundation/mobility-data-specification/pull/788
• Add Tembici Provider by @josebsneto in https://github.com/openmobilityfoundation/mobility-data-specification/pull/793
• New Mode: Delivery Robots by @schnuerle in https://github.com/openmobilityfoundation/mobility-data-specification/pull/789
• New Mode - Car Share by @schnuerle in https://github.com/openmobilityfoundation/mobility-data-specification/pull/797
• Update providers.csv by @egor-bayandin in https://github.com/openmobilityfoundation/mobility-data-specification/pull/800
• fix spelling error by @mguida22 in https://github.com/openmobilityfoundation/mobility-data-specification/pull/803
• Adds Poppy Mobility by @teebot in https://github.com/openmobilityfoundation/mobility-data-specification/pull/795
• /reports column names by @wellorder in https://github.com/openmobilityfoundation/mobility-data-specification/pull/807
• Reports - Add providerid and adaptivescooter as a special group type by @alexdemisch in https://github.com/openmobilityfoundation/mobility-data-specification/pull/804
• Modes Feedback and Final Changes by @schnuerle in https://github.com/openmobilityfoundation/mobility-data-specification/pull/801
• Improve description field in Policy to require more human readable details by @jyeo17 in https://github.com/openmobilityfoundation/mobility-data-specification/pull/786
• Updating policy query parameter language to be clearer. by @janedotx in https://github.com/openmobilityfoundation/mobility-data-specification/pull/742
• Reports - Accept header media-type by @wellorder in https://github.com/openmobilityfoundation/mobility-data-specification/pull/810
• Reports - simplify start_date column by @wellorder in https://github.com/openmobilityfoundation/mobility-data-specification/pull/809
• Policy Requirements - Use Case Support by @schnuerle in https://github.com/openmobilityfoundation/mobility-data-specification/pull/813
• Replace unknown state by @jean-populus in https://github.com/openmobilityfoundation/mobility-data-specification/pull/814
• Define a "trip" for the purposes of analyses by @jiffyclub in https://github.com/openmobilityfoundation/mobility-data-specification/pull/762
• Better Telemetry error handling by @nheilbuth in https://github.com/openmobilityfoundation/mobility-data-specification/pull/740
• updated examples read.me by @jean-populus in https://github.com/openmobilityfoundation/mobility-data-specification/pull/819
• Remove 'rate' rule-type, since we can put rate_amount on any rule by @marie-x in https://github.com/openmobilityfoundation/mobility-data-specification/pull/817
• Provider/Agency API alignment by @marie-x in https://github.com/openmobilityfoundation/mobility-data-specification/pull/796
• remove hdop by @marie-x in https://github.com/openmobilityfoundation/mobility-data-specification/pull/820
• Remove Geographies from Policy and make public by @schnuerle in https://github.com/openmobilityfoundation/mobility-data-specification/pull/824
• Clarifying GBFS use with new modes by @schnuerle in https://github.com/openmobilityfoundation/mobility-data-specification/pull/825
• Agency/Provider adjustments for Modes by @schnuerle in https://github.com/openmobilityfoundation/mobility-data-specification/pull/826
• Sensors: Tip Over, Surface Type, Parking Validation by @schnuerle in https://github.com/openmobilityfoundation/mobility-data-specification/pull/829
• Agency Provider Structure Tweaks by @schnuerle in https://github.com/openmobilityfoundation/mobility-data-specification/pull/830
• Add Telofun operator by @schnuerle in https://github.com/openmobilityfoundation/mobility-data-specification/pull/831
• Updated vehicle and propulsion types and max speed by @schnuerle in https://github.com/openmobilityfoundation/mobility-data-specification/pull/833
• Added "Updating or Ending Policies" section by @schnuerle in https://github.com/openmobilityfoundation/mobility-data-specification/pull/834
• Consolidating authorization across APIs by @schnuerle in https://github.com/openmobilityfoundation/mobility-data-specification/pull/835
• Modes Cleanup for Release by @schnuerle in https://github.com/openmobilityfoundation/mobility-data-specification/pull/836
• Fix: Add missing event types by @thekaveman in https://github.com/openmobilityfoundation/mobility-data-specification/pull/849
• Fix: clean up data types by @thekaveman in https://github.com/openmobilityfoundation/mobility-data-specification/pull/848
• Agency README fixes by @thekaveman in https://github.com/openmobilityfoundation/mobility-data-specification/pull/854
• Clean ups in the General Info file by @thekaveman in https://github.com/openmobilityfoundation/mobility-data-specification/pull/855
• Clean ups in Geography by @thekaveman in https://github.com/openmobilityfoundation/mobility-data-specification/pull/858
• OpenAPI work for MDS by @schnuerle in https://github.com/openmobilityfoundation/mobility-data-specification/pull/832
• Release Candidate 2.0.0 by @schnuerle in https://github.com/openmobilityfoundation/mobility-data-specification/pull/837
• Release 2.0 push to main by @schnuerle in https://github.com/openmobilityfoundation/mobility-data-specification/pull/865

New Contributors

• @milos-ljubinkovic made their first contribution in https://github.com/openmobilityfoundation/mobility-data-specification/pull/732
• @sonnessa made their first contribution in https://github.com/openmobilityfoundation/mobility-data-specification/pull/729
• @guiguille made their first contribution in https://github.com/openmobilityfoundation/mobility-data-specification/pull/743
• @jkurzanski made their first contribution in https://github.com/openmobilityfoundation/mobility-data-specification/pull/751
• @alexdemisch made their first contribution in https://github.com/openmobilityfoundation/mobility-data-specification/pull/754
• @johnadali made their first contribution in https://github.com/openmobilityfoundation/mobility-data-specification/pull/783
• @josebsneto made their first contribution in https://github.com/openmobilityfoundation/mobility-data-specification/pull/793
• @egor-bayandin made their first contribution in https://github.com/openmobilityfoundation/mobility-data-specification/pull/800
• @mguida22 made their first contribution in https://github.com/openmobilityfoundation/mobility-data-specification/pull/803
• @teebot made their first contribution in https://github.com/openmobilityfoundation/mobility-data-specification/pull/795
• @wellorder made their first contribution in https://github.com/openmobilityfoundation/mobility-data-specification/pull/807
• @jyeo17 made their first contribution in https://github.com/openmobilityfoundation/mobility-data-specification/pull/786
• @jean-populus made their first contribution in https://github.com/openmobilityfoundation/mobility-data-specification/pull/814
• @nheilbuth made their first contribution in https://github.com/openmobilityfoundation/mobility-data-specification/pull/740

Full Changelog: https://github.com/openmobilityfoundation/mobility-data-specification/compare/1.2.0...2.0.0

Published by schnuerle almost 3 years ago

mobility-data-specification - 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 maintenancepickup 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 - Passenger services/TNC/taxi support

Delivery Robots - Support for vehicles like delivery robots

Car Share - Carshare Support

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.

• Support to reference external use cases
• Move out of beta

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

• Geography is now public, and removed from Policy

Jurisdiction

• Jurisdiction is now public

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 https://github.com/openmobilityfoundation/mobility-data-specification/pull/720
• Added LEO and ATOM by @schnuerle in https://github.com/openmobilityfoundation/mobility-data-specification/pull/725
• Add TukTuk provider by @schnuerle in https://github.com/openmobilityfoundation/mobility-data-specification/pull/730
• Adding Helbiz to providers.csv by @milos-ljubinkovic in https://github.com/openmobilityfoundation/mobility-data-specification/pull/732
• Update providers.csv by @sonnessa in https://github.com/openmobilityfoundation/mobility-data-specification/pull/729
• Added PBOT Requirements API url by @quicklywilliam in https://github.com/openmobilityfoundation/mobility-data-specification/pull/738
• Adding Yego operator by @guiguille in https://github.com/openmobilityfoundation/mobility-data-specification/pull/743
• Add Leo&Go provider by @jkurzanski in https://github.com/openmobilityfoundation/mobility-data-specification/pull/751
• Add Provider Kiwibot by @schnuerle in https://github.com/openmobilityfoundation/mobility-data-specification/pull/741
• Refactoring MDS in preparation for new modes by @marie-x in https://github.com/openmobilityfoundation/mobility-data-specification/pull/745
• Add Scoot and Revel to providers.csv by @alexdemisch in https://github.com/openmobilityfoundation/mobility-data-specification/pull/754
• Fixes to Requirements documentation by @quicklywilliam in https://github.com/openmobilityfoundation/mobility-data-specification/pull/744
• Add passenger-services to feature-modes branch by @avatarneil in https://github.com/openmobilityfoundation/mobility-data-specification/pull/735
• Request to add Troopy by @jkurzanski in https://github.com/openmobilityfoundation/mobility-data-specification/pull/768
• Update agencies.csv to include SFMTA requirements URL by @alexdemisch in https://github.com/openmobilityfoundation/mobility-data-specification/pull/776
• Request to add BCycle to Providers list by @johnadali in https://github.com/openmobilityfoundation/mobility-data-specification/pull/783
• Issue 757 publish date vs published date by @schnuerle in https://github.com/openmobilityfoundation/mobility-data-specification/pull/784
• Feature modes passenger services by @schnuerle in https://github.com/openmobilityfoundation/mobility-data-specification/pull/763
• Extending MDS to Multiple Modes - Spec Infrastructure by @schnuerle in https://github.com/openmobilityfoundation/mobility-data-specification/pull/733
• Bringing Delivery work into Delivery Robots by @schnuerle in https://github.com/openmobilityfoundation/mobility-data-specification/pull/788
• Add Tembici Provider by @josebsneto in https://github.com/openmobilityfoundation/mobility-data-specification/pull/793
• New Mode: Delivery Robots by @schnuerle in https://github.com/openmobilityfoundation/mobility-data-specification/pull/789
• New Mode - Car Share by @schnuerle in https://github.com/openmobilityfoundation/mobility-data-specification/pull/797
• Update providers.csv by @egor-bayandin in https://github.com/openmobilityfoundation/mobility-data-specification/pull/800
• fix spelling error by @mguida22 in https://github.com/openmobilityfoundation/mobility-data-specification/pull/803
• Adds Poppy Mobility by @teebot in https://github.com/openmobilityfoundation/mobility-data-specification/pull/795
• /reports column names by @wellorder in https://github.com/openmobilityfoundation/mobility-data-specification/pull/807
• Reports - Add providerid and adaptivescooter as a special group type by @alexdemisch in https://github.com/openmobilityfoundation/mobility-data-specification/pull/804
• Modes Feedback and Final Changes by @schnuerle in https://github.com/openmobilityfoundation/mobility-data-specification/pull/801
• Improve description field in Policy to require more human readable details by @jyeo17 in https://github.com/openmobilityfoundation/mobility-data-specification/pull/786
• Updating policy query parameter language to be clearer. by @janedotx in https://github.com/openmobilityfoundation/mobility-data-specification/pull/742
• Reports - Accept header media-type by @wellorder in https://github.com/openmobilityfoundation/mobility-data-specification/pull/810
• Reports - simplify start_date column by @wellorder in https://github.com/openmobilityfoundation/mobility-data-specification/pull/809
• Policy Requirements - Use Case Support by @schnuerle in https://github.com/openmobilityfoundation/mobility-data-specification/pull/813
• Replace unknown state by @jean-populus in https://github.com/openmobilityfoundation/mobility-data-specification/pull/814
• Define a "trip" for the purposes of analyses by @jiffyclub in https://github.com/openmobilityfoundation/mobility-data-specification/pull/762
• Better Telemetry error handling by @nheilbuth in https://github.com/openmobilityfoundation/mobility-data-specification/pull/740
• updated examples read.me by @jean-populus in https://github.com/openmobilityfoundation/mobility-data-specification/pull/819
• Remove 'rate' rule-type, since we can put rate_amount on any rule by @marie-x in https://github.com/openmobilityfoundation/mobility-data-specification/pull/817
• Provider/Agency API alignment by @marie-x in https://github.com/openmobilityfoundation/mobility-data-specification/pull/796
• remove hdop by @marie-x in https://github.com/openmobilityfoundation/mobility-data-specification/pull/820
• Remove Geographies from Policy and make public by @schnuerle in https://github.com/openmobilityfoundation/mobility-data-specification/pull/824
• Clarifying GBFS use with new modes by @schnuerle in https://github.com/openmobilityfoundation/mobility-data-specification/pull/825
• Agency/Provider adjustments for Modes by @schnuerle in https://github.com/openmobilityfoundation/mobility-data-specification/pull/826
• Sensors: Tip Over, Surface Type, Parking Validation by @schnuerle in https://github.com/openmobilityfoundation/mobility-data-specification/pull/829
• Agency Provider Structure Tweaks by @schnuerle in https://github.com/openmobilityfoundation/mobility-data-specification/pull/830
• Add Telofun operator by @schnuerle in https://github.com/openmobilityfoundation/mobility-data-specification/pull/831
• Updated vehicle and propulsion types and max speed by @schnuerle in https://github.com/openmobilityfoundation/mobility-data-specification/pull/833
• Added "Updating or Ending Policies" section by @schnuerle in https://github.com/openmobilityfoundation/mobility-data-specification/pull/834
• Consolidating authorization across APIs by @schnuerle in https://github.com/openmobilityfoundation/mobility-data-specification/pull/835
• Modes Cleanup for Release by @schnuerle in https://github.com/openmobilityfoundation/mobility-data-specification/pull/836

New Contributors

• @milos-ljubinkovic made their first contribution in https://github.com/openmobilityfoundation/mobility-data-specification/pull/732
• @sonnessa made their first contribution in https://github.com/openmobilityfoundation/mobility-data-specification/pull/729
• @guiguille made their first contribution in https://github.com/openmobilityfoundation/mobility-data-specification/pull/743
• @jkurzanski made their first contribution in https://github.com/openmobilityfoundation/mobility-data-specification/pull/751
• @alexdemisch made their first contribution in https://github.com/openmobilityfoundation/mobility-data-specification/pull/754
• @johnadali made their first contribution in https://github.com/openmobilityfoundation/mobility-data-specification/pull/783
• @josebsneto made their first contribution in https://github.com/openmobilityfoundation/mobility-data-specification/pull/793
• @egor-bayandin made their first contribution in https://github.com/openmobilityfoundation/mobility-data-specification/pull/800
• @mguida22 made their first contribution in https://github.com/openmobilityfoundation/mobility-data-specification/pull/803
• @teebot made their first contribution in https://github.com/openmobilityfoundation/mobility-data-specification/pull/795
• @wellorder made their first contribution in https://github.com/openmobilityfoundation/mobility-data-specification/pull/807
• @jyeo17 made their first contribution in https://github.com/openmobilityfoundation/mobility-data-specification/pull/786
• @jean-populus made their first contribution in https://github.com/openmobilityfoundation/mobility-data-specification/pull/814
• @nheilbuth made their first contribution in https://github.com/openmobilityfoundation/mobility-data-specification/pull/740

Full Changelog: https://github.com/openmobilityfoundation/mobility-data-specification/compare/1.2.0...2.0.0-rc1

Published by schnuerle about 3 years ago

mobility-data-specification - 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.

Published by schnuerle over 4 years ago

mobility-data-specification - 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.

  • 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
• 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.

Published by schnuerle over 4 years ago

mobility-data-specification - 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

• "removed" missing "comms_restored" option in provider schemas
• Version number is 1.0.x for 1.1.0 release

Published by schnuerle over 4 years ago

mobility-data-specification - 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

• Policy and Geography can be public
• Geography-Driven Events: Issue

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

• New Reports: Issue

Agency

• N/A

Policy

• Images of Stops
• Clarify update frequency: Issue

Geography

• Elevating Geography to a first class API: PR, Issue
• Geography Types: Issue, Discussion

Metrics

• New Agency Metrics API: Definitions PR, Spec PR, Issue

Jurisdiction

• New Jurisdiction API: Issue

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.

Published by schnuerle almost 5 years ago

mobility-data-specification - 1.1.0 Release Candidate 1

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.

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 and Issues tagged with "Milestone 1.1.0" for a full list of changes.

MDS

• Policy and Geography can be public
• Geography-Driven Events - Issue

Minor Updates

• Unregistered error
• Stops updates
• Response time expectations
• Geography publish date field consistency
• Adding more cities using MDS
• Adding more providers using MDS
• New API icons

Provider

• New Reports - Issue

Agency

• N/A

Policy

• Images of Stops
• Clarify update frequency - Issue

Geography

• Elevating Geography to a first class API - PR, Issue
• Geography Types - Issue, Discussion

Metrics

• New Agency Metrics API - Definitions PR, Spec PR, Issue, k-value discussion

Jurisdiction

• New Jurisdiction API - Issue

Published by schnuerle about 5 years ago

mobility-data-specification - 1.0.0

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.

LICENSE and DISCLAIMER

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

RELEASE PLAN

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.

UPGRADING

See our Upgrading to 1.0.0 guide for some on upgrading.

CHANGES

See the closed PRs tagged with Milestone 1.0.0 for a full list of changes.

MDS

• Reconcile the Provider and Agency language differences
  • New State Machine Diagram
  • JSON Schema updates
  • Add 'located' event_type
  • Update Unknown/Unspecified transitions
  • Add 'unspecified' events where needed

• Adding Stops - Beta

• Minor Updates

  • Update cities using MDS
  • Update Austin, Louisville links
  • Add link to State of Practice
  • Update GBFS references and links
  • Move Code of Conduct, Contributing Guide, and Release Guidelines to new Governance repo
  • Updating 'master' to 'main' as default branch name
  • Add Superpedestrian to providers.csv
  • Add Circ to providers.csv
  • Removed Options version negotiation
  • Added 'other' vehicle type

Provider

• Events out of beta

Agency

• Vehicle register: add provider_id field
• Clarify vehicle endpoint requirements
• Vehicle response code should be 200
• Clarify telemetry success response

Policy

• Add Rates (fees + subsidies)
• Rearrange Speed Limit Example
• Added Geography schema
• Add Policy JSON Schema

Published by schnuerle over 5 years ago

mobility-data-specification - 1.0.0 Release Candidate 1

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.

LICENSE and DISCLAIMER

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

CHANGES

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

• Reconcile the Provider and Agency language differences
  • New State Machine Diagram
  • JSON Schema updates

• Adding Stops - Beta

• Minor Updates

  • Update cities using MDS
  • Update Austin, Louisville links
  • Add link to State of Practice
  • Update GBFS references and links
  • Move Code of Conduct, Contributing Guide, and Release Guidelines to new Governace repo
  • Updating 'master' to 'main' as default branch name
  • Update providers.csv to add Superpedestrian
  • Removed Options version negotiation
  • Added 'other' vechicle type

Provider

• Events out of beta

Agency

• Vehicle register: add provider_id field
• Clarify vehicle endpoint requirements
• Vehicle response code should be 200
• Clarify telemetry success response

Policy

• Add Rates (fees + subsidies)
• Rearrange Speed Limit Example
• Added Geography schema

Published by schnuerle over 5 years ago

mobility-data-specification - 0.4.1

0.4.1 is the first release of the Mobility Data Specification under the guidance and stewardship of the Open Mobility Foundation.

As such, this release includes a number of administrative and documentation changes, including to the licensing and release process.

This release also brings a number of language clarifications from 0.4.0 and new features across the various APIs, including the much anticipated /vehicles endpoint in Provider.

LICENSE and DISCLAIMER

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

CHANGES

MDS

• MDS officially transferred from LADOT to OMF:
  • Update license from CC0 to CC-BY
  • Updates to various documentation to support code transfer from LADOT to OMF
  • Switch CODEOWNERS to use OMF teams
  • Add documentation around currently Supported MDS versions
  • Add documentation around Understanding MDS APIs
  • ReleaseGuidelines updates to reflect OMF process and 12 week dev cycle and refinement
• Added "moped" vehicle type

Provider

• Mention ambiguity for event_type reserved
• Clarify no pagination on /trips and /status_changes
• Make required/optional endpoints more explicit
• Adding a /vehicles endpoint
• JSON Schema fixes/updates

Agency

• Add decommissioned event type reason
• Add versioning

Policy

• Update documentation to use correct field name
• Add missing rule_id
• Add versioning

Patch 1

• A minor patch was made on May 18 to include 2 of the above approved items missed during deployment. Please grab the latest version of the code using master or dev.

Published by thekaveman almost 6 years ago

mobility-data-specification - 0.4.1 Release Candidate 1

0.4.1 is the first release of the Mobility Data Specification under the guidance and stewardship of the Open Mobility Foundation. As such, this release includes a number of administrative and documentation changes, including to the licensing and release process. This release also brings a number of language clarifications from 0.4.0 and new features across the various APIs, including the much anticipated /vehicles endpoint in Provider.

CHANGES

MDS

• MDS officially transferred from LADOT to OMF:
  • Update license from CC0 to CC-BY
  • Updates to various documentation to support code transfer from LADOT to OMF
  • Switch CODEOWNERS to use OMF teams
  • Add documentation around currently Supported MDS versions
  • Add documentation around Understanding MDS APIs
  • ReleaseGuidelines updates to reflect OMF process and 12 week dev cycle
• Added "moped" vehicle type

Provider

• Mention ambiguity for event_type reserved
• Clarify no pagination on /trips and /status_changes
• Make required/optional endpoints more explicit
• Adding a /vehicles endpoint
• JSON Schema fixes/updates

Agency

• Add decommissioned event type reason
• Add versioning

Policy

• Update documentation to use correct field name
• Add missing rule_id
• Add versioning

Published by thekaveman almost 6 years ago

mobility-data-specification - 0.4.0

0.4.0

Release 2019-10-31

The 0.4.0 release represents a major step forward in the Mobility Data Specification. The provider endpoints have been refactored to allow static file backed API servers which should improve uptime, reliability and the ability to backfill what is now growing to years of data. There is a new policy API endpoint, designed to be implemented by Agencies, that allows for clearer communication of geofencing, vehicle caps and more. A full list of changes is below. Many thanks to all the contributors who helped on this release.

CHANGES Provider * Improved Handling of Cost Data * Allow static file storage backed API Endpoints * Cleanup Provider README * Legacy Version Header Cleanup * Internationalization of Currency data * Specify Types for Query Params * Clarify the definition of Municipal Boundary * Update Status Change JSON Schema to include Associated Trip properly

Agency * Add Accuracy Field for GPS Telemetry Data * String Limit to 255 Characters * Remove SLA from /telemetry * Update State Machine Diagram

Misc * New Policy API Endpoint * Improved README for Schema Directory * Add Car Vehicle Type * Unify Error Responses between Provider / Agency * Imrovements to Release Process

Published by hunterowens over 6 years ago

mobility-data-specification - 0.3.2

0.3.2

Released 2019-06-13

This release is a series of non breaking and minor changes for provider, along with JSON Schema for agency.

CHANGES

Provider * Add an optional recorded field to provider * Ordering Definitions * 406 response - version negiotation

Agency * JSON Schema for Agency

Misc * Schema Folder Cleanup * Global GNSS Support

Published by hunterowens over 6 years ago

mobility-data-specification - 0.3.1

0.3.1

Released 2019-04-30

This release represents a series of non-breaking changes and clarifications for provider, along with a number of agency bugfixes / changes.

CHANGES

Provider * MDS Schema version fix. * New release process. Thanks @jfh for documenting, all for participating * Additional documentation around what is considered Breaking / Non-Breaking. Thanks @rf- * OPTIONS for version negotiation. Thanks @billdirks * Add Agency Drop off / pick up. Thanks @margodawes * Explicitly allow associated_trip for any event type

Agency * Change from UUIDv4 to just UUID. Thanks @karcass * Change Error Messages for State Machine validation. * Update Pagination Rules * Add Unregistered event. * Add Event Diagram. Thanks @whereissean * Removing 412 Responses * Add deregister and decomissioned events. Thanks @dirkdk * Remove 5 second Telemetry requirement * Improve failure and error handling around Telemetry Data

Published by hunterowens almost 7 years ago

mobility-data-specification - 0.3.0

0.3.0

Released 2019-02-15

This release is the first minor version release of MDS with breaking changes for deployed provider API instances.

CHANGES

• Improved Time Based Filtering Query Parameters. #139. Thanks @babldev
• Changes in Service Area for Agency API.
• Switch timestamps to Integer milliseconds since Epoch rather then seconds. #179
• Removed unused bbox query parameter. #183
• Add GBFS discovery URL to /providers.csv. #205. Thanks @asadowns
• Associated Trips -> Associated Trip, no longer an array. #88, #202, #217. Thanks @black-tea, @oderby
• Version Requirements and documentation. #152, #216, and #114
• Agency API refactors to support launch of ladot.io sandbox. #193, #194. Thanks @toddapetersen, @sebdiem, @cttengsfmta.
• Clarification on Service Starts, Service Ends and Municipal Boundaries. #211, #226
• Documentation on how to implement truncate to save on payload size.

Published by hunterowens about 7 years ago

mobility-data-specification - 0.2.1

Released 2018-12-03

This release is the first patch release of MDS 0.2.

We did not chose to include the timestamp change, as discussed in issue #104, because it is breaking. Early versions of this branch included that change. The change will be made in MDS 0.3.0.

CHANGES

• Release Guidelines. Ref #147 #129
• Many Validator Fixes/Null Fixes. Ref #166 #165 #128
• Many Clarifications / Cleanup to make the spec easier to read.
• JSON Schema is now much closer to the written spec, fails on Null if required, doesn't fail if field is not required.

Thanks to all contributors.

Published by hunterowens about 7 years ago

mobility-data-specification - 0.2.1-dev

This release is the first patch release of MDS 0.2.

We did not chose to include the timestamp change, as discussed in issue #104, because it is breaking. Early versions of this branch included that change. The change will be made in MDS 0.3.0.

CHANGES

• Release Guidelines. Ref #147 #129
• Many Validator Fixes/Null Fixes. Ref #166 #165 #128
• Many Clarifications / Cleanup to make the spec easier to read.

Thanks to all contributors.

Published by hunterowens about 7 years ago

mobility-data-specification - 0.1.1

This release backports two features from 0.2.0:

• Clarifying Location Types as GeoJSON #94

• Adding electric-assist as a propulsion type #48

This makes MDS 0.1.x series more usable for Mobility Providers.

Published by hunterowens over 7 years ago

mobility-data-specification - 0.2.0

This release includes a number of enhancements and clarifications to the provider spec:

• Introduce JSON Schema for Trips and Status Changes #53

• Clarify query params for API endpoints #64

• Clarify API authentication method #81

• Clarify location formatting #94

• Clarify timestamp formatting #93

• Clarify the associated_trips field in Status Changes #96

Published by thekaveman over 7 years ago

mobility-data-specification - 0.2.0-dev

Preparing for 0.2.0

Published by thekaveman over 7 years ago