Change of Location: Difference between revisions

From Open Rail Data Wiki
Jpl (talk | contribs)
Change of Location
mNo edit summary
 
(3 intermediate revisions by one other user not shown)
Line 4: Line 4:


== Data structure ==
== Data structure ==
<pre>
{
    "header": {
        "msg_type": "0008",
        "source_dev_id": "VNHY",
        "user_id": "#PEE0031",
        "original_data_source": "TOPS",
        "msg_queue_timestamp": "1511532209000",
        "source_system_id": "TRUST"
    },
    "body": {
        "original_loc_timestamp": "1511528640000",
        "current_train_id": "",
        "train_file_address": "BDI",
        "train_service_code": "56461882",
        "dep_timestamp": "1511528640000",
        "loc_stanox": "36108",
        "train_id": "174M37CF24",
        "original_loc_stanox": "36169",
        "event_timestamp": "1511532180000"
    }
}
</pre>
In the example above, the train scheduled to call at Stanox 36169 (Tuebrook Sdgs Gbrf) will now call at Stanox 36108 (Liverpool Biomass Tml Gbf).


=== Header ===
=== Header ===
Line 15: Line 41:
|-
|-
|source_dev_id
|source_dev_id
|Set to the ID of the device that issued the change of location message
|[[LATA]] or [[CICS Session]] of the inputting terminal
|-
|-
|user_id
|user_id
|
|[[NCI signon]] of the inputting user
|-
|-
|original_data_source
|original_data_source
Line 43: Line 69:
|-
|-
|dep_timestamp
|dep_timestamp
|The planned departure time at the location where the train will call
|The planned arrival/departure time at the location where the train will call
|-
|-
|loc_stanox
|loc_stanox
Line 52: Line 78:
|-
|-
|original_loc_timestamp
|original_loc_timestamp
|The planned departure time associated with the original location
|The planned arrival/departure time associated with the original location
|-
|-
|train_service_code
|train_service_code

Latest revision as of 16:53, 10 December 2018

Overview

When a train is calling a location other than the location in the schedule, a change of location message will be sent.

Data structure

{
    "header": {
        "msg_type": "0008",
        "source_dev_id": "VNHY",
        "user_id": "#PEE0031",
        "original_data_source": "TOPS",
        "msg_queue_timestamp": "1511532209000",
        "source_system_id": "TRUST"
    },
    "body": {
        "original_loc_timestamp": "1511528640000",
        "current_train_id": "",
        "train_file_address": "BDI",
        "train_service_code": "56461882",
        "dep_timestamp": "1511528640000",
        "loc_stanox": "36108",
        "train_id": "174M37CF24",
        "original_loc_stanox": "36169",
        "event_timestamp": "1511532180000"
    }
}

In the example above, the train scheduled to call at Stanox 36169 (Tuebrook Sdgs Gbrf) will now call at Stanox 36108 (Liverpool Biomass Tml Gbf).

Header

Field Description
msg_type Set to '0008' for an change of location message
source_dev_id LATA or CICS Session of the inputting terminal
user_id NCI signon of the inputting user
original_data_source Set to "TOPS" for a change of location message
msg_queue_timestamp
source_system_id Set to "TRUST" for a change of location message

Body

Field Description
train_id The 10-character unique identity for this train at TRUST activation time
current_train_id
dep_timestamp The planned arrival/departure time at the location where the train will call
loc_stanox The STANOX of the new calling point of the train
original_loc_stanox The STANOX of the original location in the schedule
original_loc_timestamp The planned arrival/departure time associated with the original location
train_service_code Train service code as per schedule
train_file_address The TOPS train file address, if applicable
event_timestamp The time at which the Change of Location is entered into TRUST


Network Rail Open Data Feeds
Data Feeds About the Feeds Account States Durable Subscriptions Example Code ( PHP / C# / Java / Ruby / Node.js) • Advanced UsesFAQ 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)