Difference between revisions of "Train Activation"

From Open Rail Data Wiki
Jump to navigation Jump to search
(Added a Data Packet definition)
Line 17: Line 17:
  
 
There is no difference in handling Auto and Manually called trains.
 
There is no difference in handling Auto and Manually called trains.
 +
 +
== [Train_Movements|Train Movements] Data Entry ==
 +
 +
Following Columns are populated
 +
* msg_type, in this case 0002
 +
* msg_queue_timestamp,
 +
* source_system_id,
 +
* train_id, links to additional messages about the train
 +
* division_code,
 +
* train_service_code, schedule ID
 +
* toc_id,
 +
* loc_stanox, train Location Code

Revision as of 19:56, 23 July 2012

Overview

The Train Activation message is used to link a 10-character unique train identity to a schedule. This unique identity is used in all other message types to refer to the train.

Unique identities are guaranteed unique only within a calendar month, as the final two digits are the day of the month in which the train ran.

Linking a schedule to a unique identity

Schedules are uniquely identified by UID, start date and STP indicator. The activation message has three fields - 'train_uid', 'schedule_start_date' and 'schedule_type'. To find the schedule that a train is running to, look these up in your timetable database.

Auto and Manual Call

Internally, the activation process is known as 'calling', and a train may be called in one of two ways:

  • The majority of schedules are set up as Auto Call. Activation messages will automatically be sent for them around an hour before the scheduled departure time.
  • Some schedules are set up as Manual Call where a train may operate more than one schedule - usually a freight train which has three timetables available with different destinations, but will only run to one specific one depending on demand on the day.

There is no difference in handling Auto and Manually called trains.

[Train_Movements|Train Movements] Data Entry

Following Columns are populated

  • msg_type, in this case 0002
  • msg_queue_timestamp,
  • source_system_id,
  • train_id, links to additional messages about the train
  • division_code,
  • train_service_code, schedule ID
  • toc_id,
  • loc_stanox, train Location Code