Difference between revisions of "Train Movement"
Jump to navigation
Jump to search
PeterHicks (talk | contribs) m (→Header: Add GPS in to the list of data sources) |
Alex Copland (talk | contribs) m (Reordered body table to order it appears in the feed) |
||
Line 32: | Line 32: | ||
!Description | !Description | ||
|- | |- | ||
− | | | + | |event_type |
− | |The | + | |The type of event - either "ARRIVAL" or "DEPARTURE" |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
|- | |- | ||
|gbtt_timestamp | |gbtt_timestamp | ||
|The planned GBTT (passenger) date and time that the event was due to happen at this location | |The planned GBTT (passenger) date and time that the event was due to happen at this location | ||
+ | |- | ||
+ | |original_loc_stanox | ||
+ | |If the location has been revised, the STANOX of the location in the schedule at activation time | ||
|- | |- | ||
|planned_timestamp | |planned_timestamp | ||
|The planned date and time that this event was due to happen at this location | |The planned date and time that this event was due to happen at this location | ||
|- | |- | ||
− | | | + | |timetable_variation |
− | | | + | |The number of minutes variation from the scheduled time at this location. Off-route reports will contain "0" |
|- | |- | ||
|original_loc_timestamp | |original_loc_timestamp | ||
|The planned departure time associated with the original location | |The planned departure time associated with the original location | ||
|- | |- | ||
− | | | + | |current_train_id |
− | | | + | |Where a train has had its identity changed, the current 10-character unique identity for this train |
+ | |- | ||
+ | |delay_monitoring_point | ||
+ | |Set to "true" if this is a delay monitoring point, "false" if it is not. Off-route reports will contain "false" | ||
+ | |- | ||
+ | |next_report_run_time | ||
+ | |The running time to the next location | ||
|- | |- | ||
− | | | + | |reporting_stanox |
− | |The | + | |The STANOX of the location that generated this report. Set to "00000" for manual and off-route reports |
|- | |- | ||
− | | | + | |actual_timestamp |
− | | | + | |The date and time that this event happened at the location |
|- | |- | ||
|correction_ind | |correction_ind | ||
|Set to "false" if this report is not a correction of a previous report, or "true" if it is | |Set to "false" if this report is not a correction of a previous report, or "true" if it is | ||
|- | |- | ||
− | | | + | |event_source |
− | | | + | |Whether the event source was "AUTOMATIC" from SMART, or "MANUAL" from TOPS or TRUST SDR |
|- | |- | ||
− | | | + | |train_file_address |
− | | | + | |The TOPS train file address, if applicable |
− | |||
− | |||
− | |||
|- | |- | ||
|platform | |platform | ||
|Two characters (including a space for a single character) or blank if the movement report is associated with a platform number | |Two characters (including a space for a single character) or blank if the movement report is associated with a platform number | ||
|- | |- | ||
− | | | + | |division_code |
− | | | + | |Operating company ID as per [[TOC Codes]] |
+ | |- | ||
+ | |train_terminated | ||
+ | |Set to "true" if the train has completed its journey, or "false" otherwise | ||
+ | |- | ||
+ | |train_id | ||
+ | |The 10-character unique identity for this train at TRUST activation time | ||
+ | |- | ||
+ | |offroute_ind | ||
+ | |Set to "false" if this report is for a location in the schedule, or "true" if it is not | ||
|- | |- | ||
− | | | + | |variation_status |
− | | | + | |One of "ON TIME", "EARLY", "LATE" or "OFF ROUTE" |
|- | |- | ||
|train_service_code | |train_service_code | ||
|Train service code as per schedule | |Train service code as per schedule | ||
− | |||
− | |||
− | |||
|- | |- | ||
|toc_id | |toc_id | ||
|Operating company ID as per [[TOC Codes]] | |Operating company ID as per [[TOC Codes]] | ||
|- | |- | ||
− | | | + | |loc_stanox |
− | |The | + | |The STANOX of the location at which this event happened |
|- | |- | ||
− | | | + | |auto_expected |
− | | | + | |Set to "true" if an automatic report is expected for this location, otherwise "false" |
|- | |- | ||
− | | | + | |direction_ind |
− | | | + | |For automatic reports, either "UP" or "DOWN" depending on the direction of travel |
|- | |- | ||
− | | | + | |route |
− | | | + | |A single character (or blank) to indicate the exit route from this location |
|- | |- | ||
− | | | + | |planned_event_type |
− | | | + | |The planned type of event - one of "ARRIVAL", "DEPARTURE" or "DESTINATION" |
|- | |- | ||
− | | | + | |next_report_stanox |
− | | | + | |The STANOX of the location at which the next report for this train is due |
|- | |- | ||
− | | | + | |line_ind |
− | | | + | |A single character (or blank) depending on the line the train is travelling on, e.g. F = Fast, S = Slow |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
|- | |- | ||
|} | |} |
Revision as of 16:51, 13 January 2017
Contents
Overview
A train movement message is sent whenever a train arrives, passes or departs a location monitored by TRUST. It records the time at which the event happens.
Reports may be automatically generated, or manually entered.
Data structure
Header
Field | Description |
---|---|
msg_type | Set to '0003' for a movement message |
source_dev_id | Where the movement is manually entered, set to the ID of the device that generated the movement message |
source_system_id | Set to "TRUST" for a movement message |
original_data_source | Set to "TRUST", "TRUST DA", "SDR" or "GPS" for a movement message |
Body
Field | Description |
---|---|
event_type | The type of event - either "ARRIVAL" or "DEPARTURE" |
gbtt_timestamp | The planned GBTT (passenger) date and time that the event was due to happen at this location |
original_loc_stanox | If the location has been revised, the STANOX of the location in the schedule at activation time |
planned_timestamp | The planned date and time that this event was due to happen at this location |
timetable_variation | The number of minutes variation from the scheduled time at this location. Off-route reports will contain "0" |
original_loc_timestamp | The planned departure time associated with the original location |
current_train_id | Where a train has had its identity changed, the current 10-character unique identity for this train |
delay_monitoring_point | Set to "true" if this is a delay monitoring point, "false" if it is not. Off-route reports will contain "false" |
next_report_run_time | The running time to the next location |
reporting_stanox | The STANOX of the location that generated this report. Set to "00000" for manual and off-route reports |
actual_timestamp | The date and time that this event happened at the location |
correction_ind | Set to "false" if this report is not a correction of a previous report, or "true" if it is |
event_source | Whether the event source was "AUTOMATIC" from SMART, or "MANUAL" from TOPS or TRUST SDR |
train_file_address | The TOPS train file address, if applicable |
platform | Two characters (including a space for a single character) or blank if the movement report is associated with a platform number |
division_code | Operating company ID as per TOC Codes |
train_terminated | Set to "true" if the train has completed its journey, or "false" otherwise |
train_id | The 10-character unique identity for this train at TRUST activation time |
offroute_ind | Set to "false" if this report is for a location in the schedule, or "true" if it is not |
variation_status | One of "ON TIME", "EARLY", "LATE" or "OFF ROUTE" |
train_service_code | Train service code as per schedule |
toc_id | Operating company ID as per TOC Codes |
loc_stanox | The STANOX of the location at which this event happened |
auto_expected | Set to "true" if an automatic report is expected for this location, otherwise "false" |
direction_ind | For automatic reports, either "UP" or "DOWN" depending on the direction of travel |
route | A single character (or blank) to indicate the exit route from this location |
planned_event_type | The planned type of event - one of "ARRIVAL", "DEPARTURE" or "DESTINATION" |
next_report_stanox | The STANOX of the location at which the next report for this train is due |
line_ind | A single character (or blank) depending on the line the train is travelling on, e.g. F = Fast, S = Slow |
Network Rail Open Data Feeds | |
---|---|
Data Feeds | About the Feeds • Account States • Durable Subscriptions • Example Code ( PHP / C# / Java / Ruby / Node.js) • 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 • 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 |