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 #2112 is a reply to message #2104] Mon, 21 January 2019 15:09 Go to previous messageGo to previous message
Thomas Nygreen JBD is currently offline  Thomas Nygreen JBD
Messages: 68
Registered: February 2017
Member
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).

Best regards,
Thomas Nygreen
Railway capacity engineer
Jernbanedirektoratet

Report message to a moderator

[Message index]
 
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:
  

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

Current Time: Mon May 06 18:20:22 CEST 2024