| Orientation of baliseGroup and validity direction of balise telegrams [message #3640] |
Fri, 06 June 2025 15:04  |
Silvan Gruber
Messages: 7
Registered: July 2024
|
Junior Member |
|
|
Dear community
Regarding the orientation of balise groups and the validity directions of balise telegrams, the RailML specification does not seem to be clear. According to the Wiki, the information on the orientation and validity direction of balise telegrams can be described in railML as follows:
- Balise groups are located using "spotLocation," with the optional "applicationDirection" attribute. As I understand, this attribute is used to relate the effective direction of an element to the orientation of the NetElement.
- According to the wiki, the attribute "mileageDirection" can be used to align the balise group according to the track mileage.
- The child element "functionalType" is used to specify kinds of telegrams sent by a balise group. Since the telegrams are direction-dependent, the validity direction is described by the "mileageDirection" attribute.
The following questions arise in relation to these points:
1.) Should the attribute "applicationDirection" be used to describe the alignment in relation to the underlying NetElement? Then the following convention would make sense:
- applicationDirection="normal" => The orientation of the balise group corresponds to the orientation of the NetElement. (The position of the single balise with N_PIG=0 located on the NetElement is closer to the beginning of the NetElement than the single balise with N_PIG = 0+n)
- applicationDirection="reverse" => The orientation of the balise group is inverse to the orientation of the NetElement. (The position of the single balise with N_PIG=0+n located on the NetElement is closer to the beginning of the NetElement than the single balise with N_PIG = 0)
- applicationDirection="both" => is not used
2.) If an orientation of a balise group is specified when locating the balise group using "applicationDirection" (according to 1.), the information in "mileageDirection" would be redundant. Furthermore, problems can arise if the orientation of elements is not consistently related to the NetElements, but rather, as in this case, the route mileage is used with "mileageDirection." Here, the orientation should be described in relation to the underlying NetElement.
3.) According to Subset-026 Chapter 7, the validity direction of balise telegrams (Q_DIR) refers to the orientation of the balise group. Thus, the use of the "mileageDirection" attribute is not defined precisely enough in this regard. Furthermore, the functionalType@mileageDirection attribute can only specify whether a function acts in the nominal or reverse direction. If a function acts in both directions, the "both" attribute is missing. The attribute should indicate the relevant validity direction with reference to directionality of the balise group sending the information (Q_DIR).
In this context we ask the community if there are other users who have defined a clarification of the railML specification and a corresponding convention?
Kind regards
Silvan Gruber
SBB Swiss Railways
[Updated on: Fri, 06 June 2025 15:07] Report message to a moderator |
|
|
|
Members
Search
Help
Login
Home
