Changes for MDS 0.4.x

[thekaveman]

Tracking issue for 0.4.x related updates

• deprecate support of 0.2.x line DONE: Removing support for MDS 0.2.x #90
• provider schema sub-types have moved (e.g /dockless/trips.json) Support for multiple modes (255 redux) openmobilityfoundation/mobility-data-specification#336 DONE: Update JSON schema URLs #86
• add vehicle_type: car Add "car" vehicle type openmobilityfoundation/mobility-data-specification#219 N/A
• add status_changes.associated_ticket field add associated_ticket. Fixes #269 openmobilityfoundation/mobility-data-specification#380 DONE: New status_changes and trips fields #92
• add trips.currency field Add a section clarifying currency units; specify behavior when no currency is given openmobilityfoundation/mobility-data-specification#388 DONE: New status_changes and trips fields #92
• fix time query param formatting and deprecate non-time params for /status_changes and /trips Allow static file data storage for Provider /status_changes and /trips openmobilityfoundation/mobility-data-specification#357 DONE: Query param adjustments #91
• remove paging support for /status_changes and /trips Clarify no pagination on static provider endpoints /trips and /status_changes openmobilityfoundation/mobility-data-specification#424 DONE: Query param adjustments #91
• add support for /events endpoint Allow static file data storage for Provider /status_changes and /trips openmobilityfoundation/mobility-data-specification#357 DONE: Support for the /events endpoint #93
  • JSON schema validation
  • API queries
  • DB loading
• add support for /vehicles endpoint Adding a /vehicles endpoint to show the current status of the fleet openmobilityfoundation/mobility-data-specification#376 DONE: Support for the /vehicles endpoint #95
  • JSON schema validation
  • API queries
  • DB loading

[schnuerle]

Can this be updated and closed based on 0.4.0 release?

https://groups.google.com/forum/#!msg/mds-announce/JM3ZOJ7m8e8/n1svUmkeAQAJ

0.4.0
Released 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
• Improvements to Release Process

[thekaveman]

@schnuerle none of this has been implemented in mds-provider yet! I am happy to take PRs for any of the various changes needed to support MDS 0.4.x. I think the most pressing is probably the schema directory shuffle, but any help is appreciated.

[schnuerle]

Oh I got it now. This was your area to track provider changes to implement those updates in this repo. I'll take a look and see if I can help.

[thekaveman]

Opened WIP PR #87, please target the 04x branch for any changes related to MDS 0.4.x support so we can merge all at once.