| Re: [railML3]: openend and Macroscopic nodes [message #1678 is a reply to message #1676] |
Mon, 04 December 2017 15:50  |
christian.rahmig
Messages: 472
Registered: January 2016
|
Senior Member |
|
|
Dear Fabrizio,
Am 29.11.2017 um 14:53 schrieb Fabrizio Cosso:
> Dear Christian,
> How <openEnd> and <macroscopicNode> elements can be modeled
> within railML3?
> Generally speaking, what are the allowed values for
> trackBegin and trackEnd elements: are switches, crossings
> and bufferStops the only allowed values?
<track> child elements <trackBegin> and <trackEnd> provide reference to
demarcating infrastructure elements. At microscopic level, a <track> may
reference <bufferStop>, <switch> or <crossing> elements as begin and
end. At the aggregated mesoscopic or macroscopic level a <track> may
reference <operationalPoint> or <border> elements. If you want to model
a station track without knowing exactly about the underlying microscopic
topology network, a possible solution may look like this:
<operationalPoint id="opp01">
</operationalPoint>
....
<track id="trc01" type="sidingTrack" length="320">
<trackBegin ref="opp01"/>
<trackEnd ref="opp01"/>
</track>
This solution is very close to the implementation in railML 2.3, see
"Best Practices" in [1].
But how about the "open end"? Does anybody have a brilliant idea on how
to model them in railML v3?
[1] http://wiki.railml.org/index.php?title=IS:track
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
|
|
|
|
Members
Search
Help
Login
Home
