Template:InheritConnection: Difference between revisions
| [checked revision] | [checked revision] |
(added maxSpeed definition) |
(added definition for the "straight" attribute) |
||
| Line 28: | Line 28: | ||
:* {{Enum|incoming}}: A track is merging into the principal track, tracks are converging relative to the direction [Jernbanedirektoratet railML 2.4 glossary] | :* {{Enum|incoming}}: A track is merging into the principal track, tracks are converging relative to the direction [Jernbanedirektoratet railML 2.4 glossary] | ||
:* {{Enum|outgoing}}: A track is splitting out from the principal track, tracks are diverging relative to the direction [Jernbanedirektoratet railML 2.4 glossary] | :* {{Enum|outgoing}}: A track is splitting out from the principal track, tracks are diverging relative to the direction [Jernbanedirektoratet railML 2.4 glossary] | ||
:* {{Enum|rightAngled}}: Right-angled crossing has four frogs, four guard rails, one inner guard closed rail etc. [О.М. Даренський З`єднання і схрещення залізничних колій] | :* {{Enum|rightAngled}}: related to the "crossing" connection. Right-angled crossing has four frogs, four guard rails, one inner guard closed rail etc. [О.М. Даренський З`єднання і схрещення залізничних колій] | ||
:* {{Enum|unknown}}: The direction is not known | :* {{Enum|unknown}}: The direction is not known | ||
| Line 37: | Line 37: | ||
* {{Attr|course}}: Relative direction of a converging/diverging track connection facilitated by a switch in a crossing. Course is always defined relative to the switch element (i.e. to stock rail), regardless of global track direction. [Jernbanedirektoratet railML 2.4 glossary] | * {{Attr|course}}: Relative direction of a converging/diverging track connection facilitated by a switch in a crossing. Course is always defined relative to the switch element (i.e. to stock rail), regardless of global track direction. [Jernbanedirektoratet railML 2.4 glossary] | ||
{{missing information|user=[[User:Ferri Leberl|Ferri Leberl]] ([[User talk:Ferri Leberl|talk]]) 16:28, 25 April 2018 (CEST)|topic=the semantics of the enumeration items}} | {{missing information|user=[[User:Ferri Leberl|Ferri Leberl]] ([[User talk:Ferri Leberl|talk]]) 16:28, 25 April 2018 (CEST)|topic=the semantics of the enumeration items}} | ||
:* {{Enum|straight}} | :* {{Enum|straight}} is related to the "crossing" connection. Simple crossing allows going "straight" across. Double switch crossing is a narrow-angled diagonal flat crossing of two lines combined with four pairs of points in such a way as to allow vehicles to change from one straight track to the other, as well as going "straight" across. A train approaching the arrangement may leave by either of the two tracks on the opposite side of the crossing. To reach the third possible exit, the train must change tracks on the slip and then reverse. | ||
:* {{Enum|left}}: A switch track is merging from the left or is diverging leftward from the principal track [Jernbanedirektoratet railML 2.4 glossary] | :* {{Enum|left}}: A switch track is merging from the left or is diverging leftward from the principal track [Jernbanedirektoratet railML 2.4 glossary] | ||
:* {{Enum|right}}: A switch track is merging from the right or is diverging rightward from the principal track [Jernbanedirektoratet railML 2.4 glossary] | :* {{Enum|right}}: A switch track is merging from the right or is diverging rightward from the principal track [Jernbanedirektoratet railML 2.4 glossary] | ||
Revision as of 12:36, 19 October 2022
Usage
This is an Element Template. Element templates are intended to avoid routine work in railML® element documentation. These templates are very specific and are therefore documented uniformely by Template:TemplateDocu. They are collected in Category:Element Template and are based on Template:ElementDocu. They represent Template:ElementDoku with specific values and hand all other parameters through to Template:ElementDoku. If you want to use or handle an Element Template, you have to examine the code to find out, which arguments are set, and you have to be careful, because occationally arguments will be renamed, so that the use of argument names of Template ElementDoku may cause errors.
Arguments
As this is a bulk documentation, we do not explain the specific arguments of element templates.
Dependencies
As this is a bulk documentation, we do not explain the specific dependencies of element templates. You can find out, which other templates the current template supports by following this link. You can find out easily, which other templates the current template employs, as templates are included via {{doubble braces}}.
Example
As this is a bulk documentation, we do not offer specific examples of element templates. You can find in the field examples by following this link.