D6130
Established Member
Which 1K13 is that?As much as i love RTT there are times when looking elsewhere is very important.. Currently showing 1K13 as cancelled due to an issue with the train crew yet it is running on time.
Which 1K13 is that?As much as i love RTT there are times when looking elsewhere is very important.. Currently showing 1K13 as cancelled due to an issue with the train crew yet it is running on time.
Believe they mean the XC one, it's still displaying the cancelled message but the times of it running are showing as normal tooWhich 1K13 is that?
Yes looks like this oneBelieve they mean the XC one, it's still displaying the cancelled message but the times of it running are showing as normal too
Although seemingly not for 'Tiger Worldline', whatever that is... I use RTT and Traksy and can almost always deduce what is going on from them.There is bound to be some lag between what is happening and what happens on an internet app.
It'll be this bug.There is a long standing issue where a cancellation is correctly reversed when it comes in (hence the locations aren't marked with cancelled or dashed out) but the original cancellation data that caused it still hangs around ... even if we manually delete it out of the schedule.
It's fully automatic based on signalling data, eg if train goes from berth X to berth Y then it "knows" that it can no longer call at or pass stations 2, 3, 4, 5 and will instead add passing points 6, 7, 8 and 9. The passing points are added incrementally where necessary, for example if a train is detected as going from Rochester towards Strood instead of Sole Street, then passing points will be added as far as Dartford but not beyond - until the train departs Dartford, given the 3 potential routes available from Dartford to London.How "automatically" is automatically? Does it guess the diversion route, or is it still relying on a human to tell it that?
In any case, surely you'd throw a manual delay on the point it rejoined to avoid the "delayed" problem, even if you didn't add the diversion locations in?
That is cool!It's fully automatic based on signalling data, eg if train goes from berth X to berth Y that it knows that it can no longer call at or pass stations 2, 3, 4, 5 and will instead add passing points 6, 7, 8 and 9. The passing points are added incrementally where necessary, for example if a train is detected as going from Rochester towards Strood instead of Sole Street, then passing points will be added as far as Dartford but not beyond - until the train departs Dartford, given the 3 potential routes available from Dartford to London.
On the second point, yes a manual delay will usually be added where this is known in advance. So if a train is supposed to be running Ramsgate > Canterbury > Ashford > London but is diverted to run via Dover instead, we know that this will result in a delay at Ashford so this will be manually added at the point the diversion is added to our systems.

There are many factors that require careful balancing regarding when to announce platforms, and often there are very good reasons which are out of public view, I.e. servicing of stock at a terminus, and trying to safely manage pedestrian flows through choke points of which Kings Cross has many.Same at Kings Cross, where platform numbers are announced late even if the train is stood there and staffed and ready. Obviously you do need to be aware of late changes and make sure you have the right info. The annoying thing, a lot of the issues I use RTT to avoid could be avoided by better management/procedures. If a train is ready staffed and open start getting people on it.
That's indeed a data issue.Very nicely designed and integrated into the site.
I have just noticed a curious behaviour however. Consider the following service from Plymouth to Aberdeen, which despite showing Worcestershire Parkway as a calling point in the schedule, does not show as a marker or even a line vertex on the map. I would presume that this is something in the underlying data that is causing this?
This is just a quirk of data when sets get swapped.It was recently showing a 22 car Pendolino from Edinburgh to Euston with separate train numbers.
Although seemingly not for 'Tiger Worldline', whatever that is...
Likely Darwin, the same as all customer-facing information across the industry.Be interested to see which system LNER use for delay repay - yesterday 0755 Inverness to Peterborough (1E13) on realtime shows arriving at 1539:30 (scheduled arrival 1509) but LNER claims it arrived 1538 ???
It was recently showing a 22 car Pendolino from Edinburgh to Euston with separate train numbers.
Thankfully these reasons are all open source, and anyone can submit proposed changes to them.Similarly, the delay reasons are just as frustrating, as someone who is involved in the nuances of the delay attribution process, RTT’s reasons are sometimes wildly inaccurate to just plain stupid. The “TT” reason being one during leaf fall season (cancelled due to it being autumn) which reflects badly on the industry as a whole and casual users who don’t understand such nuances.
The TT reasons being used on specific leaf fall “red days” where there is agreed time loss between the TOC and NR, and joint/full responsibility between both parties. Such adhesion delays can cause cancellations which would be displayed through Darwin as “Slippery Rails” and through to RTT “due to it being autumn”
Again, I’m not trying to take anything from away from the incredible work Tom has done but casual end users have to sometimes take with a pinch of salt what is shown on there.
having Worldline CIS, Does not automatically translate to all your stations being on TIGER - trust me on that. ( There’s a cost involved ) For example,GWR and TfW both have Worldline CIS but not all stations are on TIGER - eg Fishguard Harbour, Pembroke Dock, Sugar Loaf to name just 3 examples.It is digital reflection of the CIS for any TOC using Worldline as their CIS provider. That's why there is not universal coverage.
Why's that?having Worldline CIS, Does not automatically translate to all your stations being on TIGER - trust me on that. ( There’s a cost involved ) For example,GWR and TfW both have Worldline CIS but not all stations are on TIGER - eg Fishguard Harbour, Pembroke Dock, Sugar Loaf to name just 3 examples.
Cost for one thingWhy's that?
Darlaston DAS Willenhall WIA. They came up for me easily on RTTSomeone else might have pointed this out elsewhere, but the two new Black Country stations don't come up in the search. How do they get updated? There are a few new stations due this year.
Only when searching in 'detailed' mode; in simple mode, neither station comes upDarlaston DAS Willenhall WIA. They came up for me easily on RTT
I never use the simple mode as there is far too much useful info missing from it.Only when searching in 'detailed' mode; in simple mode, neither station comes up
in the list of suggested stations as you start typing the letters in; you have to type
the entire station name in and press enter.
MARK