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 82
    • Issues 82
    • 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
  • #54

Closed
Open
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
  • #254 Unit for @crossSection (de: Einheit für @crossSection)
  • 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.x

When a use case requires the implementation of a tunnel cross section or an Operational Point 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