Planned Cancellations
Jump to navigation
Jump to search
Overview
Planned cancellations are schedule records with an STP indicator of "C" which are overlaid on WTT schedules. They contain no calling points, and they indicate a schedule does not apply on a particular day.
The difference between a planned cancellation and an operational cancellation is subtle, but important:
- An operational cancellation is reactive - a train was due to run to this schedule, but was cancelled for an operational reason, e.g. service disruption
- A planned cancellation is not reactive - the schedule that would apply on a particular date is overridden, for example, on a public holiday
Activations for CAN schedules
Planned cancellations will be activated by a Train Activation message as normal, but immediately cancelled with a Train Cancellation message with a 'PD' - Planned Cancellation - causation code. For the purposes of tracking real-time trains, these can be ignored.
| 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) |
