| [railML2] Modeling through service without rostering [message #2840] |
Mon, 18 October 2021 10:21  |
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>
|
|
|
|
Members
Search
Help
Login
Home
