Template:InheritDirection: Difference between revisions

From railML 2 Wiki
Jump to navigation Jump to search
[unchecked revision][unchecked revision]
(Created for use in several IS element documentation sites)
 
(Updated using new template (Vorlage:AddAnn))
Line 4: Line 4:
:* {{Enum|down}} This goes opposite to {{Enum|up}} (decreasing relative {{Attr|pos}}ition values).
:* {{Enum|down}} This goes opposite to {{Enum|up}} (decreasing relative {{Attr|pos}}ition values).
:* {{Enum|both}} {{{selfLink|FIXME}}} is valid in both directions.
:* {{Enum|both}} {{{selfLink|FIXME}}} is valid in both directions.
:* {{Enum|unknown}} {{{selfLink|FIXME}}} is restricted to a certain direction, but this direction is not known.<br/> {{Ann| {{{dir|}}} }} <noinclude>[[Category:AttributeTemplate]]</noinclude>
:* {{Enum|unknown}} {{{selfLink|FIXME}}} is restricted to a certain direction, but this direction is not known.{{AddAnn|{{{dir|}}}|{{{dir_de|}}} }} <noinclude>[[Category:AttributeTemplate]]</noinclude>

Revision as of 00:28, 8 December 2011

  • dir: This defines the validity of FIXME along the track. Possible values are:
  • none FIXME 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 FIXME is valid in both directions.
  • unknown FIXME is restricted to a certain direction, but this direction is not known.