Home » railML newsgroups » railml.interlocking » Defining the AreaLocation of a IL:RestrictedArea
Defining the AreaLocation of a IL:RestrictedArea [message #3949] Fri, 27 March 2026 16:05 Go to next message
Mathias Vanden Auweele is currently offline  Mathias Vanden Auweele
Messages: 105
Registered: February 2025
Location: Brussels
Senior Member
Hello,

We need to define the topological location of a workzone. How can we do this? This question can be generalised for all RestrictedArea subclasses.

There is no corresponding IS:Workzone element. So no possibility to define it directly.

Note: I initially thought that a workaround could be to use the IL:isLimitedBy and referencing a IS:GenericArea. But railVivid limits the elements that can be referred by <isLimitedBy> to <trainDectionElement>, <bufferStop>, <baliseGroup> and <signalIS>

Thanks

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

[Updated on: Fri, 27 March 2026 16:33]

Report message to a moderator

Re: Defining the AreaLocation of a IL:RestrictedArea [message #3961 is a reply to message #3949] Fri, 10 April 2026 05:48 Go to previous messageGo to next message
Jörg von Lingen is currently offline  Jörg von Lingen
Messages: 123
Registered: March 2016
Senior Member
Dear Mathias,

in general the elements in interlocking domain do not have any location. This can only be retrieved by using the references into functional infrastructure.

The idea of IL:isLimitedBy is to define the extend of an area using functional elements at the area's border. This shall be elements with a spot location like signals, train detectors etc.
The location of these 'border' elements shall be used to determine the area location of such a RestrictedArea. The direct reference to a defined area in functional infrastructure does not make sense from interlocking point of view. The interlocking needs to know the elements at the border of a RestrictedArea as the might be handled in a special way - e.g. locking to protect access from or to the area.

---
Jörg von Lingen - Interlocking scheme coordinator

Report message to a moderator

Re: Defining the AreaLocation of a IL:RestrictedArea [message #3962 is a reply to message #3961] Mon, 13 April 2026 11:47 Go to previous message
Mathias Vanden Auweele is currently offline  Mathias Vanden Auweele
Messages: 105
Registered: February 2025
Location: Brussels
Senior Member
Defining only the borders with IL:isLimitedBy and calculating the areaLocation from those holds a lot of risk. I have done this before and you need a lot of hypothesis to be able to perform this calculation (is it always the shortest path?) and when one border is missing due to data quality?

I propose that this is not the place to save bits but allow data providors to also provide a topology position for these elements. So I would propose a counterpart in the IS schema that can hold the areaLocation and be referenced by the IL.

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

Report message to a moderator

Previous Topic: aspectRelation - multiplicity of references
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Fri Apr 17 17:58:16 CEST 2026