| MileageChanges [message #124] |
Thu, 11 November 2004 18:01  |
ron.van.kampen
Messages: 2
Registered: March 2004
|
Junior Member |
|
|
We are working on a program to convert dutch infrastructure defined in
InfraAtlas to RailML. In InfraAtlas many measuring tapes are used. In one
track one can encounter (track/ocs) elements defined by various measuring
tapes. Some measuring tapes run in the same direction as the track/relPos,
others in opposite direction.
We convert all absolute positions to a relative position (relative to the
start of each track), that we enter in the required pos attribute.
We would also like to use the optional absPos attribute in order to
reflect the original InfraAtlas position.
Doing this, we believe, we should also use the mileageChange element, to
reflect switching to a different measuring tape.
Assumption 1: Measuring tapes are mileages, and the transition to a new
measuring tape is defined by a mileageChange element.
At the start of the track, the absPos of elements is according to the
first measuring tape.
Question 1: Does one need to specify the direction of the first measuring
tape/mileage? If yes, how?
Assumption 2: When switching to the second mileage, we assume that absPos
is the position according to the first mileage, and absPosIn is the
position according to the new mileage.
Question 2: How does one specify the direction of the new mileage
(relative to track/relPos, or relative to previous mileage)?
Assumption 3: That is what the dir attribute is for.
Can someone tell us, if our assumptions are right?
If so, can our questions be answered?
Best regards,
-- Ron
|
|
|
|
| Re: MileageChanges [message #127 is a reply to message #124] |
Fri, 12 November 2004 09:26  |
Joachim.Rubröder
Messages: 33
Registered: September 2004
|
Member |
|
|
I thought the usage was meant like that:
dir:
is a general attribute that means, the km-point is valid for this
direction. A mileageChange should allways be valid in "both" directions.
In comparison, a signal is seen in only one direction.
pos:
is the distance relative to the start of the track, as in your assumption
1
absPos:
this is the absolute position, this means the km value written on the sign
beside the track. Or it is the starting value on your maesuring tape,
beginning at this point, being valid for the next part of the track. (not
as in your assumption 2)
absPosIn:
this should be the incoming mileage (the correct one, according to the
previous measuring tape) that could be different from the one, standing on
the sign beside the track. (not as in your assumption 2)
the direction of a mileage must be derived by "absPos"" and "absPosIn" of
the next mileageChange along the track. This direction attribute is
missing (and not the one in your 3rd assumption)
Maybe Ulrich could clear up the correct usage of the mileageChange
element.
Best regards,
Joachim
|
|
|
|
| Re: MileageChanges [message #132 is a reply to message #127] |
Wed, 17 November 2004 13:24 |
Ulrich Linder
Messages: 28
Registered: July 2003
|
Junior Member |
|
|
Hi,
your description was perfect.
Indeed is the direction of the mileage missing, but it's possible to get the
direction from two absolute positions. Should we introduce a special
attribute for this in the final release of V1.00? How to implement such an
attribute?
Today I'm working on the final version so please answer soon if you would
prefer to introduce such an attribute.
With best regards
Ulli
------------------------------
Dr.-Ing. Ulrich Linder
Linder Rail Consult
Undinestraße 9
D-12203 Berlin
Tel. +49.30.84 72 56 87
Fax. +49.30.84 47 11 56
Email mailto:UlrichLinder(at)linder-rail-consultde
www http://www.Linder-rail-consult.de
|
|
|
|
Members
Search
Help
Login
Home
