Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Nextbike provider #22

Closed
AdrienGiboire opened this issue Jul 19, 2014 · 5 comments
Closed

Nextbike provider #22

AdrienGiboire opened this issue Jul 19, 2014 · 5 comments

Comments

@AdrienGiboire
Copy link

I'm not sure it's the right place but I'm wondering if Citybik.es provides data from Nextbike (http://www.nextbike.net/)? I don't really know how to find out by myself…

@eskerda
Copy link
Owner

eskerda commented Jul 20, 2014

Yes, it is in pybikes/nextbike.py. Just Budapest is present right now (pybikes/data/nextbike.json). Assuming the current implementation works for other nextbike systems, it should be trivial to add them to the data file.

@AdrienGiboire
Copy link
Author

​(thumbsup)

I wonder why is there just Budapest though.​

@eskerda
Copy link
Owner

eskerda commented Jul 20, 2014

I am still thinking on a way to correctly integrate nextbike to the lib. By just issuing a call to the main feed https://nextbike.net/maps/nextbike-live.xml multiple networks can be loaded. It would seem a waste to issue multiple calls for no reason.

eskerda added a commit that referenced this issue Jan 14, 2015
Some networks provide one url for multiple networks at the same time. We do not
want to do unnecessary requests to providers that play nice, so a timestamp
based rate-limiting makes these kind of providers compatible with the pybikes
architecture.

This merge fixes Issue #22.
@eskerda
Copy link
Owner

eskerda commented Jan 14, 2015

Ok, now that we are not going to flood nextbike servers with unnecessary requests, we can actually add most nextbike networks.

eskerda added a commit that referenced this issue Jan 14, 2015
Some networks provide one url for multiple networks at the same time. We do not
want to do unnecessary requests to providers that play nice, so a timestamp
based rate-limiting makes these kind of providers compatible with the pybikes
architecture.

This merge fixes Issue #22.
@eskerda
Copy link
Owner

eskerda commented Sep 21, 2015

We currently support 108 nextbike networks. If anything relevant is missing, feel free to open a ticket or a PR about it.

@eskerda eskerda closed this as completed Sep 21, 2015
eskerda added a commit that referenced this issue Mar 30, 2016
Some networks provide one url for multiple networks at the same time. We do not
want to do unnecessary requests to providers that play nice, so a timestamp
based rate-limiting makes these kind of providers compatible with the pybikes
architecture.

This merge fixes Issue #22.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants