Home » railML newsgroups » railML.infrastructure » meaning of 'up' and 'down' in mileageChange.dir and track.mainDir
Re: meaning of 'up' and 'down' in mileageChange.dir and track.mainDir [message #373 is a reply to message #371] Tue, 02 October 2012 18:44 Go to previous messageGo to previous message
Dirk Bräuer is currently offline  Dirk Bräuer
Messages: 311
Registered: August 2008
Senior Member
Dear Christian,

> the attributes "type" ('missing', 'overlapping') and "absPosIn" will
> become optional with the next major release since this change is not
> compatible with railML 2.x.

Accepted - with a deep regret.

> In addition to the changes for the element <mileageChange>, it is now
> possible to define an absolute (mileage) direction at the beginning of a
> track, too. The type tTrackNode has been extended by the new attribute
> "absDir" providing the values 'raising' and 'falling'.

At least for 3.0, I would prefer a solution which describes the mileages
in _one_ structure for easier parsing. (With the above mentioned changes,
the mileages currently are described in the structures <trackBegin>,
<trackEnd>, and <mileageChanges>.)

> In order to keep a proper syntax, the new optional attribute "absPosIn"
> is introduced in the trackEnd element for defining the mileage of the
> (incoming) line. Thus, the track node provides the same parameters
> required for the mileage description like the mileageChange element.

Thank you.

> The <mileageChange> element gets a new optional attribute "absDir",
> which provides the values 'raising' and 'falling'. It will replace the
> current attribute "dir" with the next major release and will become
> required then.

Introducing "absDir": Very good, thank you.

Short remark (only for keeping it in mind for 3.0): Making it required
from 3.0 should not be necessary. 'AbsDir' can be calculated by comparing
two neighboring 'absPos' (better: 'absPosOut' from the previous and
'absPosIn' from the next change). From the triplet 'absPosOut', 'absPosIn'
and 'absDir' of one section, one is redundant. Since we want to allow
'stretching' of absolute mileage, 'absDir' is redundant - we cannot omit
'absPosOut' and 'absPosIn' to calculate whether and how much the mileage
is stretched.

Than you again,
with best regards,
Dirk.
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Infrastructure registers
Next Topic: Include track length information in topology
Goto Forum:
  


Current Time: Tue May 07 11:24:12 CEST 2024