Home » railML newsgroups » railML.infrastructure » How to represent Line Continuation on railML
Re: How to represent Line Continuation on railML [message #2220 is a reply to message #2219] Tue, 09 July 2019 12:15 Go to previous messageGo to previous message
Jörg von Lingen is currently offline  Jörg von Lingen
Messages: 87
Registered: March 2016
Member
Dear Fabiana,

1) "border" element of type="rail3:Border" is a separate functionalInfrastructure element

2) a "trainDetectionElement" delimiting a tvdSection can be only of type "axleCounter" or "insulatedRailJoint". You may
consider "insulatedRailJoint" also for locations limiting an audio frequency track circuit without having a physical
insulation in the rails.

A "trackCircuit" would be already an equivalent to "tvdSection", i.e. not representing a spotLocation.
A "clearancePoint" or "virtualClearancePoint" is not really a mean to detect the presence of a train on the track -
explanation for use is missing.
For "axleCountingCircuit" I have no clue what it stands for, but it seems also not representing a spotLocation.

Regards,
Jörg von Lingen - Interlocking Coordinator
Fabiana Diotallevi wrote on 09.07.2019 09:37:
> Dear Joerg,
> thanks for the quick answer.
> I get your point, but I have another question then: what
> kind of "trainDetectionElement" could a line border be?
>
> From the 3.1 railML documentation the possible values are:
>
> <xs:enumeration value="axleCounter"/>
> <xs:enumeration value="axleCountingCircuit"/>
> <xs:enumeration value="clearancePoint"/>
> <xs:enumeration value="insulatedRailJoint"/>
> <xs:enumeration value="trackCircuit"/>
> <xs:enumeration value="virtualClearancePoint"/
>
> Any suggestion?
>
> Thanks again in advance,
>
> f.
>
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: How to model 3 topology levels in rail.ML
Next Topic: Proposed Semantic Constraint for <speedChange> in railML 2.x
Goto Forum:
  


Current Time: Thu Apr 25 18:28:32 CEST 2024