londoner
thinking on '73 stock
Posts: 478
|
Post by londoner on Oct 1, 2019 2:12:31 GMT
In my opinion, regardless of what train they are intending to catch, the passengers are the responsibility of the company operating the station whilst they are on the concourse or platform, only becoming the rain operator's responsibility when they board a train, and thus SWT should have made it their business to find out why THEIR departure screens were giving out duff information, and if the source of the duff information was TfL, getting them to correct it. But since SWR (and SWT and BR before them) have always pretended that platforms 3 to 7 at Richmond (and 1-4, 9 and 10 at Wimbledon) are mere figments of our imagination, perhaps TfL should insist on having their own presence there (as for instance SWR do at Network Rail-managed Waterloo)
You should be able to access the train times for Richmond station, as well as the platform numbers, directly using the following link:
You can also use the link on TfL listed here which is probably presented in a nicer format:
Note that Richmond station has an ID code of "940GZZLURMD". All stations seem to have another code, and for Richmond this is listed as "1000192" but I found issues with using the latter code, so I always used the former. Also note that when no services are run, no information is listed in the first link, i.e. it will be empty, denoted by "[]" in the raw data column.
Anyway, it may be useful to first check whether the SWR boards are giving the same information as the information provided on the TfL API. If the data matches correctly during the disruption, then it is likely an issue at TfL's end, and at least in my mind, there is not much SWR could do to change the displayed information. It is also probably difficult for the front line staff in such circumstances. In my mind, its something the management between SWR and TfL need to sort out and better cooperation is needed.
|
|
|
Post by norbitonflyer on Oct 1, 2019 6:16:45 GMT
You should be able to access the train times for Richmond station, as well as the platform numbers, directly using the following link: You can also use the link on TfL listed here which is probably presented in a nicer format: Doubtless, but you shouldn't need to, and presented with a screen showing no District Line trains, and a possible but less convenient alternative about to leave in 30 seconds, and a ticket/Oyster etc in one hand and a bag in the other, there isn't time to start messing about with a smartphone to check. I did in fact use my phone once on the train Overground train, and indeed discovered that the station screens were telling porkies, but it was a bit late by then. It is also probably difficult for the front line staff in such circumstances. In my mind, its something the management between SWR and TfL need to sort out and better cooperation is needed. Absolutely it is something for management to sort out. The front line staff must get fed up of having to tell passengers they are getting the mushroom treatment (kept in the dark, and fed ordure)
|
|
|
Post by commuter on Oct 1, 2019 10:58:16 GMT
You should be able to access the train times for Richmond station, as well as the platform numbers, directly using the following link:
You can also use the link on TfL listed here which is probably presented in a nicer format:
No disrespect... but did you actually click on either of these links and read the information provided? If you did you would have seen that the information given for all five platforms accessible from the North London Line show the exact same three trains as being the next to depart. Therefore these links are useless in the context for the O.P as they don't tell you what platform the next train is due to depart from. Something you also won't be able to tell from this link is that the times given are actually the arrival times of the trains, not when they are due to depart. The reason for this is that the data is taken from the L.U.L TrackerNet system and it is not intelligent enough to actually cope with trains getting to the end of the line and turning around. The same even happens on modern signalled lines, you'll see the same thing at places like West Ruislip and Hammersmith.
|
|
|
Post by aslefshrugged on Oct 1, 2019 11:43:08 GMT
|
|
rincew1nd
Administrator
Junior Under-wizzard of quiz
Posts: 10,225
|
Post by rincew1nd on Oct 1, 2019 18:32:28 GMT
And correct me if I'm wrong but aren't the boards (and the information on them) Network Rail's rather than SWR's? I think it's a bit of a bodge, the data comes from NR but the boards (as part of the station infrastructure) are managed by SWR.
|
|
|
Post by silverfoxcc on Oct 2, 2019 22:48:00 GMT
Re Cust care. I hope the person involved in the incident last night is ok. There were a few 'tuts' from pax, on hearing there were delays but i didn't bother trying to explain that their problem might pale into insignificance, they appeared to be too wrapped up in their own universe BTW the announcers were doing a good job keeping people informed on where trains were and timings
|
|
|
Post by scheduler on Oct 3, 2019 23:41:34 GMT
Surely it can't be too difficult to get Line Information Specialist's updates through to a non-LU station such as Richmond. The problem is, it won't fix Network Rail's signalling part, so it is not going to correct the departure monitors at the station. The platforming at Wimbledon and Richmond is entirely done by Network Rail, the platforms at these stations do not even appear in the District WTT. I entirely agree that a better solution to these problems needs to be found. Richmond branch is problematic, but the Wimbledon branch is virtually entirely LU, with the occasional empty stock movement over the bottom end of the route, surely it would be better if LU signalled and controlled this section.
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Oct 4, 2019 0:19:00 GMT
And for that very reasoning with the empty stock moves it’s never going to happen the cost would be ridiculously expensive
|
|
|
Post by commuter on Oct 4, 2019 9:47:11 GMT
Surely it can't be too difficult to get Line Information Specialist's updates through to a non-LU station such as Richmond. The problem is, it won't fix Network Rail's signalling part, so it is not going to correct the departure monitors at the station. The platforming at Wimbledon and Richmond is entirely done by Network Rail, the platforms at these stations do not even appear in the District WTT. I entirely agree that a better solution to these problems needs to be found. Richmond branch is problematic, but the Wimbledon branch is virtually entirely LU, with the occasional empty stock movement over the bottom end of the route, surely it would be better if LU signalled and controlled this section. 100% it would... the number of signal failures and other incidents on this line that occur and take twice as long to sort out because Network Rail are just not set up to deal with incidents as efficiently and effectively as L.U.L. Sadly even after the upgrades the status quo will persist.
|
|