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
  • #486
Closed
Open
Issue created Jan 24, 2022 by TT Coordination@coordination.TTMaintainer

Document requirements for exchanging 3.x infrastructure

We discussed how to identify and detect changes (movements) of elements of the functional infrastructure.

  1. producer and consumer of the railML need to have common designators (at least one needs to be understood by both) or UUIDs
  2. functional infrastructure elements need to be absolutely located (e.g. milage). Either by direct usage of a non relative position system, or by indirect usage of such (if the track is described with an absolute length, then intrinsic coordinate related to that track is enough).

We need to document that in the wiki3 at some place where it can easily be found.

First step provide a text to be integrated into the wiki, then identify a proper location then assign to Mr. Leberl for writing the article accordingly.

Links

  • Forum discussion:
    • Karl-Friedemann Jerosch, 08.12.2021: https://www.railml.org/forum/index.php?t=msg&th=841&start=0&
Edited Mar 18, 2022 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