Home » railML newsgroups » railML.infrastructure » How to model ETCS BL2 speed restrictions and gradients, in railML v2.x (Best practice)
Re: How to model ETCS BL2 speed restrictions and gradients, in railML v2.x [message #2084 is a reply to message #2078] Fri, 11 January 2019 11:22 Go to previous message
christian.rahmig is currently offline  christian.rahmig
Messages: 436
Registered: January 2016
Senior Member
Dear all,

Am 08.01.2019 um 21:00 schrieb Christian Rahmig:
> Am 07.12.2018 um 09:33 schrieb Jörgen Strandberg:
>> [...]
>>
>> 1.    gradientChange
>> This seems to be the only way to enter slope of track.
>>
>> Description of @dir value range on wiki.railml.org is
>> incorrect. Only up and down are valid according to schema,
>> and that is what the wiki should say too.
>
> You are right, this is a mistake in the wiki. Since this wiki page uses
> many templates, changing it is quite complex, but I will trigger the
> changing process.

I filed a Trac ticket for this issue (see [1]). In this ticket, I also
listed all the other elements, where this problem of wrong @dir
enumeration values occurs.

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

Best regards
Christian

--
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
Previous Topic: [railML3.1] Difference between Stopping Places and Operational Point (opOperationType stoppingPoint)
Next Topic: Question towards use of @passable attribute (2.4)
Goto Forum:
  


Current Time: Tue May 07 04:43:32 CEST 2024