Home » railML newsgroups » railml.infrastructure » Switch: usage of attribute @course
Switch: usage of attribute @course [message #1540] Wed, 05 April 2017 12:51 Go to next message
christian.rahmig is currently offline  christian.rahmig
Messages: 76
Registered: January 2016
Member
Dear all,

a standard question for railML newcomers is about the connection of
tracks via switches and crossings in order to form a railway network.
Some years ago, we created a Wiki page [1] for this topic. It became one
of the most called railML wiki pages. However, some questions remained
and I would like to bring the discussion here to the forum in order to
find a final solution for upcoming version 2.4.

The situation:
A switch is situated in the beginning or the end of a track and may be
connected to other tracks. See the following example:

<track id="tr01">
<trackTopology>
<trackBegin id="tr01_tb" pos="0">
<connection id="tr01_c01" ref="tr02_c01"/>
</trackBegin>
...
<switch id="sw01" pos="0" type="ordinarySwitch">
<connection id="sw01_c01" ref="tr03_c01" orientation="incoming"
course="left"/>
</switch>
</trackTopology>
</track>

The switch begin is located in the beginning of track "tr01". The main
course of the switch is defined by the <connection> in line 4. The
branching course of the switch is defined by the <connection> in line 8.

The problem:
The attribute @course may have the values "left", "right" and
"straight". However, the choice of this value currently depends on the
orientation of the track where the switch is located. The wiki page [1]
shows this in four small figures (examples 1-4). Consequently, the same
type of switch (with respect to its construction layout) may define its
branch one time with course="left" and the other time with
course="right" depending on the different orientation of the track where
the switch is located.

The question:
I want to ask you if you understand the current implementation /
understanding of railML track connection modelling or whether you
support to change it in the future? Shall the choice of value for
@course depend on the orientation of the track or shall it be
independent and just linked with the construction layout of the switch?

I am looking forward to receiving your comments. The main aspects of the
discussion and the final solution will be tracked with railML Trac
ticket #39 [2].

[1] http://wiki.railml.org/index.php?title=Connection_between_tr acks
[2] http://trac.railml.org/ticket/39

Best regards
Christian

--
Christian Rahmig - Infrastructure scheme coordinator
railML.org (Registry of Associations: VR 5750)
Phone Coordinator: +49 173 2714509; railML.org: +49 351 47582911
Altplauen 19h; 01187 Dresden; Germany www.railml.org
Re: Switch: usage of attribute @course [message #1707 is a reply to message #1540] Tue, 13 February 2018 11:46 Go to previous message
christian.rahmig is currently offline  christian.rahmig
Messages: 76
Registered: January 2016
Member
Dear all,

please let me remind you on the following forum post about the use of
<switch> attributes @course and @orientation. Please also consider the
forum post by Claus Feyling on this matter (see [3]).

If there is no feedback from your side, we anticipate that for upcoming
railML 2.4 you are happy with the current solution described in [4]. In
any case, railML 3.x is going to implement a modified approach.

[3] https://www.railml.org/forum/index.php?t=msg&th=516& start=0&
[4] http://wiki.railml.org/index.php?title=Dev:Connection_betwee n_tracks

Best regards
Christian

Am 05.04.2017 um 12:51 schrieb Christian Rahmig:
> Dear all,
>
> a standard question for railML newcomers is about the connection of
> tracks via switches and crossings in order to form a railway network.
> Some years ago, we created a Wiki page [1] for this topic. It became one
> of the most called railML wiki pages. However, some questions remained
> and I would like to bring the discussion here to the forum in order to
> find a final solution for upcoming version 2.4.
>
> The situation:
> A switch is situated in the beginning or the end of a track and may be
> connected to other tracks. See the following example:
>
> <track id="tr01">
> <trackTopology>
> <trackBegin id="tr01_tb" pos="0">
> <connection id="tr01_c01" ref="tr02_c01"/>
> </trackBegin>
> ...
> <switch id="sw01" pos="0" type="ordinarySwitch">
> <connection id="sw01_c01" ref="tr03_c01" orientation="incoming"
> course="left"/>
> </switch>
> </trackTopology>
> </track>
>
> The switch begin is located in the beginning of track "tr01". The main
> course of the switch is defined by the <connection> in line 4. The
> branching course of the switch is defined by the <connection> in line 8.
>
> The problem:
> The attribute @course may have the values "left", "right" and
> "straight". However, the choice of this value currently depends on the
> orientation of the track where the switch is located. The wiki page [1]
> shows this in four small figures (examples 1-4). Consequently, the same
> type of switch (with respect to its construction layout) may define its
> branch one time with course="left" and the other time with
> course="right" depending on the different orientation of the track where
> the switch is located.
>
> The question:
> I want to ask you if you understand the current implementation /
> understanding of railML track connection modelling or whether you
> support to change it in the future? Shall the choice of value for
> @course depend on the orientation of the track or shall it be
> independent and just linked with the construction layout of the switch?
>
> I am looking forward to receiving your comments. The main aspects of the
> discussion and the final solution will be tracked with railML Trac
> ticket #39 [2].
>
> [1] http://wiki.railml.org/index.php?title=Connection_between_tr acks
> [2] http://trac.railml.org/ticket/39
>
> Best regards
> Christian
>


--
Christian Rahmig - Infrastructure scheme coordinator
railML.org (Registry of Associations: VR 5750)
Phone Coordinator: +49 173 2714509; railML.org: +49 351 47582911
Altplauen 19h; 01187 Dresden; Germany www.railml.org
Previous Topic: Track: description vs. trackDescr
Next Topic: ocpRef at <platformEdges> and <stopPost>
Goto Forum:
  


Current Time: Mon Feb 19 16:50:39 CET 2018