Never mind Brexit: TfL just released new tube map showing an interchange at Camden Town!!!

Mmmmm tube-y goodness. Image: TfL.

Crossrail has just been given a £1bn bail out. This, according to the Financial TImes’s Jim Pickard, is on top of the £600m bailout in July and £300m loan in October.

That, even with the pound crashing as it is right now, is quite a lot of money. It’s bad, especially at a time when there is still seemingly not a penny available to make sure trains can actually run in the north.

But the world is quite depressing enough today, so let’s focus on something happier. On Saturday night – obviously peak time for cartographic news – Transport for London emailed me to let me know it would be updating the tube map, to show more street-level interchanges:

Connections between several pairs of stations that are near to each other, but have traditionally not been shown as interchanges, now appear on the map for the first time. These include:

  • Camden Road and Camden Town
  • Euston and Euston Square
  • Finchley Road and Finchley Road & Frognal
  • Kenton and Northwick Park
  • New Cross and New Cross Gate
  • Seven Sisters and South Tottenham
  • Swiss Cottage and South Hampstead

The stations shown meet a set of criteria that has been used to help determine which should be included. This criteria includes stations less than a 700m or a 10 minute walk apart, where there is an easy, well-lit, signposted walking route and where making the change opens up additional travel options.

The results are, well, this:

In addition, interchanges between stations have traditionally appeared on the Tube map as two solid lines, irrespective of whether they are internal or external (which means customers need to leave the station and then re-enter for the station or stop they need). This approach has now been updated and shows a clear distinction between the two types, with external interchanges now being depicted by a dashed line, linking the two stations or stops.

And lo, it came to pass:

I have slightly mixed feelings about this, in all honesty. On the positive side: I think generally showing useful street-level interchanges as A Good Thing. I’ve thought for years that Camden Road/Camden Town in particular was one worth highlighting, as it opens up a huge number of north-east travel options (Finchley to Hackney, say), and apps like CityMapper tell you to use it already.


And yet, now they’ve actually done it, I’m suddenly not sure. That interchange is pretty useful if you’re an able bodied person who doesn’t mind navigating crowds or crossing roads – but the map gives you no indication that it’s a harder interchange than, say, Wanstead Park to Forest Gate.

The new map also doesn’t tell you how far you’re going to be walking at street level. I can see the argument that a 400m walk shouldn’t disqualify something as an interchange – you can end up walking that far inside certain stations (Green Park, Bank/Monument), and the map shows them as interchanges. But the new version makes no effort to distinguish between 100m walks (West Hampstead) and 700m ones (Northwick Park-Kenton), which it probably should.

I’m also slightly baffled by some of the specific choices. Is Finchley Road-Finchley Road & Frognal really a useful interchange, when there’s an easier and more direct version, one stop up the line? No hang on West Hampstead isn’t on the Metropolitan line isn’t it? So that’s what it’s about.

Okay, a better one: if you’re switching from District to Central lines in the City, you’re generally better off alighting at Cannon Street, rather than Monument, for Bank – honestly, it’s a 90 second walk to the new entrance on Walbrook. Yet that one isn’t there. What gives?

The complete new tube map. The full version is on TfL’s website, here.

On balance, showing more possible interchanges on the map is a positive change. But it doesn’t negate the need for a fundamental rethink of how the tube map looks and what it is for. And it’s not, I fear, enough to distract from the Crossrail problem.

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

 
 
 
 

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.