Mobility Data Specification

The Mobility Data Specification (MDS) is a set of data specifications and data sharing requirements focused on dockless e-scooters and bicycles. Inspired by GTFS and GBFS the goals of the MDS are to provide API and data standards for municipalities to help ingest, compare and analyze mobility as a service provider data.

The MDS helps the City ingest and analyze information from for-profit companies who operate dockless scooters and bicycles in the public right-of-way. MDS is a key piece of digital infrastructure that helps cities and regulators such as Los Angeles Department of Transportation (LADOT) understand how dockless mobility operate.

Mobility providers are required to share data with LADOT as part of the City of Los Angeles' Dockless Mobility Permit. Standardizing data collection between different providers improves cooperation, innovation, and efficiency of the City's transportation network.

MDS is currently comprised of two distinct components:

• The provider Application Program Interface (API) was first released May 2018 to be implemented by mobility providers. When a municipality queries information from a mobility provider, the Provider API has a historical view of operations in a standard format.

• The agency API was first released in April 2019 to be implemented by regulatory agencies. The first implementation went live in Febuary 2019. Providers query the Agency API when an event occurs, like a trip starting or ending.

Cities and regulators can choose best how to implement Agency and Provider either separately, concurrently, or by endpoint.

Versions

The specification will be versioned using Git tags and semantic versioning. See prior releases and the Release Guidelines for more information.

Information about the latest release and all releases are below. Please note, you may be viewing a development copy of the Mobility Data Specification based on the current branch. Info about the latest release and all releases is below.

• Latest Release

• All Releases

Cities Using MDS

The Mobility Data Specification is an Open Source project. Comments can be made by making an Github Issue, while suggested changes can be made using a pull request. Many cities and operators have implemented MDS, more details about their specific programs can be found below.

• Los Angeles: The rules and guidelines for the Los Angeles Dockless Bikeshare Systems / Pilot Program can be found on Council Clerk Connect along with support info on ladot.io.

Add your City here by opening a pull request

Use Cases

MDS enables cities to

• To verify how many scooters are operating.
• To verify whether scooters are being deployed equitably across neighborhoods.
• To determine whether scooters are dropped off outside of a service area.
• To determine whether scooters are being parked in safe and appropriate parking areas.
• To ensure compliance with Device Caps, Operating Regulations.
• To ensure inform and help manage 311 / Service Request style operations.
• To inform future capital investments such as dockless vehicle drop zones or furniture zones.
• To inform policy making – number of scooters, distribution, etc.
• Develop ways to communicate dynamic information on unplanned events, such as emergency road closures, water main breaks, etc. to mobility providers to help them keep their users and contractors informed for better route planning and re-balancing efforts.
• Much More!

Related Projects

City of Los Angeles

• 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

City of Santa Monica

• mds-provider - Python package implementing a provider API client, 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, using mds-provider and handling the various dependencies.

City of Austin

• 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 from CityofSantaMonica/mds-provider.

Others

• midas - Python/Django open source server for the agency API, developed by BlueSystems.

Please open a pull request if you create open source or private tools for implementing or working with MDS data.

Learn More / Get Involved

To stay up to date on MDS releases and planning calls, please subscribe to the MDS-Announce mailing list. You can view info about past releases and planning calls in the wiki.

To learn more about MDS and other related projects, including LADOT's Technology Action Plan, visit ladot.io.

For questions about MDS please contact [email protected].