Difference between revisions of "CIF File Format"

From Open Rail Data Wiki
Jump to navigation Jump to search
m
m (CIF)
Line 1: Line 1:
The CIF file contains a sequence of records.  Each record is 80 character long.  The first two bytes of a record identifies the type of a record.
+
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''' - [[CIF_Association | Association record]]
+
* '''AA''' - [[CIF_Association_Record | Association record]]
* '''BS''' - [[CIF_Basic_schedule | Basic schedule record]]
+
* '''BS''' - [[CIF_Train_Schedule | Basic schedule record]]
* '''BX''' - [[CIF_Basic_schedule_extra | Basic schedule extra details record]]
+
* '''BX''' - [[CIF_Train_Schedule | Basic schedule extra details record]]
* '''LO''' - [[CIF_Origin_location | Origin location record]]
+
* '''TN''' - Train specific note (unused)
* '''LI''' - [[CIF_Intermediate_location | Intermediate location record]]
+
* '''LO''' - [[CIF_Train_Schedule | Origin location record]]
* '''CR''' - [[CIF_Change_en_route | Change en Route]]
+
* '''LI''' - [[CIF_Train_Schedule | Intermediate location record]]
* '''LT''' - [[CIF_Terminating_location | Terminating location record]]
+
* '''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 [[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.
+
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

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 UsesFAQ 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 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