Home » railML newsgroups » railml.rollingstock » Distinguish between physical and operational
Distinguish between physical and operational [message #2618] Sun, 20 December 2020 13:16
Joerg von Lingen is currently offline  Joerg von Lingen
Messages: 148
Registered: May 2011
Senior Member
Dear all,

rather often I have the impression that it is difficult to clearly distinguish
the use of data in railML.

As noted in post "[railML2] extend <formation> with the attribute @load" we have
some data, which are used in different context. In rollingstock we can define
only the physical characteristics of the formation or the vehicle. This data are
completely independent of the ones when using the formation/vehicle in train
operation. The structure of data may similar but the values may differ. See also
the attached table of non-exhaustive examples of such values.

--
Best regards,
Joerg v. Lingen - Rollingstock Coordinator
 
Read Message
Previous Topic: [railML2] extend <formation> with the attribute @load
Next Topic: [railML2] Do we need a solution to declare the states of rolling stock?
Goto Forum:
  


Current Time: Thu Mar 28 10:56:28 CET 2024