Skip to content
GitLab
    • Explore Projects Groups Topics Snippets
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
  • #374
Something went wrong while setting issue due date.
Closed
Open
Issue created 5 years ago by IS Coordination@coordination.ISMaintainer
  • New related issue

  • New related issue

Precise Level Crossing Location (de: Präzise Ortsangabe für Bahnübergänge)

Open

Precise Level Crossing Location (de: Präzise Ortsangabe für Bahnübergänge)

Description

Locating a level crossing using attributes @pos and @absPos is not sufficient for precise location of the area where track and road intersect.

Background

The attributes @pos and @absPos can be used to define a point on the track. The attribute @length can be used to describe the length of the intersection area. However, it is unclear, where the value of @pos and @absPos is located: at the beginning of @length, exactly in the middle of @length or somewhere in between... the offset between @pos and begin of @length is not specified.

Links

  • Forum discussion:
  • Janne Möller, 10.04.2019: [https://www.railml.org/forum/index.php?t=msg&th=655&start=0&]
  • Trac tickets:
  • Wiki documentation:
  • IS:LevelCrossing: [https://wiki2.railml.org/index.php?title=IS:levelCrossing_levelCrossings]

Proposed solution railML 2.4

Attributes @pos and @absPos shall describe the location of the (geometric) middle of the level crossing. Half the @length is before @pos and the other half is after.

This explanation has to be added to the documentation of in the railML 2 wiki.

Proposed solution railML 2.5

Attributes @pos and @absPos shall describe by default the location of the (geometric) middle of the level crossing. Half the @length is before @pos and the other half is after.

In order to define a different setting, the new optional attribute @offset can be used. It describes how many metres of the @length is before @pos. If @offset is not given, the default value shall apply.

In the Wiki to be added:

  • LevelCrossing: usage of @offset and application point of @pos (center of element)
  • Bridge: different application point of @pos (begin of element as seen from trackBegin)
  • Tunnel: different application point of @pos (begin of element as seen from trackBegin)

    Tasks

    0

    No tasks are currently assigned. Use tasks to break down this issue into smaller parts.

    Linked items
    0

    Link issues together to show that they're related. Learn more.

    Activity


    • IS Coordination
      IS Coordination @coordination.IS · 4 years ago
      Author Maintainer

      In [changeset:"1050/railML"]:

      implementing new attribute @offset for element <levelCrossing>; see #374
    • IS Coordination
      IS Coordination @coordination.IS · 4 years ago
      Author Maintainer
      • Owner set to @documentation.GOV
      • Status changed from new to assigned

      code implemented in railML 2.5 schema; railML 2 wiki documentation still has to be adapted

    • IS Coordination
      IS Coordination @coordination.IS · 4 years ago
      Author Maintainer
      • Resolution set to fixed
      • Status changed from assigned to closed

      railML2 wiki page of has been modified: new attribute @offset added

    • O
      Organisation @organisation.GOV · 4 years ago
      Owner
      • Resolution fixed deleted
      • Status changed from closed to reopened

      As agreed in the telco with JBD (Torben Brand + Thomas Nygreen) and railML.org (Vasco Kolmorgen + Christian Rahmig) on 08.03.2021.

    • IS Coordination
      IS Coordination @coordination.IS · 4 years ago
      Author Maintainer
      • Description changed
        == Description ==
        
        Locating a level crossing using attributes @pos and @absPos is not sufficient for precise location of the area where track and road intersect.
        
        === Background ===
        
        The attributes @pos and @absPos can be used to define a point on the track. The attribute @length can be used to describe the length of the intersection area. However, it is unclear, where the value of @pos and @absPos is located: at the beginning of @length, exactly in the middle of @length or somewhere in between... the offset between @pos and begin of @length is not specified.
        
        === Links ===
        
        * Forum discussion:
         * Janne Möller, 10.04.2019: [https://www.railml.org/forum/index.php?t=msg&th=655&start=0&]
        * Trac tickets:
        * Wiki documentation:
         * IS:LevelCrossing: [https://wiki2.railml.org/index.php?title=IS:levelCrossing_levelCrossings]
        
        == Proposed solution railML 2.4 ==
        
        Attributes @pos and @absPos shall describe the location of the (geometric) middle of the level crossing. Half the @length is before @pos and the other half is after.
        
        This explanation has to be added to the documentation of <levelCrossing> in the railML 2 wiki.
        
        == Proposed solution railML 2.5 ==
        
        Attributes @pos and @absPos shall describe by default the location of the (geometric) middle of the level crossing. Half the @length is before @pos and the other half is after.
        
        In order to define a different setting, the new optional attribute **<levelCrossing>@offset** can be used. It describes how many metres of the @length is before @pos. If @offset is not given, the default value shall apply.
      + 
      + In the Wiki to be added:
      + * LevelCrossing: usage of @offset and application point of @pos
      + * Bridge: different application point of @pos
      + * Tunnel: different application point of @pos

      add To Do for adapting wiki pages of LevelCrossing, Tunnel and Bridge

    • R
      Administrator @root · 4 years ago
      Owner

      Changes related to this ticket have been described in

      https://wiki2.railml.org/wiki/IS:levelCrossing_levelCrossings#offset

      and

      https://wiki2.railml.org/wiki/Dev:changes/2.5#New_Attribute_.3ClevelCrossing.3E.40offset

      Relation to tunnel & bridge unclear.

      By Documentation on 2021-05-07T09:58:46 (imported from GitLab)

    • R
      Administrator @root · 4 years ago
      Owner
      • Owner set to @coordination.IS
      • Status changed from reopened to assigned

      By Documentation on 2021-05-07T10:01:22 (imported from GitLab)

    • IS Coordination
      IS Coordination @coordination.IS · 3 years ago
      Author Maintainer
      • Description changed
        == Description ==
        
        Locating a level crossing using attributes @pos and @absPos is not sufficient for precise location of the area where track and road intersect.
        
        === Background ===
        
        The attributes @pos and @absPos can be used to define a point on the track. The attribute @length can be used to describe the length of the intersection area. However, it is unclear, where the value of @pos and @absPos is located: at the beginning of @length, exactly in the middle of @length or somewhere in between... the offset between @pos and begin of @length is not specified.
        
        === Links ===
        
        * Forum discussion:
         * Janne Möller, 10.04.2019: [https://www.railml.org/forum/index.php?t=msg&th=655&start=0&]
        * Trac tickets:
        * Wiki documentation:
         * IS:LevelCrossing: [https://wiki2.railml.org/index.php?title=IS:levelCrossing_levelCrossings]
        
        == Proposed solution railML 2.4 ==
        
        Attributes @pos and @absPos shall describe the location of the (geometric) middle of the level crossing. Half the @length is before @pos and the other half is after.
        
        This explanation has to be added to the documentation of <levelCrossing> in the railML 2 wiki.
        
        == Proposed solution railML 2.5 ==
        
        Attributes @pos and @absPos shall describe by default the location of the (geometric) middle of the level crossing. Half the @length is before @pos and the other half is after.
        
        In order to define a different setting, the new optional attribute **<levelCrossing>@offset** can be used. It describes how many metres of the @length is before @pos. If @offset is not given, the default value shall apply.
        
        In the Wiki to be added:
      - * LevelCrossing: usage of @offset and application point of @pos
      + * LevelCrossing: usage of @offset and application point of @pos (center of element)
      ?                                                                ++++++++++++++++++++
      
      - * Bridge: different application point of @pos
      - * Tunnel: different application point of @pos
      + * Bridge: different application point of @pos (begin of element as seen from trackBegin)
      + * Tunnel: different application point of @pos (begin of element as seen from trackBegin)
      • Owner set to @documentation.GOV

      added more details about what to add in the wiki

    • Documentation assigned to @coordination.IS and unassigned @root 3 years ago

      assigned to @coordination.IS and unassigned @root

    • Documentation
      Documentation @documentation.GOV · 3 years ago
      Maintainer

      https://wiki2.railml.org/wiki/IS:levelCrossing_levelCrossings has been updated and section https://wiki2.railml.org/wiki/Dev:changes/2.5#New_Attribute_.3ClevelCrossing.3E.40offset entered.

      @coordination.IS please, check.

    • Documentation removed Wiki label 3 years ago

      removed Wiki label

    • TT Coordination changed milestone to %2.5 2 years ago

      changed milestone to %2.5

    • TT Coordination removed 2.5 label 2 years ago

      removed 2.5 label

    Please register or sign in to reply
    Assignee
    Documentation's avatar
    Documentation
    Assign to
    Labels
    0
    None
    0
    None
      Assign labels
    • Manage project labels

    Milestone
    No milestone
    None
    Due date
    None
    None
    None
    Time tracking
    No estimate or time spent
    Confidentiality
    Not confidential
    Not confidential

    You are going to turn on confidentiality. Only project members with at least the Reporter role, the author, and assignees can view or be notified about this issue.

    Lock issue
    Unlocked
    0
    0 Participants
    Reference:

    Menu

    Explore Projects Groups Topics Snippets

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