|
|
Line 10: |
Line 10: |
| {{importComment}} | | {{importComment}} |
| =={{examples}}== | | =={{examples}}== |
| | Until railML 3.3. release the following work-around should be used if there is no information on <location>. |
| | <syntaxhighlight lang=xml> |
| | <genericArea id="111"> |
| | <location> |
| | <circle radius="0"> |
| | <centralPoint> |
| | <pos>0, 0</pos> |
| | </centralPoint> |
| | </circle> |
| | </location> |
| | </genericArea> |
| | </syntaxhighlight> |
| | |
| {{importComment}} | | {{importComment}} |
| =={{Additional Information}}== | | =={{Additional Information}}== |
| ==={{Notes}}=== | | ==={{Notes}}=== |
| ==={{Open issues}}=== | | ==={{Open issues}}=== |
Latest revision as of 12:46, 8 December 2023
Introduction
Documentation
Syntax
Autoexport from the XML-Schema for element IS:genericArea of railML ® version 3.2
|
Documentation
|
A genericArea is a generic element for describing an areal location within the topology network. Its purpose comes from outside by the functional infrastructure elements referencing this area.
|
Subschema
|
infrastructure
|
Parents*
|
genericLocations
|
Children
|
areaLocation (0..*), gmlLocations (0..*), isLimitedBy (0..*), isValid (0..*), linearLocation (0..*), location (1..1), name (0..*), networkLocation (0..*), spotLocation (0..*)
|
Attributes:
- id: the identifier of the object; this can be either of type xs:ID or UUID (obligatory;
xs:string ; patterns: (urn:uuid:)?[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}|{[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}}); compare: Dev:Identities
|
*Notice: Elements may have different parent elements. As a consequence they may be used in different contexts. Please, consider this as well as a user of this wiki as when developing this documentation further. Aspects that are only relevant with respect to one of several parents should be explained exclusively in the documentation of the respective parent element.
|
This element does not appear in railML® 3.1 within the IS subschema. It is available only in railML® 3.2. Do not hesitate to contact railML.org for further questions.
Changes 3.1→3.2
Introduced with version 3.2.
Semantics
Best Practice / Examples
Until railML 3.3. release the following work-around should be used if there is no information on <location>.
<genericArea id="111">
<location>
<circle radius="0">
<centralPoint>
<pos>0, 0</pos>
</centralPoint>
</circle>
</location>
</genericArea>
Additional Information
Notes
Open Issues