| Re: Orientation of baliseGroup and validity direction of balise telegrams [message #3690 is a reply to message #3640] |
Mon, 11 August 2025 11:36   |
christian.rahmig
Messages: 515
Registered: January 2016
|
Senior Member |
|
|
Dear Silvan,
thank you very much for bringing up this topic and for your very detailed explanation of the current situation.
Since there has been no reaction from the community so far, the topic is either absolutely clear or completely unclear :-)
Therefore, let me comment on your questions from a coordinator's point of view:
1.) Yes, @applicationDirection describes the orientation of the balise group in relation to the underlaying netElement. The possible values are "normal" and "reverse".
2.) The child element <functionalType> with attribute @mileageDirection relates to a certain balise telegram that is submitted by the balise group. So, it is not really redundant, because a balise group can submit several telegrams that are effective for different directions of travel.
3.) If you want to describe a telegram that is valid for multiple driving directions, you would need to model it with several <functionalType> child elements where you specify the different @mileageDirection values, because there is no value "both".
Following this summary of the current situation, a question may be derived: Even though there are these two directions (1 orientation of the balise group; 2 driving direction for which a balise telegram is valid), should they better refer to the same basis (orientation of the underlaying netElement)?
As usual, any comments from the community are highly appreciated...
Best regards
Christian
Christian Rahmig – Infrastructure scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
|
|
|
|
Members
Search
Help
Login
Home
