CO:speedProfile: Difference between revisions

From railML 3 Wiki
Jump to navigation Jump to search
[checked revision][checked revision]
(→‎{{introduction}}: – thanks to Karl Jerosch & Siemens)
Line 4: Line 4:


* according to UNISIG SUBSET-026, versions 2.3.0, 3.4.0 or 3.6.0, section 3.11.3.2.1:
* 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 '''''Basic''''' Static Speed Profile (SPP) or
** a '''''Specific''''' Static Speed Profile [ see section 2.2.2],
** a '''''Specific''''' Static Speed Profile,
* according to UNISIG SUBSET-026, versions 2.3.0, 3.4.0 or 3.6.0, section 3.11.4:
* 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
** an '''Axle Load''' Speed Profile or
* other speed profiles.
* other speed profiles.



Revision as of 18:22, 15 January 2024

Introduction

A speedProfile element specifies a train type for which the speed limit given by a speedSection element shall be valid. A speed profile valid for ETCS can be (among others):

  • 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) or
    • a Specific Static Speed Profile,
  • 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 or
  • other speed profiles.

Note that the information of Temporary Speed Restrictions (TSR) according to UNISIG SUBSET-026, versions 2.3.0, 3.4.0 or 3.6.0, section 3.11.5, is provided in railML® by a speedSection element using attribute @isTemporary="true" and child element speedSection/isValid.

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