Introduction
Documentation
Syntax
Autoexport from the XML-Schema for element IS:genericArea of railML ® version 3.3 |
| 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..*), elementState (0..*), gmlLocation (0..*), isLimitedBy (0..*), isValid (0..*), linearLocation (0..*), location (0..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:ID); 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.
|
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
There exists an overview of all changes between railML® 3.1 and railML® 3.2 on page Dev:Changes/3.2.
Introduced with version 3.2.
Changes 3.2→3.3
There exists an overview of all changes between railML® 3.2 and railML® 3.3 on page Dev:Changes/3.3.
The parents have been changed.
The children have been changed.
The attributes have been changed.
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