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
  • #428
Closed
Open
Issue created Oct 12, 2020 by Organisation@organisation.GOVOwner

Extend definition of <lock> and add values

Description

railML 2.4 implementation of is only very basic and needs to be extended to make usable.

Background

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

The element is a sub-element of . The set of attributes available in core railML2.4 for the lock element is extended in railML2.4nor (for a complete table, see 4.21.2).

The Norwegian standardisation requires a clearer definition of the element. The primary use case in railML2.4nor for the modelling of locks is capacity planning. Therefore, only the operational aspects of the lock are modelled and not what kind of object it locks and in which relation it locks them (interlocking).

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

Links

  • Forum discussion:
  • Torben Brand, 20.12.2016: [https://www.railml.org/forum/index.php?t=msg&th=484&goto=1458&#msg_1458]
  • Christian Rahmig, 16.11.2020: [https://www.railml.org/forum/index.php?t=msg&th=778&goto=2589&#msg_2589]
  • Morten Johansson, 29.04.2021: [https://www.railml.org/forum/index.php?t=msg&th=809&goto=2708&#msg_2708]
  • Trac tickets:
  • #428
  • #305 (Introduction of a lock as new signalling infrastructure element)
  • Wiki documentation:
  • IS:lock: [http://wiki2.railml.org/wiki/IS:lock]

Proposed solution in railML 2.5

Add new attribute @positionAtTrack ("left", "right") to describe location of the lock along the track.

Add new reference attribute @controllerRef to link the lock with the controller from where it is controlled.

Add new reference attribute @keyStorageRef to link the lock with the OCP where the key is stored in case it is not inserted in the lock.

The information about the lock type is currently not yet defined in a generic way. Therefore, it is suggested to use existing attribute @description (free text) for it.

Add new attribute @trackDist to specify the distance between the track's middle axis and the middle of the lock cabinet in meters (should be given at least with decimeter accuracy).

Edited Dec 13, 2021 by Administrator
Assignee
Assign to
Time tracking

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