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
  • #515
Closed
Open
Issue created Aug 10, 2023 by CO Onto@onto.CO👽Developer

Extend level crossing in IS by barriers and lights

Background

currently levelCrossingIS/protection has no children. This is not enough to model complex level crossings.

Links

  • Forum discussion:
    • Georg Boasson, 02.06.2022: https://www.railml.org/forum/index.php?t=msg&th=880&start=0&
    • Larissa Zhuchyi, 23.01.2024: https://www.railml.org/forum/index.php?t=msg&th=939&start=0&

Proposed solution railML 3.3

levelCrossingIS/protection should have additional <barriers> and <lights> children.

both <barriers> and <lights> should have

  • name and spot, linear, areaLocation children.
  • @roadSide attribute. Possible values are "left" and "right".

After internal discussion it was decided to change naming to <roadSideBarriers> and <roadSideLights>.

Edited Jun 03, 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