An open data standard for real-time shared mobility system availability, providing uniform public data feeds.
GBFS (General Bikeshare Feed Specification) is an open data standard that defines a uniform format for real-time data feeds from shared mobility systems, such as bikeshare and scooter networks. It solves the problem of fragmented and inconsistent data availability by providing a standardized way for mobility operators to publish system status—like vehicle and dock availability—publicly online. This enables developers to build applications that offer real-time transit advice and improve user access to shared mobility services.
Shared mobility system operators, public transit agencies, application developers building mobility or transit apps, and civic technology practitioners who need to consume or provide standardized real-time mobility data.
Developers choose GBFS because it is the industry-standard, community-driven specification that ensures interoperability across hundreds of global shared mobility systems. Its focus on real-time, public data with clear versioning and backward compatibility reduces integration complexity and fosters a robust ecosystem of tools and applications.
Documentation for the General Bikeshare Feed Specification, a standardized data feed for shared mobility system availability. Maintained by MobilityData
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Defines standardized JSON schemas that ensure consistency across hundreds of global shared mobility systems, enabling seamless integration for developers building transit apps.
Includes a mandatory auto-discovery file (gbfs.json) that makes data feeds publicly accessible and easily locatable, reducing setup complexity for consumers.
Follows semantic versioning with clear release cycles and backward compatibility for minor updates, providing long-term stability for both producers and consumers.
Managed through an open, consensus-based model involving GBFS producers and consumers, ensuring the spec evolves with real-world needs, as detailed in the governance.md.
Explicitly designed to exclude archival information, limiting use cases for performance analysis or trend reporting beyond real-time status.
Changes require minimum 7-day discussions and 10-day votes with specific voter requirements (e.g., producer and consumer votes), which can delay feature adoption.
JSON schemas are hosted in a different GitHub repository (gbfs-json-schema), adding an extra step for validation and implementation compared to an all-in-one package.