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 #2103 is a reply to message #2080] Wed, 16 January 2019 12:35 Go to previous messageGo to previous message
Joerg von Lingen is currently offline  Joerg von Lingen
Messages: 149
Registered: May 2011
Senior Member
Dear all,

we discussed the issue of <relatedToTrack>s in TVD section today.
1) The element shall be optional not mandatory.
2) It was introduced to allow finding the neighbour TVD section in case of sections with gap as described by Norwegians.
Means there may be cases where (especially) track circuits without explicit insulated rail joints (IRJ) are not joining
or overlapping. As long as we cannot exclude such cases of gaps I would rather keep the possible references to
underlaying track.

Regards,
Jörg von Lingen - Interlocking coordinator

Thomas Nygreen wrote on 08.01.2019 22:21:
> Dear all,
>
> It seems to me that the references to all tracks (partially)
> inside a TVD section (<relatedToTrack>s) and the references
> to all track assets in a restricted area (<trackAssetInRA>s)
> are both redundant and incurring a large overhead. In both
> cases, these references can be found by the consuming system
> by following other defined references.
>
  • Attachment: TC_gap.jpg
    (Size: 6.55KB, Downloaded 402 times)

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 Sep 09 03:55:10 CEST 2024