I would bet good money on londoners and people from the counties that surround it use the infrastructure way more than any tourists will. If they dont like the lines having names then tough tittyNames may be easier to remember for native speakers, but they aren't for tourists and London is a tourist city.
What isn't?
Most services are good, whats wrong with that?This isn’t great is it
I would reckon that the vast majority of tourists to london are there for the oxford street/Buck Palace/Camden Market/West end shows. They probably dont care as long as they can get to those placesJust had this information from TfL
I understand the names have already been revealed, and in some cases seen on signage.
Having just looked at the maps, then the standalone Overground map is OK. However, once combined with the Tube map, does it seem confusing for visitors to London trying to navigate their way by public transport?
Getting an end of year update. As far as I’m aware they are also adding more to TfL Go apart from just the new lines so I’m guessing for they are waiting for that update to be done sillily enough.Im surprised TFL Go app hasnt been updated yet.
Elizabeth, Lioness, Weaver, etc. are all missing "line" at the end!
What isn't?
What's obvious is that there is disruption on the Elizabeth, Windrush and Metropolitan lines and everything else - including all the other bits of the Overground - is operating a good service. Previously it would've shown "Severe delays" for the Overground, when in actual fact, much of the system was operating normally.I thought that would be obvious. It's a riot of almost similar colours. Or in the case of Mildmay and Central the same colours, at least they look that way to me. Just glance at the above at it looks like there's issues on the Central line. To say one of the main reasons for was to give better status updates for Overground lines you've now lost what was previously a clear, colour coded system.
The Overground lines need separating or some kind of visual key added to easily differentiate them.
What's obvious is that there is disruption on the Elizabeth, Windrush and Metropolitan lines and everything else - including all the other bits of the Overground - is operating a good service. Previously it would've shown "Severe delays" for the Overground, when in actual fact, much of the system was operating normally.
Weird how all the lines and categories are just jumbled up like that, rather than separating out Underground, Overground, Elizabeth Line, DLR and Tramlink. Especially when it will take time for people to learn the names, which aren't geographical.
There are pairs of colours used that might be confused if the viewer isn't too careful, i.e.: Central/Windrush, Metropolitain/Weaver, Circle/Lioness, DLR/Suffragette, Jubilee/Liberty, Mildmay/Victoria, - the majority of those reading it will either be regulars just checking for disruption, or tourists/leisure travellers who generally take a bit more care when checking status.I don't think it is at all, as I said in the previous message from a quick glance which is the purpose of using a colour coded system this looks like there are issues on the Central line.
I'l point you in the direction of this thread on Reddit where they are discussing the same thing and the consensus seems to be it's a mess
The map has the overground lines with white sandwiched between the colour. That service chart has room to do the same. Bit amateurish.I thought that would be obvious. It's a riot of almost similar colours. Or in the case of Mildmay and Central the same colours, at least they look that way to me. Just glance at the above at it looks like there's issues on the Central line for example. To say one of the main reasons for was to give better status updates for Overground lines you've now lost what was previously a clear, colour coded system.
The Overground lines need separating or some kind of visual key added to easily differentiate them.
I’m very supportive of TfL giving the Overground lines their own identity, but it is frustrating to see what often seem to be obvious mistakes crop up here and there. I happened to be looking at the timetables page on the TfL website earlier and spotted at least three errors in the published PDFs:
I know it’s a lot of things to get changed all at once and there’s always the chance of human error, but it feels like these sorts of errors crop up a lot more than they used to.
- The Mildmay line timetable states in the footnotes that ‘frequent Bakerloo line services run’ between stations marked with the TfL roundel on the timetable. The three stations with such a marking on this particular line are Richmond, Kew Gardens and Gunnersbury, none of which the Bakerloo goes anywhere near! The text has clearly been copy/pasted from the Lioness line timetable, and the internal proofreading process has failed to pick up that it should refer to the District line instead.
- The line diagram on the Suffragette line timetable lists different walking distances for the same station. For example, the distance from Walthamstow Queen’s Road to Walthamstow Central is said to be 320m for the Victoria line, but 350m to the Weaver line. You have to pass along the Weaver line platforms to get to the Victoria line, so it’s not possible for them to be further away! The interchange distances between South Tottenham and Seven Sisters are similarly inconsistent - it’s apparently only 350m to the Victoria line but 560m to the Weaver line/National Rail.
- On the Mildmay line timetable line diagram, the text in the interchange box for West Hampstead is left-aligned, but on every other interchange box the text is centred.
No inconsistency there (though I haven't checked the distances) given there's direct access to the Victoria Line from the High Road but direct access to the NR station is from Seven Sisters Road.
- The interchange distances between South Tottenham and Seven Sisters are similarly inconsistent - it’s apparently only 350m to the Victoria line but 560m to the Weaver line/National Rail.
They absolutely need some way of differentiating between Tube and Overground, this is an ease-of-use nightmare, particularly for the ones with identical colours (looking at you Windrush and Metropolitan/Weaver). Either create separate sections for the different modes, or use something that isn't a block colour for non-tube lines.
This looks so much better than what TfL have done!Edit: I couldn't help but have a quick play around and try tidy it up. To me at least this is much clearer.
View attachment 170017
Although it looks like they’ve missed ‘line’ for Mildmay as well as the correct iconCityMapper has been updated today. I quite like what they've done.
View attachment 170057
View attachment 170056
Although it looks like they’ve missed ‘line’ for Mildmay as well as the correct icon
Looks like they've borrowed the alphabetical sorting algorithm from the TfL Single Fare Finder pageWeird how all the lines and categories are just jumbled up like that, rather than separating out Underground, Overground, Elizabeth Line, DLR and Tramlink. Especially when it will take time for people to learn the names, which aren't geographical.
The list isn't jumbled up; it's the case that the line(s)/mode(s) with the most severe disruption will appear at the top.Weird how all the lines and categories are just jumbled up like that, rather than separating out Underground, Overground, Elizabeth Line, DLR and Tramlink. Especially when it will take time for people to learn the names, which aren't geographical.
That is much better. Although having them in mode order as well would be even betterI don't think it is at all, as I said in the previous message from a quick glance which is the purpose of using a colour coded system this looks like there are issues on the Central line.
I'l point you in the direction of this thread on Reddit where they are discussing the same thing and the consensus seems to be it's a mess
Edit: I couldn't help but have a quick play around and try tidy it up. To me at least this is much clearer.
View attachment 170017
Disruption to London Overground services through Norwood Junction expected until the end of the day
Meanwhile, over on the NRE service disruption page , we still have: