Darwin 'TS.Location.suppr' attribute

72 views
Skip to first unread message

WantStuff

unread,
May 10, 2018, 6:06:21 PM5/10/18
to A gathering place for the Open Rail Data community
Hi All,

Could someone explain Darwin's 'suppr' attribute?

The description says "The service is suppressed at this location", but I have found suppressed locations with a public activity, public times, platform, etc.
So what does 'suppressed' really mean? Is the train available to the public at this location? What actually is suppressed?


For example...

<Pport xmlns="http://www.thalesgroup.com/rtti/PushPort/v12" xmlns:ns2="http://www.thalesgroup.com/rtti/PushPort/Schedules/v1" ts="2018-04-06T02:56:32.4293165+01:00" version="12.0">
<uR requestID="0000000000000925" requestSource="at38" updateOrigin="CIS">
<schedule rid="201804076790379" ssd="2018-04-07" toc="CH" trainCat="XX" trainId="1T77" uid="C90379">
<ns2:OR act="TB" ptd="00:10" tpl="MARYLBN" wtd="00:10"/>
<ns2:PP tpl="NEASDSJ" wtp="00:17"/>
<ns2:PP tpl="WEMBLSM" wtp="00:18"/>
<ns2:PP tpl="NTHOPKJ" wtp="00:21"/>
<ns2:PP tpl="SRUISLP" wtp="00:22:30"/>
<ns2:PP tpl="WRUISLP" wtp="00:24"/>
<ns2:PP tpl="GERRDSX" wtp="00:29"/>
<ns2:IP act="T " pta="00:39" ptd="00:40" tpl="HWYCOMB" wta="00:39" wtd="00:40"/>
<ns2:PP tpl="SUNDRTN" wtp="00:45:30"/>
<ns2:PP tpl="PRINRIS" wtp="00:48"/>
<ns2:PP tpl="HADMATP" wtp="00:52:30"/>
<ns2:PP tpl="BCSTSJ" wtp="01:03:30"/>
<ns2:PP tpl="BCSTGJN" wtp="01:05"/>
<ns2:IP act="T " pta="01:06" ptd="01:07" tpl="BCSTRTN" wta="01:06" wtd="01:07"/>
<ns2:IP act="T " pta="01:15" ptd="01:15" tpl="OXFPWAY" wta="01:14:30" wtd="01:15"/>
<ns2:PP tpl="OXFDWRJ" wtp="01:17"/>
<ns2:PP tpl="OXFDNNJ" wtp="01:19"/>
<ns2:DT act="TF" pta="01:24" tpl="OXFD" wta="01:24"/>
</schedule>
</uR>
</Pport>

<Pport xmlns="http://www.thalesgroup.com/rtti/PushPort/v12" xmlns:ns3="http://www.thalesgroup.com/rtti/PushPort/Forecasts/v2" ts="2018-04-07T00:10:17.8346302+01:00" version="12.0">
<uR updateOrigin="TD">
<TS rid="201804076790379" ssd="2018-04-07" uid="C90379">
<ns3:Location ptd="00:10" tpl="MARYLBN" wtd="00:10">
<ns3:dep at="00:09" src="TD"/>
<ns3:plat platsrc="M" platsup="true">4</ns3:plat>
<ns3:suppr>true</ns3:suppr>
<ns3:length>2</ns3:length>
</ns3:Location>
<ns3:Location tpl="NEASDSJ" wtp="00:17">
<ns3:pass et="00:16" src="Darwin"/>
<ns3:length>2</ns3:length>
</ns3:Location>
<ns3:Location tpl="WEMBLSM" wtp="00:18">
<ns3:pass et="00:17" src="Darwin"/>
<ns3:plat platsrc="M" platsup="true">2</ns3:plat>
<ns3:length>2</ns3:length>
</ns3:Location>
<ns3:Location tpl="NTHOPKJ" wtp="00:21">
<ns3:pass et="00:20" src="Darwin"/>
<ns3:length>2</ns3:length>
</ns3:Location>
<ns3:Location tpl="WRUISLP" wtp="00:24">
<ns3:pass et="00:23" src="Darwin"/>
<ns3:plat platsrc="M" platsup="true">3</ns3:plat>
<ns3:length>2</ns3:length>
</ns3:Location>
<ns3:Location tpl="GERRDSX" wtp="00:29">
<ns3:pass et="00:28" src="Darwin"/>
<ns3:plat platsrc="M" platsup="true">1</ns3:plat>
<ns3:length>2</ns3:length>
</ns3:Location>
<ns3:Location pta="00:39" ptd="00:40" tpl="HWYCOMB" wta="00:39" wtd="00:40">
<ns3:arr et="00:39" src="Darwin" wet="00:36"/>
<ns3:dep et="00:40" src="Darwin"/>
<ns3:plat platsrc="M">2</ns3:plat>
<ns3:length>2</ns3:length>
</ns3:Location>
</TS>
</uR>
</Pport>



Thanks,
Martin

petermount

unread,
May 11, 2018, 5:38:11 AM5/11/18
to A gathering place for the Open Rail Data community
It means it should not be displayed to the public.

Usual reasons like for Marlybone or for me London Victoria is that the platform's aren't displayed until it's actually known what platform the train will be on. Quite often they can change at the last minute so it limits the risk of people being on the wrong platform etc.

Peter Hicks

unread,
May 11, 2018, 5:49:38 AM5/11/18
to petermount, A gathering place for the Open Rail Data community
Isn't that the purpose of the platSup and cisPlatSup flags?

Looking at the timestamp on the message, it looks like it's to suppress display of the train because it's very close to departure time - the "train doors close 30 seconds before departure" thing.


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.


OpenTrainTimes Ltd. registered in England and Wales, company no. 09504022.
Registered office: 13a Davenant Road, Upper Holloway, London N19 3NW

WantStuff

unread,
May 11, 2018, 11:39:06 AM5/11/18
to A gathering place for the Open Rail Data community
As Peter H says, I’m not sure that this is platform related as I have seen the platSupp properties separately.
However it probably is of a similar concept so I believe you are on the right track (no pun intended).

The description says "The *service* is suppressed at this location" but it still gives a public ‘pickup’ activity.
I can’t fathom why the whole service (and several others) would be suppressed from public view so close to departure.

Martin

Rail Delivery Group

unread,
May 14, 2018, 5:54:10 AM5/14/18
to A gathering place for the Open Rail Data community
There is a difference between platform suppressions and suppression as noted above. Platform suppression hides the platform from the public as the operator is not yet ready to display it (still preparing the train for customers etc.) - there are two variants for some reason relating to CIS which I can't quite recall right now.

The suppression asked about above relates to suppressing the service from display at the relevant location(s). This is done as part of board management at a location, usually with larger stations like Marylebone in the example quoted. What this value represents is that the CIS provider at the relevant location has chosen to hide this service from display. There could be any reason for this of course but the main reason is to manage available display space on a board. So for example, if you have a location like Euston which has LM and VT trains running on completely separate lines, if there is a problem affecting one of the lines which means all VT services are at a standstill, after a while the main display board would fill up with delayed VT services and the on-time LM services would not be shown.

As this flag is purely there to handle display constraints, and is only relevant if you are physically AT the location itself, other Darwin users are not expected to hide the service (e.g. if you're sitting in an office looking for a service which happens to have been suppressed on a station board you would still expect to see it!) but you may consider using the flag to warn users that the service is not currently being shown on the departure board(s) at the relevant location.

WantStuff

unread,
May 14, 2018, 4:45:13 PM5/14/18
to A gathering place for the Open Rail Data community
Thank you RDG.
As always, a clear and concise response.

Kind regards
Martin

Reply all
Reply to author
Forward
0 new messages