Home » railML newsgroups » railml.timetable » [railML2] Modeling through service without rostering
[railML2] Modeling through service without rostering [message #2840] Mon, 18 October 2021 10:21 Go to next message
Bertolt Lang is currently offline  Bertolt Lang
Messages: 2
Registered: October 2021
Junior Member
Hello,

I would like to know how to correctly model through services without using 'rosterings'.
The first idea would be to use the 'connections' container on the last 'ocpTT' of a 'trainPart' and to refer to the following train with the 'connection.trainRef' element (see example and https://wiki2.railml.org/wiki/TT:connection).
Would that be a legitimate solution or is there a better way to go?

Thanks and best regards,

Bert


============================================================ =================================================

Hallo,

ich würde gerne wissen, wie Durchbindungen korrekt dargestellt werden können, ohne dass 'rosterings' verwendet werden.
Die erste Idee wäre die Nutzung des Containers 'connections' am letzten 'ocpTT' eines 'trainPart' und in diesem auf den nachfolgenden Zug mit dem Element 'connection.trainRef' zu verweisen (Siehe Beispiel und https://wiki2.railml.org/wiki/TT:connection).
Wäre das eine legitime Lösung, oder gibt es hier einen besseren Weg?

Danke und viele Grüße,

Bert

============================================================ =================================================

Example:

..<trainParts>
....<trainPart id="tp01_1" categoryRef="29ES" trainNumber="900" additionalTrainNumber="900" line="1">
......<operatingPeriodRef ref="OP_1"/>
......<formationTT formationRef="ICE"/>
......<ocpsTT>
........<ocpTT ocpRef="A" ocpType="stop">
..........<times scope="scheduled" departure="13:15:00" departureDay="0"/>
........</ocpTT>
........<ocpTT ocpRef="B" ocpType="stop">
..........<times scope="scheduled" arrival="16:00:00" arrivalDay="0"/>
..........<connections>
............<connection trainRef="TR_4" connOperation="throughService"/> <!--throughService as other:anything-->
..........</connections>

........</ocpTT>
......</ocpsTT>
....</trainPart>
....<trainPart id="tp02_1" categoryRef="29ES" trainNumber="9001" additionalTrainNumber="9001" line="2">
......<operatingPeriodRef ref="OP_1"/>
......<formationTT formationRef="ICE"/>
......<ocpsTT>
........<ocpTT ocpRef="C" ocpType="stop">
..........<times scope="scheduled" departure="16:15:00" departureDay="0"/>
........</ocpTT>
........<ocpTT ocpRef="D" ocpType="stop">
..........<times scope="scheduled" departure="17:47:00" arrival="17:45:00" departureDay="0" arrivalDay="0"/>
........</ocpTT>
......</ocpsTT>
....</trainPart>
..</trainParts>
..<trains>
....<train id="TR_3" trainNumber="900" type="commercial">
......<trainPartSequence sequence="1">
........<trainPartRef ref="tp01_1" position="1"/>
......</trainPartSequence>
....</train>
....<train id="TR_4" trainNumber="9001" type="commercial">
......<trainPartSequence sequence="1">
........<trainPartRef ref="tp02_1" position="1"/>
......</trainPartSequence>
....</train>
..</trains>
Re: [railML2] Modeling through service without rostering [message #2842 is a reply to message #2840] Fri, 29 October 2021 17:07 Go to previous message
Christian Rößiger is currently offline  Christian Rößiger
Messages: 62
Registered: March 2015
Member
Hello Bert,

since railML2.1, the element <connection> should only be used to model
connections with passenger interchange (or freight transhipment). With
railML version 2.1, all values for the attribute "connType" that refer
to the transfer of vehicles between trains were marked as deprecated.
In my view, the correct way would be to use commercial trains instead.
In the wiki there are some descriptions*) for the modelling of coupling
& sharing using commercial trains, which can also be applied to through
connections.

Best Regards
Christian

*)
https://wiki2.railml.org/wiki/Dev:Train_Coupling_And_Sharing
https://wiki2.railml.org/wiki/TT:train, section Best practices
============================================================

Hallo Bert,

das Element <connection> sollte spätestens seit railML2.1 nur zur
Abbildung von Anschlüssen mit Fahrgastwechsel (oder Güterumladung)
verwendet werden. Mit railML-Version 2.1 wurden für das Attribut
"connType" alle Werte als deprecated markiert, die sich auf den Übergang
von Fahrzeugen zwischen Zügen beziehen.
Der aus meiner Sicht richtige Weg wäre stattdessen die Verwendung von
commercial trains. Im Wiki gibt es an einigen Stellen*) Beschreibungen
für die Abbildung von coupling & sharing mit commercial trains,
sinngemäß lassen sich diese auch auf Durchbindungen anwenden.

Viele Grüße
Christian

*)
https://wiki2.railml.org/wiki/Dev:Train_Coupling_And_Sharing
https://wiki2.railml.org/wiki/TT:train, Abschnitt Best practices
Previous Topic: [railML3] Fahrzeitzuschläge / Runtimereserves
Next Topic: [railML2] Inconsistent examples in the wiki for <category>
Goto Forum:
  


Current Time: Sat Jul 20 07:52:16 CEST 2024