TSPEED value in 10-character TRUST id.

32 views
Skip to first unread message

Mark Withall

unread,
Jul 25, 2017, 8:50:07 AM7/25/17
to A gathering place for the Open Rail Data community
Hi all,

I'm wondering if it is possible to generate the 10-character unique TRUST identity in advance.

9 of the characters are from readily accessible information (headcode, origin location/time, day of the month). The 7th character, however, is the train status code (TSPEED).

The documentation doesn't appear to have enough information to determine, in advance, which precise value a train will be allocated in TRUST.

Does anyone have any more detail on how to determine the TSPEED value for a train?

Thanks,

Mark

Peter Hicks

unread,
Jul 25, 2017, 9:08:39 AM7/25/17
to Mark Withall, A gathering place for the Open Rail Data community
Hi Mark

You can't reliably predict the TSPEED value 100% of the time I'm afraid - you can maybe get 99.5% accuracy, but you're likely to fail quite drastically under certain conditions.

TRUST has an algorithm which sets the TSPEED to N, and then O, if there's already a train called with the TSPEED of M which starts from the same STANOX at the same time.  Trying to replicate this algorithm will be at best tricky.

One example: last Tuesday, for example, three 2D06s were due to leave from an origin in STANOX 'area' (not sure if that's quite the right term) 88xxx and were called thus:

03:26:46 W81375 - 0526 Gravesend - Charing Cross as 882D06M518
03:40:47 W81379 - 0540 Orpington - London Victoria as 882D06N518
03:42:46 L05097 - 0542 Hastings - Eastbourne as 882D06O518

If schedule L05097 is manually called at 0310 so it can be cancelled from origin, then it will have a TSPEED of M, and the other two N and O.  Or, if it were manually called at 0330, it would have a TSPEED of N.

There are some other instances too which I'd have to look up.  Of course, it's up to you whether you want to try to re-implement the algorithm - only you know what the impact of getting it wrong will be.


Peter

--
You received this message because you are subscribed to the Google Groups "A gathering place for the Open Rail Data community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openraildata-t...@googlegroups.com.
To post to this group, send email to openrail...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Mark Withall

unread,
Jul 25, 2017, 9:16:50 AM7/25/17
to A gathering place for the Open Rail Data community, mark.w...@tracsis.com
Thanks Peter.

I had a suspicion that it wouldn't be straightforward. It's interesting to know more detail though.

Regards,

Mark
Reply all
Reply to author
Forward
0 new messages