| Re: How to mix switches and crossings en connections ? [message #1361 is a reply to message #1360] |
Wed, 15 June 2016 08:01   |
christian.rahmig
Messages: 436
Registered: January 2016
|
Senior Member |
|
|
Dear Patrick,
thank you for your post and welcome to the railML infrastructure forum
community.
Am 11.06.2016 um 11:57 schrieb Patrick Renaud:
> [...]
>
> <xs:complexType name="eConnections">
> <xs:choice minOccurs="0" maxOccurs="unbounded">
> <xs:element name="switch" type="rail:eSwitch"
> minOccurs="0" maxOccurs="unbounded"/>
> <xs:element name="crossing" type="rail:eCrossing"
> minOccurs="0" maxOccurs="unbounded"/>
> </xs:choice>
> </xs:complexType>
>
> [...]
>
> How can I describe both the switches and the crossings for
> one track ?
There should be no problem in modelling both switches and crossings in
the same <trackTopology><connections> element.
As you can see from the schema, it is modelled as 'choice' that may
occur several times. So, you have the choice between <switch> and
<crossing> as many times as you want.
I validated this with the following code example code snippet:
<connections>
<switch id="s85" pos="518.102673">
<connection id="c64" course="left" ref="c65" orientation="outgoing"/>
</switch>
<crossing id="cr0909" pos="23.45">
<connection orientation="incoming" ref="c65" id="c99"/>
</crossing>
</connections>
Please let me know if your problem remains.
Best regards
Christian
--
Christian Rahmig
railML.infrastructure coordinator
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
