-
Notifications
You must be signed in to change notification settings - Fork 0
Home
MDS Compliance Monitoring on DataGovs Mobile
The Mobility Data Specification (MDS), a project of the Open Mobility Foundation (OMF), is a set of Application Programming Interfaces (APIs) focused on dockless e-scooters, bicycles and carshare. Inspired by projects like GTFS and GBFS, the goals of MDS are to provide a standardized way for municipalities or other regulatory agencies to ingest, compare and analyze data from mobility service providers, and to give municipalities the ability to express regulation in machine-readable formats.
MDS helps cities interact with companies who operate dockless scooters, bicycles and carshare in the public right-of-way. MDS is a key piece of digital infrastructure that supports the effective implementation of mobility policies in cities around the world.
MDS is an open-source project. It was originally created by the Los Angeles Department of Transportation (LADOT). In November 2019, stewardship of MDS and the ownership of this repository were transferred to the Open Mobility Foundation. GitHub automatically redirects any links to this repository in the CityOfLosAngeles organization to the openmobilityfoundation instead. MDS continues to be used by LADOT and many other municipalities.
This app helps your agency verify that the data provided to MDS by mobility service providers actually match what's happening on the street.
Currently, this takes two forms:
- Monitoring Vehicle Compliance as Reported by Providers
Verifying that vehicles registered with MDS are actually present on the street. Reporting vehicles that are present on the street but not in MDS. Noting broken, mis-parked, etc. vehicles. 2) Auditing Vehicle Trips
This involves taking a trip on a provider vehicle (scooter or bike) and simultaneously using the Compliance Mobile app to create a matching "audit trip". You can then compare the audit trip with the provider trip data submitted to MDS to:
Ensure that the provider is reporting trip_start, trip_end, etc events accurately and in a timely manner. Verify that telemetry for the trip is being reported accurately and that it roughly matches telemetry recorded during the audit.