IS:trackVis: Difference between revisions
| [checked revision] | [checked revision] |
(removing DEPRECATED flag) |
(Link internalized) |
||
| (9 intermediate revisions by 3 users not shown) | |||
| Line 3: | Line 3: | ||
|parent={{IS:Tag|lineVis}} | |parent={{IS:Tag|lineVis}} | ||
|childs={{IS:Tag|trackElementVis}} | |childs={{IS:Tag|trackElementVis}} | ||
| | |minocc=0 | ||
|maxocc=∞ | |||
|intro=2.4 | |||
|depr=2.1 | |||
|semantics=Visualization of a {{tag|is|track}} or a track element. | |||
|ownAttributes= | |ownAttributes= | ||
*{{attr|ref}}: reference is required because it's the purpose of the element | *{{attr|ref}}: reference is required because it's the purpose of the element | ||
|constraints= | |constraints= | ||
*{{attr|ref}}: {{railMLType|tGenericRef}}; required | *{{attr|ref}}: {{railMLType|tGenericRef}}; required | ||
|bestpractice= | |||
please refer to {{tag|is|infrastructureVisualizations}} for an example | |||
|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 {{rml}} 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 {{eml}} 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. | |||
}} | }} | ||
Latest revision as of 15:11, 20 May 2024
<trackVis>
|
Schema description / Schemabeschreibung
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 <infrastructureVisualizations> for an 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 Template:Eml 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.