Schedule records are contained within the SCHEDULE data feed, and provide information about the possible schedules available for trains. For a given train service, there may be multiple schedules listed - the date of the train service and any short / very-short term plans will affect which schedule is current.
Schedule records are encoded as a JSON hash with a key of "JsonScheduleV1" and a value containing the schedule data.
Schedule Record Fields
|CIF_train_uid||The unique identifier for the schedule.
This is made up of a letter plus five numbers. There may be multiple schedules for one schedule UID. See also the train_uid field of the TRUST Train Activation message type.
|transaction_type||create or delete|
|schedule_start_date||The start date of the schedule|
|schedule_end_date||The end date of the schedule|
|schedule_days_runs||A seven-character field; character 1 represents Monday, character 7 represents Sunday. A 1 in a character position means that the service runs on that day, while a 0 means that it does not.
Note: this field is called schedule_days_runs within the JSON file.
|CIF_bank_holiday_running||Bank holiday running code
|signalling_id||For passenger services, this is the headcode of the service. For freight services this will be blank.|
|CIF_train_service_code||Divides trains into service groups and used for revenue reasons|
|CIF_business_sector||Formery used to denote the business sector running the service; now represent the Portion ID for services which join or split|
|CIF_speed||Planned speed of the train service|
|CIF_train_class||Seating classes available:
|CIF_sleepers||Sleeping accommodation available:
|CIF_catering_code||Up to two characters from the following:
|CIF_stp_indicator||STP (short-term planning) schedule indicator
|uic_code||Union Internationale des Chemins de Fer code for the service|
|applicable_timetable||Applicable timetable service?