Darwin Schedule Update

94 views
Skip to first unread message

Lee Fortnam

unread,
Sep 26, 2017, 4:19:52 PM9/26/17
to A gathering place for the Open Rail Data community
Hi All,

Hoping someone can help with a very simple question:

Train 201709267662679 has a schedule update issued in the pPortData.log.2017-09-26-21-06 file this evening with the XML showing below. My question is as follows, with a cancel reason of 100 in the last few lines does this INDICATE the entire train was cancelled as none of the ns2_OR/IP/DT nodes have the can="true" attribute but also there are no aat or dat values.

Thanks in advance,

Lee

<?xml version="1.0" encoding="UTF-8"?>
<Pport
xmlns:ns2="http://www.thalesgroup.com/rtti/PushPort/Schedules/v1" ts="2017-09-26T21:09:22.1901307+01:00" version="12.0">
<uR updateOrigin="Workstation">
<schedule rid="201709267662679" ssd="2017-09-26" toc="LO" trainId="2N08" uid="L62679">
<ns2_OR act="TB" ptd="19:27" tpl="RICHNLL" wtd="19:27"/>
<ns2_IP act="T " pta="19:30" ptd="19:30" tpl="KEWGRDN" wta="19:30" wtd="19:30:30"/>
<ns2_IP act="T " pta="19:33" ptd="19:33" tpl="GNRSBRY" wta="19:33" wtd="19:33:30"/>
<ns2_PP tpl="SACTONJ" wtp="19:34:53"/>
<ns2_IP act="T " pta="19:36" ptd="19:36" tpl="SACTON" wta="19:35:30" wtd="19:36"/>
<ns2_IP act="T " pta="19:38" ptd="19:39" tpl="ACTNCTL" wta="19:38" wtd="19:39"/>
<ns2_PP tpl="ACWLJN" wtp="19:41"/>
<ns2_IP act="T " pta="19:44" ptd="19:44" tpl="WLSDJHL" wta="19:43:30" wtd="19:45:30"/>
<ns2_PP tpl="KENSLGJ" wtp="19:46:30"/>
<ns2_IP act="T " pta="19:46" ptd="19:46" tpl="KENR" wta="19:47:30" wtd="19:48"/>
<ns2_IP act="T " pta="19:48" ptd="19:48" tpl="BRBYPK" wta="19:49:30" wtd="19:50"/>
<ns2_IP act="T " pta="19:50" ptd="19:50" tpl="BRBY" wta="19:51" wtd="19:51:30"/>
<ns2_IP act="T " pta="19:52" ptd="19:52" tpl="WHMDSTD" wta="19:53" wtd="19:53:30"/>
<ns2_IP act="T " pta="19:53" ptd="19:53" tpl="FNCHLYR" wta="19:54:30" wtd="19:55"/>
<ns2_IP act="T " pta="19:56" ptd="19:56" tpl="HMPSTDH" wta="19:57" wtd="19:57:30"/>
<ns2_IP act="T " pta="19:58" ptd="20:00" tpl="GOSPLOK" wta="19:59:30" wtd="20:00:30"/>
<ns2_IP act="T " pta="20:02" ptd="20:02" tpl="KNTSHTW" wta="20:02" wtd="20:02:30"/>
<ns2_PP tpl="CMDNRDJ" wtp="20:05"/>
<ns2_IP act="T " pta="20:06" ptd="20:06" tpl="CMDNRD" wta="20:05:30" wtd="20:06"/>
<ns2_PP tpl="CMDNREJ" wtp="20:07"/>
<ns2_IP act="T " pta="20:09" ptd="20:09" tpl="CLDNNRB" wta="20:08:30" wtd="20:09"/>
<ns2_PP tpl="WSBRNRJ" wtp="20:10"/>
<ns2_IP act="T " pta="20:11" ptd="20:12" tpl="HIGHBYA" wta="20:10:30" wtd="20:12"/>
<ns2_PP tpl="CNNBYWJ" wtp="20:13"/>
<ns2_IP act="T " pta="20:14" ptd="20:14" tpl="CNNB" wta="20:13:30" wtd="20:14"/>
<ns2_IP act="T " pta="20:16" ptd="20:16" tpl="DALSKLD" wta="20:15:30" wtd="20:16"/>
<ns2_PP tpl="NAVRDJ" wtp="20:17"/>
<ns2_IP act="T " pta="20:18" ptd="20:18" tpl="HACKNYC" wta="20:17:30" wtd="20:18"/>
<ns2_IP act="T " pta="20:20" ptd="20:20" tpl="HOMRTON" wta="20:19:30" wtd="20:20"/>
<ns2_IP act="T " pta="20:22" ptd="20:22" tpl="HACKNYW" wta="20:22" wtd="20:22:30"/>
<ns2_PP tpl="LEAJ" wtp="20:23:30"/>
<ns2_PP tpl="CHNELSJ" wtp="20:24"/>
<ns2_DT act="TF" pta="20:28" tpl="STFD" wta="20:28"/>
<ns2_cancelReason>100</ns2_cancelReason>
</schedule>
</uR>
</Pport>

petermount

unread,
Sep 26, 2017, 5:53:54 PM9/26/17
to A gathering place for the Open Rail Data community
odd as I got movement for that one.


Could have been cancelled then reinstated? I do just show both reasons when they are there.

Rail Delivery Group

unread,
Sep 27, 2017, 5:29:44 AM9/27/17
to A gathering place for the Open Rail Data community
Hi,

The presence of a cancellation reason code does not infer the train or any of its stops are cancelled, that is determined on a location by location basis by the 'can' attribute - if a location's can attribute is true then the reason that location has been cancelled can be determined from the reason code, if one is supplied.

That said, there probably shouldn't be a cancel reason code on a schedule if none of the locations are cancelled. It's a right side failure in that it can simply be ignored but technically it shouldn't be there as it serves no purpose.

RDG

Lee Fortnam

unread,
Sep 28, 2017, 8:28:58 AM9/28/17
to Rail Delivery Group, A gathering place for the Open Rail Data community
Thanks for the responses, only just got back to this one.

Much appreciated.

--
You received this message because you are subscribed to the Google Groups "A gathering place for the Open Rail Data community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openraildata-talk+unsubscribe@googlegroups.com.
To post to this group, send email to openraildata-talk@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply all
Reply to author
Forward
0 new messages