Slipping and sliding in the Cotswolds

[whole diary]

[philips999]

Well, the 1P26 has got through as far as Hanborough without a glitch so far. My lucky day?

[Worcester_Passenger]

The second up train, the 04:50 from Hereford, is shown on JourneyCheck as being diverted between Worcester and Didcot, but is shown on Realtimetrains as running from Charlbury to Didcot in 15 minutes without stopping at Oxford.

[CLPGMS]

The second up train, the 04:50 from Hereford, is shown on JourneyCheck as being diverted between Worcester and Didcot, but is shown on Realtimetrains as running from Charlbury to Didcot in 15 minutes without stopping at Oxford.

It did run via Swindon.  Times in the Ascott/Charlbury area are those for the following train 1P21 (0528 HFD^» (Hereford - next trains)-PAD^» (Paddington (London) - next trains)), which seem to have been confused with the previous one.

[tomL]

Another area where RTT^» (Real Time Trains - website) doesn't appear to cope is when a train is diverted en route. There doesn't appear to be the facility to record that it is now going a completely different way.

That is a problem for other systems like the CIS^▸ (Customer Information System).  If a train from the West is booked to run via the Berks & Hants but is sent via Melksham and Swindon at the last minute the system "loses" it at Westbury and after the default 10 minutes the CIS starts showing the train as "Delayed" until it reaches Oxford Road Junction just outside Reading.  At that point the screens then revert to showing a time.

I'm pretty sure there is way to figure that out with the data from the network rail data feeds. I've been nerding out with them over the last couple months. But I'm guessing that discussion would be the place of a dedicated board/thread for it. If that could be done, MODS?

As a software developer it has interested me how these things work, but I haven't been able to see under the covers, only the data Network rail has made available which even in itself is very interesting.