Forum: railML.infrastructure » How to represent Line Continuation on railML

Home » railML newsgroups » railML.infrastructure » How to represent Line Continuation on railML

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

How to represent Line Continuation on railML [message #2217]

Mon, 08 July 2019 18:02

Fabiana Diotallevi
Messages: 21
Registered: October 2018

Junior Member

Dear all,

if I want to export in railML 3.1 the schematic of a station that has several "real" bufferstops, and also some "fake" bufferstops representing the line borders (see image below), how can I export the fake ones?

/forum/index.php?t=getfile&id=48&private=0

/forum/index.php?t=getfile&id=48&private=0

I need to export them beacuse they define the borders of the tvdSection for the interlocking schema.

Any ideas?

Thanks in advance,
f.

Attachment: bufferstops.JPG
(Size: 34.52KB, Downloaded 555 times)

Report message to a moderator

Re: How to represent Line Continuation on railML [message #2218 is a reply to message #2217]

Tue, 09 July 2019 06:27

Jörg von Lingen
Messages: 87
Registered: March 2016

Member

Hi,

from interlocking point of view I think the tvdSection is delimited by the trainDetectionElement. A bufferstop would be
no active element for an interlocking.

I have added some detection points and names to your example:
tvdSection "R1" is delimited by "dp01" and "dp02"

tvdSection "R4" is delimited by "bs01" and "dp03"

The infrastructure limits shall be marked by border elements.

Regards,
Jörg von Lingen - Interlocking Coordinator
Fabiana Diotallevi wrote on 08.07.2019 18:02:
> Dear all,
>
> if I want to export in railML 3.1 the schematic of a station
> that has several "real" bufferstops, and also some "fake"
> bufferstops representing the line borders (see image below),
> how can I export the fake ones?
>
>
>
> I need to export them beacuse they define the borders of the
> tvdSection for the interlocking schema.
>
> Any ideas?
>
> Thanks in advance,
> f.

Attachment: bufferstop2.png
(Size: 23.45KB, Downloaded 286 times)

Report message to a moderator

Re: How to represent Line Continuation on railML [message #2219 is a reply to message #2218]

Tue, 09 July 2019 09:37

Fabiana Diotallevi
Messages: 21
Registered: October 2018

Junior Member

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.

Report message to a moderator

Re: How to represent Line Continuation on railML [message #2220 is a reply to message #2219]

Tue, 09 July 2019 12:15

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.
>

Report message to a moderator

Re: How to represent Line Continuation on railML [message #2221 is a reply to message #2220]

Fri, 12 July 2019 18:09

Fabiana Diotallevi
Messages: 21
Registered: October 2018

Junior Member

Ok,
thank you for the answer!

f.

Report message to a moderator

Re: How to represent Line Continuation on railML [message #2233 is a reply to message #2220]

Mon, 26 August 2019 14:24

christian.rahmig
Messages: 436
Registered: January 2016

Senior Member

Dear Fabiana,
dear Jörg,

let me also contribute to this topic :-)

Am 09.07.2019 um 12:15 schrieb Joerg von Lingen:
> [...]
> 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.

Yes, "insulatedRailJoint" and "axleCounter" are the train detection
elements that can be modelled via spot location elements.

> A "trackCircuit" would be already an equivalent to "tvdSection", i.e. not representing a spotLocation.

A "trackCircuit" is a track circuit and it is used (from interlocking
perspective) as "tvdSection" detecting the presence of a railway vehicle
inside.

> 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.

A "clearancePoint" can be used as a "manual border" of a "tvdSection":
the dispatcher checks (by looking) if the end of train has passed the
clearance point at the switch before allowing the next train to run the
switch on its other branch. Therefore, the "clearancePoint" (together
with the dispatcher) is also some kind of train detector.

The "virtualClearancePoint" is probably not really relevant. It
describes a clearance point, that is not linked with a physical element,
e.g. the "police man" in Germany [1]. @community: What id your opinion
about "virtualClearancePoint"?

[1]
https://upload.wikimedia.org/wikipedia/commons/thumb/e/e6/Ba hn-Grenzzeichen_aus_Blech_im_D%C3%BCsseldorfer_Hafen.jpg/120 0px-Bahn-Grenzzeichen_aus_Blech_im_D%C3%BCsseldorfer_Hafen.j pg

Best regards
Christian

--
Christian Rahmig - Infrastructure scheme coordinator
railML.org (Registry of Associations: VR 5750)
Phone Coordinator: +49 173 2714509; railML.org: +49 351 47582911
Altplauen 19h; 01187 Dresden; Germany www.railml.org

Christian Rahmig – Infrastructure scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org

Report message to a moderator

Previous Topic:	How to model 3 topology levels in rail.ML
Next Topic:	Proposed Semantic Constraint for <speedChange> in railML 2.x

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Fri Apr 19 07:53:43 CEST 2024