| Re: TrainpartRefs [message #753 is a reply to message #750] |
Mon, 03 October 2011 11:58   |
Joachim Rubröder railML
Messages: 0
Registered: November 2019
|
|
|
|
Hi,
you are totally right.
The multiple use of the same trainPart in different trainPartSequences
provides problems together with the use of rosterings or resevations.
I therefore corrected the exaple to:
<trainPartRef position="1" ref="tp2109a" />
<trainPartRef position="2" ref="tp2109b" />
Best regards,
Joachim Rubröder
Carsten Weber wrote:
>
> Dear RailML-Users,
>
> "Andreas Tanner" <ata(at)ivude> schrieb im Newsbeitrag
> news:j3q8j2$386$1(at)sifaivifhgde...
>> Hallo RailML-group,
>>
>> is the <trainPart> element intended for "multiple use"? The example file
>> TT_ICN.xml has
>>
>> <train id="o2109" name="ICN 2109" type="operational" trainNumber="2109"
>> description="betrieblicher Zug 2109 mit 2 Kompositionen">
>> <trainPartSequence sequence="1" pathStatus="confirmed">
>> <trainPartRef position="1" ref="tp2109" />
>> <trainPartRef position="2" ref="tp2109" />
>>
> For me it looks like a mistake in the example.
> The example should look like this:
>
>> <trainPartRef position="1" ref="tp2109a" />
>> <trainPartRef position="2" ref="tp2109b" />
>
> Maybe tp2190a includes the same vehicle(s!) as tp2109b but maybe not.
> This way you can differ between the train parts in the rostering process.
>
> If it is necessary there should be an extension inside of the train parts if
> for example several coaches are combined in a train part and you want to
> create a roster for every single coach. But up to now no one has been
> interested in.
>
> Best regards.
>
> Carsten Weber
>
>
>
>
--
----== posted via PHP Headliner ==----
|
|
|
|
Members
Search
Help
Login
Home
