Home » railML newsgroups » railml.interlocking » [railml3] Signal types and functions (See IS forum)
Re: [railml3] Signal types and functions [message #2143 is a reply to message #2135] Mon, 11 February 2019 18:17 Go to previous messageGo to previous message
Thomas Nygreen JBD is currently offline  Thomas Nygreen JBD
Messages: 68
Registered: February 2017
Member
Dear Jörg,

Jörg von Lingen wrote on Sat, 09 February 2019 09:32

<signalIL>@signalFunction is about the function of the signal as seen from the interlocking
"main" could be seen as a duplication but its meaning is more anything else but the specific uses - "The main signal is
a normal signal for train traffic protection which is neither used as block, entry, exit nor intermediate signal."

Even with this kind of definition, "main" or "distant" still describes another type of property than "exit" or "entry". Hence, there should be two different attributes.

Quote:

<signalIL>@isVirtual is especially considering ETCS systems were the interlocking in its data still has signals which
are switched to particular aspects. But on the outside there are only marker boards to identify the position of these
interlocking only signals. In that sense they are physical outside but virtual for the interlocking.
Whereas <signalIS>/<signalConstruction>@type="virtual" really means no physical object outside.

OK. I assume that there may also be other cases where the signal model in the IL differs from the actual (or non-existing) signal outside, in which case it would also then be considered virtual?


Best regards,
Thomas Nygreen
Railway capacity engineer
Jernbanedirektoratet
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Definition of Emergency Stop Area for railML 3.3
Next Topic: Reuse IL:SignalBox for Object controllers
Goto Forum:
  


Current Time: Wed Jun 19 15:23:15 CEST 2024