This doesn't however say what the service status is. If you are suggesting that if there is a good service, this be replaced with a list of station closures, then this would be confusing because how would you then handle a part suspension, or delays, where stations are still closed?
Again, I'm not quite sure how this helps. The present situation reflects the service status for the overwhelming majority of customer journeys, this would require people to "drill down" and find out what is actually affected.
Actually, isn't this already an issue? Currently on TfL's website, the Northern line is listed as "severe delays", but drilling down reveals that it only applies to just the High Barnet branch, and the Northern line is in fact just fine in zone 1, the Edgware branch, and everywhere south of zone 1.
Admittedly I have no clue what the usage patterns on the Northern line are like (or anywhere on the tube really, I'm in Scotland!), but assuming the branches get roughly equal usage, this requires roughly 3/4 of the Northern line's users to drill down to see that the line's actually fine (or even more, if a significant number of Northern line journeys are exclusively in zone 1).
I think what's really needed is for the for the status to display one or more issues, each with a specific location, eg:
- "Lancaster Gate station closed" (implying good service elsewhere)
- "Severe delays throughout, Lancaster Gate station closed"
- "Severe delays on High Barnet branch, Battersea Power Station station closed"
But admittedly that's definitely going to require big technical changes, especially considering the variety of places this data is shown (e.g. Thameslink on-train PIS!).
Given the current situation, though, my inclination is that it's better to tell people too much (and require them to drill down) than to tell them everything is fine when it definitely isn't.