TSPEED: Difference between revisions
No edit summary |
PeterHicks (talk | contribs) m Correct 'trips and agreed pathways' as per TOPS reference data |
||
Line 12: | Line 12: | ||
|- | |- | ||
|Trips and agreed pathways | |Trips and agreed pathways | ||
|A, B, H | |A, B, H-L, P-Z | ||
|- | |- | ||
|Special Trains (Freight or Passenger) | |Special Trains (Freight or Passenger) | ||
|0 | |0-9 | ||
|} | |} | ||
Revision as of 08:38, 31 May 2013
The 'TSpeed' field is used in the train signalling ID along with the headcode. Values are as follows:
Status | Code |
---|---|
Passenger and Parcels in WTT | M, N, O |
Freight trains in WTT | C, D, E, F, G |
Trips and agreed pathways | A, B, H-L, P-Z |
Special Trains (Freight or Passenger) | 0-9 |
Network Rail Open Data Feeds | |
---|---|
Data Feeds | About the Feeds • Account States • Durable Subscriptions • Example Code ( PHP / C# / Java / Ruby / Node.js) • Advanced Uses • FAQ • Release Notes |
RTPPM | RTPPM Feed |
Train Movements | Train Movements Feed • Train Activation • Train Cancellation • Train Movement • Train Reinstatement • Change of Origin • Change of Identity • Change of Location • TSPEED Field • Planned Cancellations • Cancellation Codes |
TD | TD Feed • C-Class Messages • S-Class Messages • Train Describers • TD Berths |
VSTP | VSTP Feed |
TSR | TSR Feed • Route Codes |
SCHEDULE | SCHEDULE Feed • TIPLOC Records • Schedule and Location Records • Association Records • CIF Codes • How Scheduling Works • Allowances |
Reference Data | Reference Data Feed • TOC Codes • CIF Codes • Delay Attribution Codes • Identifying Locations (STANOX, TIPLOC, NLC and 3-Alpha Codes) • STANOX Geographical Areas • Train Planning data (BPLAN) |