Darwin:Tracking ID corrections: Difference between revisions

From Open Rail Data Wiki
Q (talk | contribs)
m Added category
EvelynSnow (talk | contribs)
Add example for TD tracking ID corrections
 
Line 6: Line 6:


These messages are sent not included in the snapshot, and are published once, when the corrected headcode is known to Darwin.
These messages are sent not included in the snapshot, and are published once, when the corrected headcode is known to Darwin.
== Examples (v16) ==
<pre><Pport... xmlns:ns10="http://www.thalesgroup.com/rtti/PushPort/TDData/v1" ...>
  <uR updateOrigin="CIS" requestSource="AM07" requestID="AM07278321">
    <trackingID>
      <ns10:berth area="AW">GB09</ns10:berth>
      <ns10:incorrectTrainID>2N13</ns10:incorrectTrainID>
      <ns10:correctTrainID>2N14</ns10:correctTrainID>
    </trackingID>
  </uR>
</Pport></pre>


[[Category:National Rail Enquiries Data Feeds]]
[[Category:National Rail Enquiries Data Feeds]]

Latest revision as of 09:57, 17 January 2023

Overview

Tracking ID corrections are messages that are provided by Darwin to correct headcodes that have been reported incorrectly by TD.NET.

Detail

The tracking ID message contains the TD berth where the train is currently expected to be. It also contains the original incorrect headcode, and the correct headcode.

These messages are sent not included in the snapshot, and are published once, when the corrected headcode is known to Darwin.

Examples (v16)

<Pport... xmlns:ns10="http://www.thalesgroup.com/rtti/PushPort/TDData/v1" ...>
  <uR updateOrigin="CIS" requestSource="AM07" requestID="AM07278321">
    <trackingID>
      <ns10:berth area="AW">GB09</ns10:berth>
      <ns10:incorrectTrainID>2N13</ns10:incorrectTrainID>
      <ns10:correctTrainID>2N14</ns10:correctTrainID>
    </trackingID>
  </uR>
</Pport>