IS:trackVis: Difference between revisions
| [checked revision] | [checked revision] |
(added notes) |
(added ref for exapmle) |
||
| Line 12: | Line 12: | ||
|constraints= | |constraints= | ||
*{{attr|ref}}: {{railMLType|tGenericRef}}; required | *{{attr|ref}}: {{railMLType|tGenericRef}}; required | ||
|bestpractice= | |||
please refer to [https://wiki2.railml.org/wiki/IS:infrastructureVisualizations <IS:infrastructureVisualizations>] for the example | |||
|notes= | |notes= | ||
Tracks and their children are modelled through <trackElementVis> elements referring to their beginning, end, platforms, switches etc. This is because, in a planar space, the line is represented by two dots. In the railML world, these two dots are <trackBegin> and <trackEnd> elements. The “x” and “y” coordinates are attributes of the <position> child element. | Tracks and their children are modelled through <trackElementVis> elements referring to their beginning, end, platforms, switches etc. This is because, in a planar space, the line is represented by two dots. In the railML world, these two dots are <trackBegin> and <trackEnd> elements. The “x” and “y” coordinates are attributes of the <position> child element. | ||
Revision as of 13:18, 20 April 2023
<trackVis>
|
Scheme description / Schemenbeschreibung
Position of <trackVis> in the XML-Tree / Position von <trackVis> im XML-Baum
- Parent: <lineVis>
- Children: <trackElementVis>
Multiplicity / Anzahl
Semantics / Bedeutung
Visualization of a <track> or a track element.(introduced with version 2.4) (deprecated with version 2.1)
Attributes of <trackVis> / Attribute von <trackVis>
- ref: reference is required because it's the purpose of the element
Syntactic Constraints / Syntaktische Beschränkungen
- ref: xs:IDREF; required
Best practice & Examples / Empfohlene Anwendung & Beispiele
please refer to <IS:infrastructureVisualizations> for the example
Notes / Anmerkungen
Tracks and their children are modelled through <trackElementVis> elements referring to their beginning, end, platforms, switches etc. This is because, in a planar space, the line is represented by two dots. In the railML world, these two dots are <trackBegin> and <trackEnd> elements. The “x” and “y” coordinates are attributes of the <position> child element.
One can find out whether something is visualized by <trackElementVis> or <objectVis> by finding its position in the railML hierarchy. Every child of a <track> element is visualized by <trackElementVis>. In that, operation control points are <objectVis> elements. These have not only a <position> child but also a <size> one.
Open issues / Offene Punkte/Pendenzen
Not yet described. / Noch nicht beschrieben.