Home » railML newsgroups » railML.infrastructure » last open points for speedProfiles in railML 2.2
Re: Mandatory braking in front of a steep gradient [message #1703 is a reply to message #1586] Mon, 12 February 2018 14:42 Go to previous message
christian.rahmig is currently offline  christian.rahmig
Messages: 436
Registered: January 2016
Senior Member
Dear Dirk,

thank you for your feedback. In general, there is a "docking place" for
user-defined extensions in <trackElements>, which could be used to
define <mandatoryBrakingPlace> etc.
Since there has not been a big interest into this topic, I close the
ticket #227 [1].

Best regards
Christian Rahmig

[1] https://trac.railml.org/ticket/227


Am 18.05.2017 um 18:48 schrieb Dirk Bräuer:
> Dear Christian,
>
>> Therefore the implementation of "mandatoryBraking" in the element
>> "speedChange" should be removed.
>>
>> railML partners should use an "any"-Attribute as a short-term solution.
>
> I agree with that solution.
>
> Please care (with a lower priority) that there will be a "docking" place
> for user-defined (country-specific) virtual track elements as
> <any>-elements like "mandatoryBrakingPlace" or "signalViewingPlace" or
> such.
>
> With best regards,
> Dirk.


--
Christian Rahmig - Infrastructure scheme coordinator
railML.org (Registry of Associations: VR 5750)
Phone Coordinator: +49 173 2714509; railML.org: +49 351 47582911
Altplauen 19h; 01187 Dresden; Germany www.railml.org


Christian Rahmig – Infrastructure scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Maximum train current - Proposal for extension of infrastructure scheme in railML 2.4
Next Topic: Track: description vs. trackDescr
Goto Forum:
  


Current Time: Sat May 04 12:40:46 CEST 2024