PPort Schedule Data

[Chris Holly]

Hi,

I have a few questions that I can't seem to find the answers too so would be greatful for some pointers:

Below is a real Schedule message received 02/11/16 @ ~9.

<?xml version="1.0" encoding="UTF-8"?>

<Pport xmlns="http://www.thalesgroup.com/rtti/PushPort/v12" xmlns:ns2="http://www.thalesgroup.com/rtti/PushPort/Schedules/v1" ts="2016-12-02T20:55:39.4491861Z" version="12.0">

   <uR requestID="0000000000014116" requestSource="at07" updateOrigin="CIS">

      <schedule rid="201612026765212" ssd="2016-12-02" toc="EM" trainCat="XX" trainId="1L18" uid="C65212">

         <ns2:OR act="TB" ptd="19:52" tpl="LVRPLSH" wtd="19:52" />

         <ns2:PP tpl="EDGH" wtp="19:56" />

         <ns2:PP tpl="EDGHSB" wtp="19:56:30" />

         <ns2:PP tpl="WVRTREJ" wtp="19:58" />

         <ns2:IP act="T " pta="20:02" ptd="20:03" tpl="ALERTN" wta="20:02" wtd="20:03" />

         <ns2:PP tpl="HUNTXWJ" wtp="20:04" />

         <ns2:PP tpl="HUNTSX" wtp="20:05:30" />

         <ns2:PP tpl="HALW" wtp="20:06" />

         <ns2:PP tpl="HOUGHGR" wtp="20:08:30" />

         <ns2:IP act="T " pta="20:10" ptd="20:11" tpl="WIDNES" wta="20:10" wtd="20:11" />

         <ns2:PP tpl="SANKEY" wtp="20:15" />

         <ns2:IP act="T " pta="20:18" ptd="20:19" tpl="WRGT" wta="20:18" wtd="20:19" />

         <ns2:PP tpl="BIRCHWD" wtp="20:22:30" />

         <ns2:PP tpl="GLAZBRK" wtp="20:24" />

         <ns2:PP tpl="GLAZBKE" wtp="20:25" />

         <ns2:PP tpl="IRLAM" wtp="20:25:30" />

         <ns2:PP tpl="FLIXTON" wtp="20:28" />

         <ns2:PP tpl="CHASNRD" wtp="20:28:30" />

         <ns2:PP tpl="URMSTON" wtp="20:29" />

         <ns2:PP tpl="HMPHRYP" wtp="20:30" />

         <ns2:PP tpl="TRFDPEJ" wtp="20:32:30" />

         <ns2:PP tpl="CFLDJN" wtp="20:36" />

         <ns2:PP tpl="MNCRDGT" wtp="20:36:30" />

         <ns2:IP act="T " pta="20:39" ptd="20:39" tpl="MNCROXR" wta="20:37:30" wtd="20:39" />

         <ns2:IP act="T " pta="20:41" ptd="20:43" tpl="MNCRPIC" wta="20:41" wtd="20:43" />

         <ns2:PP tpl="ARDWCKJ" wtp="20:45" />

         <ns2:PP tpl="SLDLJN" wtp="20:47" />

         <ns2:PP tpl="LVHM" wtp="20:47:30" />

         <ns2:PP tpl="HTCP" wtp="20:48" />

         <ns2:PP tpl="HTNOJN" wtp="20:49:30" />

         <ns2:IP act="T " pta="20:52" ptd="20:54" tpl="STKP" wta="20:52" wtd="20:54" />

         <ns2:PP tpl="STKPE1" wtp="20:55" />

         <ns2:PP tpl="HAZL" wtp="21:00:30" />

         <ns2:PP tpl="HAZLGHJ" wtp="21:01:30" />

         <ns2:PP tpl="NWMILSJ" wtp="21:06:30" />

         <ns2:PP tpl="CHNLY" wtp="21:09" />

         <ns2:PP tpl="CHNLYNJ" wtp="21:10" />

         <ns2:PP tpl="CHNLYEJ" wtp="21:10:30" />

         <ns2:PP tpl="EDALE" wtp="21:17" />

         <ns2:PP tpl="ERLESDG" wtp="21:19:30" />

         <ns2:PP tpl="HOPD" wtp="21:20" />

         <ns2:PP tpl="BAMFORD" wtp="21:21:30" />

         <ns2:PP tpl="HATHRSG" wtp="21:23" />

         <ns2:PP tpl="GRNDLFD" wtp="21:25:30" />

         <ns2:PP tpl="TOTLYTE" wtp="21:28:30" />

         <ns2:PP tpl="DOREWJ" wtp="21:29" />

         <ns2:PP tpl="DORESNJ" wtp="21:30" />

         <ns2:IP act="T RM" pta="21:35" ptd="21:37" tpl="SHEFFLD" wta="21:35" wtd="21:39" />

         <ns2:PP tpl="DORESNJ" wtp="21:44:30" />

         <ns2:IP act="T " pta="21:49" ptd="21:49" tpl="DRONFLD" wta="21:48:30" wtd="21:49" />

         <ns2:PP tpl="TAPTONJ" wtp="21:53" />

         <ns2:IP act="T " pta="21:54" ptd="21:55" tpl="CHFD" wta="21:54" wtd="21:55" />

         <ns2:PP tpl="CHFDSJ" wtp="21:56:30" />

         <ns2:PP tpl="CLAYXNJ" wtp="21:58:30" />

         <ns2:IP act="T " pta="22:05" ptd="22:05" tpl="ALFRETN" wta="22:04:30" wtd="22:05:30" />

         <ns2:PP tpl="IRNVLJN" wtp="22:09" />

         <ns2:IP act="T " pta="22:12" ptd="22:13" tpl="LGML" wta="22:12" wtd="22:13" />

         <ns2:OPIP act="N " tpl="ILKES" wta="22:17" wtd="22:17:30" />

         <ns2:PP tpl="TRWLJN" wtp="22:21" />

         <ns2:PP tpl="RADFDJ" wtp="22:26:30" />

         <ns2:PP tpl="NTNGMJN" wtp="22:28:30" />

         <ns2:DT act="TF" pta="22:35" tpl="NTNG" wta="22:30" />

      </schedule>

   </uR>

</Pport>

 Questions:

1. Why is there duplicate rows for "DORESNJ" tpl with different wtp values?

2. The attribute "act" I understand stands for activity and is broken into 2 parts however what does "TB", "T ", "T RM", "N ", "TF" mean?

[Peter Hicks (Poggs)]

Hi Chris

On 2 Dec 2016, at 22:06, Chris Holly <chris....@gmail.com> wrote:

1. Why is there duplicate rows for "DORESNJ" tpl with different wtp values?

The rows aren’t duplicate - the train visits this location twice - see below.

2. The attribute "act" I understand stands for activity and is broken into 2 parts however what does "TB", "T ", "T RM", "N ", "TF" mean?

These are documented in the CIF End-User Specification - see http://www.atoc.org/clientfiles/files/RSPS5004%20v27.pdf for an older version where the activities are unchanged:

TB = Train Begins

T = Calls to pick up and set down passengers

RM = Reversing Movement

N = Stop not advertised

The ‘RM’ activity is important here - in the schedule above, the train you’ve quoted reverses at Sheffield and calls at DORESNJ twice.

Peter

[Derek Goodwin]

Looks like this service passes through the DORESNJ tiploc twice, the RM activity code at SHEFFLD stands for reversing movement and so it looks like it goes into there and then reverses out again through DORESNJ again. The activity codes at a location are upto six 2 character codes and are listed in the CIF spec here on page 36. TB is origin, TF is destination, T is stops to pick up and set down and N is non advertised

[Sandro Gržičić]

Hi,

can someone please upload the mentioned PDF (with the full list the "act" activity codes)? I cannot find it anywhere and the latest version of the PDF doesn't contain it

(https://www.raildeliverygroup.com/files/Publications/services/rsp/RSPS5046-01-00_Timetable_Information_Data_Feed_InterfaceSpecification.pdf).

Thank you,

Sandro

[Richard Lamberton]

You need the "CIF End User Interface Specification", if you google this you should find the link to a PDF.

[Guido Eco]

Hi,

You are likely want the "Common Interface File End User Specification version 29" which is available as a googledocs download here. I have also extracted and attached the list of activity codes as a tsv file to this post.

Also, there is a discussion about whether an update to the specification (version 30) is needed to cater for the change of power-unit for the new diesel-electric hybrid Intercity Express Trains run by the Great Western Rail franchise. Albeit that is likely to be an addition rather than a wholesale change to the specification.

Cheers,

G

On Sunday, 11 March 2018 11:07:00 UTC, Sandro Gržičić wrote:

[Peter Hicks (Poggs)]

Hi Guido

On 30 Mar 2018, at 15:09, Guido Eco <gecoop...@gmail.com> wrote:

You are likely want the "Common Interface File End User Specification version 29" which is available as a googledocs download here. I have also extracted and attached the list of activity codes as a tsv file to this post.

Also, there is a discussion about whether an update to the specification (version 30) is needed to cater for the change of power-unit for the new diesel-electric hybrid Intercity Express Trains run by the Great Western Rail franchise. Albeit that is likely to be an addition rather than a wholesale change to the specification.

The issue with the IET is that it can change power type (diesel to electric, and vice versa) at a location that isn’t a stopping point.  As far as I’m aware, the ‘CR’ (change-en-route) activity in CIF has only been published for locations where the train is booked to stop, and the IET will see a CR record occurring for a passing point.

Some IT systems many systems may not be set up to handle a change-en-route at a non-stopping location since it hasn’t ever happened up until now.

Peter

OpenTrainTimes Ltd. registered in England and Wales, company no. 09504022.

Registered office: 13a Davenant Road, Upper Holloway, London N19 3NW