IS:gmlLocations
Jump to navigation
Jump to search
This element does not appear in railML® 3.3 within the IS subschema. It is available only in railML® 3.1, 3.2. Do not hesitate to contact railML.org e.V. for further questions.
Introduction
Documentation
Syntax
Autoexport from the XML-Schema for element IS:gmlLocations of railML® version 3.2 | |
| Documentation | place that EntityIS is in, expressed in GML |
| Subschema | infrastructure |
| Parents* |
balise, baliseGroup, border, bufferStop, crossing, derailerIS, detector, electrificationSection, etcsArea, etcsLevelTransition, genericArea, geometryPoint, gradientCurve, horizontalCurve, keyLockIS, levelCrossingIS, line, loadingGauge, mileageChange, operationalPoint, overCrossing, platform, platformEdge, radioBlockCentreBorder, restrictionArea, serviceSection, signalIS, speedSection, stoppingPlace, switchIS, track, trackBed, trackGauge, trainDetectionElement, trainProtectionElement, trainRadio, tunnelGateIS, underCrossing, weightLimit |
| Children |
lineString (0..*), point (0..*) |
| Attributes:None | |
| *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:gmlLocations of railML® version 3.1 | |
| Documentation | This element is not documented in the schema! |
| Subschema | infrastructure |
| Parents* |
balise, border, bufferStop, crossing, derailerIS, electrificationSection, geometryPoint, gradientCurve, horizontalCurve, keyLockIS, levelCrossingIS, line, loadingGauge, operationalPoint, overCrossing, platform, restrictionArea, serviceSection, signalIS, speedSection, stoppingPlace, switchIS, track, trackBed, trackGauge, trainDetectionElement, trainProtectionElement, trainRadio, underCrossing, weightLimit |
| Children |
lineString (0..*), point (0..*) |
| Attributes:None | |
| *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. | |
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.
The element documentation has been changed.
The parents have been changed.
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.
Removed with version 3.3.
Semantics
Best Practice / Examples
How to handle multiple lineString children?
The interpretation shall be analogous to MultiLineString, which is a collection of Line Strings [1]. Please refer to page 23 of Simple feature access documentation for the examples[2].
How to handle multiple point children?
Please refer to page page 56 of GML documentation for an example[3].
Additional Information
|
Best practices were reviewed by the coordinator (link to the railML® website) of the Timetable subschema on 2025-10-28.