CO:speedProfile: Difference between revisions

From railML 3 Wiki
Jump to navigation Jump to search
[unchecked revision][unchecked revision]
(Entwurf)
(Replaced content with "<!--Element '''{{{element}}}'''--> =={{introduction}}== <!--{{#ifeq:{{{comment}}}||{{missing information|topic=the semantics|user=<br>This template was inserted Automatica...")
Tag: Replaced
Line 1: Line 1:
<!--Element '''{{{element}}}'''-->
<!--Element '''{{{element}}}'''-->
=={{introduction}}==
=={{introduction}}==
A {{tag|co|speedProfile}} element specifies a train type for which the speed limit given by a {{tag|is|speedSection}} element shall be valid. A speed profile valid for ETCS can be (among others):
<!--{{#ifeq:{{{comment}}}||{{missing information|topic=the semantics|user=<br>This template was inserted Automatically on import by [[user:Roboter]]}}|{{{comment}}}}}-->
 
{{ImportComment}}
* according to UNISIG SUBSET-026, versions 2.3.0, 3.4.0 or 3.6.0, section 3.11.3.2.1:
** a '''''Basic''''' Static Speed Profile (SPP) [ see section 2.2.1] or
** a '''''Specific''''' Static Speed Profile [ see section 2.2.2],
* according to UNISIG SUBSET-026, versions 2.3.0, 3.4.0 or 3.6.0, section 3.11.4:
** an '''Axle Load''' Speed Profile [ see section 2.3] or
* other speed profiles.
 
Note that the information of '''T'''emporary '''S'''peed '''R'''estrictions (TSR) according to UNISIG SUBSET-026, versions 2.3.0, 3.4.0 or 3.6.0, section 3.11.5, is provided in {{rml}} by a {{tag|is|speedSection}} element using attribute @isTemporary=&quot;true&quot; and child element speedSection/isValid.
 
=== Static Speed Profiles for ETCS ===
 
==== Basic Speed Profile ====
 
;A '''''Basic''''' Static Speed Profile (SPP) is uniquely described by the {{rml}} attribute {{@|isBasicSpeedProfile|CO:speedProfile}}. The modelling in {{rml}} is:
<syntaxhighlight lang=xml>
<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>
</syntaxhighlight>
 
==== Specific Speed Profile ====
 
A '''''Specific''''' Static Speed Profile (SPP) is uniquely described by a value for “Cant Deficiency” SSP category (corresponds to UNISIG trackside variable NC_CDDIFF) and/or by a value for “other specific” SSP categories (corresponds to UNISIG trackside variable NC_DIFF).
 
The UNISIG variable NC_CDDIFF is represented by the the {{rml}} attribute {{tag|co|speedProfile}}/{{@|maxCantDeficiency|CO:speedProfile}}.
 
The UNISIG variable NC_DIFF in the meaning of ETCS Baseline 3 is represented by the combination of the {{rml}} attributes {{tag|co|speedProfile}}/{{tag|co|braking}}/{{@|airBrakeApplicationPosition|CO:braking}} and {{tag|co|speedProfile}}/{{tag|co|trainType}}/{{@|type|CO:trainType}}.
===== a) Cant Deficiency SSP category =====
;Below an example of the modelling in {{rml}} for a “cant deficiency” SSP category:
<syntaxhighlight lang=xml>
<common id="co_01">
  <speedProfiles>
<speedProfile id="ssp_cant1" isBasicSpeedProfile="false"
maxCantDeficiency="100" mVersion="32">
  <name name="ETCS Specific SSP for Cant Deficiency 1"
description="Specific ETCS static speed profile used by trains
which can handle a cant deficiency of 100mm means NC_CDDIFF=1"
language="EN"/>
</speedProfile>
  </speedProfiles>
</common>
</syntaxhighlight>
 
===== b) “Other Specific” SSP category =====
;Below 3 examples of the modelling in {{rml}} for an “other specific” SSP category (brake type depending category):
<syntaxhighlight lang=xml>
<common id="co_01">
  <speedProfiles>
 
<speedProfile id="ssp_freightTrainP" isBasicSpeedProfile="false"
mVersion="32">
  <name name="ETCS Specific SSP for freight trains braked in P position"
description="Specific ETCS static speed profile used by freight trains
braked in P position means NC_DIFF=0" language="EN"/>
  <braking airBrakeApplicationPosition="P"/>
  <trainType type="freight">
  </trainType>
</speedProfile>
 
<speedProfile id="ssp_freightTrainG" isBasicSpeedProfile="false"
mVersion="32">
  <name name="ETCS Specific SSP for freight trains braked in G position"
description="Specific ETCS static speed profile used by freight trains
braked in G position means NC_DIFF=1" language="EN"/>
  <braking airBrakeApplicationPosition="G"/>
  <trainType type="freight">
  </trainType>
</speedProfile>
 
<speedProfile id="ssp_passengerTrainP" isBasicSpeedProfile="false"
mVersion="32">
  <name name="ETCS Specific SSP for passenger trains braked in P position"
description="Specific ETCS static speed profile used by passenger
trains braked in P position means NC_DIFF=2" language="EN"/>
  <braking airBrakeApplicationPosition="P"/>
  <trainType type="passenger">
  </trainType>
</speedProfile>
 
  </speedProfiles>
</common>
</syntaxhighlight>
 
===== c) Combinations of Cant Deficiency SPP and “Other Specific” SSP =====
 
An “'''''ETCS operational''' Train Category''” is uniquely described by the combination of the following 3 variables: “type of the train”, “type of brake” and “cant deficiency”.
<div class="res-img">
[[file:speedProfile2.pdf]]
</div>''ETCS Operational Train Categories (Source: TSI OPE Version 4)
 
Note: The presented page 79 of Figure 2 is taken from Appendix A (version 4) of the Technical Specifications „Operation and traffic management“ from 30/06/15 (File „Appendix A to TSI OPE (EN).pdf“ which is downloaded from https://www.era.europa.eu/activities/technical-specifications-interoperability_en).
 
The added information in Figure 2 concerning the UNISIG variables NC_DIFF and NC_CDDIFF is based on UNISIG SUBSET-026 (version 3.4.0 or 3.6.0), section 7.5.1.82.1 and 7.5.1.83.
 
;Examples:
 
The ETCS operational train category “PASS 2” can be modelled in {{rml}} as illustrated below:
<syntaxhighlight lang=xml>
<common id="co_01">
  <speedProfiles>
<speedProfile id="ssp_PASS2" isBasicSpeedProfile="false"
maxCantDeficiency="130" mVersion="32">
  <name name="Speed Profile PASS 2" description="ETCS static speed profile
for ETCS Operational Train Category PASS 2 means NC_DIFF=2 with
NC_CDDIFF=2" language="EN"/>
  <braking airBrakeApplicationPosition="P"/>
  <trainType type="passenger"/>
</speedProfile>
  </speedProfiles>
</common>
</syntaxhighlight>
The ETCS operational train category “TILT 6” can be modelled in {{rml}} as illustrated below:
<syntaxhighlight lang=xml>
<common id="co_01">
  <speedProfiles>
<speedProfile id="ssp_TILT6" isBasicSpeedProfile="false"
maxCantDeficiency="275" mVersion="32">
  <name name="Speed Profile TILT 6" description="ETCS static speed profile
for ETCS Operational Train Category TILT 6 means NC_DIFF=2 with
NC_CDDIFF=9" language="EN"/>
  <braking airBrakeApplicationPosition="P"/>
  <trainType type="passenger">
  </trainType>
</speedProfile>
  </speedProfiles>
</common>
</syntaxhighlight>
 
===== Static Speed Profiles for ETCS Baseline 2 =====
 
An “'''''International''' Train Category''” according to ETCS Baseline 2 can be modelled in {{rml}} as combination of the 3 {{rml}} attributes {{tag|co|speedProfile}}/{{@|maxCantDeficiency|CO:speedProfile}} (= A *), {{tag|co|speedProfile}}/{{tag|co|trainType}}/{{@|type|CO:trainType}} (= B *) and {{tag|co|speedProfile}}/{{tag|co|braking}}/{{@|airBrakeApplicationPosition|CO:braking}} (= C *) according to the following transformation table.
<div class="res-img">
[[file:speedProfile7.pdf]]
</div>
=== Axle Load Speed Profiles for ETCS ===
 
According to UNISIG SUBSET-026 (version 2.3.0 (d), 3.4.0 or 3.6.0), section 3.11.4, a speed limit valid for a speed section can be determined depending on the axle load. Trains with equal or higher axle load as defined for this speed section have to consider the axle load speed limit. Trains with lower axle load as defined for this speed section will ignore the axle load speed limit. It is possible to provide different speed limits for the same speed section, but each speed limit must be valid for an own axle load.
 
=={{documentation}}==
=={{documentation}}==
==={{syntax}}===
==={{syntax}}===
Line 154: Line 10:
{{importComment}}
{{importComment}}
=={{examples}}==
=={{examples}}==
===Examples for Static Speed Profiles for ETCS===
{{importComment}}
<div class="res-img">
[[file:speedProfile3.pdf]]
</div>''Example Static Speed Profiles for a railway track section''
 
====Extract of a corresponding {{rml}} modelling according to ETCS Baseline 3 (part 1 of 2):====
<syntaxhighlight lang=xml>
<common id="co_01">
  <speedProfiles>
<speedProfile id="ssp_b0" isBasicSpeedProfile="true" mVersion="32">
  <name name="Basic ETCS speed profile" description="international static
speed profile valid in general if no specific profile is applicable
for a train" language="EN"/>
</speedProfile>
…
<speedProfile id="ssp_freightTrainP" isBasicSpeedProfile="false" mVersion="32">
  <name name="ETCS Specific SSP for freight trains braked in P position"
description="Specific ETCS static speed profile used by freight trains
braked in P position means NC_DIFF=0" language="EN"/>
  <braking airBrakeApplicationPosition="P"/>
  <trainType type="freight">
  </trainType>
</speedProfile>
…
<speedProfile id="ssp_passengerTrainP" isBasicSpeedProfile="false" mVersion="32">
  <name name="ETCS Specific SSP for passenger trains braked in P position"
description="Specific ETCS static speed profile used by passenger
trains braked in P position means NC_DIFF=2" language="EN"/>
  <braking airBrakeApplicationPosition="P"/>
  <trainType type="passenger">
  </trainType>
</speedProfile>
  </speedProfiles>
</common>
</syntaxhighlight>
====Extract of a corresponding {{rml}} modelling according to ETCS Baseline 3 (part 2 of 2):====
<syntaxhighlight lang=xml>
<infrastructure id="is_01">
  <functionalInfrastructure>
…
    <speeds>
<speedSection id="spsec100" maxSpeed="80" isTemporary="false" isSignalized="false">
<name name="Speed section Line_1 track_A from KM_11.200 to KM_11.600" 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>
<speedSection id="spsec101_0" maxSpeed="100" isTemporary="false" isSignalized="false">
<name name="Speed section Line_1 track_A from KM_11.600 to KM_12.300" description="Speed section" language="EN"/>
<linearLocation id="spsec101_0_lloc" applicationDirection="normal">
<associatedNetElement netElementRef="ne_102" keepsOrientation="true" posBegin="600.0" posEnd="1300.0">
<linearCoordinateBegin positioningSystemRef="lps01" measure="11600.0"/>
<linearCoordinateEnd positioningSystemRef="lps01" measure="12300.0"/>
</associatedNetElement>
</linearLocation>
<validForSpeedProfile ref="ssp_basic"/>
</speedSection>
<speedSection id="spsec101_1" maxSpeed="120" isTemporary="false" isSignalized="false">
<name name="Speed section Line_1 track_A from KM_11.600 to KM_12.300" description="Speed section" language="EN"/>
<linearLocation id="spsec101_1_lloc" applicationDirection="normal">
<associatedNetElement netElementRef="ne_102" keepsOrientation="true" posBegin="600.0" posEnd="1300.0">
<linearCoordinateBegin positioningSystemRef="lps01" measure="11600.0"/>
<linearCoordinateEnd positioningSystemRef="lps01" measure="12300.0"/>
</associatedNetElement>
</linearLocation>
<validForSpeedProfile ref="ssp_passengerTrainP"/>
</speedSection>
 
 
<speedSection id="spsec102_0" maxSpeed="100" isTemporary="false" isSignalized="false">
<name name="Speed section Line_1 track_A from KM_12.300 to KM_13.500" description="Speed section" language="EN"/>
<linearLocation id="spsec102_0_lloc" applicationDirection="normal">
<associatedNetElement netElementRef="ne_102" keepsOrientation="true" posBegin="1300.0" posEnd="2500.0">
<linearCoordinateBegin positioningSystemRef="lps01" measure="12300.0"/>
<linearCoordinateEnd positioningSystemRef="lps01" measure="13500.0"/>
</associatedNetElement>
</linearLocation>
<validForSpeedProfile ref="ssp_basic"/>
</speedSection>
<speedSection id="spsec102_1" maxSpeed="110" isTemporary="false" isSignalized="false">
<name name="Speed section Line_1 track_A from KM_12.300 to KM_13.500" description="Speed section" language="EN"/>
<linearLocation id="spsec102_1_lloc" applicationDirection="normal">
<associatedNetElement netElementRef="ne_102" keepsOrientation="true" posBegin="1300.0" posEnd="2500.0">
<linearCoordinateBegin positioningSystemRef="lps01" measure="12300.0"/>
<linearCoordinateEnd positioningSystemRef="lps01" measure="13500.0"/>
</associatedNetElement>
</linearLocation>
<validForSpeedProfile ref="ssp_freightTrainP"/>
</speedSection>
<speedSection id="spsec102_2" maxSpeed="140" isTemporary="false" isSignalized="false">
<name name="Speed section Line_1 track_A from KM_12.300 to KM_13.500" description="Speed section" language="EN"/>
<linearLocation id="spsec102_2_lloc" applicationDirection="normal">
<associatedNetElement netElementRef="ne_102" keepsOrientation="true" posBegin="1300.0" posEnd="2500.0">
<linearCoordinateBegin positioningSystemRef="lps01" measure="12300.0"/>
<linearCoordinateEnd positioningSystemRef="lps01" measure="13500.0"/>
</associatedNetElement>
</linearLocation>
<validForSpeedProfile ref="ssp_passengerTrainP"/>
</speedSection>
    </speeds>
…
  </functionalInfrastructure>
</infrastructure>
</syntaxhighlight>
 
=== Examples for Axle Load Speed Profiles for ETCS ===
====Example 1====
The first example shows an axle load speed profile for '''''ETCS baseline 2'''''. The modelling in {{rml}} is:
<syntaxhighlight lang=xml>
<common id="co_01">
  <speedProfiles>
<speedProfile id="asp_20-5t" isBasicSpeedProfile="false" mVersion="16">
  <name name="ETCS Axle Load Speed Profile 20.5 tons"
description="ETCS axle load speed profile for trains with an axle load
equal or higher than 20.5 tons using UNISIG Version 2.3.0d"
language="EN"/>
  <load exceedsAxleLoad="20.5"/>
</speedProfile>
  </speedProfiles>
</common>
</syntaxhighlight>
For ETCS baseline 2, the axle load is presented by axle load categories, given by UNISIG variable M_AXLELOADCAT defined in SUBSET-026 (version 2.3.0(d)) section 7.5.1.62. The values of M_AXLELOAD (represented by {{rml}} attribute {{@|exceedsAxleLoad|CO:load}}) can define a limit in tons (with resolution 0.5t) in the range from 0.0t to 40.0t (means 0.0t, 0.5t, 1.0t, …, 20.0t, …, up to 40.0t) and the special value “above 40.0t”.
 
====Example 2====
The second example shows an axle load speed profile for '''''ETCS baseline 3'''''. The modelling in {{rml}} is:
<syntaxhighlight lang=xml>
<common id="co_01">
  <speedProfiles>
<speedProfile id="asp_C3" isBasicSpeedProfile="false" mVersion="32">
  <name name="ETCS Axle Load Speed Profile C3"
description="ETCS axle load speed profile for trains belonging to axle
load category C3 or higher"
language="EN"/>
  <load exceedsAxleLoadCat="C3"/>
</speedProfile>
  </speedProfiles>
</common>
</syntaxhighlight>
For ETCS baseline 3, the axle load is presented by axle load categories, given by UNISIG variable M_AXLELOADCAT defined in SUBSET-026 (version 3.4.0 or 3.6.0) section 7.5.1.62. The values of M_AXLELOADCAT (represented by {{rml}} attribute {{@|exceedsAxleLoadCat|CO:load}}) can be for example: A, HS17, B1, B2, D4XL and others.
=={{Additional Information}}==
=={{Additional Information}}==
==={{Notes}}===
==={{Notes}}===
==={{Open issues}}===
==={{Open issues}}===
# The reason of the attribute {{@|influence|CO:speedProfile}} in the {{tag|co|speedProfile}} element is not clear.
# The complete section for Axle Load Speed Profile is based on {{rml|3.2 beta-2}} with additional new attribute {{@|exceedsAxleLoad|CO:speedProfile}} as suggested by Christian Rahmig in the {{rml}} web meeting from 20th September 2021.<br />
Additionally, the this document includes the new attribute {{@|exceedsAxleLoadCat|CO:speedProfile}}. The values of {{@|exceedsAxleLoadCat|CO:speedProfile}} should be defined by the existing “rail3:tLineCategoryExt” and added by the ETCS value “HS17” (see section 2.6).
The new attribute {{@|exceedsAxleLoadCat|CO:speedProfile}} is to be discussed in {{rml}} working group “ETCS Track Net”: Should it be possible to provide both a) the “rail3:tLineCategoryExt” values and b) “tons limits” or only one of them?
==== ''Section to be deleted if discussions to axle load have been finished:'' Relationship between the Axle Load Profiles of ETCS Baseline 2 and 3 ====
This section has no relation to the modelling of {{rml}}. This section provides background information how the UNISIG variables concerning Axle Load Speed Profiles have to be transformed in case a train with an ETCS baseline 3 onboard unit is running on a railway line equipped with ETCS baseline 2 trackside devices.
The relation between the axle load speed profiles of M_AXLELOAD (as used in ETCS Baseline 2) and M_AXLELOADCAT (as used in ETCS Baseline 3) is presented by UNISIG SUBSET-026 (version 3.4.0 or 3.6.0), section 6.
=====The transformation from M_AXLELOAD to M_AXLELOADCAT is presented in SUBSET-026 (version 3.4.0 or 3.6.0), section 6.6.3.2.3 [5]:=====
[[File:speedProfile4.pdf]]
Figure 4: Transformation from M_AXLELOAD to M_AXLELOADCAT (Source: UNISIG SUBSET-026, version 3.6.0, section 6.6.3.2.3 [5])
{{note|Figure 4 is applicable when a train equipped with ETCS onboard unit on basis of ETCS Baseline 3 receives a trackside message on basis of ETCS Baseline 2.}}
=====The transformation from M_AXLELOADCAT to M_AXLELOAD is presented in SUBSET-026 (version 3.4.0 or 3.6.0), section 6.6.3.4.5 [3d]:=====
[[File:speedProfile5.pdf]]
[[File:speedProfile6.pdf]]
Figure 5: Transformation from M_AXLELOADCAT to M_AXLELOAD (Source: UNISIG SUBSET-026, version 3.6.0, section 6.6.3.4.5 [3d])
Note: Figure 5 is applicable when a train equipped with ETCS onboard unit on basis of ETCS Baseline 3 sends a message to an RBC which works on basis of ETCS Baseline 2.

Revision as of 21:14, 20 December 2021

Introduction

Documentation

Syntax

Autoexport from the XML-Schema for element CO:speedProfile of railML® version 3.2
Documentation This element is not documented in the schema!
Subschema common
Parents* speedProfiles
Children braking (0..1), load (0..1), name (0..*), tilting (0..1), trainType (0..*)
Attributes:
  • isBasicSpeedProfile: boolean flag to identify basic speed profiles;
    if NO, then further information need to be defined, e.g. trainType, braking or maxCantDeficiency (optional; xs:boolean),

  • mVersion: corresponds to ETCS variable M_VERSION (optional; xs:nonNegativeInteger),

  • influence: This attribute is not documented in the schema! (optional; xs:string)
Possible values:
  • decreasing
  • increasing,

  • maxCantDeficiency: the maximum cant deficiency provided in mm (80..300) (optional; xs:integer; minInclusive: 80; maxInclusive: 300),

  • id: unique identifier (obligatory; xs:string; patterns: (urn:uuid:)?[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}|{[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}}); 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 CO:speedProfile of railML® version 3.1
Documentation This element is not documented in the schema!
Subschema common
Parents* speedProfiles
Children braking (0..1), load (0..1), name (0..*), tilting (0..1), trainType (0..1)
Attributes:
  • influence: This attribute is not documented in the schema! (optional; xs:string)
Possible values:
  • increasing
  • decreasing,

  • id: unique identifier (optional; xs:ID; patterns: (urn:uuid:)?[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}|{[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}}); 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

The children have changed.

The attributes have been changed.

Semantics

Best Practice / Examples

Additional Information

Notes

Open Issues

Retrieved from "https://wiki3.railml.org/index.php?title=CO:speedProfile&oldid=5468"