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 previous message
Torben Brand is currently offline  Torben Brand
Messages: 158
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/>
 
Read Message
Read Message
Previous Topic: [railML3] Concept Location: RTM location association to railML entity
Next Topic: railML 2.3 infrastructure extension proposal - a new "state"
Goto Forum:
  


Current Time: Mon Apr 29 04:57:42 CEST 2024