TfL is offering you the chance to stop two proposed Bakerloo line stations from having stupid names

Bakerloo line trains at London Road depot, mournfully wishing they could continue their journey to the south. Image: Getty.

Ever wanted to name a tube station? Well boy is this your lucky week. The latest round of Transport for London's interminable consultation on the proposed extension of the Bakerloo line from Elephant & Castle to Lewisham, hopefully due to arrive at some point in the early 2030s, is asking your input into names.

Necessary background blah blah blah. The most efficient way of running a metro line is to have it cross the city. The Central Line, for example, doesn't just allow west Londoners to get into the city centre: it allows east Londoners to do the same, and for everyone to get about within the city centre to boot. All that and it's only one line. Amazing really, isn't it?

But the Bakerloo line, unusually, isn't doing all this, because it gets to the south-eastern-most edge of the city centre and then gives up. That doesn't just mean that south east London remains the bit of the capital most poorly served by TfL's rail network, although it does mean that – there are no stations inside the yellow box here, look:

The tube/rail desert, with the rough location of the proposed new stations marked. Image: Google Maps.

It also means that the line through the centre isn't pulling its weight compared to every other line, because it's a lot more useful to commuters coming from the north west than from the south east. That's great if you want to get a seat for the six minutes it takes to get from Elephant to Embankment. It's not great if you're, say, in charge of London's transport network and want to sweat your assets.

Anyway, the plan for some time has been to extend the line under New and Old Kent Roads, down to New Cross Gate and Lewisham. A later phase may see it take over the Hayes branch of the South Eastern Rail network, but one thing at a time. The official map of the proposal looks like this:

Ooooh. Image: TfL.

Old Kent Road 1 and Old Kent Road 2 are obviously rubbish names for stations, so the latest round of consultation suggests some alternatives: Old Kent Road or Burgess Park for the northern one, Old Kent Road or Asylum for the southern.

CityMetric has long argued that naming stations after roads is stupid: either the road is long enough that it's not a useful name because who knows if you’re at the right end or not, or short enough that it's only useful to people who already know an area. The fact that two different stations might revel in the name Old Kent Road seems to me to prove this point pretty nicely – so if I had my way TfL would go with Burgess Park and Asylum. The latter, named for both Asylum Road and, well, what used to be an asylum, seems particularly cool to me.

Alternatively, buses terminating at the former have sometimes said "Old Kent Road Dun Cow" after a long dead pub, and naming a tube station after some livestock is amusing too, so, Dun Cow, why not?


Meanwhile the latter site, next to the junction between Asylum Road and the Old Kent Road, is sometimes known as Canal Bridge, because it used to be where the Old Kent Road crossed the Surrey Canal. The latter is long gone – although more bridges across it remain in Burgess Park, which is nicely surreal – but naming tube stations after two things that aren't there any more would be amusing too.

Anyway, the point is: please don't call either of these stations Old Kent Road, the world is confusing enough as it is. Now go vote.

Incidentally, one thing TfL has already decided is that there won't be a third Old Kent Road station, at its northernmost point, the Bricklayers Arms junction. This seems a shame to me, but I suppose they know what they're doing.

Jonn Elledge is the editor of CityMetric. He is on Twitter as @jonnelledge and on Facebook as JonnElledgeWrites.

Want more of this stuff? Follow CityMetric on Twitter or Facebook.

 
 
 
 

London’s rail and tube map is out of control

Aaaaaargh. Image: Getty.

The geographical limits of London’s official rail maps have always been slightly arbitrary. Far-flung commuter towns like Amersham, Chesham and Epping are all on there, because they have tube stations. Meanwhile, places like Esher or Walton-on-Thames – much closer to the city proper, inside the M25, and a contiguous part of the built up area – aren’t, because they fall outside the Greater London and aren’t served by Transport for London (TfL) services. This is pretty aggravating, but we are where we are.

But then a few years ago, TfL decided to show more non-London services on its combined Tube & Rail Map. It started with a few stations slightly outside the city limits, but where you could you use your Oyster card. Then said card started being accepted at Gatwick Airport station – and so, since how to get to a major airport is a fairly useful piece of information to impart to passengers, TfL’s cartographers added that line too, even though it meant including stations bloody miles away.

And now the latest version seems to have cast all logic to the wind. Look at this:

Oh, no. Click to expand. Image: TfL.

The logic for including the line to Reading is that it’s now served by TfL Rail, a route which will be part of the Elizabeth Line/Crossrail, when they eventually, finally happen. But you can tell something’s gone wrong here from the fact that showing the route, to a town which is well known for being directly west of London, requires an awkward right-angle which makes it look like the line turns north, presumably because otherwise there’d be no way of showing it on the map.

What’s more, this means that a station 36 miles from central London gets to be on the map, while Esher – barely a third of that distance out – doesn’t. Nor does Windsor & Eton Central, because it’s served by a branchline from Slough rather than TfL Rail trains, even though as a fairly major tourist destination it’d probably be the sort of place that at least some users of this map might want to know how to get to.

There’s more. Luton Airport Parkway is now on the map, presumably on the basis that Gatwick is. But that station doesn’t accept Oyster cards yet, so you get this:

Gah. Click to expand. Image: TfL.

There’s a line, incidentally, between Watford Junction and St Albans Abbey, which is just down the road from St Albans City. Is that line shown on the map? No it is not.

Also not shown on the map: either Luton itself, just one stop up the line from Luton Airport Parkway, or Stansted Airport, even though it’s an airport and not much further out than places which are on the map. Somewhere that is, however, is Welwyn Garden City, which doesn’t accept Oyster, isn’t served by TfL trains and also – this feels important – isn’t an airport.

And meanwhile a large chunk of Surrey suburbia inside the M25 isn’t shown, even though it must have a greater claim to be a part of London’s rail network than bloody Reading.

The result of all these decisions is that the map covers an entirely baffling area whose shape makes no sense whatsoever. Here’s an extremely rough map:

Just, what? Image: Google Maps/CityMetric.

I mean that’s just ridiculous isn’t it.

While we’re at it: the latest version shows the piers from which you can get boats on the Thames. Except for when it doesn’t because they’re not near a station – for example, Greenland Pier, just across the Thames to the west of the Isle of Dogs, shown here with CityMetric’s usual artistic flair.

Spot the missing pier. You can’t, because it’s missing. Image: TfL/CityMetric.

I’m sure there must be a logic to all of this. It’s just that I fear the logic is “what makes life easier for the TfL cartography team” rather than “what is actually valuable information for London’s rail passengers”.

And don’t even get me started on this monstrosity.

Jonn Elledge is the editor of CityMetric. He is on Twitter as @jonnelledge and on Facebook as JonnElledgeWrites.