| Re: [railML2] adding an attribute for clearance on switches and crossings. [message #2701 is a reply to message #2695] |
Sun, 11 April 2021 06:25  |
Jörg von Lingen
Messages: 87
Registered: March 2016
|
Member |
|
|
Dear all,
just to explain the situation/solution in railML3:
For movableElements like switches or crossings we have the reference by
<hasGaugeClearanceMarker> to the physical marker near the track. However, for
the interlocking purpose this info is not sufficient as one would need the
explicit branch, which is possibly fouling the gauge of the other track.
Therefore there is the reference <hasFoulingTrainDetector> in addition.
Once you have defined the clearance point it is fixed with the related clearance
gauge. So if you would change using a different clearance gauge then you have to
redefine the clearance point. Beside the physical marker this would also affect
the interlocking.
Best regards,
Joerg v. Lingen - Interlocking Coordinator
Am 09.04.2021 um 16:20 schrieb Christian Rahmig:
> Option 1 may be suitable for railML 3.x where we are
> refactoring the whole infrastructure model. For railML 2.x I
> prefer option 2 to stay as close as possible to the current
> implementation focusing only on small adaptations.
>
> b) Usually, the clearance point is marked by a small
> infrastructure element: the clearance post. This post marks
> the point, where the distance between two track center lines
> reaches 3.5 meters. Therefore, the clearance point is linked
> with the regular clearance gauge profile. If different
> clearance gauge profiles shall be considered (resulting in
> different clearance points), the attribute @clearance need
> to be repeatable and therefore transformed into a repeatable
> child element. Do you need to model different clearance
> points at once?
|
|
|
|
Members
Search
Help
Login
Home
