Upcoming Games

(UTC times)


Full list
Add a game

Upcoming Events

No events to display

Who's Online

Person82 (1 users seen recently)

How many errors/mistakes can be in one Timetable

You are here: Home > Forum > Miscellaneous > The real thing (anything else rail-oriented) > How many errors/mistakes can be in one Timetable

Page 1 of 1

How many errors/mistakes can be in one Timetable 15/11/2016 at 17:36 #88362
08wrighta
Avatar
26 posts
Hi,
So I was just checking my train status for the way home when I ran into this timetable which was entertaining to read,
here is the timetable in question:

http://www.realtimetrains.co.uk/train/H36456/2016/11/15/advanced/
http://l.facebook.com/l.php?u=http%3A%2F%2Fwww.realtimetrains.co.uk%2Ftrain%2FH36456%2F2016%2F11%2F15%2Fadvanced&h=PAQELq6DT

Curious, how many are actual errors and how does the timing system get so messed on 1 train, I assume its cause there are several timing points that are the same which has confused the timing system, or would be a network rail issues/ faulty reading equipment?

Alex

Last edited: 15/11/2016 at 17:37 by 08wrighta
Reason: original link not working

Log in to reply
How many errors/mistakes can be in one Timetable 15/11/2016 at 17:44 #88363
Sacro
Avatar
1171 posts
08wrighta in post 88362 said:
Hi,
So I was just checking my train status for the way home when I ran into this timetable which was entertaining to read,
here is the timetable in question:

http://www.realtimetrains.co.uk/train/H36456/2016/11/15/advanced/
http://l.facebook.com/l.php?u=http%3A%2F%2Fwww.realtimetrains.co.uk%2Ftrain%2FH36456%2F2016%2F11%2F15%2Fadvanced&h=PAQELq6DT

Curious, how many are actual errors and how does the timing system get so messed on 1 train, I assume its cause there are several timing points that are the same which has confused the timing system, or would be a network rail issues/ faulty reading equipment?

Alex
It's down to how Tom (the guy behind RealTimeTrains) is interpreting the data. he's using TD steps and not accounting for trains that run over the same "location" multiple times. The later pass is getting recorded as an earlier pass (and then both end up showing the earlier pass delay time I think).

OpenTrainTimes I think is using a different method but seems to be showing a more sane result.

Log in to reply
The following user said thank you: 08wrighta