Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • railML 3 railML 3
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Graph
    • Compare revisions
  • Issues 71
    • Issues 71
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • railML.orgrailML.org
  • railML 3railML 3
  • Issues
  • #266
Closed
Open
Issue created Jun 15, 2015 by IS Coordination@coordination.ISMaintainer

Default value for application direction (de: Vorgabewert für Element-Wirkrichtung)

Almost every infrastructure element has an application direction related to the orientation of the track, where it is positioned. In railML 2.x, there is no default value for this direction, but it is often anticipated. Furthermore, the direction attribute is optional in railML 2.2, which may lead to unusable data, since e.g. a speedChange requires the direction information in order to be correctly interpreted.

de:Zusammenfassung

Jedes Infrastruktur-Element besitzt eine Wirkrichtung bezogen auf die Orientierung des Gleises, an dem es sich befindet. In railML 2.x gab es keinen Vorgabewert für diesen Parameter und auch der Parameter selbst war nicht verpflichted. In railML 3.0 soll dies anders sein, um damit die Verwendung der Daten besser zu garantieren.

Links

  • Forum discussion:
    • Torben Brand, 12.09.2018: [https://www.railml.org/forum/index.php?t=msg&th=607&goto=1959&#msg_1959]
    • Christian Rahmig, 17.09.2018: [https://www.railml.org/forum/index.php?t=msg&th=607&goto=1967&#msg_1967]
    • Thomas Nygreen, 29.12.2018: [https://www.railml.org/forum/index.php?t=msg&th=630&start=0&]
  • Trac ticket:
    • #266 (closed)
  • Wiki documentation:

Proposed solution railML 3.1

All infrastructure elements deriving from base class NetEntity may have several locations in the topology network. These locations can be spot locations, linear locations or area locations.

Elements and have a mandatory attribute @applicationDirection with enumeration values "normal", "reverse" and "both".

Since there exist infrastructure elements, which do not have an application direction or where the value is unknown, it is suggested to mark the attribute @applicationDirection as optional. For all infrastructure elements, where an application direction exists and is known, the value has to be given. There shall be no further default value for @applicationDirection.

Edited Oct 07, 2024 by IS Coordination
Assignee
Assign to
Time tracking

railML.org e.V. (Registry of Associations: VR 5750) Phone: +49 351 47582911 Altplauen 19h; 01187 Dresden; Germany