HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
MobilityData
gbfs
JavaScript2018–2024
MobilityData / gbfs

gbfs

Documentation for the General Bikeshare Feed Specification, a standardized data feed for shared mobility system availability. Maintained by MobilityData

Learning & ReferenceCommunication & Social
Explore on GitHubRead Hacker News discussions
6Distinct people
7Mentions
0Explicit recommenders
927GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Documentation for the General Bikeshare Feed Specification, a standardized data feed for shared mobility system availability. Maintained by MobilityData

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 2:04:58 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year7 dated mentions

Observed mentions: 2018-09-10 16:29:27 UTC to 2024-08-12 12:37:59 UTC.

0122018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments20182019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments20212022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2024

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC202
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC110
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC211
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC000
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC000
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC000
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC202

What Hacker News says

7 sources
wiredfool·Aug 12, 2024
PMTiles is great, but there's a risk hosting multi-gb files on metered hosting -- a client might not respect range requests and you open yourself up to a denial of wallet attack. I can't really see doing it on S3, unless it's behind a lightweight tile server. I'd do it on hetzner or linode or one of the lower cost bandwidth providers. (edit -- citybik.es is pretty cool, are you backing up to GBFS or a different set of data feeds? e.g. https://github.com/MobilityData/gbfs/blob/master/systems.csv is a list of ~ 800 gbfs feeds, some dockless, some docked I've done a bit of work in this space, feel free to ping me)
In Show HN: Simple Mbtiles Server – Self-host the entire planet of OpenStreetMaps
cfeeley·Jul 5, 2024
I wrote a tool in Haskell that continually polls my city's (Toronto) bike share API and dumps it into a database, along with a web server component that does a bunch of on-the-fly analysis of the data and serves that up as various visualizations and stats. I got so frustrated with my city's bike share program one night and I wanted to figure out whether the problems I had been having were widespread or not. Surprisingly enough there's a standard for bike share APIs [0] that my city adheres to. I'd been looking for an excuse to learn Haskell and figured the best way to stay motivated was to make useful tool for myself. I've been working on it for the better part of a year at this point (probably >200 hours) and I use it roughly daily. After gathering a few months of station-level data it became clear enough that the system (specifically, h
Read the rest
ow the e-bikes are handled) has some pretty serious issues. I ended up sending the city a couple of freedom of information requests for some data I was missing and for the contract between them and the company that operates the system. The contract says that the operator gets paid a fee for every dead e-bike they move to a charging station - regardless of whether or not that bike actually manages to charge. The city owns around 2000 e-bikes and there are frequently times where a whopping 20 are available - the rest are out of battery, sitting in docking stations for multiple days. Occasionally the operator shuffle the bikes over to the handful electrified charging stations, and about half the time the bikes don't charge (they just completely fill the stations, meaning nobody can use them - one of those stations happens to be right outside my partner's place). Then 4-7 days later they come around in a truck and get rid of the bikes, and the whole cycle repeats again in a couple days. Basically, we're getting fleeced by the system operator. It isn't even clear to me if it's intentional or not, or just the usual combination of lax municipal oversight and an apathetic operator. I've been meaning to send my data and the contract over to a few reporters who care about that sort of thing, since (a) the bike share system is genuinely a great way to get around (when it works) and (b) financially it's really good value for the city [1], and I'd like to see the problems fixed (especially given that the city is planning on massively expanding the e-bike fleet). [0]: General Bikeshare Feed Specification: https://github.com/MobilityData/gbfs [1]: The per-trip subsidy is $0.67, versus $4.08 for a trip on our transit system (!)
In Ask HN: Is there any software you only made for your own use but nobody else?
BrianHenryIE·Apr 5, 2020
You reminded me to work on my Jump Bikes Siri Shortcut which uses General Bike Share Feed specification. https://github.com/BrianHenryIE/Bikeshare-Siri-Shortcuts I made it so I could ask "where's the nearest Jump bike?" in Sacramento. At some point the API stopped working, but, after checking today, it was just the URLs of the updated feeds had changed (the old ones still 200 with no actual data) so I think I've managed to fix it. Unfortunately, Jump shut down in Sacramento because of Corona virus! Overall, it only works OK. When Apple Shortcuts requests GPS location, it doesn't just return the GPS, it makes a HTTP call to get the street info, which isn't needed here and slows things down. Then the gbfs.uber.com API is very slow... as though they don't cache at all, whereas I thought they only refreshed once/minute: https://gbfs.uber.com/
Read the rest
v1/sacb/station_information.json https://github.com/NABSA/gbfs/pull/190 https://www.sacbee.com/news/business/article241326756.html
In General Transit Feed Specification and Clojure

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.