Home » railML newsgroups » railml.infrastructure » need for new attribute "virtual" of trainDetector
need for new attribute "virtual" of trainDetector [message #1255] Wed, 23 September 2015 22:50
Joachim Rubröder is currently offline  Joachim Rubröder
Messages: 88
Registered: April 2007
Presently, railML defines traindetection elements that has children
trainDetector and trackCircuitborder.

Now, the interlocking model introduces the Virtual Subsection (VSS). The
VSS has either physical limits such as track insulators or axle counters
or, as the name suggests, a virtual limit.

I plead for the introduction of a boolean attribute "virtual" to the
trainDetector element. Suggestion for documentation: "true if this element
delimits a Virtual Subsection, false if this is a physically exisiting
train detection device such as an axle counter or a pedal".

If a user defines <trainDetector ... virtual="yes"/>, we're dealing with a
virtual section limit.

I can't export the virtual limit to the IL namespace because I need all
VSS-limits to be fully defined in the IS namespace. This allows one to do
graph-like operations like finding all (virtual) sections along a route.

I would need this in railML 3.

----== posted via PHP Headliner ==----
Previous Topic: Line category according to EN 15528
Next Topic: Re: Missing 'any' attributes/elements
Goto Forum:

Current Time: Fri Aug 18 04:55:00 CEST 2017