I guess this is the API it uses. It's pretty impressive. Seemingly hundreds of bike sharing systems are on this thing. It uses OSM for the background, and gives you a reading on how many bikes are at a given station.
Yes, when those laws are in place, but almost never actually enforced. Nextbike[0] is extremely popular in my city, even though my country has a helmet law in place. They also offer a bike for 30 minutes per day completely free (you can also rent two bikes for free at the same time), so that alone makes it a pretty easy way to travel through half a city without paying a dime. Not a day goes by without me seeing one[1].
As far as my experience goes, the country did try heavily enforcing the helmet law when they first introduced it (about a decade ago), now it seems to me like the police simply doesn't care if you're wearing a helmet or not.
Of course, if you commit any other traffic violation on a bike, you can be pretty damn sure that they're gonna bundle it with "not wearing a helmet" fine.
Vancouver's seems to be pretty successful and BC has a bike helmet law.
Vancouver's Mobi bike system did a good job with their messaging around helmets to make it optional to users. There is a helmet attached to each bike lock, and a convenient basket on the bike where you can put the helmet if you don't want to use it.
I built an app over it that attempts to predict the future state of any network. It later recommends addings/substractions in order to keep offer and demand balanced among stations.
It could work in about 440 cities but none of the big companies that lead this wanted this. What would you do with it?
I found two reasons here:
- They make money by using bikes as advertising space, so they do not really care about the overall quality of the system as long as they have a permanent exploitation contract.
- They use historic data to approach future situations. In spite they do not have alert systems, they seem to think this is enough. Although, when sun suddenly appears, the shore tends to get crowded and "locked" for hours; they doing nothing about it.
What my system was going to provide was smart routes for the vans, to add or subtract bikes on strategic places.
I'm pretty sure all these companies already have a system like that. The problem is actually getting the bikes moved given the amount of personnel/vans they have.
This is interesting, because when I'm in front of an empty station, the app would tell me when I get a chance to have someone park a bike. With an app telling me it should happen in less than 2mn, I can wait confidently.
My network : Velib, Paris.
My local city has just got a slightly different type of bike sharing scheme where there are no stations/docks for the bikes, but you're allowed to leave them anywhere sensible [1]. From other articles including the guardian one linked above, it seems that this a model that's been used in China and certainly seems to have proven very rapidly scalable.
I guess in these cases it's quite difficult, since it's likely not feasible to update the locations of individual bikes for these guys. I've checked their map and Bristol, UK doesn't appear to show YoBike at the moment, however it's only been in action for a few weeks.
Great project, it seems that some companies —like Citymapper— use the API[0]. Would be nice if they also contributed with code or supported the author.
Just spent 3 weeks in 6 cities in China. Ofo and Mobike seems to be the biggest bike share companies. There is also a company that makes electric bikes (with hub motor) available for bike share.
How they work:
1. Pay a deposit (99 RMB for Ofo, 299 RMB for Mobike) and register
2. Scan the QR code to unlock the bike -Mobike will unlock automatically- Ofo will send a pin to your phone that you can use to unlock the bike.
3. When you are done, just lock up your bike (rear wheel) and leave it anywhere.
In Shanghai it was common to see incensed security Guards dragging bikes off premises. Bikes definitely do clutter up precious walking space.
Those bikes would become inoperable within days, and could present significant legal liability.
Citibikes and such are quite heavy because they must withstand a lot of abuse. The quality of 'department store' bikes are very low; they're often not even assembled correctly.
How is the data gathered? In Stockholm all three items were in the middle of the water without any real information. The names sounded faux and were ungooglable.
Seems Stockholm's system in Citybikes were the remnants of a test project by JCDecaux, which was providing the data. The actual project on Stockholm is run (or at least used to be) by ClearChannel.
Actually, many years ago we supported Stockholm's system but stopped doing so after receiving a C&D by, apparently, a sole guy that had permission to use the data in exchange for providing the apps. Most possibly the situation has changed (this was more than 5 years ago) but it left an aftertaste that has stopped me from adding it. A PR to the project for adding Stockholm would be welcome, though.
Since the info is scraped from the respective official websites, the Chinese networks will only be added once someone puts in the work to reverse-engineer their apps.
I think you're just seeing a poor design choice: the purple dots they use to indicate cities with bike shares are very visible at the whole-world zoom level, but virtually impossible to see when you've zoomed in because they're the same size and in the same location as the map's default city marker.
In case you mean the dot just next to London, that's a town named Slough, with their own bike share system. By clicking on the dots you can actually zoom in on the systems. Here are some links with these zoomed in:
https://f-droid.org/repository/browse/?fdcategory=Navigation...
I guess this is the API it uses. It's pretty impressive. Seemingly hundreds of bike sharing systems are on this thing. It uses OSM for the background, and gives you a reading on how many bikes are at a given station.