HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
eskerda
pybikes
Python2013–2024
eskerda / pybikes

pybikes

bike sharing + python = pybikes

Explore on GitHubRead Hacker News discussions
3Distinct people
8Mentions
0Explicit recommenders
610GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

bike sharing + python = pybikes

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 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 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 year8 dated mentions

Observed mentions: 2013-05-28 13:36:37 UTC to 2024-08-12 13:18:29 UTC.

0122013-01-01 00:00:00 UTC to 2014-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments20132014-01-01 00:00:00 UTC to 2015-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments20182019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-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): 1 mentions; 0 submissions, 1 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 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
20132013-01-01 00:00:00 UTC2014-01-01 00:00:00 UTC202
20142014-01-01 00:00:00 UTC2015-01-01 00:00:00 UTC101
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC000
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC101
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC202
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC000
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC000
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC000
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 UTC101
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC101

What Hacker News says

8 sources
kh_hk·Jan 28, 2023
Thanks for replying and for providing feeds much on the same philosophy as citybikes. I guess the feed you mention is for Aachen [1]? Sometimes I take a very hands-off approach on the library contributions, so I do not know about specifics. At the moment our gbfs feeds come with a 'gbfs_href' field mentioning the source. Is there any way on which I can give more credit to the work you are doing? It would suck for our project to perpetuate the same kind of damage we receive from other projects, so this is important to me. Will send you an email, happy to chat. [1]: https://github.com/eskerda/pybikes/blob/86c8cca04b9e747fda1e...
In Ask HN: Those making $0/month or less on side projects – Show and tell
kh_hk·Apr 1, 2014
If interested, take a look at my project on unifying bike sharing networks data. Besides providing a public API, we are also providing a python library that accesses and abstracts different sources under the same model [1, 2] There are a lot of accessible sources (though, not documented), but there are also clear examples on how one would never provide a service! Some examples [3, 4] What I was referring, though, was in a way to avoid having to build an intermediate server scraping services that are perfectly usable (JSON, XML) just because we (all) prefer to build clients that understand one type of feed (standard). Maybe it's not about designing a language, but just as a new way of doing things. Let's say I provide the client with the clear instructions on how to use a service (its format, and where are the fields that the client under
Read the rest
stands (in an XPath-like syntax)). That should be enough to avoid periodically scraping good-player servers, but at the same time being able to build client apps without having to implement all the differences between feeds. Besides, it would avoid being banned for accessing too much times a service, and would give data providers insight on who is really using their data. Let's say we want to unify the data in Feed A and Feed B. The model is about foos and bars: Feed A: { "status": "ok", "foobars": [ { "name": "Foo", "bar": "Baz" }, ... ] } Feed B [{"n": "foo","info": {"b": "baz"}},...] We could provide: { "feeds": [ { "name": "Feed A", "url": "http://feed.a", "format": "json", "fields": { "name": "/foobars//name", "bar": "/foobars//bar" } }, { "name": "Feed B", "url": "http://feed.b", "format": "json", "fields": { "name": "//n", "bar": "//info/b" } ] } Instead of providing a service ourselves that accesses Feed A and Feed B every minute just because we want to ease things on the client. Not sure if that's what you asked, though. [1]: http://citybik.es [2]: http://github.com/eskerda/pybikes [3]: https://github.com/eskerda/PyBikes/blob/experimental/pybikes... [4]: https://github.com/eskerda/PyBikes/blob/experimental/pybikes...
In Portia, an open-source visual web scraper
kh_hk·May 28, 2013
In Germany, there's the 'next-bike', and 'call a bike'. I have been waiting to add them until I have the new structure of the project figured out. At that point, they will be much easier to have, and less hacky. The 'call a bike' system is interesting, and differs from the overall scheme of most bike sharing systems. You have to call a number, enter a pin, and then you get a code to unlock the chain. I find it pretty intelligent, but a bit conflicting with what I have currently running. At the same time, both systems are really small in stations, but big in locations (as in, there are lots of cities). That's the main reason I have to not support them at the moment, and the main reason of rewriting the architecture of the project. I did not know the project was going to grow at the start, so every city is a different module, if possible, w
Read the rest
ith some inheritance. The new architecture [1] will feature systems as instances, instead of a separated class, thus, making it trivial to generate instances on the run. Not sure if I went too far with the response, hope it's useful. [1]: https://github.com/eskerda/pybikes/wiki/architecture
In Bike Share Program Opens in New York City After Long Delay

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.