IS:switchToLevel: Difference between revisions

From railML 3 Wiki
Jump to navigation Jump to search
[checked revision][checked revision]
(Created page IS:switchToLevel using XSD2MediaWiki Converter 1.0.6)
 
(added introduction taken from ETCS working group material)
Line 1: Line 1:
<!--Element '''{{{element}}}'''-->
<!--Element '''{{{element}}}'''-->
=={{introduction}}==
=={{introduction}}==
<!--{{#ifeq:{{{comment}}}||{{missing information|topic=the semantics|user=<br>This template was inserted Automatically on import by [[user:Roboter]]}}|{{{comment}}}}}-->
The {{IS:Tag|switchToLevel}} element contains information about to which ETCS level the vehicle shall transition and the length of the acknowledgement area.
{{ImportComment}}
=={{documentation}}==
=={{documentation}}==
==={{syntax}}===
==={{syntax}}===

Revision as of 18:18, 11 January 2024

Introduction

The <switchToLevel> element contains information about to which ETCS level the vehicle shall transition and the length of the acknowledgement area.

Documentation

Syntax

Autoexport from the XML-Schema for element IS:switchToLevel of railML® version 3.2
Documentation destination of ETCS level switching in order of priority
Subschema infrastructure
Parents* etcsLevelTransition
Children None
Attributes:
  • lengthOfAcknowledgement: length of acknowledgement area in meters (optional; xs:decimal),

  • levelType: specifies whether interlocking type is interoperable (obligatory; xs:string; patterns: other:w{2,})
Possible values:
  • ETCS
  • NTC: national train control system,

  • levelValue: characterizes level of ETCS (obligatory; xs:positiveInteger),

  • priority: priority of all supported level from the highest to the lowest one as defined in chapter 5.10.2 of the Subset 26 specification. Lower numbers mean higher priority (the highest possible priority is 0). (optional; xs:nonNegativeInteger)
*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.

This element does not appear in railML® 3.1 within the IS subschema. It is available only in railML® 3.2. Do not hesitate to contact railML.org for further questions.


Changes 3.1→3.2

Introduced with version 3.2.

Semantics

Best Practice / Examples

Additional Information

Notes

Open Issues