IS:gmlLocation

From railML 3 Wiki
Jump to navigation Jump to search

Introduction

The Geography Markup Language (GML) is the XML grammar defined by the Open Geospatial Consortium (OGC) to express geographical features. GML serves as a modeling language for geographic systems as well as an open interchange format for geographic transactions on the Internet [1].

Documentation

Syntax

Autoexport from the XML-Schema for element IS:gmlLocation of railML® version 3.3
    
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, linesideElectronicUnitIS, loadingGauge, loop, mileageChange, operationalPoint, overCrossing, platform, platformEdge, radioBlockCentreBorder, restrictionArea, roadSideBarriers, roadSideLights, serviceSection, signalIS, speedSection, stoppingPlace, switchIS, track, trackBed, trackGauge, trainDetectionElement, trainProtectionElement, trainRadio, tunnelGateIS, underCrossing, weightLimit

Children

lineString (1..1), point (1..1)

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.


 

This element does not appear in railML® 3.2 within the IS subschema. It is available only in railML® 3.3. Do not hesitate to contact railML.org e.V. for further questions.
This element does not appear in railML® 3.1 within the IS subschema. It is available only in railML® 3.3. Do not hesitate to contact railML.org e.V. for further questions.


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.
Introduced with version 3.3.

Semantics

Best Practice / Examples

Additional Information

Notes

Open Issues