Darwin Staff Missing Data

[Alexander MacLeod]

Dear all,

I am attempting to download the arrivals from a filtered station board using the LDBWS Staff Version. For example, I searched for arrivals at London Euston calling at Manchester Piccadilly which returned:

<GetBoardResult xmlns:t5="http://thalesgroup.com/RTTI/2012-01-13/ldbsv/types" xmlns:c1="http://thalesgroup.com/RTTI/2007-10-10/ldb/commontypes" xmlns:t7="http://thalesgroup.com/RTTI/2015-05-14/ldbsv/types" xmlns:t3="http://thalesgroup.com/RTTI/2010-07-07/ldbsv/types" xmlns:c4="http://thalesgroup.com/RTTI/2016-02-16/ldbsv/commontypes" xmlns:c5="http://thalesgroup.com/RTTI/2017-02-02/ldbsv/commontypes" xmlns:t1="http://thalesgroup.com/RTTI/2008-10-24/ldbsv/types" xmlns:t="http://thalesgroup.com/RTTI/2007-10-10/ldbsv/types" xmlns:t10="http://thalesgroup.com/RTTI/2016-02-16/ldbsv/types" xmlns:t2="http://thalesgroup.com/RTTI/2010-04-26/ldbsv/types" xmlns:t6="http://thalesgroup.com/RTTI/2014-02-20/ldbsv/types" xmlns:t9="http://thalesgroup.com/RTTI/2015-11-27/ldbsv/types" xmlns:t4="http://thalesgroup.com/RTTI/2011-10-31/ldbsv/types" xmlns:c3="http://thalesgroup.com/RTTI/2015-11-27/ldbsv/commontypes" xmlns:t8="http://thalesgroup.com/RTTI/2015-09-09/ldbsv/types" xmlns:c2="http://thalesgroup.com/RTTI/2010-11-01/ldb/commontypes" xmlns:t11="http://thalesgroup.com/RTTI/2017-02-02/ldbsv/types">

                 <t6:generatedAt>2018-05-09T19:45:46.3408555+01:00</t6:generatedAt>

                              <t6:locationName>London Euston</t6:locationName>

                              <t6:crs>EUS</t6:crs>

                              <t6:filterLocationName>Manchester Piccadilly</t6:filterLocationName>

                              <t6:filtercrs>MAN</t6:filtercrs>

                              <t6:stationManager>Network Rail</t6:stationManager>

                              <t6:stationManagerCode>RT</t6:stationManagerCode>

                              <t6:nrccMessages>

                                      <t5:message>

                                              <t5:category>Train service</t5:category>

                                              <t5:severity>Minor</t5:severity>

                                              <t5:xhtmlMessage>Disruption between Chester and Crewe due to a section of defective track on the line towards Crewe. More information can be found in &lt;A href=&quot;http://nationalrail.co.uk/service_disruptions/190734.aspx &quot;&gt;Latest Travel News&lt;/A&gt;.</t5:xhtmlMessage>

                                      </t5:message>

                              </t6:nrccMessages>

                              <t10:qos>-1</t10:qos>

                      </GetBoardResult>

This implies there are no services but the official National Rail app suggests otherwise:

Would someone be able to provide me with an update on this issue? 

Many thanks,

Alexander

[Rail Delivery Group]

The NRE app uses the same LDBSV web service as you are using. You've not included your request but I think I can guess what you may have done. A correct request is of the form:

      <ldb:GetArrivalBoardByCRSRequest>
         <ldb:numRows>5</ldb:numRows>
         <ldb:crs>EUS</ldb:crs>
         <ldb:time>2018-05-10T08:45:00</ldb:time>
         <ldb:timeWindow>120</ldb:timeWindow>
         <ldb:filtercrs>MAN</ldb:filtercrs>
         <ldb:filterType>from</ldb:filterType>
      </ldb:GetArrivalBoardByCRSRequest>

I can replicate the results you get by setting the filterType to 'to' instead of 'from'. This returns no results as there are no services which arrive into Euston which are travelling to Manchester (or indeed anywhere else!). Services which come into Euston arrive from Manchester and depart to Manchester so the correct filterType would be 'from'.

Note: the 'to' option can be used with arrivals when the specified filter station is later in a schedule. So in the above example, replacing EUS with MKC and filterType with 'to' will provide results as there are services which arrive into MKC that go on to call at MAN. The problem with EUS of course is that as a terminal station there will never be any stations later in the schedule so the 'to' filterType for arrivals has no meaning.

[Alexander MacLeod]

That's great, thank you! I wish there was a way to receive both from and to at once though.

Kind regards,

Alexander