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 70
    • Issues 70
    • 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
  • #54
Closed
Open
Issue created Apr 19, 2010 by Deleted User@deleted-user

crossSection: ocp vs. tunnel

  • A tunnel has an attribute crossSection that means something like clearance profil.

  • An ocp has to be referenced on a track with help of crossSection element as part of trackTopology.

'''These two occurences of the same word have a totally different meaning.

'''Please provide some other term for one of this issues.

My idea: rename crossSection attribute in tunnel element to nominalWidth.

Links

  • Forum discussion
  • Trac tickets
    • #54 (closed)
    • #254 (closed) Unit for @crossSection (de: Einheit für @crossSection)
    • #563 (closed)
  • Wiki documentation

Proposed solution railML 3.1

Neither the tunnel cross section nor the OCP cross section have been modeled in railML 3.1.

Proposed solution railML 3.3

The term "cross section" is well known and established for describing the size of a cutting plane of a tube. Therefore, this term is being used for an attribute in the newly introduced element //overcrossing/tunnelResistance (see #563 (closed)).

Proposed solution railML 3.x

When a use case requires the implementation of an Operational Point cross section, the resulting model has to consider alternative names/terms for the modelled information.

Edited Oct 07, 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