Train Movement
Overview
The Train Movement message is used to indicate a train has passed a particular reporting point, indicated by the reporting_stanox
field. The STANOX may represent a station or junction.
Example
"header": { msg_type:"0003", source_dev_id:"", user_id:"", original_data_source:"SMART", msg_queue_timestamp:"1341391532000", source_system_id:"TRUST" }, "body": { event_type:"DEPARTURE", gbtt_timestamp:"", original_loc_stanox:"", planned_timestamp:"1341393780000", timetable_variation:"22", original_loc_timestamp:"", current_train_id:"", delay_monitoring_point:"true", next_report_run_time:"1", reporting_stanox:"52701", actual_timestamp:"1341395100000", correction_ind:"false", event_source:"AUTOMATIC", train_file_address:,platform:"", division_code:"21", train_terminated:"false", train_id:"521N16ME04", offroute_ind:"false", variation_status:"LATE", train_service_code:"21939001", toc_id:"21", loc_stanox:"52701", auto_expected:"true", direction_ind:"DOWN", route:"1", planned_event_type:"DEPARTURE", next_report_stanox:"52226", line_ind:"M" }
Important Fields
The fields of main significance are:
Field | Value | Explanation |
---|---|---|
event_type | DEPARTURE | the train has departed the STANOX reported |
planned_timestamp | 1341393780000 | The time the train should have departed the STANOX ( 09:23:00 ) |
actual_timestamp | 1341395100000 | The time the train actually departed the STANOX ( 09:45:00 ) |
train_id | 521N16ME04 | train header code. provides a unique identifier for this journey. Digits 3-6 indicate the route, which can be looked up in the timetable data (1N16 - In this case may have been Liverpool Street -Clacton-on-Sea ) |
reporting_stanox | 52701 | The location of the train when the message occured. (Bow Junction in this case) |
next_report_stanox | 52226 | The next location where this train will report its location. (Stratford in this case) |