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

Add <lineSection> to <trackGroups>

Description

It is suggested to divide a element into several elements. elements shall be available under . A line section should reference the tracks that belong to it.

Background

In Norway, railway lines - element - are segmented into line sections. They consist of either stations (defined from home to home signal) or open sections (sections between stations). Tracks are to be segmented at these borders.

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

The element was introduced in railML2.4nor as a sub-element of , which is an element present in railML 2.4. In railML 2.4, stations (OCP with attribute @propOperational="station") reference their tracks with <propEquipment/trackRef>@ref. Open sections are not defined in railML2.4 and do not have a track reference. However, this is important in Norway and thus shall be modelled with the element. It is a new child element of .

has a sub-element to reference the tracks which belong to the section.

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

Links

  • Forum discussion:
  • Torben Brand, 20.12.2016: [https://www.railml.org/forum/index.php?t=msg&th=482&goto=1456&#msg_1456]
  • Torben Brand, 06.03.2017: [https://www.railml.org/forum/index.php?t=msg&goto=1523&&srch=nor%3Aarea#msg_1523]
  • Trac tickets:
  • #414
  • #415 (closed)
  • #316
  • Wiki documentation:
  • none

Proposed solution in railML 2.5

tbc: Is there a need for railML 2.5 implementation or is a railML 3 implementation sufficient?

There is a need for having a solution in railML 2.5. However, the forum post by Christian from 20.11.2017 (see [https://www.railml.org/forum/index.php?t=msg&th=482&goto=1665&#msg_1665]) ist still waiting for answers.

It is suggested to follow a similar approach like in railML 3: Instead of introducing a new element , a hierarchy of elements shall be implemented:

  • a element can be used to model a line segment as well as a whole line
  • introduce new attribute @belongsToParent to reference a line by a line segment.
  • there is no new element

In the wiki, the definition/description for the element need to be adapted:

  • "A line is a sequence of one or more line sections forming a route, which connects operational points and which may consist of several tracks used for regular railway operation."
  • "The element shall be used to model line sections as well as whole lines."
  • attribute @belongsToParent: "reference to the (one and only) parent (line) section"

Proposed solution in railML 3.x

See Trac ticket #316

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

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