RTT gets a lot of mention here but the last post on its "news" section is January 31st 2017. Is it an abandoned project?
RTT gets a lot of mention here but the last post on its "news" section is January 31st 2017. Is it an abandoned project?
It works doesn’t it?RTT gets a lot of mention here but the last post on its "news" section is January 31st 2017. Is it an abandoned project?
I don't believe so, though I suspect its owner has different priorities so isn't actively developing new features as things stand. It's good as it is, though.
Well, I don't know that it works unless I check the output. It might be spitting out ancient cached results for all I know if the project is dead.It works doesn’t it?
What more do you want from it?
Well, I don't know that it works unless I check the output. It might be spitting out ancient cached results for all I know if the project is dead.
Updated train info, e.g. max speeds, first class info, unit info etc.It works doesn’t it?
What more do you want from it?
Updated train info, e.g. max speeds, first class info, unit info etc.
All turbostars are classed as express sprinters, that would be an easy update!
I do like it though and it can be very helpful, I use it a lot to see how on time my train is.
The TOC code description was updated when ATW (Arriva Trains Wales) changed to TfW (Transport for Wales) towards the end of last year.
But an easy algorithm would be that if these timings are for a certain operator e.g. greater Anglia, then change unit name to 170 turbostar, GA don't even operate 158s so would be easy. Same for southern and the diesel units, as these are the only diesel units they operate.Remember the unit info is not what works a train but the timings known as the Timing Load that has been selected to use and suitable for what works it
It’s the timing load used in the NR train planning system that RTT takes its feed from.
You don’t need to operate a certain class of stock to use it’s timing load. It’s about what set of times you use to compile a timetable, not what class of stock you operate.
Not really true. Looked at doing this before. Setting something up like this initially is easy, then they start changing their fleets. 755s being a primary example. It's hard enough keeping up with signalling system changes.But an easy algorithm would be that if these timings are for a certain operator e.g. greater Anglia, then change unit name to 170 turbostar, GA don't even operate 158s so would be easy. Same for southern and the diesel units, as these are the only diesel units they operate.
RTT has its faults like diverted trains disappearing after the point at which it was diverted so I did not know what time I should meet someone off a train.
The AW code is still in use but the train detail itself shows Transport for Wales. There is a thread here currently quite active discussing the Codes:-
https://www.railforums.co.uk/threads/toc-codes-when-operators-change-hands.188866/page-2
None of the apps/sites do that though - it takes the data from NR’s data feed. To use the advanced version some knowledge of what you’re looking at is essential.RTT has its faults like diverted trains disappearing after the point at which it was diverted so I did not know what time I should meet someone off a train. I have heard of people helping by checking distances and timing so it is working.
However I am very happy with it and, like many others, I use it regularly.
That only works so far. To take TfW as an example, both their 175s and 58s are listed under express sprinter (158) timings. One can distinguish between them by whether they're listed as 90mph or 100mp max speed. And that isn't guaranteed to be accurate either: 1K62 to Crewe is timed as 100mph, and the return working 1D10 is timed for 90. Which is the "correct" one?But an easy algorithm would be that if these timings are for a certain operator e.g. greater Anglia, then change unit name to 170 turbostar, GA don't even operate 158s so would be easy. Same for southern and the diesel units, as these are the only diesel units they operate.
That's the one thing I'm going to miss most being recently retired - access to TOPS/TRUST off booked route reports!None of the apps/sites do that though - it takes the data from NR’s data feed. To use the advanced version some knowledge of what you’re looking at is essential.
...
That only works so far. To take TfW as an example, both their 175s and 58s are listed under express sprinter (158) timings. One can distinguish between them by whether they're listed as 90mph or 100mp max speed. And that isn't guaranteed to be accurate either: 1K62 to Crewe is timed as 100mph, and the return working 1D10 is timed for 90. Which is the "correct" one?
Elsewhere, what do you do with an EMT service that's pathed as a "Class 150/153/155/156 (Sprinter) DMU", given that EMT operate both 153s and 156s? And as for Northern's fabled Random Unit Generator...
Yes. They're just the timing models used. But for Denyboy's plan:But it is not intended to show what is actually booked to work it. All these classes are 75mph
it would be problematic.But an easy algorithm would be that if these timings are for a certain operator e.g. greater Anglia, then change unit name to 170 turbostar, GA don't even operate 158s so would be easy. Same for southern and the diesel units, as these are the only diesel units they operate.
Hard enough to do properly for the 'easy' stuff (all Ryde-Shanklin trains are class 483, for example). Once that info is available people will clamour for the same information everywhere else.Yes. They're just the timing models used. But for Denyboy's plan:
it would be problematic.