Autoexport from the XML-Schema for element IS:speedSection of railML® version 3.3 | |
| Description | locates part of a track where given permanent speed restriction is applicable |
| Subschema | infrastructure |
| Parents* | |
| Children |
name (0..*), isValid (0..*), areaLocation (0..*), linearLocation (0..*), spotLocation (0..*), gmlLocation (0..*), networkLocation (0..*), designator (0..*), typeDesignator (0..*), elementState (0..*), validForSpeedProfile (0..*) |
Attributes:
| |
| *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. | |
IS:speedSection
Introduction
Speed limits are modelled in railML® using speedSection elements in combination with <speedProfile> elements.
-
Speed change in Kyritz (
), Germany, Bahnkonzept, license ‒ with generous permission by the image creator
Documentation
Syntax
Autoexport from the XML-Schema for element IS:speedSection of railML® version 3.2 | |
| Description | locates part of a track where given permanent speed restriction is applicable |
| Subschema | infrastructure |
| Parents* | |
| Children |
name (0..*), isValid (0..*), areaLocation (0..*), linearLocation (0..*), spotLocation (0..*), gmlLocations (0..*), networkLocation (0..*), designator (0..*), external (0..*), typeDesignator (0..*), validForSpeedProfile (0..*) |
Attributes:
| |
| *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:speedSection of railML® version 3.1 | |
| Description | This element is not documented in the schema! |
| Subschema | infrastructure |
| Parents* | |
| Children |
name (0..*), isValid (0..*), areaLocation (0..*), linearLocation (0..*), spotLocation (0..*), gmlLocations (0..*), networkLocation (0..*), designator (0..*), external (0..*), validForSpeedProfile (0..*), any (0..*) |
Attributes:
| |
| *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 children have 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 children have been changed.
The attributes have been changed.
Semantics
|
Best Practice / Examples
A speed limit valid for a speed section is presented in railML® by a <speedSection> element. The <speedSection> element defines the start and end location of the speed section and the maximum speed limit valid for this section.
-
Example of a static speed profile for a railway track section
The modelling in railML® is:
<speedSection id="spsec100" maxSpeed="80" isTemporary="false" isSignalized="false" refersToTrain="endOfTrain"> <name name="JNA-201" description="Speed section" language="EN"/> <linearLocation id="spsec100_lloc" applicationDirection="normal"> <associatedNetElement netElementRef="ne_102" keepsOrientation="true"> <linearCoordinateBegin positioningSystemRef="lps01" measure="11200.0"/> <linearCoordinateEnd positioningSystemRef="lps01" measure="11600.0"/> </associatedNetElement> </linearLocation> <validForSpeedProfile ref="ssp_basic"/> </speedSection>
Each railML® <speedSection> element must reference (at least) one global defined railML® <speedProfile> element. A <speedProfile> element specifies a train type for which the speed limit given by a <speedSection> element shall be valid.
For example a <speedProfile> element can be used to provide for ETCS a Basic Static Speed Profile, a Specific Static Speed Profile (cant deficiency or brake type depending train categories, ETCS Operational Train categories or International Train Categories) or an Axle Load Speed Profile. For detailed information see <speedProfile>.
- Example
<common id="co_01"> <speedProfiles> <speedProfile id="ssp_Basic" isBasicSpeedProfile="true" mVersion="32"> <name name="ETCS Basic SSP" description="Basic ETCS static speed profile used by trains for which no Specific SSP matches" language="EN"/> </speedProfile> </speedProfiles> </common>
Upcomming
Additional Information
Notes
Additional Information
|
Modelling change @refersToTrain in railML3.2 to @endPointValidity in railML 3.3 was triggered by ticket #596.