User:RailML Coord Documentation/IS:speedSection: Difference between revisions

From railML 3 Wiki
Jump to navigation Jump to search
(Created page with "= The element “speedSection” = == Introduction == Speed limits are modelled in {{rml}} using speedSection elements in combination with speedProfile elements. A simple ex...")
 
m (RailML Orga Admin Wiki3 moved page User:Documentation/IS:speedSection to User:RailML Coord Documentation/IS:speedSection: Automatically moved page while renaming the user "Documentation" to "RailML Coord Documentation")
 
(3 intermediate revisions by one other user not shown)
Line 2: Line 2:


== Introduction ==
== Introduction ==
 
Speed limits are modelled in {{rml}} using {{tag|is|speedSection}} elements in combination with {{tag|co|speedProfile}} elements. A simple example is shown [[#examples|below]]. A more complex example is provided in [[CO:speedProfile#Example3|Example 3 of {{rml}} element <speedProfile>]].
Speed limits are modelled in {{rml}} using speedSection elements in combination with speedProfile elements. A simple example is shown in section 1.2. A more complex example is provided in section 2.2.3 of {{rml}} element speedProfile.


== Best Practice / Examples ==
== Best Practice / Examples ==


A speed limit valid for a speed section is presented in {{rml}} 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.
A speed limit valid for a speed section is presented in {{rml}} by a {{tag|is|speedSection}} element. The {{tag|is|speedSection}} element defines the start and end location of the speed section and the maximum speed limit valid for this section.
 
<div class="res-img">
Figure 1: Example Static Speed Profile for a railway track section
[[file:speedProfile1.pdf]]
 
</div>''Example Static Speed Profile for a railway track section''
The modelling in {{rml}} is:
 
&lt;speedSection id=&quot;spsec100&quot; maxSpeed=&quot;80&quot; isTemporary=&quot;false&quot; isSignalized=&quot;false&quot;&gt;
 
&lt;name name=&quot;JNA-201&quot; description=&quot;Speed section&quot; language=&quot;EN&quot;/&gt;
 
&lt;linearLocation id=&quot;spsec100_lloc&quot; applicationDirection=&quot;normal&quot;&gt;
 
&lt;associatedNetElement netElementRef=&quot;ne_102&quot; keepsOrientation=&quot;true&quot;
 
posBegin=&quot;200.0&quot; posEnd=&quot;600.0&quot;&gt;
 
&lt;linearCoordinateBegin positioningSystemRef=&quot;lps01&quot; measure=&quot;11200.0&quot;/&gt;
 
&lt;linearCoordinateEnd positioningSystemRef=&quot;lps01&quot; measure=&quot;11600.0&quot;/&gt;
 
&lt;/associatedNetElement&gt;
 
&lt;/linearLocation&gt;
 
&lt;validForSpeedProfile ref=&quot;ssp_basic&quot;/&gt;
 
&lt;/speedSection&gt;


Each {{rml}} speedSection element must reference (at least) one global defined {{rml}} speedProfile element. A speedProfile element specifies a train type for which the speed limit given by a speedSection element shall be valid.
;The modelling in {{rml}} is:
<syntaxhighlight lang=xml>
<speedSection id="spsec100" maxSpeed="80" isTemporary="false" isSignalized="false">
  <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>
</syntaxhighlight>
Each {{rml}} {{tag|is|speedSection}} element must reference (at least) one global defined {{rml}} {{tag|co|speedProfile}} element. A {{tag|co|speedProfile}} element specifies a train type for which the speed limit given by a {{tag|is|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 X)
For example a {{tag|co|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 X)


;Example:
;Example:
 
<syntaxhighlight lang=xml>
&lt;common id=&quot;co_01&quot;&gt;
<common id="co_01">
 
  <speedProfiles>
&lt;speedProfiles&gt;
<speedProfile id="ssp_Basic" isBasicSpeedProfile="true" mVersion="32">
 
  <name name="ETCS Basic SSP" description="Basic ETCS static
&lt;speedProfile id=&quot;ssp_Basic&quot; isBasicSpeedProfile=&quot;true&quot; mVersion=&quot;32&quot;&gt;
speed profile used by trains for which no Specific SSP matches"
 
language="EN"/>
&lt;name name=&quot;ETCS Basic SSP&quot; description=&quot;Basic ETCS static
</speedProfile>
 
  </speedProfiles>
<blockquote>speed profile used by trains for which no Specific SSP matches&quot;
</common>
 
</syntaxhighlight>
language=&quot;EN&quot;/&gt;
</blockquote>
&lt;/speedProfile&gt;
 
&lt;/speedProfiles&gt;
 
&lt;/common&gt;


== Additional Information ==
== Additional Information ==
=== Notes ===
=== Notes ===
''--- (no notes) ---''
=== Open Issues ===
=== Open Issues ===
 
# Shall the location of {{tag|is|speedSection}} in {{rml}} be provided as linear element or as area element?
# Shall the location of “speedSection” in {{rml}} provided as linear element or as area element?
# A {{rml}} attribute for {{tag|is|speedSection}} is missing to represent the UNISIG variable Q_FRONT.
# A {{rml}} attribute in the speedSection element is missing to represent the UNISIG variable Q_FRONT.

Latest revision as of 19:18, 4 January 2023

The element “speedSection”

Introduction

Speed limits are modelled in railML® using <speedSection> elements in combination with <speedProfile> elements. A simple example is shown below. A more complex example is provided in Example 3 of railML® element <speedProfile>.

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.

SpeedProfile1.pdf

Example Static Speed Profile for a railway track section

The modelling in railML® is
<speedSection id="spsec100" maxSpeed="80" isTemporary="false" isSignalized="false">
   <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 X)

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>

Additional Information

Notes

Open Issues

  1. Shall the location of <speedSection> in railML® be provided as linear element or as area element?
  2. A railML® attribute for <speedSection> is missing to represent the UNISIG variable Q_FRONT.