Home » railML newsgroups » railml.common » SI units in railML 3.x
Re: SI units in railML 3.x [message #1799 is a reply to message #1689] Tue, 22 May 2018 14:34 Go to previous messageGo to previous message
Ferri Leberl is currently offline  Ferri Leberl
Messages: 24
Registered: September 2016
Junior Member
Dear all,

I have listed the simple types that are connected with units in https://trac.railml.org/ticket/317#comment:3
(for railML version 2.3)

It seems, that several simple Types are never used:
  • tWeightKG
  • tSpeedMPerSec
  • tAngleDeg
One could argue that these simple types can be removed, as they are not used, on the other hand, two of them use are SI units, so removing them would thwart the idea of converging towards SI units.

As Dirk Bräuer mentioned, in some cases it is not preferable to convert values between different units because of rounding errors.

A possible rule could be to keep non-SI units which are prone to rounding errors (e.g. km/h, miles per hour), but to remove non-SI units that where rounding errors are unlikely (e.g. millimetres can be converted into meters with mere point shifting). Further examples are tVolumeLitre→tVolumeCubicMeter (the first is used only by aDieselEngine/@fuelCapacity; and in practice, diesel engines will tank cubic meters rather than litres), tLengthKM→tLengthM and tWeightTons→tWeightKG.

I hope to hear your opinions soon.

Yours, Ferri Leberl

Mag. Ferri Leberl - Documentation
railML.org (Registry of Associations: VR 5750)
Phone railML.org: +49 351 47582911
Altplauen 19h; 01187 Dresden; Germany http://www.railml.org
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Define requirements for processContent strictly than lax
Next Topic: More concise usage of namespaces
Goto Forum:
  


Current Time: Sun Apr 28 05:56:08 CEST 2024