Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • railML 2 railML 2
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Graph
    • Compare revisions
  • Issues 50
    • Issues 50
    • 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 2railML 2
  • Issues
  • #429
Closed
Open
Issue created Oct 12, 2020 by Organisation@organisation.GOVOwner

Extend definition of <signal> and add attributes

Description

The <signal> element implementation misses information required by some use cases.

Background

This ticket was raised by Norway as part of the standardisation in Norway and shall be used commonly in the future.

The element <signal> is a sub-element of <ocsElements>.

Definition extension in accordance to Norwegian usage sees both light signals and boards as signals. railML2.4 does not offer the possibility to define boards as an individual element. Hence, in railML2.4nor the, in railML2.4 deprecated attribute, attribute @switchable becomes mandatory for and differentiates boards and signals:

  • Signals: signal@switchable = “true”
  • Boards: signal@switchable = “false”

Additionally, railML2.4nor extends the element by the following attributes: @lamps, @mounted and @side.

For more details see document “railML2.4nor Infrastructure Documentation“ (https://www.jernbanedirektoratet.no/railML), version 1.3, 03.07.2020, point 4.4.

Links

  • Forum discussion:
    • Morten Johansen, 30.04.2018: [https://www.railml.org/forum/index.php?t=msg&th=568&goto=1777&#msg_1777] --> lamps
    • Thomas Nygreen, 18.02.2019: [https://www.railml.org/forum/index.php?t=msg&th=648&goto=2152&#msg_2152] --> lamps in railML3
    • Tobias Bregulla, 25.01.2020: [https://www.railml.org/forum/index.php?t=msg&goto=2342&&srch=switchable#msg_2342] --> name, code, ruleCode
  • Trac tickets:
    • #429
  • Wiki documentation:
    • IS:signal: [http://wiki2.railml.org/wiki/IS:signal]

Proposed solution in railML 2.5

Sharpen definitions and examples in railML2 wiki:

  • @name: to be used for human-readable names; free text
  • @ruleCode: code for this element in the rule book, combination of letters and numbers and space allowed, e.g. Ne5, GA, SFRS/E
  • @code: for typical, specific abbreviations, used in different systems with the same understanding

Re-introduce attribute <signal>@switchable deprecated since version 2.2.

Enumeration attribute @function shall be extended with value "end"?

Number of lamps (for light signals) shall be given with new attribute <signal>@numberOfLamps.

Add new enumeration attribute <signal>@mountedOn with values "pole", "gantry" and "wall".

Add new enumeration attribute <signal>@positionAtTrack with values "left", "right", "above" and "ground".

Proposed solution railML 3.2

copy paste...

Edited Mar 14, 2022 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