Home » railML newsgroups » railML.infrastructure » MileageChanges
MileageChanges [message #124] Thu, 11 November 2004 18:01 Go to previous message
ron.van.kampen is currently offline  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
 
Read Message
Read Message
Read Message
Previous Topic: crossings and internal connections
Next Topic: Content-Type .xsd files
Goto Forum:
  


Current Time: Wed May 01 08:57:13 CEST 2024