Autoexport from the XML-Schema for element IS:speedSection of railML® version 3.2 | |
Documentation | This element is not documented in the schema! |
Subschema | infrastructure |
Parents* | speeds |
Children | areaLocation (0..*), designator (0..*), external (0..*), gmlLocations (0..*), isValid (0..*), linearLocation (0..*), name (0..*), networkLocation (0..*), spotLocation (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. |
IS:speedSection
Introduction
Speed limits are modelled in railML® using speedSection elements in combination with <speedProfile> elements.
Documentation
Syntax
Autoexport from the XML-Schema for element IS:speedSection of railML® version 3.1 | |
Documentation | This element is not documented in the schema! |
Subschema | infrastructure |
Parents* | speeds |
Children | any (0..*), areaLocation (0..*), designator (0..*), external (0..*), gmlLocations (0..*), isValid (0..*), linearLocation (0..*), name (0..*), networkLocation (0..*), spotLocation (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. |
Changes 3.1→3.2
The children have 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.
The railML® speedSection element is located in the railML® scheme: “railML/infrastructure/functionalInfrastructure/speeds/speedSection“.
Figure 1: Example 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" posBegin="200.0" posEnd="600.0"> <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 Element (section 2)
- 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>