Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • 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
    • Contributors
    • Graph
    • Compare
  • Issues 81
    • Issues 81
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Infrastructure Registry
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • railML.org
  • railML 3railML 3
  • Issues
  • #254

Closed
Open
Created Jul 17, 2014 by Coordination@coordination.GOVOwner

Unit for <tunnel>@crossSection (de: Einheit für <tunnel>@crossSection)

The unit for the cross section of an Tunnel is metre (tLengthM), but must be square metre, as the area of the cross section is meant. Typical values for railways are 80 m² or 100 m², see http://commons.wikimedia.org/wiki/File:4-05m_Tunnelquerschnitt.png for more details.

Links

  • Forum discussion
  • Trac tickets
  • #54 crossSection: ocp vs. tunnel
  • Wiki documentation

Proposed solution railML 3.1

railML 3.1 does not implement tunnel cross section.

Proposed solution railML 3.x

When a use case requires the implementation of a tunnel cross section, the resulting model has to consider this issue.

Assignee
Assign to
3.3
Milestone
3.3
Assign milestone
Time tracking

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