CIF Schedule Records: Difference between revisions
New page |
PeterHicks (talk | contribs) Tidy up CIF Schedule Records page |
||
(6 intermediate revisions by 4 users not shown) | |||
Line 1: | Line 1: | ||
== Overview == | == Overview == | ||
Schedule records are contained within the [[SCHEDULE]] data feed, and provide information about the possible schedules available for trains. For a given train service, there may be multiple schedules listed - the date of the train service and any short / very-short term plans will affect which schedule is current. | Schedule records are contained within the [[SCHEDULE]] data feed, and provide information about the possible schedules available for trains. For a given train service, there may be multiple schedules listed - the date of the train service and any short / very-short term plans will affect which schedule is current. | ||
Line 11: | Line 12: | ||
== Record Format == | == Record Format == | ||
A schedule comprises a [[CIF_Basic_Schedule | BS (Basic Schedule)]] record. For actions other than 'delete', there will be a [[CIF_Basic_Schedule_Extended | BX (Basic Schedule Extended)]] record, and a group comprising [[CIF_Location | LO/LI/CR/LT records]]: | |||
* Exactly one Location Origin (LO) record | |||
* Zero or more Location Intermediate (LI) records | |||
* Zero or more Change en Route (CR) records | |||
* Exactly one Location Terminate (LT) record. | |||
For BS records with a type of 'delete', this will be the only record, as schedules to be deleted are identified only by a truncated record. | |||
{{Navtable-CifSchedule}} | |||
{{Navtable-DataFeeds}} | {{Navtable-DataFeeds}} | ||
[[Category:Schedule Data]] | [[Category:Schedule Data]] |
Latest revision as of 08:31, 18 November 2023
Overview
Schedule records are contained within the SCHEDULE data feed, and provide information about the possible schedules available for trains. For a given train service, there may be multiple schedules listed - the date of the train service and any short / very-short term plans will affect which schedule is current.
A schedule record comprises of a header containing a schedule UID, data about the schedule (including whether it is a train, bus or ship) and validity dates, and an ordered list of locations and times at which a particular service should arrive, depart or pass.
- Originating locations will always have a WTT departure time and optionally a public departure time
- Intermediate locations in a schedule will have a passing time if they are a mandatory timing point, or an arrival and departure time if the train carries out an activity at that location
- Terminating locations will always have a WTT arrival time and optionally a public arrival time, which may be some minutes later than the WTT time
- A location may have one or more activities associated with it - for example, U for locations where the train calls to pick up passengers (i.e. not available for alighting), D for locations where the train calls to set down passengers (i.e. not available for boarding).
- A location may have engineering, pathing or performance allowances
Record Format
A schedule comprises a BS (Basic Schedule) record. For actions other than 'delete', there will be a BX (Basic Schedule Extended) record, and a group comprising LO/LI/CR/LT records:
- Exactly one Location Origin (LO) record
- Zero or more Location Intermediate (LI) records
- Zero or more Change en Route (CR) records
- Exactly one Location Terminate (LT) record.
For BS records with a type of 'delete', this will be the only record, as schedules to be deleted are identified only by a truncated record.
CIF | |
---|---|
CIF | HD (Header) • ZZ (End of File) |
TIPLOC | TI (TIPLOC Insert) • TA (TIPLOC Amend) • TD (TIPLOC Delete) |
Association | AA (Association) |
Location | BS (Basic Schedule) • BX (Basic Schedule Extended) • LO (Location Origin) • LI (Location Intermediate) • CR (Change-en-Route) • LT (Location Terminate) |
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) |