Home » railML newsgroups » railml.rollingstock » [railML3.2] Cant Deficiency Class for RS and/or TT
[railML3.2] Cant Deficiency Class for RS and/or TT [message #2891] Sun, 30 January 2022 13:46 Go to next message
Joerg von Lingen is currently offline  Joerg von Lingen
Messages: 151
Registered: May 2011
Senior Member
Dear all,

for use case ITMS there is the request to have "Cant Deficiency Class" in
rollingstock data. There is reference given to UNISIG Specification SUBSET-026-06.

When looking into chapter 6.5.1.5.34 NC_DIFF it becomes clear the resulting
Static Speed Profile (SSP) is what's needed. The definition of values for
NC_DIFF is the typical mixture of physical values and other conditions. Most of
the values for NC_DIFF are related to a specific value of cant deficiency in mm.
However, there are three values in-between referring to the brake position.

Question: Shall we model in railML the brake position and cant deficiency
separately or as a resulting integer like in UNISIG?

P.S: Be reminded that RS can only take (maximal) values of a train. But TT may
define deviating values/settings according to the needs of the specific run.

--
Best regards,
Joerg v. Lingen - Rollingstock Coordinator

Report message to a moderator

Re: [railML3.2] Cant Deficiency Class for RS and/or TT [message #2895 is a reply to message #2891] Tue, 01 February 2022 10:22 Go to previous messageGo to next message
Dirk Bräuer is currently offline  Dirk Bräuer
Messages: 313
Registered: August 2008
Senior Member
Dear Jörg,

we will surely need possible brake positions separated from cant deficiency classes (as already existing in railML). This leads to possible contradictions between "original" brake positions and such encoded into integers of cant deficiency classes.

I understand that this does not necessarily need to be a direct redundancy. So, I do not dare to have a final conclusion here. However, in such cases it was at least in the past tradition in railML to tend to the basic physical values and leave the higher "aggregated" values to the context of the reading software. (For instance, this also applies to track classes A..E which can only be given within a certain national context. So, railML encodes the basic physical values of axle load and load spread.)

If there would be a resulting integer in railML like in UNISIG, there should also be the "original" cant deficiency separated.

Best regards,
Dirk.

Report message to a moderator

Re: [railML3.2] Cant Deficiency Class for RS and/or TT [message #3907 is a reply to message #2895] Mon, 23 February 2026 13:54 Go to previous message
Jörg von Lingen is currently offline  Jörg von Lingen
Messages: 119
Registered: March 2016
Senior Member
Dear all,

as no one did argue to have 'coded' integer values for it like in UNISIG we will stay with the attribute for physical value and separate brake capabilities.

Best regards,
Joerg v. Lingen

Rollingstock Coordinator

Report message to a moderator

Previous Topic: new values for places and service
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Wed Mar 11 01:15:22 CET 2026