Specification¶
Versions of this documentation¶
- Pre-release - Version 3.1-RC
- Latest - Version 3.0
- v2.3 - Version 2.3
- v2.2 - Version 2.2
- v2.1 - Version 2.1
- v2.0 - Version 2.0
- v1.1 - Version 1.1
As described in the GBFS governance, when changes are made to the specification, the changes are placed into Release Candidate (RC) status. The changes remain in RC status pending implementation.
- Implementation requirements are that at least 1 producer and 1 consumer implement the changes.
- The implementors MUST be stakeholders other than The Advocate (who opened the PR).
- Once implemented successfully, the change is merged into an official current release.
To support this process and ensure it is as timely as possible, MobilityData tracks implementation through one-on-one discussions and other stakeholder events and by examining GBFS datasets. To improve this tracking process, GBFS data producers and consumers are encouraged to add their organization here if they have implemented or are planning on implementing any of these release candidate changes. After votes are called, MobilityData will update this list to reflect organizations that included an implementation note in their vote.
First Adopters¶
🎉 Shoutout to the first adopters! These organizations invest a large amount of time and energy to implement the changes contained in the Release Candidate and make sure that GBFS continues to evolve.
- Producers: Check, ENTUR, Flamingo, TIER.
- Consumers: Dashboard Deelmobiliteit, ENTUR, Transit, transport.data.gouv.fr, Where To?.
Implementation Status¶
The following items have passed through the voting process and will be included in the next version.
Request a change Add your organization (producers) Add your organization (consumers)
Extensions Outside of the Specification¶
To accommodate the needs of feed producers and consumers prior to the adoption of a change, additional fields can be added to feeds even if these fields are not part of the official specification. Custom extensions that may provide value to the GBFS community and align with the GBFS Guiding Principles should be proposed for inclusion in the specification through the change process.
Field names of extensions should be prefixed with an underscore (_) character. It is strongly recommended that these additional fields be documented here in this format:
Change Proposals¶
GBFS is an open source project developed under a consensus-based governance model. Contributors come from across the shared mobility industry, public sector, civic technology and elsewhere. An overview of current work can be found on the Project Roadmap. Comments or questions can be addressed to the community by opening an issue on the GBFS GitHub repo. Proposals for changes or additions to the specification can be made through pull requests.
Governance Process¶
GBFS is an open source project developed under a consensus-based governance model. Contributors come from across the shared mobility industry, public sector, civic technology and elsewhere. Anyone can propose a change to the specification by opening a pull request on the GBFS GitHub repository.