A data standard and API specification for mobility as a service providers, such as Dockless Bikeshare, E-Scooters, and Shared Ride providers who work within the public right of way.
Inspired by GTFS and GBFS. Specifically, the goals of the Mobility Data Specification (MDS) are to provide API and data standards for municipalities to help ingest, compare and analyze mobility as a service provider data.
The specification is a way to implement realtime data sharing, measurement and regulation for municipalities and mobility as a service providers. It is meant to ensure that governments have the ability to enforce, evaluate and manage providers.
MDS is currently comprised of two distinct components:
-
The
providerAPI is to be implemented by mobility as a service providers, for data exchange and operational information that a municipality will query.providerpresents the historical view of operations. -
The
agencyAPI is to be implemented by municipalities and other regulatory agencies, for providers to query and integrate with during operations.agencyprovides tools to inform and permit future operations.
Cities and regulators can choose best how to implement Agency and Provider either separately, concurrently, or by endpoint.
The specification will be versioned using Git tags and semantic versioning. See prior releases and the Release Guidelines for more information.
The City of Los Angeles is currently looking for feedback and comments on the draft versions. Comments can be made by making an Github Issue, while suggested changes can be made using a pull request. The rules and guidelines for the Los Angeles Dockless Bikeshare Systems / Pilot Program can be found on Council Clerk Connect.
2/12/2019 Update: City of Los Angeles One Year Permit Application MDS Agency Compliance: LADOT is seeking compliance with MDS Agency as a requirement of the one-year permit, and hosted a webinar on Thursday, February 7th to give an overview of the MDS Agency sandbox, discuss and answer questions about integration and timeline for Agency services. The slides from the webinar presentation can be found here
12/27/2018 Update: Applications for the One-Year Dockless On-Demand Personal Mobility Permit are now available on the LADOT Website
10/28/2018 Update: LADOT Guidelines for Handling of Data from Mobility Service Providers
10/1/2018 Update: Applications for the Conditional Permit are now open for submission on the LADOT Website
9/12/2018 Update: LADOT presentation on MDS (Video / Presentation Materials)
mds-dev- Code to do cap checking, fake data generation and more with provider data.mds-validator- Code to validate MDS APIs using JSONSchema.aqueduct- ETL, Data Warehousing, and Machine Learning Platform for LA City Data Science team. Handles extracting MDS provider APIs and storing in data warehouse.mds-agency-cli- Nodejs-based command-line interface to exercise the Agency API in the LADOT sandbox
mds-provider- Python package implementing the provider API, validation using JSONSchema, data loading to multiple targets, and fake provider data generation.mds-provider-services- Python scripts wrapped in Docker containers implementing a MDS provider data ingestion flow, usingmds-providerand handling the various dependencies.
transportation-dockless-dataviz- A hexbin origin/destintation web map of dockless trips using jQuery & Mapbox GL JS. See http://dockless.austintexas.io/.transportation-dockless-api- Python Sanic-based API that provides an interface for retrieving anonymized and aggregated trip data. This API supplies data to our interactive Dockless Mobility Explorer. The source database for the API is our Dockless Vehicle Trips dataset.transportation-dockless-processing- Python scripts for dockless mobility data ETL.mds-provider-client- A forked Python client fromCityofSantaMonica/mds-provider.
Please open a pull request if you create open source or private MDS tooling.
Questions can be directed to [email protected].
To stay up to date on MDS releases, please subscribe to the MDS-Announce mailing list.