GBFS
The General Bikeshare Feed Specification: dock and vehicle availability in a format anyone can read. It is why a bike-share system appears in apps its operator never built.
How this list is decided. Membership is not a field an editor set: it is every published entry whose own text names GBFS, matched at build time, with the sentence printed under each row so you can judge the match yourself. 14 entries in 14 cities.
✔ Every published entry is checked against the public sources it cites before publication.
Where it appears in the atlas
Because the city bought nothing, it holds nothing: the only live data is a GBFS feed on the operator's own platform, and that feed declares no licence, no terms of use and no attribution.
Beyond the catalogue the portal serves live feeds under the same terms — bike-share station status in the GBFS standard, road-traffic counts, roadworks and real-time parking occupancy.
What is actually published, and it is thinner than the peers: trip files quarterly rather than monthly, with trip duration, start and stop time, start and end station name and ID, bike ID and user type, staff service trips and rides under 60 seconds removed, plus station files and a live GBFS feed.
The city publishes every trip record from 2010 onward on its open-data portal under CC BY 2.5 Argentina, while the operator's live GBFS feed carries no licence, no terms and no operator field at all.
No public trip data or GBFS feed was found.
What is actually published: monthly trip files with start and end time, start and end station and rider type (member, single ride, day pass), with staff trips and trips under 60 seconds removed, plus a live GBFS station feed.
Houston Bike Share, a nonprofit launched with city backing, started Houston BCycle in May 2012 with 18 bikes at three docking stations and grew it to more than 150 stations and roughly 900 bikes/2,200 docks by FY2022, reporting over 300,000 rides in its peak year — every station published live bike-and-dock counts t…
Example of a live feed published onward to the national mobility data platform in GBFS format, updated every minute — evidence that the real-time layer is consumed outside the Métropole's own portal.
Real-time GBFS station feed on the city portal, publishing organisation listed as BIXI Montréal, carrying the identical IP notice: 'la paternité des données doit être attribuée à BIXI Montréal'.
Alongside the real-time services Nantes Métropole publishes GTFS, NeTEx stops and NeTEx offer files, plus GBFS feeds for four separate shared-mobility operators.
Citi Bike publishes monthly trip-level data and a live GBFS feed, but under a bespoke licence that forbids redistributing the dataset.
The operator owns the bikes and carries the revenue risk, and it holds the data — the public GBFS feed names no operator, no licence and no terms, and still ships the placeholder system name "kitchen".
Show 2 more entriesShow fewer
A public GBFS feed gives live station availability, but it declares no licence and there is no archive of trip records.
Registry row: "BR,Bike Itaú — Sampa,São Paulo,bike_sampa,...,1.1 ; 2.3 ; 3.0" — confirms the São Paulo feed is a registered public GBFS endpoint, distinct from Tembici's other city systems.
Others in this group
The whole layer
Every standard, protocol and licence the atlas names, with the open-data licence ladder in one table: Standards & licences.