CIF Association Records

Record Format

Associations are relationships between two schedules (i.e. a main train and an associated train.) Association records are contained within the SCHEDULE data feed, and provide information about the possible associations between train schedules. These can list the service that forms a given schedule and / or the service that a given schedule goes on to form.

For further details, see the Network Rail Common Interface Format file specification.

AANY80987Y808801601041602121111100JJSPRST     TP                               P

Record Fields

FieldFormatSizeMandatoryComment
Record IdentityString2YValue AA.
Transaction TypeString1YThe type of transaction
  • N - New
  • D - Delete
  • R - Revise.
Main Train UIDString6YUID of one train in the association.
Associated Train UIDString6YUID of the other train in the association.
Association start dateDate (YYMMDD)6YStart date of the association.
Association end dateDate (YYMMDD)6YEnd date for the association.
Association daysBit String7YA seven-bit field; first bit starting from the left represents Monday, and last bit represents Sunday. A 1 means that the service runs on that day, while a 0 means that it does not.
Association CategoryString2Y*The type of association
  • JJ - Join
  • VV - Divide
  • NP - Next.
Association Date IndicatorChar1Y*Date relationship of the association
  • S - Standard - the association occurs on the same day
  • N - Over next-midnight - the association occurs the next day
  • P - Over previous-midnight - the association occurs the previous day.
Association LocationString7YTIPLOC of the location where the association applies.
Base Location SuffixInteger1Together with the TIPLOC, identifies the event on the base UID.
Association Location SuffixInteger1Together with the TIPLOC, identifies the event on the associated UID.
Diagram TypeChar1YNot used. Value T.
Association TypeChar1Y*P = passenger use, O = operating use only.
SpareString31
STP IndicatorChar1YSTP (short-term planning) schedule indicator:
  • C - STP cancellation of permanent association
  • N - New STP association (not an overlay)
  • O - STP overlay of permanent association
  • P - Permanent association

* may be truncated in Delete records.

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) STOMP Client Libraries 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)
This article is issued from Openraildata. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.