Directions (de: Richtungen)

Description

It has to be clarified how the @dir attribute shall be interpreted and used. In particular, a definition for "direction" (@dir) shall be given. Further, it has to be decided for each (infrastructure) element, whether @dir shall be applied and which values shall be possible.

Background

There are some elements, where the @dir attribute does not make much sense. Either, because the element is valid for both directions of travel or because the element shall be only defined for one direction. So, the task is to identify elements where the @dir attribute shall be marked DEPRECATED.

Links

• Forum discussion
  • Torben Brand, 12.09.2018, 14:57h: [https://www.railml.org/forum/index.php?t=msg&goto=2304&#msg_2304]
  • Christian Rahmig, 16.04.2019, 20:25h: [https://www.railml.org/forum/index.php?t=msg&th=655&goto=2179&#msg_2179]
  • Christian Rahmig, 27.05.2019, 11:57h: [https://www.railml.org/forum/index.php?t=msg&th=665&start=0&]
• Trac tickets
  • #352
  • #357 (closed)
• Wiki documentation

Proposed solution railML 2.5

The following solution is under discussion in the forum:

Elements without extent (without @length attribute) examples: balise, border, derailer, signal, stopPost... usage: @dir describes the direction of travel, for which the element applies. Possible values are "up", "down" and "both". A missing @dir attribute means that the application direction of this element is unknown. proposal: DEPRECATE @dir for trackCircuitBorder

Elements with extent (with @length attribute) examples: bridge, levelCrossing, platformEdge, serviceSection... usage: @dir describes the direction of travel, for which the element applies. Possible values are "up", "down" and "both". A missing @dir attribute means that the application direction of this element is unknown. By standard, the elements' orientation (not their application direction!) shall be always in direction of track orientation (from trackBegin towards trackEnd). proposal: DEPRECATE @dir for brigde, levelCrossing, platformEdge, serviceSection and tunnel

Elements that describe a change examples: axleWeightChange, clearanceGaugeChange, electrificationChange, gaugeChange, speedChange... usage: @dir describes the direction of travel, for which the change applies. Possible values are "up", "down" and "both". A missing @dir attribute means that the application direction of this change element is unknown. By standard (except for speedChange), the change elements' orientation (not their application direction!) shall be always in direction of track orientation (from trackBegin towards trackEnd). proposal: DEPRECATE @dir for elements where properties cannot differ by direction of travel, e.g. axleWeightChange, clearanceGaugeChange, electrificationChange, gaugeChange, ownerChange, powerTransmissionChange, radiusChange