Odd push port data for CROY today

[Andrew Langmead]

Hi 

I've seen a fairly weird record today from the Push Port.  Look at CROY (all three of them) in the message below:

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

<Pport xmlns="http://www.thalesgroup.com/rtti/PushPort/v12"

       xmlns:ns3="http://www.thalesgroup.com/rtti/PushPort/Forecasts/v2" ts="2015-09-07T06:46:35.6366222+01:00"

       version="12.0">

    <uR updateOrigin="Tyrell">

        <TS rid="201509070553510" ssd="2015-09-07" uid="G86142">

            <ns3:LateReason>179</ns3:LateReason>

            <ns3:Location ptd="07:00" tpl="GLGQHL" wtd="07:00">

                <ns3:dep et="07:00" src="Darwin"/>

                <ns3:plat cisPlatsup="true" platsup="true">6</ns3:plat>

            </ns3:Location>

            <ns3:Location tpl="CWLRSSJ" wtp="07:03">

                <ns3:pass et="07:03" src="Darwin"/>

            </ns3:Location>

            <ns3:Location tpl="CWLRSWJ" wtp="07:03:30">

                <ns3:pass et="07:03" src="Darwin"/>

            </ns3:Location>

            <ns3:Location tpl="BSHB" wtp="07:05">

                <ns3:pass et="07:05" src="Darwin"/>

                <ns3:plat cisPlatsup="true" platsrc="A" platsup="true">1</ns3:plat>

            </ns3:Location>

            <ns3:Location pta="07:08" ptd="07:08" tpl="LENZIE" wta="07:08" wtd="07:08:30">

                <ns3:arr et="07:08" src="Darwin"/>

                <ns3:dep et="07:08" src="Darwin"/>

                <ns3:plat>1</ns3:plat>

            </ns3:Location>

            <ns3:Location pta="07:09" ptd="07:09" tpl="CROY" wta="07:09" wtd="07:09">

                <ns3:arr et="07:09" src="Darwin" wet="07:08"/>

                <ns3:dep et="07:09" src="Darwin"/>

                <ns3:plat cisPlatsup="true" platsup="true">1</ns3:plat>

            </ns3:Location>

            <ns3:Location pta="07:13" ptd="07:13" tpl="CROY" wta="07:13" wtd="07:13">

                <ns3:arr et="07:13" src="Darwin" wet="07:12"/>

                <ns3:dep et="07:13" src="Darwin"/>

            </ns3:Location>

            <ns3:Location tpl="CROY" wtp="07:13:30">

                <ns3:pass et="07:13" src="Darwin"/>

                <ns3:plat cisPlatsup="true" platsup="true">1</ns3:plat>

            </ns3:Location>

            <ns3:Location tpl="GNHLUJN" wtp="07:17">

                <ns3:pass et="07:17" src="Darwin"/>

            </ns3:Location>

            <ns3:Location pta="07:21" ptd="07:21" tpl="FALKRKH" wta="07:20:30" wtd="07:21:30">

                <ns3:arr et="07:21" src="Darwin" wet="07:20"/>

                <ns3:dep et="07:21" src="Darwin"/>

                <ns3:plat>1</ns3:plat>

            </ns3:Location>

            <ns3:Location pta="07:26" ptd="07:26" tpl="POLMONT" wta="07:25:30" wtd="07:26">

                <ns3:arr et="07:26" src="Darwin" wet="07:25"/>

                <ns3:dep et="07:26" src="Darwin"/>

                <ns3:plat>1</ns3:plat>

            </ns3:Location>

            <ns3:Location pta="07:32" ptd="07:32" tpl="LNLTHGW" wta="07:31:30" wtd="07:32:30">

                <ns3:arr et="07:32" src="Darwin" wet="07:31"/>

                <ns3:dep et="07:32" src="Darwin"/>

                <ns3:plat>1</ns3:plat>

            </ns3:Location>

            <ns3:Location tpl="WNCBROJ" wtp="07:37:30">

                <ns3:pass et="07:37" src="Darwin"/>

            </ns3:Location>

            <ns3:Location tpl="NWBG" wtp="07:40:30">

                <ns3:pass et="07:40" src="Darwin"/>

            </ns3:Location>

            <ns3:Location tpl="HAYMRWJ" wtp="07:47">

                <ns3:pass et="07:44" src="Darwin"/>

            </ns3:Location>

            <ns3:Location tpl="HAYMRCJ" wtp="07:48">

                <ns3:pass et="07:45" src="Darwin"/>

            </ns3:Location>

            <ns3:Location pta="07:50" tpl="HAYMRKT" wta="07:49:30" wtd="07:50:30">

                <ns3:arr et="07:50" src="Darwin" wet="07:46"/>

                <ns3:dep src="Darwin" wet="07:47"/>

                <ns3:plat>1</ns3:plat>

            </ns3:Location>

            <ns3:Location tpl="PRNCSTG" wtp="07:53">

                <ns3:pass et="07:49" src="Darwin"/>

            </ns3:Location>

            <ns3:Location pta="07:55" tpl="EDINBUR" wta="07:55">

                <ns3:arr et="07:55" src="Darwin" wet="07:51"/>

                <ns3:plat>11</ns3:plat>

            </ns3:Location>

        </TS>

    </uR>

</Pport>

Does anyone have any feelings about how this sort of data should be handled?  On the face of it it looks wrong to me.

Thanks

Andrew

[Andrew Langmead]

Similar strange data (though not quite so off the wall) here around POLMONT and LNLTHGW.  There's passing and calling point data for each in this message.

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

<Pport xmlns="http://www.thalesgroup.com/rtti/PushPort/v12"

       xmlns:ns3="http://www.thalesgroup.com/rtti/PushPort/Forecasts/v2" ts="2015-09-07T12:03:15.3371096+01:00"

       version="12.0">

    <uR updateOrigin="Tyrell">

        <TS rid="201509070553934" ssd="2015-09-07" uid="G91200">

            <ns3:LateReason>153</ns3:LateReason>

            <ns3:Location ptd="12:00" tpl="GLGQHL" wtd="12:00">

                <ns3:dep at="12:00" src="TD"/>

                <ns3:plat platsrc="M">7</ns3:plat>

            </ns3:Location>

            <ns3:Location tpl="CWLRSSJ" wtp="12:03">

                <ns3:pass et="12:03" src="Darwin"/>

            </ns3:Location>

            <ns3:Location tpl="CWLRSWJ" wtp="12:03:30">

                <ns3:pass et="12:03" src="Darwin"/>

            </ns3:Location>

            <ns3:Location tpl="BSHB" wtp="12:05">

                <ns3:pass et="12:05" src="Darwin"/>

                <ns3:plat cisPlatsup="true" platsrc="A" platsup="true">1</ns3:plat>

            </ns3:Location>

            <ns3:Location tpl="LENZIE" wtp="12:07:30">

                <ns3:pass et="12:07" src="Darwin"/>

                <ns3:plat cisPlatsup="true" platsrc="A" platsup="true">1</ns3:plat>

            </ns3:Location>

            <ns3:Location pta="12:12" ptd="12:12" tpl="CROY" wta="12:11:30" wtd="12:12">

                <ns3:arr et="12:12" src="Darwin" wet="12:11"/>

                <ns3:dep et="12:12" src="Darwin"/>

                <ns3:plat>1</ns3:plat>

            </ns3:Location>

            <ns3:Location tpl="GNHLUJN" wtp="12:17:30">

                <ns3:pass et="12:17" src="Darwin"/>

            </ns3:Location>

            <ns3:Location pta="12:21" ptd="12:22" tpl="FALKRKH" wta="12:21" wtd="12:22">

                <ns3:arr et="12:21" src="Darwin"/>

                <ns3:dep et="12:22" src="Darwin"/>

                <ns3:plat>1</ns3:plat>

            </ns3:Location>

            <ns3:Location pta="12:25" ptd="12:25" tpl="POLMONT" wta="12:25" wtd="12:25">

                <ns3:arr et="12:25" src="Darwin"/>

                <ns3:dep et="12:25" src="Darwin"/>

                <ns3:plat platsup="true">1</ns3:plat>

            </ns3:Location>

            <ns3:Location tpl="POLMONT" wtp="12:25:30">

                <ns3:pass et="12:25" src="Darwin"/>

                <ns3:plat cisPlatsup="true" platsrc="A" platsup="true">1</ns3:plat>

            </ns3:Location>

            <ns3:Location tpl="LNLTHGW" wtp="12:29">

                <ns3:pass et="12:29" src="Darwin"/>

                <ns3:plat cisPlatsup="true" platsup="true">1</ns3:plat>

            </ns3:Location>

            <ns3:Location pta="12:29" ptd="12:29" tpl="LNLTHGW" wta="12:29" wtd="12:29">

                <ns3:arr et="12:29" src="Darwin"/>

                <ns3:dep et="12:29" src="Darwin"/>

                <ns3:plat platsup="true">1</ns3:plat>

            </ns3:Location>

            <ns3:Location tpl="WNCBROJ" wtp="12:33">

                <ns3:pass et="12:33" src="Darwin"/>

            </ns3:Location>

            <ns3:Location tpl="NWBG" wtp="12:36">

                <ns3:pass et="12:36" src="Darwin"/>

            </ns3:Location>

            <ns3:Location tpl="HAYMRWJ" wtp="12:42:30">

                <ns3:pass et="12:42" src="Darwin"/>

            </ns3:Location>

            <ns3:Location pta="12:45" tpl="HAYMRKT" wta="12:45:30" wtd="12:46:30">

                <ns3:arr et="12:45" src="Darwin"/>

                <ns3:dep src="Darwin" wet="12:46"/>

                <ns3:plat>3</ns3:plat>

            </ns3:Location>

            <ns3:Location tpl="PRNCSTG" wtp="12:49">

                <ns3:pass et="12:48" src="Darwin"/>

            </ns3:Location>

            <ns3:Location pta="12:52" tpl="EDINBUR" wta="12:51">

                <ns3:arr et="12:52" src="Darwin" wet="12:50"/>

                <ns3:plat>7</ns3:plat>

[Peter Hicks]

Hi Andrew

This is the 0700 Glasgow Queen Street - Edinburgh, which has a passing time at Croy of 0713H (07:13:30).  This is the final instance of Croy.

I'm not entirely sure what happened, but Darwin itself is showing three calls at Croy - a pass at 07:13:30, but also a call at Croy at 07:13, but then a cancellation at Croy at 07:09.

It looks like there was a Tyrell message around 0645 this morning that caused things to go wrong - so this looks like a problem with Darwin itself.

I will get this raised as a possible bug - congratulations :-)

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.

[Andrew Langmead]

Hi Peter

Do I get a prize? :)

Do you feel the second examples are a result of a similar problem or should I be handling that data in some way?

Many thanks as ever for your assistance.

Kind regards,

Andrew

[Peter Hicks]

Hi Andrew

It appears this is a known defect in Darwin, which is being fixed in the next release.

I'll let you know when I hear back about a fix.  In the meantime, it's a good idea to be consistent with Darwin (as per the T&Cs) and just display the data verbatim, rather than trying to work around it.

Peter

[Andrew Langmead]

Hi Peter

 

Thanks very much for your help and the information.

 

 

 

Andrew

 

 

 

 

Andrew Langmead
Software Team Manager
Nexus Alpha Limited
Email: andrew....@nexusalpha.com
Tel: 020 7652 2051
Fax: 020 7622 6817
Mobile: 07989 605 646
Web: www.nexusalpha.com
London House, 7-11 Prescott Place, Clapham, London SW4 6BS
____________________________________________________________________________
Nexus Alpha Limited Registered Office London House, 7-11 Prescott Place, Clapham,

London SW4 6BS. Registered in England, No 2941132.  The information transmitted is

confidential and may be privileged.  It is intended for use only by the addressee and may

not be dealt with in any way by any other person.  If you have received it in error, please

destroy all copies and contact the sender immediately.  Nexus Alpha Limited accepts no

liability for changes made to this message after it has been sent.
____________________________________________________________________________

[Peter Hicks]

All,

I've had feedback about this bug - a fix is planned for Darwin 3.7.

I'm not sure when the release for this scheduled for, but there will be a separate communication about that when it's due to go live.

Kind regards,

Peter

[petermount]

That'll be good as I've been seeing t

[Andrew Langmead]

Hi Peter

 

Many thanks for the update – much appreciated.