Difference between revisions of "CIF File Format"

From Open Rail Data Wiki
Jump to: navigation, search
m (CIF specification link not available anymore.)
Line 21: Line 21:
** '''LN''' - Location Specific Note (unused)
** '''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.
[[Category:Schedule Data]]
[[Category:Schedule Data]]

Latest revision as of 10:40, 24 October 2017

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

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