Home » railML newsgroups » railML.infrastructure » the use of @dir in railML. (@dir)
Values of attribute @dir [message #1968 is a reply to message #1959] Mon, 17 September 2018 12:15 Go to previous messageGo to previous message
christian.rahmig is currently offline  christian.rahmig
Messages: 436
Registered: January 2016
Senior Member
Dear Torben,

here comes answer part 2...

Am 12.09.2018 um 14:57 schrieb Torben Brand:
> [...]
> @dir denotes the validity of the objects as seen from the
> direction of travel by the train. Or as it says similar in
> the gradientChange wiki: "dir: This defines the validity
> of gradientChange along the track."
> [...]
>
> Possible values are:
> • none: gradientChange has no direction restriction.
> • up: This denotes the direction from
> the <trackBegin> to the <trackEnd> (increasing
> relative position values).
> • down: This goes opposite to up (decreasing
> relative position values).
> • both: gradientChange is valid in both directions.
> • unknown: gradientChange is restricted to a certain
> direction, but this direction is not known.
>
> First having the value "none" and "both" make no sense. This
> as they both cover the same thing (glass is half full or
> half empty)

I think you are right. The value "none" does not make much sense since
all possibilities of direction validity are covered by the other values:
* up (for elements being valid in up direction)
* down (for elements being valid in down direction)
* both (for elements being valid in both directions)

And if an information is unknown, you may leave this optional attribute
empty.

So, we may put it on the agenda for a next railML version? By the way,
in railML 3, the new attribute @applicationDir has been implemented
exactly that way - with only three values. Instead of "up" and "down"
the terms "normal" and "reverse" are being used, but the meaning is the
same.

@all: Do you have any examples where you use direction enumeration
values "none" or "unknown"?

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
 
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: [railML2] Clearer modelling of the signal designation
Next Topic: [railML 3.1] level crossing parameters
Goto Forum:
  


Current Time: Sat Apr 27 05:49:41 CEST 2024