Schedule with passing points that don't match with train status messages

[George Goldberg]

Hi all,

Last night's push port snapshot contained the following schedule. However, I found that the wtp values in the train status messages to do with this schedule didn't match those in this schedule at some of the passing points, picked out in bold below. This is the first time in a week or so of data collection I've seen this happen. Anyone else seen similar behaviour, or have any idea what I might have messed up?

<schedule rid="201509221011696" uid="W83292" trainId="1F01" ssd="2015-09-22" toc="SN" trainCat="XX">
  <sc:OR tpl="EBOURNE" act="TB" ptd="05:08" wtd="05:08" />
  <sc:IP tpl="HMPDNPK" act="T " pta="05:12" ptd="05:12" wta="05:11:30" wtd="05:12" />
  <sc:PP tpl="WILDJN" wtp="05:13" />
  <sc:IP tpl="POLGATE" act="T " pta="05:16" ptd="05:16" wta="05:15:30" wtd="05:16:30" />
  <sc:PP tpl="STHRHMJ" wtp="05:25:30" />
  <sc:IP tpl="LEWES" act="T " pta="05:28" ptd="05:29" wta="05:28" wtd="05:29" />
  <sc:IP tpl="PLMPTON" act="T " pta="05:37" ptd="05:37" wta="05:36:30" wtd="05:37" />
  <sc:PP tpl="KEYMERJ" wtp="05:42:30" />
  <sc:IP tpl="HYWRDSH" act="T " pta="05:46" ptd="05:47" wta="05:46" wtd="05:47" />
  <sc:PP tpl="CPYHLDJ" wtp="05:48:30" />
  <sc:PP tpl="BALCMTJ" wtp="05:53" />
  <sc:IP tpl="THBDGS" act="T " pta="05:55" ptd="05:56" wta="05:55" wtd="05:56" />
  <sc:IP tpl="GTWK" act="T " pta="06:00" ptd="06:01" wta="05:59:30" wtd="06:01" />
  <sc:PP tpl="EARLSWD" wtp="06:05:30" />
  <sc:PP tpl="SNSTJN" wtp="06:11" />
  <sc:PP tpl="PURLEY" wtp="06:11:30" />
  <sc:PP tpl="PURLEYO" wtp="06:12:25" />
  <sc:PP tpl="SCROYDN" wtp="06:13:32" />
  <sc:IP tpl="ECROYDN" act="T " pta="06:15" ptd="06:16" wta="06:15" wtd="06:16" />
  <sc:PP tpl="WNDMLBJ" wtp="06:17" />
  <sc:PP tpl="SELHRST" wtp="06:17:30" />
  <sc:PP tpl="THTH" wtp="06:18:10" />
  <sc:PP tpl="NORBURY" wtp="06:19:14" />
  <sc:PP tpl="STRHCOM" wtp="06:20" />
  <sc:PP tpl="STRENJN" wtp="06:20:30" />
  <sc:PP tpl="BALHJN" wtp="06:21" />
  <sc:PP tpl="BALHAM" wtp="06:21:30" />
  <sc:PP tpl="WANDCMN" wtp="06:22:35" />
  <sc:IP tpl="CLPHMJC" act="T " pta="06:25" ptd="06:25" wta="06:24:30" wtd="06:25:30" />
  <sc:DT tpl="VICTRIC" act="TF" pta="06:32" wta="06:32" />
</schedule>

George

[Peter Hicks]

Hi George

Those pass times look bogus.  I'll follow it up for you - as I understand it, the times can only by :00 or :30.

Peter

--
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-t...@googlegroups.com.
To post to this group, send email to openrail...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Peter Hicks]

George,

I've had a look back through historical messages, and this looks like a non-isolated incident, which I've reported through the right channels.

I'll let you know when I hear back.

Thanks for spotting this and raising it!

Kind regards,

Peter

[Peter Hicks]

Hi George

I've heard back.  I'm told this is expected behaviour if the passing point has been added by a CIS.  However, I'm not entirely sure this is correct - weren't you seeing these come in for the schedules in the timetable snapshot itself...?

Peter

[George Goldberg]

On 27 September 2015 at 21:11, Peter Hicks <peter...@poggs.co.uk> wrote:

I've heard back.  I'm told this is expected behaviour if the passing point has been added by a CIS.  However, I'm not entirely sure this is correct - weren't you seeing these come in for the schedules in the timetable snapshot itself...?

Assuming what you are referring to as the timetable snapshot is the file that turns up each night in the snapshots subdirectory of the ftp server, then yes, I was seeing them in there. The example in the first email of this thread was actually copied directly from that night's snapshot file.

George