| Re: speedProfile and rolling stock [message #1836 is a reply to message #1829] |
Tue, 12 June 2018 18:20   |
Dirk Bräuer
Messages: 311
Registered: August 2008
|
Senior Member |
|
|
Dear Torben,
I understand that you want to link speedProfiles with vehicles in railML. However, so far, the link between speedProfiles and vehicles has been seen by trains only, not directly. That's why there is a reference to a <speedProfile> from a <trainPart> but not from a <vehicle>.
From the current point of view, only the train determines which speedProfile its vehicles use. Without a train, the vehicles don't "know" about speedProfiles. For instance, an ICE-T (with tilting technology) is ready to run with or without increased tilting speeds. Only the actual planned train = timetable decides whether it uses tilting or not. A hybrid engine (Diesel+battery) is ready to run with Diesel or battery, only the timetable decides which is actually planned a.s.o.
I understand that you may want to encode the possible links between speedProfiles and vehicles _without_ having a timetable. And I have no objection against it in general.
However, please consider that this leads to a possible redundancy: In case there is a timetable in the railML file, there is possibly the already existing reference from <trainPart> to <speedProfile> and/or a future reference from <vehicle> to <speedProfile>.
Which one should be used?
Can I assume that my railML file is still valid when I have a <trainPart> referencing a <speedProfile> and a <vehicle>, but the vehicle does not reference the <speedProfile>? This should not lead to a conflict.
So, when extending the schemes in the suggested way, please keep in mind clarifying a distinct usage at least in Wiki.
With best regards,
Dirk.
---
Am 08.06.2018 um 14:57 schrieb Torben Brand:
> As I so faar have gotten no feedback from the community I
> will allow me to give a solution suggestgion.
>
> Please add the following new (in blue) optional elements and
> attributes to railML2.4RS:
>
> <vehicle><speedProfileRef>
> @ref="corresponding id in <infrastructure/speedProfile>in
> the same file" of type id and optional
> @name="corresponding name in <infrastructure/speedProfile>in
> another file" of type string and optional
>
> Usually the lowest comon denominator of the combination of
> vehicles will determin the speedProfile of the formation.
> But the formation can also reduce/determin the speedProfile
> in it's own right. Setting the speedProfile in the formation
> is also nessesary when not modelling the wagons as vehicles,
> but as just as increased weight, length and lower speed than
> the vehicle attached. So the same extention must be attached
> under formation.
> <formation><speedProfileRef>
> @ref="corresponding id in <infrastructure/speedProfile> in
> the same file" of type id and optional
> @name="corresponding name in <infrastructure/speedProfile>
> in another file" of type string and optional
>
|
|
|
|
Members
Search
Help
Login
Home
