CIF File Format: Difference between revisions
mNo edit summary |
m CIF |
||
| Line 1: | Line 1: | ||
The CIF file | The Common Interface File (CIF) format is the industry standard for transfer of schedules electronically from Network Rail's Integrated Train Planning System (ITPS) to downstream operational and information systems. | ||
The CIF file is a text file containing one record per row. Each record has a fixed length of 80 characters. The first two characters of a row identify the ''Record Type''. | |||
== Record Types == | == Record Types == | ||
| Line 7: | Line 9: | ||
* '''TA''' - [[CIF_Tiploc_Amend | TIPLOC Amend record]] | * '''TA''' - [[CIF_Tiploc_Amend | TIPLOC Amend record]] | ||
* '''TD''' - [[CIF_Tiploc_Delete | TIPLOC Delete record]] | * '''TD''' - [[CIF_Tiploc_Delete | TIPLOC Delete record]] | ||
* '''AA''' - [[ | * '''AA''' - [[CIF_Association_Record | Association record]] | ||
* '''BS''' - [[ | * '''BS''' - [[CIF_Train_Schedule | Basic schedule record]] | ||
* '''BX''' - [[ | * '''BX''' - [[CIF_Train_Schedule | Basic schedule extra details record]] | ||
* '''LO''' - [[ | * '''TN''' - Train specific note (unused) | ||
* '''LI''' - [[ | * '''LO''' - [[CIF_Train_Schedule | Origin location record]] | ||
* '''CR''' - [[ | * '''LI''' - [[CIF_Train_Schedule | Intermediate location record]] | ||
* '''LT''' - [[ | * '''CR''' - [[CIF_Train_Schedule | Change en Route]] | ||
* '''LT''' - [[CIF_Train_Schedule | Terminating location record]] | |||
* '''LN''' - Location specific note (unused) | |||
* '''ZZ''' - Trailer record (End of File) | * '''ZZ''' - Trailer record (End of File) | ||
The | The [http://www.atoc.org/download/clientfiles/files/RSPDocuments/CIF%20USER%20SPEC%20v29%20FINAL.pdf CIF End User Specification] is also available from ATOC's website, which details the format of the CIF file and the fields within. | ||
{{Navtable-DataFeeds}} | {{Navtable-DataFeeds}} | ||
[[Category:Schedule Data]] | [[Category:Schedule Data]] | ||
Revision as of 22:50, 29 March 2016
The Common Interface File (CIF) format is the industry standard for transfer of schedules electronically from Network Rail's Integrated Train Planning System (ITPS) to downstream operational and information systems.
The CIF file is a text file containing one record per row. Each record has a fixed length of 80 characters. The first two characters of a row identify the Record Type.
Record Types
- HD - Header record
- TI - TIPLOC Insert record
- TA - TIPLOC Amend record
- TD - TIPLOC Delete record
- AA - Association record
- BS - Basic schedule record
- BX - Basic schedule extra details record
- TN - Train specific note (unused)
- LO - Origin location record
- LI - Intermediate location record
- CR - Change en Route
- LT - Terminating location record
- LN - Location specific note (unused)
- ZZ - Trailer record (End of File)
The CIF End User Specification is also available from ATOC's website, which details the format of the CIF file and the fields within.
| 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) |