Forum: railml.interlocking » Restricted Areas: limitedBy vs. elements inside

Home » railML newsgroups » railml.interlocking » Restricted Areas: limitedBy vs. elements inside

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

Restricted Areas: limitedBy vs. elements inside [message #2091]

Sun, 13 January 2019 04:37

Joerg von Lingen
Messages: 151
Registered: May 2011

Senior Member

Dear all,

currently a restricted area can be defined by the references to limiting objects
(isLimitedBy) and the references to all track assets inside the area
(trackAssetInRA).

This can be seen as a redundancy which is not really needed. So how would you
define such an area?

--
Best regards,
Joerg v. Lingen - Interlocking Coordinator

Report message to a moderator

[Message index]

		Restricted Areas: limitedBy vs. elements inside By: Joerg von Lingen on Sun, 13 January 2019 04:37
		Re: Restricted Areas: limitedBy vs. elements inside By: Thomas Nygreen JBD on Mon, 14 January 2019 13:49
		Re: Restricted Areas: limitedBy vs. elements inside By: Jörg von Lingen on Wed, 16 January 2019 12:08
		Re: Restricted Areas: limitedBy vs. elements inside By: Joerg von Lingen on Sat, 26 January 2019 05:03
		Re: Restricted Areas: limitedBy vs. elements inside By: Joerg von Lingen on Wed, 13 January 2021 05:58

Previous Topic:	What is the rationale for multiple <assetsForIL>s?
Next Topic:	[railML3]: Referencing between IS and IL

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Mon Feb 09 13:01:41 CET 2026