Home » railML newsgroups » railml.timetable » TrainpartRefs
Re: TrainpartRefs [message #750 is a reply to message #745] Fri, 09 September 2011 10:23 Go to previous messageGo to previous message
Carsten Weber is currently offline  Carsten Weber
Messages: 27
Registered: November 2011
Junior Member
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
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Frage zu TT:category
Next Topic: deprecated attribute "trainLine" for element "trainPart"
Goto Forum:
  


Current Time: Thu May 16 05:04:34 CEST 2024