Home » railML newsgroups » railML.infrastructure » Shown values on mileposts
Shown values on mileposts [message #527] Fri, 15 March 2013 23:05 Go to next message
Christian Rahmig is currently offline  Christian Rahmig
Messages: 151
Registered: January 2011
Senior Member
Hello everybody,

at the last railML meeting in Berlin, we discussed about the following
aspects of mileposts (de: Hektometertafeln):

(1) Are there "switchable" mileposts?
(2) Are there references between mileposts and mileage changes?

Number (1) can be answered with "no". For number (2) the situation is
more complex (see [1]) so that a Trac ticket has been filed [2]:

It is necessary to put the offset in a separate field. Only then it is
possible to distinguish between the mileage value in the gap and after
the gap. In particular "123.4 +1" is a different value than "123.5".
Therefore, I suggest to give the milepost two attributes: "shownValue"
given in kilometers with 3 digits behind the comma and "shownOffset"
given in dezi-kilometers without any digits behind the comma (e.g. 100m
= 1).

Of course, it can happen, that the milepost is situated exactly at the
position of a mileage change. So, I suggest to include an optional
reference mileageChangeRef to the mileage change element.

Any comments appreciated...

[1] http://www.drehscheibe-foren.de/foren/read.php?3,2958137,296 0646
[2] https://trac.assembla.com/railML/ticket/228

Regards

--
Christian Rahmig
railML.infrastructure coordinator
Re: Shown values on mileposts [message #528 is a reply to message #527] Sat, 16 March 2013 12:04 Go to previous message
Christian Rahmig is currently offline  Christian Rahmig
Messages: 151
Registered: January 2011
Senior Member
Hello everybody,

Am 15.03.2013 23:05, schrieb Christian Rahmig:
> It is necessary to put the offset in a separate field. Only then it is
> possible to distinguish between the mileage value in the gap and after
> the gap. In particular "123.4 +1" is a different value than "123.5".
> Therefore, I suggest to give the milepost two attributes: "shownValue"
> given in kilometers with 3 digits behind the comma and "shownOffset"
> given in dezi-kilometers without any digits behind the comma (e.g. 100m
> = 1).

Susanne mentioned that this solution might be very specific for Germany.
How about the situation in other countries in Europe and the world? I
would like to forward this question to our international users: Please
share your experiences here in the forum. Thank you.

Regards

--
Christian Rahmig
railML.infrastructure coordinator
Previous Topic: speed profiles for general directions
Next Topic: Haltetafel / stop post
Goto Forum:
  


Current Time: Thu Mar 28 21:08:20 CET 2024