Data Standards

MobilityData facilitates changes to two internationally used mobility data standards: the General Transit Feed Specification (GTFS) and the General Bike Feed Specification (GBFS).

What is GTFS?

The General Transit Feed Specification (GTFS) is used by over 10,000 transit operators so they can share their data with trip planning applications. Anyone in the world can propose changes to the specification and vote on adopting new features.

hand holding a phone that displays trip planner

What it looks like to passengers

Part of what it looks like in GTFS

computer displays homepage of gtfs.org with purple background

Do you want to learn more about how to use the specification? Go to gtfs.org for an in-depth breakdown of the specification and data examples.

Go to GTFS.org

How changes to GTFS are made

Changes to GTFS are made on consensus by anyone who wants to participate. MobilityData facilitates each stage of the change process to make sure the highest priority needs of the industry are addressed.

magnifying glass illustration with circle around it

Step 1: Idea

Someone shares an idea for a new feature as an issue on the GitHub repository. This can be anyone across the world.

document illustration inside a blue circle

Step 2: Feature Proposal

A proposal is shared on how to implement this feature in the specification.

two dialog boxes intersecting

Step 3: Feedback

Anyone can read the proposal and provide feedback. MobilityData facilitates workshops to resolve issues.

phone illustration with a map

Step 4: First adopters

One data producer and one data consumer commit to implementing the new feature as first adopters.

Step 5: Dataset published

The first adopters share their dataset with the new feature to get feedback and insight from the public.

three intersecting circles

Step 6: Public Vote

The proposed change goes to a vote. Anyone can vote and the vote is made based on consensus.

hand holding a phone with a map on it

Step 7: Adoption

The new feature is added to the official specification. Transit operators and trip planning applications across the world can now use it.

Do you want to know what features the GTFS community is actively discussing and developing? Take a look below to see the specification roadmap.

See what is coming next to GTFS

What is GBFS?

The General Bike Feed Specification (GBFS) is used in over 40 countries so shared mobility operators can share their data with trip planning applications. Anyone in the world can propose changes to the specification and vote on adopting new features.

hand holding a phone that displays bike trip planning

What it looks like to passengers

example of a gbfs.json file

Part of what it looks like in GBFS

display of GBFS.mobilitydata.org home page

Do you want to learn more about how to use the specification? Go to gbfs.mobilitydata.org for an in-depth breakdown of the specification and data examples.

Go to GBFS.mobilitydata.org

How changes to GBFS are made

Changes to GBFS are made on consensus by anyone who wants to participate. MobilityData facilitates each stage of the change process to make sure the highest priority needs of the industry are addressed.

magnifying glass illustration with circle around it

Step 1: Idea

Someone shares an idea for a new feature as an issue on the GitHub repository. This can be anyone across the world.

document illustration inside a blue circle

Step 2: Feature Proposal

A proposal is shared on how to implement this feature in the specification.

two dialog boxes intersecting

Step 3: Feedback

Anyone can read the proposal and provide feedback. MobilityData facilitates workshops to resolve issues.

three intersecting circles

Step 4: Vote

The proposed change goes to a vote. Anyone can vote and the vote is made based on consensus.

Step 5: Release candidate version status

The change is placed into Release Candidate (RC) status. The change remains in RC status pending implementation. During this time, the change is added to the GBFS validator.

phone illustration with a map

Step 6: Adoption

The change is adopted by different data producers and consumers and implemented in their datasets.

hand holding a phone with a map on it

Step 7: Official version status

Once the feature is adopted by a data producer and a data consumer, it is merged into an official current release.

the back of someone standing looking at a wall of papers

Do you want to know what features the GBFS community is actively discussing and developing? Take a look below to see the specification roadmap.

See what is coming next to GBFS