Home » railML newsgroups » railML.infrastructure » Extension suggestion for track sections
Extension suggestion for track sections [message #1882] Sat, 14 July 2018 17:48 Go to next message
Torben Brand is currently offline  Torben Brand
Messages: 162
Registered: March 2016
Senior Member
nor:trackSection

Initially we did not want to include the direct mapping of track vacancy detection sections (often abbreviated to TVD) in railML2. We will here use the shortened term track section (TS). We included them, until now, in the name of their borders being formed by trackCircuitBorder or trainDetector. Thus we needed two of each to have a name with dir="up" and one name with dir="down".
As there are not two physical objects on the same position, the physical objects need to be named (so need the name attribute themselves) and we need to map the track sections in the route extension we abandon this approach.

We instead suggest to add a Norwegian extension for a root element that is optional <nor:trackSection>. We suggest them as a root element as they are track independent and have no position on their own. They reference their borders through either trackCircuitBorder or trainDetector.

Example:
<nor:trackSections>
<nor:trackSection code="BD" description="desc" id="id10" name="01"/>
<nor:trainDetectionElementRef ref="id15"/>
<nor:trainDetectionElementRef ref="id16"/>
<nor:trackSection/>
<nor:trackSections/>

Report message to a moderator

Re: Extension suggestion for track sections [message #1894 is a reply to message #1882] Wed, 15 August 2018 09:20 Go to previous message
Joerg von Lingen is currently offline  Joerg von Lingen
Messages: 149
Registered: May 2011
Senior Member
Dear Torben,

within the example it seems @code is for identifying the set code of any track circuit as there is additionally @name
for naming the element.
In railML:IL it would look slightly different:

<rail3:ownsTvdSection isBerthingTrack="true" code="Arnau A02" id="A02T" partialRouteReleaseTimer="PT1S"
isReliable="true" residualRouteCancellationTimer="PT90S">
<rail3:hasDemarcatingBufferstop ref="bus02"/> <!-- reference to bufferStop in IS -->
<rail3:hasDemarcatingTraindetector ref="tde02"/> <!-- reference to trainDetectionElement in IS -->
<rail3:relatedToTrack ref="trc02"/> <!-- reference to track in IS -->
</rail3:ownsTvdSection>

Note: @code is here used for naming the element

Regards
Jörg von Lingen - Interlocking scheme coordinator

Torben Brand wrote on 14/07/2018 17:48:

> Example:
> <nor:trackSections>
> <nor:trackSection code="BD" description="desc" id="id10"
> name="01"/>
> <nor:trainDetectionElementRef ref="id15"/>
> <nor:trainDetectionElementRef ref="id16"/>
> <nor:trackSection/>
> <nor:trackSections/>
>

Report message to a moderator

Previous Topic: [railML3] Concept Location: RTM location association to railML entity
Next Topic: railML 2.3 infrastructure extension proposal - a new "state"
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Sat Sep 21 05:04:33 CEST 2024