Precise Level Crossing Location (de: Präzise Ortsangabe für Bahnübergänge)
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)
Activity
- 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
-
- Resolution set to fixed
- Status changed from assigned to closed
railML2 wiki page of has been modified: new attribute @offset added
-
- 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 @posadd To Do for adapting wiki pages of LevelCrossing, Tunnel and Bridge
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)
- Owner set to @coordination.IS
- Status changed from reopened to assigned
By Documentation on 2021-05-07T10:01:22 (imported from GitLab)
-
- 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
assigned to @coordination.IS and unassigned @root
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.
removed Wiki label
changed milestone to %2.5
removed 2.5 label