Introduction
Documentation
Syntax
Autoexport from the XML-Schema for element IS:lineString of railML ® version 3.3 |
| Documentation
|
A LineString is a special curve that consists of a single segment with linear interpolation. It is defined by two or more coordinate tuples, with linear interpolation between them. The number of direct positions in the list shall be at least two.
|
| Subschema
|
infrastructure
|
| Parents*
|
gmlLocation
|
| Children
|
description (0..1), descriptionReference (0..1), identifier (0..1), name (0..*), pos (2..*), posList (1..1)
|
Attributes:
- axisLabels: a list of labels of the axes of the grid [gml/3.2.1/grids.xsd] (optional;
NCNameList),
- srsDimension: specifies the number of dimensions represented by the CRS and the positions in the GML Point [1] (optional;
xs:positiveInteger),
- srsName: references the Coordinate Reference System (CRS) that applies to the coordinates of the GML Point [2]. (optional;
xs:anyURI); the URN value for an anyURI that references one object in the European Petroleum Survey Group (EPSG) database shall have the form: urn:ogc:def:objectType:EPSG:version:code. For further information see “Definition identifier URNs in OGC namespace” Version 1.1.2 Open Geospatial Consortium Inc. 2007,
- uomLabels: Ordered list of unit of measure (uom) labels for all the axes of this CRS. The value of the string in the gml:catalogSymbol should be used for this uom labels, after spaces and forbiddden characters are removed. When the axisLabels attribute is included, this attribute shall also be included. When the axisLabels attribute is omitted, this attribute shall also be omitted [gml/3.1.1/base/geometryBasic0d1d.xsd]. (optional;
NCNameList),
- id: The attribute gml:id supports provision of a handle for the XML element representing a GML Object. Its use is mandatory for all GML objects. It is of XML type ID, so is constrained to be unique in the XML document within which it occurs [gmlBase.xsd]. (optional;
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:lineString of railML ® version 3.2 |
| Documentation
|
A LineString is a special curve that consists of a single segment with linear interpolation. It is defined by two or more coordinate tuples, with linear interpolation between them. The number of direct positions in the list shall be at least two.
|
| Subschema
|
infrastructure
|
| Parents*
|
gmlLocations
|
| Children
|
description (0..1), descriptionReference (0..1), identifier (0..1), name (0..*), pos (0..1), posList (0..1)
|
Attributes:
- axisLabels: a list of labels of the axes of the grid [gml/3.2.1/grids.xsd] (optional;
NCNameList),
- srsDimension: specifies the number of dimensions represented by the CRS and the positions in the GML Point [3] (optional;
xs:positiveInteger),
- srsName: references the Coordinate Reference System (CRS) that applies to the coordinates of the GML Point [4]. (optional;
xs:anyURI); the URN value for an anyURI that references one object in the European Petroleum Survey Group (EPSG) database shall have the form: urn:ogc:def:objectType:EPSG:version:code. For further information see “Definition identifier URNs in OGC namespace” Version 1.1.2 Open Geospatial Consortium Inc. 2007,
- uomLabels: Ordered list of unit of measure (uom) labels for all the axes of this CRS. The value of the string in the gml:catalogSymbol should be used for this uom labels, after spaces and forbiddden characters are removed. When the axisLabels attribute is included, this attribute shall also be included. When the axisLabels attribute is omitted, this attribute shall also be omitted [gml/3.1.1/base/geometryBasic0d1d.xsd]. (optional;
NCNameList),
- id: The attribute gml:id supports provision of a handle for the XML element representing a GML Object. Its use is mandatory for all GML objects. It is of XML type ID, so is constrained to be unique in the XML document within which it occurs [gmlBase.xsd]. (optional;
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:lineString of railML ® version 3.1 |
| Documentation
|
This element is not documented in the schema!
|
| Subschema
|
infrastructure
|
| Parents*
|
gmlLocations
|
| Children
|
description (0..1), descriptionReference (0..1), identifier (0..1), name (0..*), pos (0..1), posList (0..1)
|
Attributes:
- srsDimension: This attribute is not documented in the schema! (optional;
xs:positiveInteger),
- srsName: This attribute is not documented in the schema! (optional;
xs:anyURI); the URN value for an anyURI that references one object in the European Petroleum Survey Group (EPSG) database shall have the form: urn:ogc:def:objectType:EPSG:version:code. For further information see “Definition identifier URNs in OGC namespace” Version 1.1.2 Open Geospatial Consortium Inc. 2007,
- id: This attribute is not documented in the schema! (optional;
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.
|
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 attributes 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.
The parents have been changed.
The children have been changed.
Semantics
Best Practice / Examples
Even though child <pos> is allowed by schema, it's recommended to remain consistent with Simple features approach i.e. to model lineString with <posList>[1].
Please refer to Geographic positioning of functional infrastructure for an example.
Additional Information
Notes
Additional Information
| 🗒️
|
This segment provides background information that is not relevant for the certification process.
|
|
|
Best practice was reviewed by the coordinator (link to the railML® website) of the Timetable subschema on 2025-10-28.
Open Issues
References