Home » railML newsgroups » railml.interlocking » [railml3.1] Redundant references in TVD sections and restricted areas
Re: [railml3.1] Redundant references in TVD sections and restricted areas [message #2116 is a reply to message #2112] Sat, 26 January 2019 05:00 Go to previous message
Joerg von Lingen is currently offline  Joerg von Lingen
Messages: 148
Registered: May 2011
Senior Member
<relatedToTrack>s in TVD section removed

Thomas Nygreen wrote on 21.01.2019 15:10:
> It is correct that finding the next TVD section by looking
> for other sections referencing the same boarder is not
> robust when there can be gaps. But that does not make it
> necessary to include a reference to the track. Actually, in
> the case of a gap, the next TVD section will not necessarily
> belong to the same track (e.g. if the gap occurs in a
> switch). I would rather suggest using the
> spotLocation/@netElementRef of the already referenced
> trainDetectionElement and follow that netElement in the
> applicable direction (if necessary across relations).
>
 
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Using type EntityILref for references to the infrastructure domain
Next Topic: switchType IS vs. IL
Goto Forum:
  


Current Time: Mon May 06 23:45:00 CEST 2024