Categories
Data

Lime Bikes Now in Google Maps

The Google Maps Android app now shows the locations of available Lime bikes, which, in the UK, operate in much of London, Milton Keynes and Oxford. It is, for now, quite well hidden.

The app shows the bikes as a potential option when planning a journey, although not as a dedicated entry in the mode choice “band”. Instead, they currently appears as:

1. A sub-option when you choose cycling (which you would probably only do if you had your own bike). “Your bike” is the default, but Lime appears as a toggle at the bottom of the app.:

On selecting it, it will show the route to the nearest bike, and also other nearby Lime bikes:

2. An “also consider” option when looking a public transport options – interestingly this one picks a slightly further away Lime bike, but one which results in a much shorter overall journey (7 minutes here) than the “dedicated cyclist” option above:

3. A suggested alternative “route” when looking at the walking route map, which also picks the shortest walk/cycle combination route:

The data displayed includes the number of bikes “nearby”, the walking time to the nearest one, a confirmation that it is an “electric bike” (i.e. pedelec), its battery range, a guideline journey length and time, and an estimated cost.

Google does know Lime’s operating area – if you choose a origin or destination that is outside of it, then the option doesn’t appear. However, it doesn’t show this boundary in the app itself. Lime’s boundary is fairly nebulous – it has two official operating areas in north and south London but in practice currently allows journeys to start/end in the central area between the official areas, without penalties being applied.

One thing to note is, the bikes don’t appear in the app if you are not planning a journey. So it is, for now, rather hidden away. However, the general public will probably not think of using a single-mode app for their journey planning, no matter how each of the operators would love them to. So, having this information on Google Maps is a really big deal for the 99% of people who would see bikeshare as an alternative rather than the first choice mode in their mind. Especially as the other 5 systems currently operating in central London (Santander Cycles, Mobike, Jump, Freebike and Beryl) are not currently offered as an option. Google Maps does show Santander Cycle docking stations (if you zoom right in) with the current number of bikes there, but doesn’t appear to suggest journeys with these.

CityMapper continue to also map Lime bikes, along with Mobike and Santander Cycles – so 3 of the 6 central London systems:

In both Google Maps and CityMapper, the app will switch away to the dedicated Lime app (if you have it installed) when you start a transaction (i.e. hiring the bike).

Lime announced the tie-in on their website. It looks like it is a direct partnership by the two. Lime data is available for some areas in the US (e.g. New York City) via an GBFS-format open data feed, but this does not include London.

TfL’s own journey planner suggests Santander Cycles, but none of the other five, on the journey planner section of its website. Uber’s app is having a go at trying to be a multi-modal planner by including TfL rail/bus options, but of course only its own “Jump” bikes for its bikeshare options. It currently feels like the rail/bus information is only there to highlight how much better/quicker its own options may be.

So, multi-modal journey planning continues to make small improvements, but we are still a long way from any one app showing all the options. Meanwhile, on the City of London/Islington border, six separate systems, all with different operating areas, fees and rules, fight it out, while for large parts of London, only driving, expensive cabs or slow buses remain the only option.

One reply on “Lime Bikes Now in Google Maps”

London busses are hardly slow since they have dedicated bus lines brought in by the first Mayor of London, Ken Livingstone.

Leave a Reply to BILL Cancel reply

Your email address will not be published. Required fields are marked *