Forum: railML.infrastructure » [railML 3.4 bèta 3] BaliseGroup attribute validityDirection

Home » railML newsgroups » railML.infrastructure » [railML 3.4 bèta 3] BaliseGroup attribute validityDirection

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

Re: [railML 3.4 bèta 3] BaliseGroup attribute validityDirection [message #4053 is a reply to message #4050]

Wed, 17 June 2026 15:25

Mathias Vanden Auweele is currently offline

Mathias Vanden Auweele
Messages: 167
Registered: February 2025
Location: Brussels

Senior Member

Thank you Christian for the feedback. So if I understand correctly, a <baliseGroup> can have multiple <functionalType> with different @validityDirection values. In that case, to avoid ambiguity, I think a reference to the spotLocation for which the @validityDirection applies is required?

Mathias Vanden Auweele
Railway data freelancer
https://matdata.eu
Brussels, Belgium

Report message to a moderator

[Message index]

		[railML 3.4 bèta 3] BaliseGroup attribute validityDirection By: Mathias Vanden Auweele on Tue, 16 June 2026 18:04
		Re: [railML 3.4 bèta 3] BaliseGroup attribute validityDirection By: christian.rahmig on Wed, 17 June 2026 14:02
		Re: [railML 3.4 bèta 3] BaliseGroup attribute validityDirection By: Mathias Vanden Auweele on Wed, 17 June 2026 15:25

Previous Topic:	[railML 3.4 bèta 3] PlatformEdge's new attribute "lateralDistance"
Next Topic:	Interpreting "begin" and "end" in the sub elements <linearCoordinateBegin> and <linearCoordinateEnd>

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Tue Sep 15 11:48:14 CEST 2026