Format

Common Interface File

Summary

Name: Common Interface File
Identifiers: PUID: fmt/1871
Format type: Dataset
Description: The Common Interface File (CIF) format is used to transfer train schedules from Network Rail's Integrated Train Planning System to computer systems requiring train data in electronic format. The files contains a set of train schedules and amendments. These files are automatically generated and disseminated every day after a ITPS publication run is completed. CIF files are text files containing one train schedule/amendment per row, of a fixed length of 80 bytes. The first two characters of a row/schedule identify the record type, ie if it is a new record, amendment or deletion etc. This signature is quite broad, due to the fact that it is possible to receive an empty file with no amendments, consisting of a header (HD) and a trailer (ZZ) only. Lastly, it should be noted that The Rail Delivery Group uses an .mca file extension for their .cif files, however they are identical in every other respect.
Note: https://wiki.openraildata.com/index.php?title=CIF_File_Format Specification: https://www.rspaccreditation.org/downloadPublic.php?DOCUMENT=RSPS5046+P-04-00+Timetable+Information+Data+Feed+Interface+Specification.pdf&ID=1144
File extensions: cif, mca
Source: Transport for London / Transport for London
Developed by: Assist / Assist
Supported by: Assist / Assist

Note: Absolute from beginning of file, magic bytes: HD{75-80}.{80-81}. EOF, offset 0-2: .ZZ,followed by 78 bytes of white space,{0-1}.

Min Frag Length: Absolute from EOF
Offset: 0
Max offset: 2
Byte Sequence: 5A5A202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020{0-1}0A
Endianness: None