Organisation code
DP
IRI: http://data.europa.eu/949/organisationCode
- Parameter of
-
Organisation Role
- General Information
-
- Number:
- 1.1.0.0.0.1
- 1.1.1.1.8.1
- 1.2.1.0.0.1
- 1.2.1.0.5.1
- 1.2.1.0.6.1
- 1.2.2.0.0.1
- 1.2.2.0.5.1
- XML Name:
- SOLIMCode
- OPTrackPlatformIMCode
- OPSidingIMCode
- OPTrackTunnelIMCode
- OPSidingTunnelIMCode
- SOLTunnelIMCode
- OPTrackIMCode
- Deadline:
- In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
- Belongs to parameters group
-
Section of line generic information
(
1.1.0.0.0
)
-
Running track generic information
(
1.1.1.0.0
)
-
Tunnel
(
1.1.1.1.8
|
1.2.1.0.5
|
1.2.2.0.5
)
-
Platform
(
1.2.1.0.6
)
-
Siding
(
1.2.2
)
-
Identifier
- Data Format
-
- Data Presentation
-
String
- Format:
- AAAA
- Flags
-
- Applicability Flags:
- Y
- Validation
-
- Validation Rules:
-
Organisation Code
Comment: Four alpha-numeric code allocated by ERA to a body. It represent's the Infrastructure Manager (IM) code in RINF. Infrastructure manager means any body or firm responsible in particular for establishing, managing and maintaining railway infrastructure, including traffic management and control-command and signalling; the functions of the infrastructure manager on a network or part of a network may be allocated to different bodies or firms. Definition in (Article 3(2)).
Message: organisationCode (1.2.1.0.6.1, 1.1.0.0.0.1, 1.1.1.1.8.1, 1.2.1.0.0.1, 1.2.1.0.5.1, 1.2.2.0.0.1, 1.2.2.0.5.1): An OrganisationRole must have exactly one value of organisationCode. This error may be due to not having a value, having more than one value, having a value that is not a string or having a value that is not a four character code
- OPE TSI References
-
- Appendix D2 Index
- 1.1
- Additional Information
-
- General explanation:
- The Code is a unique identifier for the Infrastructure Manager and it shall be verified on national level.
- If the IM is subject to TAF/TAP TSIs, it corresponds to the code used in TAF/TAP TSIs.
- In other cases, it corresponds to the "organisation code" assigned by the Agency for the specific needs of the RINF.
Each Section of Line shall concern only one IM.
To be able to follow the "only once" principle, the infrastructure manager code is a property of the organisation having the role of infrastructuer manager. For data provision, a subset of elements with common characteristics should be created with the era:infrastructureManager property having as value the instance of the infrastructure mananger role.
-
- Example:
- Simplified example:
:ABCD_IM rdf:type era:OrganisationRole;
era:hasOrganisationRole era-skos:InfrastructureManager.
era:organisationCode "ABCD".
:0000_IM rdf:type era:OrganisationRole;
era:hasOrganisationRole era-skos:InfrastructureManager.
era:organisationCode "0000".
:imNetwork rdf:type era:SubsetWithCommonCharacteristics;
era:infrastructureManager :ABCD_IM.
#IM code parameter as a common characteristic
:track1 rdf:type era:Track;
era:belongsTo :imNetwork.
#IM Code parameter - directly attached to a track
:track2 rdf:type era:Track;
era:infrastructureManager :0000_IM.
National line identification
OP
IRI: http://data.europa.eu/949/nationalLine
- Parameter of
-
Section Of Line
- General Information
-
- Number:
- 1.1.0.0.0.2
- XML Name:
- SOLLineIdentification
- Belongs to parameters group
-
Section of line generic information
(
1.1.0.0.0
)
- Data Format
-
- Data Presentation
-
Linear Positioning System
- Validation
-
- Validation Rules:
-
National Line So L
Comment: Unique line identification or unique line number within Member State.
Message: nationalLine (1.1.0.0.0.2): Each SoL belongs to exactly one linear positioning system. This error is due to not having a value, having more than one value, or having a value that is not an instance of LinearPositioningSystem.
- Additional Information
-
- General explanation:
- Each SoL can belong to only one national line.
In case when SoL is the track connecting between OPs within big node (resulting from division of big station into several smaller) the line can be identified using the name of this track.
Operational point at start of section of line
OP
IRI: http://data.europa.eu/949/opStart
- Parameter of
-
Section Of Line
- General Information
-
- Number:
- 1.1.0.0.0.3
- XML Name:
- SOLOPStart
- Deadline:
- In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
- Belongs to parameters group
-
Section of line generic information
(
1.1.0.0.0
)
- Data Format
-
- Data Presentation
-
Operational Point
- Flags
-
- Applicability Flags:
- Y
- Validation
-
- Validation Rules:
-
Op Start Exists
Comment: Each SoL may have only one start OP, and each OP has unique OP ID within the MS. The “uniqueOPID” is defined in parameter 1.2.0.0.0.2. Each SoL has the principal direction of the traffic defined by increasing kilometres running from the start OP to the end OP. That is why the start OP is always located at lowest kilometre of the line within the SoL. Data collected in the UK in miles will be transformed to km for uploading to the RINF application. The OP ID must exist in the MS file of RINF. The value of this parameter must be different from 1.1.0.0.0.4. No validation will be performed by RINF application regarding which is the start and which the end OP. This requires national verification.
Message: opStart (1.1.0.0.0.3): There is an error with the SoL {$this} ({?solLabel}) and its OP start which does not exist.
-
Op Start
Comment: Each SoL may have only one start OP, and each OP has unique OP ID within the MS. The “uniqueOPID” is defined in parameter 1.2.0.0.0.2. Each SoL has the principal direction of the traffic defined by increasing kilometres running from the start OP to the end OP. That is why the start OP is always located at lowest kilometre of the line within the SoL. Data collected in the UK in miles will be transformed to km for uploading to the RINF application. The OP ID must exist in the MS file of RINF. The value of this parameter must be different from 1.1.0.0.0.4. No validation will be performed by RINF application regarding which is the start and which the end OP. This requires national verification.
Message: opStart (1.1.0.0.0.3): There must be at most one OP start for this section of line and it must be different from the OP end.
- OPE TSI References
-
- Appendix D2 Index
- 3.1.1
- Additional Information
-
- General explanation:
- Each SoL may have only one start OP, and each OP has unique OP ID within the MS. The “uniqueOPID” is defined in parameter 1.2.0.0.0.2.
Each SoL has the principal direction of the traffic defined by increasing kilometres running from the start OP to the end OP.
That is why the start OP is always located at lowest kilometre of the line within the SoL.
No validation will be performed by RINF application regarding which is the start and which the end OP. This requires IM's verification.
Operational point at end of section of line
OP
IRI: http://data.europa.eu/949/opEnd
- Parameter of
-
Section Of Line
- General Information
-
- Number:
- 1.1.0.0.0.4
- XML Name:
- SOLOPEnd
- Deadline:
- In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
- Belongs to parameters group
-
Section of line generic information
(
1.1.0.0.0
)
- Data Format
-
- Data Presentation
-
Operational Point
- Flags
-
- Applicability Flags:
- Y
- Validation
-
- Validation Rules:
-
Op End
Comment: Each SoL may have only one end OP, and each OP has unique OP ID within the MS. The “uniqueOPID” is defined in parameter 1.2.0.0.0.2. Each SoL has the principal direction of the traffic defined by increasing kilometres running from the start OP to the end OP. That is why the start OP is always located at lowest kilometre of the line within the SoL. Data collected in the UK in miles will be transformed to km for uploading to the RINF application. The OP ID must exist in the MS file of RINF. The value of this parameter must be different from 1.1.0.0.0.3. No validation will be performed by RINF application regarding which is the start and which the end OP. This requires national verification.
Message: opEnd (1.1.0.0.0.4): There must be at most one OP end for this section of line and it must be different from the OP start.
-
Op End Exists
Comment: Each SoL may have only one start OP, and each OP has unique OP ID within the MS. The “uniqueOPID” is defined in parameter 1.2.0.0.0.2. Each SoL has the principal direction of the traffic defined by increasing kilometres running from the start OP to the end OP. That is why the start OP is always located at lowest kilometre of the line within the SoL. Data collected in the UK in miles will be transformed to km for uploading to the RINF application. The OP ID must exist in the MS file of RINF. The value of this parameter must be different from 1.1.0.0.0.3. No validation will be performed by RINF application regarding which is the start and which the end OP. This requires national verification.
Message: opEnd (1.1.0.0.0.4): There is an error with the SoL {$this} ({?solLabel}) and its OP end which does not exist.
- OPE TSI References
-
- Appendix D2 Index
- 3.1.2
- Additional Information
-
- General explanation:
- Each SoL may have only one end OP, and each OP has unique OP ID within the MS. The “uniqueOPID” is defined in parameter 1.2.0.0.0.2.
Each SoL has the principal direction of the traffic defined by increasing kilometres running from the start OP to the end OP.
That is why the end OP is always located at highest kilometre of the line within the SoL.
No validation will be performed by RINF application regarding which is the start and which the end OP. This requires IM's verification.
Length of section of line
DP
IRI: http://data.europa.eu/949/lengthOfSectionOfLine
- Parameter of
-
Section Of Line
- General Information
-
- Number:
- 1.1.0.0.0.5
- XML Name:
- SOLLength
- Deadline:
- In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
- Belongs to parameters group
-
Section of line generic information
(
1.1.0.0.0
)
-
Length
- Data Format
-
- Data Presentation
-
Double
- Unit of Measure:
-
Kilometre
- Flags
-
- Applicability Flags:
- Y
- Validation
-
- Validation Rules:
-
Sol Length
Comment: General description: The length of SoL is theoretical distance between centre points of Ops which are selected in such a way to represent the average value for all tracks within the SoL. It is advised to include distances applied by IM for commercial purposes. Validation: No validation will be performed by RINF application regarding the length of SoL. This requires national verification.
Message: lengthOfSectionOfLine (1.1.0.0.0.5): Each SoL has exactly one length. This error is due to that either there is no length for the specified SoL, more than one length has been defined, or the datatype cannot be converted into an xsd:double.
- OPE TSI References
-
- Part of RCC Algorithm:
- true
-
- Appendix D2 Index
- 3.2.3
Nature of Section of Line
OP
IRI: http://data.europa.eu/949/solNature
- Parameter of
-
Section Of Line
- General Information
-
- Number:
- 1.1.0.0.0.6
- XML Name:
- SOLNature
- Deadline:
- In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
- Belongs to parameters group
-
Section of line generic information
(
1.1.0.0.0
)
- Data Format
-
- Data Presentation
-
Concept
- Taxonomy Reference:
-
Section of Line Natures
-
Values :
-
| Code |
Value |
| 10 |
Regular SoL |
| 20 |
Link |
- Flags
-
- Applicability Flags:
- Y
- Validation
-
- Validation Rules:
-
Sol Nature Skos
Comment: Indication of the SOL nature.
Message: SoL nature (1.1.0.0.0.6): The SOL {$this} with label {?label} has a value {?concept} that is not one of the predefined values and cannot be converted into a SKOS concept on this list: http://data.europa.eu/949/concepts/sol-natures/SoLNatures.
-
Sol Nature Applicability
Comment: If the value of this parameter is “Link”, then for all tracks belonging to this SoL, all the parameters of the following groups of parameters are not applicable: 1.1.1.1 Infrastructure subsystem; 1.1.1.2 Energy subsystem; 1.1.1.3 Control-command and signalling subsystem.
Message: SoL nature (1.1.0.0.0.6): The SoL {$this} ({?solLabel}), with opStart {?opStartID} and opEnd {?opEndID}, has a SOLnature of type Link, and at least one of its tracks has values for at least one of the groups of parameters 1.1.1.1, 1.1.1.2 or 1.1.1.3. This happens at least with the track {?track} ({?trackLabel}), with property {?p} (RINF index {?index}).
-
Sol Nature
Comment: General description: Validation: If the value of this parameter is 'Link', then for all tracks belonging to this SoL, all the parameters of the following groups of parameters are not applicable: 1.1.1.1 Infrastructure subsystem, 1.1.1.2 Energy subsystem, 1.1.1.3 Control-command and signalling subsystem.
Message: SoL nature (1.1.0.0.0.6): Either no SOL nature is specified for this SoL, or more than one SoL nature has been specified.
Industrial risks — locations where it is dangerous for the driver to step out
DP
IRI: http://data.europa.eu/949/existanceOfIndustrialRisk
- Parameter of
-
Section Of Line
-
Subset with common characteristics
- General Information
-
- Number:
- 1.1.0.0.1.1
- Deadline:
- In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
- Belongs to parameters group
-
Route book specific parameters
(
1.1.0.0.1
)
- Data Format
-
- Data Presentation
-
Boolean
- Format:
- Y/N
- Flags
-
- Applicability Flags:
- Y/N
- OPE TSI References
-
- Appendix D2 Index
- 3.2.5
- Additional Information
-
- General explanation:
- Although it is just an indication of existence of an industrial risk, the area covering the industrial risk should be references on the topological network.
For the route book purpose, the industrial risks should be defined as linear references instead of area. SpecialArea of type "industrial risk" should be used
Operating language
OP
IRI: http://data.europa.eu/949/operatingLanguage
- Parameter of
-
Infrastructure element
- General Information
-
- Number:
- 1.1.0.0.1.2
- 1.2.0.0.0.8
- Deadline:
- 12 months after publication of Article 7 Guide
- Belongs to parameters group
-
Route book specific parameters
(
1.1.0.0.1
)
- Data Format
-
- Data Presentation
-
Concept
- Format:
- http://publications.europa.eu/resource/authority/language
- Flags
-
- Applicability Flags:
- Y/NYA
- OPE TSI References
-
- Appendix D2 Index
- 3.5.1
Operational regime
OP
IRI: http://data.europa.eu/949/operationalRegimeType
- Parameter of
-
Section Of Line
- General Information
-
- Number:
- 1.1.0.0.1.3
- Deadline:
- 12 months after publication of Article 7 Guide
- Belongs to parameters group
-
Route book specific parameters
(
1.1.0.0.1
)
- Data Format
-
- Data Presentation
-
Concept
- Taxonomy Reference:
-
Operational regime types
-
Values :
-
| Code |
Value |
| 10 |
Mono-directional single track line |
| 20 |
Bi-directional single track line |
| 30 |
Reversible multiple track line |
| 40 |
Double or multiple track line |
- Flags
-
- Applicability Flags:
- Y/N/NYA
- OPE TSI References
-
- Appendix D2 Index
- 3.2.7
Identification of track
DP
IRI: http://data.europa.eu/949/trackId
- Parameter of
-
Running track
- General Information
-
- Number:
- 1.1.1.0.0.1
- 1.2.1.0.0.2
- XML Name:
- SOLTrackIdentification
- OPTrackIdentification
- Deadline:
- In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
- Belongs to parameters group
-
Running track generic information
(
1.1.1.0.0
)
-
Identifier
- Data Format
-
- Data Presentation
-
String
- Flags
-
- Applicability Flags:
- Y
- Validation
-
- Validation Rules:
-
No Repeated Track Ids So L
Comment: Each track shall have unique identification or number within the SoL. This number cannot be used for naming any other track in the same SoL.
Message: trackId (1.1.1.0.0.1): Each track shall have unique identification or number within the SoL. This number cannot be used for naming any other track in the same SoL. There is a problem with SoL {$this} ({?solLabel}) and tracks {?track1} ({?track1Label}) and {?track2} ({?track2Label}), since they have the same identifier: {?value}.
-
Track Id
Comment: Unique track identification or unique track number within an OP or a section of line.
Message: trackId (1.1.1.3.3.3.3, 1.2.1.1.2.3.3): The identification of a track must be a string. This error may be due to having a track with no identification or with more than one value as identification, or having a value that is not a string.
-
No Repeated Track Ids Op
Comment: Each track shall have unique identification or number within the OP. This number cannot be used for naming any other track in the same OP.
Message: trackId (1.2.1.0.0.2):: Each track shall have unique identification or number within the OP. This number cannot be used for naming any other track in the same OP. There is a problem with OP {$this} ({?opLabel}) and tracks {?track1} ({?track1Label}) and {?track2} ({?track2Label}), since they have the same identifier: {?value}.
- OPE TSI References
-
- Appendix D2 Index
- 2.2.1.1
- Additional Information
-
- General explanation:
- Each track shall have unique identification or number within the SoL. This number cannot be used for naming any other track in the same SoL.
The check regarding the uniqueness of the ID within the SoL has to be done on national level (preferably by IM).
Normal running direction
OP
IRI: http://data.europa.eu/949/trackDirection
- Parameter of
-
Running track
- General Information
-
- Number:
- 1.1.1.0.0.2
- XML Name:
- SOLTrackDirection
- Deadline:
- In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
- Belongs to parameters group
-
Running track generic information
(
1.1.1.0.0
)
- Data Format
-
- Data Presentation
-
Concept
- Taxonomy Reference:
-
Track Running Directions
-
Values :
-
- Flags
-
- Applicability Flags:
- Y
- Validation
-
- Validation Rules:
-
So Ltrack Direction Max Count
Comment: The normal running direction is: 1) the same as the direction defined by the start and end of the SoL 2) the opposite to the direction defined by the start and end of the SoL 3) both directions defined for SoL.
Message: There should be at most one Track Direction. There is a problem with SoL {$this} ({?solLabel}) and its track {?track} ({?trackLabel}). This track has at least two different values for this property: {?value1} and {?value2}
-
So Ltrack Direction Min Count
Comment: The normal running direction is: 1) the same as the direction defined by the start and end of the SoL 2) the opposite to the direction defined by the start and end of the SoL 3) both directions defined for SoL.
Message: There should be at least one Track Direction. There is a problem with SoL {$this} ({?solLabel}) and its track {?track} ({?trackLabel}). This track has no values for this property
-
Track Direction Skos
Comment: The normal running direction is: 1) the same as the direction defined by the start and end of the SoL 2) the opposite to the direction defined by the start and end of the SoL 3) both directions defined for SoL.
Message: Indication of the trackDirection (1.1.1.0.0.2):): The track {?track} in the Section of Line {$this} has a value {?concept} that is not one of the predefined values and cannot be converted into a SKOS concept on this list: http://data.europa.eu/949/concepts/track-running-directions/TrackRunningDirections.
- OPE TSI References
-
- Appendix D2 Index
- 2.2.1.1
Lineside distance indication
OP
IRI: http://data.europa.eu/949/linesideDistanceIndication
- Parameter of
-
Running track
-
Subset with common characteristics
- General Information
-
- Number:
- 1.1.1.0.0.3
- Belongs to parameters group
-
Running track generic information
(
1.1.1.0.0
)
- Data Format
-
- Data Presentation
-
Lineside indications of distance
- Format:
- [NNNN] frequency in meters
Appearance - selectable list
[L/R] - the side along the track where the lineside indication is positioned (left or right)
- Validation
-
- Validation Rules:
-
Lineside Distance Indication
Comment: Indication of types of appearance of track lineside distance indications.
Message: linesideDistanceIndication (1.1.1.0.0.3) : The track must have exactly one value of a lineside distance indication that must be an instance of LinesideDistanceIndication. This error may be due to the track having no value, having more than one value or having a value that is not an instance of the class LinesideDistanceIndication.
- OPE TSI References
-
- Appendix D2 Index
- 3.1.3
- Additional Information
-
- General explanation:
- Frequency, appearance and positioning of a sign indicating distance as reference post. Two types of sign are normally available: kilometer post and hectometer post.
- A kilometer post is a lineside sign indicating the distance from a specific point, usually being the strarting point of the railway line.
- An hectometer post is a lineside sign indicating a relative distance.
Connected to
OP
IRI: http://data.europa.eu/949/connectedTo
- Parameter of
-
Track
- General Information
-
- Number:
- 1.1.1.0.1.2
- 1.2.4.1
- Deadline:
- 12 months after publication of Article 7 Guide
- Belongs to parameters group
-
Running track generic information
(
1.1.1.0.0
)
- Data Format
-
- Data Presentation
-
Track
- Flags
-
- Applicability Flags:
- Y/N/NYA
- Additional Information
-
- General explanation:
- This property defines a connection between two tracks. It is symmetric, meaning if a track A is connected to track B, then track B is also connected to track A. A track cannot be connected to itself (irreflexive property).
Used to indicate connectivity between track instances in a network, ensuring that connections are non-self-referential and in the normal running direction of the track.
This is a simplistic representation of the internal connectivity of the tracks in an operational point or the connectivity of the tracks between operational points and sections of line.
For a more detailed representation of connectivity and navigability, this information should be available on the topology of the network.
-
- Example:
- Track_A connectedTo Track_B implies Track_B connectedTo Track_A.
EC declaration of verification for infrastructure element relating to compliance with the requirements from TSIs applicable to infrastructure subsystem
DP
IRI: http://data.europa.eu/949/verificationINF
- Parameter of
-
Running track
-
Subset with common characteristics
- General Information
-
- Number:
- 1.1.1.1.1.1
- 1.2.1.0.1.1
- 1.2.2.0.1.1
- XML Name:
- IDE_ECVerification
- Deadline:
- In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
- Belongs to parameters group
-
Declarations of verification for track
(
1.1.1.1.1
)
- Data Format
-
- Data Presentation
-
String
- Format:
- CC/RRRRRRRRRRRRRR/YYYY/NNNNNN
- Flags
-
- Applicability Flags:
- Y/N
- Validation
-
- Validation Rules:
-
Verification Infs
Comment: Indication of the verification of the infrastructure manager
Message: verificationINF (1.2.2.0.1.1, 1.2.1.0.1.1, 1.2.2.0.1.1): Each Siding or subset with common characteristics may have one or more verificationINF. This error is due to the value not being a string or the value not following this pattern: country code/national registration number/year between 1900 and 2100/progressive counter.
-
Verification Inf
Comment: Unique number for EC declarations following format requirements specified in the 'Document about practical arrangements for transmitting interoperability documents'.
Message: verificationINF (1.1.1.1.1.1, 1.2.1.0.1.1): The verificationINF must be a string following the format 'XX/XXXXXXXXXXXXXX/YYYY/DDDDDD' where XX is the country code, XXXXXXXXXXXXXX is the unique number for EC declarations, YYYY is the year of the declaration (1900-2100) and DDDDDD is the sequential number of the declaration. This error is due to the value not following the pattern.
- Additional Information
-
- General explanation:
- The parameter may be repeated only when several EC declarations were issued related to the INF subsystem.
With the extension of scope according to the IOD, geographical scope of the INF TSI now includes all the networks (TEN and off-TEN) with the following nominal track gauges: 1435, 1520, 1524, 1600 and 1668 mm
EI declaration of demonstration (as defined in Commission 2014/881/EU (2)) relating to compliance with the requirements from TSIs applicable to infrastructure subsystem
DP
IRI: http://data.europa.eu/949/demonstrationINF
- Parameter of
-
Running track
-
Subset with common characteristics
- General Information
-
- Number:
- 1.1.1.1.1.2
- 1.2.1.0.1.2
- 1.2.2.0.1.2
- XML Name:
- IDE_EIDemonstration
- Deadline:
- In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
- Belongs to parameters group
-
Declarations of verification for track
(
1.1.1.1.1
)
- Data Format
-
- Data Presentation
-
String
- Format:
- CC/RRRRRRRRRRRRRR/YYYY/NNNNNN
- Flags
-
- Applicability Flags:
- Y/N
- Validation
-
- Validation Rules:
-
Demonstration Infs
Comment: Unique number for EI declarations following the same format requirements as specified in the 'Documents about practical arrangements for transmitting interoperability documents'
Message: demonstrationINF (1.1.1.1.1.2, 1.2.1.0.1.2, 1.2.2.0.1.2): Each siding or subset with common characteristics may have one or more demonstrationINF. This error is due to the value not being a string or the value not following this pattern: country code/national registration number/year between 1900 and 2100/progressive counter.
-
Demonstration Inf
Comment: Unique number for EI declarations following format requirements specified in the 'Document about practical arrangements for transmitting interoperability documents'.
Message: demonstrationINF (1.1.1.1.1.2, 1.2.1.0.1.2): The demonstrationINF must be a string following the format 'XX/XXXXXXXXXXXXXX/YYYY/DDDDDD' where XX is the country code, XXXXXXXXXXXXXX is the unique number for EI declarations, YYYY is the year of the declaration (1900-2100) and DDDDDD is the sequential number of the declaration. This error is due to the value not following the pattern.
- Additional Information
-
- General explanation:
- EI declaration of demonstration (as defined Commission 2014/881/EU) for track relating to compliance with the requirements from TSIs applicable to infrastructure subsystem.
It may happen that several EI declarations were issued - then parameter has to be repeated as many times as many declarations were issued.
The procedure for demonstration that existing network fits to requirements of the TSIs is executed on voluntary basis, so when EI declaration do not exist then the parameter is optional. If EI declaration was not issued, then field shall be left empty.
- It may happen that several EI declarations were issued - then parameter has to be repeated as many times as many declarations were issued.
The procedure for demonstration that existing network fits to requirements of the TSIs is executed on voluntary basis, so when EI declaration do not exist then the parameter is optional. If EI declaration was not issued, then field shall be left empty.
TEN classification of track
OP
IRI: http://data.europa.eu/949/tenClassification
- Parameter of
-
Platform edge
-
Running track
-
Siding
-
Subset with common characteristics
- General Information
-
- Number:
- 1.1.1.1.2.1
- 1.2.1.0.2.1
- 1.2.1.0.6.3
- 1.2.2.0.0.3
- XML Name:
- IPP_TENClass
- IPL_TENClass
- Deadline:
- In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
- Belongs to parameters group
-
Performance parameter
(
1.1.1.1.2
|
1.2.1.0.2
|
1.2.2.0.2
)
-
Platform
(
1.2.1.0.6
)
-
Siding
(
1.2.2
)
- Data Format
-
- Data Presentation
-
Concept
- Taxonomy Reference:
-
TEN Classifications
-
Values :
-
| Code |
Value |
| 10 |
Part of the TEN-T Comprehensive Network |
| 20 |
Part of the TEN-T Core Freight Network |
| 30 |
Part of the TEN-T Core Passenger Network |
| 40 |
Off TEN |
| 50 |
Part of the TEN-T Extended Core Freight Network |
| 60 |
Part of the TEN-T Extended Core Passenger Network |
- Flags
-
- Applicability Flags:
- Y/N
- Validation
-
- Validation Rules:
-
Ten Classification Skost
Comment: Indication of the TEN classification of track.
Message: TEN classification (1.1.1.1.2.1, 1.2.1.0.2.1): The track or subset with common characteristics {$this} (label {?label}) has a value {?concept} that is not one of the predefined values and cannot be converted into a SKOS concept on this list: http://data.europa.eu/949/concepts/ten-classifications/TENClassifications.
-
Ten Classification S
Comment: Indicates the part of the trans-European network the platform belongs to.
Message: TEN classification (1.1.1.1.2.1, 1.2.1.0.2.1, 1.2.1.0.6.3, 1.2.2.0.0.3): This error may be due to having a Platform with a TEN classification that is not an URI.
-
Ten Classification P
Comment: Indicates the part of the trans-European network the platform belongs to.
Message: TEN classification (1.2.1.0.6.3): This error may be due to having a Platform with a TEN classification that is not an URI.
-
Ten Classification T
Comment: Indication of the part of the trans-European network the line belongs to.
Message: tenClassification (1.1.1.1.2.1, 1.2.1.0.2.1): The track or subset with common characteristics has a TEN classificaion value (Indication of the part of the trans-European network the line belongs to) that must be an IRI.
-
Ten Classification Skoss
Comment: Indication of the part of the trans-European network the line belongs to.
Message: TEN classification (1.1.1.1.2.1, 1.2.1.0.2.1, 1.2.1.0.6.3, 1.2.2.0.0.3): The siding or subset with common characteristics {$this} with label {?sidingLabel} has a value {?concept} that is not one of the predefined values and cannot be converted into a SKOS concept on this list: http://data.europa.eu/949/concepts/ten-classifications/TENClassifications.
-
Ten Classification Skosp
Comment: Indicates the part of the trans-European network the platform belongs to.
Message: TEN classification (1.2.1.0.6.3): The platform {$this} with label {?label} has a value {?concept} that is not one of the predefined values and cannot be converted into a SKOS concept on this list: http://data.europa.eu/949/concepts/ten-classifications/TENClassifications.
- Additional Information
-
- General explanation:
- Article 39 2. freight lines of the core network as indicated in Annex I: at least 22,5 t axle load, 100 km/h line speed and the possibility of running trains with a length of 740 m.
TEN geographic information system identity (GIS ID)
DP
IRI: http://data.europa.eu/949/tenGISId
- Parameter of
-
Running track
-
Subset with common characteristics
- General Information
-
- Number:
- 1.1.1.1.2.1.2
- XML Name:
- IPP_TENGISID
- Deadline:
- 1 January 2021
- Belongs to parameters group
-
Performance parameter
(
1.1.1.1.2
|
1.2.1.0.2
|
1.2.2.0.2
)
- Data Format
-
- Data Presentation
-
String
- Flags
-
- Applicability Flags:
- Y/N
- Validation
-
- Validation Rules:
-
Ten Gisid Applicability
Comment: Indication of the GIS identity (GIS ID) of the section of TEN-T database to which the track belongs.
Message: tenGISId (1.1.1.1.2.1.2): This error is due to the track or subset with common characteristics {?trackLabel} , violating the rule: Y if the answer to parameter 1.1.1.1.2.1 is not off TEN.
-
Ten Gisid
Comment: Indication of the GIS identity (GIS ID) of the section of TEN-T database to which the track belongs.
Message: tenGISId (1.1.1.1.2.1.2): The track or subset with common characteristics must have at most one character string value (GIS Id) of the section of TEN-T database to which the track belongs. This error may be due to having a track with more than one TEN GIS identity or that the value is not a string.
- Additional Information
-
- General explanation:
- This parameter will be deprecated in a next revision. Please use value "Not applicable" until the RINF regulation is aligned. The information below remains for reference only.
TENtec is the European Commission's information system to coordinate and support the Trans-European Transport Network Policy (TEN-T). For more details about the system and the legal background please follow the link to the TENtec Public Portal.
The list of sections of the TEN networks with their GIS IDs can be requested via MOVE-TENTEC-PUBLIC@ec.europa.eu
Category of line
OP
IRI: http://data.europa.eu/949/lineCategory
- Parameter of
-
Running track
-
Subset with common characteristics
- General Information
-
- Number:
- 1.1.1.1.2.2
- 1.2.1.0.2.2
- XML Name:
- IPP_LineCat
- Deadline:
- In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
- Belongs to parameters group
-
Performance parameter
(
1.1.1.1.2
|
1.2.1.0.2
|
1.2.2.0.2
)
- Data Format
-
- Data Presentation
-
Concept
- Taxonomy Reference:
-
Line Categories
-
Values :
-
- Flags
-
- Applicability Flags:
- Y/N
- Validation
-
- Validation Rules:
-
Line Category Skos
Comment: Classification of a line according to the TSI INF.
Message: lineCategory (1.1.1.1.2.2, 1.2.1.0.2.2): The track or subset with common characteristics {$this} (label {?label}) has a value {?concept} that is not one of the predefined values and cannot be converted into a SKOS concept on this list: http://data.europa.eu/949/concepts/line-category/LineCategories.
-
Line Category
Comment: Classification of a line according to the TSI INF.
Message: lineCategory (1.1.1.1.2.2, 1.2.1.0.2.2): The track or subset with common characteristics must have a classification of a line value that is an IRI.
- Additional Information
-
- General explanation:
- INF TSI (4.2.1) classifies lines based on the type of traffic (traffic code).
TSI categories of line shall be used for the classification of existing lines to define a target system so that the relevant performance parameters will be met.
The TSI category of line is a combination of traffic codes. For lines where only one type of traffic is carried (for example a freight only line), a single code can be used to describe the requirements; where mixed traffic runs the category will be described by one or more codes for passenger and freight in case of two types of traffic. Then the parameter is repeated if relevant. The combined traffic codes describe the envelope within which the desired mix of traffic can be accommodated.
Technical scope of the INF TSI includes all the networks (TEN and off-TEN) for nominal track gauges 1435, 1520, 1524, 1600 and 1668 mm.
It is not applicable when track is not included in technical scope of the TSI.
When more than one value of the parameter has to be published, then parameter has to be repeated as many times as many values of the parameter will be published.
-
- Example:
- If a line is operated by passenger trains with speed of 250 km/h, local commuter trains with speed of 120 km/h and heavy freight trains in the night, then the best combination of traffic codes seems to be P2, P5 and F1.
Then, the TSI category of line for this case would simply be P2-P5-F1.
Part of a Railway Freight Corridor
OP
IRI: http://data.europa.eu/949/freightCorridor
- Parameter of
-
Running track
-
Subset with common characteristics
- General Information
-
- Number:
- 1.1.1.1.2.3
- 1.2.1.0.2.3
- XML Name:
- IPP_FreightCorridor
- Deadline:
- In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
- Belongs to parameters group
-
Performance parameter
(
1.1.1.1.2
|
1.2.1.0.2
|
1.2.2.0.2
)
- Data Format
-
- Data Presentation
-
Concept
- Taxonomy Reference:
-
Freight Corridors
-
Values :
-
| Code |
Value |
| 10 |
Rhine-Alpine RFC |
| 20 |
North Sea-Mediterranean RFC |
| 30 |
Scandinavian – Mediterranean RFC |
| 40 |
Atlantic RFC |
| 50 |
Baltic-Adriatic RFC |
| 60 |
Mediterranean RFC |
| 70 |
Orient-EastMed RFC |
| 80 |
North Sea-Baltic RFC |
| 90 |
Rhine – Danube RFC |
| 100 |
Alpine-Western Balkan RFC |
| 110 |
Amber RFC |
- Flags
-
- Applicability Flags:
- Y/N
- Validation
-
- Validation Rules:
-
Freight Corridor Shape
Comment: Indication whether the line is designated to a Railway Freight Corridor
Message: freightCorridor (1.1.1.1.2.3, 1.2.1.0.2.3): Each track or subset with common characteristics may have an indication whether the line is designated to a Railway Freight Corridor that is an IRI. This error is due to having a value that is not an IRI.
-
Freight Corridor Skos
Comment: Indication whether the line is designated to a Railway Freight Corridor
Message: Indication whether the line is designated to a Railway Freight Corridor (1.1.1.1.2.3, 1.2.1.0.2.3): The National Line {$this} has a value {?concept} that is not one of the predefined values and cannot be converted into a SKOS concept on this list: http://data.europa.eu/949/concepts/freight-corridor/FreightCorridors.
- Additional Information
-
- General explanation:
- Not applicable if the line is not part of an RFC. If a line belongs to several corridors, repeat the parameter.
Load capability
OP
IRI: http://data.europa.eu/949/trackLoadCapability
- Parameter of
-
Running track
-
Subset with common characteristics
- General Information
-
- Number:
- 1.1.1.1.2.4
- XML Name:
- IPP_LoadCap
- Deadline:
- In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
- Belongs to parameters group
-
Performance parameter
(
1.1.1.1.2
|
1.2.1.0.2
|
1.2.2.0.2
)
- Data Format
-
- Data Presentation
-
Load capability
- Format:
- The value of this parameter is an instance of the era:LoadCapability class which consists of 2 properties:
- era:loadCapabilityLineCategory - as a taxonomy of load models representing line category
- era:loadCapabilitySpeed - integer for the value of speed [km/h] permitted for a specific load model
For RINF XML data sets:
As long as the data provision through XML data sets is allowed, the data format is:
[CCCC] [NNN],
where:
- [CCCC] is a single selection from the predefined list of load models representing line category
- [NNN] is the value of speed [km/h] permitted for a specific load model.
- Unit of Measure:
-
Kilometre per Hour
- Flags
-
- Applicability Flags:
- Y
- Validation
-
- Validation Rules:
-
Track Load Capability
Comment: Relates the track with the class LoadCapability. A combination of the line category and speed at the weakest point of the track.
Message: trackLoadCapability (1.1.1.1.2.4): The track or subset with common characteristics defines a load capability value that must be an instance of LoadCapability.
- OPE TSI References
-
- Part of RCC Algorithm:
- true
- Additional Information
-
- General explanation:
- At this step, RINF does not allow to enter additional data referred to additional speed regulations and operating requirements relating to locomotives (e.g., locomotive classes and associated maximum speed) or traffic types (e.g., maximum speed of freight traffic or passenger traffic).
The load capability describes the weakest point of this track within this section of line (which is normally a bridge or other sub-track structure).
It is expressed as a combination of the line category and speed permitted for trains exerting loads defined for this line category.
The result of the classification process is set out in EN 15528:2021 (Annex A) and referred to in that standard as Line Category.
The Load capability for UK in respect of Northern Ireland consists of RA and speed in miles per hour. RA shall be applied according to UK Railway Group Standard GE/RT8006, Issue Two, September 2010.
More than one combination may be published for the same track if applicable, but it has to be done by repetition of the parameter with one value selected only that is why Y is given in line Can be repeated.
For the following cases, it is not possible to use EN 15528:2021 categories of line classification:
- TSI categories of line P1520 and F1520 (passenger traffic or freight traffic at any speed)
- TSI categories of line P1600 and F1600 (passenger traffic or freight traffic at any speed)
When more than one value of the parameter has to be published, then parameter has to be repeated as many times as many values of the parameter will be published.
-
- Example:
- The set of selected data may include: B2-160, D4-120 and E5-100
When classifying infrastructure lines into line categories, the following options shall be used by the infrastructure manager to optimize freight traffic:
Option 1: determination of the line category at maximum freight traffic speed (maximum 120 Km/h)
Option 2: determination of a line category at an associated lower speed (less than the maximum freight traffic speed)
Example of option 1 (Annex F of EN 15528:2021): In a given track, if the traffic is mixed, the local speed of the line is 90 Km/h and the determined line category is D4 at a maximum of 90 Km/h, the information displayed should be: D4/90.
Example of option 2 (Annex F of EN 15528:2021): In a given track, if the traffic is mixed, the local speed of the line is 120 Km/h and the determined line category is C4 at a maximum of 120 Km/h and D4 at maximum of 90 Km/h, the information displayed should be: C4/120 and D4/90.
National classification for load capability
DP
IRI: http://data.europa.eu/949/nationalLoadCapability
- Parameter of
-
Running track
-
Subset with common characteristics
- General Information
-
- Number:
- 1.1.1.1.2.4.1
- XML Name:
- IPP_NCLoadCap
- Deadline:
- 16 January 2020
- Belongs to parameters group
-
Performance parameter
(
1.1.1.1.2
|
1.2.1.0.2
|
1.2.2.0.2
)
- Data Format
-
- Data Presentation
-
String
- Flags
-
- Applicability Flags:
- Y/N
- Validation
-
- Validation Rules:
-
National Load Capability
Comment: National classification for load capability
Message: nationalLoadCapability (1.1.1.1.2.4.1): The track or subset with common characteristics has a national load capability value that must be a string. This error may be due to the track having a value of national load capability that is not a character string.
- OPE TSI References
-
- Part of RCC Algorithm:
- true
- Additional Information
-
- General explanation:
- Some Networks are using National classification for load capability (instead of parameter 1.1.1.1.2.4 Load capability that provide load capability in accordance with EN 15528)
-
- Example:
- The French IM SNCF reseau is using the concept of 'groupe Demeaux' with the following definition is 'Groupe de classification de la voie tenant compte de la resistance de son armement en flexion verticale'.
Compliance of structures with the High Speed Load Model (HSLM)
DP
IRI: http://data.europa.eu/949/highSpeedLoadModelCompliance
- Parameter of
-
Running track
-
Subset with common characteristics
- General Information
-
- Number:
- 1.1.1.1.2.4.2
- XML Name:
- IPP_HSLMCompliant
- Deadline:
- 16 January 2020
- Belongs to parameters group
-
Performance parameter
(
1.1.1.1.2
|
1.2.1.0.2
|
1.2.2.0.2
)
- Data Format
-
- Data Presentation
-
Boolean
- Flags
-
- Applicability Flags:
- Y/N
- Validation
-
- Validation Rules:
-
High Speed Load Model Compliance
Comment: For sections of line with a maximum permitted speed of 200km/h or more information regarding the procedure to be used to perform the dynamic compatibility check
Message: highSpeedLoadModelCompliance (1.1.1.1.2.4.2): The track or subset with common characteristics must have at most one high speed load model compliance value that must be Y/N (boolean). This error may be due to the track having more than one value or having a value of high speed load model compliance that is not Y/N.
- OPE TSI References
-
- Part of RCC Algorithm:
- true
- Additional Information
-
- General explanation:
- (TSI INF 4.2.7.1.2(2)) Applicable if the maximum permitted speed of the running track is more than 200km/h and the structures within the section of line are all compatible with the High Speed Load Model (HSLM); information regarding the procedure to be used to perform the dynamic compatibility check shall be provided as well.
Railway location of structures requiring specific checks
DP
IRI: http://data.europa.eu/949/structureCheckLocation
- Parameter of
-
Running track
-
Subset with common characteristics
- General Information
-
- Number:
- 1.1.1.1.2.4.3
- XML Name:
- IPP_StructureCheckLoc
- Deadline:
- 16 January 2020
- Belongs to parameters group
-
Performance parameter
(
1.1.1.1.2
|
1.2.1.0.2
|
1.2.2.0.2
)
- Data Format
-
- Data Presentation
-
Double
- Flags
-
- Applicability Flags:
- Y/N
- Validation
-
- Dependencies:
- This information is to be linked with parameter 1.1.1.1.2.4.4
- Validation Rules:
-
Structure Check Location
Comment: Localisation of structures requiring specific checks.
Message: structureCheckLocation (1.1.1.1.2.4.3): The track or subset with common characteristics has a location of the structure check value that must be a double (real) number and follow the format [±NNNN.NNN]. This error may be due to the track having a value that does not follow the pattern or is not a double (real) number.
- OPE TSI References
-
- Part of RCC Algorithm:
- true
- Additional Information
-
- General explanation:
- The railway location identifies the location of the structure in the system of reference of the line to which the track belongs.
-
- Example:
- The IM A knows that its bridge X might have problems with combination of speed and load above a certain limit values Z, and for that the IM A has a specific procedure W for the check to be done; if the vehicle operation is intended to be within this case (above the limit Z), then RU shall proceed in accordance to the procedure W; therefore the bridge X shall be referred to in the parameter of the RINF: 1.1.1.1.2.4.3 / Railway location of structures requiring specific checks.
Document with the procedure(s) for static and dynamic route compatibility checks
OP
IRI: http://data.europa.eu/949/compatibilityProcedureDocument
- Parameter of
-
Running track
-
Subset with common characteristics
- General Information
-
- Number:
- 1.1.1.1.2.4.4
- XML Name:
- IPP_StructureCheckDocRef
- Deadline:
- 16 January 2020
- Belongs to parameters group
-
Performance parameter
(
1.1.1.1.2
|
1.2.1.0.2
|
1.2.2.0.2
)
- Data Format
-
- Data Presentation
-
ERA Document
- Flags
-
- Applicability Flags:
- Y/N
- Validation
-
- Validation Rules:
-
Compatibility Procedure Document
Comment: Document with the procedure for static and dynamic compatibility checks.
Message: compatibilityProcedureDocument (1.1.1.1.2.4.4): The track or subset with common characteristics has a name of the compatibility procedure document that must be a Document.
- OPE TSI References
-
- Part of RCC Algorithm:
- true
- Additional Information
-
- General explanation:
- The value of this parameter should be either a reference to a file name or an external link to a document.
If a file name is provided, the Infrastructure Manager (IM) must upload a document with the same file name using the "Reference Documents Management" functionality in the RINF application. The document must be in electronic format and available in two official EU languages. In this case, the parameter value must be repeated for each document.
If an external link is provided, the IM must ensure that the document is available at the provided link.
Maximum permitted speed
DP
IRI: http://data.europa.eu/949/maximumPermittedSpeed
- Parameter of
-
Running track
-
Subset with common characteristics
- General Information
-
- Number:
- 1.1.1.1.2.5
- XML Name:
- IPP_MaxSpeed
- Deadline:
- In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
- Belongs to parameters group
-
Performance parameter
(
1.1.1.1.2
|
1.2.1.0.2
|
1.2.2.0.2
)
- Data Format
-
- Data Presentation
-
Integer
- Unit of Measure:
-
Kilometre per Hour
- Flags
-
- Applicability Flags:
- Y/N
- Validation
-
- Validation Rules:
-
Maximum Permitted Speed
Comment: Maximum permitted speed.
Message: maximumPermittedSpeed (1.1.1.1.2.5): The track or subset with common characteristics must have at most one value of maximum permitted speed that is an integer that lies within the range 0 to 500. This error may be due to the track having more than one value of maximum permitted speed, that the value does not lie within the range, or that the value is not an integer.
- OPE TSI References
-
- Part of RCC Algorithm:
- true
-
- Appendix D2 Index
- 3.1.4
- Additional Information
-
- General explanation:
- "Speed on the line" shall be understood as speed on the track of the section of line in question.
-
- Example:
- In case INF, ENE and/or CCS allow different speeds, the max permitted speed on this track of this section of line shall be the lowest one.
In case the maximum permitted speed for freight and passenger trains operation are different, the max permitted speed on this track of this section of line shall be the highest one.
Temperature range
OP
IRI: http://data.europa.eu/949/temperatureRange
- Parameter of
-
Running track
-
Subset with common characteristics
-
Vehicle Type
- General Information
-
- Number:
- 1.1.1.1.2.6
- XML Name:
- IPP_TempRange
- Deadline:
- In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
- Belongs to parameters group
-
Performance parameter
(
1.1.1.1.2
|
1.2.1.0.2
|
1.2.2.0.2
)
- Data Format
-
- Data Presentation
-
Concept
- Taxonomy Reference:
-
Temperature ranges
-
Values :
-
- Flags
-
- Applicability Flags:
- Y/N
- Validation
-
- Validation Rules:
-
Temperature Range Skos
Comment: Indication of the temperature range of track.
Message: Indication of the temperature range (1.1.1.1.2.6):): The track {$this} has a value {?concept} that is not one of the predefined values and cannot be converted into a SKOS concept on this list: http://data.europa.eu/949/concepts/temperature-ranges/TemperatureRanges.
-
Temperature Range
Comment: Indication of the temperature range of track.
Message: temperatureRange (1.1.1.1.2.6): Each track or subset with common characteristics may have exactly one temperature range value that must be an IRI. This error may be due to the track not having a temperature range, or having more than one temperature range.
- OPE TSI References
-
- Part of RCC Algorithm:
- true
- Additional Information
-
- General explanation:
- T1 (-25 to +40)
T2 (-40 to +35)
T3 (-25 to +45)
Tx (-40 to +50)
Maximum altitude
DP
IRI: http://data.europa.eu/949/maximumAltitude
- Parameter of
-
Running track
-
Subset with common characteristics
- General Information
-
- Number:
- 1.1.1.1.2.7
- XML Name:
- IPP_MaxAltitude
- Deadline:
- In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
- Belongs to parameters group
-
Performance parameter
(
1.1.1.1.2
|
1.2.1.0.2
|
1.2.2.0.2
)
- Data Format
-
- Data Presentation
-
Double
- Format:
- [+/-][NNNN]
- Unit of Measure:
-
Metre
- Flags
-
- Applicability Flags:
- Y/N
- Validation
-
- Validation Rules:
-
Maximum Altitude
Comment: Highest point of the section of line above sea level in reference to Normal Amsterdam's Peil (NAP).
Message: maximumAltitude (1.1.1.1.2.7): The track or subset with common characteristics must define at most one maximum altitude value that must be a double (real) number with format[±NNNN]. This error may be due to the track having more than one value of maximum altitude or that the value is not a double (real) number.
- Additional Information
-
- General explanation:
- Normaal Amsterdams Peil (NAP), called also Amsterdam Ordnance Datum, it is a vertical datum commonly in use in Europe as reference level for the description of the height of objects in relation to the sea level.
The value of the parameter shall be given in metres, with tolerance of +/-100m.
Existence of severe climatic conditions
DP
IRI: http://data.europa.eu/949/hasSevereWeatherConditions
- Parameter of
-
Running track
-
Subset with common characteristics
- General Information
-
- Number:
- 1.1.1.1.2.8
- XML Name:
- IPP_SevereClimateCon
- Deadline:
- In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
- Belongs to parameters group
-
Performance parameter
(
1.1.1.1.2
|
1.2.1.0.2
|
1.2.2.0.2
)
- Data Format
-
- Data Presentation
-
Boolean
- Flags
-
- Applicability Flags:
- Y/N
- Validation
-
- Validation Rules:
-
Has Severe Weather Conditions
Comment: Climatic conditions on the line are severe according to European standard.
Message: hasSevereWeatherConditions (1.1.1.1.2.8): The track or subset with common characteristics must have at most one existence of severe weather conditions value that must be Y/N (boolean). This error may be due to the track having more than one value of has severe weather conditions or that the value is not Y/N (boolean).
- OPE TSI References
-
- Part of RCC Algorithm:
- true
- Additional Information
-
- General explanation:
- Value 'true' shall be selected in case there are possible severe climatic conditions to be expected, i.e. a significant amount of snow or ice is to be expected during winter and vehicle should be designed accordingly to be able to run in such conditions. (compliance to 4.2.6.1.2(3),(4) of TSI Loc&Pas required). 'False' to be selected otherwise.
Nominal and severe conditions are defined at TSI Loc&Pas level, section 4.2.6.1.2, which requires that the applicant declares to which snow conditions a vehicle complies with : either "nominal" or "severe" conditions. This technical aspect is reflected in the parameter 4.3.3 "Snow, ice and hail conditions" of ERATV , which will provide the two possible values:
- Nominal conditions correspond to compliance with clause 4.7 of EN 50125 as referred in the §4.2.6.1.2 (1) of TSI Loc&Pas.
To be noted: It is not required to precise the categorisation S1, S2 or S3 as mentioned in the EN 50125.
- Severe conditions correspond to compliance with §4.2.6.1.2 (3) and (4) : the applicant designs and tests its vehicle according to the different scenarios mentioned in the TSI §4.2.6.1.2 (3) (snowdrift, powder snow, temperature gradient, etc.) and set the related provisions to achieve this as required by §4.2.6.1.2 (4) (obstacle deflector of sufficient size, effect of ice and snow on running gear and brake function, etc.).
Gauging
OP
IRI: http://data.europa.eu/949/gaugingProfile
- Parameter of
-
Running track
-
Subset with common characteristics
-
Vehicle Type
- General Information
-
- Number:
- 1.1.1.1.3.1.1
- 1.2.1.0.3.4
- XML Name:
- ILL_Gauging
- Deadline:
- 16 January 2020
- Belongs to parameters group
-
Line layout
(
1.1.1.1.3
|
1.2.1.0.3
)
-
Vehicle type technical characteristic
- Data Format
-
- Data Presentation
-
Concept
- Taxonomy Reference:
-
Gauging Profiles
-
Values :
-
- Flags
-
- Applicability Flags:
- Y
- Validation
-
- Validation Rules:
-
Gauging Profile Skos
Comment: Indication of the gauging profile of track.
Message: Gauging profile (1.1.1.1.3.1.1, 1.2.1.0.3.4): The track or subset with common characteristics {$this} (label {?label}) has a value {?concept} that is not one of the predefined values and cannot be converted into a SKOS concept on this list: http://data.europa.eu/949/concepts/gaugings/GaugingProfiles.
-
Gauging Profile
Comment: Gauges as defined in European standard or other local gauges, including lower or upper part.
Message: gaugingProfile (1.1.1.1.3.1.1, 1.2.1.0.3.4): The track or subset with common characteristics must define a value that is an IRI. The error is due to having a value that is not an IRI.
- OPE TSI References
-
- Part of RCC Algorithm:
- true
- Additional Information
-
- General explanation:
- It is possible to include additional values than the already identified and included in the concept scheme. They will be introduced by the Agency on request via a process of change request.
UK in respect of the Northern Ireland have a reference profile, but defined based on national rule:
7.3.2.2 Specific case Ireland and UK for Northern Ireland ('P')
It is permissible for the reference profile of the upper and the lower part of the unit to be established in accordance with the national technical rules notified for this purpose.
See also:
- Annex D1 OPE TSI
- INF TSI: 4.2.3.1, 4.2.3.2
Railway location of particular points requiring specific checks
DP
IRI: http://data.europa.eu/949/gaugingCheckLocation
- Parameter of
-
Running track
-
Subset with common characteristics
- General Information
-
- Number:
- 1.1.1.1.3.1.2
- 1.2.1.0.3.5
- XML Name:
- ILL_GaugeCheckLoc
- Deadline:
- 16 January 2020
- Belongs to parameters group
-
Line layout
(
1.1.1.1.3
|
1.2.1.0.3
)
- Data Format
-
- Data Presentation
-
String
- Flags
-
- Applicability Flags:
- Y/N
- Validation
-
- Validation Rules:
-
Gauging Check Location
Comment: Location of particular points requiring specific checks due to deviations from gauging referred to in 1.1.1.1.3.1.1.
Message: gaugingCheckLocation (1.1.1.1.3.1.2, 1.2.1.0.3.5): The track or subset with common characteristics has a location of the gauging check that must be a string and follow the format [±NNNN.NNN]. The error is due to the value not following the pattern.
- OPE TSI References
-
- Part of RCC Algorithm:
- true
- Additional Information
-
- General explanation:
- This parameter is applicable when the IM wants to highlight a particular point requiring checks and provide info via parameter 'Document with the transversal section of the particular points requiring specific checks'.
The railway location identifies the location of the structure in the system of reference of the line to which the track belongs.
The location (generally the distance from the origin of the line to the point of interest for the specific check) on a line is given in kilometres with decimals (precision of 0.001).
Document with the transversal section of the particular points requiring specific checks
OP
IRI: http://data.europa.eu/949/gaugingTransversalDocument
- Parameter of
-
Running track
-
Subset with common characteristics
- General Information
-
- Number:
- 1.1.1.1.3.1.3
- 1.2.1.0.3.6
- XML Name:
- ILL_GaugeCheckDocRef
- Deadline:
- 16 January 2020
- Belongs to parameters group
-
Line layout
(
1.1.1.1.3
|
1.2.1.0.3
)
- Data Format
-
- Data Presentation
-
ERA Document
- Flags
-
- Applicability Flags:
- Y/N
- Validation
-
- Validation Rules:
-
Gauging Transversal Document
Comment: Document with the transversal section of the particular points requiring specific checks.
Message: gaugingTransversalDocument (1.1.1.1.3.1.3, 1.2.1.0.3.6): The track or subset with common characteristics has a transversal document of the gauging check value that must be a Document.
- OPE TSI References
-
- Part of RCC Algorithm:
- true
- Additional Information
-
- General explanation:
- The value of this parameter should be either a reference to a file name or an external link to a document.
If a file name is provided, the Infrastructure Manager (IM) must upload a document with the same file name using the "Reference Documents Management" functionality in the RINF application. The document must be in electronic format and available in two official EU languages. In this case, the parameter value must be repeated for each document.
If an external link is provided, the IM must ensure that the document is available at the provided link.
Standard combined transport profile number for swap bodies
OP
IRI: http://data.europa.eu/949/profileNumberSwapBodies
- Parameter of
-
Running track
-
Subset with common characteristics
- General Information
-
- Number:
- 1.1.1.1.3.4
- XML Name:
- ILL_ProfileNumSwapBodies
- Deadline:
- by 16 March 2019 at the latest for lines belonging to the TEN (1.1.1.1.2.1)
- Belongs to parameters group
-
Line layout
(
1.1.1.1.3
|
1.2.1.0.3
)
- Data Format
-
- Data Presentation
-
Concept
- Taxonomy Reference:
-
Profile Numbers for Swap Bodies
-
Values :
-
- Flags
-
- Applicability Flags:
- Y/N
- Validation
-
- Validation Rules:
-
Profile Number Swap Bodies Skos
Comment: Coding for combined transport with swap bodies as defined in UIC Code.
Message: Indication of the profileNumberSwapBodies(1.1.1.1.3.4):): The track {$this} has a value {?concept} that is not one of the predefined values and cannot be converted into a SKOS concept on this list: http://data.europa.eu/949/concepts/profile-num-swap-bodies/ProfileNumbersSwapBodies.
- Additional Information
-
- General explanation:
- The technical number is made up of the wagon compatibility code (1 letter) and the standard combined transport profile number (2 digits when width <= 2550 mm or 3 digits when, 2550 < width <= 2600 mm).
Standard combined transport profile number for semi-trailers
OP
IRI: http://data.europa.eu/949/profileNumberSemiTrailers
- Parameter of
-
Running track
-
Subset with common characteristics
- General Information
-
- Number:
- 1.1.1.1.3.5
- XML Name:
- ILL_ProfileNumSemiTrailers
- Deadline:
- by 16 March 2019 at the latest for lines belonging to the TEN (1.1.1.1.2.1)
- Belongs to parameters group
-
Line layout
(
1.1.1.1.3
|
1.2.1.0.3
)
- Data Format
-
- Data Presentation
-
Concept
- Taxonomy Reference:
-
Profile Numbers for Semi-Trailers
-
Values :
-
- Flags
-
- Applicability Flags:
- Y/N
- Validation
-
- Validation Rules:
-
Profile Number Semi Trailers Skos
Comment: Coding for combined transport with semi-trailers as defined in UIC Code.
Message: Indication of the profileNumberSemiTrailers(1.1.1.1.3.5):): The track or subset with common characteristics {$this} has a value {?concept} that is not one of the predefined values and cannot be converted into a SKOS concept on this list: http://data.europa.eu/949/concepts/profile-num-semi-trailers/ProfileNumbersSemiTrailers.
- Additional Information
-
- General explanation:
- The technical number is made up of the wagon compatibility code (1 letter) and the standard combined transport profile number (2 digits when width <= 2500 mm or 3 digits when 2500 < width <= 2600 mm).
Additional values than the already identified in the list above are possible. They will be introduced by the Agency on request via a process of change request.
Gradient profile
DP
IRI: http://data.europa.eu/949/gradientProfile
- Parameter of
-
Running track
-
Subset with common characteristics
- General Information
-
- Number:
- 1.1.1.1.3.6
- XML Name:
- ILL_GradProfile
- Deadline:
- In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
- Belongs to parameters group
-
Line layout
(
1.1.1.1.3
|
1.2.1.0.3
)
- Data Format
-
- Data Presentation
-
String
- Format:
- in XML: +/-NN.N (+/-NNNN.NNN)
- Flags
-
- Applicability Flags:
- Y
- Validation
-
- Validation Rules:
-
Gradient Profile
Comment: Sequence of gradient values and locations of change in gradient.
Message: gradientProfile (1.1.1.1.3.6): The track or subset with common characteristics has a gradient profile value that must be a string with a sequence of values in the format [+/-][NN.N]([+/-][NNNN.NNN]). This error may be due to having a sequence of values that are not a string or that do not follow the pattern.
- OPE TSI References
-
- Part of RCC Algorithm:
- true
-
- Appendix D2 Index
- 3.2.2
- Additional Information
-
- General explanation:
- Data on the values of gradient along a SoL is given as a chain of information:
Gradient (location) The first location corresponding to the start of the first value of the gradient is the centre point of start OP. If there are different values of the gradient, the parameter will be repeated. The last location will correspond to the point where the last value of the gradient starts. This value will be available until the centre point of the end OP.
If there is only one value for the gradient along the track, then the location is not required, only the +/-NN.N value is expected.
Gradient is expressed in mm/m; location is expressed in km of the line.
Positive gradient (uphill) is marked with "+" and negative gradient (downhill) is marked by "-".
The sequence shall follow the increasing kilometres of the line, and this does not take into consideration the running direction of the specific track. This will make the profile easier to read.
Changes in gradient shall be registered only as far as necessary for train running calculations (minimum length of constant gradient shall be 500 m, the minimum change of gradient value shall be 0,5 mm/m).
The required precision for gradient value is 0,5 mm/m, the required precision of location of the points of change of gradient is 10 m. The points of change of gradient are the points of vertical intersection of each vertical curve.
Minimum radius of horizontal curve
DP
IRI: http://data.europa.eu/949/minimumHorizontalRadius
- Parameter of
-
Running track
-
Subset with common characteristics
-
Vehicle Type
- General Information
-
- Number:
- 1.1.1.1.3.7
- 1.2.2.0.3.2
- XML Name:
- ILL_MinRadHorzCurve
- Deadline:
- In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
- Belongs to parameters group
-
Line layout
(
1.1.1.1.3
|
1.2.1.0.3
)
-
Siding
(
1.2.2
)
-
Vehicle type technical characteristic
- Data Format
-
- Data Presentation
-
Integer
- Format:
- NNNNN
- Unit of Measure:
-
Metre
- Flags
-
- Applicability Flags:
- Y/N
- Validation
-
- Validation Rules:
-
Minimum Horizontal Radius S
Comment: Radius of the smallest horizontal curve of the track in metres.
Message: minimumHorizontalRadius (1.2.2.0.3.2, 1.2.2.0.3.2): Each siding or subset with common characteristics may have a minimumHorizontalRadius in meters. This error is due to having more than one minimum horisontal radius value or having a minimum horizontal radius that is not an integer number.
-
Minimum Horizontal Radius
Comment: Radius of the smallest horizontal curve of The track or subset with common characteristics in metres.
Message: minimumHorizontalRadius (1.1.1.1.3.7, 1.2.2.0.3.2): The track or subset with common characteristics defines a minimum radius of horizontal curve. This error is due to having more than one value, having a value that is not an integer or having an integer that does not follow the pattern [NNNNNN].
- OPE TSI References
-
- Part of RCC Algorithm:
- true
- Additional Information
-
- General explanation:
- To describe a straight section of line value " 99999" shall be used.
Standard combined transport profile number for containers
OP
IRI: http://data.europa.eu/949/standardCombinedTransportContainers
- Parameter of
-
Running track
-
Subset with common characteristics
- General Information
-
- Number:
- 1.1.1.1.3.8
- XML Name:
- ILL_standardCombinedTransportContainers
- Deadline:
- 12 months after the adoption of the Article 7 Guide for lines belonging to the TEN (1.1.1.1.2.1)
- Belongs to parameters group
-
Line layout
(
1.1.1.1.3
|
1.2.1.0.3
)
- Data Format
-
- Data Presentation
-
Concept
- Taxonomy Reference:
-
Standard combined transport containers
-
Values :
-
| Code |
Value |
| 00 |
ISO 00 |
| 01 |
ISO 01 |
| 02 |
ISO 02 |
| 03 |
ISO 03 |
| 04 |
ISO 04 |
| 05 |
ISO 05 |
| 06 |
ISO 06 |
| 07 |
ISO 07 |
| 08 |
ISO 08 |
| 09 |
ISO 09 |
| 10 |
ISO 10 |
| 11 |
ISO 11 |
| 12 |
ISO 12 |
| 13 |
ISO 13 |
| 14 |
ISO 14 |
| 15 |
ISO 15 |
| 16 |
ISO 16 |
| 17 |
ISO 17 |
| 18 |
ISO 18 |
| 19 |
ISO 19 |
| 20 |
ISO 20 |
| 21 |
ISO 21 |
| 22 |
ISO 22 |
| 23 |
ISO 23 |
| 24 |
ISO 24 |
| 25 |
ISO 25 |
| 26 |
ISO 26 |
| 27 |
ISO 27 |
| 28 |
ISO 28 |
| 29 |
ISO 29 |
| 30 |
ISO 30 |
| 31 |
ISO 31 |
| 32 |
ISO 32 |
| 33 |
ISO 33 |
| 34 |
ISO 34 |
| 35 |
ISO 35 |
| 36 |
ISO 36 |
| 37 |
ISO 37 |
| 38 |
ISO 38 |
| 39 |
ISO 39 |
| 40 |
ISO 40 |
| 41 |
ISO 41 |
| 42 |
ISO 42 |
| 43 |
ISO 43 |
| 44 |
ISO 44 |
| 45 |
ISO 45 |
| 46 |
ISO 46 |
| 47 |
ISO 47 |
| 48 |
ISO 48 |
| 49 |
ISO 49 |
| 50 |
ISO 50 |
| 51 |
ISO 51 |
| 52 |
ISO 52 |
| 53 |
ISO 53 |
| 54 |
ISO 54 |
| 55 |
ISO 55 |
| 56 |
ISO 56 |
| 57 |
ISO 57 |
| 58 |
ISO 58 |
| 59 |
ISO 59 |
| 60 |
ISO 60 |
| 61 |
ISO 61 |
| 62 |
ISO 62 |
| 63 |
ISO 63 |
| 64 |
ISO 64 |
| 65 |
ISO 65 |
| 66 |
ISO 66 |
| 67 |
ISO 67 |
| 68 |
ISO 68 |
| 69 |
ISO 69 |
| 70 |
ISO 70 |
| 71 |
ISO 71 |
| 72 |
ISO 72 |
| 73 |
ISO 73 |
| 74 |
ISO 74 |
| 75 |
ISO 75 |
| 76 |
ISO 76 |
| 77 |
ISO 77 |
| 78 |
ISO 78 |
| 79 |
ISO 79 |
| 80 |
ISO 80 |
| 81 |
ISO 81 |
| 82 |
ISO 82 |
| 83 |
ISO 83 |
| 84 |
ISO 84 |
| 85 |
ISO 85 |
| 86 |
ISO 86 |
| 87 |
ISO 87 |
| 88 |
ISO 88 |
| 89 |
ISO 89 |
| 90 |
ISO 90 |
| 91 |
ISO 91 |
| 92 |
ISO 92 |
| 93 |
ISO 93 |
| 94 |
ISO 94 |
| 95 |
ISO 95 |
| 96 |
ISO 96 |
| 97 |
ISO 97 |
| 98 |
ISO 98 |
| 99 |
ISO 99 |
- Flags
-
- Applicability Flags:
- Y/N
- Validation
-
- Validation Rules:
-
Standard Combined Transport Containers Skos
Comment: Coding for combined transport for containers (for all freight and mixed-traffic lines) in accordance with the specification referenced in Appendix A-1, index [B].
Message: standardCombinedTransportContainers (1.1.1.1.3.8):): The track or subset with common characteristics {$this} has a value {?concept} that is not one of the predefined values and cannot be converted into a SKOS concept on this list: http://data.europa.eu/949/concepts/standard-combined-transport-containers/StandardCombinedTransportContainers.
-
Standard Combined Transport Containers
Comment: Coding for combined transport for containers (for all freight and mixed-traffic lines) in accordance with the specification referenced in Appendix A-1, index [B].
Message: standardCombinedTransportContainers (1.1.1.1.3.8): The track defines a standard combined transport profile number for containers. This error is due to having a value that is not an IRI.
Standard combined transport profile number for roller units
OP
IRI: http://data.europa.eu/949/standardCombinedTransportRollerUnits
- Parameter of
-
Running track
-
Subset with common characteristics
- General Information
-
- Number:
- 1.1.1.1.3.9
- XML Name:
- ILL_standardCombinedTransporRollerUnits
- Deadline:
- 12 months after the adoption of the Article 7 Guide for lines belonging to the TEN (1.1.1.1.2.1)
- Belongs to parameters group
-
Line layout
(
1.1.1.1.3
|
1.2.1.0.3
)
- Data Format
-
- Data Presentation
-
Concept
- Taxonomy Reference:
-
Standard combined transport profile numbers for roller units
-
Values :
-
- Flags
-
- Applicability Flags:
- Y/N/NYA
- Validation
-
- Validation Rules:
-
Standard Combined Roller Units Skos
Comment: Coding for combined transport for roller units (for all freight and mixed-traffic lines) in accordance with the specification referenced in Appendix A-1, index [B].
Message: standardCombinedTransportRollerUnits (1.1.1.1.3.9):): The track or subset with common characteristics {$this} in the Section of Line {$this} has a value {?concept} that is not one of the predefined values and cannot be converted into a SKOS concept on this list: http://data.europa.eu/949/concepts/standard-combined-transport-roller-units/StandardCombinedTransportRollerUnits.
-
Standard Combined Roller Units
Comment: Coding for combined transport for roller units (for all freight and mixed-traffic lines) in accordance with the specification referenced in Appendix A-1, index [B].
Message: standardCombinedTransportRollerUnits (1.1.1.1.3.9): The track or subset with common characteristics defines a standard combined transport profile number for roller units. This error is due to having or having a value that is not an IRI.
Nominal track gauge
OP
IRI: http://data.europa.eu/949/wheelSetGauge
- Parameter of
-
Running track
-
Subset with common characteristics
-
Vehicle Type
- General Information
-
- Number:
- 1.1.1.1.4.1
- 1.2.1.0.4.1
- XML Name:
- ITP_NomGauge
- Deadline:
- In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
- Belongs to parameters group
-
Track parameters
(
1.1.1.1.4
|
1.2.1.0.4
)
-
Vehicle type technical characteristic
- Data Format
-
- Data Presentation
-
Concept
- Taxonomy Reference:
-
Nominal Track Gauges
-
Values :
-
- Flags
-
- Applicability Flags:
- Y
- Validation
-
- Validation Rules:
-
Wheel Set Gauge Skos
Comment: A single value expressed in millimeters that identifies The track or subset with common characteristics gauge.
Message: Nominal track gauge (1.1.1.1.4.1, 1.2.1.0.4.1): The track or subset with common characteristics {$this} (label {?label}) has a value {?concept} that is not one of the predefined values and cannot be converted into a SKOS concept on this list: http://data.europa.eu/949/concepts/nominal-track-gauges/NominalTrackGauges.
-
Wheel Set Gauge
Comment: A single value expressed in millimeters that identifies the track gauge.
Message: wheelSetGauge (1.1.1.1.4.1, 1.2.1.0.4.1): The track or subset with common characteristics must have at most one wheel set gauge value that is an IRI.
- OPE TSI References
-
- Part of RCC Algorithm:
- true
- Additional Information
-
- General explanation:
- In case of multi-rail track, a set of data is to be published separately to each pair of rails to be operated as separate track (the whole set of parameters for the separate track has to be delivered be careful then with the track identification). Nominal track gauges provided by the INF TSI are only 1435, 1520, 1524, 1600 and 1668.
Cant deficiency
DP
IRI: http://data.europa.eu/949/cantDeficiency
- Parameter of
-
Running track
-
Subset with common characteristics
- General Information
-
- Number:
- 1.1.1.1.4.2
- XML Name:
- ITP_CantDeficiency
- Deadline:
- In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
- Belongs to parameters group
-
Track parameters
(
1.1.1.1.4
|
1.2.1.0.4
)
- Data Format
-
- Data Presentation
-
Integer
- Format:
- +/-NNN
- Unit of Measure:
-
Millimetre
- Flags
-
- Applicability Flags:
- Y
- Validation
-
- Validation Rules:
-
Cant Deficiency
Comment: Maximum cant deficiency expressed in millimeters defined as difference between the applied cant and a higher equilibrium cant the line has been designed for.
Message: cantDeficiency (1.1.1.1.4.2): The track or subset with common characteristics must have at most one cant deficiency value that is an integer. This error may be due to the track having more than one cant deficiency value or to having a value that is not an int.
- OPE TSI References
-
- Part of RCC Algorithm:
- true
- Additional Information
-
- General explanation:
- In case of positive value of cant deficiency or zero symbol '+' shall be applied. In case of negative cant deficiency symbol '-' has to be selected. Value of the cant deficiency shall be given in millimetres. In case of lateral uncompensated acceleration on a 1435 mm track gauge of 1.0 m/s2 the value of 153 mm may be published.
Rail inclination
OP
IRI: http://data.europa.eu/949/railInclination
- Parameter of
-
Running track
-
Subset with common characteristics
-
Vehicle Type
- General Information
-
- Number:
- 1.1.1.1.4.3
- XML Name:
- ITP_RailInclination
- Deadline:
- In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
- Belongs to parameters group
-
Track parameters
(
1.1.1.1.4
|
1.2.1.0.4
)
-
Vehicle type technical characteristic
- Data Format
-
- Data Presentation
-
Concept
- Format:
- In XML the accepted value is NN, where N is a digit from 0 to 9.
- Taxonomy Reference:
-
Rail Inclinations
-
Values :
-
| Code |
Value |
| 10 |
1/10 |
| 20 |
1/20 |
| 30 |
1/30 |
| 40 |
1/40 |
| 80 |
1/80 |
- Flags
-
- Applicability Flags:
- Y
- Validation
-
- Validation Rules:
-
Rail Inclination
Comment: An angle defining the inclination of the head of a rail relatie to the running surface.
Message: railInclination (1.1.1.1.4.3): The track or subset with common characteristics must have at most one rail inclination measurement value that is an IRI. This error may be due to the track having more than one rail inclination measurement value or to having a value that is not an IRI.
-
Rail Inclination Skos
Comment: An angle defining the inclination of the head of a rail relatie to the running surface.
Message: Indication of the rail inclination (1.1.1.1.4.3):): The track or subset with common characteristics {$this} has a value {?concept} that is not one of the predefined values and cannot be converted into a SKOS concept on this list: http://data.europa.eu/949/concepts/rail-inclinations/RailInclinations.
- OPE TSI References
-
- Part of RCC Algorithm:
- true
- Additional Information
-
- General explanation:
- This inclination is in most cases expressed for MS globally, but anyway it requires presentation for the specific track, when in one SoL more values occur.
An angle defining the inclination of the head of a rail when installed in the track relative to the plane of the rails (running surface), equal to the angle between the axis of symmetry of the rail (or of an equivalent symmetrical rail having the same rail head profile) and the perpendicular to the plane of the rails. The typical values for the railway inclination are 1:20, 1:30, 1:40.
Existence of ballast
DP
IRI: http://data.europa.eu/949/hasBallast
- Parameter of
-
Running track
-
Subset with common characteristics
- General Information
-
- Number:
- 1.1.1.1.4.4
- XML Name:
- ITP_Ballast
- Deadline:
- In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
- Belongs to parameters group
-
Track parameters
(
1.1.1.1.4
|
1.2.1.0.4
)
- Data Format
-
- Data Presentation
-
Boolean
- Format:
- in XML: Y/N
- Flags
-
- Applicability Flags:
- Y/N
- Validation
-
- Dependencies:
- Mandatory for tracks with permitted speed (parameter 1.1.1.1.2.5) greater than 250km/h
- Validation Rules:
-
Has Ballast
Comment: Specifies whether the track construction is with sleepers embedded in ballast or not.
Message: hasBallast (1.1.1.1.4.4): The track or subset with common characteristics must have at most one existence of ballast value that is Y/N (boolean). This error may be due to the track having more than one has ballast value or to having a value that is not Y/N (boolean).
-
Has Ballast Applicability
Comment: Specifies whether track construction is with sleepers embedded in ballast or not.
Message: hasBallast (1.1.1.1.4.4): This error is due to the track or subset with common characteristics {?trackLabel} , violating the rule: Y for tracks with permitted speed (parameter 1.1.1.1.2.5) greater than 250km/h.
- Additional Information
-
- General explanation:
- This parameter is related to phenomena of ballast pick-up observed for the high-speed traffic.
Requirements regarding ballast pick-up reduction at infrastructure subsystem level only applies to lines intended to be operated at speed greater than 250 km/h and is an open point in INF TSI: 4.2.10.3
The parameter is about the phenomenon of ballast pick-up observed for the high-speed traffic, not about the ballast itself.
As so far any specifications for mitigation of the problem were disclosed, the only information from RINF will be data about the network where the problems may be faced.
TSI compliance of in-service values for switches and crossings
DP
IRI: http://data.europa.eu/949/tsiSwitchCrossing
- Parameter of
-
Running track
-
Subset with common characteristics
- General Information
-
- Number:
- 1.1.1.1.5.1
- XML Name:
- ISC_TSISwitchCrossing
- Deadline:
- In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
- Belongs to parameters group
-
Switches and crossings
(
1.1.1.1.5
)
- Data Format
-
- Data Presentation
-
Boolean
- Format:
- in XML: Y/N
- Flags
-
- Applicability Flags:
- Y
- Validation
-
- Validation Rules:
-
Tsiswitch Crossing
Comment: Switches and crossings are maintained to in service limit dimension as specified in TSI.
Message: tsiSwitchCrossing (1.1.1.1.5.1): The track or subset with common characteristics must have at most one existence of TSI switches and crossing value that is Y/N (boolean). This error may be due to the track having more than one tsi swith crossing value or to having a value that is not Y/N (boolean).
- Additional Information
-
- General explanation:
- If for existing track at least one parameter has less strict value than specified in the TSI, then 'N' (false) shall be selected.
Minimum wheel diameter for fixed obtuse crossings
DP
IRI: http://data.europa.eu/949/minimumWheelDiameter
- Parameter of
-
Running track
-
Subset with common characteristics
-
Vehicle Type
- General Information
-
- Number:
- 1.1.1.1.5.2
- XML Name:
- ISC_MinWheelDiaFixObtuseCrossings
- Deadline:
- In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
- Belongs to parameters group
-
Switches and crossings
(
1.1.1.1.5
)
-
Vehicle type technical characteristic
- Data Format
-
- Data Presentation
-
Integer
- Format:
- NNN
- Unit of Measure:
-
Millimetre
- Flags
-
- Applicability Flags:
- Y
- Validation
-
- Validation Rules:
-
Minimum Wheel Diameter
Comment: Maximum unguided length of fixed obtuse crossings is based on a minimum wheel diameter in service expressed in millimiters.
Message: minimumWheelDiameter (1.1.1.1.5.2): The track or subset with common characteristics must have at most one minimum wheel diameter value that is an integer. This error may be due to the track having more than one minimum wheel diameter value or to having a value that is not an integer.
- OPE TSI References
-
- Part of RCC Algorithm:
- true
- Additional Information
-
- General explanation:
- The minimum TSI value is 330 mm and this shall be used as a default value unless advised otherwise. If the value of the wheel diameter is bigger than 330 mm, it has to be specified.
New lines are assumed to be compliant with the TSI INF. When the line is compliant to TSI the default value of 330 mm has to be presented.
Maximum train deceleration
DP
IRI: http://data.europa.eu/949/maximumTrainDeceleration
- Parameter of
-
Running track
-
Subset with common characteristics
- General Information
-
- Number:
- 1.1.1.1.6.1
- XML Name:
- ILR_MaxDeceleration
- Deadline:
- In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
- Belongs to parameters group
-
Track resistance to applied loads
(
1.1.1.1.6
)
- Data Format
-
- Data Presentation
-
Double
- Format:
- N.N
- Unit of Measure:
-
Metre per Square Second
- Flags
-
- Applicability Flags:
- Y/N
- Validation
-
- Dependencies:
- Not applicable if line is not in scope of INF TSI
- Validation Rules:
-
Maximum Train Deceleration
Comment: Limit for longitudinal track resistance given as a maximum allowed train deceleration and expressed in m/s2.
Message: maximumTrainDeceleration (1.1.1.1.6.1): The track or subset with common characteristics must have at most one maximum train deceleration value that is a double (real) number . This error may be due to the track having more than one maximum train deceleration value or to having a value that is not a real (double) number.
- OPE TSI References
-
- Part of RCC Algorithm:
- true
- Additional Information
-
- General explanation:
- New lines are assumed to be compliant with the TSI INF.
For TSI compliant lines the default value of 2.5 m/s2 shall be presented.
If for the design of the track the braking forces were assumed on basis of the deceleration lower value than 2.5 m/s2, the applied value of the deceleration has to be specified.
Use of eddy current brakes
OP
IRI: http://data.europa.eu/949/eddyCurrentBraking
- Parameter of
-
Running track
-
Subset with common characteristics
- General Information
-
- Number:
- 1.1.1.1.6.2
- 1.2.1.0.4.2
- XML Name:
- ILR_EddyCurrentBrakes
- Deadline:
- 12 months after publication of Article 7 Guide for OP tracks
- In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
- Belongs to parameters group
-
Track parameters
(
1.1.1.1.4
|
1.2.1.0.4
)
-
Track resistance to applied loads
(
1.1.1.1.6
)
- Data Format
-
- Data Presentation
-
Concept
- Taxonomy Reference:
-
Eddy Current Braking
-
Values :
-
| Code |
Value |
| 10 |
Allowed |
| 20 |
Allowed under conditions |
| 30 |
Allowed only for emergency brake |
| 40 |
Allowed under conditions only for emergency brake |
| 50 |
Not allowed |
- Flags
-
- Applicability Flags:
- Y/N/NYA
- Validation
-
- Validation Rules:
-
Eddy Current Braking
Comment: Indication of limitations on the use of eddy current brakes.
Message: eddyCurrentBraking (1.1.1.1.6.2, 1.2.1.0.4.2): The track or subset with common characteristics must have a single use of eddy current brakes value that is an IRI. This error is due to having more than one value or having a value that is not an IRI.
-
Eddy Current Braking Skos
Comment: Indication of limitations on the use of eddy current brakes.
Message: eddyCurrentBraking (1.1.1.1.6.2, 1.2.1.0.4.2): The track or subset with common characteristics {$this} (label {?label}) has a value {?concept} that is not one of the predefined values and cannot be converted into a SKOS concept on this list: http://data.europa.eu/949/concepts/eddy-current-braking/EddyCurrentBraking.
- OPE TSI References
-
- Part of RCC Algorithm:
- true
-
- Appendix D2 Index
- 3.4.5
- Additional Information
-
- General explanation:
- The use of both brakes is allowed or not under exterior conditions (depending on the features of the train engines for example).
The RINF can't be filled without more precisions.
Use of magnetic brakes
OP
IRI: http://data.europa.eu/949/magneticBraking
- Parameter of
-
Running track
-
Subset with common characteristics
- General Information
-
- Number:
- 1.1.1.1.6.3
- 1.2.1.0.4.3
- XML Name:
- ILR_MagneticBrakes
- Deadline:
- 12 months after publication of Article 7 Guide for OP tracks
- In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
- Belongs to parameters group
-
Track resistance to applied loads
(
1.1.1.1.6
)
- Data Format
-
- Data Presentation
-
Concept
- Taxonomy Reference:
-
Magnetic Braking
-
Values :
-
| Code |
Value |
| 10 |
Allowed |
| 20 |
Allowed under conditions |
| 30 |
Allowed under conditions only for emergency brake |
| 40 |
Allowed only for emergency brake |
| 50 |
Not allowed |
- Flags
-
- Applicability Flags:
- Y/N/NYA
- Validation
-
- Validation Rules:
-
Magnetic Braking
Comment: Indication of limitations on the use of magnetic brakes.
Message: magneticBraking (1.1.1.1.6.3, 1.2.1.0.4.3): The track or subset with common characteristics must have a single use of magnetic brakes value that is an IRI. This error is due to having more than one value or having a value that is not an IRI.
-
Magnetic Braking Skos
Comment: Indication of limitations on the use of magnetic brakes.
Message: magneticBraking (1.1.1.1.6.3, 1.2.1.0.4.3): The track or subset with common characteristics {$this} (label {?label}) has a value {?concept} that is not one of the predefined values and cannot be converted into a SKOS concept on this list: http://data.europa.eu/949/concepts/magnetic-braking/MagneticBraking.
- OPE TSI References
-
- Part of RCC Algorithm:
- true
-
- Appendix D2 Index
- 3.4.6
Document with the conditions for the use of eddy current brakes
OP
IRI: http://data.europa.eu/949/eddyCurrentBrakingConditionsDocument
- Parameter of
-
Running track
-
Subset with common characteristics
- General Information
-
- Number:
- 1.1.1.1.6.4
- XML Name:
- ILR_ECBDocRef
- Deadline:
- 16 January 2020
- Belongs to parameters group
-
Track resistance to applied loads
(
1.1.1.1.6
)
- Data Format
-
- Data Presentation
-
ERA Document
- Flags
-
- Applicability Flags:
- Y/N
- Validation
-
- Dependencies:
- Mandatory value to be provided when 1.1.1.1.6.2/Use of eddy current brakes is allowed under conditions or allowed under conditions only for emergency brake
- Validation Rules:
-
Eddy Current Braking Conditions Document Applicability
Comment: Electronic document available in two EU languages from the IM stored by the Agency with conditions for the use of eddy current brakes identified in 1.1.1.1.6.2.
Message: eddyCurrentBrakingConditionsDocument (1.1.1.1.6.4): This error is due to the track or subset with common characteristics {?trackLabel} , violating the rule: Y in case of Y for 1.1.1.1.6.2 Use of eddy current brakes is “allowed under conditions” or “allowed under conditions only for emergency brake””.
-
Eddy Current Braking Conditions Document
Comment: Electronic document available in two EU languages from the IM stored by the Agency with conditions for the use of eddy current brakes identified in 1.1.1.1.6.2.
Message: eddyCurrentBrakingConditionsDocument (1.1.1.1.6.4): The track or subset with common characteristics has an eddy current braking conditions document value that must be a Document.
- OPE TSI References
-
- Part of RCC Algorithm:
- true
-
- Appendix D2 Index
- 3.4.5
- Additional Information
-
- General explanation:
- If there exist conditions to allow the use of eddy current brakes.
The value of this parameter should be either a reference to a file name or an external link to a document.
If a file name is provided, the Infrastructure Manager (IM) must upload a document with the same file name using the "Reference Documents Management" functionality in the RINF application. The document must be in electronic format and available in two official EU languages. In this case, the parameter value must be repeated for each document.
If an external link is provided, the IM must ensure that the document is available at the provided link.
Document with the conditions for the use of magnetic brakes
OP
IRI: http://data.europa.eu/949/magneticBrakingConditionsDocument
- Parameter of
-
Running track
-
Subset with common characteristics
- General Information
-
- Number:
- 1.1.1.1.6.5
- XML Name:
- ILR_MBDocRef
- Deadline:
- 16 January 2020
- Belongs to parameters group
-
Track resistance to applied loads
(
1.1.1.1.6
)
- Data Format
-
- Data Presentation
-
ERA Document
- Flags
-
- Applicability Flags:
- Y/N
- Validation
-
- Dependencies:
- Mandatory value to be provided when 1.1.1.1.6.3 / Use of magnetic brakes is 'allowed under conditions' or 'allowed under conditions only for emergency brake'.
- Validation Rules:
-
Magnetic Braking Conditions Document Applicability
Comment: Electronic document available in two EU languages from the IM stored by the Agency with conditions for the use of magnetic brakes identified in 1.1.1.1.6.3.
Message: magneticBrakingConditionsDocument (1.1.1.1.6.5): This error is due to the track or subset with common characteristics {?trackLabel} , violating the rule: Y if the answer to 1.1.1.1.6.3 / Use of magnetic brakes is “allowed under conditions” or “allowed under conditions only for emergency brake”.
-
Magnetic Braking Conditions Document
Comment: Electronic documents available in two EU languages from the IM stored by the Agency with conditions for the use of magnetic brakes identified in 1.1.1.1.6.3.
Message: magneticBrakingConditionsDocument (1.1.1.1.6.5): The track or subset with common characteristics has a magnetic braking conditions document value that must be a Document.
- OPE TSI References
-
- Part of RCC Algorithm:
- true
-
- Appendix D2 Index
- 3.4.6
- Additional Information
-
- General explanation:
- If there exist conditions to allow the use of magnetic brakes.
The value of this parameter should be either a reference to a file name or an external link to a document.
If a file name is provided, the Infrastructure Manager (IM) must upload a document with the same file name using the "Reference Documents Management" functionality in the RINF application. The document must be in electronic format and available in two official EU languages. In this case, the parameter value must be repeated for each document.
If an external link is provided, the IM must ensure that the document is available at the provided link.
Use of flange lubrication forbidden
DP
IRI: http://data.europa.eu/949/flangeLubeForbidden
- Parameter of
-
Running track
-
Subset with common characteristics
- General Information
-
- Number:
- 1.1.1.1.7.1
- XML Name:
- IHS_FlangeLubeForbidden
- Deadline:
- In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
- Belongs to parameters group
-
Health, safety and environment
(
1.1.1.1.7
)
- Data Format
-
- Data Presentation
-
Boolean
- Format:
- in XML: Y/N
- Flags
-
- Applicability Flags:
- Y
- Validation
-
- Validation Rules:
-
Flange Lube Forbidden
Comment: Indication whether the use of on-board device for flange lubrication is forbidden.
Message: flangeLubeForbidden (1.1.1.1.7.1): The track or subset with common characteristics must have at most one flange lube forbidden value that is Y/N (boolean). This error may be due to having more than one value or having a value that is not Y/N (boolean).
Existence of level crossings
DP
IRI: http://data.europa.eu/949/hasLevelCrossings
- Parameter of
-
Running track
-
Subset with common characteristics
- General Information
-
- Number:
- 1.1.1.1.7.2
- XML Name:
- IHS_LevelCrossing
- Deadline:
- In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
- Belongs to parameters group
-
Health, safety and environment
(
1.1.1.1.7
)
- Data Format
-
- Data Presentation
-
Boolean
- Format:
- in XML: Y/N
- Flags
-
- Applicability Flags:
- Y
- Validation
-
- Validation Rules:
-
Has Level Crossings
Comment: Indication whether level crossings (including pedestrian track crossing) exist onf the section line.
Message: hasLevelCrossings (1.1.1.1.7.2): The track or subset with common characteristics must have at most one existence of level crossings value that is Y/N (boolean). This error may be due to having more than one value or having a value that is not Y/N (boolean).
- Additional Information
-
- General explanation:
- This parameter concerns the level crossing of the railway with a road or a street. Provision the correct location of the level crossing(s) is not required, but RINF data model allows providing such information on a voluntary basis, and it can be a geographical information and/or a reference to a line referencing system.
Acceleration allowed near level crossing
OP
IRI: http://data.europa.eu/949/accelerationLevelCrossing
- Parameter of
-
Subset with common characteristics
-
Track
- General Information
-
- Number:
- 1.1.1.1.7.3
- XML Name:
- IHS_AccelerationLevelCrossing
- Deadline:
- In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
- Belongs to parameters group
-
Health, safety and environment
(
1.1.1.1.7
)
- Data Format
-
- Data Presentation
-
ERA Document
- Flags
-
- Applicability Flags:
- Y/N
- Validation
-
- Dependencies:
- Mandatory value when the level crossing is defined
- Validation Rules:
-
Acceleration Level Crossing Applicability
Comment: Existence of limit for acceleration of train if stopping or recovering speed close to a level crossing expressed in a specific reference acceleration curve.
Message: accelerationLevelCrossing (1.1.1.1.7.3): This error is due to the track or subset with common characteristics {?trackLabel} , violating the rule: Applicable only when selected value of parameter 1.1.1.1.7.2 is ‘Y’
-
Acceleration Level Crossing
Comment: Existence of limit for acceleration of train if stopping or recovering speed close to a level crossing expressed in a specific reference acceleration curve.
Message: accelerationLevelCrossing (1.1.1.1.7.3): The track or subset with common characteristics must have at most one acceleration level crossing value that is a Document. This error may be due to having more than one value or having a value that is not an instance of Document.
- Additional Information
-
- General explanation:
- The value of this parameter should be either a reference to a file name or an external link to a document.
If a file name is provided, the Infrastructure Manager (IM) must upload a document with the same file name using the "Reference Documents Management" functionality in the RINF application. The document must be in electronic format and available in two official EU languages. In this case, the parameter value must be repeated for each document.
If an external link is provided, the IM must ensure that the document is available at the provided link.
Existence of trackside hot axle box detector (HABD)
DP
IRI: http://data.europa.eu/949/hasHotAxleBoxDetector
- Parameter of
-
Running track
-
Subset with common characteristics
- General Information
-
- Number:
- 1.1.1.1.7.4
- XML Name:
- IHS_HABDExist
- Deadline:
- 16 January 2020
- Belongs to parameters group
-
Health, safety and environment
(
1.1.1.1.7
)
- Data Format
-
- Data Presentation
-
Boolean
- Format:
- in XML: Y/N
- Flags
-
- Applicability Flags:
- Y
- Validation
-
- Validation Rules:
-
Has Hot Axle Box Detector
Comment: Existence of trackside hot axle box detector.
Message: hasHotAxleBoxDetector (1.1.1.1.7.4): The track or subset with common characteristics must have at most one existence of hot axle box detector value that is Y/N (boolean).
- OPE TSI References
-
- Part of RCC Algorithm:
- true
- Additional Information
-
- General explanation:
- The aim of axle bearing condition monitoring is to detect deficient axle box bearings. The TSI Loc&Pas provides with the requirement that units of maximum design speed higher than or equal to 250 km/h, on board detection equipment shall be provided. For units of maximum design speed lower than 250 km/h, and designed to be operated on others track gauge systems than the 1 520 mm system, axle bearing condition monitoring shall be provided and be achieved either by on board equipment or by using track side equipment. Track side equipment (also known as HABD) are defined from the perspective of rolling stock, for which the zone visible to the trackside equipment is defined by the area referred in the standard EN 15437-1:2009, as required by the TSI Loc&Pas.
This parameter is to indicate whether the section of line is equipped with trackside hot axle box detector (HABD) and is necessary for the route compatibility check.
Trackside HABD TSI compliant
DP
IRI: http://data.europa.eu/949/hotAxleBoxDetectorTSICompliant
- Parameter of
-
Hot Axle Box Detector
- General Information
-
- Number:
- 1.1.1.1.7.5
- XML Name:
- IHS_TSIHABD
- Deadline:
- 16 January 2020
- Belongs to parameters group
-
Health, safety and environment
(
1.1.1.1.7
)
- Data Format
-
- Data Presentation
-
Boolean
- Flags
-
- Applicability Flags:
- Y
- Validation
-
- Validation Rules:
-
Hot Axle Box Detector Tsicompliant
Comment: Trackside HABD compilant to TSI means that the HABD is compliant with EN 15437:2009 and specific cases mentioned in TSIs.
Message: hotAxleBoxDetectorTSICompliant (1.1.1.1.7.5): The track or subset with common characteristics must have at most one value that defines if the hot axle box detector is TSI compliant and the value is Y/N (boolean). This error may be due to having more than one value or having a value that is not Y/N (boolean).
- OPE TSI References
-
- Part of RCC Algorithm:
- true
Identification of trackside HABD
DP
IRI: http://data.europa.eu/949/hotAxleBoxDetectorIdentification
- Parameter of
-
Hot Axle Box Detector
- General Information
-
- Number:
- 1.1.1.1.7.6
- XML Name:
- IHS_HABDID
- Deadline:
- 16 January 2020
- Belongs to parameters group
-
Health, safety and environment
(
1.1.1.1.7
)
- Data Format
-
- Data Presentation
-
String
- Flags
-
- Applicability Flags:
- Y/N
- Validation
-
- Dependencies:
- Mandatory if the HABD is not TSI compliant (the value of parameter 1.1.1.1.7.5 (Trackside HABD TSI compliant) is 'False')
- Validation Rules:
-
Hot Axle Box Detector Identification Applicability
Comment: Specific for the French Italian and Swedish networks. Applicable if trackside HABD is not TSI compliant, identification of trackside hot axle box detector.@en
Message: hotAxleBoxDetectorIdentification (1.1.1.1.7.6): This error is due to the track or subset with common characteristics {?trackLabel}, violating the rule: “Y” if the answer to parameter 1.1.1.1.7.5 is “N”
-
Hot Axle Box Detector Identification
Comment: Specific for the French, Italian and Swedish networks. Applicable if trackside HABD is not TSI compliant. Identification of the trackside HABD.
Message: hotAxleBoxDetectorIdentification (1.1.1.1.7.6): The track or subset with common characteristics must have at most one value that defines the identification of the hot axle box detector and the value is a character string. This error may be due to having more than one value or having a value that is not a string.
- OPE TSI References
-
- Part of RCC Algorithm:
- true
Generation of trackside HABD
DP
IRI: http://data.europa.eu/949/hotAxleBoxDetectorGeneration
- Parameter of
-
Hot Axle Box Detector
- General Information
-
- Number:
- 1.1.1.1.7.7
- XML Name:
- IHS_HABDGen
- Deadline:
- 16 January 2020
- Belongs to parameters group
-
Health, safety and environment
(
1.1.1.1.7
)
- Data Format
-
- Data Presentation
-
String
- Flags
-
- Applicability Flags:
- Y/N
- Validation
-
- Dependencies:
- Mandatory if the HABD is not TSI compliant (the value of parameter 1.1.1.1.7.5 (Trackside HABD TSI compliant) is 'False')
- Validation Rules:
-
Hot Axle Box Detector Generation Applicability
Comment: Specific for the French Italian and Swedish networks. Generation of trackside hot axle box detector. “Y” if the answer to parameter 1.1.1.1.7.5 is “N”
Message: hotAxleBoxDetectorGeneration (1.1.1.1.7.7): This error is due to the track or subset with common characteristics {?trackLabel}, violating the rule: “Y” if the answer to parameter 1.1.1.1.7.5 is “N”
-
Hot Axle Box Detector Generation
Comment: Applicable if trackside HABD is not TSI compliant. Generation of the trackside HABD.
Message: hotAxleBoxDetectorGeneration (1.1.1.1.7.7): The track or subset with common characteristics must have at most one generation of the hot axle box detector value that is Y/N (boolean). This error may be due to having more than one value or having a value that is not Y/N (boolean).
- OPE TSI References
-
- Part of RCC Algorithm:
- true
- Additional Information
-
- General explanation:
- Waiting provision of possible answers by the French, Italian and Swedish NREs
Railway location of trackside HABD
DP
IRI: http://data.europa.eu/949/hotAxleBoxDetectorLocation
- Parameter of
-
Hot Axle Box Detector
- General Information
-
- Number:
- 1.1.1.1.7.8
- XML Name:
- IHS_HABDLoc
- Deadline:
- 16 January 2020
- Belongs to parameters group
-
Health, safety and environment
(
1.1.1.1.7
)
- Data Format
-
- Data Presentation
-
Double
- Flags
-
- Applicability Flags:
- Y/N
- Validation
-
- Dependencies:
- Mandatory if the HABD is not TSI compliant (the value of parameter 1.1.1.1.7.5 (Trackside HABD TSI compliant) is 'False')
- Validation Rules:
-
Hot Axle Box Detector Location Applicability
Comment: Specific for the French Italian and Swedish networks. Applicable if trackside HABD is not TSI compliant, localisation of trackside hot axle box detector.
Message: hotAxleBoxDetectorLocation (1.1.1.1.7.8): This error is due to the track or subset with common characteristics {?trackLabel}, violating the rule: “Y” if the answer to parameter 1.1.1.1.7.5 is “N”
-
Hot Axle Box Detector Location
Comment: Applicable if trackside HABD is not TSI compliant. Location of the trackside HABD.
Message: hotAxleBoxDetectorLocation (1.1.1.1.7.8): The track or subset with common characteristics has a location of the hot axle box detector(s) vallue that must be a double (real) number with format [±NNNN.NNN]. This error may be due to having a value that is not a double (real) number or does not follow the pattern [±NNNN.NNN].
- OPE TSI References
-
- Part of RCC Algorithm:
- true
- Additional Information
-
- General explanation:
- The location (generally the distance from the origin of the line to the point of interest) on a line is given in kilometres with decimals (precision of 0.001).
It may be also possible to provide the location of the HABD as an era:netReference property for the HABD pointing to an era:NetPointReference with (at least)era:LinearPositioningSystemCoordinate
Direction of measurement of trackside HABD
OP
IRI: http://data.europa.eu/949/hotAxleBoxDetectorDirection
- Parameter of
-
Hot Axle Box Detector
- General Information
-
- Number:
- 1.1.1.1.7.9
- XML Name:
- IHS_HABDDirecton
- Deadline:
- 16 January 2020
- Belongs to parameters group
-
Health, safety and environment
(
1.1.1.1.7
)
- Data Format
-
- Data Presentation
-
Concept
- Taxonomy Reference:
-
Hot Axle Box Detector Directions
-
Values :
-
- Flags
-
- Applicability Flags:
- Y/N
- Validation
-
- Dependencies:
- Mandatory if the HABD is not TSI compliant (the value of parameter 1.1.1.1.7.5 (Trackside HABD TSI compliant) is 'False')
- Validation Rules:
-
Hot Axle Box Detector Direction Skos
Comment: Direction of measurement of the trackside HABD.
Message: Indication of the hotAxleBoxDetectorDirection (1.1.1.1.7.9):): The track or subset with common characteristics {$this} has a value {?concept} that is not one of the predefined values and cannot be converted into a SKOS concept on this list: http://data.europa.eu/949/concepts/hot-axle-box-detector-direction/HotAxleBoxDetectorDirections.
-
Hot Axle Box Detector Direction Applicability
Comment: Specific for the French Italian and Swedish networks. If the direction of measurement is: - the same as the direction defined by the start and end of the SoL: (N); - the opposite to the direction defined by the start and end of the SoL: (O); - both directions: (B). “Y” if the answer to parameter 1.1.1.1.7.5 is “N”.
Message: hotAxleBoxDetectorDirection (1.1.1.1.7.9): This error is due to the track or subset with common characteristics {?trackLabel}, violating the rule: “Y” if the answer to parameter 1.1.1.1.7.5 is “N”
-
Hot Axle Box Detector Direction
Comment: Direction of measurement of the trackside HABD.
Message: hotAxleBoxDetectorDirection (1.1.1.1.7.9): The track or subset with common characteristics must have at most one direction of measurement of the hot axle box detector value that is an IRI. This error may be due to the track having more than one value of hot axle box detector direction.
- OPE TSI References
-
- Part of RCC Algorithm:
- true
- Additional Information
-
- General explanation:
- Specific for the French Italian and Swedish networks.
Applicable if trackside HABD is not TSI compliant, direction of measurement of trackside hot axle box detector.
If the direction of measurement is:
- the same as the direction defined by the start and end of the SoL: (N)
- the opposite to the direction defined by the start and end of the SoL: (O)
- both directions: (B)
Steady red lights required
DP
IRI: http://data.europa.eu/949/redLightsRequired
- Parameter of
-
Running track
-
Subset with common characteristics
- General Information
-
- Number:
- 1.1.1.1.7.10
- XML Name:
- IHS_RedLights
- Deadline:
- 1 January 2021
- Belongs to parameters group
-
Health, safety and environment
(
1.1.1.1.7
)
- Data Format
-
- Data Presentation
-
Boolean
- Format:
- in XML: Y/N
- Flags
-
- Applicability Flags:
- Y/N
- Validation
-
- Validation Rules:
-
Red Lights Required
Comment: Sections where two steady red lights are required in accordance with Implementing Regulations (EU) 2019/773.
Message: redLightsRequired (1.1.1.1.7.10): The track or subset with common characteristics must have at most one value that defines if two steady red lights are required and the value must be Y/N (boolean). This error may be due to having more than one value or having a value that is not Y/N (boolean).
- Additional Information
-
- General explanation:
- Regulation (EU) 2019/773 says:
Specific case:
Belgium, France, Italy, Portugal, Spain and UK may continue to apply notified national rules that require freight trains to be equipped with 2 steady red lights as a condition to run on sections of their network, where this is justified by operating practices already in place and/or national rules notified before end of January 2019.
Cooperation with neighbouring countries:
In the meantime Member States concerned, in particular at the request of the railway undertakings, shall perform an assessment with a view to accept the use of 2 reflective plates in one or more sections of their network if the result of the assessment is positive and define appropriate conditions, which shall be based upon an assessment of the risks and operational requirements. This assessment shall be completed within a maximum period of 6 months after receiving the railway undertaking's request. The acceptance of reflective plates shall be granted, unless the Member State can duly justify the refusal based on the negative result of the assessment.
Member States shall in particular endeavour to permit the use of reflective plates on rail freight corridors, with a view to prioritise the current bottlenecks. These sections and details of any conditions pertaining to them shall be recorded in the RINF. Until the information is encoded in RINF, the infrastructure manager shall ensure the information is communicated to railway undertakings by other appropriate means. The infrastructure manager shall identify the sections of lines on which 2 steady red lights are required in the RINF.
Belonging to a quieter route
DP
IRI: http://data.europa.eu/949/isQuietRoute
- Parameter of
-
Running track
-
Subset with common characteristics
- General Information
-
- Number:
- 1.1.1.1.7.11
- XML Name:
- IHS_QuietRoute
- Deadline:
- 1 January 2021
- Belongs to parameters group
-
Health, safety and environment
(
1.1.1.1.7
)
- Data Format
-
- Data Presentation
-
Boolean
- Format:
- in XML: Y/N
- Flags
-
- Applicability Flags:
- Y
- Validation
-
- Validation Rules:
-
Is Quiet Route
Comment: Belonging to a 'quiet route' in accordance with Article 5b of Regulation (EU) 1304/2014.
Message: isQuietRoute (1.1.1.1.7.11): The track or subset with common characteristics must have at most one value that defines if it belongs to a 'quiet route' and the value must be Y/N (boolean). This error may be due to having more than one value or having a value that is not Y/N (boolean).
- Additional Information
-
- General explanation:
- Art 5B: A quieter route means a part of the railway infrastructure with a minimum length of 20 km on which the average number of daily operated freight trains during the night-time as defined in national legislation transposing Directive 2002/49/EC of the European Parliament and of the Council (5) was higher than 12. The freight traffic in the years 2015, 2016 and 2017 shall be the basis for the calculation of that average number. In case the freight traffic due to exceptional circumstances diverges in a given year from that average number by more than 25 %, the Member State concerned can calculate the average number on the basis of the remaining two years.
Art 5.C 1: Member States shall designate quieter routes in accordance with Article 5b and the procedure set out in Appendix D.1 of the Annex. They shall provide the European Union Agency for Railways ( the Agency ) with a list of quieter routes six months after the date of publication of this Regulation at the latest. The Agency shall publish those lists on its website.
Permit of use of reflective plates
DP
IRI: http://data.europa.eu/949/permitUseReflectivePlates
- Parameter of
-
Running track
-
Subset with common characteristics
- General Information
-
- Number:
- 1.1.1.1.7.12
- XML Name:
- IHS_ReflectivePlates
- Deadline:
- 12 months after publication of Article 7 Guide
- Belongs to parameters group
-
Health, safety and environment
(
1.1.1.1.7
)
- Data Format
-
- Data Presentation
-
Boolean
- Flags
-
- Applicability Flags:
- Y/N/NYA
- Additional Information
-
- General explanation:
- From TSI OPE: Member States shall in particular endeavour to permit the use of reflective plates on rail freight corridors, with a view to prioritise the current bottlenecks. These sections and details of any conditions pertaining to them shall be recorded in the RINF. Until the information is encoded in RINF, the infrastructure manager shall ensure the information is communicated to railway undertakings by other appropriate means. The infrastructure manager shall identify the sections of lines on which 2 steady red lights are required in the RINF.
Conditions for use of reflective plates
OP
IRI: http://data.europa.eu/949/conditionsUseReflectivePlates
- Parameter of
-
Running track
-
Subset with common characteristics
- General Information
-
- Number:
- 1.1.1.1.7.12.1
- XML Name:
- IHS_ReflectivePlatesConditions
- Deadline:
- 12 months after publication of Article 7 Guide
- Belongs to parameters group
-
Health, safety and environment
(
1.1.1.1.7
)
- Data Format
-
- Data Presentation
-
Concept
- Taxonomy Reference:
-
Conditions for use of reflective plates
-
Values :
-
| Code |
Value |
| 00 |
Placeholder |
- Flags
-
- Applicability Flags:
- Y/N/NYA
- Validation
-
- Dependencies:
- A value is mandatory if the value of parameter "Permit of use of reflective plates" is boolean "Yes"
- Validation Rules:
-
Conditions Use Reflective Plates
Comment: Details of any conditions for using the reflective plates on freight corridors. Specific case for Portugal and Spain until 1.1.2025 and Belgium and France until 1.1.2026.
Message: conditionsUseReflectivePlates (1.1.1.1.7.12.1): The track or subset with common characteristics may have a value of the conditions for use of reflective plates. This error may be due to the track having a value that is not an IRI.
-
Conditions Use Reflective Plates Skos
Comment: Details of any conditions for using the reflective plates on freight corridors. Specific case for Portugal and Spain until 1.1.2025 and Belgium and France until 1.1.2026.
Message: Indication of the conditionsUseReflectivePlates (1.1.1.1.7.12.1): The track or subset with common characteristics {$this} has a value {?concept} that is not one of the predefined values and cannot be converted into a SKOS concept on this list: http://data.europa.eu/949/concepts/conditions-use-reflective-plates/ConditionsUseReflectivePlates.
- Additional Information
-
- General explanation:
- From TSI OPE: Member States shall in particular endeavour to permit the use of reflective plates on rail freight corridors, with a view to prioritise the current bottlenecks. These sections and details of any conditions pertaining to them shall be recorded in the RINF. Until the information is encoded in RINF, the infrastructure manager shall ensure the information is communicated to railway undertakings by other appropriate means. The infrastructure manager shall identify the sections of lines on which 2 steady red lights are required in the RINF.
Tunnel identification
DP
IRI: http://data.europa.eu/949/tunnelIdentification
- Parameter of
-
Tunnel
- General Information
-
- Number:
- 1.1.1.1.8.2
- 1.2.1.0.5.2
- 1.2.2.0.5.2
- XML Name:
- SOLTunnelIdentification
- OPTrackTunnelIdentification
- OPSidingTunnelIdentification
- Deadline:
- In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
- Belongs to parameters group
-
Tunnel
(
1.1.1.1.8
|
1.2.1.0.5
|
1.2.2.0.5
)
-
Identifier
- Data Format
-
- Data Presentation
-
String
- Flags
-
- Applicability Flags:
- Y
- Validation
-
- Validation Rules:
-
Tunnel Identification
Comment: Unique tunnel identification or unique number within Member State.
Message: tunnelIdentification (1.1.1.1.8.2, 1.2.1.0.5.2, 1.2.2.0.5.2): Each Tunnel can be referred with only one identification. This error may be due to having a Tunnel with no identification, with more than one identification or with an identification that is not a character string.
- OPE TSI References
-
- Appendix D2 Index
- 3.2.3
- Additional Information
-
- General explanation:
- Here should be given the name, number, code or any other expression which is normally used for the identification of the tunnel other than mentioned in parameters 1.1.1.1.8.3 1.1.1.1.8.4. In case when tunnel does not have its own identification within the Member State, the IM should deliver it himself
Start of tunnel kilometer
OP
IRI: http://data.europa.eu/949/lineReferenceTunnelStart
- Parameter of
-
Tunnel
- General Information
-
- Number:
- 1.1.1.1.8.3
- XML Name:
- SOLTunnelStart
- Deadline:
- In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
- Belongs to parameters group
-
Tunnel
(
1.1.1.1.8
|
1.2.1.0.5
|
1.2.2.0.5
)
- Data Format
-
- Data Presentation
-
Net Point Reference
- Flags
-
- Applicability Flags:
- Y
- Validation
-
- Validation Rules:
-
Line Reference Tunnel Start
Comment: Part of the Start of tunnel that indicates the km of the line at the beginning of a tunnel.
Message: lineReferenceTunnelStart (1.1.1.1.8.3): A Tunnel may have a start of tunnel location (lineReferenceTunnelStart). This error may be due to a value that is not an IRI, more than one value being provided, or a value that is not a NetPointReference.
- Additional Information
-
- General explanation:
- Geographical coordinates according to the standard World Geodetic System (WGS). Precision for both geographical latitude and geographical longitude is assumed as [NN.NNNNNNN] in degrees with decimals what gives discretion of 10 cm in the network.
Kilometre shall concern the national line identification given in 1.1.0.0.0.2
Location of the point which is assumed to be the beginning of the tunnel it is the point on the track centre line where is laid the vertical shadow of the extreme part of the tunnel s portal.
-
- Example:
- Kilometer=`0.895`
Start of tunnel location
OP
IRI: http://data.europa.eu/949/startLocation
- Parameter of
-
Tunnel
- General Information
-
- Number:
- 1.1.1.1.8.3
- XML Name:
- SOLTunnelStart
- Belongs to parameters group
-
HasGeometry
(
1.1.0.0.1.1
|
1.1.1.0.1.1
|
1.1.1.3.14.6
|
1.2.0.0.0.5
|
1.2.1.0.8.5
)
-
Tunnel
(
1.1.1.1.8
|
1.2.1.0.5
|
1.2.2.0.5
)
- Data Format
-
- Data Presentation
-
Point
- Validation
-
- Validation Rules:
-
Start Location
Comment: Part of the Start of tunnel that indicates the Geographical coordinates according to the standard World Geodetic System (WGS).
Message: startLocation (1.1.1.1.8.3): The Tunnel may have a start location (startLocation) reference that is a Geometry object or a Point. This error mey be due to a startLocation relationship from a Tunnel that is not a Geometry nor a Point.
End of tunnel
OP
IRI: http://data.europa.eu/949/endLocation
- Parameter of
-
Tunnel
- General Information
-
- Number:
- 1.1.1.1.8.4
- XML Name:
- SOLTunnelEnd
- Deadline:
- In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
- Belongs to parameters group
-
HasGeometry
(
1.1.0.0.1.1
|
1.1.1.0.1.1
|
1.1.1.3.14.6
|
1.2.0.0.0.5
|
1.2.1.0.8.5
)
-
Tunnel
(
1.1.1.1.8
|
1.2.1.0.5
|
1.2.2.0.5
)
- Data Format
-
- Data Presentation
-
Point
- Flags
-
- Applicability Flags:
- Y
- Validation
-
- Validation Rules:
-
End Location
Comment: Geographical coordinates in decimal degrees and km of the line at the end of a tunnel.
Message: endLocation (1.1.1.1.8.4): The Tunnel may have an end location (endLocation) reference that is a Geometry object or a Point. This error mey be due to an endLocation relationship from a Tunnel that is not a Geometry nor a Point.
- Additional Information
-
- General explanation:
- Geographical coordinates according to the standard World Geodetic System (WGS). Precision for both geographical latitude and geographical longitude is assumed as [NN.NNNNNNN] in degrees with decimals what gives discretion of 10 cm in the network.
Kilometre shall concern the national line identification given in 1.1.0.0.0.2
Location of the point which is assumed to be the end of the tunnel it is the point on the track centre line where is laid the vertical shadow of the extreme part of the tunnel s portal.
-
- Example:
- Latitude=`51.5479123` Longitude=`-0.076732`
End of tunnel kilometer
OP
IRI: http://data.europa.eu/949/lineReferenceTunnelEnd
- Parameter of
-
Tunnel
- General Information
-
- Number:
- 1.1.1.1.8.4
- XML Name:
- SOLTunnelEnd
- Belongs to parameters group
-
Tunnel
(
1.1.1.1.8
|
1.2.1.0.5
|
1.2.2.0.5
)
- Data Format
-
- Data Presentation
-
Net Point Reference
- Validation
-
- Validation Rules:
-
Line Reference Tunnel End
Comment: Part of the End of tunnel that indicates the km of the line at the end of a tunnel.
Message: lineReferenceTunnelEnd (1.1.1.1.8.4): A Tunnel may have an end of tunnel location (lineReferenceTunnelEnd). This error may be due to a value that is not an IRI, more than one value being provided, or a value that is not a NetPointReference.
- Additional Information
-
- General explanation:
- Parameters of this group (from 1.1.1.1.8.1 to 1.1.1.1.8.13) are only applicable if tunnels exist on the SoL
-
- Example:
- Kilometer=`0.270`
EC declaration of verification relating to compliance with the requirements from TSIs applicable to railway tunnel
DP
IRI: http://data.europa.eu/949/verificationSRT
- Parameter of
-
Subset with common characteristics
-
Tunnel
- General Information
-
- Number:
- 1.1.1.1.8.5
- 1.2.1.0.5.3
- 1.2.2.0.5.3
- XML Name:
- ITU_ECVerification
- Deadline:
- In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
- Belongs to parameters group
-
Tunnel
(
1.1.1.1.8
|
1.2.1.0.5
|
1.2.2.0.5
)
- Data Format
-
- Data Presentation
-
String
- Format:
- CC/RRRRRRRRRRRRRR/YYYY/NNNNNN
- Flags
-
- Applicability Flags:
- Y/N
- Validation
-
- Validation Rules:
-
Verification Srt
Comment: Unique number for EC declarations following format requirements specified in the 'Document about practical arrangements for transmitting interoperability documents'
Message: verificationSRT (1.1.1.1.8.5, 1.2.1.0.5.3, 1.2.2.0.5.3): Each Tunnel may have one or more verificationSRT following this pattern country code/national registration number/year between 1900 and 2100/progressive counter. This error may be due to having a value that does not follow the pattern or that is not a character string.
- Additional Information
-
- General explanation:
- (SRT) in title means that here we include only declarations concerning requirements of SRT TSI for infrastructure system on the specific track.
Parameter shall be repeated when different EC declarations were issued for different elements of infrastructure subsystem on the specific track in the tunnel.
With the extension of scope according to Interoperability Directive 2016/797, geographical scope of the INF, ENE and CCS TSIs now includes all the networks (TEN and off-TEN) with the following nominal track gauges: 1435, 1520, 1524, 1600 and 1668 mm
EI declaration of demonstration (as defined in Recommendation 2014/881/EU) relating to compliance with the requirements from TSIs applicable to railway tunnel
DP
IRI: http://data.europa.eu/949/demonstrationSRT
- Parameter of
-
Subset with common characteristics
-
Tunnel
- General Information
-
- Number:
- 1.1.1.1.8.6
- 1.2.1.0.5.4
- 1.2.2.0.5.4
- XML Name:
- ITU_EIDemonstration
- Deadline:
- In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
- Belongs to parameters group
-
Tunnel
(
1.1.1.1.8
|
1.2.1.0.5
|
1.2.2.0.5
)
- Data Format
-
- Data Presentation
-
String
- Format:
- CC/RRRRRRRRRRRRRR/YYYY/NNNNNN
- Flags
-
- Applicability Flags:
- Y/N
- Validation
-
- Dependencies:
- Applicable in case when the demonstration was executed and EI declaration was issued.
The procedure for demonstration that existing network fits to requirements of the TSIs is executed on voluntary bases, so when EI declaration do not exist then the parameter is optional.
- Validation Rules:
-
Demonstration Srt
Comment: Unique number for EI declarations following the same format requirements as specified in the 'Document about practical arrangements for transmitting interoperability documents'
Message: demonstrationSRT (1.1.1.1.8.6, 1.2.1.0.5.4, 1.2.2.0.5.4): Each Tunnel may have one or more demonstrationSRT following this pattern country code/national registration number/year between 1900 and 2100/progressive counter. This error may be due to having a value that does not follow the pattern or that is not a character string.
- Additional Information
-
- General explanation:
- (SRT) in title means that here we include only declarations concerning requirements of SRT TSI for infrastructure system on the specific track.
Parameter shall be repeated when different EI declarations were issued for different elements of infrastructure subsystem on the specific track in the tunnel.
It may happen that several EI declarations were issued then parameter has to be repeated as many times as many declarations were issued.
The procedure for demonstration that existing network fits to requirements of the TSIs is executed on voluntary bases, so when EI declaration do not exist then the parameter is optional.
Length of tunnel
DP
IRI: http://data.europa.eu/949/lengthOfTunnel
- Parameter of
-
Tunnel
- General Information
-
- Number:
- 1.1.1.1.8.7
- 1.2.1.0.5.5
- 1.2.2.0.5.5
- XML Name:
- ITU_Length
- Deadline:
- In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
- Belongs to parameters group
-
Tunnel
(
1.1.1.1.8
|
1.2.1.0.5
|
1.2.2.0.5
)
-
Length
- Data Format
-
- Data Presentation
-
Double
- Format:
- NNNNN
- Unit of Measure:
-
Metre
- Flags
-
- Applicability Flags:
- Y
- Validation
-
- Dependencies:
- Only applicable for a tunnel with length of 100 metres or more.
- Validation Rules:
-
Length T
Comment: Length of a tunnel in metres from entrance portal to exit portal.
Message: length (1.1.1.1.8.7, 1.2.1.0.5.5, 1.2.2.0.5.5): A Tunnel must have at most one length declaration. This error may be due to having a tunnel with more than one length or to having a value that is not a double (real) number.
- OPE TSI References
-
- Part of RCC Algorithm:
- true
-
- Appendix D2 Index
- 3.2.3
- Additional Information
-
- General explanation:
- Length of a tunnel is expressed in metres from portal to portal at the level of the top of rail.
Cross section area
DP
IRI: http://data.europa.eu/949/crossSectionArea
- Parameter of
-
Subset with common characteristics
-
Tunnel
- General Information
-
- Number:
- 1.1.1.1.8.8
- XML Name:
- ITU_CrossSectionArea
- Deadline:
- In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
- Belongs to parameters group
-
Tunnel
(
1.1.1.1.8
|
1.2.1.0.5
|
1.2.2.0.5
)
- Data Format
-
- Data Presentation
-
Integer
- Format:
- NNN
- Unit of Measure:
-
Square metre
- Flags
-
- Applicability Flags:
- Y/N
- Validation
-
- Dependencies:
- Mandatory if the speed of the line is equal or greater than 200km/h
- Validation Rules:
-
Cross Section Area T
Comment: Smallest cross section area in square metres of the tunnel.
Message: crossSectionArea (1.1.1.1.8.8): A Tunnel can have at most one crossSectionArea. This error may be due to having a tunnel with more than one crossSectionArea or having a value that is not an integer number.
-
Cross Section Area Applicability
Comment: Y (applicable) if is speed of the line equal or greater than 200km/h.
Message: crossSectionArea (1.1.1.1.8.8): The Tunnel {$this} ({?label}) has a maximum permitted speed of {?tunnelSpeed} Km/h . For any tunnel with a speed of the line equal or greater than 200km/h the crossSectionArea parameter is applicable. This error is due to {$this} not having a value for such a parameter.
- Additional Information
-
- General explanation:
- Smallest real cross section area (expressed in square metres) of the tunnel.
Reference: 4.2.10.1 of INF TSI on Maximum pressure variations in tunnels.
Compliance of the tunnel with TSI INF
DP
IRI: http://data.europa.eu/949/complianceInfTsi
- Parameter of
-
Subset with common characteristics
-
Tunnel
- General Information
-
- Number:
- 1.1.1.1.8.8.1
- XML Name:
- ITU_TSITunnel
- Deadline:
- 1 January 2021
- Belongs to parameters group
-
Tunnel
(
1.1.1.1.8
|
1.2.1.0.5
|
1.2.2.0.5
)
- Data Format
-
- Data Presentation
-
Boolean
- Flags
-
- Applicability Flags:
- Y/N
- Validation
-
- Dependencies:
- Mandatory if the speed of the line is equal or greater than 200km/h
- Validation Rules:
-
Compliance Inf Tsi P
Comment: Compliance of the tunnel with INF TSI at the maximum permitted speed.
Message: complianceInfTsi (1.1.1.1.8.8.1): A Tunnel can have at most one complianceInfTsi. This error may be due to having a tunnel with more than one complianceInfTsi or having a value type different than Y/N (boolean).
-
Compliance Inf Tsi Applicability
Comment: Y (applicable) if is speed of the line equal or greater than 200km/h.
Message: complianceInfTsi (1.1.1.1.8.9, 1.2.1.0.5.6, 1.2.2.0.5.6): The Tunnel {$this} ({?label}) has a maximum permitted speed of {?tunnelSpeed} Km/h . For any tunnel with a speed of the line equal or greater than 200km/h the complianceInfTsi parameter is applicable. This error is due to {$this} not having a value for such a parameter.
Document available from the IM with precise description of the tunnel
OP
IRI: http://data.europa.eu/949/tunnelDocRef
- Parameter of
-
Tunnel
- General Information
-
- Number:
- 1.1.1.1.8.8.2
- XML Name:
- ITU_TunnelDocRef
- Deadline:
- 1 January 2021
- Belongs to parameters group
-
Tunnel
(
1.1.1.1.8
|
1.2.1.0.5
|
1.2.2.0.5
)
- Data Format
-
- Data Presentation
-
ERA Document
- Flags
-
- Applicability Flags:
- Y/N
- Validation
-
- Validation Rules:
-
Tunnel Doc Ref
Comment: Electronic document available from the IM stored by the Agency with precise description of the clearance gauge and geometry of the tunnel
Message: tunnelDocRef (1.1.1.1.8.8.2): A Tunnel has a tunnelDocRef with precise description of the clearance gauge and geometry of the tunnel, and it must be a Document. This error a due to having a value that is not an instance of Document
- Additional Information
-
- General explanation:
- The value of this parameter should be either a reference to a file name or an external link to a document.
If a file name is provided, the Infrastructure Manager (IM) must upload a document with the same file name using the "Reference Documents Management" functionality in the RINF application. The document must be in electronic format and available in two official EU languages. In this case, the parameter value must be repeated for each document.
If an external link is provided, the IM must ensure that the document is available at the provided link.
Existence of emergency plan
DP
IRI: http://data.europa.eu/949/hasEmergencyPlan
- Parameter of
-
Subset with common characteristics
-
Tunnel
- General Information
-
- Number:
- 1.1.1.1.8.9
- 1.2.1.0.5.6
- 1.2.2.0.5.6
- XML Name:
- ITU_EmergencyPlan
- Deadline:
- In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
- Belongs to parameters group
-
Tunnel
(
1.1.1.1.8
|
1.2.1.0.5
|
1.2.2.0.5
)
- Data Format
-
- Data Presentation
-
Boolean
- Flags
-
- Applicability Flags:
- Y/N
- Validation
-
- Dependencies:
- Mandatory for tunnels longer than 1 km
- Validation Rules:
-
Has Emergency Plan Applicability
Comment: Applicable for tunnels longer than 1 km.
Message: hasEmergencyPlan (1.1.1.1.8.9, 1.2.1.0.5.6, 1.2.2.0.5.6): The Tunnel {$this} ({?label}) has a length of {?tunnelLength} meters. Any tunnel longer than 1 Km makes the hasEmergencyPlan parameter applicable. This error is due to {$this} not having a value for such a parameter.
-
Has Emergency Plan
Comment: Indication whether emergency plan exists.
Message: hasEmergencyPlan (1.1.1.1.8.9, 1.2.1.0.5.6, 1.2.2.0.5.6): A Tunnel has an indication about the existence of an emergency plan. This error may be due to having a tunnel with more than one value for hasEmergencyPlan or having a value type different than Y/N (boolean).
- Additional Information
-
- General explanation:
- A value may not be applicable for tunnels shorter than 1 km, as for them the fire category according SRT TSI does not exist.
Emergency plan has to be a document developed for each tunnel under the direction of the IM, in co-operation, where appropriate, with RUs, Rescue services and relevant authorities. It shall be consistent with the self-rescue, evacuation and rescue facilities provided.
It is applicable for tunnels longer than 1 km, in accordance with section 4.4.2 of SRT TSI, the emergency plan is mandatory only for tunnel length of more than 1km.
SRT TSI: 4.4.2
OPE TSI: 4.2.3.7
Fire category of rolling stock required
OP
IRI: http://data.europa.eu/949/rollingStockFireCategory
- Parameter of
-
Subset with common characteristics
-
Tunnel
- General Information
-
- Number:
- 1.1.1.1.8.10
- 1.2.1.0.5.7
- 1.2.2.0.5.7
- XML Name:
- ITU_FireCatReq
- Deadline:
- In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
- Belongs to parameters group
-
Tunnel
(
1.1.1.1.8
|
1.2.1.0.5
|
1.2.2.0.5
)
- Data Format
-
- Data Presentation
-
Concept
- Taxonomy Reference:
-
Rolling Stock Fire Categories
-
Values :
-
- Flags
-
- Applicability Flags:
- Y/N
- Validation
-
- Dependencies:
- Mandatory for tunnels longer than 1 km
- Validation Rules:
-
Rolling Stock Fire Category Applicability
Comment: Applicable for tunnels longer than 1 km.
Message: rollingStockFireCategory (1.1.1.1.8.10, 1.2.1.0.5.7, 1.2.2.0.5.7): The Tunnel {$this} ({?label}) has a length of {?tunnelLength} meters. Any tunnel longer than 1 Km makes the rollingStockFireCategory parameter applicable. This error is due to {$this} not having a value for such a parameter.
-
Rolling Stock Fire Category Skos
Comment: Categorisation on how a passenger train with a fire on board will continue to operate for a defined time period
Message: Categorisation on how a passenger train with a fire on board will continue to operate (1.1.1.1.8.10, 1.2.1.0.5.7, 1.2.2.0.5.7): The tunnel {$this} (label {?tunnelLabel}) has a value {?concept} that is not one of the predefined values and cannot be converted into a SKOS concept on this list: http://data.europa.eu/949/concepts/rolling-stock-fire/Categories.
-
Rolling Stock Fire Category
Comment: Categorisation on how a passenger train with a fire on board will continue to operate for a defined time period
Message: rollingStockFireCategory (1.1.1.1.8.10, 1.2.1.0.5.7, 1.2.2.0.5.7): A Tunnel may have an indication about the rollingStockFireCategory. This error may be due to having a tunnel without a rollingStockFireCategory declaration or having a literal as value. This error may be due to a tunnel having more than one value or having a value that is not an IRI.
- OPE TSI References
-
- Part of RCC Algorithm:
- true
-
- Appendix D2 Index
- 3.2.3
- Additional Information
-
- General explanation:
- Wherever category B is not needed, generally the category A has to be understood as the default value. None shall be selected when none of A or B fire category is applied for a specific tunnel.
For tunnels shorter than 1km, the fire category according to SRT TSI does not exist.
National fire category of rolling stock required
DP
IRI: http://data.europa.eu/949/nationalRollingStockFireCategory
- Parameter of
-
Subset with common characteristics
-
Tunnel
- General Information
-
- Number:
- 1.1.1.1.8.11
- 1.2.1.0.5.8
- 1.2.2.0.5.8
- XML Name:
- ITU_NatFireCatReq
- Deadline:
- In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
- Belongs to parameters group
-
Tunnel
(
1.1.1.1.8
|
1.2.1.0.5
|
1.2.2.0.5
)
- Data Format
-
- Data Presentation
-
String
- Flags
-
- Applicability Flags:
- Y/N
- Validation
-
- Dependencies:
- Mandatory for tunnels without value for 1.1.1.8.10 and where national values exist.
- Validation Rules:
-
National Rolling Stock Fire Category Applicability
Comment: Applicable only for tunnels when for the parameter 1.1.1.1.8.10 the option 'none' was selected and national rules exist.
Message: nationalRollingStockFireCategory (1.1.1.1.8.11, 1.2.1.0.5.8, 1.2.2.0.5.8): The Tunnel {$this} ({?clsLabel}), has a 'rolling stock fire' category that makes the nationalRollingStockFireCategory parameter applicable. This error is due to {$this} not having a value for such a parameter.
-
National Rolling Stock Fire Category
Comment: Categorisation on how a passenger train with a fire on board will continue to operate for a defined time period - according to national rules if they exist.
Message: nationalRollingStockFireCategory (1.1.1.1.8.11, 1.2.1.0.5.8, 1.2.2.0.5.8): A Tunnel may have an indication about the nationalRollingStockFireCategory. This error may be due to having a tunnel with more than one value or having a value type different than string.
- OPE TSI References
-
- Part of RCC Algorithm:
- true
- Additional Information
-
- General explanation:
- Data shall include both the category and brief name of the document introducing the categorisation.
A value is mandatory only for tunnels when the value of the parameter 1.1.1.1.8.10 is none and national rules exist.
It may be not applicable when respective national rules do not exist
Existence of walkways
DP
IRI: http://data.europa.eu/949/hasWalkway
- Parameter of
-
Subset with common characteristics
-
Tunnel
- General Information
-
- Number:
- 1.1.1.1.8.12
- 1.2.1.0.5.10
- 1.2.2.0.5.9
- Deadline:
- 12 months after publication of Article 7 Guide
- Belongs to parameters group
-
Tunnel
(
1.1.1.1.8
|
1.2.1.0.5
|
1.2.2.0.5
)
- Data Format
-
- Data Presentation
-
Boolean
- Format:
- [Y/N]
If =Y then TSI-Compliant OR NON-TSI-Compliant
- Flags
-
- Applicability Flags:
- Y/NYA
- Validation
-
- Dependencies:
- Mandatory for TSI-compliant tunnels longer than 0.5 km
- Validation Rules:
-
Has Walkway
Comment: Indication of existence of walkways.
Message: hasWalkway (1.1.1.1.8.12, 1.2.1.0.5.10, 1.2.2.0.5.9): A Tunnel can have at most one hasWalkway. This error may be due to having a tunnel with more than one hasWalkway or having a value type different than Y/N (boolean).
- OPE TSI References
-
- Appendix D2 Index
- 3.2.3
- Additional Information
-
- General explanation:
- Indicates the existence of "Escape walkways", if the tunnel is longer than 0.5km then definition from Section 4.2.1.6 of TSI SRT applies.
If the selected value is "true", provide the boolean value for "Is TSI compliant".
On top of the requirements set out in the TSI SRT, the application guide to the TSI allows to use a ballastless track as a walkway. So, a 'Yes' in this parameters might not result in a physical standalone walkway.
For Siding the mechanism to locate a specific object is different depending on the member state. The TWG is still working on it.
Existence of evacuation and rescue points
DP
IRI: http://data.europa.eu/949/hasEvacuationAndRescuePoints
- Parameter of
-
Subset with common characteristics
-
Tunnel
- General Information
-
- Number:
- 1.1.1.1.8.13
- 1.2.1.0.5.11
- 1.2.2.0.5.10
- Deadline:
- 12 months after publication of Article 7 Guide
- Belongs to parameters group
-
Tunnel
(
1.1.1.1.8
|
1.2.1.0.5
|
1.2.2.0.5
)
- Data Format
-
- Data Presentation
-
Boolean
- Flags
-
- Applicability Flags:
- Y/N/NYA
- Validation
-
- Dependencies:
- Mandatory for TSI-compliant tunnels longer than 0.5 km
- Validation Rules:
-
Has Evacuation And Rescue Points
Comment: Indication of existence of evacuation and rescue points.
Message: hasEvacuationAndRescuePoints (1.1.1.1.8.13, 1.2.1.0.5.11, 1.2.2.0.5.10): A Tunnel has an indication about the existence of an evacuation and rescue points. This error may be due to having a tunnel with more than one value for hasEvacuationAndRescuePoints or having a value type different than Y/N (boolean).
- OPE TSI References
-
- Appendix D2 Index
- 3.2.3
EC declaration of verification for track relating to compliance with the requirements from TSIs applicable to energy subsystem
DP
IRI: http://data.europa.eu/949/verificationENE
- Parameter of
-
Running track
-
Subset with common characteristics
- General Information
-
- Number:
- 1.1.1.2.1.1
- XML Name:
- EDE_ECVerification
- Deadline:
- In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
- Belongs to parameters group
-
Declarations of verification for track
(
1.1.1.2.1
)
- Data Format
-
- Data Presentation
-
String
- Flags
-
- Applicability Flags:
- Y/N
- Validation
-
- Validation Rules:
-
Verification Ene
Comment: Unique number for EC declarations following format requirements specified in the 'Document about practical arrangents for transmitting interoperability documents' .
Message: verificationENE (1.1.1.2.1.1): The track or subset with common characteristics has a number for EC declarations that must follow format CC/XXXXXXXXXXXXXX/YYYY/NNNNNN where CC is country code, XXXXX... is a number, YYYY is a year between 1900 and 2100, NNNNNN is the number for the EC declaration. This error may be due to the track having a value that does not follow the pattern.
EI declaration of demonstration (as defined Recommendation 2014/881/EU) for track relating to compliance with the requirements from TSIs applicable to energy subsystem
DP
IRI: http://data.europa.eu/949/demonstrationENE
- Parameter of
-
Running track
-
Subset with common characteristics
- General Information
-
- Number:
- 1.1.1.2.1.2
- XML Name:
- EDE_EIDemonstration
- Deadline:
- In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
- Belongs to parameters group
-
Declarations of verification for track
(
1.1.1.2.1
)
- Data Format
-
- Data Presentation
-
String
- Flags
-
- Applicability Flags:
- Y/N
- Validation
-
- Validation Rules:
-
Demonstration Ene
Comment: Unique number for EI declarations following the same format requirements as specified in the 'Document about practical arrangents for transmitting interoperability documents'.
Message: demonstrationENE (1.1.1.2.1.2): The track or subset with common characteristics has a number for EI declarations that must follow format CC/XXXXXXXXXXXXXX/YYYY/NNNNNN where CC is country code, XXXXX... is a number, YYYY is a year between 1900 and 2100, NNNNNN is the number for the EI declaration. This error may be due to the track having a value that is not a tring or that does not follow the pattern.
Energy supply system (Voltage and frequency)
OP
IRI: http://data.europa.eu/949/energySupplySystem
- Parameter of
-
Contact Line System
-
Vehicle Type
- General Information
-
- Number:
- 1.1.1.2.2.1.2
- XML Name:
- ECS_VoltFreq
- Deadline:
- In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
- Belongs to parameters group
-
Contact line system
(
1.1.1.2.2
)
-
Vehicle type technical characteristic
- Data Format
-
- Data Presentation
-
Concept
- Taxonomy Reference:
-
Energy Supply Systems
-
Values :
-
- Flags
-
- Applicability Flags:
- Y/N
- Validation
-
- Dependencies:
- When `not electrified` is chosen in parameter 1.1.1.2.2.1.1, then this parameter is not applicable.
- Validation Rules:
-
Energy Supply System
Comment: Indication of the traction supply system
Message: energySupplySystem (1.1.1.2.2.1.2): The contact line system defines the energy supply system.This error is due to a contact line system having more than one value for this property or having a value that is not an IRI.
-
Energy Supply System Skos
Comment: Indication of the traction supply system
Message: energySupplySystem (1.1.1.2.2.1.2): The contact line system {$this} has a value {?concept} that is not one of the predefined values and cannot be converted into a SKOS concept on this list: http://data.europa.eu/949/concepts/energy-supply-systems/EnergySupplySystems.
- OPE TSI References
-
- Part of RCC Algorithm:
- true
-
- Appendix D2 Index
- 3.3.1
- Additional Information
-
- General explanation:
- If the real values exceed range of the EN 50163:2004+A1:2007+A2:2020+A3:2022, they could be introduced by the Agency on request via a process of change request.
See: ENE TSI: 4.2.3 and EN 50163:2004: clause 4
For RINF XML data sets:
As long as the data provision through XML data sets is allowed, an XML attribute called “Set” will be used to link the value of this parameter to the parameter 1.1.1.2.2.1.1 / ECS_SystemType
Umax2 for the French network
DP
IRI: http://data.europa.eu/949/umax2
- Parameter of
-
Contact Line System
- General Information
-
- Number:
- 1.1.1.2.2.1.3
- XML Name:
- ECS_Umax2
- Deadline:
- 16 January 2020
- Belongs to parameters group
-
Contact line system
(
1.1.1.2.2
)
- Data Format
-
- Data Presentation
-
Integer
- Unit of Measure:
-
Volt
- Flags
-
- Applicability Flags:
- Y/N
- Validation
-
- Dependencies:
- When `not electrified` is chosen in parameter 1.1.1.2.2.1.1, then this parameter is not applicable.
- Validation Rules:
-
Umax2
Comment: Umax2 for lines referred to in sections 7.4.2.2.1 and 7.4.2.11.1 of Regulation (EU) 1301/2014
Message: umax2 (1.1.1.2.2.1.3): The contact line system defines the Umax2 . This error is due to having more than one value for this property, having a value that is not an integer, or having an integer that does not follow the pattern [NNNNNN].
- OPE TSI References
-
- Part of RCC Algorithm:
- true
- Additional Information
-
- General explanation:
- Specific for the French network. It may concern DC 1.5kV and AC 25kV.
For RINF XML data sets:
As long as the data provision through XML data sets is allowed, an XML attribute called “Set” will be used to link the value of this parameter to the parameter 1.1.1.2.2.1.1 / ECS_SystemType
Maximum train current
DP
IRI: http://data.europa.eu/949/maxTrainCurrent
- Parameter of
-
Contact Line System
- General Information
-
- Number:
- 1.1.1.2.2.2
- XML Name:
- ECS_MaxTrainCurrent
- Deadline:
- In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
- Belongs to parameters group
-
Contact line system
(
1.1.1.2.2
)
- Data Format
-
- Data Presentation
-
Integer
- Unit of Measure:
-
Ampere
- Flags
-
- Applicability Flags:
- Y/N
- Validation
-
- Dependencies:
- When `not electrified` is chosen in parameter 1.1.1.2.2.1.1, then this parameter is not applicable.
- Validation Rules:
-
Maximum Train Current
Comment: Indication of the maximum allowable train current
Message: maxTrainCurrent (1.1.1.2.2.2): The contact line system defines the maximum allowable train current . This error is due to having more than one value for this property, having a value that is not an integer, or having an integer that does not follow the pattern [NNNN].
- OPE TSI References
-
- Appendix D2 Index
- 3.3.2
- Additional Information
-
- General explanation:
- For RINF XML data sets:
As long as the data provision through XML data sets is allowed, an XML attribute called “Set” will be used to link the value of this parameter to the parameter 1.1.1.2.2.1.1 / ECS_SystemType
Maximum current at standstill per pantograph
DP
IRI: http://data.europa.eu/949/maxCurrentStandstillPantograph
- Parameter of
-
Contact Line System
-
Siding
-
Vehicle Type
- General Information
-
- Number:
- 1.1.1.2.2.3
- 1.2.2.0.6.1
- XML Name:
- ECS_MaxStandstillCurrent
- Deadline:
- In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest for DC systems
30 June 2024 for AC systems
- Belongs to parameters group
-
Contact line system
(
1.1.1.2.2
)
-
Vehicle type technical characteristic
- Data Format
-
- Data Presentation
-
Integer
- Format:
- NNN
- Unit of Measure:
-
Ampere
- Flags
-
- Applicability Flags:
- Y/N
- Validation
-
- Dependencies:
- This parameter is applicable only the type of contact line system is 'Overhead contact line (OCL)'
In sidings, it may be not applicable, in the following cases:
- siding is not electrified
- Siding is destined to freight traffic, whose trains have a low consumption in stationary (the maximum demand of energy is due to air conditioning systems, which is not significant in these trains).
- Siding is used in access to depots or workshops.
- Validation Rules:
-
Max Current Standstill Pantograph Applicability
Comment: This parameter is applicable (“Y”) only if “Overhead contact line (OCL)” is selected for parameter 1.1.1.2.2.1.1.
Message: maxCurrentStandstillPantograph (1.1.1.2.2.3, 1.2.2.0.6.1):The Contact Line System {$this} ({?clsLabel}), has a 'Overhead contact line (OCL)' type which makes the maxCurrentStandstillPantograph parameter applicable. This error is due to {$this} not having a value for such a parameter.
-
Max Current Standstill Pantograph
Comment: Indication of the maximum allowable current at standstill per pantograph
Message: maxCurrentStandstillPantograph (1.1.1.2.2.3, 1.2.2.0.6.1): The contact line system defines the maximum allowable current at standstill per pantograph . This error is due to having more than one value for this property, having a value that is not a double (real) number, or having a number that does not follow the pattern [NNN] (with 0 decimals).
-
Max Current Standstill Pantograph S
Comment: Indication of the maximum allowable train current at standstill for DC systems expressed in amperes
Message: maxCurrentStandstillPantograph (1.1.1.2.2.3, 1.2.2.0.6.1): Each siding may define the maximum allowable train current at standstill for DC systems expressed in amperes. This error is due to having a max current standstill pantograph value that is not a double (real) number.
- OPE TSI References
-
- Part of RCC Algorithm:
- true
-
- Appendix D2 Index
- 3.3.8
- Additional Information
-
- General explanation:
- Parameter related to current taken by the vehicle when it is not in a traction or regenerative mode, e.g. preheating, air-condition, etc.
Due to operational reasons, trains can get stuck on SoL for hours, and in some cases, this parameter is even the reason the air-condition is shut down
Permission for regenerative braking
OP
IRI: http://data.europa.eu/949/conditionalRegenerativeBrake
- Parameter of
-
Contact Line System
- General Information
-
- Number:
- 1.1.1.2.2.4
- XML Name:
- ECS_RegenerativeBraking
- Deadline:
- In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
- Belongs to parameters group
-
Track parameters
(
1.1.1.1.4
|
1.2.1.0.4
)
-
Track resistance to applied loads
(
1.1.1.1.6
)
- Data Format
-
- Data Presentation
-
Concept
- Taxonomy Reference:
-
Regenerative Braking
-
Values :
-
| Code |
Value |
| 10 |
Allowed |
| 20 |
Allowed under conditions |
| 30 |
Allowed only for emergency brake |
| 40 |
Allowed under conditions only for emergency brake |
| 50 |
Not allowed |
- Flags
-
- Applicability Flags:
- Y/N
- Validation
-
- Dependencies:
- When `not electrified` is chosen in parameter 1.1.1.2.2.1.1, then this parameter is not applicable.
- Validation Rules:
-
Conditional Regenerative Brake Skos
Comment: Indication whether regenerative braking is permitted, not permitted, or permitted under specific conditions.
Message: conditionalRegenerativeBrake (1.1.1.2.2.4):): The track or subset with common characteristics {$this} has a value {?concept} that is not one of the predefined values and cannot be converted into a SKOS concept on this list: http://data.europa.eu/949/concepts/regenerative-braking/RegenerativeBraking.
-
Conditional Regenerative Brake
Comment: Indication whether regenerative braking is permitted, not permitted, or permitted under specific conditions.
Message: conditionalRegenerativeBrake (1.1.1.2.2.4): The track or subset with common characteristics defines if the regenerative brake is permitted. This error is due to having more than one value for this property or having a value that is not an IRI.
- OPE TSI References
-
- Part of RCC Algorithm:
- true
-
- Appendix D2 Index
- 3.3.7
- Additional Information
-
- General explanation:
- When regenerative braking is "allowed under conditions", a document must be provided under 1.1.1.2.2.4.1.
For RINF XML data sets:
As long as the data provision through XML data sets is allowed, an XML attribute called “Set” will be used to link the value of this parameter to the parameter 1.1.1.2.2.1.1 / ECS_SystemType
Conditions applying in regards to regenerative braking
OP
IRI: http://data.europa.eu/949/conditionsAppliedRegenerativeBraking
- Parameter of
-
Contact Line System
- General Information
-
- Number:
- 1.1.1.2.2.4.1
- XML Name:
- ECS_RegBrakingConditions
- Deadline:
- 12 months after publication of Article 7 Guide
- Belongs to parameters group
-
Contact line system
(
1.1.1.2.2
)
- Data Format
-
- Data Presentation
-
ERA Document
- Flags
-
- Applicability Flags:
- Y/N/NYA
- Validation
-
- Dependencies:
- When `not electrified` is chosen in parameter 1.1.1.2.2.1.1, then this parameter is not applicable. Mandatory when parameter 1.1.1.2.2.4 announces Conditions.
- Validation Rules:
-
Conditions Applied Regenerative Braking
Comment: Name and/or reference of the document specifying the conditions applying in regards to regenerative braking.
Message: conditionsAppliedRegenerativeBraking (1.1.1.2.2.4.1): The contact line system has a conditionsAppliedRegenerativeBraking reference that must be a Document. This error is due to having more than one value for this property or having a value that is not a Document.
-
Conditions Applied Regenerative Braking Applicability
Comment: This parameter is applicable (“Y”) only if “Overhead contact line (OCL)” is selected for parameter 1.1.1.2.2.1.1.
Message: conditionsAppliedRegenerativeBraking (1.1.1.2.2.4.1):The Contact Line System {$this} ({?clsLabel}), has a 'Overhead contact line (OCL)' type which makes the conditionsAppliedRegenerativeBraking parameter applicable. This error is due to {$this} not having a value for such a parameter.
- OPE TSI References
-
- Appendix D2 Index
- 3.3.7
- Additional Information
-
- General explanation:
- The value of this parameter should be either a reference to a file name or an external link to a document.
If a file name is provided, the Infrastructure Manager (IM) must upload a document with the same file name using the "Reference Documents Management" functionality in the RINF application. The document must be in electronic format and available in two official EU languages. In this case, the parameter value must be repeated for each document.
If an external link is provided, the IM must ensure that the document is available at the provided link.
Accepted TSI compliant pantograph heads
OP
IRI: http://data.europa.eu/949/tsiPantographHead
- Parameter of
-
Running track
-
Subset with common characteristics
- General Information
-
- Number:
- 1.1.1.2.3.1
- XML Name:
- EPA_TSIHeads
- Deadline:
- In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
- Belongs to parameters group
-
Pantograph
(
1.1.1.2.3
)
- Data Format
-
- Data Presentation
-
Concept
- Taxonomy Reference:
-
CompliantPantograph Heads
-
Values :
-
| Code |
Value |
| 10 |
1950 mm (Type 1) |
| 20 |
1600 mm (EP) |
| 30 |
2000 mm – 2260 mm |
| 40 |
None |
| 50 |
1950 mm (Type 1) with insulated horns |
- Flags
-
- Applicability Flags:
- Y/N
- Validation
-
- Dependencies:
- Mandatory only if “Overhead contact line (OCL)” is selected in 1.1.1.2.2.1.1, otherwise the parameter is not applicable.
- Validation Rules:
-
Tsi Pantograph Head Skos
Comment: Accepted TSI compliant pantograph heads.
Message: Indication of the tsiPantographHead (1.1.1.2.3.1):): The track or subset with common characteristics {$this} has a value {?concept} that is not one of the predefined values and cannot be converted into a SKOS concept on this list: http://data.europa.eu/949/concepts/compliant-pantograph-heads/CompliantPantographHeads.
-
Tsi Pantograph Head Applicability
Comment: Indication of TSI compliant pantograph heads which are allowed to be used.
Message: tsiPantographHead (1.1.1.2.3.1): This error is due to the track or subset with common characteristics {?trackLabel} , violating the rule: This parameter is applicable ('Y') only if “Overhead contact line (OCL)” is selected for 1.1.1.2.2.1.1.
- OPE TSI References
-
- Part of RCC Algorithm:
- true
- Additional Information
-
- General explanation:
- The parameter can contain more than one pantograph defined in LOC&PAS TSI. Presentation of those pantographs is done by repetition of the parameter with a single selection.
If declaring acceptance of pantograph heads 1950 (type 1), both insulated and conductive horns shall be accepted.
The head geometry of pantograph type 1600 mm is as depicted in the points 4.2.8.2.9.2.1 of LOC&PAS TSI which refers to EN 50367:2020+A1:2022 Annex A.2 Figure A.6.
The head geometry of pantograph type 1950 mm is as depicted in the points 4.2.8.2.9.2.2 of LOC&PAS TSI which refers to EN 50367:2020+A1:2022 Annex A.2 Figure A.7.
The head geometry for pantograph type 2000/2260 mm is depicted in the point 4.2.8.2.9.2.3 of LOC&PAS TSI.
Accepted other pantograph heads
OP
IRI: http://data.europa.eu/949/otherPantographHead
- Parameter of
-
Running track
-
Subset with common characteristics
- General Information
-
- Number:
- 1.1.1.2.3.2
- XML Name:
- EPA_OtherHeads
- Deadline:
- In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
- Belongs to parameters group
-
Pantograph
(
1.1.1.2.3
)
- Data Format
-
- Data Presentation
-
Concept
- Taxonomy Reference:
-
Other Pantograph Heads
-
Values :
-
| Code |
Value |
| 10 |
1950 mm (Type2) |
| 20 |
1800 mm (NO,SE) |
| 30 |
1800 mm (NO,SE) |
| 40 |
1760 mm (BE) |
| 70 |
1450 mm |
| 80 |
Other |
| 90 |
None |
| 100 |
1700 mm (ES) |
| 110 |
1700 mm with insulated horns (ES) |
- Flags
-
- Applicability Flags:
- Y/N
- Validation
-
- Dependencies:
- Mandatory only if “Overhead contact line (OCL)” is selected in 1.1.1.2.2.1.1, otherwise the parameter is not applicable.
- Validation Rules:
-
Other Pantograph Head Applicability
Comment: Indication of pantograph heads which are allowed to be used.
Message: otherPantographHead (1.1.1.2.3.2): This error is due to the track or subset with common characteristics {?trackLabel} , violating the rule: This parameter is applicable ('Y') only if “Overhead contact line (OCL)” is selected for 1.1.1.2.2.1.1.
-
Other Pantograph Head Skos
Comment: Indication of which other pantograph heads are allowed to be used.
Message: Indication of the otherPantographHead (1.1.1.2.3.2):): The track or subset with common characteristics {$this} has a value {?concept} that is not one of the predefined values and cannot be converted into a SKOS concept on this list: http://data.europa.eu/949/concepts/other-pantograph-heads/OtherPantographHeads.
- OPE TSI References
-
- Part of RCC Algorithm:
- true
- Additional Information
-
- General explanation:
- The parameter may contain more than one type of the pantograph head - all of them shall be indicated by repetition of the parameter with different single selections.
Additional values than the already identified in the list above are possible. They will be introduced by the Agency on request via a process of change request.
Requirements for number of raised pantographs and spacing between them, at the given speed
OP
IRI: http://data.europa.eu/949/trackRaisedPantographsDistanceAndSpeed
- Parameter of
-
Running track
-
Subset with common characteristics
- General Information
-
- Number:
- 1.1.1.2.3.3
- XML Name:
- EPA_NumRaisedSpeed
- Deadline:
- In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
- Belongs to parameters group
-
Pantograph
(
1.1.1.2.3
)
- Data Format
-
- Data Presentation
-
Requirements for number of raised pantographs and spacing between them, at the given speed
- Format:
- Three values: [N] is number of pantographs; [NNN] is minimum distance between pantographs, in metres; [NNN] is the speed considered in km/h.
- Flags
-
- Applicability Flags:
- Y/N
- Validation
-
- Dependencies:
- Mandatory only if “Overhead contact line (OCL)” is selected in 1.1.1.2.2.1.1, otherwise the parameter is not applicable.
- Validation Rules:
-
Track Raised Pantographs Distance And Speed
Comment: Relates the track with the class RaisedPantporaphsDistanceAndSpeed. Indication of maximum number of raised pantographs per train allowed and minimum spacing centre line to centre line of adjacent pantograph heads, expressed in metres, at the given speed.
Message: trackRaisedPantographsDistanceAndSpeed (1.1.1.2.3.3): The track defines a raised pantographs distance and speed value that must be an instance of RaisedPantographsDistanceAndSpeed.
-
Track Raised Pantograph Distance And Speed Applicability
Comment: Relates the track with the class RaisedPantographsDistanceAndSpeed. Indication of maximum number of raised pantographs per train allowed and minimum spacing centre line to centre line of adjacent pantograph heads, expressed in metres, at the given speed.
Message: trackRaisedPantographsDistanceAndSpeed (1.1.1.2.3.3): This error is due to the track or subset with common characteristics {?trackLabel} , violating the rule: This parameter is applicable ('Y') only if “Overhead contact line (OCL)” is selected for 1.1.1.2.2.1.1.
- OPE TSI References
-
- Part of RCC Algorithm:
- true
- Additional Information
-
- General explanation:
- This parameter gives the information about the number of pantographs and the distance between them at a given speed for which the Overhead Contact Line (OCL) has been designed.
As for different speeds different combinations of number of pantographs and distance between them may exist, so this parameter can be repeated to present all of them.
The raised pantographs distance and speed is the indication of maximum number of raised pantographs per train allowed and minimum spacing centre line to centre line of adjacent pantograph heads, expressed in metres, at the given speed.
See 4.2.13 (TSI ENE) and 4.2.8.2.9.7 (TSI LOC&PAS)
Contact strip material metallic content
DP
IRI: http://data.europa.eu/949/contactStripMaterialMetallicContent
- Parameter of
-
Running track
-
Subset with common characteristics
- General Information
-
- Number:
- 1.1.1.2.3.4
- XML Name:
- EPA_StripMaterial
- Belongs to parameters group
-
Pantograph
(
1.1.1.2.3
)
- Data Format
-
- Data Presentation
-
Integer
- Validation
-
- Dependencies:
- Mandatory only if impregnated carbon ([NN] % of metallic content)” is selected in 1.1.1.2.3.4, otherwise no value should be provided
- Validation Rules:
-
Contact Strip Material Metallic Content
Comment: In case that the value of the property era:contactStripMaterial is impregnated carbon, it is the metallic content, the maximum percentage allowed.
Message: contactStripMaterialMetallicContent (1.1.1.2.3.4): The track or subset with common characteristics has an indication of the material of the contact strip that must be an integer. This error may be due to the track having a value that is not an integer.
- OPE TSI References
-
- Part of RCC Algorithm:
- true
- Additional Information
-
- General explanation:
- In case that the value of the property era:contactStripMaterial is "impregnated carbon", it is the metallic content in % (this value must be added). This is the maximum percentage allowed.
Phase separation
DP
IRI: http://data.europa.eu/949/hasPhaseSeparation
- Parameter of
-
Running track
-
Subset with common characteristics
- General Information
-
- Number:
- 1.1.1.2.4.1.1
- XML Name:
- EOS_Phase
- Deadline:
- In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
- Belongs to parameters group
-
OCL separation sections
(
1.1.1.2.4
)
- Data Format
-
- Data Presentation
-
Boolean
- Format:
- in XML: Y/N
- Flags
-
- Applicability Flags:
- Y/N
- Validation
-
- Dependencies:
- A value is mandatory only if 1.1.1.2.2.1.1 parameter values is Overhead contact line (OCL) , otherwise applicability flag is "N" (not applicable)
- Validation Rules:
-
Has Phase Separation Applicability
Comment: Indication of existence of phase separation and required information.
Message: hasPhaseSeparation (1.1.1.2.4.1.1): This error is due to the track or subset with common characteristics {?trackLabel} , violating the rule: This parameter is applicable ('Y') only if “Overhead contact line (OCL)” is selected for 1.1.1.2.2.1.1.
-
Has Phase Separation
Comment: Indication of existence of phase separation and required information.
Message: hasPhaseSeparation (1.1.1.2.4.1.1): The track or subset with common characteristics defines at most one existence of phase separation and required information value that is Y/N (boolean). This error may be due to the track having more than one value or having a value that is not Y/N (boolean).
- Additional Information
-
- General explanation:
- In case of existence of phase separation on the track or on the section of the line the option True shall be selected.
Information on phase separation
OP
IRI: http://data.europa.eu/949/trackPhaseInfo
- Parameter of
-
Running track
-
Subset with common characteristics
- General Information
-
- Number:
- 1.1.1.2.4.1.2
- XML Name:
- EOS_InfoPhase
- Deadline:
- In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
- Belongs to parameters group
-
OCL separation sections
(
1.1.1.2.4
)
- Data Format
-
- Data Presentation
-
Phase info
- Format:
- In RDF the range is an instance of the era:PhaseInfo class with all its properties.
For RINF XML data sets:
As long as the data provision through XML data sets is allowed, the data format is a character sting with the following structure: distance type [MIN/MAX] + length [NNN] + switch off breaker [Y/N] + lower pantograph [Y/N] + change supply system [Y/N] + km [NNN.NNN]. The structure of the string is as follows:
- distance type [MIN/MAX] - single selection of 'MIN=minimum' or 'MAX=maximum' to show whether the length is a minimum distance between the inner contact strips of the pantographs or a maximum distance between the outer contact strips of the pantographs. Multiple strings for this parameter are accepted;
- length [NNN] - the length of the phase separation in metres;
- switch off breaker [Y/N], single selection of 'yes' or 'no' to show whether the breaker has to be switched off;
- lower pantograph [Y/N], single selection of 'yes' or 'no' to show whether the pantograph has to be lowered,
- Km [NNN.NNN] - the location from the start of the line where the new value is valid.
- Flags
-
- Applicability Flags:
- Y/N
- Validation
-
- Dependencies:
- A value is mandatory only if 1.1.1.2.4.1.1 parameter "Phase separation" value is "Y" (true), otherwise applicability flag is "N" (not applicable)
- Validation Rules:
-
Track Phase Info
Comment: Relates the Track with PhaseInfo. Indication of required several information on phase separation.
Message: trackPhaseInfo (1.1.1.2.4.1.2): The track defines a track phase info value that must be an instance of PhaseInfo.
-
Track Phase Info Applicability
Comment: Relates the Track with PhaseInfo. Indication of required several information on phase separation.
Message: trackPhaseInfo (1.1.1.2.4.1.2): This error is due to the track or subset with common characteristics {?trackLabel} , violating the rule: Applicable when in parameter 1.1.1.2.4.1.1 selected option is ‘Y’
System separation
DP
IRI: http://data.europa.eu/949/hasSystemSeparation
- Parameter of
-
Running track
-
Subset with common characteristics
- General Information
-
- Number:
- 1.1.1.2.4.2.1
- XML Name:
- EOS_System
- Deadline:
- In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
- Belongs to parameters group
-
OCL separation sections
(
1.1.1.2.4
)
- Data Format
-
- Data Presentation
-
Boolean
- Format:
- Y/N
- Flags
-
- Applicability Flags:
- Y/N
- Validation
-
- Dependencies:
- It is applicable ( Y ) only if the value Overhead contact line (OCL) is selected for parameter "Type of contact line system"
- Validation Rules:
-
Has System Separation
Comment: Indication of existence of system separation.
Message: hasSystemSeparation (1.1.1.2.4.2.1): The track or subset with common characteristics has at most one existence of system separation value that must be Y/N (boolean). This error may be due to the track having more than one value or to having a value that is not Y/N (boolean).
-
Has System Separation Applicability
Comment: Indication of existence of system separation.
Message: hasSystemSeparation (1.1.1.2.4.2.1): This error is due to the track or subset with common characteristics {?trackLabel} , violating the rule: This parameter is applicable ('Y') only if “Overhead contact line (OCL)” is selected for 1.1.1.2.2.1.1.
- Additional Information
-
- General explanation:
- In case of existence of system separation on the track or on the section of the line and required information on the section of the line, the option Y=yes shall be selected.
Information on system separation
OP
IRI: http://data.europa.eu/949/trackSystemSeparationInfo
- Parameter of
-
Running track
-
Subset with common characteristics
- General Information
-
- Number:
- 1.1.1.2.4.2.2
- XML Name:
- EOS_InfoSystem
- Deadline:
- In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
- Belongs to parameters group
-
OCL separation sections
(
1.1.1.2.4
)
- Data Format
-
- Data Presentation
-
System separation info
- Format:
- In RDF, the range is an instance of the era:SystemSeparationInfo class with all its properties.
For RINF XML data sets:
As long as the data provision through XML data sets is allowed, the data format is a character sting with the following structure: length [NNN] + switch off breaker [Y/N] + lower pantograph [Y/N] + km [NNN.NNN]
- Flags
-
- Applicability Flags:
- Y/N
- Validation
-
- Dependencies:
- Mandatory if there is an indication of existence of system separation (parameter 1.1.1.2.4.2.1)
- Validation Rules:
-
Track System Separation Info
Comment: Relates the Track with the SystemSeparationInfo. Indication of required several information on system separation.
Message: trackSystemSeparationInfo (1.1.1.2.4.2.2): The track defines a system separation info value that must be an instance of SystemSeparationInfo.
-
Track System Separation Info Applicability
Comment: Relates the Track with the SystemSeparationInfo. Indication of required several information on system separation.
Message: trackSystemSeparationInfo (1.1.1.2.4.2.2): This error is due to the track or subset with common characteristics {?trackLabel} , violating the rule: Applicable when in parameter 1.1.1.2.4.2.1 selected option is ‘Y’
- Additional Information
-
- General explanation:
- Length - the length of the system separation in metres
Switch off breaker - single selection of Y=yes or N=no to show whether the breaker has to be switched off
Lower pantograph - single selection of Y=yes or N=no to show whether the pantograph has to be lowered
Change supply system - single selection of Y=yes or N=no to show whether the supply system has to be changed
Km - the location from the start of the line where the new value is valid
Distance between signboard and phase separation ending
DP
IRI: http://data.europa.eu/949/distSignToPhaseEnd
- Parameter of
-
Running track
-
Subset with common characteristics
- General Information
-
- Number:
- 1.1.1.2.4.3
- XML Name:
- EOS_DistSignToPhaseEnd
- Deadline:
- 16 January 2020
- Belongs to parameters group
-
OCL separation sections
(
1.1.1.2.4
)
- Data Format
-
- Data Presentation
-
Integer
- Format:
- NNN
- Unit of Measure:
-
Metre
- Flags
-
- Applicability Flags:
- Y/N
- Validation
-
- Dependencies:
- It is applicable ( Y ) only if the value Overhead contact line (OCL) is selected for parameter "Type of contact line system"
- Validation Rules:
-
Dist Sign To Phase End
Comment: Specific for route compatibility check on French network. Distance between the signboard authorizing the driver to 'raise pantograph' or 'close the circuit breaker' after passing the phase separation and the end of the phase separation section.
Message: distSignToPhaseEnd: The track or subset with common characteristics must have at most one value of the distance between the signboard authorizing the driver to 'raise pantograph' or 'close the circuit breaker' after passing the phase separation and the end of the phase separation section, and the value is an integer. This error is due to the track having more than one value or to having a value that is not an integer.
- OPE TSI References
-
- Part of RCC Algorithm:
- true
- Additional Information
-
- General explanation:
- Specific for route compatibility check on French network.
Current or power limitation on board required
DP
IRI: http://data.europa.eu/949/currentLimitationRequired
- Parameter of
-
Contact Line System
- General Information
-
- Number:
- 1.1.1.2.5.1
- XML Name:
- ERS_PowerLimitOnBoard
- Deadline:
- In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
- Belongs to parameters group
-
Requirements for rolling stock
(
1.1.1.2.5
)
- Data Format
-
- Data Presentation
-
Boolean
- Format:
- Y/N
- Flags
-
- Applicability Flags:
- Y/N
- Validation
-
- Dependencies:
- When "not electrified" is chosen in parameter "Type of contact line system", then this parameter is not applicable.
- Validation Rules:
-
Current Limitation Required
Comment: Indication of whether an on board current or power limitation function on vehicles is required.
Message: currentLimitationRequired (1.1.1.2.5.1): The track or subset with common characteristics may have a current limitation required value that is a boolean. This error may be due to the track having a value that is not a boolean.
-
Current Limitation Required Applicability
Comment: Indication of whether an on board current or power limitation function on vehicles is required.
Message: currentLimitationRequired (1.1.1.2.5.1): This error is due to the track or subset with common characteristics {?trackLabel} , violating the rule: When 'not electrified' is chosen in parameter 1.1.1.2.2.1.1, then this parameter is not applicable selection ‘N’.
- OPE TSI References
-
- Part of RCC Algorithm:
- true
Automatic dropping device required
DP
IRI: http://data.europa.eu/949/automaticDroppingDeviceRequired
- Parameter of
-
Running track
-
Subset with common characteristics
- General Information
-
- Number:
- 1.1.1.2.5.3
- XML Name:
- ERS_AutoDropRequired
- Deadline:
- In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
- Belongs to parameters group
-
Requirements for rolling stock
(
1.1.1.2.5
)
- Data Format
-
- Data Presentation
-
Boolean
- Format:
- Y/N
- Flags
-
- Applicability Flags:
- Y/N
- Validation
-
- Dependencies:
- A value is mandatory if the value Overhead contact line (OCL) is selected for parameter "Type of contact line system"
- Validation Rules:
-
Automatic Dropping Device Required
Comment: Indication of the requirement of automatic dropping device.
Message: automaticDroppingDeviceRequired (1.1.1.2.5.3): The track or subset with common characteristics must have at most one value of the requirement of automatic dropping device and it is Y/N (boolean). This error is due to the track having more than one value or to having a value that is not Y/N (boolean).
-
Automatic Dropping Device Required Applicability
Comment: Indication of whether an automatic dropping device (ADD) required on the vehicle.
Message: automaticDroppingDeviceRequired (1.1.1.2.5.3): This error is due to the track or subset with common characteristics {?trackLabel} , violating the rule: This parameter is applicable ('Y') only if “Overhead contact line (OCL)” is selected for 1.1.1.2.2.1.1.
- OPE TSI References
-
- Part of RCC Algorithm:
- true
Document with restriction related to power consumption of specific electric traction unit(s)
OP
IRI: http://data.europa.eu/949/documentRestrictionPowerConsumption
- Parameter of
-
Running track
-
Subset with common characteristics
- General Information
-
- Number:
- 1.1.1.2.5.4
- XML Name:
- ERS_PowerConsumptionDocument
- Deadline:
- 12 months after publication of Article 7 Guide
- Belongs to parameters group
-
Requirements for rolling stock
(
1.1.1.2.5
)
- Data Format
-
- Data Presentation
-
ERA Document
- Flags
-
- Applicability Flags:
- Y/N/NYA
- Validation
-
- Validation Rules:
-
Document Restriction Power Consumption
Comment: Document with restriction related to power consumption of specific electric traction unit(s).
Message: documentRestrictionPowerConsumption (1.1.1.2.5.4): The track or subset with common characteristics may have a Document with restriction related to power consumption of specific electric traction unit(s) value that is a Document. This error may be due to the track having a value that is not a Document.
- Additional Information
-
- General explanation:
- The value of this parameter should be either a reference to a file name or an external link to a document.
If a file name is provided, the Infrastructure Manager (IM) must upload a document with the same file name using the "Reference Documents Management" functionality in the RINF application. The document must be in electronic format and available in two official EU languages. In this case, the parameter value must be repeated for each document.
If an external link is provided, the IM must ensure that the document is available at the provided link.
EC declaration of verification for track relating to compliance with the requirements from TSIs applicable to control, command signalling subsystem
DP
IRI: http://data.europa.eu/949/verificationCCS
- Parameter of
-
Running track
-
Subset with common characteristics
- General Information
-
- Number:
- 1.1.1.3.1.1
- XML Name:
- CDE_ECVerification
- Deadline:
- In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
- Belongs to parameters group
-
Declarations of verification for track
(
1.1.1.3.1
)
- Data Format
-
- Data Presentation
-
String
- Format:
- CC/RRRRRRRRRRRRRR/YYYY/NNNNNN
- Flags
-
- Applicability Flags:
- Y/N
- Validation
-
- Validation Rules:
-
Verification Ccs
Comment: Unique number for EC declarations following format requirements specified in the 'Document about practical arrangements for transmitting interoperability documents'.
Message: verificationCCS (1.1.1.3.1.1): The track or subset with common characteristics defines the unique number for EC declarations following format requirements specified in the 'Document about practical arrangements for transmitting interoperability documents; the value must be a string that follows the pattern [CC/RRRRRRRRRRRRRR/YYYY/NNNNNN] where the YYYY characters must be a number between 1900 and 2100, and the NNNNNN characters must be digits. This error is due to having a value that does not follow the pattern.
- Additional Information
-
- General explanation:
- (CCS) in title means that here we include only declarations concerning command control and signalling subsystem on the specific track. For the specific track the several EC declarations may be issued, so parameter has to repeated as many times as many numbers of declarations has to be presented.
Error corrections required for the on-board ETCS, GSM-R and/or ATO function
OP
IRI: http://data.europa.eu/949/errorCorrectionsOnboard
- Parameter of
-
Running track
-
Subset with common characteristics
- General Information
-
- Number:
- 1.1.1.3.1.2
- 1.2.1.1.1.19
- XML Name:
- CDE_ReqErrorCorrections
- Deadline:
- 12 months after the entry into force of TSI CCS and at least 12 months after publication of Article 7 Guide
- Belongs to parameters group
-
Declarations of verification for track
(
1.1.1.3.1
)
- Data Format
-
- Data Presentation
-
Concept
- Taxonomy Reference:
-
Onboard Error Corrections
-
Values :
-
- Flags
-
- Applicability Flags:
- Y/N
- Validation
-
- Dependencies:
- A value has to be provided when ETCS is present (a value is provided on 1.1.1.3.2.1).
- Validation Rules:
-
Error Corrections Onboard
Comment: List of unacceptable errors impacting the IM network that are required to be solved in the on-board according to the TSI CCS point 7.2.10.3 specification maintenance point (ETCS, GSM-R and/or ATO).
Message: errorCorrectionsOnboard (1.1.1.3.1.2, 1.2.1.1.1.19): The track or subset with common characteristics may have an error correction required for the on-board ETCS, GSM-R and/or ATO function value that is an IRI. This error is due to having more than one value or having a value that is not an IRI.
-
Error Corrections Onboard Skos
Comment: List of unacceptable errors impacting the IM network that are required to be solved in the on-board according to the TSI CCS point 7.2.10.3 specification maintenance point (ETCS, GSM-R and/or ATO).
Message: errorCorrectionsOnboard (1.1.1.3.1.2, 1.2.1.1.1.19): The track or subset with common characteristics {$this} (label {?label}) has a value {?concept} that is not one of the predefined values and cannot be converted into a SKOS concept on this list: http://data.europa.eu/949/concepts/error-corrections/OnboardErrorCorrections.
-
Error Corrections Onboard Explanation
Comment: Explanation on why a mandatory onboard CR required to be solved in the on-board (ETCS, GSM-R and/or ATO) was accepted by the IM.
Message: errorCorrectionsOnboardExplanation (1.1.1.3.1.2, 1.2.1.1.1.19): The errorCorrectionsOnboardExplanation must be a string. This error is due to having more than one value or having a value that is not a string.
- Additional Information
-
- General explanation:
- This parameter should be limited to those required for the onboard, in order to allow normal service as defined in Art. 10 CR. The values will come from a list.
IM's may choose to make available the optional ETCS error corrections as well, but this should be done using other means than the RINF register.
This parameter should also be understood as ETCS, ATO and GSM-R related error corrections required for the on-board. pending a formal update and approval of the relevant legislative annex.
For the specific track the error corrections to be applied is one list only.
Reasons for Error corrections required, but accepted by the IM for the on-board ETCS, GSM-R and/or ATO function
DP
IRI: http://data.europa.eu/949/errorCorrectionsOnboardExplanation
- Parameter of
-
Running track
-
Subset with common characteristics
- General Information
-
- Number:
- 1.1.1.3.1.2
- 1.2.1.1.1.19
- XML Name:
- CDE_ReqErrorCorrections
- Deadline:
- 12 months after the entry into force of TSI CCS and at least 12 months after publication of Article 7 Guide
- Belongs to parameters group
-
Declarations of verification for track
(
1.1.1.3.1
)
- Data Format
-
- Data Presentation
-
String
- Flags
-
- Applicability Flags:
- Y/N/NYA
- Validation
-
- Dependencies:
- A value has to be provided when ETCS is present (a value is provided on 1.1.1.3.2.1).
- Validation Rules:
-
Error Corrections Onboard Explanation
Comment: Explanation on why a mandatory onboard CR required to be solved in the on-board (ETCS, GSM-R and/or ATO) was accepted by the IM.
Message: errorCorrectionsOnboardExplanation (1.1.1.3.1.2, 1.2.1.1.1.19): The errorCorrectionsOnboardExplanation must be a string. This error is due to having more than one value or having a value that is not a string.
European Train Control System (ETCS) level
OP
IRI: http://data.europa.eu/949/etcsLevelType
- Parameter of
-
ETCS
- General Information
-
- Number:
- 1.1.1.3.2.1
- 1.2.1.1.1.1
- XML Name:
- CPE_Level
- Deadline:
- In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
- Belongs to parameters group
-
TSI compliant train protection system (ETCS)
(
1.1.1.3.2
|
1.2.1.1.1
)
- Data Format
-
- Data Presentation
-
Concept
- Taxonomy Reference:
-
ETCS Levels
-
Values :
-
- Flags
-
- Applicability Flags:
- Y/N
- Validation
-
- Validation Rules:
-
Etcs Level Type
Comment: Indicates the type associated as a SKOS concept from the era:ETCSLevel related to the track side equipment.
Message: etcsLevelType (1.1.1.3.2.1, 1.2.1.1.1.1): The ETCS has at most one etcsLevelType value and it must be an IRI. This error is due to the ETCS having more than one value or having a value that is not an IRI.
-
Etcs Level Type Skos
Comment: Indicates the type associated as a SKOS concept from the era:ETCSLevel related to the track side equipment.
Message: Indication of the etcsLevelType (1.1.1.3.2.1, 1.2.1.1.1.1): The ETCS {$this} has a value {?concept} that is not one of the predefined values and cannot be converted into a SKOS concept on this list: http://data.europa.eu/949/concepts/etcs-levels/.
- OPE TSI References
-
- Appendix D2 Index
- 3.2.7
- Additional Information
-
- General explanation:
- The different ERTMS / ETCS application levels are a way to express the possible operating relationships between track and train.
Level definitions are principally related to the track side equipment used, to the way the track side information reaches the on-board units and to which functions are processed in the track side and in the on-board equipment respectively.
If ETCS is on the trackside (one or more levels are selected), all other ETCS parameters (from 1.1.1.3.2.2 to 1.1.1.3.2.10) are applicable and mandatory to be populated with values .
If the line is only equipped with Class B, this should be reflected in Parameter 1.1.1.3.5.3, and this parameter is “N”(not applicable).
The ETCS value NTC is only relevant when the line is dual equipped with ETCS (i.e., balises are placed in the track) and Class B system, and both systems are in operation at the same time.
In those cases, this parameter should be filled relevant ETCS Level and repeated with the value NTC.
If the line is only equipped with Class B, this should be reflected in Parameter 1.1.1.3.5.3, and this parameter etcsLevelType should not be used.
See: TSI CCS (Subset-026, Chapter 2, 2.6)
ETCS baseline
OP
IRI: http://data.europa.eu/949/etcsBaseline
- Parameter of
-
ETCS
-
Vehicle Type
- General Information
-
- Number:
- 1.1.1.3.2.2
- 1.2.1.1.1.2
- XML Name:
- CPE_Baseline
- Deadline:
- 12 months after publication of Article 7 Guide for OP tracks
- In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
- Belongs to parameters group
-
TSI compliant train protection system (ETCS)
(
1.1.1.3.2
|
1.2.1.1.1
)
-
Vehicle type technical characteristic
- Data Format
-
- Data Presentation
-
Concept
- Taxonomy Reference:
-
ETCS Baselines
-
Values :
-
| Code |
Value |
| 10 |
Prebaseline 2 |
| 20 |
Baseline 2 |
| 30 |
Baseline 3 |
| 40 |
Baseline 3 maintenance release 1 |
| 50 |
Baseline 3 release 2 |
| 60 |
Baseline 4 release 1 |
- Flags
-
- Applicability Flags:
- Y/N/NYA
- Validation
-
- Dependencies:
- A value has to be provided when ETCS is present (a value is provided on 1.1.1.3.2.1).
- Validation Rules:
-
Etcs Baseline
Comment: ETCS baseline installed lineside
Message: etcsBaseline (1.1.1.3.2.2, 1.2.1.1.1.2): The ETCS may have an ETCS baseline, and its value must be an IRI. This error is due to the ETCS instance having more than one value or having a value that is not an IRI.
-
Etcs Baseline Skos
Comment: ETCS baseline installed lineside
Message: etcsBaseline (1.1.1.3.2.2, 1.2.1.1.1.2): The ETCS {$this} has a value {?concept} that is not one of the predefined values and cannot be converted into a SKOS concept on this list: http://data.europa.eu/949/concepts/etcs-baselines/.
-
Etcs Baseline Applicability
Comment: Only applicable when selected value for 1.1.1.3.2.1 (ETCS present).
Message: etcsBaseline (1.1.1.3.2.2, 1.2.1.1.1.2): The ETCS {$this} ({?thisLabel}), has a ETCS level type which makes the etcsBaseline parameter applicable. This error is due to {$this} not having a value for such a parameter.
- OPE TSI References
-
- Appendix D2 Index
- 3.2.7
- Additional Information
-
- General explanation:
- The ETCS baseline needs to be provided for each available ETCS Level. See: TSI CCS (Table A2)
ETCS infill necessary for line access
DP
IRI: http://data.europa.eu/949/etcsInfillLineAccess
- Parameter of
-
Running track
-
Subset with common characteristics
- General Information
-
- Number:
- 1.1.1.3.2.3
- 1.2.1.1.1.3
- XML Name:
- CPE_Infill
- Deadline:
- 12 months after publication of Article 7 Guide for OP tracks
- In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
- Belongs to parameters group
-
TSI compliant train protection system (ETCS)
(
1.1.1.3.2
|
1.2.1.1.1
)
- Data Format
-
- Data Presentation
-
Boolean
- Flags
-
- Applicability Flags:
- Y/N/NYA
- Validation
-
- Dependencies:
- A value has to be provided when ETCS is present (a value is provided on 1.1.1.3.2.1) and the ETCS level is 1.
- Validation Rules:
-
Etcs Infill Line Access Applicability
Comment: Only applicable when selected value for 1.1.1.3.2.1 (ETCS present).
Message: etcsInfillLineAccess (1.1.1.3.2.3, 1.2.1.1.1.3):The track or subset with common characteristics {$this} ({?label}), has a 'ETCS Level Type' defined which makes the etcsInfillLineAccess parameter applicable. This error is due to {$this} not having a value for such a parameter.
-
Etcs Infill Line Access
Comment: Indication whether infill is required to access the line for safety reasons.
Message: etcsInfillLineAccess (1.1.1.3.2.3, 1.2.1.1.1.3): Each track or subset with common characteristics may define the existence of a ETCS infill necessary for line access. This error is due to having more than one indication of ETCS infill necessary for line access value or having an indication of ETCS infill necessary for line access value that is not Y/N (boolean).
- Additional Information
-
- General explanation:
- As indicated in CCS TSI section 7.2.9.1, an ETCS Level 1 trackside application may require that the on-board is equipped with the corresponding in-fill data transmission (Euroloop or radio) if the release speed is set to zero for safety reasons.
See: TSI CCS 7.2.9.1 & 4.2.3
ETCS infill installed line-side
OP
IRI: http://data.europa.eu/949/etcsInfill
- Parameter of
-
ETCS
-
Vehicle Type
- General Information
-
- Number:
- 1.1.1.3.2.4
- 1.2.1.1.1.4
- XML Name:
- CPE_InfillLineSide
- Deadline:
- 12 months after publication of Article 7 Guide for OP tracks
- In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
- Belongs to parameters group
-
TSI compliant train protection system (ETCS)
(
1.1.1.3.2
|
1.2.1.1.1
)
-
Vehicle type technical characteristic
- Data Format
-
- Data Presentation
-
Concept
- Taxonomy Reference:
-
ETCS Infills
-
Values :
-
| Code |
Value |
| 10 |
None |
| 20 |
Euroloop |
| 30 |
Radio infill |
| 40 |
Euroloop & Radio |
- Flags
-
- Applicability Flags:
- Y/N/NYA
- Validation
-
- Dependencies:
- Mandatory in case of ETCS level 1 and infill device(s) are installed. Otherwise it is not applicable.
- Validation Rules:
-
Etcs Infill Skos
Comment: Information about installed trackside equipment capable of transmitting infill information by loop or Global System for Mobile communications for Railways (GSM-R) for level 1 installations.
Message: etcsInfill (1.1.1.3.2.4, 1.2.1.1.1.4): The ETCS {$this} has a value {?concept} that is not one of the predefined values and cannot be converted into a SKOS concept on this list: http://data.europa.eu/949/concepts/etcs-infills/.
-
Etcs Infill
Comment: Information about installed trackside equipment capable of transmitting infill information by loop or Global System for Mobile communications for Railways (GSM-R) for level 1 installations.
Message: etcsInfill (1.1.1.3.2.4, 1.2.1.1.1.4): The ETCS may have an ETCS infill, and its value must be an IRI. This error is due to the ETCS instance having more than one value or having a value that is not an IRI.
-
Etcs Infill Applicability
Comment: Only applicable when selected value for 1.1.1.3.2.1 contains 1. Related to rule for etcsLevelType
Message: etcsInfill (1.1.1.3.2.4, 1.2.1.1.1.4): The ETCS {$this} ({?thisLabel}), has a ETCS level type value of 1 which makes the etcsInfill parameter applicable. This error is due to {$this} not having a value for such a parameter.
- Additional Information
-
- General explanation:
- TSI CCS (4.2.2 & 4.3.3)
Has ETCS national packet 44 application implemented
DP
IRI: http://data.europa.eu/949/hasEtcsNationalPacket44
- Parameter of
-
Subset with common characteristics
-
Track
- General Information
-
- Number:
- 1.1.1.3.2.5
- 1.2.1.1.1.5
- XML Name:
- CPE_NatApplication
- Belongs to parameters group
-
TSI compliant train protection system (ETCS)
(
1.1.1.3.2
|
1.2.1.1.1
)
- Data Format
-
- Data Presentation
-
Boolean
- Validation
-
- Dependencies:
- Only applicable when selected value for 1.1.1.3.2.1 (ETCS present).
- Validation Rules:
-
Has Etcs National Packet44
Comment: Indication whether data for national packet 44 applications is transmitted between track and train.
Message: hasEtcsNationalPacket44 (1.1.1.3.2.5, 1.2.1.1.1.5): Each track or subset with common characteristics may define the existence of an ETCS national packet 44 application. This error is due to having more than one indication of ETCS national packet 44 application value or having an indication of ETCS national packet 44 application value that is not Y/N (boolean).
-
Has Etcs National Packet44applicability
Comment: Only applicable when selected value for 1.1.1.3.2.1 (ETCS present).
Message: hasEtcsNationalPacket44 (1.1.1.3.2.5, 1.2.1.1.1.5):The track or subset with common characteristics {$this} ({?label}), has an 'ETCS Level Type' defined that makes the hasEtcsNationalPacket44 parameter applicable. This error is due to {$this} not having a value for such a parameter.
- Additional Information
-
- General explanation:
- Value can be `false` or a link to the implemented functions. The hasEtcsNationalPacket44 property represents the true or false value. The etcsNationalPacket44Function represents the functions.
Packets 44 are the means to transmit data for national applications between train and track and vice versa, using the data transmission facilities included within the ETCS.
NID_XUSER values managed by ERA in a document about ETCS variables available on ERA website.
See: TSI CCS (7.4.3 & 6.2.4.2).
Existence of operating restrictions or conditions
DP
IRI: http://data.europa.eu/949/hasETCSRestrictionsConditions
- Parameter of
-
Running track
-
Subset with common characteristics
- General Information
-
- Number:
- 1.1.1.3.2.6
- 1.2.1.1.1.6
- XML Name:
- CPE_RestrictionsConditions
- Deadline:
- 12 months after publication of Article 7 Guide for OP tracks
- In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
- Belongs to parameters group
-
TSI compliant train protection system (ETCS)
(
1.1.1.3.2
|
1.2.1.1.1
)
- Data Format
-
- Data Presentation
-
Boolean
- Flags
-
- Applicability Flags:
- Y/N/NYA
- Validation
-
- Dependencies:
- A value has to be provided when ETCS is present (a value is provided on 1.1.1.3.2.1).
- Validation Rules:
-
Has Etcsrestrictions Conditions
Comment: Indication whether restrictions or conditions due to partial compliance with the TSI CCS exist.
Message: hasETCSRestrictionsConditions (1.1.1.3.2.6, 1.2.1.1.1.6): Each track or subset with common characteristics may define the existence of operating restrictions or conditions. This error is due to having more than one value or having a value that is not Y/N (boolean).
-
Has Etcsrestrictions Conditions Applicability
Comment: Only applicable (true) when selected value for 1.1.1.3.2.1 (ETCS present).
Message: hasETCSRestrictionsConditions (1.1.1.3.2.6, 1.2.1.1.1.6):The track or subset with common characteristics {$this} ({?label}), has a 'ETCS level' type selected which makes the hasETCSRestrictionsConditions parameter applicable. This error is due to {$this} not having a value for such a parameter.
- Additional Information
-
- General explanation:
- If operational restrictions and conditions are applicable, a document will be provided as a value of era:era:etcsRestrictionsConditionsDoc property. The RU has to contact the IM to be informed about these conditions.
These conditions and restrictions of use are considered in section 6.4 of the CCS TSI. They should be described using the template available on Agency website (Certification
and deviations - Guidelines for using the ERA template) with the following link: https://www.era.europa.eu/activities/european-rail-traffic-management-system-ertms_en#meeting6.
Train integrity confirmation from on-board (not from driver) necessary for line access
DP
IRI: http://data.europa.eu/949/trainIntegrityOnBoardRequired
- Parameter of
-
Running track
-
Subset with common characteristics
- General Information
-
- Number:
- 1.1.1.3.2.8
- 1.2.1.1.1.8
- XML Name:
- CPE_IntegrityConfirmation
- Deadline:
- 16 January 2020
- 12 months after publication of Article 7 Guide for OP tracks
- Belongs to parameters group
-
TSI compliant train protection system (ETCS)
(
1.1.1.3.2
|
1.2.1.1.1
)
- Flags
-
- Applicability Flags:
- Y/N/NYA
- Validation
-
- Dependencies:
- A value has to be provided when ETCS Level 2 is present, ETCS Baseline > 4 MR1 and IM confirms train integrity function is required).
- Parameter only applicable when ETCS Baseline > 4 MR1 with operation requiring train integrity.
- Validation Rules:
-
Train Integrity On Board Required
Comment: Indication whether train confirmation from on-board is required to access the line for safety reasons. In hybrid operation, the confirmation can be optional.
Message: trainIntegrityOnBoardRequired (1.1.1.3.2.8, 1.2.1.1.1.8): The track or subset with common characteristics defines a train integrity confirmation from on-board (not from driver) necessary for line access. This error is due to having more than one value or having a value that is not in the list of valid alternatives.
- OPE TSI References
-
- Part of RCC Algorithm:
- true
-
- Appendix D2 Index
- 3.4.11
- Additional Information
-
- General explanation:
- In hybrid operation, the confirmation can be optional.
See also: TSI CCS BDC 4.2.2 (Managing information about the completeness of the train (not from driver))
ETCS system compatibility
OP
IRI: http://data.europa.eu/949/etcsSystemCompatibility
- Parameter of
-
ETCS
-
Vehicle Type
- General Information
-
- Number:
- 1.1.1.3.2.9
- 1.2.1.1.1.9
- XML Name:
- CPE_SystemCompatibility
- Deadline:
- 12 months after publication of Article 7 Guide for OP tracks
- 16 January 2020
- Belongs to parameters group
-
TSI compliant train protection system (ETCS)
(
1.1.1.3.2
|
1.2.1.1.1
)
-
Vehicle type technical characteristic
- Data Format
-
- Data Presentation
-
Concept
- Taxonomy Reference:
-
ETCS System Compatibilities
-
Values :
-
| Code |
Value |
| 10 |
Not Defined |
| 20 |
ESC-EU-0 |
| 30 |
ESC-SE-01-HiL2 |
| 40 |
ESC-SE-02-BoL2 |
| 50 |
ESC-SE-03-L3 |
| 60 |
ESC-SE-04-HiL2B3 |
| 70 |
ESC-SE-05-BoL2B3 |
| 71 |
ESC-ES-211 |
| 72 |
ESC-ES-221 |
| 73 |
ESC-ES-231 |
| 74 |
ESC-ES-232 |
| 75 |
ESC-ES-241 |
| 76 |
ESC-ES-251 |
| 77 |
ESC-ES-262 |
| 78 |
ESC-ES-271 |
| 79 |
ESC-ES-281 |
| 80 |
ESC-ES-292 |
| 81 |
ESC-ES-311 |
| 82 |
ESC-ES-312 |
| 83 |
ESC-ES-321 |
| 84 |
ESC-ES-332 |
| 85 |
ESC-ES-341 |
| 86 |
ESC-ES-351 |
| 87 |
ESC-ES-381 |
| 88 |
ESC-ES-412 |
| 89 |
ESC-ES-422 |
| 90 |
ESC-ES-432 |
| 91 |
ESC-ES-441 |
| 92 |
ESC-ES-511 |
| 93 |
ESC-ES-521 |
| 94 |
ESC-ES-541 |
| 95 |
ESC-SE-07 |
| 101 |
ESC-NL-01 |
| 102 |
ESC-NL-02 |
| 103 |
ESC-NL-03 |
| 104 |
ESC-NL-04 |
| 105 |
ESC-NL-05 |
| 106 |
ESC-NL-06 |
| 107 |
ESC-NL-07 |
| 108 |
ESC-NL-08 |
| 109 |
ESC-NL-09 |
| 110 |
ESC-NL-10 |
| 111 |
ESC-NL-11 |
| 112 |
ESC-NL-12 |
| 113 |
ESC-NL-13 |
| 114 |
ESC-NL-14 |
| 115 |
ESC-NL-15 |
| 116 |
ESC-NL-16 |
| 117 |
ESC-NL-17 |
| 118 |
ESC-NL-18 |
| 119 |
ESC-NL-19 |
| 120 |
ESC-NL-20 |
| 121 |
ESC-NL-21 |
| 122 |
ESC-NL-22 |
| 123 |
ESC-NL-23 |
| 201 |
ESC-FR-01-LB |
| 202 |
ESC-FR-02-LB |
| 203 |
ESC-FR-03-LB |
| 204 |
ESC-FR-04-LB |
| 205 |
ESC-FR-05-LB |
| 206 |
ESC-FR-06-LB |
| 207 |
ESC-FR-07-SF |
| 208 |
ESC-FR-08-SF |
| 209 |
ESC-FR-09-SF |
| 210 |
ESC-FR-10-SF |
| 211 |
ESC-FR-11-SF |
| 212 |
ESC-FR-12-SF |
| 213 |
ESC-FR-13-SF |
| 214 |
ESC-FR-14-SF |
| 215 |
ESC-FR-15-SF |
| 216 |
ESC-FR-16-SF |
| 217 |
ESC-FR-17-SF |
| 218 |
ESC-FR-18-SF |
| 219 |
ESC-FR-19-SF |
| 220 |
ESC-FR-20-SF |
| 221 |
ESC-FR-21-SF |
| 222 |
ESC-FR-22-LB |
| 223 |
ESC-FR-23-LB |
| 224 |
ESC-FR-27-LGVEE |
| 225 |
ESC-FR-28-LGVEE |
| 226 |
ESC-FR-29-LGVEE |
| 227 |
ESC-FR-30-LGVEE |
| 228 |
ESC-FR-31-LGVEE |
| 229 |
ESC-FR-32-LGVEE |
| 230 |
ESC-BE-02-L2FS |
| 231 |
ESC-BE-03-L1LS |
| 232 |
ESC-IT-01-RFI-1.0_L2_AVp_RMNA_01 |
| 233 |
ESC-IT-02-RFI-1.0_L2_AVp_MIBO_01 |
| 234 |
ESC-IT-03-RFI-1.0_L2_AVp_BOFI_01 |
| 235 |
ESC-IT-04-RFI-1.0_L2_AVp_TOMI_01 |
| 236 |
ESC-IT-05-RFI-1.0_L2_AVp_TRBR_01 |
| 237 |
ESC-IT-06-RFI-1.0_L2_AVp_DD_01 |
| 238 |
ESC-IT-08-RFI-2.0_L1_Cs_DONO_01 |
| 239 |
ESC-PL-01-L1 |
| 240 |
ESC-PL-02-L1LS |
| 241 |
ESC-PL-03-L2 |
| 242 |
ESC-PL-04-L2 |
| 243 |
ESC-NO-01 |
| 244 |
ESC-IT-07-RFI-2.0_L1_Cs_ISDO_01 |
| 245 |
ESC-IT-09-RFI-2.0_L1_Cs_CHIASSO_01 |
| 246 |
ESC-IT-10-RFI-2.1_L2_Cs_NOPD_01 |
| 247 |
ESC-IT-11-RFI-2.0_L1_Cs_PTLU_01 |
| 248 |
ESC-BE-01-L1FS |
| 249 |
ESC-BE-04-LGV3_4 |
| 250 |
ESC-DK-01-East |
| 251 |
ESC-DK-02-West |
| 252 |
ESC-AT-01 |
| 253 |
ESC-FR-24-AA |
| 254 |
ESC-FR-25-AD |
| 255 |
ESC-FR-26-AE |
| 256 |
ESC-FR-33-SEA |
| 257 |
ESC-FR-34-SEA |
| 258 |
ESC-FR-35-BPL |
| 259 |
ESC-FR-36-BPL |
| 260 |
ESC-IT-12-RFI-2.0_L1_Cs_ISDO_CH_01 |
| 261 |
ESC-IT-13-RFI-2.0_L1_Cs_PTLU_CH_01 |
| 262 |
ESC-IT-14-RFI_2.1_L1_Cs_VENTIMIGLIA_01 |
| 263 |
ESC-IT-15-RFI_2.1_L1_Cs_VENTIMIGLIA_FR_01 |
| 264 |
ESC-IT-16-RFI_2.1_L1_Cs_VIVO_01 |
| 265 |
ESC-IT-17-RFI_2.1_L2_Cs_MIMOCH_01 |
| 266 |
ESC-PL-05-L2 |
| 267 |
ESC-PL-06-L2 |
| 268 |
ESC-CZ-01 |
| 269 |
ESC-CZ-02 |
| 270 |
ESC-RO-01 |
| 271 |
ESC-DE-01-B2_L2 |
| 272 |
ESC-DE-02-B3_L2 |
| 273 |
ESC-NO-02 |
| 274 |
ESC-IT-18-RFI_2.1_L2_Cs_NOPD_02 |
| 275 |
ESC-IT-19-RFI_1.0_L2_AVp_AGGR01_01 |
| 276 |
ESC-IT-20-RFI_1.0_L2_AVp_AGGR02_01 |
| 277 |
ESC-IT-21-RFI_2.0_L1_Cs_AGGR03_01 |
| 278 |
ESC-IT-22-RFI_1.0_L1_Cs_AGGR04_01 |
| 279 |
ESC-IT-23-RFI_2.1_L1_Cs_AGGR05_01 |
| 280 |
ESC-CH-01-L1LS |
| 281 |
ESC-CH-02-L2 |
| 282 |
ESC-CH-03-L1LSL2 |
| 283 |
ESC-LU-01-RFN |
| 284 |
ESC-LU-02-MSM |
| 285 |
ESC-LU-03-IG |
- Flags
-
- Applicability Flags:
- Y/N/NYA
- Validation
-
- Dependencies:
- A value has to be provided when ETCS is present (a value is provided on 1.1.1.3.2.1).
- Validation Rules:
-
Etcs System Compatibility Applicability
Comment: Only applicable when selected value for 1.1.1.3.2.1 (ETCS present).
Message: etcsSystemCompatibility (1.1.1.3.2.9, 1.2.1.1.1.9): The ETCS {$this} ({?thisLabel}), has a ETCS level type which makes the etcsSystemCompatibility parameter applicable. This error is due to {$this} not having a value for such a parameter.
-
Etcs System Compatibility Skos
Comment: ETCS requirements used for demonstrating technical compatibility.
Message: etcsSystemCompatibility (1.1.1.3.2.9, 1.2.1.1.1.9): The ETCS {$this} has a value {?concept} that is not one of the predefined values and cannot be converted into a SKOS concept on this list: http://data.europa.eu/949/concepts/etcs-system-compatibilities/ETCSSystemCompatibilities.
-
Etcs System Compatibility
Comment: ETCS requirements used for demonstrating technical compatibility.
Message: etcsSystemCompatibility (1.1.1.3.2.9, 1.2.1.1.1.9): The ETCS has a etcsSystemCompatibility value that must be an IRI. This error is due to the ETCS having a value that is not an IRI.
- OPE TSI References
-
- Part of RCC Algorithm:
- true
- Additional Information
-
- General explanation:
- The Values "Not defined" or "ESC-EU-0" should not be combined with other values.
For application in CCS Onboard:
The vehicles are considered compatible with the infrastructure for this parameter, if their parameter value matches any of the values declared on the trackside.
For application in CCS Trackside:
The Infrastructure Manager is responsible for defining the ESC type(s). All sections of the Union network which require the same set of checks for the demonstration of ESC shall have the same ESC type.
See: TSI CCS, Appendix A, Table A 1, 4.2.17 a.
The list of ESC Types is published and maintained by the European Union Agency for Railways in the technical document "ESC/RSC technical document, TD/011REC1028".
The Agency shall assess the checks unless they have been assessed by a NoBo as required in Table 6.3 row 10.
The assessment by the Agency shall be done within 2 months of receipt thereof, unless a longer period is agreed between the Agency and the Infrastructure Manager but not exceeding 4 months in total.
The technical document will be updated within 10 working days after positive assessment.
The ESC Types shall only be used when published with status "Valid" in the Agency Technical document referred above.
ETCS M_version
OP
IRI: http://data.europa.eu/949/etcsMVersion
- Parameter of
-
ETCS
- General Information
-
- Number:
- 1.1.1.3.2.10
- 1.2.1.1.1.10
- XML Name:
- CPE_MVersion
- Deadline:
- 12 months after publication of Article 7 Guide for OP tracks
- 1 January 2021
- Belongs to parameters group
-
TSI compliant train protection system (ETCS)
(
1.1.1.3.2
|
1.2.1.1.1
)
- Data Format
-
- Data Presentation
-
Concept
- Taxonomy Reference:
-
ETCS M Versions
-
Values :
-
- Flags
-
- Applicability Flags:
- Y/N/NYA
- Validation
-
- Dependencies:
- A value has to be provided when ETCS is present (a value is provided on 1.1.1.3.2.1).
- Validation Rules:
-
Etcs Mversion
Comment: ETCS_M version according to SRS 7.5.1.9
Message: etcsMVersion (1.1.1.3.2.10, 1.2.1.1.1.10): The ETCS has at most one ETCS_M version value and it must be an IRI. This error is due to the ETCS having more than one value or having a value that is not an IRI.
-
Etcs Mversion Applicability
Comment: Only applicable when selected value for 1.1.1.3.2.1 contains 1. Related to rule for etcsLevelType
Message: etcsMVersion (1.1.1.3.2.10, 1.2.1.1.1.10): The ETCS {$this} ({?thisLabel}), has a ETCS level type '1' which makes the etcsMVersion parameter applicable. This error is due to {$this} not having a value for such a parameter.
-
Etcs Mversion Skos
Comment: ETCS_M version according to SRS 7.5.1.9
Message: Indication of the etcsMVersion (1.1.1.3.2.10, 1.1.1.3.2.10):): The ETCS {$this} has a value {?concept} that is not one of the predefined values and cannot be converted into a SKOS concept on this list: http://data.europa.eu/949/concepts/etcs-m-versions/ETCSMVersions.
- OPE TSI References
-
- Part of RCC Algorithm:
- true
- Additional Information
-
- General explanation:
- See: TSI CCS (Subset-026, Chapter 7, 7.5.1.79 M_VERSION)
Is the ETCS trackside engineered to transmit Track Conditions
DP
IRI: http://data.europa.eu/949/etcsTransmitsTrackConditions
- Parameter of
-
ETCS
- General Information
-
- Number:
- 1.1.1.3.2.12
- 1.2.1.1.1.12
- XML Name:
- CPE_CanTransmitTCs
- Deadline:
- 12 months after publication of Article 7 Guide
- Belongs to parameters group
-
TSI compliant train protection system (ETCS)
(
1.1.1.3.2
|
1.2.1.1.1
)
- Data Format
-
- Data Presentation
-
Boolean
- Flags
-
- Applicability Flags:
- Y/N/NYA
- Validation
-
- Dependencies:
- A value has to be provided when ETCS is present (a value is provided on 1.1.1.3.2.1).
- Validation Rules:
-
Etcs Transmits Track Conditions
Comment: If the trackside does not provide Track Conditions, the driver will need to be informed about such conditions via alternative methods.
Message: etcsTransmitsTrackConditions (1.1.1.3.2.12, 1.2.1.1.1.12): Each Track may define the existence of ETCS trackside engineered to transmit Track Conditions. This error is due to having more than one value or having a value that is not Y/N (boolean).
-
Etcs Transmits Track Conditions Applicability
Comment: Only applicable when selected value for 1.1.1.3.2.1 (ETCS present).
Message: etcsTransmitsTrackConditions (1.1.1.3.2.12.1, 1.2.1.1.1.12.1): The ETCS {$this} ({?thisLabel}), has a ETCS level type which makes the etcsTransmitsTrackConditions parameter applicable. This error is due to {$this} not having a value for such a parameter.
- Additional Information
-
- General explanation:
- According to the specification referenced in Appendix A-1, index [C]
If the trackside does not provide Track Conditions, the driver will need to be informed about such conditions via alternative methods.
In ETCS level NTC and level 0 track conditions are not managed (at least in Baseline 2)
See: TSI CCS (Subset-026, Chapter 5, section 5.18)
Track conditions which can be transmitted
OP
IRI: http://data.europa.eu/949/etcsTransmittedTrackConditions
- Parameter of
-
ETCS
- General Information
-
- Number:
- 1.1.1.3.2.12.1
- 1.2.1.1.1.12.1
- XML Name:
- CPE_TransmittedTCs
- Deadline:
- 12 months after publication of Article 7 Guide
- Belongs to parameters group
-
TSI compliant train protection system (ETCS)
(
1.1.1.3.2
|
1.2.1.1.1
)
- Data Format
-
- Data Presentation
-
Concept
- Flags
-
- Applicability Flags:
- Y/N/NYA
- Validation
-
- Dependencies:
- Mandatory when ETCS is present (a value is provided on 1.1.1.3.2.1) and value of 1.1.1.3.2.12 is True.
- Validation Rules:
-
Etcs Transmitted Track Conditions Applicability
Comment: Only applicable when selected value for 1.1.1.3.2.1 (ETCS present).
Message: etcsTransmittedTrackConditions (1.1.1.3.2.12.1, 1.2.1.1.1.12.1): The ETCS {$this} ({?thisLabel}), has a ETCS level type which makes the etcsTransmittedTrackConditions parameter applicable. This error is due to {$this} not having a value for such a parameter.
-
Etcs Transmitted Track Conditions Skos
Comment: Transmittable track conditions by the CCSSubsystem, as per CCS TSI.
Message: etcsTransmittedTrackConditions (1.1.1.3.2.12.1, 1.2.1.1.1.12.1): The ETCS {$this} has a value {?concept} that is not one of the predefined values and cannot be converted into a SKOS concept on this list: http://data.europa.eu/949/concepts/etcs-transmitted-tcs/TransmittedTrackConditions.
-
Etcs Transmitted Track Conditions
Comment: Transmittable track conditions by the CCSSubsystem, as per CCS TSI.
Message: etcsTransmittedTrackConditions (1.1.1.3.2.12.1, 1.2.1.1.1.12.1): The ETCS has at most one etcsTransmittedTrackConditions value and it must be an IRI. This error is due to the ETCS having more than one value or having a value that is not an IRI.
- Additional Information
-
- General explanation:
- See: TSI CCS (Subset-026, Chapter 5, section 5.18.1.1)
ETCS trackside implements level crossing procedure or an equivalent solution
DP
IRI: http://data.europa.eu/949/etcsImplementsLevelCrossingProcedure
- Parameter of
-
Running track
-
Subset with common characteristics
- General Information
-
- Number:
- 1.1.1.3.2.13
- 1.2.1.1.1.13
- XML Name:
- CPE_LXProcedure
- Deadline:
- 12 months after publication of Article 7 Guide
- Belongs to parameters group
-
TSI compliant train protection system (ETCS)
(
1.1.1.3.2
|
1.2.1.1.1
)
- Data Format
-
- Data Presentation
-
Boolean
- Flags
-
- Applicability Flags:
- Y/N/NYA
- Validation
-
- Dependencies:
- Applicable and mandatory when ETCS is present (a value is provided on 1.1.1.3.2.1).
- Validation Rules:
-
Etcs Implements Level Crossing Procedure Applicability
Comment: Only applicable when selected value for 1.1.1.3.2.1 (ETCS present).
Message: etcsImplementsLevelCrossingProcedure (1.1.1.3.2.13, 1.2.1.1.1.13):The track or subset with common characteristics {$this} ({?label}), has an 'ETCS Level Type' defined that makes the etcsImplementsLevelCrossingProcedure parameter applicable. This error is due to {$this} not having a value for such a parameter.
-
Etcs Implements Level Crossing Procedure
Comment: If The track or subset with common characteristicsside does not implement any solution to cover defective LXs (which are normally protected by means of a technical system), then drivers will be required to comply with instructions received from other sources.
Message: etcsImplementsLevelCrossingProcedure (1.1.1.3.2.13, 1.2.1.1.1.13): Each track or subset with common characteristics may define the existence of level crossing procedure or an equivalent solution for ETCS trackside. This error is due to having more than one value or having a value that is not Y/N (boolean).
- Additional Information
-
- General explanation:
- See: TSI CCS (Subset-026, Chapter 5, section 5.16)
Cant Deficiency used for the basic SSP
OP
IRI: http://data.europa.eu/949/cantDeficiencyBasicSSP
- Parameter of
-
Running track
-
Subset with common characteristics
- General Information
-
- Number:
- 1.1.1.3.2.14
- 1.2.1.1.1.14
- XML Name:
- CPE_SSPUsesCantDef
- Deadline:
- 12 months after publication of Article 7 Guide
- Belongs to parameters group
-
TSI compliant train protection system (ETCS)
(
1.1.1.3.2
|
1.2.1.1.1
)
- Data Format
-
- Data Presentation
-
Concept
- Unit of Measure:
-
Millimetre
- Taxonomy Reference:
-
Cant Deficiencies - Static Speed Profile Categories (Basic and Specific, type 1)
-
Values :
-
- Flags
-
- Applicability Flags:
- Y/N/NYA
- Validation
-
- Dependencies:
- A value has to be provided when ETCS is present (a value is provided on 1.1.1.3.2.1).
- Validation Rules:
-
Cant Deficiency Basic Ssp
Comment: Essential information for drivers of trains with a worse (lower) tolerated cant deficiency than those for which the ETCS trackside provides SSP (Static Speed Profiles) in conjunction with parameter "Other Cant Deficiency train categories for which the ETCS trackside is configured to provide SSP".
Message: cantDeficiencyBasicSSP (1.1.1.3.2.14, 1.2.1.1.1.14): The track or subset with common characteristics must have a cant deficiency used for the basis SSP value that is an IRI.
-
Cant Deficiency Basic Sspapplicability
Comment: Only applicable when selected value for 1.1.1.3.2.1 (ETCS present).
Message: cantDeficiencyBasicSSP (1.1.1.3.2.14, 1.2.1.1.1.14):The track or subset with common characteristics {$this} ({?label}), has a 'ETCS Level Type' defined which makes the cantDeficiencyBasicSSP parameter applicable. This error is due to {$this} not having a value for such a parameter.
-
Cant Deficiency Basic Sspskos
Comment: Essential information for drivers of trains with a worse (lower) tolerated cant deficiency than those for which the ETCS trackside provides SSP (Static Speed Profiles) in conjunction with parameter "Other Cant Deficiency train categories for which the ETCS trackside is configured to provide SSP".
Message: cantDeficiencyBasicSSP (1.1.1.3.2.14, 1.2.1.1.1.14): The track or subset with common characteristics {$this} (label {?label}) has a value {?concept} that is not one of the predefined values and cannot be converted into a SKOS concept on this list: http://data.europa.eu/949/concepts/cant-deficiencies/CantDeficiencies.
- Additional Information
-
- General explanation:
- The values indicated in millimetres correspond to tracks with UIC gauge. For tracks with a gauge different from UIC, the values provided here are the equivalent ones for UIC gauge, as the actual physical cant deficiency values differ. Please refer to parameter 1.1.1.1.4.2 for more details.
Subset-026 (3.11.3.2.1.1) definition:
a) The "Cant Deficiency" SSP categories: the cant deficiency value assigned to one category shall define the maximum speed, determined by suspension design, at which a particular train can traverse a curve and thus can be used to set a specific speed limit in a curve with regards to this category.
Other Cant Deficiency train categories for which the ETCS trackside is configured to provide SSP
OP
IRI: http://data.europa.eu/949/otherCantDeficiencyBasicSSP
- Parameter of
-
Running track
-
Subset with common characteristics
- General Information
-
- Number:
- 1.1.1.3.2.14.1
- 1.2.1.1.1.14.1
- XML Name:
- CPE_OtherCantDef
- Deadline:
- 12 months after publication of Article 7 Guide
- Belongs to parameters group
-
TSI compliant train protection system (ETCS)
(
1.1.1.3.2
|
1.2.1.1.1
)
- Data Format
-
- Data Presentation
-
Concept
- Unit of Measure:
-
Millimetre
- Taxonomy Reference:
-
Cant Deficiencies - Static Speed Profile Categories (Basic and Specific, type 1)
-
Values :
-
- Flags
-
- Applicability Flags:
- Y/N/NYA
- Validation
-
- Dependencies:
- A value has to be provided when ETCS is present (a value is provided on 1.1.1.3.2.1).
- Validation Rules:
-
Other Cant Deficiency Basic Ssp
Comment: Essential information for drivers of trains with a worse (lower) tolerated cant deficiency than those for which the ETCS trackside provides SSP (Static Speed Profiles) in conjunction with parameter 'Cant Deficiency used for the basic SSP'.
Message: otherCantDeficiencyBasicSSP (1.1.1.3.2.14.1, 1.2.1.1.1.14.1): The track or subset with common characteristics must have other Cant Deficiency train categories basic SSP value that is an IRI. This error is due to having more than one value or having a value that is not an IRI
-
Other Cant Deficiency Basic Sspskos
Comment: Essential information for drivers of trains with a worse (lower) tolerated cant deficiency than those for which the ETCS trackside provides SSP (Static Speed Profiles) in conjunction with parameter 'Cant Deficiency used for the basic SSP'.
Message: otherCantDeficiencyBasicSSP (1.1.1.3.2.14.1, 1.2.1.1.1.14.1): The track or subset with common characteristics {$this} (label {?label}) has a value {?concept} that is not one of the predefined values and cannot be converted into a SKOS concept on this list: http://data.europa.eu/949/concepts/cant-deficiencies/CantDeficiencies.
-
Other Cant Deficiency Basic Sspapplicability
Comment: Only applicable when selected value for 1.1.1.3.2.1 (ETCS present).
Message: otherCantDeficiencyBasicSSP (1.1.1.3.2.14.1, 1.2.1.1.1.14.1):The track or subset with common characteristics {$this} ({?label}), has an 'ETCS Level Type' defined which makes the otherCantDeficiencyBasicSSP parameter applicable. This error is due to {$this} not having a value for such a parameter.
- Additional Information
-
- General explanation:
- The values indicated in millimetres correspond to tracks with UIC gauge. For tracks with a gauge different from UIC, the values provided here are the equivalent ones for UIC gauge, as the actual physical cant deficiency values differ. Please refer to parameter 1.1.1.1.4.2 for more details.
Subset-026 (3.11.3.2.1.1) definition: b) The "other specific" SSP categories: it groups all other specific SSP categories corresponding to the other international train categories.
Reasons for which an ETCS Radio Block Center can reject a train
OP
IRI: http://data.europa.eu/949/reasonsEtcsRadioBlockCenterReject
- Parameter of
-
Radio Block Center
- General Information
-
- Number:
- 1.1.1.3.2.15
- 1.2.1.1.1.15
- XML Name:
- CPE_RBCRejectReasons
- Deadline:
- 12 months after publication of Article 7 Guide
- Belongs to parameters group
-
TSI compliant train protection system (ETCS)
(
1.1.1.3.2
|
1.2.1.1.1
)
- Data Format
-
- Data Presentation
-
Concept
- Taxonomy Reference:
-
ETCS Reasons RBC can reject a train
-
Values :
-
| Code |
Value |
| 00 |
N/A - no usage of Message 40 (Train rejected) |
| 01 |
Invalid ETCS-key |
| 02 |
Non-matching ETCS-ID |
| 03 |
Incompatible baseline |
- Flags
-
- Applicability Flags:
- Y/N/NYA
- Validation
-
- Dependencies:
- A value has to be provided when ETCS is present (a value is provided on 1.1.1.3.2.1).
- Validation Rules:
-
Reasons Etcs Radio Block Center Reject
Comment: List of cases subject to system design choices made by the infrastructure manager according to the specification referenced in TSI CCS.
Message: reasonsEtcsRadioBlockCenterReject (1.1.1.3.2.15, 1.2.1.1.1.15): The track or subset with common characteristics must have a single reasons for which an ETCS Radio Block Center can reject a train value that is an IRI. This error is due to having more than one value or having a value that is not an IRI.
-
Reasons Etcs Radio Block Center Reject Skos
Comment: List of cases subject to system design choices made by the infrastructure manager according to the specification referenced in TSI CCS.
Message: reasonsEtcsRadioBlockCenterReject (1.1.1.3.2.15, 1.2.1.1.1.15): The track or subset with common characteristics {$this} (label {?label}) has a value {?concept} that is not one of the predefined values and cannot be converted into a SKOS concept on this list: http://data.europa.eu/949/concepts/etcs-rbc-reject-reasons/ETCSRBCRejectionReasons.
- Additional Information
-
- General explanation:
- 1. Distinguish between mandatory and optional: decision was only to record the mandatory ones, but optional reasons can be added.
2. Providing the non-implemented CR-solution which have been accepted by IM, after check/approval with RU's, is also allowed.
D_NVROLL
DP
IRI: http://data.europa.eu/949/dNvroll
- Parameter of
-
Running track
-
Subset with common characteristics
- General Information
-
- Number:
- 1.1.1.3.2.16.1
- 1.2.1.1.1.16.1
- XML Name:
- CPE_DNVROLL
- Deadline:
- 12 months after publication of Article 7 Guide
- Belongs to parameters group
-
ETCS National Values
(
1.1.1.3.2.16
|
1.2.1.1.1.16
)
- Data Format
-
- Format:
- A number of form at NNNNNN.N, from 0 to 327670
- Unit of Measure:
-
Metre
- Flags
-
- Applicability Flags:
- Y/N/NYA
- Validation
-
- Dependencies:
- A value has to be provided when ETCS is present (a value is provided on 1.1.1.3.2.1).
- Validation Rules:
-
Dnvroll Applicability
Comment: Only applicable when selected value for 1.1.1.3.2.1 (ETCS present).
Message: dNvroll (1.1.1.3.2.16.7, 1.2.1.1.1.16.7):The track or subset with common characteristics {$this} ({?label}), has an 'ETCS Level Type' defined which makes the dNvroll parameter applicable. This error is due to {$this} not having a value for such a parameter.
-
Dnvroll
Comment: Parameter used by the ETCS on-board to supervise the distance allowed to be travelled under the roll-away protection and the reverse movement protection, in metres.
Message: dNvroll (1.1.1.3.2.16.1, 1.2.1.1.1.16.1): Each track or subset with common characteristics must define the parameter used by the ETCS on-board to supervise the distance allowed to be travelled under the roll-away protection and the reverse movement protection expressed in metres. This error is due to having more than one value or having a value that is not a double (real) number.
- Additional Information
-
- General explanation:
- Precision: [NNNNNN.N], with N a decimal number (0 9).
See: TSI CCS (Subset 26, chapter 7. 7.5.1.17 D_NVROLL)
Q_NVEMRRLS
OP
IRI: http://data.europa.eu/949/qNvemrrls
- Parameter of
-
Running track
-
Subset with common characteristics
- General Information
-
- Number:
- 1.1.1.3.2.16.2
- 1.2.1.1.1.16.2
- XML Name:
- CPE_QNVEMRRLS
- Deadline:
- 12 months after publication of Article 7 Guide
- Belongs to parameters group
-
ETCS National Values
(
1.1.1.3.2.16
|
1.2.1.1.1.16
)
- Data Format
-
- Data Presentation
-
Concept
- Taxonomy Reference:
-
Emergency Brake Release Command Qualifiers
-
Values :
-
| Code |
Value |
| 0 |
Revoke emergency brake command at standstill |
| 1 |
Revoke emergency brake command when permitted speed supervision limit is no longer exceeded |
- Flags
-
- Applicability Flags:
- Y/N/NYA
- Validation
-
- Dependencies:
- A value has to be provided when ETCS is present (a value is provided on 1.1.1.3.2.1).
- Validation Rules:
-
Qnvemrrls Skos
Comment: Qualifier defining whether the application of the emergency brake for reasons other than a trip can be revoked as soon as the conditions for it have disappeared or after the train has come to a complete standstill.
Message: qNvemrrls (1.1.1.3.2.16.2, 1.2.1.1.1.16.2): The track or subset with common characteristics {$this} (label {?label}) has a value {?concept} that is not one of the predefined values and cannot be converted into a SKOS concept on this list: http://data.europa.eu/949/concepts/ebr-qualifier/EBReleaseQualifier.
-
Qnvemrrls
Comment: Qualifier defining whether the application of the emergency brake for reasons other than a trip can be revoked as soon as the conditions for it have disappeared or after the train has come to a complete standstill.
Message: qNvemrrls (1.1.1.3.2.16.2, 1.2.1.1.1.16.2): The track or subset with common characteristics must have a single Q_NVEMRRLS value that is an IRI. This error is due to having more than one value or having a value that is not an IRI.
-
Qnvemrrls Applicability
Comment: Only applicable when parameter 1.1.1.3.2.1 is applicable (its Applicable: 'Y').
Message: qNvemrrls (1.1.1.3.2.16.2, 1.2.1.1.1.16.2):The track or subset with common characteristics {$this} ({?label}), has an 'ETCS Level Type' defined which makes the qNvemrrls parameter applicable. This error is due to {$this} not having a value for such a parameter.
- Additional Information
-
- General explanation:
- According to the specification referenced in Appendix A-1, index [C] - TSI CCS (Subset-026, chapter 7, 7.5.1.123 Q_NVEMRRLS)
V_NVALLOWOVTRP
DP
IRI: http://data.europa.eu/949/vNvallowovtrp
- Parameter of
-
Running track
-
Subset with common characteristics
- General Information
-
- Number:
- 1.1.1.3.2.16.3
- 1.2.1.1.1.16.3
- XML Name:
- CPE_VNVALLOWOVTRP
- Deadline:
- 12 months after publication of Article 7 Guide
- Belongs to parameters group
-
ETCS National Values
(
1.1.1.3.2.16
|
1.2.1.1.1.16
)
- Data Format
-
- Format:
- NNF, with N a decimal number (0 9), NNF must be divisible by 5, so F=(0|5), max. `600`
- Unit of Measure:
-
Kilometre per Hour
- Flags
-
- Applicability Flags:
- Y/N/NYA
- Validation
-
- Dependencies:
- A value has to be provided when ETCS is present (a value is provided on 1.1.1.3.2.1).
- Validation Rules:
-
Vnvallowovtrp
Comment: Speed limit allowing the driver to select the “override” function in km/h.
Message: vNvallowovtrp (1.1.1.3.2.16.3, 1.2.1.1.1.16.3): The track or subset with common characteristics defines a speed limit allowing the driver to select the “override” function (V_NVALLOWOVTRP). This error is due to having more than one value, having a value that is not an integer or having an integer that does not follow the pattern [NNF], with N a decimal number (0÷9), F=(0|5), max. `600`.
-
Vnvallowovtrp Applicability
Comment: Only applicable when selected value for 1.1.1.3.2.1 (ETCS present).
Message: vNvallowovtrp (1.1.1.3.2.16.3, 1.2.1.1.1.16.3):The track or subset with common characteristics {$this} ({?label}), has an 'ETCS Level Type' defined which makes the vNvallowovtrp parameter applicable. This error is due to {$this} not having a value for such a parameter.
- Additional Information
-
- General explanation:
- Format: [NNF], with N a decimal number (0÷9), [NNF] must be divisible by 5, so F=(0|5), max. `600`.
See: TSI CCS (Subset-026, Chapter 7. 7.5.1.161)
V_NVSUPOVTRP
DP
IRI: http://data.europa.eu/949/vNvsupovtrp
- Parameter of
-
Running track
-
Subset with common characteristics
- General Information
-
- Number:
- 1.1.1.3.2.16.4
- 1.2.1.1.1.16.4
- XML Name:
- CPE_VNVSUPOVTRP
- Deadline:
- 12 months after publication of Article 7 Guide for OP tracks
- 12 months after publication of Article 7 Guide
- Belongs to parameters group
-
ETCS National Values
(
1.1.1.3.2.16
|
1.2.1.1.1.16
)
- Data Format
-
- Format:
- NNF, with N a decimal number (0 9), NNF must be divisible by 5, so F=(0|5), max. `600`
- Unit of Measure:
-
Kilometre per Hour
- Flags
-
- Applicability Flags:
- Y/N/NYA
- Validation
-
- Dependencies:
- A value has to be provided when ETCS is present (a value is provided on 1.1.1.3.2.1).
- Validation Rules:
-
Vnvsupovtrp Applicability
Comment: Only applicable when selected value for 1.1.1.3.2.1 (ETCS present).
Message: vNvsupovtrp (1.1.1.3.2.16.4, 1.2.1.1.1.16.4):The track or subset with common characteristics {$this} ({?label}), has an 'ETCS Level Type' defined which makes the vNvsupovtrp parameter applicable. This error is due to {$this} not having a value for such a parameter.
-
Vnvsupovtrp
Comment: Override speed limit to be supervised when the “override” function is active in km/h.
Message: vNvsupovtrp (1.1.1.3.2.16.4, 1.2.1.1.1.16.4): The track or subset with common characteristics defines a override speed limit to be supervised when the “override” function is active (V_NVSUPOVTRP). This error is due to having more than one value, having a value that is not an integer or having an integer that does not follow the pattern [NNF], with N a decimal number (0÷9), F=(0|5), max. `600`.
- Additional Information
-
- General explanation:
- Format: [NNF], with N a decimal number (0÷9), [NNF] is divisible by 5 so F=(0|5), max. `600`.
See: TSI CCS (Subset-026, chapter 7. 7.5.1.163 V_NVSUPOVTRP)
D_NVOVTRP
DP
IRI: http://data.europa.eu/949/dNvovtrp
- Parameter of
-
Running track
-
Subset with common characteristics
- General Information
-
- Number:
- 1.1.1.3.2.16.5
- 1.2.1.1.1.16.5
- XML Name:
- CPE_DNVOVTRP
- Deadline:
- 12 months after publication of Article 7 Guide
- Belongs to parameters group
-
ETCS National Values
(
1.1.1.3.2.16
|
1.2.1.1.1.16
)
- Data Format
-
- Format:
- NNNNNNN.N whereby the last digit is only used when Q_SCALE = 10 CM
- Unit of Measure:
-
Metre
- Flags
-
- Applicability Flags:
- Y/N/NYA
- Validation
-
- Dependencies:
- A value has to be provided when ETCS is present (a value is provided on 1.1.1.3.2.1).
- Validation Rules:
-
Dnvovtrp Applicability
Comment: Only applicable when selected value for 1.1.1.3.2.1 (ETCS present)
Message: dNvovtrp (1.1.1.3.2.16.5, 1.2.1.1.1.16.5):The track or subset with common characteristics {$this} ({?label}), has an 'ETCS Level Type' defined which makes the dNvovtrp parameter applicable. This error is due to {$this} not having a value for such a parameter.
-
Dnvovtrp
Comment: Maximum distance for overriding the train trip in metres.
Message: dNvovtrp (1.1.1.3.2.16.5, 1.2.1.1.1.16.5): Each track or subset with common characteristics must define the maximum distance for overriding the train trip expressed in metres. This error is due to having maximum distance for overriding the train trip value that is not a double (real) number.
- Additional Information
-
- General explanation:
- Precision: the value must be expressed in meter.
Depending on the chosen Q_SCALE, the maximal value will be: +327670 M, +32767 M or +3276.7 M.
As in TSI CCS Subset 26, chapter 7. 7.5.1.15 D_NVOVTRP.
T_NVOVTRP
DP
IRI: http://data.europa.eu/949/tNvovtrp
- Parameter of
-
Running track
-
Subset with common characteristics
- General Information
-
- Number:
- 1.1.1.3.2.16.6
- 1.2.1.1.1.16.6
- XML Name:
- CPE_TNVOVTRP
- Deadline:
- 12 months after publication of Article 7 Guide
- Belongs to parameters group
-
ETCS National Values
(
1.1.1.3.2.16
|
1.2.1.1.1.16
)
- Data Format
-
- Format:
- NNN, with N as a digit from 0 to 9. Value NNN = 255 means ∞ (infinity), so values cannot be higher.
- Unit of Measure:
-
Second
- Flags
-
- Applicability Flags:
- Y/N/NYA
- Validation
-
- Dependencies:
- A value has to be provided when ETCS is present (a value is provided on 1.1.1.3.2.1).
- Validation Rules:
-
Tnvovtrp Applicability
Comment: Only applicable when selected value for 1.1.1.3.2.1 (ETCS present).
Message: tNvovtrp (1.1.1.3.2.16.6, 1.2.1.1.1.16.6):The track or subset with common characteristics {$this} ({?label}), has an 'ETCS Level Type' defined which makes the tNvovtrp parameter applicable. This error is due to {$this} not having a value for such a parameter.
-
Tnvovtrp
Comment: Maximum time for overriding the train trip in seconds.
Message: tNvovtrp (1.1.1.3.2.16.6 , 1.2.1.1.1.16.6): The track or subset with common characteristics defines a T_NVOVTRP. This error is due to having more than one value, having a value that is not an integer or having an integer that does not follow the pattern [NNN].
- Additional Information
-
- General explanation:
- Precision: [NNN], with N a decimal number (0÷9)
See: TSI CCS (Subset 26, chapter 7. 7.5.1.149 T_NVOVTRP)
D_NVPOTRP
DP
IRI: http://data.europa.eu/949/dNvpotrp
- Parameter of
-
Running track
-
Subset with common characteristics
- General Information
-
- Number:
- 1.1.1.3.2.16.7
- 1.2.1.1.1.16.7
- XML Name:
- CPE_DNVPOTRP
- Deadline:
- 12 months after publication of Article 7 Guide
- Belongs to parameters group
-
ETCS National Values
(
1.1.1.3.2.16
|
1.2.1.1.1.16
)
- Data Format
-
- Format:
- NNNNNNN.N whereby the last digit is only used when Q_SCALE = 10 CM
- Unit of Measure:
-
Metre
- Flags
-
- Applicability Flags:
- Y/N/NYA
- Validation
-
- Validation Rules:
-
Dnvpotrp Applicability
Comment: Only applicable when selected value for 1.1.1.3.2.1 (ETCS present).
Message: dNvpotrp (1.1.1.3.2.16.7, 1.2.1.1.1.16.7):The track or subset with common characteristics {$this} ({?label}), has an 'ETCS Level Type' defined which makes the dNvpotrp parameter applicable. This error is due to {$this} not having a value for such a parameter.
-
Dnvpotrp
Comment: Maximum distance for reversing in Post Trip mode in metres
Message: dNvpotrp (1.1.1.3.2.16.7, 1.2.1.1.1.16.7): Each track or subset with common characteristics must define the maximum distance for reversing in Post Trip mode in metres. This error is due to having maximum distance for reversing in Post Trip mode value that is not a double (real) number.
- Additional Information
-
- General explanation:
- Precision: the value must be expressed in meter.
Depending on the chosen Q_SCALE, the maximal value will be: +327670 M, +32767 M or +3276.7 M.
See: TSI CCS (Subset 26, chapter 7. 7.5.1.16 D_NVPOTRP)
M_NVDERUN
DP
IRI: http://data.europa.eu/949/mNvderun
- Parameter of
-
Running track
-
Subset with common characteristics
- General Information
-
- Number:
- 1.1.1.3.2.16.10
- 1.2.1.1.1.16.10
- XML Name:
- CPE_MNVDERUN
- Deadline:
- 12 months after publication of Article 7 Guide
- Belongs to parameters group
-
ETCS National Values
(
1.1.1.3.2.16
|
1.2.1.1.1.16
)
- Data Format
-
- Data Presentation
-
Boolean
- Flags
-
- Applicability Flags:
- Y/N/NYA
- Validation
-
- Dependencies:
- A value has to be provided when ETCS is present (a value is provided on 1.1.1.3.2.1).
- Validation Rules:
-
Mnvderun
Comment: Entry of Driver ID permitted while running.
Message: mNvderun (1.1.1.3.2.16.10, 1.2.1.1.1.16.10): Each track or subset with common characteristics may define the M_NVDERUN value. This error is due to having more than one value or having a value that is not Y/N (boolean).
-
Mnvderun Applicability
Comment: Only applicable when selected value for 1.1.1.3.2.1 (ETCS present).
Message: mNvderun (1.1.1.3.2.16.10, 1.2.1.1.1.16.10):The track or subset with common characteristics {$this} ({?label}), has an 'ETCS Level Type' defined which makes the mNvderun parameter applicable. This error is due to {$this} not having a value for such a parameter.
- Additional Information
-
- General explanation:
- See: TSI CCS (Subset 26, chapter 7. 7.5.1.75 M_NVDERUN)
Q_NVDRIVER_ADHES
OP
IRI: http://data.europa.eu/949/qNvdriverAdhes
- Parameter of
-
Running track
-
Subset with common characteristics
- General Information
-
- Number:
- 1.1.1.3.2.16.11
- 1.2.1.1.1.16.11
- XML Name:
- CPE_QNVDRIVERADHES
- Deadline:
- 12 months after publication of Article 7 Guide
- Belongs to parameters group
-
ETCS National Values
(
1.1.1.3.2.16
|
1.2.1.1.1.16
)
- Data Format
-
- Data Presentation
-
Concept
- Taxonomy Reference:
-
Driver allowed to change adhesion factor Qualifiers
-
Values :
-
| Code |
Value |
| 0 |
Not allowed |
| 1 |
Allowed |
- Flags
-
- Applicability Flags:
- Y/N/NYA
- Validation
-
- Dependencies:
- A value has to be provided when ETCS is present (a value is provided on 1.1.1.3.2.1).
- Validation Rules:
-
Qnvdriver Adhes
Comment: Qualifier determining whether the driver is allowed to modify the adhesion factor used by the ETCS on-board to calculate the braking curves.
Message: qNvdriverAdhes (1.1.1.3.2.16.11, 1.2.1.1.1.16.11): The track or subset with common characteristics must have a single Q_NVDRIVER_ADHES value that is an IRI. This error is due to having more than one value or having a value that is not an IRI.
-
Qnvdriver Adhes Skos
Comment: Qualifier determining whether the driver is allowed to modify the adhesion factor used by the ETCS on-board to calculate the braking curves.
Message: qNvdriverAdhes (1.1.1.3.2.16.11, 1.2.1.1.1.16.11): The track or subset with common characteristics {$this} (label {?label}) has a value {?concept} that is not one of the predefined values and cannot be converted into a SKOS concept on this list: http://data.europa.eu/949/concepts/adhf-qualifier/AdhesionFactorChange.
-
Qnvdriver Adhes Applicability
Comment: Only applicable when selected value for 1.1.1.3.2.1 (ETCS present).
Message: qNvdriverAdhes (1.1.1.3.2.16.11, 1.2.1.1.1.16.11):The track or subset with common characteristics {$this} ({?label}), has an 'ETCS Level Type' defined which makes the qNvdriverAdhes parameter applicable. This error is due to {$this} not having a value for such a parameter.
- Additional Information
-
- General explanation:
- See: TSI CCS (Subset 26, chapter 7. 7.5.1.122 Q_NVDRIVER_ADHES)
Q_NVSBTSMPERM
DP
IRI: http://data.europa.eu/949/qNvsbtsmperm
- Parameter of
-
Running track
-
Subset with common characteristics
- General Information
-
- Number:
- 1.1.1.3.2.16.12
- 1.2.1.1.1.16.12
- XML Name:
- CPE_QNVSBTSMPERM
- Deadline:
- 12 months after publication of Article 7 Guide
- Belongs to parameters group
-
ETCS National Values
(
1.1.1.3.2.16
|
1.2.1.1.1.16
)
- Data Format
-
- Data Presentation
-
Boolean
- Flags
-
- Applicability Flags:
- Y/N/NYA
- Validation
-
- Dependencies:
- A value has to be provided when ETCS is present (a value is provided on 1.1.1.3.2.1).
- Validation Rules:
-
Qnvsbtsmperm Applicability
Comment: Only applicable when selected value for 1.1.1.3.2.1 (ETCS present).
Message: qNvsbtsmperm (1.1.1.3.2.16.12, 1.2.1.1.1.16.12):The track or subset with common characteristics {$this} ({?label}), has an 'ETCS Level Type' defined which makes the qNvsbtsmperm parameter applicable. This error is due to {$this} not having a value for such a parameter.
-
Qnvsbtsmperm
Comment: Permission to use service brake in target speed monitoring.
Message: qNvsbtsmperm (1.1.1.3.2.16.12, 1.2.1.1.1.16.12): Each track or subset with common characteristics may define the Q_NVSBTSMPERM value. This error is due to having more than one value or having a value that is not Y/N (boolean).
- Additional Information
-
- General explanation:
- See: TSI CCS (Subset-026, chapter 7. 7.5.1.124 Q_NVSBTSMPERM)
National Values used for the brake model
DP
IRI: http://data.europa.eu/949/nationalValuesBrakeModel
- Parameter of
-
Running track
-
Subset with common characteristics
- General Information
-
- Number:
- 1.1.1.3.2.16.13
- 1.2.1.1.1.16.13
- XML Name:
- CPE_NVBRAKEMOD
- Deadline:
- 12 months after publication of Article 7 Guide
- Belongs to parameters group
-
ETCS National Values
(
1.1.1.3.2.16
|
1.2.1.1.1.16
)
- Data Format
-
- Data Presentation
-
String
- Flags
-
- Applicability Flags:
- Y/N/NYA
- Validation
-
- Dependencies:
- A value has to be provided when ETCS is present (a value is provided on 1.1.1.3.2.1).
- Validation Rules:
-
National Values Brake Model
Comment: Set of parameters for adapting the braking curves calculated by the ETCS on-board system to match accuracy, performance and safety margins imposed by the infrastructure manager.
Message: nationalValuesBrakeModel (1.1.1.3.2.16.13, 1.2.1.1.1.16.13): The track or subset with common characteristics has a National Value used for the brake model that must be a string and follow the format [±NNNN.NNN]. The error is due to having more than one value, having a vaalue that is not a string, or it is due to the value not following the pattern.
-
National Values Brake Model Applicability
Comment: Only applicable when selected value for 1.1.1.3.2.1 (ETCS present).
Message: nationalValuesBrakeModel (1.1.1.3.2.16.13, 1.2.1.1.1.16.13):The track or subset with common characteristics {$this} ({?label}), has an 'ETCS Level Type' defined which makes the nationalValuesBrakeModel parameter applicable. This error is due to {$this} not having a value for such a parameter.
- Additional Information
-
- General explanation:
- Non-harmonizable character string: [Contents of P3/P203] (TSI CCS, Annex I, Appendix A, Table A.2 - Subset-026)
ID of ERTMS/ETCS Radio Block Center
DP
IRI: http://data.europa.eu/949/rbcID
- Parameter of
-
Radio Block Center
- General Information
-
- Number:
- 1.1.1.3.2.17
- 1.2.1.1.1.17
- XML Name:
- CPE_IDRBC
- Deadline:
- 12 months after publication of Article 7 Guide
- Belongs to parameters group
-
TSI compliant train protection system (ETCS)
(
1.1.1.3.2
|
1.2.1.1.1
)
-
Identifier
- Data Format
-
- Data Presentation
-
String
- Format:
- NNNN NNNN with N a decimal number (0÷9)
- Flags
-
- Applicability Flags:
- Y/N/NYA
- Validation
-
- Validation Rules:
-
Rbc Id
Comment: Unique RBC identification (NID_C+NID_RBC) as defined in the specification referenced in TSI CCS.
Message: rbcID (1.1.1.3.2.17, 1.2.1.1.1.17): The radio block center id must be represented as a String and follow the pattern [NNNN NNNN].This error may be due to having a value that is not a string or that does not follow the pattern
- OPE TSI References
-
- Appendix D2 Index
- 3.4.7
Phone number of ERTMS/ETCS Radio Block Center
DP
IRI: http://data.europa.eu/949/rbcPhone
- Parameter of
-
Radio Block Center
- General Information
-
- Number:
- 1.1.1.3.2.17
- 1.2.1.1.1.17
- XML Name:
- CPE_PHONERBC
- Deadline:
- 12 months after publication of Article 7 Guide
- Belongs to parameters group
-
TSI compliant train protection system (ETCS)
(
1.1.1.3.2
|
1.2.1.1.1
)
- Data Format
-
- Data Presentation
-
String
- Format:
- NNNN NNNN NNNN NNNN with N a decimal number (0-9)
- Flags
-
- Applicability Flags:
- Validation
-
- Validation Rules:
-
Rbc Phone
Comment: Unique RBC calling number (NID_RADIO) as defined in the specification referenced in TSI CCS.
Message: rbcPhone (1.1.1.3.2.17, 1.2.1.1.1.17): The radio block center phone must be represented as a String and follow the pattern [NNNN NNNN NNNN NNNN].This error may be due to having a value that is not a string or that does not follow the pattern
- OPE TSI References
-
- Appendix D2 Index
- 3.4.7
GSM-R version
OP
IRI: http://data.europa.eu/949/gsmRVersion
- Parameter of
-
Running track
-
Subset with common characteristics
-
Vehicle Type
- General Information
-
- Number:
- 1.1.1.3.3.1
- 1.2.1.1.2.1
- XML Name:
- CRG_Version
- Deadline:
- In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
- 12 months after publication of Article 7 Guide for OP tracks
- Belongs to parameters group
-
TSI compliant radio (RMR)
(
1.1.1.3.3
|
1.2.1.1.2
)
-
Vehicle type technical characteristic
- Data Format
-
- Data Presentation
-
Concept
- Taxonomy Reference:
-
GSM-R Versions
-
Values :
-
| Code |
Value |
| 00 |
Baseline 0 |
| 10 |
None |
| 20 |
Previous version to Baseline 0 |
| 30 |
Baseline 0 r3 |
| 40 |
Baseline 0 r4 |
| 50 |
Baseline 1 |
- Flags
-
- Applicability Flags:
- Y/N/NYA
- Validation
-
- Dependencies:
- GSM-R must be installed for this parameter to be applicable and a value to be provided. If this property is not used, all GSM-R related properties should not be used either.
- Validation Rules:
-
Gsm Rversion
Comment: GSM-R functional requirements specification and system requirements specification in accordance with the specification respectively referenced in TSI CCS (Annex ), version number installed lineside.
Message: gsmRVersion (1.1.1.3.3.1, 1.2.1.1.2.1): The track or subset with common characteristics must have a GSM-R version value that is an IRI.
-
Gsm Rversion Skos
Comment: GSM-R functional requirements specification and system requirements specification in accordance with the specification respectively referenced in TSI CCS (Annex ), version number installed lineside.
Message: gsmRVersion (1.1.1.3.3.1, 1.2.1.1.2.1): The track or subset with common characteristics {$this} (label {?label}) has a value {?concept} that is not one of the predefined values and cannot be converted into a SKOS concept on this list: http://data.europa.eu/949/concepts/gsmr-versions/GSMRVersions.
- OPE TSI References
-
- Appendix D2 Index
- 3.1.7
- Additional Information
-
- General explanation:
- GSM-R functional requirements specification and system requirements specification in accordance with the specification respectively referenced in TSI CCS (Annex ), version number installed lineside.
Since more than one version may be installed in different areas, this property can have multiple values.
In case there is no GSM-R network available, this property shall be flagged as not applicable and all other GSM-R parameters ('Number of active GSM-R mobiles (EDOR) or simultaneous communication session on-board for ETCS Level 2 needed to perform radio block centre handovers without having an operational disruption' and 'Optional GSM-R functions') shall be flagged as not applicable.
Number of active GSM-R mobiles (EDOR) or simultaneous communication session on board for ETCS level 2 needed to perform radio block centre handovers without having an operational disruption
OP
IRI: http://data.europa.eu/949/gsmRActiveMobiles
- Parameter of
-
Running track
-
Subset with common characteristics
- General Information
-
- Number:
- 1.1.1.3.3.2
- 1.2.1.1.2.2
- XML Name:
- CRG_NumActiveMob
- Deadline:
- 12 months after publication of Article 7 Guide for OP tracks
- In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
- Belongs to parameters group
-
TSI compliant radio (RMR)
(
1.1.1.3.3
|
1.2.1.1.2
)
- Data Format
-
- Data Presentation
-
Concept
- Taxonomy Reference:
-
Number of active GSM-R mobiles
-
Values :
-
- Flags
-
- Applicability Flags:
- Y/N/NYA
- Validation
-
- Dependencies:
- GSM-R and ETCS level 2 must be installed for this parameter to be applicable.
- Validation Rules:
-
Gsm Ractive Mobiles
Comment: Number of simultaneous communication session on board for ETCS level 2 required for a smooth running of the train. This relates to the radio block centre (RBC) handling of communication sessions. Not safety critical and no matter of interoperability.
Message: gsmRActiveMobiles (1.1.1.3.3.2, 1.2.1.1.2.2): The track or subset with common characteristics must have a number of active GSM-R mobiles (EDOR) or simultaneous communication session on-board for ETCS Level 2 needed to perform radio block centre handovers without having an operational disruption value that is a single IRI. This error is due to having more than one value or having a value that is not an IRI.
-
Gsm Ractive Mobiles Skos
Comment: Number of simultaneous communication session on board for ETCS level 2 required for a smooth running of the train. This relates to the radio block centre (RBC) handling of communication sessions. Not safety critical and no matter of interoperability.
Message: gsmRActiveMobiles (1.1.1.3.3.2, 1.2.1.1.2.2): The track or subset with common characteristics {$this} (label {?label}) has a value {?concept} that is not one of the predefined values and cannot be converted into a SKOS concept on this list: http://data.europa.eu/949/concepts/gsmr-number-active-mobiles/NumberActiveMobiles.
-
Gsm Ractive Mobiles Applicability
Comment: GSM-R (parameter 1.1.1.3.3.1) and ETCS L2 (parameter 1.1.1.3.2.1) must be installed for this parameter to be applicable.
Message: gsmRActiveMobiles (1.1.1.3.3.2, 1.2.1.1.2.2):The track or subset with common characteristics {$this} ({?label}), has a 'GSM-R version' defined and a 'ETCS level' type selected which makes the gsmRActiveMobiles parameter applicable. This error is due to {$this} not having a value for such a parameter.
- Additional Information
-
- General explanation:
- In case there is no ETCS Level 2 in the line, do this parameter must be flagged as Not Applicable.
In case there is ETCS Level 2 in the line, the minimum number of EDOR required on board would be 1.
In case ETCS baseline 3 release 2 or baseline 4 is selected, select "2" .
Please select " 1" or "2" , taking into account that TSI compliant trains may only be fitted with 1 EDOR.
Optional GSM-R functions
OP
IRI: http://data.europa.eu/949/gsmROptionalFunctions
- Parameter of
-
Running track
-
Subset with common characteristics
- General Information
-
- Number:
- 1.1.1.3.3.3
- 1.2.1.1.2.3
- XML Name:
- CRG_OptionalFunctions
- Deadline:
- 12 months after publication of Article 7 Guide for OP tracks
- In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
- Belongs to parameters group
-
TSI compliant radio (RMR)
(
1.1.1.3.3
|
1.2.1.1.2
)
- Data Format
-
- Data Presentation
-
Concept
- Taxonomy Reference:
-
Optional GSM-R functions
-
Values :
-
| Code |
Value |
| 10 |
Network selection manual (*1) |
| 20 |
Network selection via balise (*1) |
| 30 |
Network selection automatic (*1) |
| 40 |
Public emergency (112) available (*2) |
| 50 |
Broadcast calls (VBS) used (*3) |
| 60 |
Text message service used (SMS) (*4) |
| 70 |
Restriction of display of called/calling user (*5) |
| 80 |
Automatically forward of incoming call if no reply (*5) |
| 90 |
Automatically forward of incoming call if not reachable (*5) |
| 100 |
Use of chargeable Network Services (*6) |
| 110 |
General data applications (*7) |
| 130 |
ETCS RBC or other devices alerted when initiating a REC (Railway Emergency Call) (*8) |
| 140 |
Display at the controller terminal of the location of the mobile initiating a REC (Railway Emergency Call) (*8) |
| 150 |
Use of enhanced Railway Emergency Call (eREC) (*8) |
| 160 |
GSM-R shunting used (*8) |
| 170 |
Data recorded in case of Shunting Emergency Call (*8) |
| 180 |
Extended frequency bands used (*9) |
| 200 |
Other |
- Flags
-
- Applicability Flags:
- Y/N/NYA
- Validation
-
- Dependencies:
- GSM-R (parameter 1.1.1.3.3.1) must be installed for this parameter to be applicable
- Validation Rules:
-
Gsm Roptional Functions Skos
Comment: Use of optional GSM-R functions which might improve operation on the line. They are for information only and not for network access criteria.
Message: gsmROptionalFunctions (1.1.1.3.3.2, 1.2.1.1.2.2): The track or subset with common characteristics {$this} (label {?label}) has a value {?concept} that is not one of the predefined values and cannot be converted into a SKOS concept on this list: http://data.europa.eu/949/concepts/gsmr-optional-functions/OptionalFunctions.
-
Gsm Roptional Functions
Comment: Use of optional GSM-R functions which might improve operation on the line. They are for information only and not for network access criteria.
Message: gsmROptionalFunctions (1.1.1.3.3.3, 1.2.1.1.2.3): The track or subset with common characteristics must have optional GSM-R functions value that is an IRI. This error is due to having a avalue that is not an IRI
-
Gsm Roptional Functions Applicability
Comment: GSM-R (parameter 1.1.1.3.3.1) must be installed for this parameter to be applicable.
Message: gsmROptionalFunctions (1.1.1.3.3.2, 1.2.1.1.2.2):The track or subset with common characteristics {$this} ({?label}), has a 'GSM-R version' defined which makes the gsmROptionalFunctions parameter applicable. This error is due to {$this} not having a value for such a parameter.
- Additional Information
-
- General explanation:
- (*1) These inputs refer to the expected behaviour by the network, i.e. if there is any area or point where an automatic selection of network should be done or if there is any location where balises to instruct a change of radio network have been installed.
In order to be able to attend to these indications (automatic network, network change by balise) some configuration is needed in the mobile.
In case there is a balise used to announce the change of the network, or if there are locations where the network selection is planned by the IM to be done automatically (and not manually, as stated in the requirements). It should be considered as an item that is related to the design of the infrastructure.
(*2) the possibility to dial 112 is something specific to the network that should be communicated to the vehicles accessing it.
(*3) the use of broadcast calls is something specific to the network that has to be configured in it.
(*4) it is something specific to the network that has to be configured in it if the service is provided.
(*5) it is something specific to the network that has to be configured in it if the service is provided; something may need to be configured on the network but also in the mobile subscriber data if it wants to use the service. What is requested here is the information of the network capability.
(*6) if they are configured on the network. Please indicate which in the "Other information" box.
(*7) To be selected if other data applications, different from ETCS L2, can be used within the network -
(*8) if it is configured on the network.
"GSM-R Shunting used" in order to make public if the GSM-R is used in the network for shunting activities.
(*9) Please specify in the "Other information" box for which services /applications are they planned and which are the frequencies in use.
(*11) Please use this field to indicate any additional information on network characteristics, e.g.; interference level, leading to the need of additional on-board protection;
Additional information on network characteristics
OP
IRI: http://data.europa.eu/949/gsmRAdditionalInfo
- Parameter of
-
Running track
-
Subset with common characteristics
- General Information
-
- Number:
- 1.1.1.3.3.3.1
- 1.2.1.1.2.3.1
- XML Name:
- CRG_AdditionalnetworkInfo
- Deadline:
- 1 January 2021
- 12 months after publication of Article 7 Guide for OP tracks
- Belongs to parameters group
-
TSI compliant radio (RMR)
(
1.1.1.3.3
|
1.2.1.1.2
)
- Data Format
-
- Data Presentation
-
ERA Document
- Flags
-
- Applicability Flags:
- Y/N/NYA
- Validation
-
- Dependencies:
- GSM-R must be installed for this parameter to be applicable
- Validation Rules:
-
Gsm Radditional Info Applicability
Comment: GSM-R (parameter 1.1.1.3.3.1) must be installed for this parameter to be applicable.
Message: gsmRAdditionalInfo (1.1.1.3.3.3.1, 1.2.1.1.2.3.1):The track or subset with common characteristics {$this} ({?label}), has a 'GSM-R version' defined which makes the gsmRAdditionalInfo parameter applicable. This error is due to {$this} not having a value for such a parameter.
-
Gsm Radditional Info
Comment: Any additional information on network characteristics or corresponding document available from the IM and stored by the Agency, e.g.; interference level, leading to the recommendation of additional on-board protection.
Message: gsmRAdditionalInfo (1.1.1.3.3.3.1): The track or subset with common characteristics defines an additional information on network characteristics value that must be a Document.
- Additional Information
-
- General explanation:
- Please use this field to indicate any additional information on the GSM-R network.
The value of this parameter should be either a reference to a file name or an external link to a document.
If a file name is provided, the Infrastructure Manager (IM) must upload a document with the same file name using the "Reference Documents Management" functionality in the RINF application. The document must be in electronic format and available in two official EU languages. In this case, the parameter value must be repeated for each document.
If an external link is provided, the IM must ensure that the document is available at the provided link.
GPRS for ETCS
DP
IRI: http://data.europa.eu/949/gprsForETCS
- Parameter of
-
Running track
-
Subset with common characteristics
- General Information
-
- Number:
- 1.1.1.3.3.3.2
- 1.2.1.1.2.3.2
- XML Name:
- CRG_GPRSForETCS
- Deadline:
- 1 January 2021
- 12 months after publication of Article 7 Guide for OP tracks
- Belongs to parameters group
-
TSI compliant radio (RMR)
(
1.1.1.3.3
|
1.2.1.1.2
)
- Data Format
-
- Data Presentation
-
Boolean
- Flags
-
- Applicability Flags:
- Y/N/NYA
- Validation
-
- Dependencies:
- GSM-R and ETCS L2 must be installed for this parameter to be applicable.
- Validation Rules:
-
Gprs For Etcs
Comment: Indication if GPRS can be used for ETCS.
Message: gprsForETCS (1.1.1.3.3.3.2, 1.2.1.1.2.3.2): Each track or subset with common characteristics may define the existence of GPRS for ETCS. This error is due to having more than one value or having a value that is not Y/N (boolean).
-
Gprs For Etcsapplicability
Comment: GSM-R (parameter 1.1.1.3.3.1) and ETCS L2 (parameter 1.1.1.3.2.1) must be installed for this parameter to be applicable.
Message: gprsForETCS (1.1.1.3.3.3.2, 1.2.1.1.2.3.2):The track or subset with common characteristics {$this} ({?label}), has a 'GSM-R version' defined and a 'ETCS level' type selected which makes the gprsForETCS parameter applicable. This error is due to {$this} not having a value for such a parameter.
- Additional Information
-
- General explanation:
- Sections of EIRENE and ETCS subsets for trackside in TSI
Area of implementation of GPRS
DP
IRI: http://data.europa.eu/949/gprsImplementationArea
- Parameter of
-
Running track
-
Subset with common characteristics
- General Information
-
- Number:
- 1.1.1.3.3.3.3
- 1.2.1.1.2.3.3
- XML Name:
- CRG_GPRSAreaOfImpl
- Deadline:
- 1 January 2021
- 12 months after publication of Article 7 Guide for OP tracks
- Belongs to parameters group
-
TSI compliant radio (RMR)
(
1.1.1.3.3
|
1.2.1.1.2
)
- Data Format
-
- Data Presentation
-
String
- Flags
-
- Applicability Flags:
- Y/N/NYA
- Validation
-
- Dependencies:
- GSM-R, ETCS L2 and GPRS for ETCS must be installed for this parameter to be applicable.
- Validation Rules:
-
Gprs Implementation Area Applicability
Comment: GSM-R (parameter 1.1.1.3.3.1), ETCS L2 (parameter 1.1.1.3.2.1) and GPRS for ETCS (parameter 1.1.1.3.3.3.2) must be installed for this parameter to be applicable.
Message: gprsImplementationArea (1.1.1.3.3.3.3, 1.2.1.1.2.3.3):The track or subset with common characteristics {$this} ({?label}), has a 'GSM-R version' defined and a 'ETCS level' type selected which makes the gprsImplementationArea parameter applicable. This error is due to {$this} not having a value for such a parameter.
-
Gprs Implementation Area
Comment: Indication of the area in which GPRS can be used for ETCS.
Message: gprsImplementationArea (1.1.1.3.3.3.3): The track or subset with common characteristics defines the area in which GPRS can be used for ETCS value that must be a string. This error may be due to the track having a value that is not a string.
- Additional Information
-
- General explanation:
- Since GPRS can be used for ETCS, indicate in which areas it is implemented (e.g.: whole section, only between two signals, at the station…)
GSM-R use of group 555
DP
IRI: http://data.europa.eu/949/usesGroup555
- Parameter of
-
Running track
-
Subset with common characteristics
- General Information
-
- Number:
- 1.1.1.3.3.4
- 1.2.1.1.2.4
- XML Name:
- CRG_Needof555
- Deadline:
- 12 months after publication of Article 7 Guide for OP tracks
- 16 January 2020
- Belongs to parameters group
-
TSI compliant radio (RMR)
(
1.1.1.3.3
|
1.2.1.1.2
)
- Data Format
-
- Data Presentation
-
Boolean
- Flags
-
- Applicability Flags:
- Y/N/NYA
- Validation
-
- Dependencies:
- GSM-R and ETCS L2 must be installed for this parameter to be applicable.
- Validation Rules:
-
Uses Group555
Comment: Indication if group 555 is used.
Message: usesGroup555 (1.1.1.3.3.4, 1.2.1.1.2.4): Each track or subset with common characteristics may define the existence of GSM-R use of group 555. This error is due to having more than one value or having a value that is not Y/N (boolean).
-
Uses Group555applicability
Comment: GSM-R (parameter 1.1.1.3.3.1) and ETCS L2 (parameter 1.1.1.3.2.1) must be installed for this parameter to be applicable.
Message: usesGroup555 (1.1.1.3.3.4, 1.2.1.1.2.4):The track or subset with common characteristics {$this} ({?label}), has a 'GSM-R version' defined and a 'ETCS level' type selected which makes the usesGroup555 parameter applicable. This error is due to {$this} not having a value for such a parameter.
- OPE TSI References
-
- Part of RCC Algorithm:
- true
- Additional Information
-
- General explanation:
- Sections of EIRENE not covered by references in TSI. GSM-R (parameter 1.1.1.3.3.1) and ETCS L2 (parameter 1.1.1.3.2.1) must be installed for this parameter to be applicable.
GSM-R networks covered by a roaming agreement
OP
IRI: http://data.europa.eu/949/gsmrNetworkCoverage
- Parameter of
-
Running track
-
Subset with common characteristics
- General Information
-
- Number:
- 1.1.1.3.3.5
- 1.2.1.1.2.5
- XML Name:
- CRG_RoamingAgreement
- Deadline:
- 12 months after publication of Article 7 Guide for OP tracks
- 16 January 2020
- Belongs to parameters group
-
TSI compliant radio (RMR)
(
1.1.1.3.3
|
1.2.1.1.2
)
- Data Format
-
- Data Presentation
-
Concept
- Taxonomy Reference:
-
GSM-R Networks
-
Values :
-
| Code |
Value |
| 10 |
GSM-R A (Austria) |
| 20 |
GSM-R AL (Albania) |
| 30 |
GSM-R B (Belgium) |
| 40 |
GSM-R BA (Bosnia Herzegovina) |
| 50 |
GSM-R BG (Bulgaria) |
| 60 |
GSM-R BY (Belarus) |
| 70 |
GSM-R CH (Switzerland) |
| 80 |
GSM-R CZ (Czech Rep.) |
| 90 |
GSM-R D (Germany) |
| 100 |
GSM-R DK (Denmark) |
| 110 |
GSM-R E (Spain) |
| 120 |
GSM-R EE (Estonia) |
| 130 |
GSM-R F (France) |
| 140 |
GSM-R FI (Finland) |
| 150 |
GSM-R GB (UK (Great Britain)) |
| 160 |
GSM-R GR (Greece) |
| 170 |
GSM-R HR (Croatia) |
| 180 |
GSM-R HU (Hungary) |
| 190 |
GSM-R I (Italy) |
| 200 |
GSM-R IE (Ireland) |
| 210 |
GSM-R IS (Iceland) |
| 220 |
GSM-R KO (Kosovo) |
| 230 |
GSM-R L (Luxembourg) |
| 240 |
GSM-R LT (Lithuania) |
| 250 |
GSM-R LV (Latvia) |
| 260 |
GSM-R MD (Moldova) |
| 270 |
GSM-R ME (Montenegro) |
| 280 |
GSM-R MK (Macedonia) |
| 290 |
GSM-R N (Norway) |
| 300 |
GSM-R NL (Netherlands) |
| 310 |
GSM-R P (Portugal) |
| 320 |
GSM-R PL (Poland) |
| 330 |
GSM-R RO (Romania) |
| 340 |
GSM-R RU (Russia) |
| 350 |
GSM-R S (Sweden) |
| 360 |
GSM-R SI (Slovenia) |
| 370 |
GSM-R SK (Slovakia) |
| 380 |
GSM-R SR (Serbia ) |
| 390 |
GSM-R TR (Turkey) |
| 400 |
GSM-R UA (Ukraine) |
- Flags
-
- Applicability Flags:
- Y/N/NYA
- Validation
-
- Dependencies:
- GSM-R must be installed for this parameter to be applicable
- Validation Rules:
-
Gsmr Network Coverage Applicability
Comment: GSM-R (parameter 1.1.1.3.3.1) must be installed for this parameter to be applicable.
Message: gsmrNetworkCoverage (1.1.1.3.3.5, 1.2.1.1.2.5):The track or subset with common characteristics {$this} ({?label}), has a 'GSM-R version' defined which makes the gsmrNetworkCoverage parameter applicable. This error is due to {$this} not having a value for such a parameter.
-
Gsmr Network Coverage
Comment: List of GSM-R networks which are covered by a roaming agreement.
Message: gsmrNetworkCoverage (1.1.1.3.3.5, 1.2.1.1.2.5): The track or subset with common characteristics must have a GSM-R networks covered by a roaming agreement value that is an IRI.
-
Gsmr Network Coverage Skos
Comment: List of GSM-R networks which are covered by a roaming agreement.
Message: gsmrNetworkCoverage (1.1.1.3.3.5, 1.2.1.1.2.5): The track or subset with common characteristics {$this} (label {?label}) has a value {?concept} that is not one of the predefined values and cannot be converted into a SKOS concept on this list: http://data.europa.eu/949/concepts/gsmr-networks/GSMRNetworks.
- OPE TSI References
-
- Part of RCC Algorithm:
- true
- Additional Information
-
- General explanation:
- Name of the own GSM-R network and list of GSM-R networks which are covered by a roaming agreement for CS services.
This list is managed by UIC. The Agency will monitor it in order to update the list of possible values when necessary.
For Route Compatibility purposes and simplicity, the own network needs to be declared by the IM, so the RUs can systematically check the compatibility.
For voice services, roaming for CS is applicable. For ETCS, as long as roaming for CS is ensured, the interoperability will be guaranteed.
Existence of GSM-R roaming to public networks
DP
IRI: http://data.europa.eu/949/publicNetworkRoaming
- Parameter of
-
Running track
-
Subset with common characteristics
- General Information
-
- Number:
- 1.1.1.3.3.6
- 1.2.1.1.2.6
- XML Name:
- CRG_RoamingPublic
- Deadline:
- 12 months after publication of Article 7 Guide for OP tracks
- 1 January 2021
- Belongs to parameters group
-
TSI compliant radio (RMR)
(
1.1.1.3.3
|
1.2.1.1.2
)
- Data Format
-
- Data Presentation
-
Boolean
- Flags
-
- Applicability Flags:
- Y/N/NYA
- Validation
-
- Dependencies:
- GSM-R must be installed for this parameter to be applicable
- Validation Rules:
-
Public Network Roaming
Comment: Existence of roaming to a public network.
Message: publicNetworkRoaming (1.1.1.3.3.6, 1.2.1.1.2.6): Each track or subset with common characteristics may define the existence of GSM-R roaming to public networks. This error is due to having more than one value or having a value that is not Y/N (boolean).
-
Public Network Roaming Applicability
Comment: GSM-R (parameter 1.1.1.3.3.1) must be installed for this parameter to be applicable.
Message: publicNetworkRoaming (1.1.1.3.3.6, 1.2.1.1.2.6):The track or subset with common characteristics {$this} ({?label}), has a 'GSM-R version' defined which makes the publicNetworkRoaming parameter applicable. This error is due to {$this} not having a value for such a parameter.
- Additional Information
-
- General explanation:
- Sections of EIRENE not covered by references in TSI.
Details on GSM-R roaming to public networks
DP
IRI: http://data.europa.eu/949/publicNetworkRoamingDetails
- Parameter of
-
Running track
-
Subset with common characteristics
- General Information
-
- Number:
- 1.1.1.3.3.7
- 1.2.1.1.2.7
- XML Name:
- CRG_RoamingPublicDetails
- Deadline:
- 1 January 2021
- 12 months after publication of Article 7 Guide for OP tracks
- Belongs to parameters group
-
TSI compliant radio (RMR)
(
1.1.1.3.3
|
1.2.1.1.2
)
- Data Format
-
- Data Presentation
-
String
- Flags
-
- Applicability Flags:
- Y/N/NYA
- Validation
-
- Dependencies:
- Mandatory if GSM-R is installed and era:publicNetworkRoaming is 'true'. Otherwise, it is not applicable.
- Validation Rules:
-
Public Network Roaming Details Applicability
Comment: GSM-R (parameter 1.1.1.3.3.1) must be installed for this parameter to be applicable.
Message: publicNetworkRoamingDetails (1.1.1.3.3.7, 1.2.1.1.2.7):The track or subset with common characteristics {$this} ({?label}), has a 'GSM-R version' defined which makes the publicNetworkRoamingDetails parameter applicable. This error is due to {$this} not having a value for such a parameter.
-
Public Network Roaming Details
Comment: If roaming to public networks is configured, please:
1. indicate to which networks, for which users and in which areas.
2. list if any GSM-R functionality is not available when roaming to a public network (e.g. REC, Functional Addressing, Group Calls).
3. also add if there is any operational restriction for vehicles that cannot roam into any of the available public networks.
Message: publicNetworkRoamingDetails (1.1.1.3.3.7, 1.2.1.1.2.7): Each track or subset with common characteristics may have details on GSM-R roaming to public networks that is a character string. This error is due to having more than one publicNetworkRoamingDetails value or having a value that is not a string.
- Additional Information
-
- General explanation:
- List if any GSM-R functionality is not available when roaming to a public network (e.g. REC, Functional Addressing, Group Calls).
Please also add if there is any operational restriction for vehicles that cannot roam into any of the available public networks.
No GSMR coverage
DP
IRI: http://data.europa.eu/949/gsmRNoCoverage
- Parameter of
-
Running track
-
Subset with common characteristics
- General Information
-
- Number:
- 1.1.1.3.3.8
- 1.2.1.1.2.8
- XML Name:
- CRG_GSMRNoCoverage
- Deadline:
- 1 January 2021
- 12 months after publication of Article 7 Guide for OP tracks
- Belongs to parameters group
-
TSI compliant radio (RMR)
(
1.1.1.3.3
|
1.2.1.1.2
)
- Data Format
-
- Data Presentation
-
Boolean
- Flags
-
- Applicability Flags:
- Y/N/NYA
- Validation
-
- Dependencies:
- GSM-R must be installed for this parameter to be applicable
- GSM-R (parameter 1.1.1.3.3.1) must be installed for this parameter to be applicable.
- Validation Rules:
-
Gsm Rno Coverage
Comment: Indication if there is no GSMR coverage.
Message: gsmRNoCoverage (1.1.1.3.3.8, 1.2.1.1.2.8): Each track or subset with common characteristics may define the indication of existence of GSMR coverage. This error is due to having more than one value or having a value that is not Y/N (boolean).
-
Gsm Rno Coverage Applicability
Comment: GSM-R (parameter 1.1.1.3.3.1) must be installed for this parameter to be applicable.
Message: gsmRNoCoverage (1.1.1.3.3.8, 1.2.1.1.2.8):The track or subset with common characteristics {$this} ({?label}), has a 'GSM-R version' defined which makes the gsmRNoCoverage parameter applicable. This error is due to {$this} not having a value for such a parameter.
- Additional Information
-
- General explanation:
- If GSM-R is not installed, this parameter should not be used.
This parameter is mainly to capture the case of Radio Hole functionality (lack of GSM-R coverage), that is foreseen in the ETCS specifications as packet 68.
Another possible use is the declaration of a temporary situation where, although the area is in principle covered by GSM-R, there is a long-term outage or a project for replacement of the radio (i.e. a section that will not be covered with GSM-R for half a year or longer).
Radio system compatibility voice
OP
IRI: http://data.europa.eu/949/voiceRadioCompatible
- Parameter of
-
Running track
-
Subset with common characteristics
-
Vehicle Type
- General Information
-
- Number:
- 1.1.1.3.3.9
- 1.2.1.1.2.9
- XML Name:
- CRG_RadioCompVoice
- Deadline:
- 12 months after publication of Article 7 Guide for OP tracks
- 16 January 2020
- Belongs to parameters group
-
TSI compliant radio (RMR)
(
1.1.1.3.3
|
1.2.1.1.2
)
-
Vehicle type technical characteristic
- Data Format
-
- Data Presentation
-
Concept
- Taxonomy Reference:
-
Radio System Compatibilities Voice
-
Values :
-
| Code |
Value |
| 10 |
Not Defined |
| 20 |
RSC-EU-0 |
| 30 |
RSC-ES-01-V |
| 40 |
RSC-ES-02-V |
| 50 |
RSC-ES-03-V |
| 60 |
RSC-ES-04-V |
| 70 |
RSC-SE-01-V |
| 80 |
RSC-FR-01-V |
| 100 |
RSC-AT-01-V |
| 110 |
RSC-BE-01-V |
| 120 |
RSC-RO-01-V |
| 130 |
RSC-ES-05-V |
| 140 |
RSC-DE-01-V |
| 150 |
RSC-LU-01-V |
| 160 |
RSC-CH-01-V |
| 170 |
RSC-PT-01-V |
| 171 |
RSC-PT-02-V |
| 180 |
RSC-PT-02-V |
- Flags
-
- Applicability Flags:
- Y/N/NYA
- Validation
-
- Dependencies:
- GSM-R must be installed for this parameter to be applicable.
In case of RSC-EU-0 or None, no other values are allowed.
- Validation Rules:
-
Voice Radio Compatible Skos
Comment: Radio requirements used for demonstrating technical compatibility voice.
Message: voiceRadioCompatible (1.1.1.3.3.9, 1.2.1.1.2.9): The track or subset with common characteristics {$this} (label {?label}) has a value {?concept} that is not one of the predefined values and cannot be converted into a SKOS concept on this list: http://data.europa.eu/949/concepts/radio-system-compatibilities-voice/RadioSystemCompatibilitiesVoice.
-
Voice Radio Compatible
Comment: Radio requirements used for demonstrating technical compatibility voice.
Message: voiceRadioCompatible (1.1.1.3.3.9, 1.2.1.1.2.9): The track or subset with common characteristics may have a radio system compatibility voice value that is an IRI. This error is due to having a value that is not an IRI.
-
Voice Radio Compatible Applicability
Comment: GSM-R (parameter 1.1.1.3.3.1) must be installed for this parameter to be applicable.
Message: voiceRadioCompatible (1.1.1.3.3.9, 1.2.1.1.2.9):The track or subset with common characteristics {$this} ({?label}), has a 'GSM-R version' defined which makes the voiceRadioCompatible parameter applicable. This error is due to {$this} not having a value for such a parameter.
- Additional Information
-
- General explanation:
- Information on RSC voice requirements per country is given in the referred document.
Vehicles are considered compatible with the infrastructure regarding this parameter, if any of the values declared matches.
In case the value “Not Defined” or “RSC-EU-0” is used, repetitions with additional values are not expected.
Radio system compatibility data
OP
IRI: http://data.europa.eu/949/dataRadioCompatible
- Parameter of
-
Running track
-
Subset with common characteristics
-
Vehicle Type
- General Information
-
- Number:
- 1.1.1.3.3.10
- 1.2.1.1.2.10
- XML Name:
- CRG_RadioCompData
- Deadline:
- 12 months after publication of Article 7 Guide for OP tracks
- 16 January 2020
- Belongs to parameters group
-
TSI compliant radio (RMR)
(
1.1.1.3.3
|
1.2.1.1.2
)
-
Vehicle type technical characteristic
- Data Format
-
- Data Presentation
-
Concept
- Taxonomy Reference:
-
Radio System Compatibilities Data
-
Values :
-
| Code |
Value |
| 10 |
Not Defined |
| 20 |
RSC-EU-0 |
| 30 |
RSC-ES-01-D |
| 40 |
RSC-ES-02-D |
| 50 |
RSC-ES-03-D |
| 60 |
RSC-ES-04-D |
| 61 |
RSC-ES-04.LAXAVA-D |
| 62 |
RSC-ES-04.ORESAN-D |
| 63 |
RSC-ES-04.ARAVIL-D |
| 64 |
RSC-ES-04.GENERAL-D |
| 70 |
RSC-SE-01-D |
| 80 |
RSC-FR-01-D |
| 90 |
RSC-AT-01-D |
| 100 |
RSC-PL-01-D |
| 110 |
RSC-ES-05-D |
| 111 |
RSC-ES-05.LEOPOL-D |
| 112 |
RSC-ES-05.PEDORE-D |
| 113 |
RSC-ES-05.GENERAL-D |
| 114 |
RSC-ES-03.GENERAL-D |
| 115 |
RSC-ES-03.SPECIFIC-D |
| 116 |
RSC-ES-04.GENERAL-D |
| 117 |
RSC-ES-05.GENERAL-D |
| 160 |
RSC-CH-01-D |
| 501 |
RSC-ES-03.ALBALI-D |
| 502 |
RSC-ES-03.ANTGRA-D |
| 503 |
RSC-ES-03.CHATO-D |
| 504 |
RSC-ES-03.BAFI-D |
| 505 |
RSC-ES-03.CORMAL-D |
| 506 |
RSC-ES-03.SAGTOL-D |
| 507 |
RSC-ES-03.MADBCN-D |
| 508 |
RSC-ES-03.MADVLL-D |
| 509 |
RSC-ES-03.MONMUR-D |
| 510 |
RSC-ES-03.MOTVLCALB-D |
| 511 |
RSC-ES-03.OLMPED-D |
| 512 |
RSC-ES-05.PLACACBAD-D |
| 513 |
RSC-ES-03.TORMOT-D |
| 514 |
RSC-ES-03.VALLEOBUR-D |
| 515 |
RSC-ES-03.VILTAR-D |
| 516 |
RSC-ES-05.HOSMAT-D |
| 517 |
RSC-ES-03.GENERAL-D |
| 518 |
RSC-ES-03.SPECIFIC-D |
- Flags
-
- Applicability Flags:
- Y/N/NYA
- Validation
-
- Dependencies:
- GSM-R and ETCS L2 must be installed for this parameter to be applicable.
- Validation Rules:
-
Data Radio Compatible Applicability
Comment: GSM-R (parameter 1.1.1.3.3.1) and ETCS L2 (parameter 1.1.1.3.2.1) must be installed for this parameter to be applicable.
Message: dataRadioCompatible (1.1.1.3.3.10, 1.2.1.1.2.10):The track or subset with common characteristics {$this} ({?label}), has a 'GSM-R version' defined and a 'ETCS level' type selected which makes the dataRadioCompatible parameter applicable. This error is due to {$this} not having a value for such a parameter.
-
Data Radio Compatible Skos
Comment: Radio requirements used for demonstrating technical compatibility data.
Message: dataRadioCompatible (1.1.1.3.3.10, 1.2.1.1.2.10): The track or subset with common characteristics {$this} (label {?label}) has a value {?concept} that is not one of the predefined values and cannot be converted into a SKOS concept on this list: http://data.europa.eu/949/concepts/radio-system-compatibilities-data/RadioSystemCompatibilitiesData.
-
Data Radio Compatible
Comment: Radio requirements used for demonstrating technical compatibility data.
Message: dataRadioCompatible (1.1.1.3.3.10, 1.2.1.1.2.10): The track or subset with common characteristics may have a radio system compatibility data value that is an IRI. This error is due to having a value that is not an IRI.
- Additional Information
-
- General explanation:
- Information on RSC data requirements per country.
Vehicles are considered compatible with the infrastructure regarding this parameter, if any of the values declared matches.
In case the value “Not Defined” or “RSC-EU-0” is used, repetitions with additional values are not expected.
GSM-R network is configured to allow forced de-registration of a functional number by another driver
DP
IRI: http://data.europa.eu/949/gsmrForcedDeregistrationFunctionalNumber
- Parameter of
-
Running track
-
Subset with common characteristics
- General Information
-
- Number:
- 1.1.1.3.3.11
- 1.2.1.1.2.11
- XML Name:
- CRG_ForcedDeReg
- Deadline:
- 12 months after publication of Article 7 Guide
- Belongs to parameters group
-
TSI compliant radio (RMR)
(
1.1.1.3.3
|
1.2.1.1.2
)
- Data Format
-
- Data Presentation
-
Boolean
- Flags
-
- Applicability Flags:
- Y/N/NYA
- Validation
-
- Dependencies:
- GSM-R and ETCS L2 must be installed for this parameter to be applicable.
- Validation Rules:
-
Gsmr Forced Deregistration Functional Number
Comment: This feature will determine the applicable operational rules for drivers and signallers when dealing with cab radios registered under wrong numbers.
Message: gsmrForcedDeregistrationFunctionalNumber (1.1.1.3.3.11, 1.2.1.1.2.11): Each track or subset with common characteristics may define the existence of GSM-R network configured to allow forced de-registration of a functional number by another driver. This error is due to having more than one value or having a value that is not Y/N (boolean).
-
Gsmr Forced Deregistration Functional Number Applicability
Comment: GSM-R (parameter 1.1.1.3.3.1) and ETCS L2 (parameter 1.1.1.3.2.1) must be installed for this parameter to be applicable.
Message: gsmrForcedDeregistrationFunctionalNumber (1.1.1.3.3.11, 1.2.1.1.2.11):The track or subset with common characteristics {$this} ({?label}), has a 'GSM-R version' defined and a 'ETCS level' type selected which makes the gsmrForcedDeregistrationFunctionalNumber parameter applicable. This error is due to {$this} not having a value for such a parameter.
- Additional Information
-
- General explanation:
- See documents regarding Operational Harmonisation ETCS.
Radio Network ID
DP
IRI: http://data.europa.eu/949/radioNetworkId
- Parameter of
-
Running track
-
Subset with common characteristics
- General Information
-
- Number:
- 1.1.1.3.3.12
- 1.2.1.1.2.13
- XML Name:
- CRG_RadioNID
- Deadline:
- 12 months after publication of Article 7 Guide
- Belongs to parameters group
-
TSI compliant radio (RMR)
(
1.1.1.3.3
|
1.2.1.1.2
)
- Data Format
-
- Data Presentation
-
String
- Format:
- NNNNNN with N a decimal number (0 9).
- Flags
-
- Applicability Flags:
- Y/N/NYA
- Validation
-
- Dependencies:
- GSM-R must be installed for this parameter to be applicable.
- Validation Rules:
-
Radio Network Id
Comment: Unique identification of the GSM-R network the calling mobile station has to register with, as defined in the specification referenced in TSI CCS.
Message: radioNetworkId (1.1.1.3.3.12, 1.2.1.1.2.13): The track or subset with common characteristics has a Radio Network ID that must be a string and follow the format [NNNNNN]. The error is due to the value not being a string or not following the pattern.
-
Radio Network Id Applicability
Comment: GSM-R (parameter 1.1.1.3.3.1) must be installed for this parameter to be applicable.
Message: radioNetworkId (1.1.1.3.3.12, 1.2.1.1.2.13):The track or subset with common characteristics {$this} ({?label}), has a 'GSM-R version' defined which makes the radioNetworkId parameter applicable. This error is due to {$this} not having a value for such a parameter.
- OPE TSI References
-
- Appendix D2 Index
- 3.4.4
- Additional Information
-
- General explanation:
- According to the specification referenced in TSI CCS.
Existence of train detection system fully compliant with the TSI
DP
IRI: http://data.europa.eu/949/hasTSITrainDetection
- Parameter of
-
Running track
-
Subset with common characteristics
- General Information
-
- Number:
- 1.1.1.3.4.1
- 1.2.1.1.3.1
- XML Name:
- CCD_TSITrainDetection
- Deadline:
- 12 months after publication of Article 7 Guide for OP tracks
- In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
- Belongs to parameters group
-
Train detection systems defined based on frequency bands
(
1.1.1.3.4
|
1.2.1.1.3
)
- Data Format
-
- Data Presentation
-
Boolean
- Flags
-
- Applicability Flags:
- Y/N/NYA
- Validation
-
- Validation Rules:
-
Has Tsitrain Detection
Comment: Indication if there is any train detection system installed and fully compliant with the TSI CCS (Annex I, Appendix A, Table A.2 -Index 77).
Message: hasTSITrainDetection (1.1.1.3.4.1, 1.2.1.1.3.1): Each track or subset with common characteristics may define the existence of train detection system fully compliant with the TSI. This error is due to having more than one value or having a value that is not Y/N (boolean).
- Additional Information
-
- General explanation:
- Verification of compliance with TSI includes application of notified national rules (when they exist).
See: (Annex I, Appendix A, Table A.2 -Index 77).
Frequency bands for detection
OP
IRI: http://data.europa.eu/949/frequencyBandsForDetection
- Parameter of
-
Train Detection System
- General Information
-
- Number:
- 1.1.1.3.4.2
- 1.2.1.1.3.2
- XML Name:
- CCD_TSIFreqBandsDet
- Deadline:
- 12 months after publication of Article 7 Guide
- Belongs to parameters group
-
Train detection systems defined based on frequency bands
(
1.1.1.3.4
|
1.2.1.1.3
)
- Data Format
-
- Data Presentation
-
Concept
- Taxonomy Reference:
-
Frequency bands for detection, one collection for axle counters, one for track circuits.
-
Values :
-
| Code |
Value |
| A0_TC |
DC-operated Track Circuits |
| A1_AC |
Band A1 for Axle Counters |
| A1_TC |
Band A1 for Track Circuits |
| A2_AC |
Band A2 for Axle Counters |
| A2_TC |
Band A2 for Track Circuits |
| A3_AC |
Band A3 for Axle Counters |
| A3_TC |
Band A3 for Track Circuits |
| A4_TC |
Band A4 for Track Circuits |
| A5_TC |
Band A5 for Track Circuits |
| A6_TC |
Band A6 for Track Circuits |
| A7_TC |
Band A7 for Track Circuits |
| A8_TC |
Band A8 for Track Circuits |
- Flags
-
- Applicability Flags:
- Y/N/NYA
- Validation
-
- Validation Rules:
-
Frequency Bands For Detection
Comment: Bands of the frequency management of the train detection systems as defined in the TSI CCS (Annex I, Appendix A, Table A.2 -Index 77), and in the specific cases or technical documents referred to in Article 13 of TSI CCS when they are available.
Message: frequencyBandsForDetection (1.1.1.3.4.2.1, 1.2.1.1.3.2): The train detection system has a frequency band for detection that must be an IRI. This error may be due to having more than one value or having a value that is not a Document.
-
Frequency Bands For Detection Skos
Comment: Indication of the frequency band for detection of the train detection system
Message: Indication of the frequency band for detection of the train detection system (1.1.1.3.4.2, 1.2.1.1.3.2): The train detection system {$this} has a value {?concept} that is not one of the predefined values and cannot be converted into a SKOS concept on this list: http://data.europa.eu/949/concepts/train-detection/FrequencyBandsForDetection.
- Additional Information
-
- General explanation:
- Verification of compliance with TSI includes application of notified national rules (when they exist).
Multiple selection from a predefined list:
- Axle Counters: bands A1-A3
- Track circuits: bands A1-A8
Evaluation parameters if maximum interference current is not measured in the preferred bands
DP
IRI: http://data.europa.eu/949/maximumInterferenceCurrentEvaluation
- Parameter of
-
Train Detection System
- General Information
-
- Number:
- 1.1.1.3.4.2.1
- 1.2.1.1.3.2.1
- XML Name:
- CCD_IInterferenceMax
- Belongs to parameters group
-
Train detection systems defined based on frequency bands
(
1.1.1.3.4
|
1.2.1.1.3
)
- Data Format
-
- Data Presentation
-
String
- Validation
-
- Dependencies:
- If the preferred frequency bands are not used, (mandatory) description of the parameters for evaluation of compliance.
If the preferred frequency bands are used, this parameter is optional.
- Validation Rules:
-
Maximum Interference Current Evaluation
Comment: If the preferred frequency bands are not used, (mandatory) description of the parameters for evaluation of compliance. If the preferred frequency bands are used, this parameter is optional.
Message: maximumInterferenceCurrentEvaluation (1.1.1.3.4.2.1, 1.2.1.1.3.2.1): Each TrainDetectionSystem may have a single value for maximumInterferenceCurrentEvaluation that is a character string. This error is due to having more than one maximumInterferenceCurrentEvaluation value or having a value that is not a string.
Maximum interference current
DP
IRI: http://data.europa.eu/949/maximumInterferenceCurrent
- Parameter of
-
Train Detection System
- General Information
-
- Number:
- 1.1.1.3.4.2.1
- 1.2.1.1.3.2.1
- XML Name:
- CCD_IInterferenceMax
- Deadline:
- For train detection system compliant with TSIs: 12 months after publication of Article 7 Guide.
For train detection system not TSI compliant: in relation to article 13 of TSI CCS
- Belongs to parameters group
-
Train detection systems defined based on frequency bands
(
1.1.1.3.4
|
1.2.1.1.3
)
- Data Format
-
- Data Presentation
-
Double
- Format:
- NNN. An optional value could be filled in era:maximumInterferenceCurrentEvaluation
- Unit of Measure:
-
Ampere per metre
- Flags
-
- Applicability Flags:
- Y/N/NYA
- Validation
-
- Dependencies:
- Evaluation parameters must be added if preferred bands are not used.
- Validation Rules:
-
Maximum Interference Current
Comment: Maximum interference current limits allowed for track circuits for a defined frequency band (to be expressed in A/m).
Message: maximumInterferenceCurrent (1.1.1.3.4.2.1, 1.2.1.1.3.2.1): Each train detection system must define the maximum interference current in Amperes. This error may be due to having more than one value or having a value that is not a double (real) number.
- Additional Information
-
- General explanation:
- To be expressed in A/m. Verification of compliance with TSI includes application of notified national rules (when they exist).
Evaluation parameters must be added if preferred bands are not used.
Vehicle impedance
OP
IRI: http://data.europa.eu/949/minVehicleImpedance
- Parameter of
-
Train Detection System
- General Information
-
- Number:
- 1.1.1.3.4.2.2
- 1.2.1.1.3.2.2
- XML Name:
- CCD_TCVehicleImpedance
- Deadline:
- For train detection system compliant with TSIs, 12 months after publication of Article 7 Guide.
For train detection system not TSI compliant: in relation to article 13 of TSI CCS
- 12 months after publication of Article 7 Guide for OP tracks
- Belongs to parameters group
-
Train detection systems defined based on frequency bands
(
1.1.1.3.4
|
1.2.1.1.3
)
- Data Format
-
- Data Presentation
-
Minimum Vehicle Impedance
- Format:
- The values is an instance of era:MinVehicleImpedance class with its 2 properties. Per voltage : input Capacitance (Cin) and Input Impedance (Zin)
- Flags
-
- Applicability Flags:
- Y/N/NYA
- Validation
-
- Dependencies:
- Mandatory only for track circuits
- Validation Rules:
-
Min Vehicle Impedance
Message: minVehicleImpedance (1.1.1.3.4.2.2): The train detection system has a minimum vehicle impedance reference that must be a minimum vehicle impedance. This error may be due to having more than one value or having a value that is not an instance of a MinVehicleImpedance.
-
Min Vehicle Impedance Applicability
Comment: The parameter minVehicleImpedance is applicable for track circuits.
Message: minVehicleImpedance (1.1.1.3.4.2.2):The Train Detection System {$this} ({?tdsLabel}), has a 'track circuit' type that makes the minVehicleImpedance parameter applicable. This error is due to not having a value for such a parameter.
- Additional Information
-
- General explanation:
- Compatibility with track circuits. A track circuit is only able to detect rolling stock if the impedance between rails does not exceed a certain value.
Maximum magnetic field
OP
IRI: http://data.europa.eu/949/tdsMaximumMagneticField
- Parameter of
-
Train Detection System
- General Information
-
- Number:
- 1.1.1.3.4.2.3
- 1.2.1.1.3.2.3
- XML Name:
- CCD_ACMagFieldMax
- Deadline:
- 12 months after publication of Article 7 Guide for OP tracks
- For train detection system compliant with TSIs, 12 months after publication of Article 7 Guide.
For train detection system not TSI compliant: in relation to article 13 of TSI CCS
- Belongs to parameters group
-
Train detection systems defined based on frequency bands
(
1.1.1.3.4
|
1.2.1.1.3
)
- Data Format
-
- Data Presentation
-
Maximum magnetic field
- Flags
-
- Applicability Flags:
- Y/N/NYA
- Validation
-
- Dependencies:
- Mandatory for train detection systems based on axle counters
- Validation Rules:
-
Tds Maximum Magnetic Field Applicability
Comment: Y, for parameter 1.1.1.3.7.1.1 “Axle Counters” only.
Message: tdsMaximumMagneticField (1.1.1.3.4.2.3, 1.2.1.1.3.2.3):The Train Detection System {$this} ({?clsLabel}), has an 'axle counters' type that makes the tdsMaximumMagneticField parameter applicable. This error is due to {$this} not having a value for such a parameter.
-
Tds Maximum Magnetic Field
Comment: Relates the Axle Counter TrainDetectionSystem with its MaximumMagneticField in (X,Y,Z). The maximum magnetic field limits allowed for axle counters (in dB µA/m) for a defined frequency band. It should be provided in 3 directions.
Message: tdsMaximumMagneticField (1.1.1.3.4.2.3, 1.2.1.1.3.2.3): The train detection system has a train detection system maximum magnetic field reference that must be a maximum magnetic field. This error may be due to having more than one value or having a value that is not an instance of a MaximumMagnaticField.
- Additional Information
-
- General explanation:
- Relates the Axle Counter TrainDetectionSystem with its MaximumMagneticField in (X,Y,Z). Verification of compliance with TSI includes application of notified national rules (when they exist).
Train protection legacy system
OP
IRI: http://data.europa.eu/949/protectionLegacySystem
- Parameter of
-
Running track
-
Subset with common characteristics
-
Vehicle Type
- General Information
-
- Number:
- 1.1.1.3.5.3
- 1.2.1.1.4.1
- XML Name:
- CPO_LegacyTrainProtection
- Deadline:
- 12 months after publication of Article 7 Guide for OP tracks
- 16 January 2020
- Belongs to parameters group
-
Train protection legacy systems
(
1.1.1.3.5
|
1.2.1.1.4
)
-
Vehicle type technical characteristic
- Data Format
-
- Data Presentation
-
Concept
- Taxonomy Reference:
-
Other Protection Control and Warnings (in line with ERA/TD/2011-09/INT (v1.13), Table 3)
-
Values :
-
| Code |
Value |
| 01 |
ALSN |
| 02 |
ASFA |
| 04 |
ATB First generation |
| 05 |
ATB new generation |
| 07 |
ATC v2 |
| 09 |
ATC vR |
| 10 |
ATP |
| 11 |
ATP-VR/RHK |
| 12 |
BACC |
| 13 |
CAWS |
| 14 |
Chiltern-ATP |
| 15 |
Crocodile |
| 16 |
DAAT |
| 17 |
EBICAB 700 BU |
| 18 |
EBICAB 700 PT (CONVEL) |
| 19 |
EBICAB 900 ES |
| 21 |
EuroSIGNUM |
| 23 |
EuroZUB |
| 25 |
EVM |
| 26 |
GNT (Geschwindigkeitsüberwachung für NeiTech-Züge) |
| 27 |
GW ATP |
| 28 |
INDUSI I60 |
| 29 |
KCVB |
| 30 |
KCVP |
| 31 |
KVB |
| 32 |
KVBP |
| 33 |
LS |
| 34 |
LZB (LZB L72, LZB L72 CE I and LZB L72 CE II) |
| 35 |
LZB ES |
| 36 |
Mechanical Trainstops |
| 37 |
MEMOR II+ |
| 38 |
NEXTEO |
| 39 |
PKP radio system with Radiostop function |
| 40 |
PZB 90 |
| 41 |
RETB |
| 42 |
RSDD/SCMT |
| 43 |
SHP |
| 44 |
SSC |
| 45 |
TBL 1 |
| 46 |
TBL 2 |
| 47 |
TBL1+ |
| 48 |
TPWS/AWS |
| 49 |
TVM 300 |
| 50 |
TVM 430 |
| 51 |
ZUB 123 |
| 100 |
None |
| scmt |
SCMT |
| scmt-rsc |
SCMT + RSC |
- Flags
-
- Applicability Flags:
- Y/N/NYA
- Validation
-
- Validation Rules:
-
Protection Legacy System Skos
Comment: Indication of which class B system is installed.
Message: Indication of the protectionLegacySystem (1.1.1.3.5.3): The track or subset with common characteristics {$this} has a value {?concept} that is not one of the predefined values and cannot be converted into a SKOS concept on this list: http://data.europa.eu/949/concepts/train-protection-legacy-systems/TrainProtectionLegacySystems.
- OPE TSI References
-
- Part of RCC Algorithm:
- true
- Additional Information
-
- General explanation:
- The list is in line with ERA/TD/2011-09/INT (v1.13), Table 3, and is now in 3.3 of the annex II of TSI CCS.
Other radio systems installed (Radio Legacy Systems)
OP
IRI: http://data.europa.eu/949/legacyRadioSystem
- Parameter of
-
Running track
-
Subset with common characteristics
-
Vehicle Type
- General Information
-
- Number:
- 1.1.1.3.6.1
- 1.2.1.1.5.1
- XML Name:
- CRS_Installed
- Deadline:
- 12 months after publication of Article 7 Guide for OP tracks
- 16 January 2020
- Belongs to parameters group
-
Radio Legacy Systems
(
1.1.1.3.6
|
1.2.1.1.5
)
- Data Format
-
- Data Presentation
-
Concept
- Taxonomy Reference:
-
Legacy Radio Systems (in line with ERA/TD/2011-09/INT (v1.13), Table 4)
-
Values :
-
| Code |
Value |
| 01 |
UIC Radio Chapter 1-4 |
| 02 |
UIC Radio Chapter 1-4+6 |
| 03 |
UIC Radio Chapter 1-4 + 6 (Irish system) |
| 04 |
UIC Radio Chapter 1-4 (TTT radio system installed at Cascais line) |
| 05 |
TTT radio system CP_N (RSC - Radio Solo-Comboio) |
| 06 |
PKP radio system |
| 07 |
TRS — The Czech Railways radio system |
| 08 |
LDZ radio system |
| 09 |
CH — Greek Railways radio system (VHF) |
| 10 |
UIC Radio Chapter Bulgaria |
| 11 |
The Estonian radio system |
| 12 |
The Lithuanian radio system |
| 13 |
450 Mhz UIC (kanál C) |
| 14 |
Analogue Radio Germany - UIC 751 |
| 15 |
BOSCH (160 MHz) |
| 16 |
GSM-P |
| 17 |
Multikom (160 MHz and 450 MHz) |
| 18 |
OMEGA (160 MHz) |
| 19 |
RDZ - in compliance with UIC 751-3 |
| 20 |
RETB (voice) |
| 21 |
Radio Network of CFR |
| 22 |
SRO (160 MHz) |
| 23 |
Shunting Radio Communication System |
| 24 |
ZUGFUNK 95 |
| 25 |
ZUGFUNK 2000 |
| 27 |
SRV — The Czech Railways radio system |
| 29 |
Telecar 10/460 (AEG Mobile) |
| 100 |
None |
- Flags
-
- Applicability Flags:
- Y/N/NYA
- Validation
-
- Validation Rules:
-
Legacy Radio System
Comment: Indication of radio legacy systems installed.
Message: legacyRadioSystem (1.1.1.3.6.1, 1.2.1.1.5.1): The track or subset with common characteristics may have other radio systems installed (Radio Legacy Systems) value that is an IRI. This error is due to having a value that is not an IRI
-
Legacy Radio System Skos
Comment: Indication of radio legacy systems installed.
Message: legacyRadioSystem (1.1.1.3.6.1, 1.2.1.1.5.1): The track or subset with common characteristics {$this} (label {?label}) has a value {?concept} that is not one of the predefined values and cannot be converted into a SKOS concept on this list: http://data.europa.eu/949/concepts/legacy-radio-systems/LegacyRadioSystems.
- OPE TSI References
-
- Part of RCC Algorithm:
- true
-
- Appendix D2 Index
- 3.1.7
- Additional Information
-
- General explanation:
- The list is in line with ERA/TD/2011-09/INT, Table 4, and is now in 3.4 of the annex II of TSI CCS.
Type of train detection system
OP
IRI: http://data.europa.eu/949/trainDetectionSystemType
- Parameter of
-
Train Detection System
-
Vehicle Type
- General Information
-
- Number:
- 1.1.1.3.7.1.1
- 1.2.1.1.3.1.1
- XML Name:
- CTD_DetectionSystem
- Deadline:
- In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
- 12 months after publication of Article 7 Guide for OP tracks
- Belongs to parameters group
-
Other train detection systems
(
1.1.1.3.7
|
1.2.1.1.6
)
-
Vehicle type technical characteristic
- Data Format
-
- Data Presentation
-
Concept
- Taxonomy Reference:
-
Train Detection Systems
-
Values :
-
| Code |
Value |
| 10 |
Track circuit |
| 20 |
Wheel detector |
| 30 |
Loop |
- Flags
-
- Applicability Flags:
- Y/N/NYA
- Validation
-
- Dependencies:
- Not all parameters are applicable to all types of train detection systems; it depends on the applicability condition.
- Validation Rules:
-
Train Detection System Type Skos
Comment: Indication of types of train detection system installed.
Message: Indication of types of train detection system installed (1.1.1.3.7.1.1, 1.2.1.1.3.1.1): The train detection system {$this} (label {?tdsLabel}) has a value {?concept} that is not one of the predefined values and cannot be converted into a SKOS concept on this list: http://data.europa.eu/949/concepts/train-detection/TrainDetectionSystems.
-
Train Detection System Type
Comment: Indication of types of train detection system installed.
Message: trainDetectionSystemType (1.1.1.3.7.1.1, 1.2.1.1.3.1.1): The train detection system has a train detection system type that must be a single IRI. This error may be due to having more than one value or having a value that is not an IRI.
- OPE TSI References
-
- Part of RCC Algorithm:
- true
- Additional Information
-
- General explanation:
- Explanation on data presentation:
The option of "wheel detector" has to be also selected for: wheel sensor for axle counter, pedal or treadle.
- Verification of compliance with TSI includes application of notified national rules (when they exist).
Explanation on data presentation:
The option of "wheel detector" has to be also selected for: wheel sensor for axle counter, pedal or treadle.
If there is no train detection system (if this parameters is not applicable) it has an impact on parameters "Type of track circuits or axle counter to which specific checks are needed" and "Document with the procedure(s) related to the type of train detection systems declared in 1.1.1.3.7.1.2 ( 1.2.1.1.6.1, if in OP)", making them also not applicable.
Type of track circuits or axle counters to which specific checks are needed
OP
IRI: http://data.europa.eu/949/trainDetectionSystemSpecificCheck
- Parameter of
-
Train Detection System
- General Information
-
- Number:
- 1.1.1.3.7.1.2
- 1.2.1.1.6.1
- XML Name:
- CTD_TCCheck
- Deadline:
- 12 months after publication of Article 7 Guide
- Belongs to parameters group
-
Other train detection systems
(
1.1.1.3.7
|
1.2.1.1.6
)
- Data Format
-
- Data Presentation
-
Concept
- Taxonomy Reference:
-
Train Detection Systems Specific Checks
-
Values :
-
| Code |
Value |
| 10 |
Direct current Track circuit |
| 20 |
50Hz Track circuit |
| 30 |
Zp30K / Zp30H |
| 40 |
83.3 Hz Track circuit |
| 50 |
125 Hz Track circuit |
| 60 |
ZP 43 E (manufactured prior to 2015) |
| 70 |
83.3 Hz and 125 Hz track circuits |
| 80 |
83.3 Hz track circuit and ZP 43 E (manufactured prior to 2015) |
| 90 |
125 Hz track circuit and ZP 43 E (manufactured prior to 2015) |
| 100 |
83.3 Hz and 125 Hz track circuits and ZP 43 E (manufactured prior to 2015) |
| 110 |
EBÜT 80: axle counter |
| 120 |
WSSB: track circuit |
| 130 |
Siemens 100Hz (106,7Hz) : track circuit |
| 140 |
Thales 100Hz (106,7Hz) : track circuit |
- Flags
-
- Applicability Flags:
- Y/N/NYA
- Validation
-
- Dependencies:
- It is applicable only when parameter "Type of train detection system" is applicable
- Validation Rules:
-
Train Detection System Specific Check Skos
Comment: Reference to the technical specification of train detection system.
Message: Indication of specific checks of train detection system installed (1.1.1.3.7.1.2, 1.2.1.1.6.1): The train detection system {$this} (label {?tdsLabel}) has a value {?concept} that is not one of the predefined values and cannot be converted into a SKOS concept on this list: http://data.europa.eu/949/concepts/train-detection-specific-checks.
-
Train Detection System Specific Check Applicability
Comment: Only applicable, when 1.1.1.3.7.1.1 is applicable.
Message: trainDetectionSystemSpecificCheck (1.1.1.3.7.1.2, 1.2.1.1.6.1):The Train Detection System {$this} ({?clsLabel}), has a type that makes the trainDetectionSystemSpecificCheck parameter applicable. This error is due to {$this} not having a value for such a parameter.
-
Train Detection System Specific Check
Comment: Reference to the technical specification of train detection system.
Message: trainDetectionSystemSpecificCheck (1.1.1.3.7.1.2, 1.2.1.1.6.1): The train detection system has a train detection system specific check that must be a single IRI. This error may be due to having more than one value or having a value that is not an IRI.
- OPE TSI References
-
- Part of RCC Algorithm:
- false
- Additional Information
-
- General explanation:
- String containing the name of the TD system for which checks are mentioned in 1.1.1.3.7.1.3.
Document with the procedure(s) related to the type of train detection systems declared in "Type of track circuits or axle counters to which specific checks are needed"
OP
IRI: http://data.europa.eu/949/trainDetectionSystemSpecificCheckDocument
- Parameter of
-
Train Detection System
- General Information
-
- Number:
- 1.1.1.3.7.1.3
- 1.2.1.1.6.2
- XML Name:
- CTD_TCCheckDocRef
- Deadline:
- In accordance with TSI CCS Art. 13 and 12 months after publication of Article 7 Guide
- 12 months after publication of Article 7 Guide for OP tracks
- Belongs to parameters group
-
Other train detection systems
(
1.1.1.3.7
|
1.2.1.1.6
)
- Data Format
-
- Data Presentation
-
ERA Document
- Flags
-
- Applicability Flags:
- Y/N/NYA
- Validation
-
- Dependencies:
- It is applicable only when parameter "Type of train detection system" is applicable
- Validation Rules:
-
Train Detection System Specific Check Document Applicability
Comment: Only applicable, when 1.1.1.3.7.1.1 is applicable.
Message: trainDetectionSystemSpecificCheckDocument (1.1.1.3.7.1.3, 1.2.1.1.6.2):The Train Detection System {$this} ({?clsLabel}), has a type that makes the trainDetectionSystemSpecificCheckDocument parameter applicable. This error is due to {$this} not having a value for such a parameter.
-
Train Detection System Specific Check Document
Comment: Electronic document available in two EU languages from the IM stored by the Agency with precise procedures for the specific check to be performed for train detection systems identified in 1.1.1.3.7.1.2.
Message: trainDetectionSystemSpecificCheckDocument (1.1.1.3.7.1.3, 1.2.1.1.6.2): The track defines the electronic document available in two EU languages value and it must be a Document. This error may be due to having more than one value or having a value that is not a Document.
- OPE TSI References
-
- Part of RCC Algorithm:
- false
- Additional Information
-
- General explanation:
- The value of this parameter should be either a reference to a file name or an external link to a document.
If a file name is provided, the Infrastructure Manager (IM) must upload a document with the same file name using the "Reference Documents Management" functionality in the RINF application. The document must be in electronic format and available in two official EU languages. In this case, the parameter value must be repeated for each document.
If an external link is provided, the IM must ensure that the document is available at the provided link.
Section with train detection limitation
OP
IRI: http://data.europa.eu/949/tdsFrenchTrainDetectionSystemLimitation
- Parameter of
-
Train Detection System
- General Information
-
- Number:
- 1.1.1.3.7.1.4
- 1.2.1.1.6.3
- XML Name:
- CTD_TCLimitation
- Deadline:
- 12 months after publication of Article 7 Guide for OP tracks
- 16 January 2020
- Belongs to parameters group
-
Other train detection systems
(
1.1.1.3.7
|
1.2.1.1.6
)
- Data Format
-
- Data Presentation
-
Section with train detection limitation
- Format:
- The value of this parameter is an instance of the era:FrenchTrainDetectionSystemLimitation class with all its properties:
- true/false for the existance of a section with train detection limitation
- list of values from 1 to 8 defined in the taxonomy
- Flags
-
- Applicability Flags:
- Y/N/NYA
- Validation
-
- Dependencies:
- Only applicable on running tracks in France
- Validation Rules:
-
Tds French Train Detection System Limitation
Comment: Relates the class train detection system with the class that represents the section with train detection limitation. Specific for route compatibility check on French network.
Message: tdsFrenchTrainDetectionSystemLimitation (1.1.1.3.7.1.4, 1.2.1.1.6.3): The train detection system has a tds french train detection system limitation reference that must be a french train detection system limitation. This error may be due to having more than one value or having a value that is not an instance of a FrenchTrainDetectionSystemLimitation
- OPE TSI References
-
- Part of RCC Algorithm:
- true
- Additional Information
-
- General explanation:
- Relates the class train detection system with the class that represents the section with train detection limitation. Select the special condition as applicable through National Rule from the List.
For RINF XML data sets:
As long as the data provision through XML data sets is allowed, the data format is a character sting with the following structure:
[Y/N]+[N]
where:
- [Y/N] - is the existence of section with train detection limitation
- [N] is a number from 1 to 8 referring to sections with:
[1] Tonnage circulated per track is inferior to 15000 tons/day/track
[2] Directional Interlocking
[3] 45-second delay for directional interlocking
[4] Installation with track circuit announcement
[5] Absence of a shunting assistance pedal in the normal direction of circulation for non-reversible double track lines
[6] Absence of a shunting assistance pedal regardless of the direction of traffic for single track lines and tracks for two way working
[7] Absence of a pedal announcement mechanism
[8] 45-second delay for specific announcement reset devices.
Existence of switch over between different protection, control and warning systems while running
DP
IRI: http://data.europa.eu/949/switchProtectControlWarning
- Parameter of
-
Subset with common characteristics
-
Track
- General Information
-
- Number:
- 1.1.1.3.8.1
- 1.2.1.1.7.1
- XML Name:
- CTS_SwitchProtectControlWarn
- Deadline:
- In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
- 12 months after publication of Article 7 Guide for OP tracks
- Belongs to parameters group
-
Transitions between systems
(
1.1.1.3.8
|
1.2.1.1.7
)
- Data Format
-
- Data Presentation
-
Boolean
- Flags
-
- Applicability Flags:
- Y/N/NYA
- Validation
-
- Dependencies:
- Applicable when at least two different protection, control and warning systems exist.
- Validation Rules:
-
Switch Protect Control Warning
Comment: Indication whether a switch over between different systems whilst running exists.
Message: switchProtectControlWarning (1.2.1.1.7.1, 1.1.1.3.8.1): Each track or subset with common characteristics may define the existence of switch over between different protection, control and warning systems while running. This error is due to having more than one value or having a value that is not Y/N (boolean).
-
Switch Protect Control Warning Applicability
Comment: Applicable ('Y') when at least two different class of protection systems exist.
Message: switchProtectControlWarning (1.2.1.1.7.1, 1.1.1.3.8.1):The track or subset with common characteristics {$this} ({?label}), has more than one protection system defined which makes the switchProtectControlWarning parameter applicable. This error is due to {$this} not having a value for such a parameter.
- OPE TSI References
-
- Appendix D2 Index
- 3.4.2
- Additional Information
-
- General explanation:
- Switch over between different systems whilst running. Installation depends on local conditions.
Special conditions to switch over between different class B train protection, control and warning systems
DP
IRI: http://data.europa.eu/949/conditionsSwitchTrainProtectionSystems
- Parameter of
-
Running track
-
Subset with common characteristics
- General Information
-
- Number:
- 1.1.1.3.8.1.1
- 1.2.1.1.7.1.1
- XML Name:
- CTS_SwitchProtectConditions
- Deadline:
- 12 months after publication of Article 7 Guide
- Belongs to parameters group
-
Transitions between systems
(
1.1.1.3.8
|
1.2.1.1.7
)
- Data Format
-
- Data Presentation
-
String
- Format:
- NNN
- Flags
-
- Applicability Flags:
- Y/N/NYA
- Validation
-
- Dependencies:
- Applicable when at least two different protection, control and warning systems exist.
- Validation Rules:
-
Conditions Switch Train Protection Systems
Comment: Conditions to switch over between different class B train protection, control and warning systems.
Message: conditionsSwitchTrainProtectionSystems (1.1.1.3.8.1.1, 1.2.1.1.7.1.1): The track or subset with common characteristics has a Special conditions to switch over between different class B train protection, control and warning systems value that must be a string and follow the format [NNN]. The error is due to having more than one value, having a value that is not a string, or it is due to the value not following the pattern.
- OPE TSI References
-
- Appendix D2 Index
- 3.4.2
- Additional Information
-
- General explanation:
- Switch over between different systems whilst running. Installation depends on local conditions.
Existence of switch over between different radio systems
DP
IRI: http://data.europa.eu/949/switchRadioSystem
- Parameter of
-
Subset with common characteristics
-
Track
- General Information
-
- Number:
- 1.1.1.3.8.2
- 1.2.1.1.7.2
- XML Name:
- CTS_SwitchRadioSystem
- Deadline:
- In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
- 12 months after publication of Article 7 Guide for OP tracks
- Belongs to parameters group
-
Transitions between systems
(
1.1.1.3.8
|
1.2.1.1.7
)
- Data Format
-
- Data Presentation
-
Boolean
- Flags
-
- Applicability Flags:
- Y/N/NYA
- Validation
-
- Dependencies:
- Applicable when at least two different radio systems exist.
- Validation Rules:
-
Switch Radio System
Comment: Indication whether a switch over between different radio systems and no communication system whilst running exists.
Message: switchRadioSystem (1.2.1.1.7.2, 1.1.1.3.8.2): Each track or subset with common characteristics may define the existence of switch over between different radio systems. This error is due to having more than one value or having a value that is not Y/N (boolean).
-
Switch Radio System Applicability
Comment: Applicable ('Y') when at least two different radio systems exist.
Message: switchRadioSystem (1.2.1.1.7.2, 1.1.1.3.8.2):The track or subset with common characteristics {$this} ({?label}), has more than one radio system defined which makes the switchRadioSystem parameter applicable. This error is due to {$this} not having a value for such a parameter.
- OPE TSI References
-
- Appendix D2 Index
- 3.4.4
- Additional Information
-
- General explanation:
- Switch over between different radio systems and no communication system whilst running. Installation depends on local conditions.
The "Indication if other radio systems in normal operation are installed line-side" is given in parameter 1.1.1.3.6.1 / SOL Track Parameter CRS_Installed
Special instructions to switch over between different radio systems
OP
IRI: http://data.europa.eu/949/instructionsSwitchRadioSystems
- Parameter of
-
Running track
-
Subset with common characteristics
- General Information
-
- Number:
- 1.1.1.3.8.2.1
- 1.2.1.1.7.2.1
- XML Name:
- CTS_SwitchRadioConditions
- Deadline:
- 12 months after publication of Article 7 Guide
- Belongs to parameters group
-
Transitions between systems
(
1.1.1.3.8
|
1.2.1.1.7
)
- Data Format
-
- Data Presentation
-
ERA Document
- Flags
-
- Applicability Flags:
- Y/N/NYA
- Validation
-
- Dependencies:
- Applicable when at least two different radio systems exist.
- Validation Rules:
-
Instructions Switch Radio Systems Applicability
Comment: Applicable ('Y') when at least two different radio systems exist.
Message: instructionsSwitchRadioSystems (1.1.1.3.8.2.1, 1.2.1.1.7.2.1):The track or subset with common characteristics {$this} ({?label}), has a more than one radio system defined which makes the instructionsSwitchRadioSystems parameter applicable. This error is due to {$this} not having a value for such a parameter.
-
Instructions Switch Radio Systems
Comment: Name and/or reference of the document specifying the Special instructions to switch over between different radio systems.
Message: instructionsSwitchRadioSystems (1.1.1.3.8.2.1, 1.2.1.1.7.2.1): The track or subset with common characteristics has Special instructions to switch over between different radio systems value that must be a Document.
- OPE TSI References
-
- Appendix D2 Index
- 3.4.4
- Additional Information
-
- General explanation:
- The details of the conditions to switch radio systems must be published.
The value of this parameter should be either a reference to a file name or an external link to a document.
If a file name is provided, the Infrastructure Manager (IM) must upload a document with the same file name using the "Reference Documents Management" functionality in the RINF application. The document must be in electronic format and available in two official EU languages. In this case, the parameter value must be repeated for each document.
If an external link is provided, the IM must ensure that the document is available at the provided link.
Special technical conditions required to switch over between ERTMS/ETCS and Class B systems
OP
IRI: http://data.europa.eu/949/conditionsSwitchClassBSystems
- Parameter of
-
Running track
-
Subset with common characteristics
- General Information
-
- Number:
- 1.1.1.3.8.3
- 1.2.1.1.7.3
- XML Name:
- CTS_SwitchProtectAB
- Deadline:
- 12 months after publication of Article 7 Guide
- Belongs to parameters group
-
Transitions between systems
(
1.1.1.3.8
|
1.2.1.1.7
)
- Data Format
-
- Data Presentation
-
ERA Document
- Flags
-
- Applicability Flags:
- Y/N/NYA
- Validation
-
- Dependencies:
- Applicable when at least two different class of protection systems exist.
- Validation Rules:
-
Conditions Switch Class Bsystems Applicability
Comment: Applicable ('Y') when at least two different class of protection systems exist.
Message: conditionsSwitchClassBSystems (1.1.1.3.8.3, 1.2.1.1.7.3):The track or subset with common characteristics {$this} ({?label}), has a more than one protection system defined which makes the conditionsSwitchClassBSystems parameter applicable. This error is due to {$this} not having a value for such a parameter.
-
Conditions Switch Class Bsystems
Comment: Name and/or reference of the document specifying the Special technical conditions required to switch over between ERTMS/ETCS and Class B systems.
Message: conditionsSwitchClassBSystems (1.1.1.3.8.3, 1.2.1.1.7.3): The track or subset with common characteristics has Special technical conditions required to switch over between ERTMS/ETCS and Class B systems value that must be a Document. This error is due to having more than one value or having a value that is not an instance of Document.
- OPE TSI References
-
- Appendix D2 Index
- 3.4.3
- Additional Information
-
- General explanation:
- The details of the conditions to switch between Class B train protection systems must be published.
The value of this parameter should be either a reference to a file name or an external link to a document.
If a file name is provided, the Infrastructure Manager (IM) must upload a document with the same file name using the "Reference Documents Management" functionality in the RINF application. The document must be in electronic format and available in two official EU languages. In this case, the parameter value must be repeated for each document.
If an external link is provided, the IM must ensure that the document is available at the provided link.
Existence and TSI compliance of rules for magnetic fields emitted by a vehicle
DP
IRI: http://data.europa.eu/949/tsiMagneticFields
- Parameter of
-
Running track
-
Subset with common characteristics
- General Information
-
- Number:
- 1.1.1.3.9.1
- 1.2.1.1.8.1
- XML Name:
- CEI_TSIMagneticFields
- Deadline:
- 12 months after publication of Article 7 Guide for OP tracks
- In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
- Belongs to parameters group
-
Parameters related to electromagnetic interferences
(
1.1.1.3.9
|
1.2.1.1.8
)
- Data Format
-
- Data Presentation
-
Boolean
- Format:
- Y/N
- Flags
-
- Applicability Flags:
- Y/N/NYA
- Validation
-
- Dependencies:
- Applicable ( Y ) only when for parameter 1.1.1.3.7.1 the selected option is wheel detector. The parameter is not applicable when the rules do not exist.
- Validation Rules:
-
Tsi Magnetic Fields
Comment: Indication whether rules exist and are compliant with the TSI.
Message: tsiMagneticFields (1.1.1.3.9.1, 1.2.1.1.8.1): Each track or subset with common characteristics may define the existence and TSI compliance of rules for magnetic fields emitted by a vehicle. This error is due to having more than one value or having a value that is not Y/N (boolean).
-
Tsi Magnetic Fields Applicability
Comment: Applicable ('Y') only when for parameter 1.1.1.3.7.1.1 the selected option is 'wheel detector'.
Message: tsiMagneticFields (1.1.1.3.9.1, 1.2.1.1.8.1):The track or subset with common characteristics {$this} ({?label}), has a 'train detection system' type ('wheel detector') that makes the tsiMagneticFields parameter applicable. This error is due to {$this} not having a value for such a parameter.
- Additional Information
-
- General explanation:
- The electromagnetic fields generated by rolling stock can interfere with the operation of axle counters and wheel detectors.
'True' means the rules exist and are compliant with the frequency management specified in the TSI.
'False' means the rules exist and are not compliant with the frequency management specified in the TSI.
Verification of compliance with TSI includes application of notified national rules (when they exist) in case of part covered by open point.
Existence and TSI compliance of limits in harmonics in the traction current of vehicles
DP
IRI: http://data.europa.eu/949/tsiTractionHarmonics
- Parameter of
-
Running track
-
Subset with common characteristics
- General Information
-
- Number:
- 1.1.1.3.9.2
- 1.2.1.1.8.2
- XML Name:
- CEI_TSITractionHarmonics
- Deadline:
- In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
- 12 months after publication of Article 7 Guide for OP tracks
- Belongs to parameters group
-
Parameters related to electromagnetic interferences
(
1.1.1.3.9
|
1.2.1.1.8
)
- Data Format
-
- Data Presentation
-
Boolean
- Flags
-
- Applicability Flags:
- Y/N/NYA
- Validation
-
- Validation Rules:
-
Tsi Traction Harmonics Applicability
Comment: Applicable ('Y') only when for parameter 1.1.1.3.7.1.1 the selected option is 'wheel detector' or 'track circuit'.
Message: tsiTractionHarmonics (1.1.1.3.9.2, 1.2.1.1.8.2):The track or subset with common characteristics {$this} ({?label}), has a 'train detection system' type ('wheel detector' or 'track circuit') that makes the tsiTractionHarmonics parameter applicable. This error is due to {$this} not having a value for such a parameter.
-
Tsi Traction Harmonics
Comment: Indication whether rules exist and are compliant with the TSI.
Message: tsiTractionHarmonics (1.1.1.3.9.2, 1.2.1.1.8.2): Each track or subset with common characteristics may define the existence and TSI compliance of limits in harmonics in the traction current of vehicles. This error is due to having more than one value or having a value that is not Y/N (boolean).
- Additional Information
-
- General explanation:
- Compatibility with track circuits and wheel detectors of axle counters.
The harmonics in the traction current in the rails can interfere with the operation of track circuits. The DC current in the rails may saturate the detectors of the axle counters, preventing their operation.
'Y' means the rules exist and are compliant with the frequency management specified in the TSI.
'N' 'means the rules exist and are not compliant with the frequency management specified in the TSI.
Verification of compliance with TSI includes application of notified national rules (when they exist) in case of part covered by open point.
LOC&PAS TSI : Appendix J-2, index 1, clause 3.2.2
ETCS level for degraded situation
OP
IRI: http://data.europa.eu/949/etcsDegradedSituation
- Parameter of
-
Running track
-
Subset with common characteristics
- General Information
-
- Number:
- 1.1.1.3.10.1
- 1.2.1.1.9.1
- XML Name:
- CLD_ETCSSituation
- Deadline:
- In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
- 12 months after publication of Article 7 Guide for OP tracks
- Belongs to parameters group
-
Line-side system for degraded situation
(
1.1.1.3.10
|
1.2.1.1.9
)
- Data Format
-
- Data Presentation
-
Concept
- Taxonomy Reference:
-
ETCS Level for Degraded Situations
-
Values :
-
- Flags
-
- Applicability Flags:
- Y/N/NYA
- Validation
-
- Dependencies:
- Mandatory when ETCS is present.
- Validation Rules:
-
Etcs Degraded Situation
Comment: ERTMS / ETCS application level for degraded situation related to the track side equipment.
Message: etcsDegradedSituation (1.1.1.3.10.1, 1.2.1.1.9.1): The track or subset with common characteristics must have an ETCS level for degraded situation value that is an IRI.
-
Etcs Degraded Situation Skos
Comment: ERTMS / ETCS application level for degraded situation related to The track or subset with common characteristics side equipment.
Message: etcsDegradedSituation (1.1.1.3.10.1, 1.2.1.1.9.1): The track or subset with common characteristics {$this} (label {?label}) has a value {?concept} that is not one of the predefined values and cannot be converted into a SKOS concept on this list: http://data.europa.eu/949/concepts/etcs-situation/ETCSSituations.
-
Etcs Degraded Situation Applicability
Comment: Only applicable when selected value for 1.1.1.3.2.1 (ETCS present).
Message: etcsDegradedSituation (1.1.1.3.10.1, 1.2.1.1.9.1):The track or subset with common characteristics {$this} ({?label}), has an 'ETCS Level Type' defined that makes the etcsDegradedSituation parameter applicable. This error is due to {$this} not having a value for such a parameter.
- OPE TSI References
-
- Appendix D2 Index
- 3.4.1
- Additional Information
-
- General explanation:
- System for degraded situation.
In case of failure of the ETCS Level for normal operation, train movement can be supervised in another ETCS Level.
If parameter 1.1.1.3.2.1 is not used (no ETCS), no degradation is possible, so only "none" level is possible for degraded .
It assumed that the degraded level has to be lower than the actual operating level.
See also TSI OPE 4.2.3.6. Degraded operation.
-
- Example:
- Level 1 as a degraded mode for Level 2.
Other train protection, control and warning systems for degraded situation
OP
IRI: http://data.europa.eu/949/otherTrainProtection
- Parameter of
-
Running track
-
Subset with common characteristics
- General Information
-
- Number:
- 1.1.1.3.10.2
- 1.2.1.1.9.2
- XML Name:
- CLD_OtherProtectControlWarn
- Deadline:
- 12 months after publication of Article 7 Guide for OP tracks
- In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
- Belongs to parameters group
-
Line-side system for degraded situation
(
1.1.1.3.10
|
1.2.1.1.9
)
- Data Format
-
- Data Presentation
-
Concept
- Taxonomy Reference:
-
Other Protection Control and Warnings (in line with ERA/TD/2011-09/INT (v1.13), Table 3)
-
Values :
-
| Code |
Value |
| 01 |
ALSN |
| 02 |
ASFA |
| 04 |
ATB First generation |
| 05 |
ATB new generation |
| 07 |
ATC v2 |
| 09 |
ATC vR |
| 10 |
ATP |
| 11 |
ATP-VR/RHK |
| 12 |
BACC |
| 13 |
CAWS |
| 14 |
Chiltern-ATP |
| 15 |
Crocodile |
| 16 |
DAAT |
| 17 |
EBICAB 700 BU |
| 18 |
EBICAB 700 PT (CONVEL) |
| 19 |
EBICAB 900 ES |
| 21 |
EuroSIGNUM |
| 23 |
EuroZUB |
| 25 |
EVM |
| 26 |
GNT (Geschwindigkeitsüberwachung für NeiTech-Züge) |
| 27 |
GW ATP |
| 28 |
INDUSI I60 |
| 29 |
KCVB |
| 30 |
KCVP |
| 31 |
KVB |
| 32 |
KVBP |
| 33 |
LS |
| 34 |
LZB (LZB L72, LZB L72 CE I and LZB L72 CE II) |
| 35 |
LZB ES |
| 36 |
Mechanical Trainstops |
| 37 |
MEMOR II+ |
| 38 |
NEXTEO |
| 39 |
PKP radio system with Radiostop function |
| 40 |
PZB 90 |
| 41 |
RETB |
| 42 |
RSDD/SCMT |
| 43 |
SHP |
| 44 |
SSC |
| 45 |
TBL 1 |
| 46 |
TBL 2 |
| 47 |
TBL1+ |
| 48 |
TPWS/AWS |
| 49 |
TVM 300 |
| 50 |
TVM 430 |
| 51 |
ZUB 123 |
| 100 |
None |
| scmt |
SCMT |
| scmt-rsc |
SCMT + RSC |
- Flags
-
- Applicability Flags:
- Y/N/NYA
- Validation
-
- Dependencies:
- Only applicable when for parameter 1.1.1.3.10.1 "none" was selected.
- Validation Rules:
-
Other Train Protection Skos
Comment: Indication of existence of other system than ETCS for degraded situation.
Message: otherTrainProtection (1.1.1.3.10.2, 1.2.1.1.9.2): The track or subset with common characteristics {$this} (label {?label}) has a value {?concept} that is not one of the predefined values and cannot be converted into a SKOS concept on this list: http://data.europa.eu/949/concepts/other-protection-control-warning/OtherProtectionControlWarnings.
-
Other Train Protection
Comment: Indication of existence of other system than ETCS for degraded situation.
Message: otherTrainProtection (1.1.1.3.10.2, 1.2.1.1.9.2): The track or subset with common characteristics may have other train protection, control and warning systems for degraded situation value that is an IRI. This error is due to having more than one value or having a value that is not an IRI.
-
Other Train Protection Applicability
Comment: Only applicable when selected value for 1.1.1.3.2.1 (ETCS present).
Message: otherTrainProtection (1.1.1.3.10.2, 1.2.1.1.9.2):The track or subset with common characteristics {$this} ({?label}), has an 'ETCS Level Type' defined which makes the otherTrainProtection parameter applicable. This error is due to {$this} not having a value for such a parameter.
- OPE TSI References
-
- Appendix D2 Index
- 3.4.1
- Additional Information
-
- General explanation:
- Selected value shall answer the question whether any other system than ETCS exists on the respective track. The list of possible values is in line with ERA/TD/2011-09/INT, Table 3.
Maximum braking distance requested
DP
IRI: http://data.europa.eu/949/maximumBrakingDistance
- Parameter of
-
Running track
-
Subset with common characteristics
- General Information
-
- Number:
- 1.1.1.3.11.1
- XML Name:
- CBP_MaxBrakeDist
- Deadline:
- In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
- Belongs to parameters group
-
Brake related parameters
(
1.1.1.3.11
)
- Data Format
-
- Data Presentation
-
Integer
- Format:
- NNNNN
- Unit of Measure:
-
Metre
- Flags
-
- Applicability Flags:
- Y/N
- Validation
-
- Validation Rules:
-
Maximum Braking Distance
Comment: The maximum value of the braking distance [in metres] of a train shall be given for the maximum line speed.
Message: maximumBrakingDistance (1.1.1.3.11.1): The track or subset with common characteristics must define at most one value of the maximum value of the braking distance [in metres] of a train and it is an integer. This error may be due to the track having more than one value or to having a value that is not an integer.
- OPE TSI References
-
- Part of RCC Algorithm:
- true
- Additional Information
-
- General explanation:
- This distance corresponds to the smallest physical distance between signals of the section of line at V max, taking into account the effect of gradient, minus the value of the safety margin used by the IM.
The braking capability of a train allows it to respect this braking distance.
Note that the OPE TSI provides for an exchange of detailed information between the infrastructure manager and the railway undertaking to ensure safe operation.
See also:
- OPE TSI: 4.2.2.6
- CCS TSI: 4.2.2
ATO Grade of Automation
OP
IRI: http://data.europa.eu/949/atoGradeAutomation
- Parameter of
-
Running track
-
Subset with common characteristics
- General Information
-
- Number:
- 1.1.1.3.13.1
- 1.2.1.1.10.1
- XML Name:
- ATO_GradeAutomation
- Deadline:
- 12 months after publication of Article 7 Guide
- Belongs to parameters group
-
Automated Train Operation (ATO)
(
1.1.1.3.13
|
1.2.1.1.10
)
- Data Format
-
- Data Presentation
-
Concept
- Taxonomy Reference:
-
ATO Grade of Automation
-
Values :
-
- Flags
-
- Applicability Flags:
- Y/N/NYA
- Validation
-
- Dependencies:
- Parameter only applicable when ETCS Baseline > 4 MR1 and ATO is implemented
- Validation Rules:
-
Ato Grade Automation
Comment: ATO grade of automation installed lineside.
Message: atoGradeAutomation (1.1.1.3.13.1, 1.2.1.1.10.1): The track or subset with common characteristics must have a ATO grade of automation installed lineside value that is an IRI.
-
Ato Grade Automation Skos
Comment: ATO grade of automation installed lineside.
Message: atoGradeAutomation (1.1.1.3.13.1, 1.2.1.1.10.1): The track or subset with common characteristics {$this} (label {?label}) has a value {?concept} that is not one of the predefined values and cannot be converted into a SKOS concept on this list: http://data.europa.eu/949/concepts/ato-grades-automation/ATOGradeOfAutomation.
- OPE TSI References
-
- Appendix D2 Index
- 3.4.8
- Additional Information
-
- General explanation:
- ATO is an optional function added in ETCS B4, only available under L2. See: TSI CCS, 4.2.4 & 4.2.19.
Parameter only applicable when ETCS Baseline > 4 MR1 and ATO is implemented
ATO System version
OP
IRI: http://data.europa.eu/949/atoSystemVersion
- Parameter of
-
Running track
-
Subset with common characteristics
- General Information
-
- Number:
- 1.1.1.3.13.2
- 1.2.1.1.10.2
- XML Name:
- ATO_SysVer
- Deadline:
- 12 months after publication of Article 7 Guide
- Belongs to parameters group
-
Automated Train Operation (ATO)
(
1.1.1.3.13
|
1.2.1.1.10
)
- Data Format
-
- Data Presentation
-
Concept
- Taxonomy Reference:
-
ATO System Versions
-
Values :
-
| Code |
Value |
| 0 |
Non-harmonised |
| 1 |
1.0 |
- Flags
-
- Applicability Flags:
- Y/N/NYA
- Validation
-
- Dependencies:
- Applicable when 'ATO Grade of Automation' is applicable
- Validation Rules:
-
Ato System Version
Comment: ATO system version according to the specification referenced in TSI CCS (4.2.19).
Message: atoSystemVersion (1.1.1.3.13.1, 1.2.1.1.10.1): The track or subset with common characteristics must have a ATO system version value that is an IRI.
-
Ato System Version Skos
Comment: ATO system version according to the specification referenced in TSI CCS (4.2.19).
Message: atoSystemVersion (1.1.1.3.13.1, 1.2.1.1.10.1): The track or subset with common characteristics {$this} (label {?label}) has a value {?concept} that is not one of the predefined values and cannot be converted into a SKOS concept on this list: http://data.europa.eu/949/concepts/ato-s-versions/ATOSystemVersions.
- OPE TSI References
-
- Appendix D2 Index
- 3.4.8
- Additional Information
-
- General explanation:
- ATO is an optional function added in ETCS B4, only available under L2. See: TSI CCS, 4.2.4 & 4.2.19.
Parameter only applicable when ETCS Baseline > 4 MR1 and ATO is implemented
ATO communication system
OP
IRI: http://data.europa.eu/949/atoCommunicationSystem
- Parameter of
-
Running track
-
Subset with common characteristics
- General Information
-
- Number:
- 1.1.1.3.13.3
- 1.2.1.1.10.3
- XML Name:
- ATO_CommSystem
- Deadline:
- 12 months after publication of Article 7 Guide
- Belongs to parameters group
-
Automated Train Operation (ATO)
(
1.1.1.3.13
|
1.2.1.1.10
)
- Data Format
-
- Data Presentation
-
Concept
- Taxonomy Reference:
-
ATO Communication System
-
Values :
-
- Flags
-
- Applicability Flags:
- Y/N/NYA
- Validation
-
- Dependencies:
- Applicable when 'ATO Grade of Automation' is applicable
- Validation Rules:
-
Ato Communication System Skos
Comment: Supported ATO communication systems from trackside.
Message: atoCommunicationSystem (1.1.1.3.13.3, 1.2.1.1.10.3): The track or subset with common characteristics {$this} (label {?label}) has a value {?concept} that is not one of the predefined values and cannot be converted into a SKOS concept on this list: http://data.europa.eu/949/concepts/ato-commsys/ATOCommSystem.
-
Ato Communication System
Comment: Supported ATO communication systems from trackside.
Message: atoCommunicationSystem (1.1.1.3.13.3, 1.2.1.1.10.3): The track or subset with common characteristics must have a ATO communication system value that is an IRI.
- OPE TSI References
-
- Appendix D2 Index
- 3.4.9
- Additional Information
-
- General explanation:
- ATO system communication system to the specification referenced in TSI CCS (4.2.4 & 4.2.19).
Parameter only applicable when ETCS Baseline > 4 MR1 and ATO is implemented
Name of signal
DP
IRI: http://data.europa.eu/949/signalId
- Parameter of
-
Signal
- General Information
-
- Number:
- 1.1.1.3.14.1
- 1.2.1.0.8.1
- XML Name:
- SIG_Name
- Deadline:
- 12 months after publication of Article 7 Guide
- Belongs to parameters group
-
Signal
(
1.1.1.3.14
)
-
Identifier
- Data Format
-
- Data Presentation
-
String
- Flags
-
- Applicability Flags:
- Y/N/NYA
- Validation
-
- Validation Rules:
-
Signal Id
Comment: Operational identifier of the signal (on the track or in OP), as in the operational and maintenance provisions.
Message: signalId (1.1.1.3.14.1, 1.2.1.0.8.1): A Signal may have at most one signal id and it must be represented as a String. This error may be due to having more than one value or having a value that is not a string
- OPE TSI References
-
- Appendix D2 Index
- 2.3.3
- Additional Information
-
- General explanation:
- Operational identifier of the signal (on the track or in OP), as in the operational and maintenance provisions.
Type of signal
OP
IRI: http://data.europa.eu/949/signalType
- Parameter of
-
Signal
-
Subset with common characteristics
- General Information
-
- Number:
- 1.1.1.3.14.2
- 1.2.1.0.8.2
- XML Name:
- SIG_Type
- Deadline:
- 12 months after publication of Article 7 Guide
- Belongs to parameters group
-
Signal
(
1.1.1.3.14
)
- Data Format
-
- Data Presentation
-
Concept
- Taxonomy Reference:
-
Types of Signals
-
Values :
-
| Code |
Value |
| 01 |
Home Signal |
| 02 |
Intermediate Signal |
| 03 |
Group Intermediate Signal |
| 04 |
Exit Signal |
| 05 |
Group Exit Signal |
| 06 |
Block Signal |
| 07 |
Automatic Block Signal |
| 08 |
Protection Signal |
| 09 |
Group Protection Signal |
| 10 |
Fixed Speed Home Signal |
- Flags
-
- Applicability Flags:
- Y/N/NYA
- Validation
-
- Validation Rules:
-
Signal Type
Comment: Signalling information for Route Book compilation.
Message: signalType (1.1.1.3.14.2, 1.2.1.0.8.2): The signal type must be represented as an IRI.This error may be due to having a value that is not an IRI.
-
Signal Type Skos
Comment: Signalling information for Route Book compilation.
Message: Indication of the signalType (1.1.1.3.14.2, 1.2.1.0.8.2): The signal {$this} has a value {?concept} that is not one of the predefined values and cannot be converted into a SKOS concept on this list: http://data.europa.eu/949/concepts/signal-types/.
- OPE TSI References
-
- Appendix D2 Index
- 2.3.3
- Additional Information
-
- General explanation:
- Indicates what function the signal (on the track or in OP) executes in relation to the track/switches.
Signal orientation
OP
IRI: http://data.europa.eu/949/signalOrientation
- Parameter of
-
Signal
-
Subset with common characteristics
- General Information
-
- Number:
- 1.1.1.3.14.3
- 1.2.1.0.8.3
- XML Name:
- SIG_LocDir
- Deadline:
- 12 months after publication of Article 7 Guide
- Belongs to parameters group
-
Signal
(
1.1.1.3.14
)
- Data Format
-
- Data Presentation
-
Concept
- Taxonomy Reference:
-
Directions of the orientation of a railway element
-
Values :
-
| Code |
Value |
| 00 |
Normal |
| 01 |
Opposite |
| 02 |
Both |
- Flags
-
- Applicability Flags:
- Y/N/NYA
- Validation
-
- Validation Rules:
-
Signal Orientation
Comment: Indication if the signal (on the track or in OP) is applicable for operation on normal, opposite track direction or if it contains bidirectionally valid information (radio-based system only).
Message: signalOrientation (1.1.1.3.14.3, 1.2.1.0.8.3): A Signal may have an orientation and it must be represented as an IRI. This error may be due to having a value that is not an IRI.
-
Signal Orientation Skos
Comment: Indication if the signal (on the track or in OP) is applicable for operation on normal, opposite track direction or if it contains bidirectionally valid information (radio-based system only).
Message: Indication of the signalOrientation (1.1.1.3.14.3, 1.2.1.0.8.3 ):): The signal {$this} has a value {?concept} that is not one of the predefined values and cannot be converted into a SKOS concept on this list: http://data.europa.eu/949/concepts/track-running-directions/TrackRunningDirections.
- OPE TSI References
-
- Appendix D2 Index
- 2.2.3
- Additional Information
-
- General explanation:
- Indication if the signal is applicable for operation on normal, opposite track direction or if it contains bidirectionally valid information (radio-based system only).
The position of the signal is given in relation to a line reference, using the era:netReference property. In general it represents the kilometric point on the main line where the signal is positioned, or a distance from an origin point, when there are no kilometric posts available on the tracks/sidings. See the example.
-
- Example:
- @prefix era: <http://era.europa.eu/949/> .
@prefix era-orient: <http://data.europa.eu/949/concepts/orientations/> .
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
era:signal1 a era:Signal ;
#signal's position
era:netReference [
a era:NetPointReference ;
era:hasLrsCoordinate [
a era:LinearPositioningSystemCoordinate ;
era:kmPost era:kp5 ;
era:offsetFromKilometricPost 231;
rdfs:label "5+231"@en ;
]
];
#signal's orientation (Normal)
era:signalOrientation era-orient:00.
era:kp5 a era:KilometricPost ;
era:hasLRS [
a era:LinearPositioningSystem ;
era:lineId "National line 1"
] ;
era:kmPostName "km 5" ;
era:measuredDistance 4995 .
Relative distance of the danger point
DP
IRI: http://data.europa.eu/949/relativeDistanceDangerPoint
- Parameter of
-
Signal
- General Information
-
- Number:
- 1.1.1.3.14.4
- 1.2.1.0.8.4
- XML Name:
- SIG_RelDistDP
- Deadline:
- 12 months after publication of Article 7 Guide
- Belongs to parameters group
-
Signal
(
1.1.1.3.14
)
- Data Format
-
- Data Presentation
-
Integer
- Format:
- NNN
- Unit of Measure:
-
Metre
- Flags
-
- Applicability Flags:
- Y/N/NYA
- Validation
-
- Validation Rules:
-
Relative Distance Danger Point
Comment: Distance in meters to the danger point.
Message: relativeDistanceDangerPoint (1.1.1.3.14.4, 1.2.1.0.8.4): The distance in meters to the danger point must be represented as an integer and follow the pattern [NNN].This error may be due to having a value that is not an integer or that does not follow the pattern.
- OPE TSI References
-
- Appendix D2 Index
- 2.2.3
- Additional Information
-
- General explanation:
- Danger point is defined in ERTMS/ETCS - Glossary of Terms and Abbreviations - version 4.0.0 - date 05/07/2023. For installations without ERTMS, the signalling definition is equivalent.
See: TSI OPE Appendix D2 (2.3.3), the danger point relative distance from the signal itself.
Existence of rules and restrictions of a strictly local nature
DP
IRI: http://data.europa.eu/949/localRulesOrRestrictions
- Parameter of
-
Operational Point
-
Running track
-
Subset with common characteristics
- General Information
-
- Number:
- 1.1.1.4.1
- 1.2.3.1
- XML Name:
- RUL_LocalRulesOrRestrictions
- Deadline:
- 1 January 2021
- Belongs to parameters group
-
Rules and restrictions
(
1.1.1.4
|
1.2.3
)
- Data Format
-
- Data Presentation
-
Boolean
- Format:
- Y/N
- Flags
-
- Applicability Flags:
- Y/N
- Validation
-
- Validation Rules:
-
Local Rules Or Restrictions
Comment: Existence of rules and restrictions of a strictly local nature.
Message: localRulesOrRestrictions (1.1.1.4.1, 1.2.3.1): Each track or subset with common characteristics may define the existence of rules and restrictions of a strictly local nature. This error is due to having more than one value or having a value that is not Y/N (boolean).
- Additional Information
-
- General explanation:
- There is a general obligation for Member States to notify existing national rules but: Member States may decide not to notify rules and restrictions of a strictly local nature. In such cases, Member States shall mention those rules and restrictions in the registers of infrastructure.
In this eventuality, this parameter allows the IM accordingly to its Member State decision to declare the existence of such rules and to provide them with the parameter 'Documents regarding the rules or restrictions of a strictly local nature available by the IM'
Documents regarding the rules or restrictions of a strictly local nature available by the IM
OP
IRI: http://data.europa.eu/949/localRulesOrRestrictionsDoc
- Parameter of
-
Operational Point
-
Running track
-
Subset with common characteristics
- General Information
-
- Number:
- 1.1.1.4.2
- 1.2.3.2
- XML Name:
- RUL_LocalRulesOrRestrictionsDocRef
- Deadline:
- 1 January 2021
- Belongs to parameters group
-
Rules and restrictions
(
1.1.1.4
|
1.2.3
)
- Data Format
-
- Data Presentation
-
ERA Document
- Flags
-
- Applicability Flags:
- Y/N
- Validation
-
- Dependencies:
- Mandatory to provide at least a document if parameter "Existence of rules and restrictions of a strictly local nature" value is boolean "Yes"
- Validation Rules:
-
Local Rules Or Restrictions Doc
Comment: Electronic document available from the IM stored by the Agency providing additional information.
Message: localRulesOrRestrictionsDoc (1.1.1.4.2, 1.2.3.2): The track or subset with common characteristics has a value of the document regarding the rules or restrictions of a strictly local nature available by the IM, that must be a Document.
- Additional Information
-
- General explanation:
- The value of this parameter should be either a reference to a file name or an external link to a document.
If a file name is provided, the Infrastructure Manager (IM) must upload a document with the same file name using the "Reference Documents Management" functionality in the RINF application. The document must be in electronic format and available in two official EU languages. In this case, the parameter value must be repeated for each document.
If an external link is provided, the IM must ensure that the document is available at the provided link.
IOD: Notification of national rules Art 14. 11. Member States may decide not to notify rules and restrictions of a strictly local nature. In such cases, Member States shall mention those rules and restrictions in the registers of infrastructure referred to in Article 49
List of vehicle types already identified as compatible with Traffic load and load carrying capacity of infrastructure and train detection systems
OP
IRI: http://data.europa.eu/949/vehicleTypesCompatibleTrafficLoad
- Parameter of
-
Subset with common characteristics
- General Information
-
- Number:
- 1.1.1.5.1
- XML Name:
- RCC_vehicleTypesCompatibleTrafficLoad
- Deadline:
- 12 months after publication of Article 7 Guide
- Belongs to parameters group
-
Vehicles for which Route compatibility is verified
(
1.1.1.5
)
- Data Format
-
- Data Presentation
-
ERA Document
-
Vehicle Type
- Flags
-
- Applicability Flags:
- Y/N/NYA
List of vehicles already identified as compatible with Traffic load and load carrying capacity of infrastructure and train detection systems
OP
IRI: http://data.europa.eu/949/vehiclesCompatibleTrafficLoad
- Parameter of
-
Subset with common characteristics
- General Information
-
- Number:
- 1.1.1.5.2
- XML Name:
- RCC_vehiclesCompatibleTrafficLoad
- Deadline:
- 12 months after publication of Article 7 Guide
- Belongs to parameters group
-
Vehicles for which Route compatibility is verified
(
1.1.1.5
)
- Data Format
-
- Data Presentation
-
ERA Document
-
Vehicle
- Flags
-
- Applicability Flags:
- Y/N/NYA
Name of operational point
DP
IRI: http://data.europa.eu/949/opName
- Parameter of
-
Operational Point
- General Information
-
- Number:
- 1.2.0.0.0.1
- XML Name:
- OPName
- Deadline:
- In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
- Belongs to parameters group
-
Operational point generic information
(
1.2.0.0.0
)
- Data Format
-
- Data Presentation
-
String
- Flags
-
- Applicability Flags:
- Y
- Validation
-
- Validation Rules:
-
Op Name
Comment: Name normally related to the town or village or to traffic control purpose.
Message: opName (1.2.0.0.0.1): There has to be exactly one opName, and it must be represented as a String.
- OPE TSI References
-
- Appendix D2 Index
- 2.3.1
- Additional Information
-
- General explanation:
- Name of OP may not always exist in common use. In such case IM should propose a name for OP.
Unique OP ID
DP
IRI: http://data.europa.eu/949/uopid
- Parameter of
-
Operational Point
- General Information
-
- Number:
- 1.2.0.0.0.2
- XML Name:
- UniqueOPID
- Deadline:
- In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
- Belongs to parameters group
-
Operational point generic information
(
1.2.0.0.0
)
-
Identifier
- Data Format
-
- Data Presentation
-
String
- Format:
- CCAAAAAAAAAA
The first part CC is the country code in two-letter system of ISO.
The second part is alphanumeric OP code within the MS.
For example, an OP code could be current abbreviation of name used in route books.
In case of borders point, the code is to be selected in the corresponding list in annex 5.1
- Flags
-
- Applicability Flags:
- Y
- Validation
-
- Validation Rules:
-
Border Point Valid Code
Comment: Code composed of country code and alphanumeric OP code.
Message: uopid (1.2.0.0.0.2): The OperationalPoint {$this} with id {?uopid} and label {?opLabel} is a border point that either does not point to a ReferenceBorderPoint or does not have a value for uopid that matches the id of its referenced border point.
-
Uopid P
Comment: Code composed of country code and alphanumeric OP code.
Message: uopid (1.2.0.0.0.2): This error is due to having more than one op id, having a value that is not a string, or having a value that does not follow the pattern where the first part ‘AA’ is the country code in two-letter system of ISO and the second part is the alphanumeric OP code within the MS.
-
Uopid Min
Comment: Enforce minCount considering all instances that are not border points.
Message: uopid (1.2.0.0.0.2): The OperationalPoint {$this} with label {?opLabel} does not have a value for uopid.
- OPE TSI References
-
- Appendix D2 Index
- 2.2.2
- Additional Information
-
- General explanation:
- Explanation on data presentation: The first two characters represent the country code in two-letter system of ISO.
The second part AAAAAAAAAA is maximum 10 Characters String corresponding to OP code within the MS.
'LUAB4' or 'LUAB46TH-G' or 'LUAB4/-_ERT7' are accepted by the validation process.
In case of borders point , the code is to be selected in the corresponding list in annex 5.1 (this first part AA is EU. The second part is AAAAAAAAAA ). Any OP ID that is not referenced in the annex 5.1 will not be accepted by the validation process.
In case of domestic borders point , the code will be selected in the corresponding list in annex 5.2 that will be developed later.
Any OP ID that is not referenced in the annex 5.1 will not be accepted by the validation process.
The provided OP ID must be unique within each Member State. The validation has to be made nationally by NRE. The exceptions are Border point and domestic border point that must be referenced in annex 5.1.
Primary location
OP
IRI: http://data.europa.eu/949/primaryLocation
- Parameter of
-
Infrastructure element
- General Information
-
- Number:
- 1.2.0.0.0.3
- XML Name:
- OPTafTapCode
- Deadline:
- In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
- Belongs to parameters group
-
Operational point generic information
(
1.2.0.0.0
)
- Data Format
-
- Data Presentation
-
Primary Location
- Flags
-
- Applicability Flags:
- Y/N
- Validation
-
- Dependencies:
- Applicable only in case when a primary location exists
- Validation Rules:
-
Primary Location
Comment: Primary location code developed for information exchange in accordance with the TSIs relating to the telematics applications subsystem.
Message: primaryLocation: The infrastructure element has a primaryLocation reference that must be an IRI that refers to an instance of PrimaryLocation.
- OPE TSI References
-
- Appendix D2 Index
- 2.2.2
Type of operational point
OP
IRI: http://data.europa.eu/949/opType
- Parameter of
-
Operational Point
- General Information
-
- Number:
- 1.2.0.0.0.4
- XML Name:
- OPType
- Deadline:
- In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
- Belongs to parameters group
-
Operational point generic information
(
1.2.0.0.0
)
- Data Format
-
- Data Presentation
-
Concept
- Taxonomy Reference:
-
Operational Point Types
-
Values :
-
| Code |
Value |
| 10 |
Station |
| 20 |
Small station |
| 30 |
Passenger terminal |
| 40 |
Freight terminal |
| 50 |
Depot or workshop |
| 60 |
Train technical services |
| 70 |
Passenger stop |
| 80 |
Junction |
| 90 |
Border point |
| 100 |
Shunting yard |
| 110 |
Technical change |
| 120 |
Switch |
| 130 |
Private siding |
| 140 |
Domestic border point |
| 150 |
Over crossing |
- Flags
-
- Applicability Flags:
- Y
- Validation
-
- Validation Rules:
-
Op Type P
Comment: Type of facility in relation to the dominating operational functions.Each existing case has to be approximated to the one of the above defined types by including size, importance and dominating functions. It is most important to recognize the most important role of specific OP in the network. That is why only one type for one OP is permitted.
Message: opType (1.2.0.0.0.4): Each Operational Point must have exactly one type. This error may be due to having an OP with no type or with more than one type, or its value is not an IRI.
-
Op Type Skos
Comment: Type of facility in relation to the dominating operational functions.
Each existing case has to be approximated to the one of the above defined types by including size, importance and dominating functions. It is most important to recognize the most important role of specific OP in the network. That is why only one type for one OP is permitted.
Message: Type of operational point (1.2.0.0.0.4): The OP {$this} (label {?opLabel}) has a value {?concept} that is not one of the predefined values and cannot be converted into a SKOS concept on this list: http://data.europa.eu/949/concepts/op-types/OperationalPointTypes.
- OPE TSI References
-
- Appendix D2 Index
- 2.2.2
- Additional Information
-
- General explanation:
- Each existing case has to be approximated to the one of the above defined types by including size, importance and dominating functions. It is most important to recognize the most important role of specific OP in the network. That is why only one type for one OP is permitted.
For purpose of RINF, there were defined the following types of OPs:
1. Station - large or major railway node with several functions, important for international traffic, basic for national railway system;
2. Passenger terminal - station with dominating function of service for passenger traffic, serving as a central hub for passengers, often integrating rail operations with intermodal transport networks and large-scale passenger facilities, including ticketing, waiting areas, and other passenger services;
3. Freight terminal - station dominantly serving for loading and unloading of freight trains;
4. Depot or workshop - group of tracks used by depot or workshop for RST maintenance;
5. Train technical services - group of tracks for servicing trains (parking, washing, etc.);
6. Passenger stop - or halts - small OP consisting of at least one platform, normally serving mostly for local passenger services, without routing, dispatching, or train management facilities;
7. Junction - OP consisting of at least one turnout, normally used mostly for changing direction of trains, with reduced or not existing other functions;
8. Border point - located in the point where a border between MSs meets a railway line;
9. Shunting yard - group of tracks used for shunting trains, mostly related to freight traffic;
10. Switch - OP consisting of only one switch and the area around it, delimited and protected by entry signals, normally used for changing direction of trains, with reduced or not existing other functions;
11. Domestic border point - designated location on the main lines where the infrastructure responsibilities transition between IMs.
Type of track gauge changeover facility
DP
IRI: http://data.europa.eu/949/opTypeGaugeChangeover
- Parameter of
-
Operational Point
- General Information
-
- Number:
- 1.2.0.0.0.4.1
- XML Name:
- OPTypeGaugeChangeover
- Deadline:
- 16 January 2020
- Belongs to parameters group
-
Operational point generic information
(
1.2.0.0.0
)
- Data Format
-
- Data Presentation
-
String
- Flags
-
- Applicability Flags:
- Y/N
- Validation
-
- Validation Rules:
-
Op Type Gauge Changeover
Comment: Type of track gauge changeover facility.
Message: opTypeGaugeChangeover (1.2.0.0.0.4.1): The Operational Point must have at most one value of opTypeGaugeChangeover and its type must be a string.
- OPE TSI References
-
- Part of RCC Algorithm:
- true
Kilometer number
DP
IRI: http://data.europa.eu/949/kilometer
- Parameter of
-
Kilometric Post
- General Information
-
- Number:
- 1.2.0.0.0.6
- XML Name:
- OPRailwayLocation
- Deadline:
- In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
- Belongs to parameters group
-
Tunnel
(
1.1.1.1.8
|
1.2.1.0.5
|
1.2.2.0.5
)
-
Signal
(
1.1.1.3.14
)
- Data Format
-
- Data Presentation
-
Double
- Unit of Measure:
-
Kilometre
- Flags
-
- Applicability Flags:
- Y/N
- Validation
-
- Validation Rules:
-
Kilometer
Comment: Distance measured in kilometers from the origin of a national railway line/route.
Message: kilometer (1.1.1.1.8.12.1, 1.1.1.1.8.13.1, 1.1.1.3.14.3, 1.1.1.3.14.7, 1.2.0.0.0.6, 1.2.1.0.5.10.1, 1.2.1.0.5.11.1, 1.2.1.0.8.3, 1.2.2.0.5.10.1, 1.2.2.0.5.9.1): The kilometer must be represented as a double number.
- OPE TSI References
-
- Appendix D2 Index
- 2.2.2
- Additional Information
-
- General explanation:
- For walkways: Value provided in Kilometric point of the start of the walkway and the length in m. Repeatable values for each location.
For rescue points: Value provided in Kilometric point of the start of the point of evacuation and rescue point and the length in m. Repeatable values for each location.
For signals: Relative position to the line identified under parameter 1.1.0.0.0.2, given in km ([reference point, via era:referent] / [NNN.NNN] ).
Schematic overview of the operational point
DP
IRI: http://data.europa.eu/949/schematicOverviewOP
- Parameter of
-
Operational Point
- General Information
-
- Number:
- 1.2.0.0.0.7.1
- Deadline:
- 12 months after publication of Article 7 Guide
- Belongs to parameters group
-
Operational point generic information
(
1.2.0.0.0
)
- Data Format
-
- Data Presentation
-
Any Uri
- Flags
-
- Applicability Flags:
- Y/N/NYA
- OPE TSI References
-
- Appendix D2 Index
- 2.1
Digital schematic overview
DP
IRI: http://data.europa.eu/949/digitalSchematicOverview
- Parameter of
-
Operational Point
- General Information
-
- Number:
- 1.2.0.0.0.7.2
- Deadline:
- 12 months after publication of Article 7 Guide for OP tracks
- Belongs to parameters group
-
Operational point generic information
(
1.2.0.0.0
)
- Data Format
-
- Data Presentation
-
Wkt Literal
- Flags
-
- Applicability Flags:
- Y/N/NYA
- Validation
-
- Validation Rules:
-
Digital Schematic Overview
Comment: Diagrammatic representation of the operational point in Well Known Text polyline
Message: digitalSchematicOverview (1.2.0.0.0.7.2): The Operational Point has a digitalSchematicOverview reference that must be a Well Known Text literal.
- OPE TSI References
-
- Appendix D2 Index
- 2.1
Diesel or other thermal traction allowed
DP
IRI: http://data.europa.eu/949/dieselThermalAllowed
- Parameter of
-
Subset with common characteristics
-
Tunnel
- General Information
-
- Number:
- 1.2.1.0.5.9
- XML Name:
- ITU_DieselThermAllowed
- Deadline:
- 1 January 2021
- Belongs to parameters group
-
Tunnel
(
1.1.1.1.8
|
1.2.1.0.5
|
1.2.2.0.5
)
- Data Format
-
- Data Presentation
-
Boolean
- Flags
-
- Applicability Flags:
- Y/N
- Validation
-
- Validation Rules:
-
Diesel Thermal Allowed
Comment: Indication whether it is allowed to use diesel or other thermal traction in the tunnel.
Message: dieselThermalAllowed (1.2.1.0.5.9): A Tunnel may have an indication about the permission of thermal traction. This error may be due to having a tunnel with more than one dieselThermalAllowed declaration or having a value type different than Y/N (boolean).
Existence of platform assistance for starting train
DP
IRI: http://data.europa.eu/949/assistanceStartingTrain
- Parameter of
-
Platform edge
-
Subset with common characteristics
- General Information
-
- Number:
- 1.2.1.0.6.6
- XML Name:
- IPL_AssistanceStartingTrain
- Deadline:
- In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
- Belongs to parameters group
-
Platform
(
1.2.1.0.6
)
- Data Format
-
- Data Presentation
-
Boolean
- Flags
-
- Applicability Flags:
- Y/N
- Validation
-
- Validation Rules:
-
Assistance Starting Train
Comment: Indication of existence of equipment or staff supporting the train crew in starting the train.
Fixed equipment (for example mirrors or CCTV cameras) or station staff indicating to train crew or driver when to close doors and whether this has been done successfully.
Message: assistanceStartingTrain (1.2.1.0.6.6): Each Platform must have at most one assistanceStartingTrain declaration. This error may be caused due to having a platform with having more than one assistanceStartingTrain, or its value is not Y/N (boolean).
Range of use of the platform boarding aid
DP
IRI: http://data.europa.eu/949/areaBoardingAid
- Parameter of
-
Platform edge
-
Subset with common characteristics
- General Information
-
- Number:
- 1.2.1.0.6.7
- XML Name:
- IPL_AreaBoardingAid
- Deadline:
- In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
- Belongs to parameters group
-
Platform
(
1.2.1.0.6
)
- Data Format
-
- Data Presentation
-
Integer
- Unit of Measure:
-
Millimetre
- Flags
-
- Applicability Flags:
- Y/N
- Validation
-
- Validation Rules:
-
Area Boarding Aid
Comment: Information of the train access level for which the boarding aid can be used.
Message: areaBoardingAid (1.2.1.0.6.7): Each Platform must have at most one areaBoardingAid value. This error may be caused due to having a platform with multiple areaBoardingAid values or having a value that is not an integer.
- Additional Information
-
- General explanation:
- Information of the train access level for which the boarding aid can be used. Data is presented as the vertical difference that is overcome by the platform boarding aid in millimetres. The value “0” means that the platform is not equipped with a platform boarding aid.
Permission for charging electric energy storage for traction purposes at standstill
DP
IRI: http://data.europa.eu/949/permissionChargingElectricEnergyTractionStandstill
- Parameter of
-
Contact Line System
- General Information
-
- Number:
- 1.2.1.0.7.1
- Deadline:
- Contrary to the Regulation, the deadline is not 30 June 2024 at the latest, but 12 months after publication of Article 7 Guide
- Belongs to parameters group
-
Contact line system
(
1.1.1.2.2
)
- Data Format
-
- Data Presentation
-
Boolean
- Flags
-
- Applicability Flags:
- Y/N
- Validation
-
- Validation Rules:
-
Permission Charging Electric Energy Traction Standstill
Comment: Indication if charging electric energy storage for traction purposes at standstill is permitted
Message: permissionChargingElectricEnergyTractionStandstill (1.2.1.0.7.1): The contact line system defines if charging electric energy storage for traction purposes at standstill is permitted. This error is due to having more than one value for this property or having a value that is not Y/N (boolean).
Permitted conditions for charging electric energy storage for traction purposes at standstill
DP
IRI: http://data.europa.eu/949/conditionsChargingElectricEnergyStorage
- Parameter of
-
Contact Line System
- General Information
-
- Number:
- 1.2.1.0.7.2
- Deadline:
- Contrary to the Regulation, the deadline is not 30 June 2024 at the latest, but 12 months after publication of Article 7 Guide
- Belongs to parameters group
-
Contact line system
(
1.1.1.2.2
)
- Data Format
-
- Data Presentation
-
Any Uri
- Flags
-
- Applicability Flags:
- Y/N
- Validation
-
- Validation Rules:
-
Conditions Charging Electric Energy Storage
Comment: Indication if charging electric energy storage for traction purposes at standstill is permitted
Message: conditionsChargingElectricEnergyStorage (1.2.1.0.7.2): The contact line system defines the permitted conditions for charging electric energy storage for traction purposes at standstill. This error is due to having more than one value for this property or having a value that is not an URI.
Specific constraints imposed by the GSM-R network operator on ETCS on-board units only able to operate in circuit-switch
OP
IRI: http://data.europa.eu/949/gsmrConstraintsOperateOnlyInCircuitSwitch
- Parameter of
-
Running track
-
Subset with common characteristics
- General Information
-
- Number:
- 1.2.1.1.2.12
- XML Name:
- CRG_ConstraintsCS
- Deadline:
- 12 months after publication of Article 7 Guide
- Belongs to parameters group
-
TSI compliant radio (RMR)
(
1.1.1.3.3
|
1.2.1.1.2
)
- Data Format
-
- Data Presentation
-
Concept
- Taxonomy Reference:
-
GSM-R Constraints on CS-equiped trains
-
Values :
-
| Code |
Value |
| 00 |
Placeholder |
- Flags
-
- Applicability Flags:
- Y/N/NYA
- Validation
-
- Dependencies:
- GSM-R and ETCS L2 must be installed for this parameter to be applicable. Multiple values are allowed.
- Validation Rules:
-
Gsmr Constraints Operate Only In Circuit Switch Applicability
Comment: GSM-R (parameter 1.1.1.3.3.1) and ETCS L2 (parameter 1.1.1.3.2.1) must be installed for this parameter to be applicable.
Message: gsmrConstraintsOperateOnlyInCircuitSwitch (1.1.1.3.3.10, 1.2.1.1.2.10):The track or subset with common characteristics {$this} ({?label}), has a 'GSM-R version' defined and a 'ETCS level' type selected which makes the gsmrConstraintsOperateOnlyInCircuitSwitch parameter applicable. This error is due to {$this} not having a value for such a parameter.
Identification of siding
DP
IRI: http://data.europa.eu/949/sidingId
- Parameter of
-
Siding
- General Information
-
- Number:
- 1.2.2.0.0.2
- XML Name:
- OPSidingIdentification
- Deadline:
- In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
- Belongs to parameters group
-
Siding
(
1.2.2
)
-
Identifier
- Data Format
-
- Data Presentation
-
String
- Flags
-
- Applicability Flags:
- Y/N
- Validation
-
- Validation Rules:
-
No Repeated Siding Ids
Comment: Each siding shall have unique identification or number within the OP. This number cannot be used for naming any other siding in the same OP.
Message: sidingId (1.2.2.0.0.2):: Each siding shall have unique identification or number within the OP. This number cannot be used for naming any other siding in the same OP. There is a problem with the OP {$this} ({?opLabel}) and sidings {?siding1} ({?siding1Label}) and {?siding2} ({?siding2Label}), since they have the same identifier: {?value}.
-
Siding Id
Comment: Unique siding identification or unique siding number within OP
Message: sidingId (1.2.2.0.0.2): Each siding must have a unique siding identification that is a character string. This error is due to not having a sidingId value, having more than one sidingId value or having a value that is not a string.
- OPE TSI References
-
- Appendix D2 Index
- 2.2.1.4
Usable length of siding
DP
IRI: http://data.europa.eu/949/lengthOfSiding
- Parameter of
-
Siding
- General Information
-
- Number:
- 1.2.2.0.2.1
- XML Name:
- IPP_Length
- Deadline:
- In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
- Belongs to parameters group
-
Siding
(
1.2.2
)
-
Length
- Data Format
-
- Data Presentation
-
Double
- Unit of Measure:
-
Metre
- Flags
-
- Applicability Flags:
- Y/N
- Validation
-
- Validation Rules:
-
Length S
Comment: Total length of the siding/stabling track expressed in meters where trains can be parked safely
Message: lengthOfSiding (1.2.2.0.2.1): Each siding may have a length in meters. This error is due to having more than one length value or having a length that is not a double (real) number or not following the pattern [NNNN].
- OPE TSI References
-
- Part of RCC Algorithm:
- true
-
- Appendix D2 Index
- 3.2.3
Gradient for stabling tracks
DP
IRI: http://data.europa.eu/949/gradient
- Parameter of
-
Siding
-
Subset with common characteristics
- General Information
-
- Number:
- 1.2.2.0.3.1
- XML Name:
- ILL_Gradient
- Deadline:
- In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
- Belongs to parameters group
-
Siding
(
1.2.2
)
- Data Format
-
- Data Presentation
-
Double
- Unit of Measure:
-
- Flags
-
- Applicability Flags:
- Y/N
- Validation
-
- Validation Rules:
-
Gradient
Comment: Maximum value of the gradient expressed in millimeters per meter
Message: gradient (1.2.2.0.3.1): Each siding or subset with common characteristics may have a gradient in millimeters per meter. This error is due to having more than one gradient value or having a gradient that is not a double (real) number.
- OPE TSI References
-
- Part of RCC Algorithm:
- true
Minimum radius of vertical curve
OP
IRI: http://data.europa.eu/949/minimumVerticalRadius
- Parameter of
-
Siding
-
Subset with common characteristics
- General Information
-
- Number:
- 1.2.2.0.3.3
- XML Name:
- ILL_MinRadVertCurve
- Deadline:
- In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
- Belongs to parameters group
-
Siding
(
1.2.2
)
- Data Format
-
- Data Presentation
-
Minimum radius of vertical curve
- Format:
- In RDF: the values points to an instance of era:MinimumVerticalRadius class with 2 properties for the crest and hollow values.
In XML: NNN+NNN
- Unit of Measure:
-
Metre
- Flags
-
- Applicability Flags:
- Y/N
- Validation
-
- Validation Rules:
-
Minimum Vertical Radius
Comment: Indication of types of appearance of track lineside distance indications.
Message: minimumVerticalRadius (1.2.2.0.3.3) : The siding or subset with common characteristics must have at most one value of minimum vertical radius that must be an instace of MinimumVerticalRadius. This error may be due to the track having more than one value or having a value that is not an instance of the class MinimumVerticalRadius.
- Additional Information
-
- General explanation:
- The radius of vertical curves (except for humps in marshalling yards) shall be at least 500 m on a crest or 900 m in a hollow.
Existence of toilet discharge
DP
IRI: http://data.europa.eu/949/hasToiletDischarge
- Parameter of
-
Siding
-
Subset with common characteristics
- General Information
-
- Number:
- 1.2.2.0.4.1
- XML Name:
- ITS_ToiletDischarge
- Deadline:
- In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
- Belongs to parameters group
-
Fixed installations for servicing trains
(
1.2.2.0.4
)
- Data Format
-
- Data Presentation
-
Boolean
- Flags
-
- Applicability Flags:
- Y/N
- Validation
-
- Validation Rules:
-
Has Toilet Discharge
Comment: Indication whether exists and installation for toilet discharge (fixed installation for servicing trains) as defined in INF TSIs
Message: hasToiletDischarge (1.2.2.0.4.1): Each siding or subset with common characteristics may define the existence of a toilet discharge. This error is due to having more than one has toilet discharge value or having a has has toilet discharge value that is not Y/N (boolean).
Existence of external cleaning facilities
DP
IRI: http://data.europa.eu/949/hasExternalCleaning
- Parameter of
-
Siding
-
Subset with common characteristics
- General Information
-
- Number:
- 1.2.2.0.4.2
- XML Name:
- ITS_ExternalCleaning
- Deadline:
- In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
- Belongs to parameters group
-
Fixed installations for servicing trains
(
1.2.2.0.4
)
- Data Format
-
- Data Presentation
-
Boolean
- Flags
-
- Applicability Flags:
- Y/N
- Validation
-
- Validation Rules:
-
Has External Cleaning
Comment: Indication whether exists and installation for external cleaning facility (fixed installation for servicing trains) as defined in INF TSIs
Message: hasExternalCleaning (1.2.2.0.4.2): Each siding or subset with common characteristics may define the existence of an external cleaning facility. This error is due to having more than one has external cleaning value or having a has external cleaning value that is not Y/N (boolean).
Existence of water restocking
DP
IRI: http://data.europa.eu/949/hasWaterRestocking
- Parameter of
-
Siding
-
Subset with common characteristics
- General Information
-
- Number:
- 1.2.2.0.4.3
- XML Name:
- ITS_WaterRestocking
- Deadline:
- In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
- Belongs to parameters group
-
Fixed installations for servicing trains
(
1.2.2.0.4
)
- Data Format
-
- Data Presentation
-
Boolean
- Flags
-
- Applicability Flags:
- Y/N
- Validation
-
- Validation Rules:
-
Has Water Restocking
Comment: Indication whether exists and installation for water restocking (fixed installation for servicing trains) as defined in INF TSIs
Message: hasWaterRestocking (1.2.2.0.4.3): Each siding or subset with common characteristics may define the existence of a water restocking facility. This error is due to having more than one has water restocking value or having a has water restocking value that is not Y/N (boolean).
Existence of refuelling
DP
IRI: http://data.europa.eu/949/hasRefuelling
- Parameter of
-
Siding
-
Subset with common characteristics
- General Information
-
- Number:
- 1.2.2.0.4.4
- XML Name:
- ITS_Refuelling
- Deadline:
- In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
- Belongs to parameters group
-
Fixed installations for servicing trains
(
1.2.2.0.4
)
- Data Format
-
- Data Presentation
-
Boolean
- Flags
-
- Applicability Flags:
- Y/N
- Validation
-
- Validation Rules:
-
Has Refuelling
Comment: Indication whether exists and installation for refuelling (fixed installation for servicing trains) as defined in INF TSIs
Message: hasRefuelling (1.2.2.0.4.4): Each siding or subset with common characteristics may define the existence of a refuelling facility. This error is due to having more than one has refuelling value or having a has refuelling value that is not Y/N (boolean).
Existence of sand restocking
DP
IRI: http://data.europa.eu/949/hasSandRestocking
- Parameter of
-
Siding
-
Subset with common characteristics
- General Information
-
- Number:
- 1.2.2.0.4.5
- XML Name:
- ITS_SandRestocking
- Deadline:
- In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
- Belongs to parameters group
-
Fixed installations for servicing trains
(
1.2.2.0.4
)
- Data Format
-
- Data Presentation
-
Boolean
- Flags
-
- Applicability Flags:
- Y/N
- Validation
-
- Validation Rules:
-
Has Sand Restocking
Comment: Indication whether an installation for sand restocking exists(fixed installation for servicing trains)
Message: hasSandRestocking (1.2.2.0.4.5): Each siding or subset with common characteristics may define the existence of a sand restocking facility. This error is due to having more than one has sand restocking value or having a has sand restocking value that is not Y/N (boolean).
Existence of electric shore supply
DP
IRI: http://data.europa.eu/949/hasElectricShoreSupply
- Parameter of
-
Siding
-
Subset with common characteristics
- General Information
-
- Number:
- 1.2.2.0.4.6
- XML Name:
- ITS_ElectricShoreSupply
- Deadline:
- In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
- Belongs to parameters group
-
Fixed installations for servicing trains
(
1.2.2.0.4
)
- Data Format
-
- Data Presentation
-
Boolean
- Flags
-
- Applicability Flags:
- Y/N
- Validation
-
- Validation Rules:
-
Has Electric Shore Supply
Comment: Indication whether an installation for electric shore supply exists (fixed installation for servicing trains)
Message: hasElectricShoreSupply (1.2.2.0.4.6): Each siding or subset with common characteristics may define the existence of an electric shore supply facility. This error is due to having more than one has electric shore supply value or having a has electric shore supply value that is not Y/N (boolean).
Document with operating restrictions or conditions
OP
IRI: http://data.europa.eu/949/etcsRestrictionsConditionsDoc
- Parameter of
-
Subset with common characteristics
-
Track
- General Information
-
- Belongs to parameters group
-
TSI compliant train protection system (ETCS)
(
1.1.1.3.2
|
1.2.1.1.1
)
- Data Format
-
- Data Presentation
-
ERA Document
- Flags
-
- Applicability Flags:
- Y/N/NYA
- Validation
-
- Dependencies:
- A value has to be provided when ETCS is present (a value is provided on 1.1.1.3.2.1).
- Validation Rules:
-
Etcs Restrictions Conditions Doc
Comment: Indication of the document where restrictions or conditions due to partial compliance with the TSI CCS are described.
Message: etcsRestrictionsConditionsDoc (1.1.1.3.2.6, 1.2.1.1.1.6): The track or subset with common characteristics has a document regarding the rules or restrictions of a strictly local nature available by the IM value that must be a Document.
-
Etcs Restrictions Conditions Doc Applicability
Comment: Only applicable when hasETCSRestricionsConditions is true.
Message: etcsRestrictionsConditionsDoc (1.1.1.3.2.6, 1.2.1.1.1.6):The track or subset with common characteristics {$this} ({?label}), has a 'has ETCS Restricions Condition' value 'true' which makes the etcsRestrictionsConditionsDoc parameter applicable. This error is due to {$this} not having a value for such a parameter.
- Additional Information
-
- General explanation:
- If not `false` (property hasEtcsRestrictionsConditions), a link to the conditions must be provided. The RU has to contact the IM to be informed about these conditions.
These conditions and restrictions of use are considered in section 6.4 of the CCS TSI. They should be described using the template available on Agency website (Certification and deviations - Guidelines for using the ERA template) with the following link.
The value of this parameter should be either a reference to a file name or an external link to a document.
If a file name is provided, the Infrastructure Manager (IM) must upload a document with the same file name using the "Reference Documents Management" functionality in the RINF application. The document must be in electronic format and available in two official EU languages. In this case, the parameter value must be repeated for each document.
If an external link is provided, the IM must ensure that the document is available at the provided link.
ETCS national packet 44 application implemented
OP
IRI: http://data.europa.eu/949/etcsNationalPacket44Function
- Parameter of
-
Subset with common characteristics
-
Track
- General Information
-
- Belongs to parameters group
-
TSI compliant train protection system (ETCS)
(
1.1.1.3.2
|
1.2.1.1.1
)
- Data Format
-
- Data Presentation
-
Concept
- Taxonomy Reference:
-
ETCS national packet 44 application function
-
Values :
-
| Code |
Value |
| 00 |
Placeholder |
- Flags
-
- Applicability Flags:
- Y/N/NYA
- Validation
-
- Dependencies:
- A value has to be provided when ETCS is present (a value is provided on 1.1.1.3.2.1).
- Validation Rules:
-
Etcs National Packet44function
Comment: Link to the implemented functions for national packet 44 applications that are transmitted between track and train.
Message: etcsNationalPacket44Function (1.1.1.3.2.5, 1.2.1.1.1.5): The track or subset with common characteristics must have a ETCS national packet 44 application implemented function value that is an IRI.
-
Etcs National Packet44function Skos
Comment: Link to the implemented functions for national packet 44 applications that are transmitted between track and train.
Message: etcsNationalPacket44Function (1.1.1.3.2.5, 1.2.1.1.1.5): The track or subset with common characteristics {$this} (label {?label}) has a value {?concept} that is not one of the predefined values and cannot be converted into a SKOS concept on this list: http://data.europa.eu/949/concepts/etcs-national-packet-444-functions/ETCSNationalPacket444Functions/.
- Additional Information
-
- General explanation:
- Value can be `false` or a link to the implemented functions.
Packets 44 are the means to transmit data for national applications between train and track and vice versa, using the data transmission facilities included within the ETCS.
NID_XUSER values managed by ERA in a document about ETCS variables available on ERA website.
See: TSI CCS (7.4.3 & 6.2.4.2)
Aggregates
OP
IRI: http://data.europa.eu/949/aggregates
- Parameter of
-
Non-Linear Element
- Data Format
-
- Data Presentation
-
Linear Element
- Validation
-
- Validation Rules:
-
Aggregates
Comment: Specifies the linear elements aggregated by a non-linear element.
Message: aggregates: The non linear element may aggregate only linear elements. This error is due having a value that is not an instance of LinearElement.
Allocation company
OP
IRI: http://data.europa.eu/949/allocationCompany
- Parameter of
-
Subsidiary location
- Data Format
-
- Data Presentation
-
Organisation Role
- Validation
-
- Validation Rules:
-
Allocation Company
Comment: The organisation in charge to allocate the code for the subsidiary location.
Message: allocationCompany: An instance of subsidiary location may have a value for allocation company. This error may be due to having a value that is not an IRI or that does not point to an instance of OrganisationRole.
Applies in both directions
DP
IRI: http://data.europa.eu/949/appliesInBothDirections
- Parameter of
-
Linear Element Section
- Data Format
-
- Data Presentation
-
Boolean
- Validation
-
- Validation Rules:
-
Applies In Both Directions
Comment: Specifies if the section applies in both directions (optional).
Message: appliesInBothDirections: The linear element section specifies if the section applies in both directions (optional). This error is due having a value that is not a boolean.
Applies to direction
OP
IRI: http://data.europa.eu/949/appliesToDirection
- Parameter of
-
Net Point Reference
- Data Format
-
- Data Presentation
-
Concept
- Taxonomy Reference:
-
Directions of the orientation of a railway element
-
Values :
-
| Code |
Value |
| 00 |
Normal |
| 01 |
Opposite |
| 02 |
Both |
- Validation
-
- Validation Rules:
-
Applies To Direction
Comment: The direction relative to the origin of the linear element towards the point reference applies.
Message: appliesToDirection: The net point reference must have an 'applies to direction' value that is an IRI.
-
Applies To Direction Skos
Comment: The direction relative to the origin of the linear element towards the point reference applies.
Message: appliesToDirection: The net point reference {$this} with label {?thisLabel} has a value {?concept} that is not one of the predefined values and cannot be converted into a SKOS concept on this list: http://data.europa.eu/949/concepts/orientations/Directions.
AsWKT
DP
IRI: http://www.opengis.net/ont/geosparql#asWKT
- General Information
-
- Number:
- 1.1.0.0.1.1
- 1.1.1.0.1.1
- 1.1.1.3.14.6
- 1.2.0.0.0.5
- 1.2.1.0.8.5
- XML Name:
- OPGeographicLocation
- Deadline:
- 12 months after publication of Article 7 Guide
- Flags
-
- Applicability Flags:
- Y/N/NYA
- Validation
-
- Validation Rules:
-
As Wkt
Message: geosparql:Geometry. This error may be due to having a Geometry without or with more than one asWKT property or it value is not from the wktLiteral type.
- OPE TSI References
-
- Appendix D2 Index
- 2.1.2
Belongs to
OP
IRI: http://data.europa.eu/949/belongsTo
- Parameter of
-
Infrastructure element
- Data Format
-
- Data Presentation
-
Subset with common characteristics
- Validation
-
- Validation Rules:
-
Belongs To Unique Im
Comment: Each infrastructure element may belong to several common characteristics subsets, and each of them must point to the same infrastructure manager (same organisationCode in the class organisationRole).
Message: belongsTo, organisationCode, infrastructureElement: This error is due to {$this} belonging to several common characteristics subsets, {?subset1Label}, {?subset2Label} that do not point to the same infrastructure manager (different organisationCodes), {?orgCode1}, {?orgCode2}.
-
Belongs To
Comment: Relationship between an infratructure element and a common characteristics subset.
Message: belongsTo: The infratructure element must belong to at least one common characteristics subset, a reference that must be an instance of CommonCharacteristicsSubset. This error is due to not having a value of belongsTo, or having a value that is not an instance of CommonCharacteristicsSubset.
Border point identification
DP
IRI: http://data.europa.eu/949/borderPointId
- Parameter of
-
Reference border point
- General Information
-
- Belongs to parameters group
-
Identifier
- Data Format
-
- Data Presentation
-
String
Carrier linear element
OP
IRI: http://data.europa.eu/949/carrierLinearElement
- Parameter of
-
Orientation
- Data Format
-
- Data Presentation
-
Linear Element
Container handling flag
DP
IRI: http://data.europa.eu/949/containerHandlingFlag
- Parameter of
-
Primary Location
- Data Format
-
- Data Presentation
-
Boolean
- Validation
-
- Validation Rules:
-
Container Handling Flag
Comment: Container handling flag.
Message: containerHandlingFlag : The PrimaryLocation may have a containerHandlingFlag value that is a boolean. This error may be due to the Primary Location having a value that is not a boolean.
Contains
OP
IRI: http://data.europa.eu/949/contains
- Parameter of
-
Subset with common characteristics
- Data Format
-
- Data Presentation
-
Infrastructure element
- Validation
-
- Validation Rules:
-
Contains
Comment: Relationship between a common characteristics subset and an infrastructure element (inverse of belongsTo).
Message: contains: The subset with common characteristics may contain an infrastructure element, a reference that must be an instance of InfrastructureElement. This error is due having a value that is not an instance of InfrastructureElement.
Document URL
DP
IRI: http://data.europa.eu/949/documentUrl
- Parameter of
-
ERA Document
- Data Format
-
- Data Presentation
-
Any Uri
Element A
OP
IRI: http://data.europa.eu/949/elementA
- Parameter of
-
Net Relation
- General Information
-
- Number:
- 1.1.1.0.1.2
- 1.2.4.1
- Data Format
-
- Data Presentation
-
Linear Element
- Validation
-
- Validation Rules:
-
Element A
Comment: References the first topological element in an oriented relation. For example, it may indicate the object that corresponds to a section of line, an operational point or a track inside an operational point connected at start.
Message: elementA: The net relation references the first topological object that must be an instance of a linear element. This error is due having a value that is not an instance of LinearElement.
Element B
OP
IRI: http://data.europa.eu/949/elementB
- Parameter of
-
Net Relation
- General Information
-
- Number:
- 1.1.1.0.1.2
- 1.2.4.1
- Data Format
-
- Data Presentation
-
Linear Element
- Validation
-
- Validation Rules:
-
Element B
Comment: References the second topological linear element in an oriented relation. For example, it may indicate the object that corresponds to a section of line, an operational point or a track inside an operational point connected at end.
Message: elementB: The net relation references the second topological object that must be an instance of a linear element. This error is due having a value that is not an instance of LinearElement.
End offset from the origin.
DP
IRI: http://data.europa.eu/949/endOffsetFromOrigin
- Parameter of
-
Linear Element Section
- Data Format
-
- Data Presentation
-
Double
- Unit of Measure:
-
Metre
- Validation
-
- Validation Rules:
-
End Offset From Origin
Comment: End offset of the section from the origin.
Message: endOffsetFromOrigin: The linear element section specifies the end offset of the section from the origin. This error is due having a value that is not a positive integer.
Ends at
OP
IRI: http://data.europa.eu/949/endsAt
- Parameter of
-
Net Linear Reference
- Data Format
-
- Data Presentation
-
Topological Coordinate
- Validation
-
- Validation Rules:
-
Ends At
Comment: Specifies the ending coordinate of a linear reference.
Message: endsAt: The net linear reference specifies an ending coordinate that must be an instance of a TopologicalCoordinate. This error is due to not having a value, having more than one value or having a value that is not an instance of TopologicalCoordinate.
Freight flag
DP
IRI: http://data.europa.eu/949/freightFlag
- Parameter of
-
Primary Location
- Data Format
-
- Data Presentation
-
Boolean
- Validation
-
- Validation Rules:
-
Freight Flag
Comment: Freight flag.
Message: freightFlag : The PrimaryLocation may have a freightFlag value that is a boolean. This error may be due to the Primary Location having more than one value or having a value that is not a boolean.
Handover point flag
DP
IRI: http://data.europa.eu/949/handoverPointFlag
- Parameter of
-
Primary Location
- Data Format
-
- Data Presentation
-
Boolean
- Validation
-
- Validation Rules:
-
Handover Point Flag
Comment: Handover point flag.
Message: handoverPointFlag : The PrimaryLocation may have a handoverPointFlag value that is a boolean. This error may be due to the Primary Location having a value that is not a boolean.
Has Beginning
OP
IRI: http://www.w3.org/2006/time#hasBeginning
- Parameter of
-
Temporal entity
- General Information
-
- Belongs to parameters group
-
Has Time
- Data Format
-
- Data Presentation
-
Time instant
- Validation
-
- Validation Rules:
-
Has Beginning
Comment: Applicability interval defines the date interval in which a characteristic of an infrastructure element is applicable.
Message: hasBeginning: An instance of parameter applicability must have exactly one value of the beginning of the interval in which it is applicable. This error may be due to not having a value, having more than one value, having a value that is not an IRI or is not a time:Instant.
Has bridge
DP
IRI: http://data.europa.eu/949/hasBridge
- Parameter of
-
Running track
- Data Format
-
- Data Presentation
-
Boolean
- Validation
-
- Validation Rules:
-
Has Bridge
Comment: Whether or not a track is associated with a bridge.
Message: hasBridge: The track specifies if it is associated with a bridge and the value must be boolean. This error is due to the value not being Y/N (boolean)
Has End
OP
IRI: http://www.w3.org/2006/time#hasEnd
- Parameter of
-
Temporal entity
- General Information
-
- Belongs to parameters group
-
Has Time
- Data Format
-
- Data Presentation
-
Time instant
- Validation
-
- Validation Rules:
-
Has End
Comment: Applicability interval defines the date interval in which a characteristic of an infrastructure element is applicable.
Message: hasEnd: An instance of parameter applicability must have exactly one value of the end of the interval in which it is applicable. This error may be due to not having a value, having more than one value, having a value that is not an IRI or is not a time:Instant.
Has line referencing system coordinate
OP
IRI: http://data.europa.eu/949/hasLrsCoordinate
- Parameter of
-
Net Point Reference
- Data Format
-
- Data Presentation
-
Linear Positioning System Coordinate
- Validation
-
- Validation Rules:
-
Has Lrs Coordinate
Comment: Specifies the LRS coordinate associated with a topological coordinate.
Message: hasLrsCoordinate: The net point reference specifies an LRS coordinate that must be an instance of a LinearPositioningSystemCoordinate and that in turn references a LinearPositioningSystem. This error is due to having a value that is not a LinearPositioningSystemCoordinate that in turn references a LinearPositioningSystem.
Has linear referencing system
OP
IRI: http://data.europa.eu/949/hasLRS
- Parameter of
-
Kilometric Post
- Data Format
-
- Data Presentation
-
Linear Positioning System
- Validation
-
- Validation Rules:
-
Has Lrs Coordinate
Comment: Specifies the LRS coordinate associated with a topological coordinate.
Message: hasLrsCoordinate: The net point reference specifies an LRS coordinate that must be an instance of a LinearPositioningSystemCoordinate and that in turn references a LinearPositioningSystem. This error is due to having a value that is not a LinearPositioningSystemCoordinate that in turn references a LinearPositioningSystem.
Has organisation role
OP
IRI: http://data.europa.eu/949/hasOrganisationRole
- Parameter of
-
Organisation Role
- Data Format
-
- Data Presentation
-
Concept
- Taxonomy Reference:
-
Organisation roles
-
Values :
-
| Code |
Value |
| Applicant |
Applicant |
| EC |
European Commission |
| ECM |
Entity in charge of maintenance |
| ECM-b |
ECM outsourcing the function provided for in Article 14(3), point (b) of Directive (EU) 2016/798 |
| ECM-c |
ECM outsourcing the function defined in Article 14(3), point (c) of Directive (EU) 2016/798 |
| ECM-d |
ECM outsourcing the function defined in Article 14(3), point (d) of Directive (EU) 2016/798 |
| ERA |
European Union Agency for Railways |
| EUBody |
EU Body |
| IM |
Infrastructure Manager |
| IM-1 |
Infrastructure manager operating railway lines (including sidings and stations operations) |
| IM-2 |
Infrastructure manager operating terminals (including sidings and stations operations) |
| Keeper |
Railway Vehicle Keeper |
| Manufacturer |
Manufacturer |
| MWS |
Maintenance workshop |
| MWS-b |
MWS performing the function defined in Article 14(3), points (b) of Directive (EU) 2016/798 |
| MWS-c |
MWS performing the function defined in Article 14(3), points (c) of Directive (EU) 2016/798 |
| MWS-d |
MWS performing the function defined in Article 14(3), points (d) of Directive (EU) 2016/798 |
| NSA |
National safety authority |
| Owner |
Railway Vehicle Owner |
| RU |
Railway Undertaking |
| RU-1 |
Railway Undertaking operating passenger trains |
| RU-2 |
Railway Undertaking operating high speed passenger trains |
| RU-3 |
Railway Undertaking operating freight trains |
| RU-4 |
Railway Undertaking operating dangerous goods freight trains |
| RU-5 |
Railway Undertaking operating terminals |
- Validation
-
- Validation Rules:
-
Has Organisation Role
Comment: The role played in an n-ary relationship between a Body and a specific concept in the concept scheme of organisation roles.
Message: hasOrganisationRole: The organisation role must be represented as an IRI. This error may be due to not having a value, having more than one value, or having a value that is not an IRI.
-
Has Organisation Role Skos
Comment: The role played in an n-ary relationship between a Body and a specific concept in the concept scheme of organisation roles.
Message: Indication of the hasOrganisationRole: The OrganisationRole {$this} has a value {?concept} that is not one of the predefined values and cannot be converted into a SKOS concept on this list: http://data.europa.eu/949/concepts/organisation-roles/.
Has orientation
OP
IRI: http://data.europa.eu/949/hasOrientation
- Parameter of
-
Signal
- Data Format
-
- Data Presentation
-
Orientation
Has part
OP
IRI: http://data.europa.eu/949/hasPart
- Parameter of
-
Infrastructure element
- Data Format
-
- Data Presentation
-
Infrastructure element
- Validation
-
- Validation Rules:
-
Has Part
Comment: Indicates that an infrastructure element is composed of one or more other (distinct) infrastructure elements.
Message: hasPart: The InfrastructureElement must have a hasPart reference that is an IRI that refers to an instance of InfrastructureElement. This error is due to not having a value or having a value that is not an instance of InfrastructureElement.
-
Has Part Op
Comment: Reference from an aggregated element to a basic element.
Message: hasPart from an operational point : The Operational Point may have a siding (hasPart) reference that is a Siding object or a track (hasPart) reference that is a Track object. This error may be due to a hasPart relationship from an operational point that is not a Siding nor a Track.
Has sequence
OP
IRI: http://data.europa.eu/949/hasSequence
- Parameter of
-
Net Linear Reference
- Data Format
-
- Data Presentation
-
List
- Validation
-
- Validation Rules:
-
Has Sequence
Comment: The ordered sequence of topological linear elements which create a linear net reference.
Message: hasSequence: The net linear reference specifies an ordered sequence of topological linear elements that must be an instance of an rdf:List. This error is due to having a value that is not an instance of rdf:List.
Has Serialization
DP
IRI: http://www.opengis.net/ont/geosparql#hasSerialization
Has topological coordinate
OP
IRI: http://data.europa.eu/949/hasTopoCoordinate
- Parameter of
-
Net Point Reference
- Data Format
-
- Data Presentation
-
Topological Coordinate
- Validation
-
- Validation Rules:
-
Has Topo Coordinate
Comment: Specifies the topological coordinate of a network point reference.
Message: hasTopoCoordinate: The net point reference specifies a topo coordinate that must be an instance of a TopologicalCoordinate. This error is due to having a value that is not an instance of TopologicalCoordinate.
HasGeometry
OP
IRI: http://www.opengis.net/ont/geosparql#hasGeometry
- Parameter of
-
Feature
- General Information
-
- Number:
- 1.1.0.0.1.1
- 1.1.1.0.1.1
- 1.1.1.3.14.6
- 1.2.0.0.0.5
- 1.2.1.0.8.5
- XML Name:
- OPGeographicLocation
- Related parameters
-
Start of tunnel location
(
1.1.1.1.8.3
)
-
End of tunnel
(
1.1.1.1.8.4
)
- Data Format
-
- Data Presentation
-
Geometry
- Validation
-
- Validation Rules:
-
Has Geometry
Comment: Geographical coordinates in decimal degrees normally given for the centre of the OP.
Message: hasGeometry (1.2.0.0.0.5): Each feature must have at most one location. This error may be due to having a feature with more than one location or having a value that is not a geosparql:Geometry.
- OPE TSI References
-
- Part of RCC Algorithm:
- true
Identifier
DP
IRI: http://www.w3.org/ns/org#identifier
- Parameter of
-
Organization
- General Information
-
- Belongs to parameters group
-
Notation
In country
OP
IRI: http://data.europa.eu/949/inCountry
- Parameter of
-
Infrastructure element
-
Subset with common characteristics
- Data Format
-
- Data Presentation
-
Concept
- Validation
-
- Validation Rules:
-
In Country
Comment: Indicates the country to which the infrastructure element belongs
Message: inCountry: Each infrastructure element must have exactly one country. This error may be due to having an infrast without or with more than one country or it value is not a Concept.
-
In Country Skos
Comment: Indicates the country to which the infrastructure element belongs
Message: The infrastructure element {$this} has a value {?concept} that is not one of the predefined values and cannot be converted into a SKOS concept on this list: http://publications.europa.eu/resource/authority/country.
Includes list of linear references
OP
IRI: http://data.europa.eu/949/includes
- Parameter of
-
Net Area Reference
- Data Format
-
- Data Presentation
-
List
- Validation
-
- Validation Rules:
-
Includes
Comment: List of linear references included in an network area reference.
Message: includes: The net area reference specifies a list of linear references that must be an instance of an rdf:List. This error is due to having a value that is not an instance of rdf:List.
Infrastructure manager
OP
IRI: http://data.europa.eu/949/infrastructureManager
- Parameter of
-
Infrastructure element
-
Subset with common characteristics
- Data Format
-
- Data Presentation
-
Organisation Role
- Validation
-
- Validation Rules:
-
Infrastructure Manager Skosvalue
Comment: Each infrastructure element can only be submitted by one infrastructure manager, represented by a four-digit code.
Message: imCode (1.2.1.0.6.1): Each infrastructure element {$this} with label {?label} refers to a network (subset with common characteristics), that in turn refers to an instance of an OrganisationRole. This instance must have an era:organisationRole pointing to the value era-organisation-roles:IM in the orgRoles SKOS concept scheme. The error is due to a {?value} different from
Is on origin of element A
DP
IRI: http://data.europa.eu/949/isOnOriginOfElementA
- Parameter of
-
Net Relation
- General Information
-
- Number:
- 1.1.1.0.1.2
- 1.2.4.1
- Data Format
-
- Data Presentation
-
Boolean
- Validation
-
- Validation Rules:
-
Is On Origin Of Element A
Comment: Determines if the position of the topological element A in a relation is the origin of element A.
Message: isOnOriginOfElementA: The net relation specifies if the position of the topological element A in a relation is the origin of element A. This error is due having a value that is not a boolean.
Is on origin of element B
DP
IRI: http://data.europa.eu/949/isOnOriginOfElementB
- Parameter of
-
Net Relation
- General Information
-
- Number:
- 1.1.1.0.1.2
- 1.2.4.1
- Data Format
-
- Data Presentation
-
Boolean
- Validation
-
- Validation Rules:
-
Is On Origin Of Element B
Comment: Determines if the position of the topological element B in a relation is the origin of element B.
Message: isOnOriginOfElementB: The net relation specifies if the position of the topological element B in a relation is the origin of element B. This error is due having a value that is not a boolean.
Is part of
OP
IRI: http://data.europa.eu/949/isPartOf
- Parameter of
-
Infrastructure element
- Data Format
-
- Data Presentation
-
Infrastructure element
- Validation
-
- Validation Rules:
-
Is Part Of
Comment: Indicates that an infrastructure element is a part of another (distinct) infrastructure element.
Message: hasPart: The InfrastructureElement may have a isPartOf reference that is an IRI that refers to an instance of InfrastructureElement. This error is due to having a value that is not an instance of InfrastructureElement.
Kilometric post name
DP
IRI: http://data.europa.eu/949/kmPostName
- Parameter of
-
Kilometric Post
- Data Format
-
- Data Presentation
-
String
- Validation
-
- Validation Rules:
-
Km Post Name
Comment: Name of the kilometric post (optional).
Message: kmPostName: The kilometer post name must be represented as a string of characters.
Km post for reference
OP
IRI: http://data.europa.eu/949/kmPost
- Parameter of
-
Linear Positioning System Coordinate
- Data Format
-
- Data Presentation
-
Kilometric Post
Length
DP
IRI: http://data.europa.eu/949/length
- General Information
-
- Related parameters
-
Length of section of line
(
1.1.0.0.0.5
)
-
Length of tunnel
(
1.1.1.1.8.7
|
1.2.1.0.5.5
|
1.2.2.0.5.5
)
-
Usable length of platform
(
1.2.1.0.6.4
)
-
Usable length of siding
(
1.2.2.0.2.1
)
-
Length of net linear element
-
Vehicle length
- Validation
-
- Validation Rules:
-
Length T
Comment: Length of a tunnel in metres from entrance portal to exit portal.
Message: length (1.1.1.1.8.7, 1.2.1.0.5.5, 1.2.2.0.5.5): A Tunnel must have at most one length declaration. This error may be due to having a tunnel with more than one length or to having a value that is not a double (real) number.
- OPE TSI References
-
- Part of RCC Algorithm:
- true
- Additional Information
-
- General explanation:
- The length can be
- a section of line (For operational length, use era:lengthOfSectionOfLine),
- a tunnel (For operational length, use era:lengthOfTunnel),
- a platform (For its usable length, use era:lengthOfPlatform),
- a siding (For its usable length, use era:lengthOfSiding), and
- length of other areas such as
- a non-stopping area (accuracy +- 10m),
- a walkway,
- an evacuation and rescue point.
- a vehicle length.
- Position of the start of the walkway: [integer] m (from the same origin point of the kilometer post.)
Lenght of the walkway: [integer] m
Length of net linear element
DP
IRI: http://data.europa.eu/949/lengthOfNetLinearElement
- Parameter of
-
Linear Element
- General Information
-
- Belongs to parameters group
-
Length
- Data Format
-
- Data Presentation
-
Double
- Unit of Measure:
-
Metre
- Validation
-
- Validation Rules:
-
Length Of Net Linear Element
Comment: Length of a linear element.
Message: lengthOfNetLinearElement: The linear element has at most one value of length and it is a double number. This error is due to having more than one value or that the value is not a double number.
Line identifier
DP
IRI: http://data.europa.eu/949/lineId
- Parameter of
-
Linear Positioning System
- General Information
-
- Number:
- 1.1.0.0.0.2
- XML Name:
- SOLLineIdentification
- Deadline:
- In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
- Data Format
-
- Data Presentation
-
String
- Flags
-
- Applicability Flags:
- Y
- Validation
-
- Validation Rules:
-
Line Id
Comment: Unique line identification or unique line number within Member State.
Message: lineId: The line identification is unique and must be a string. This error is due to having more than one value or having a value that is not a string of characters
- OPE TSI References
-
- Appendix D2 Index
- 2.2.1.1
Lineside distance indication appearance
OP
IRI: http://data.europa.eu/949/linesideDistanceIndicationAppearance
- Parameter of
-
Lineside indications of distance
- Data Format
-
- Data Presentation
-
Concept
- Taxonomy Reference:
-
Lineside distance indication appearance
-
Values :
-
| Code |
Value |
| 00 |
Left |
| 01 |
Right |
| 02 |
Left and right |
- Validation
-
- Validation Rules:
-
Lineside Distance Indication Appearance
Comment: Indication of types of appearance of track lineside distance indications.
Message: linesideDistanceIndicationAppearance: The track must have at most one value of the lineside distance indication appearance. This error may be due to the track having no value, more than one value or to having a value that is not an IRI.
-
Lineside Distance Indication Appearance Skos
Comment: Indication of types of appearance of track lineside distance indications.
Message: Indication of the linesideDistanceIndicationAppearance: The track or subset with common characteristics {$this} has a LinesideDistanceIndication {?linesideDistanceIndication} that has a value {?concept} that is not one of the predefined values and cannot be converted into a SKOS concept on this list: http://data.europa.eu/949/concepts/lineside-distance-indication-appearance/LinesideDistanceIndicationAppearance.
Lineside distance indication frequency
DP
IRI: http://data.europa.eu/949/linesideDistanceIndicationFrequency
- Parameter of
-
Lineside indications of distance
- Data Format
-
- Data Presentation
-
Integer
- Unit of Measure:
-
Metre
- Validation
-
- Validation Rules:
-
Lineside Distance Indication Frequency
Comment: Frequency of track lineside distance indications..
Message: linesideDistanceIndicationFrequency: The track must have at most one value of the lineside distance indication frequency. This error may be due to the track having a LineDistanceIndication with no value, more than one value or to having a value that is not an integer.
Lineside distance indication positioning
OP
IRI: http://data.europa.eu/949/linesideDistanceIndicationPositioning
- Parameter of
-
Lineside indications of distance
- Data Format
-
- Data Presentation
-
Concept
- Format:
- A selection between 3 possible selectable values:
- Left, or
- Right, or
- Left and Right
- Validation
-
- Validation Rules:
-
Lineside Distance Indication Positioning
Comment: Indication of the side along the track where the lineside indication is positioned (left or right).
Message: LinesideDistanceIndicationPositioning: The track must have at most one value of the lineside distance indication positioning. This error may be due to the track having no value, more than one value or to having a value that is not an IRI.
-
Lineside Distance Indication Positioning Skos
Comment: Indication of the side along the track where the lineside indication is positioned (left or right).
Message: Indication of the linesideDistanceIndicationPositioning: The track or subset with common characteristics {$this} has a LinesideDistanceIndication {?linesideDistanceIndication} with a value {?concept} that is not one of the predefined values and cannot be converted into a SKOS concept on this list: http://data.europa.eu/949/concepts/lineside-distance-indication-positioning/LinesideDistanceIndicationPositioning.
Linked to primary location
OP
IRI: http://data.europa.eu/949/linkedToPrimaryLocation
- Parameter of
-
Subsidiary location
- Data Format
-
- Data Presentation
-
Primary Location
- Validation
-
- Validation Rules:
-
Linked To Primary Location
Comment: Linked to primary location.
Message: linkedToPrimaryLocation: An instance of subsidiary location may have a value for linkedToPrimaryLocation. This error may be due to having a value that is not an IRI or that does not point to an instance of PrimaryLocation.
Load capability line category
OP
IRI: http://data.europa.eu/949/loadCapabilityLineCategory
- Parameter of
-
Load capability
- Data Format
-
- Data Presentation
-
Concept
- Taxonomy Reference:
-
Load capability line categories
-
Values :
-
- Validation
-
- Validation Rules:
-
Load Capability Line Category
Comment: Load capability is a combination of the line category and speed at the weakest point of the track.
Message: loadCapabilityLineCategory (1.1.1.1.2.4): The track or subset with common characteristics must have a load capability with a value of line category that is an URI. This error may be due to having an instance of Load capability with no value of a line category, more than one value of a line category, or a value that is not an IRI.
-
Load Capability Line Category Skos
Comment: Load capability is a combination of the line category and speed at the weakest point of the track.
Message: Indication of the load capability line category (1.1.1.1.2.4):): The track or subset with common characteristics {$this} has a value {?concept} that is not one of the predefined values and cannot be converted into a SKOS concept on this list: http://data.europa.eu/949/concepts/load-capability-line-categories/LoadCapabilityLineCategories.
Load capability speed
DP
IRI: http://data.europa.eu/949/loadCapabilitySpeed
- Parameter of
-
Load capability
- Data Format
-
- Data Presentation
-
Integer
- Unit of Measure:
-
Kilometre per Hour
- Validation
-
- Validation Rules:
-
Load Capability Speed
Comment: Load capability is a combination of the line category and speed at the weakest point of the track.
Message: loadCapabilitySpeed (1.1.1.1.2.4): The track or subset with common characteristics must have a load capability with a value of speed that is an integer. This error may be due to having an instance of LoadCapability with no value of speed, more than one value of speed, or that the value is not an integer.
Maximum magnetic field direction X
DP
IRI: http://data.europa.eu/949/maximumMagneticFieldDirectionX
- Parameter of
-
Maximum magnetic field
- Data Format
-
- Data Presentation
-
Integer
- Validation
-
- Validation Rules:
-
Maximum Magnetic Field Direction X
Comment: The maximum magnetic field limits allowed for axle counters (in dB µA/m) for a defined frequency band. Direction X.
Message: maximumMagneticFieldDirectionX : Each MaximumMagneticField may have a single value for maximum magnetic field direction X that is an integer. This error is due to not having a value, having more than one value or having a value that is not an integer.
- Additional Information
-
- General explanation:
- The maximumMagneticFieldDirectionX parameter is only applicable for axle counters.
Maximum magnetic field direction Y
DP
IRI: http://data.europa.eu/949/maximumMagneticFieldDirectionY
- Parameter of
-
Maximum magnetic field
- Data Format
-
- Data Presentation
-
Integer
- Validation
-
- Validation Rules:
-
Maximum Magnetic Field Direction Y
Comment: The maximum magnetic field limits allowed for axle counters (in dB µA/m) for a defined frequency band. Direction Y.
Message: maximumMagneticFieldDirectionY : Each MaximumMagneticField may have a single value for maximum magnetic field direction Y that is an integer. This error is due to not having a value, having more than one value or having a value that is not an integer.
- Additional Information
-
- General explanation:
- The maximumMagneticFieldDirectionY parameter is only applicable for axle counters.
Maximum magnetic field direction Z
DP
IRI: http://data.europa.eu/949/maximumMagneticFieldDirectionZ
- Parameter of
-
Maximum magnetic field
- Data Format
-
- Data Presentation
-
Integer
- Validation
-
- Validation Rules:
-
Maximum Magnetic Field Direction Z
Comment: The maximum magnetic field limits allowed for axle counters (in dB µA/m) for a defined frequency band. Direction Z.
Message: maximumMagneticFieldDirectionZ : Each MaximumMagneticField may have a single value for maximum magnetic field direction Z that is an integer. This error is due to not having a value, having more than one value or having a value that is not an integer.
- Additional Information
-
- General explanation:
- The maximumMagneticFieldDirectionZ parameter is applicable for axle counters.
Measured distance
DP
IRI: http://data.europa.eu/949/measuredDistance
- Parameter of
-
Kilometric Post
- Data Format
-
- Data Presentation
-
Double
- Unit of Measure:
-
Metre
- Validation
-
- Validation Rules:
-
Measured Distance
Comment: Measured distance from the origin of the LRS.
Message: measuredDistance: The kilometer post measured distance must be represented as a double number.
Minimum radius of vertical curve crest
DP
IRI: http://data.europa.eu/949/minimumVerticalRadiusCrest
- Parameter of
-
Minimum radius of vertical curve
- Data Format
-
- Data Presentation
-
Integer
- Unit of Measure:
-
Metre
- Validation
-
- Validation Rules:
-
Minimum Vertical Radius Crest
Comment: Radius of the smallest vertical curve expressed in meters, part that indicates the crest
Message: minimumVerticalRadiusCrest : Each siding may have a minimumVerticalRadiusCrest in meters. This error is due to having no value, having more than one value or having a value that is not an integer number.
Minimum radius of vertical curve hollow
DP
IRI: http://data.europa.eu/949/minimumVerticalRadiusHollow
- Parameter of
-
Minimum radius of vertical curve
- Data Format
-
- Data Presentation
-
Integer
- Unit of Measure:
-
Metre
- Validation
-
- Validation Rules:
-
Minimum Vertical Radius Hollow
Comment: Radius of the smallest vertical curve expressed in meters, part that indicates the hollow
Message: minimumVerticalRadiusHollow: Each siding may have a minimumVerticalRadiusHollow in meters. This error is due to having no value, having more than one value or having a a value that is not an integer number.
Minimum Vehicle Impedance (Voltage applicable)
OP
IRI: http://data.europa.eu/949/minVehicleImpedanceVoltages
- Parameter of
-
Minimum Vehicle Impedance
- Data Format
-
- Data Presentation
-
Concept
- Taxonomy Reference:
-
Energy Supply Systems
-
Values :
-
- Validation
-
- Validation Rules:
-
Min Vehicle Impedance Voltages Skos
Comment: Indication of the voltage system valid for the minimal impedance value (track circuits).
Message: minVehicleImpedanceVoltages: The minVehicleImpedance {$this} has a value {?concept} that is not one of the predefined values and cannot be converted into a SKOS concept on this list: http://data.europa.eu/949/concepts/energy-supply-systems/EnergySupplySystems.
-
Min Vehicle Impedance Voltages
Comment: Indication of the voltage system valid for the minimal impedance value (track circuits).
Message: minVehicleImpedanceVoltages: The MinVehicleImpedance has a minVehicleImpedanceVoltage that must be an IRI. This error may be due to not having a value, having more than one value or having a value that is not an IRI.
-
Min Vehicle Impedance Voltages Applicability
Comment: The parameter minVehicleImpedanceVoltages is applicable for track circuits.
Message: minVehicleImpedanceVoltages (1.1.1.3.4.2.2, 1.2.1.1.3.2.2):The Train Detection System {$this} ({?clsLabel}), has a 'track circuit' type that makes the minVehicleImpedanceVoltages parameter applicable. This error is due to {?minVehicleImpedance} not having a value for such a parameter.
Name
DP
IRI: http://xmlns.com/foaf/0.1/name
- Parameter of
-
Thing
- Data Format
-
- Data Presentation
-
Literal
Name of a subset with common characteristics
DP
IRI: http://data.europa.eu/949/subsetName
- Parameter of
-
Subset with common characteristics
- Data Format
-
- Data Presentation
-
String
- Additional Information
-
- Example:
- Example: "ETCSbaseline2": describes all ETCS National values (1.1.1.3.2.16 group)
Navigability
OP
IRI: http://data.europa.eu/949/navigability
- Parameter of
-
Net Relation
- General Information
-
- Number:
- 1.1.1.0.1.2
- 1.2.4.1
- Data Format
-
- Data Presentation
-
Concept
- Taxonomy Reference:
-
Navigabilities
-
Values :
-
- Validation
-
- Validation Rules:
-
Navigability Skos
Comment: Indicates the navigation possibilities between two related topological linear elements.
Message: era:navigability: The net relation {$this} with label {?thisLabel} has a value {?concept} that is not one of the predefined values and cannot be converted into a SKOS concept on this list: http://data.europa.eu/949/concepts/navigabilities/Navigabilities.
-
Navigability
Comment: Indicates the navigation possibilities between two related topological linear elements.
Message: navigability: The net relation must have a navigability value that is an IRI.
- Additional Information
-
- General explanation:
- • AB: Trains can move from element A to element B.
• BA: Trains can move from element B to element A.
• Both: Movement is bidirectional.
• None: No movement is allowed between the two elements.
Net reference
OP
IRI: http://data.europa.eu/949/netReference
- Parameter of
-
Infrastructure element
-
Linear Positioning System
- Data Format
-
- Data Presentation
-
Net Basic Reference
- Validation
-
- Validation Rules:
-
Net Reference
Comment: The reference that a physical insfrastructure element has it on the topology. It may be used to define the positioning or a representation as a point. line or area.
Message: netReference: The infratructure element must have a net reference that points to an instance of NetBasicReference. This error is due to having a value that is not an instance of NetBasicReference.
Not applicable
OP
IRI: http://data.europa.eu/949/notApplicable
- Parameter of
-
Datatype Property
-
Object Property
- Validation
-
- Validation Rules:
-
Not Applicable Property Shape
Comment: Reference to a property that is not applicable.
Message: The value of this property is a reference to an ontology property that is not provided and it must be an IRI. The error may be due to the property not belonging to the ERA ontology or the property not being an IRI.
Not provided
OP
IRI: http://data.europa.eu/949/notYetAvailable
- Parameter of
-
Datatype Property
-
Object Property
- Validation
-
- Validation Rules:
-
Not Yet Available Property Shape
Comment: Reference to a property that is not provided.
Message: The value of this property is a reference to an ontology property that is not provided and it must be an IRI. The error may be due to the property not belonging to the ERA ontology or the property not being an IRI.
Notation
DP
IRI: http://www.w3.org/2004/02/skos/core#notation
- General Information
-
- Related parameters
-
Identifier
Of parameter
OP
IRI: http://data.europa.eu/949/ofParameter
- Parameter of
-
Parameter applicability
- Data Format
-
- Data Presentation
-
Datatype Property
-
Object Property
- Validation
-
- Validation Rules:
-
Of Parameter
Comment: Applicability interval defines the date interval in which a characteristic of an infrastructure element is applicable. The characteristic to which it applies is the ofParameter property.
Message: ofParameter: An instance of parameter applicability must have exactly one value of the characteristic (ofParameter) to which it applies to. This error may be due to not having a value, having more than one value, having a value that is not an IRI or is not an object or datatype property in the ontology.
Offset
DP
IRI: http://data.europa.eu/949/offsetFromKilometricPost
- Parameter of
-
Linear Positioning System Coordinate
- Data Format
-
- Data Presentation
-
Double
- Unit of Measure:
-
Metre
- Validation
-
- Validation Rules:
-
Offset From Kilometric Post
Comment: Relative distance from a reference kilometric post.
Message: offsetFromKilometricPost: The offset from kilometric post must be represented as a double number.
Offset from origin
DP
IRI: http://data.europa.eu/949/offsetFromOrigin
- Parameter of
-
Topological Coordinate
- Data Format
-
- Data Presentation
-
Positive Integer
- Unit of Measure:
-
Metre
- Validation
-
- Validation Rules:
-
Offset From Origin
Comment: Offset from the origin in a topological coordinate.
Message: offsetFromOrigin: The offset from the origin in a topological coordinate must be represented as a positive integer.
On element
OP
IRI: http://data.europa.eu/949/onElement
- Parameter of
-
Linear Element Section
- Data Format
-
- Data Presentation
-
Linear Element
- Validation
-
- Validation Rules:
-
On Element
Comment: Specifies the linear element a section belongs to.
Message: onElement: The linear element section specifies the linear element it belongs to. This error is due having a value that is not an instance of LinearElement.
On linear element
OP
IRI: http://data.europa.eu/949/onLinearElement
- Parameter of
-
Topological Coordinate
- Data Format
-
- Data Presentation
-
Linear Element
- Validation
-
- Validation Rules:
-
On Linear Element
Comment: Specifies the linear element a coordinate is associated with.
Message: onLinearElement: The topological coordinate specifies the linear element it belongs to. This error is due having a value that is not an instance of LinearElement.
On side
OP
IRI: http://data.europa.eu/949/side
- Parameter of
-
Orientation
- Data Format
-
- Data Presentation
-
Concept
- Taxonomy Reference:
-
Sides
-
Values :
-
Parameter applicability
OP
IRI: http://data.europa.eu/949/parameterApplicability
- Parameter of
-
Infrastructure element
-
Subset with common characteristics
- Data Format
-
- Data Presentation
-
Parameter applicability
- Validation
-
- Validation Rules:
-
Parameter Applicability
Comment: Applicability interval that defines the date interval in which a characteristic of an infrastructure element is applicable. This interval can be applied for any of the technical characteristics or general information of infrastructure elements. This helps identifying planned changes applied to technical parameters over time.
Message: parameterApplicability: The infratructure element may have a parameterApplicability reference that must be an instance of ParameterApplicability. This error is due to having having a value that is not an instance of ParameterApplicability.
Parameter value
DP
IRI: http://data.europa.eu/949/parameterValue
- Parameter of
-
Parameter applicability
- Data Format
-
- Data Presentation
-
Literal
- Validation
-
- Validation Rules:
-
Parameter Value
Comment: This property is used to link an applicability to the precise value of the parameter
Message: parameterValue: An instance of parameter applicability must have exactly one value of the parameter value. This error may be due to not having a value or having more than one value.
Parameter value type
OP
IRI: http://data.europa.eu/949/parameterValueType
- Parameter of
-
Parameter applicability
- Data Format
-
- Data Presentation
-
Concept
- Taxonomy Reference:
-
Applicability types
-
Values :
-
| Code |
Value |
| NMN |
Nominal |
| PRN |
Permanent restriction |
| PTC |
Planned temporary closure |
| PTR |
Planned temporary restriction |
- Validation
-
- Validation Rules:
-
Parameter Value Type
Comment: In the case of a change in the value of a parameter, there needs to be an information on the type of the new value. The “Value type” will have different possible options: “nominal”, “planned temporary restriction”, “permanent restriction”, “planned temporary closure.
Message: parameterValueType: An instance of parameter applicability must have exactly one value of the parameter value type. This error may be due to not having a value, having more than one value, having a value that is not an IRI.
-
Parameter Value Type Skos
Comment: In the case of a change in the value of a parameter, there needs to be an information on the type of the new value. The “Value type” will have different possible options: “nominal”, “planned temporary restriction”, “permanent restriction”, “planned temporary closure.
Message: parameterValueType: The parameter applicability {$this} with label {?thisLabel} has a value {?concept} that is not one of the predefined values and cannot be converted into a SKOS concept on this list: http://data.europa.eu/949/concepts/parameterApplicability/ValueTypes.
Phase info change supply system
DP
IRI: http://data.europa.eu/949/phaseInfoChangeSupplySystem
- Parameter of
-
Phase info
- Data Format
-
- Data Presentation
-
Boolean
- Validation
-
- Validation Rules:
-
Phase Info Change Supply System
Comment: Indication of existence of phase separation and required information.
Message: Phase info changeSupplySystem : The track has the phase info with the indication whether the supply system has to be changed value, that must be a character string. This error is due to the track having a SystemSeparationInfo with no value, more than one value, or a value that is not a string.
- Additional Information
-
- General explanation:
- The phase info is the indication of required several information on phase separation.
Phase info distance type
DP
IRI: http://data.europa.eu/949/phaseInfoDistanceType
- Parameter of
-
Phase info
- Data Format
-
- Data Presentation
-
String
- Validation
-
- Validation Rules:
-
Phase Info Distance Type
Comment: Indication of existence of phase separation and required information.
Message: Phase info distance type : The track has a phase info with the single selection of 'MIN=minimum' or 'MAX=maximum' to show whether the length is a minimum distance between the inner contact strips of the pantographs or a maximum distance between the outer contact strips of the pantographs, that must be the string MIN or MAX. This error may be due to the track having a PhaseInfo with no value of distancetype, more than one value of distance type, or having a value that is not one of the strings MIN or MAX.
- Additional Information
-
- General explanation:
- The phase info is the indication of required several information on phase separation.
Phase info Km
DP
IRI: http://data.europa.eu/949/phaseInfoKm
- Parameter of
-
Phase info
- Data Format
-
- Data Presentation
-
Double
- Validation
-
- Validation Rules:
-
Phase Info Km
Comment: Indication of existence of phase separation and required information.
Message: Phase info km : The track has a phase info with the location from the start of the line value (km), that must be a double. This error may be due to the track having a PhaseInfo with no value of km, more than one value of km, or a value that is not a double (real) number.
- Additional Information
-
- General explanation:
- The phase info is the indication of required several information on phase separation.
Phase info length
DP
IRI: http://data.europa.eu/949/phaseInfoLength
- Parameter of
-
Phase info
- Data Format
-
- Data Presentation
-
Integer
- Unit of Measure:
-
- Validation
-
- Validation Rules:
-
Phase Info Length
Comment: Indication of existence of phase separation and required information.
Message: Phase infolength (): The track has a phase info with the length of the phase separation value (length), that must be an integer. This error may be due to the track having a PhaseInfo with no value of length, more than one value of length, or having a value that is not an integer.
- Additional Information
-
- General explanation:
- The phase info is the indication of required several information on phase separation.
Phase info pantograph lowered
DP
IRI: http://data.europa.eu/949/phaseInfoPantographLowered
- Parameter of
-
Phase info
- Data Format
-
- Data Presentation
-
Boolean
- Validation
-
- Validation Rules:
-
Phase Info Pantograph Lowered
Comment: Indication of existence of phase separation and required information.
Message: Phase info (1.1.1.2.4.1.2): The track has the phase info with the indication whether the pantograph is lowered value, that must be Y/N (boolean). This error may be due to the track having a PhaseInfo with no value of phaseInfoPantographLowered, more than one value of phaseInfoPantographLowered, or having a value that is not Y/N (boolean).
- Additional Information
-
- General explanation:
- The phase info is the indication of required several information on phase separation.
Phase info switch off breaker
DP
IRI: http://data.europa.eu/949/phaseInfoSwitchOffBreaker
- Parameter of
-
Phase info
- Data Format
-
- Data Presentation
-
Boolean
- Validation
-
- Validation Rules:
-
Phase Info Switch Off Breaker
Comment: Indication of existence of phase separation and required information.
Message: Phase info switchOffBreaker : The track has the phase info with the indication whether the breaker may be switched off value, that must be Y/N (boolean). This error may be due to the track having a PhaseInfo with no value of phaseInfoSwitchOffBreaker, more than one value of phaseInfoSwitchOffBreaker, or having a value that is not Y/N (boolean).
- Additional Information
-
- General explanation:
- The phase info is the indication of required several information on phase separation.
Primary location code
DP
IRI: http://data.europa.eu/949/primaryLocationCode
- Parameter of
-
Primary Location
- General Information
-
- Number:
- 1.2.0.0.0.3
- XML Name:
- OPTafTapCode
- Belongs to parameters group
-
Identifier
- Data Format
-
- Data Presentation
-
String
- Validation
-
- Validation Rules:
-
Primary Location
Comment: Primary location code developed for information exchange in accordance with the TSIs relating to the telematics applications subsystem.
Message: primaryLocation: The infrastructure element has a primaryLocation reference that must be an IRI that refers to an instance of PrimaryLocation.
-
Primary Location Code
Comment: Primary location code developed for information exchange in accordance with the TSIs relating to the telematics applications subsystem.
Message: primaryLocationCode (1.2.0.0.0.3): The primary location code must be represented as a String and follow the pattern [AANNNNN].
- OPE TSI References
-
- Appendix D2 Index
- 2.2.2
Primary location name
DP
IRI: http://data.europa.eu/949/primaryLocationName
- Parameter of
-
Primary Location
- Data Format
-
- Data Presentation
-
String
- Validation
-
- Validation Rules:
-
Primary Location Name
Comment: Primary location name.
Message: primaryLocationName : The PrimaryLocation may have a primaryLocationName value that is a string. This error may be due to the Primary Location having a value that is not a string.
Raised pantographs speed
DP
IRI: http://data.europa.eu/949/raisedPantographsSpeed
- Parameter of
-
Requirements for number of raised pantographs and spacing between them, at the given speed
- Data Format
-
- Data Presentation
-
Integer
- Unit of Measure:
-
- Validation
-
- Validation Rules:
-
Raised Pantographs Speed
Comment: Indication of maximum number of raised pantographs per train allowed and minumum spacing centre line to centre line of adjacent pantograph heads, expressed in meters, at the given speed.
Message: raised pantographs speed (1.1.1.2.3.3): The track or subset with common characteristics must have a raised pantographs distance and speed with a value of speed that is an integer. This error is due to having a RaisedPantographDistanceAndSpeed with no value of speed, more than one value of speed or having a value that is not an integer.
Reference border point
OP
IRI: http://data.europa.eu/949/referenceBorderPoint
- Parameter of
-
Operational Point
- Data Format
-
- Data Presentation
-
Reference border point
- Validation
-
- Validation Rules:
-
Reference Border Point
Comment: Relates an operational point that is a border point with an instance of the list of reference border points that are specified in the RINF Application Guide.
Message: referenceBorderPoint : The Operational Point may have a reference border pointthat is a ReferenceBorderPoint object. This error may be due to having more than one value of a reference border point, or having a value that is not a ReferenceBorderPoint instance.
Requirements for number of raised pantographs, at the given speed
DP
IRI: http://data.europa.eu/949/raisedPantographsNumber
- Parameter of
-
Requirements for number of raised pantographs and spacing between them, at the given speed
- Data Format
-
- Data Presentation
-
Integer
- Validation
-
- Validation Rules:
-
Raised Pantographs Number
Comment: Indication of maximum number of raised pantographs per train allowed and minumum spacing centre line to centre line of adjacent pantograph heads, expressed in meters, at the given speed.
Message: Raised pantographs number (1.1.1.2.3.3): The track or subset with common characteristics must have a raised pantographs distance and number with a value of number that is an integer. This error is due to having a RaisedPantographDistanceAndSpeed with no value of number, more than one value of number or having a value that is not an integer.
Requirements for spacing between raised pantographs, at the given speed
DP
IRI: http://data.europa.eu/949/raisedPantographsDistance
- Parameter of
-
Requirements for number of raised pantographs and spacing between them, at the given speed
- Data Format
-
- Data Presentation
-
Integer
- Unit of Measure:
-
Metre
- Validation
-
- Validation Rules:
-
Raised Pantographs Distance
Comment: Indication of maximum number of raised pantographs per train allowed and minumum spacing centre line to centre line of adjacent pantograph heads, expressed in meters, at the given speed.
Message: Raised pantographs distance (1.1.1.2.3.3): The track or subset with common characteristics must have a raised pantographs distance and speed with a value of distance that is an integer. This error is due to the track having a RaisedPantographDistanceAndSpeed with no value of distance, more than one value of distance or having a value that is not an integer.
Role
OP
IRI: http://data.europa.eu/949/role
- Parameter of
-
Body
- Data Format
-
- Data Presentation
-
Organisation Role
- Validation
-
- Validation Rules:
-
Role
Comment: Indicates the relationship of a Body to the organisation roles that it can play.
Message: role: Each instance of a Body must have at least one role. This error mae be due to having no value or having a value that is not an instance of OrganisationRole.
Role of
OP
IRI: http://data.europa.eu/949/roleOf
- Parameter of
-
Organisation Role
- Data Format
-
- Data Presentation
-
Body
- Validation
-
- Validation Rules:
-
Role Of
Comment: Indicates the corresponding Body that plays a certain organisation role.
Message: roleOf: Each instance of Organization Role points thorugh roleOf to exactly one instance of Body. This error mae be due to having no value, having more than one value or having a value that is not an instance of Body.
Section with train detection limitation
DP
IRI: http://data.europa.eu/949/frenchTrainDetectionSystemLimitationApplicable
- Parameter of
-
Section with train detection limitation
- General Information
-
- XML Name:
- CTD_TCLimitation
- Data Format
-
- Data Presentation
-
Boolean
- Validation
-
- Validation Rules:
-
French Train Detection System Limitation Applicable
Comment: Part of the section with train detection limitation that indicates if it is applicable. Only for the French network.
Message: frenchTrainDetectionSystemLimitationApplicable : The train detection system has a french train detection limitation applicable value that must be a boolean. This error may be due to not having a value, having more than one value or having a value that is not a boolean.
- OPE TSI References
-
- Part of RCC Algorithm:
- true
Section with train detection limitation number, only for French network
OP
IRI: http://data.europa.eu/949/frenchTrainDetectionSystemLimitationNumber
- Parameter of
-
Section with train detection limitation
- Data Format
-
- Data Presentation
-
Concept
- Taxonomy Reference:
-
French Train Detection System Limitation Numbers
-
Values :
-
| Code |
Value |
| 1 |
Sections with tonnage circulated per track is inferior to 15000 tons/day/track |
| 2 |
Sections with directional Interlocking |
| 3 |
Sections with 45-second delay for directional interlocking |
| 4 |
Sections with Installation with track circuit announcement |
| 5 |
Sections with absence of a shunting assistance pedal in the normal direction of circulation for non-reversible double track lines |
| 6 |
Sections with absence of a shunting assistance pedal regardless of the direction of traffic for single track lines and tracks for two way working |
| 7 |
Sections with absence of a pedal announcement mechanism |
| 8 |
Sections with 45-second delay for specific announcement reset devices |
- Validation
-
- Validation Rules:
-
French Train Detection System Limitation Number Skos
Comment: Part of the section with train detection limitation that indicates the type of train detection limitation. Only for the French network
Message: Indication of the frenchTrainDetectionSystemLimitationNumber: The train detection system {$this} has a value {?concept} that is not one of the predefined values and cannot be converted into a SKOS concept on this list: http://data.europa.eu/949/concepts/train-detection-numbers/FrenchTrainDetectionSystemLimitationNumbers.
-
French Train Detection System Limitation Number
Comment: Part of the section with train detection limitation that indicates the type of train detection limitation. Only for the French network
Message: frenchTrainDetectionSystemLimitationNumber : The train detection system has a french train detection limitation number that must be an IRI. This error may be due to not having a value, having more than one value or having a value that is not an IRI.
Special area type
OP
IRI: http://data.europa.eu/949/specialAreaType
- Parameter of
-
Special area
- General Information
-
- Number:
- 1.1.0.0.1.1
- Data Format
-
- Data Presentation
-
Concept
- Taxonomy Reference:
-
Types of Special Areas
-
Values :
-
- OPE TSI References
-
- Appendix D2 Index
- 3.2.4
Special tunnel area
OP
IRI: http://data.europa.eu/949/specialTunnelArea
- Parameter of
-
Tunnel
- Data Format
-
- Data Presentation
-
Special tunnel area
- OPE TSI References
-
- Appendix D2 Index
- 3.2.3
Start offset from origin
DP
IRI: http://data.europa.eu/949/startOffsetFromOrigin
- Parameter of
-
Linear Element Section
- Data Format
-
- Data Presentation
-
Double
- Unit of Measure:
-
Metre
- Validation
-
- Validation Rules:
-
Start Offset From Origin
Comment: Start offset of the section from the origin.
Message: startOffsetFromOrigin: The start offset of the section from the origin must be represented as a positive integer.
Starts at
OP
IRI: http://data.europa.eu/949/startsAt
- Parameter of
-
Net Linear Reference
- Data Format
-
- Data Presentation
-
Topological Coordinate
- Validation
-
- Validation Rules:
-
Starts At
Comment: Specifies the starting coordinate of a linear reference.
Message: startsAt: The net linear reference specifies a starting coordinate that must be an instance of a TopologicalCoordinate. This error is due to not having a value, having more than one value or having a value that is not an instance of TopologicalCoordinate.
Subset of
OP
IRI: http://data.europa.eu/949/subsetOf
- Parameter of
-
Subset with common characteristics
- Data Format
-
- Data Presentation
-
Subset with common characteristics
- Validation
-
- Validation Rules:
-
Subset Of
Comment: Relates a subset with common chatacteristics with another subset with common characteristics.
Message: subsetOf: The common characteristics subset must have a subsetOf reference that is an IRI that refers to an instance of another common characteristics subset. This error is due to having a value that is not an instance of CommonCharacteristicsSubset.
- Additional Information
-
- General explanation:
- Whenever a subset (A) is a subset of another subset (B), then the subset (A) inherits all the common characteristics of subset (B), which is that all the infrastructure elements belonging to subset (A) will have as common characteristics the union of parameters (A) and (B).
Subsidiary location code
DP
IRI: http://data.europa.eu/949/subsidiaryLocationCode
- Parameter of
-
Subsidiary location
- Data Format
-
- Data Presentation
-
String
Subsidiary location name
DP
IRI: http://data.europa.eu/949/subsidiaryLocationName
- Parameter of
-
Subsidiary location
- Data Format
-
- Data Presentation
-
String
Subsidiary location type
OP
IRI: http://data.europa.eu/949/subsidiaryLocationType
- Parameter of
-
Subsidiary location
- Data Format
-
- Data Presentation
-
Concept
- Taxonomy Reference:
-
Subsidiary location types
-
Values :
-
| Code |
Value |
| 00 |
Not Defined |
| 04 |
Sorting Code |
| 05 |
Vehicle Parking Points |
| 06 |
Public Loading Places |
| 07 |
Private sidings |
| 09 |
Depot |
| 25 |
Underpass |
| 28 |
Sign and board |
| 29 |
Phase break |
| 36 |
Freight yard |
| 37 |
Loading point |
| 39 |
Reservation code |
| 40 |
Metastation |
| 41 |
Company specific Identifier |
| 42 |
DIUM |
| 43 |
Passengers cars loading |
| 45 |
Sewage dump |
| 46 |
Refuelling |
| 47 |
Mains Supply |
| 48 |
Water Supply |
| 50 |
Indoor cleaning platform |
| 51 |
Car-wash |
| 52 |
Short dry- cleaning track |
| 54 |
Sand-filling station |
| 56 |
Signal box |
| 57 |
Intermodal Terminal |
| 58 |
OSJD system |
| 59 |
Train Service Substitute Stop |
| 60 |
Multifunction al rail terminal |
| 61 |
Relief facility |
| 70 |
Network Border |
| 71 |
State border |
| 72 |
Administrative border |
| 74 |
Operational handover |
| 75 |
Planning handover |
| 76 |
Stopping |
| 99 |
Relation to Station |
- Validation
-
- Validation Rules:
-
Subsidiary Location Type Skos
Comment: Subsidiary location type.
Message: subsidiaryLocationType: The Subsidiary Location {$this} (label {?slLabel}) has a value {?concept} that is not one of the predefined values and cannot be converted into a SKOS concept on this list: http://data.europa.eu/949/concepts/subsidiary-location-types/SubsidiaryLocationTypes.
-
Subsidiary Location Type
Comment: Subsidiary location type.
Message: subsidiaryLocationType: An instance of subsidiary location may have a value for subsidiary location type. This error may be due to having a value that is not an IRI.
System separation info pantograph lowered
DP
IRI: http://data.europa.eu/949/systemSeparationInfoPantographLowered
- Parameter of
-
System separation info
- Data Format
-
- Data Presentation
-
Boolean
- Validation
-
- Validation Rules:
-
System Separation Info Pantograph Lowered
Comment: Indication of required several information on system separation.
Message: System separation info pantograph lowered: The track has the system separation info with the indication whether the pantograph is lowered value, that must be Y/N (boolean). This error may be due to the track having a SystemSeparationInfo with no value, more than one value, or a value that is not Y/N (boolean).
System separation info change supply system
DP
IRI: http://data.europa.eu/949/systemSeparationInfoChangeSupplySystem
- Parameter of
-
System separation info
- Data Format
-
- Data Presentation
-
String
- Validation
-
- Validation Rules:
-
System Separation Info Change Supply System
Comment: Indication of required several information on system separation.
Message: System separation info changeSupplySystem : The track has the system separation info with the indication whether the supply system has to be changed value, that must be a character string. This error is due to the track having a SystemSeparationInfo with no value, more than one value, or a value that is not a string.
System separation info Km
DP
IRI: http://data.europa.eu/949/systemSeparationInfoKm
- Parameter of
-
System separation info
- Data Format
-
- Data Presentation
-
Double
- Validation
-
- Validation Rules:
-
System Separation Info Km
Comment: Indication of required several information on system separation.
Message: System separation info km : The track has a system separation info with the location from the start of the line value (km), that must be a double.This error may be due to the track having a SystemSeparationInfo with no value, more than one value, or a value that is not a double (real) number.
System separation info length
DP
IRI: http://data.europa.eu/949/systemSeparationInfoLength
- Parameter of
-
System separation info
- Data Format
-
- Data Presentation
-
Integer
- Unit of Measure:
-
- Validation
-
- Validation Rules:
-
System Separation Info Length
Comment: Indication of required several information on system separation.
Message: System separation info length: The track has a system separatione info with the length of the system separation value (length), that must be an integer. This error may be due to the track having a SystemSeparationInfo with no value, more than one value, or a value that is not an integer.
System separation info switch off breaker
DP
IRI: http://data.europa.eu/949/systemSeparationInfoSwitchOffBreaker
- Parameter of
-
System separation info
- Data Format
-
- Data Presentation
-
Boolean
- Validation
-
- Validation Rules:
-
System Separation Info Switch Off Breaker
Comment: Indication of required several information on system separation.
Message: System separation info switchOffBreaker : The track has the system separation info with the indication whther the breaker may be switched off value, that must be Y/N (boolean). This error is due to the track having a SystemSeparationInfo with no value, more than one value, or a value that is not Y/N (boolean).
Train detection system
OP
IRI: http://data.europa.eu/949/trainDetectionSystem
- Parameter of
-
Running track
-
Subset with common characteristics
- Data Format
-
- Data Presentation
-
Train Detection System
- Validation
-
- Validation Rules:
-
Train Detection System
Comment: Train detection systems installed in the section of line.
Message: trainDetectionSystem (1.1.1.3.4) : The track or subset with common characteristics may have at most one value of a train detection system that must be an instance of TrainDetectionSystem. This error may be due to the track or subset with common characteristics having more than one value or a value that is not an instance of the class TrainDetectionSystem.
- Additional Information
-
- General explanation:
- It can be repeated as many times as the number of different train detection systems are present.
Not all parameters are applicable to all types of train detection systems; it depends on the applicability condition.
For RDF data provision:
The value of this property is an instance of the era:TrainDetectionsystem, which has as properties the parameters with indices 1.1.1.3.7.x.
For RINF XML data sets:
As long as the data provision through XML data sets is allowed, this property is the equivalent of the "Set" attribute, grouping parameters 1.1.1.3.7.x.
TSI compliant train protection system (ETCS)
OP
IRI: http://data.europa.eu/949/etcs
- Parameter of
-
Running track
-
Subset with common characteristics
- Data Format
-
- Data Presentation
-
ETCS
- Validation
-
- Validation Rules:
-
Etcs
Comment: European Train Control System (ETCS) application level supported by the track side equipment.
Message: etcs (1.1.1.3.2) : The track or subset with common characteristics may have at most one value of a European Train Control System (ETCS) that must be an instance of ETCS. This error may be due to the track having more than one value or a value that is not an instance of the class ETCS.
- Additional Information
-
- General explanation:
- It can be repeated as many times as the number of different ETCS levels are present.
For RDF data provision:
The value of this property is an instance of the era:ETCS, which has as properties the parameters 1.1.1.3.2.1 and 1.1.1.3.2.2.
For RINF XML data sets:
As long as the data provision through XML data sets is allowed, this property is the equivalent of the "Set" attribute, grouping parameters 1.1.1.3.2.1 and 1.1.1.3.2.2.
Type of line referencing system
OP
IRI: http://data.europa.eu/949/lrsMethod
- Parameter of
-
Linear Positioning System
- Data Format
-
- Data Presentation
-
Concept
- Taxonomy Reference:
-
Line reference systems
-
Values :
-
| Code |
Value |
| 00 |
Placeholder |
- Validation
-
- Validation Rules:
-
Lrs Method
Comment: The preferred line referencing system.
Message: lrsMethod: The linear positioning system must have an 'lrsMethod' value that is an IRI.
-
Lrs Method Skos
Comment: The preferred line referencing system.
Message: lrsMethod: The linear positionung system {$this} with label {?thisLabel} has a value {?concept} that is not one of the predefined values and cannot be converted into a SKOS concept on this list: http://data.europa.eu/949/concepts/lines/ReferenceSystems.
Validity
OP
IRI: http://data.europa.eu/949/validity
- Parameter of
-
ERA Feature
- Data Format
-
- Data Presentation
-
Temporal Feature
- Validation
-
- Validation Rules:
-
Validity
Comment: Relates a feature with a temporal feature to indicate a validity period.
Message: validity: The feature has a validity value that points to an instance of TemporalFeature. This error is due to having a value that is not an instance of TemporalFeature.
