One man's mission to put New York's secret subway back on the map

A detail from Stewart Mader's combined New York-New Jersey subway map.

So here's an odd fact for you. It's possible to be less than a mile away from Downtown Manhattan, and yet not be in New York City at all. Across the River Hudson, just moments from the financial district, you’ll find the independent city of Hoboken, New Jersey.  

What's even better, for those who fancy saving a cool 30 per cent on their rent, it's served by its very own 24-hour metro: the Port Authority Trans-Hudson (PATH) subway system, which links Manhattan with the suburbs just across the river. The system means that stretches of New Jersey suburbia are more convenient for the heart of Manhattan than anywhere you’ll find in Brooklyn.

And yet, even many New Yorkers are only vaguely aware that it exists.


The 13-station PATH network first opened in 1908, just four years after the first subway line in New York proper. It shares five stations with the Metropolitan Transit Authority (MTA) subway system; crosses the Hudson through two tunnels (one from the Village, the other from the Battery); and provides frequent services to Hoboken, Jersey City and Newark.

There are no free transfers between the two networks; but both are compatible with the Metro Card ticketing system. The PATH is as much a part of New York’s transport system as the DLR in London, or the S-Bahn in Berlin.

And yet, the city's standard subway map does its best to play down the existence of New York's second rapid transit network, showing it in the same thin blue line it uses for infrequent heavy rail services. What's even weirder is that it's entirely silent on the existence of the state of New Jersey. Look:

An extract from the current MTA subway map. Note the lack of New Jersey. 

So why has the MTA decided to exclude the PATH system? There's no rational reason for it from the perspective of the consumer, argues writer and digital media expert Stewart Mader. It's merely that, due to an accident of history, they've ended up run by different organisations.

This, Mader decided, is a bit silly. He lives in Hoboken, and works in Lower Manhattan, all of 12 minutes away on the train. And yet, "if you look at the map, you'd think there's nothing to the west of New York”.

And so, he's launched a campaign to get the MTA to start including the PATH on its subway map. It'd look something like this:

Click to expand. 

By making the map himself, Mader told us, he hoped to demonstrate to the MTA quite how easy it would be to actually, well, make this map.

This is not a new idea. As late as the 1960s, the PATH trains did appear on the subway map, albeit in a different colour to the main system:

An extract of the 1968 New York subway map.

Resurrecting this combined effort could be an easy win for the city authorities, Mader argues, expanding the functional area of the city for many residents at almost no cost. "We live in an era when capital construction is expensive. But ‘expansion’ doesn't have to mean building a new line – it can come from giving a clearer map."

Mader's campaign has attracted support from the mayors of Hoboken and Jersey City (well they would, wouldn’t they). Those who'd have to make the final decision, though, are the authorities at the MTA itself. Watch this space.

You can read more about this campaign here.

 
 
 
 

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.