Home » railML newsgroups » railML.infrastructure » meaning of 'up' and 'down' in mileageChange.dir and track.mainDir
| meaning of 'up' and 'down' in mileageChange.dir and track.mainDir [message #285] |
Mon, 26 March 2012 11:01  |
Dirk Bräuer
Messages: 313
Registered: August 2008
|
Senior Member |
|
|
Hallo allerseits,
Ich habe beim Erstellen von Beispielen zur Kilometrierung
(http://www.irfp.de/download/railml_doku_beispiele.pdf, Seiten 4 ff.)
quasi festgelegt, dass die Ausprägungen 'up' und 'down' der Attribute
mileageChange.dir und track.mainDir streng numerisch ("hochzählen",
"runterzählen") zu interpretieren sind und damit vom britischen
Sprachgebrauch abweichen, wo 'up' = "in Richtung London" und 'down' = "weg
von London" bedeuten.
Außerdem habe ich festgelegt, dass sich up/down von 'mainDir' immer auf
die _relative_ Kilometrierungsrichtung beziehen und damit abweichen vom
Attribut mileageChange.dir, wo sich 'dir' natürlich auf die absolute
Kilometrierungsrichtung bezieht. (Da es dort das Attribut 'absPos' gibt,
wäre es konsequenter, wenn es auch 'absDir' hieße.)
Der Grund für die Festlegung von track.mainDir auf relative
Kilometrierungsrichtung ist, dass sich track.mainDir immer auf das
_gesamte_ Gleis bezieht, während die absolute Kilometrierungsrichtung ja
eben innerhalb des Gleises mehrfach wechseln kann und damit nicht
eindeutig wäre.
Falls dies keine Zustimmung trifft, bitte ich um kurzfristigen Einspruch
zwecks Korrektur der Beispiele.
Danke!
---
In my examples on mileage I wrote that the values 'up' and 'down' of the
attributes 'mileageChange.dir' and 'track.mainDir' relate to numerical
interpretation (raising, falling = "to count up or down"). Therefore, they
differ from the typical usage in British English where 'up' relates on
"direction to London" and 'down' relates on "direction away from London"..
Additionally, I decided that up & down of 'mainDir' always refer to the
_relative_ mileage direction and therefore differ from the usage of the
attribute mileageChange.dir, where 'dir' of course refers to the
_absolute_ mileage direction.
The reason for this decision is that 'track.mainDir' always applies to the
whole track while the absolute mileage direction may change (several
times) along this track. Therefore, the absolute mileage direction is not
unique.
--
Erstellt mit Operas revolutionärem E-Mail-Modul: http://www.opera.com/mail/
|
|
|
|
| Re: meaning of 'up' and 'down' in mileageChange.dir and track.mainDir [message #295 is a reply to message #285] |
Thu, 05 April 2012 00:07  |
Christian Rahmig
Messages: 151
Registered: January 2011
|
Senior Member |
|
|
Hello Dirk,
> Ich habe beim Erstellen von Beispielen zur Kilometrierung
> (http://www.irfp.de/download/railml_doku_beispiele.pdf, Seiten 4 ff.)
> quasi festgelegt, dass die Ausprägungen 'up' und 'down' der Attribute
> mileageChange.dir und track.mainDir streng numerisch ("hochzählen",
> "runterzählen") zu interpretieren sind und damit vom britischen
> Sprachgebrauch abweichen, wo 'up' = "in Richtung London" und 'down' =
> "weg von London" bedeuten.
Yes, your understanding of the direction attribute is correct. It always
relates directly to the direction of the increasing position value.
> Außerdem habe ich festgelegt, dass sich up/down von 'mainDir' immer auf
> die _relative_ Kilometrierungsrichtung beziehen und damit abweichen vom
> Attribut mileageChange.dir, wo sich 'dir' natürlich auf die absolute
> Kilometrierungsrichtung bezieht. (Da es dort das Attribut 'absPos' gibt,
> wäre es konsequenter, wenn es auch 'absDir' hieße.)
Consequently, also mileageChange elements need to be referenced to the
direction of the track, the so-called "relative direction" as you wrote
since they are elements on the track. Therefore the track's direction
parameter should be used as a reference. So, there doesn't exist an
"absolute direction" as it would be (like the absolute position) not unique.
Any comments from other users of the railML infrastructure schema? How
do you understand the direction parameter in the element <mileageChange>?
Best regards
---
Christian Rahmig
railML.infrastructure coordinator
|
|
|
|
| Re: meaning of 'up' and 'down' in mileageChange.dir and track.mainDir [message #299 is a reply to message #285] |
Fri, 13 April 2012 16:39 |
Susanne Wunsch railML
Messages: 0
Registered: January 2020
|
|
|
|
Dirk Bräuer <dirkbraeuer(at)irfpde> writes:
> Ich habe beim Erstellen von Beispielen zur Kilometrierung
> (http://www.irfp.de/download/railml_doku_beispiele.pdf, Seiten 4 ff.)
> quasi festgelegt, dass die Ausprägungen 'up' und 'down' der Attribute
> mileageChange.dir und track.mainDir streng numerisch ("hochzählen",
> "runterzählen") zu interpretieren sind und damit vom britischen
> Sprachgebrauch abweichen, wo 'up' = "in Richtung London" und 'down' =
> "weg von London" bedeuten.
Zur nächsten größeren Version soll diese Aufzählung in "raising" und
"falling" umbenannt werden. Siehe Trac Ticket #145. [1]
> abweichen vom Attribut mileageChange.dir, wo sich 'dir' natürlich auf
> die absolute Kilometrierungsrichtung bezieht. (Da es dort das
> Attribut 'absPos' gibt, wäre es konsequenter, wenn es auch 'absDir'
> hieße.)
Zur nächsten größeren Version soll dieses Attribut in "absDir" umbenannt
werden. Siehe Trac Ticket #144. [2]
> ---
> In my examples on mileage I wrote that the values 'up' and 'down' of
> the attributes 'mileageChange.dir' and 'track.mainDir' relate to
> numerical interpretation (raising, falling = "to count up or
> down"). Therefore, they differ from the typical usage in British
> English where 'up' relates on "direction to London" and 'down'
> relates on "direction away from London".
From the next major release on this enumeration values should be renamed
to "raising" and "falling". See also Trac ticket #145 [1]
> therefore differ from the usage of the attribute mileageChange.dir,
> where 'dir' of course refers to the _absolute_ mileage direction.
From the next major release on this attribute should be renamed to
"absDir". See also Trac ticket #144 [2]
Dirk, thanks for your suggestions.
Kind regards...
Susanne
[1] http://trac.assembla.com/railML/ticket/145
[2] http://trac.assembla.com/railML/ticket/144
--
Susanne Wunsch
Schema Coordinator: railML.common
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 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 |
Dirk Bräuer
Messages: 313
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.
|
|
|
|
|
|
|
|
| Re: meaning of 'up' and 'down' in mileageChange.dir and track.mainDir [message #2110 is a reply to message #299] |
Mon, 21 January 2019 13:15 |
christian.rahmig
Messages: 458
Registered: January 2016
|
Senior Member |
|
|
Dear all,
Am 13.04.2012 um 16:39 schrieb Susanne Wunsch:
> [...]
>> In my examples on mileage I wrote that the values 'up' and 'down' of
>> the attributes 'mileageChange.dir' and 'track.mainDir' relate to
>> numerical interpretation (raising, falling = "to count up or
>> down"). Therefore, they differ from the typical usage in British
>> English where 'up' relates on "direction to London" and 'down'
>> relates on "direction away from London".
>
> From the next major release on this enumeration values should be renamed
> to "raising" and "falling". See also Trac ticket #145 [1]
>
>> therefore differ from the usage of the attribute mileageChange.dir,
>> where 'dir' of course refers to the _absolute_ mileage direction.
>
> From the next major release on this attribute should be renamed to
> "absDir". See also Trac ticket #144 [2]
In railML 3.1, mileage changes are modelled using <anchor> points of
<linearPositioningSystem>. I added a detailed example in the description
of Trac ticket #144 [2]. Considering this proposal, an attribute @dir or
@absDir is not needed.
> [1] http://trac.assembla.com/railML/ticket/145
> [2] http://trac.assembla.com/railML/ticket/144
Best regards
Christian
--
Christian Rahmig - Infrastructure scheme coordinator
railML.org (Registry of Associations: VR 5750)
Phone Coordinator: +49 173 2714509; railML.org: +49 351 47582911
Altplauen 19h; 01187 Dresden; Germany www.railml.org
Christian Rahmig – Infrastructure scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
|
|
|
|
Goto Forum:
Current Time: Sun Sep 08 01:44:18 CEST 2024
|
Members
Search
Help
Login
Home
