ERA Ontology
type: Ontology
license: oj
contributor: Polymnia Vasilopoulou
  member of: ERA
contributor: Edna Ruckhaus
contributor: Oscar Corcho
contributor: Marina Aguado
  member of: ERA
contributor: Orfeas Menis
issued: 2024-04-18
modified: 2024-04-18
modified: 2024-05-24
modified: 2024-06-03
modified: 2024-06-05
modified: 2024-07-05
modified: 2024-08-02
modified: 2024-08-12
modified: 2024-08-13
modified: 2024-09-19
modified: 2024-09-20
modified: 2024-09-24
modified: 2024-09-25
modified: 2024-10-24
modified: 2024-10-28
modified: 2024-10-29
modified: 2024-10-30
modified: 2024-10-31
modified: 2024-11-04
modified: 2024-11-05
modified: 2024-11-12
modified: 2024-11-20
modified: 2024-11-22
modified: 2024-11-26
modified: 2024-11-27
modified: 2024-12-02
modified: 2024-12-03
modified: 2024-12-05
modified: 2024-12-10
modified: 2024-12-12
modified: 2024-12-13
modified: 2025-01-30
modified: 2025-02-11
modified: 2025-02-13
modified: 2025-02-18
modified: 2025-02-20
modified: 2025-03-01
modified: 2025-03-05
modified: 2025-03-07
modified: 2025-03-10
modified: 2025-03-11
modified: 2025-03-17
modified: 2025-03-24
modified: 2025-03-26
modified: 2025-04-25
modified: 2025-05-05
modified: 2025-05-06
modified: 2025-05-09
modified: 2025-05-21
modified: 2025-05-26
modified: 2025-06-06
modified: 2025-06-09
modified: 2025-06-16
modified: 2025-06-24
modified: 2025-07-21
modified: 2025-07-24
modified: 2025-08-18
modified: 2025-08-26
modified: 2025-09-03
modified: 2025-09-05
modified: 2025-09-08
modified: 2025-09-10
modified: 2025-09-21
modified: 2025-09-22
modified: 2025-10-07
modified: 2025-10-08
modified: 2025-10-17
publisher: European Union Agency for Railways
comment: This is the human and machine-readable Ontology governed by the European Union Agency for Railways (https://www.era.europa.eu/). It represents the concepts and relationships linked to the sectorial legal framework and the use cases under the Agency´s remit, as described in the Commission Implementing Regulation (EU) [to be updated after publication] on the common specifications for the register of railway infrastructure [to be updated after publication]. Currently, this Ontology covers the European railway infrastructure and the vehicle types authorized to operate over it. It is a semantic/browsable representation of the RINF application guide (1) and ERATV application guide (2) that were built by domain experts in the RINF and ERATV working parties. The Ontology also includes the route book concepts described in appendix D2 "Elements the infrastructure manager has to provide to the railway undertaking for the Route Book" as presented in the Commission Implementing Regulation (EU) [to be updated after publication] 2019/773 of 16 May 2019 on the technical specification for interoperability relating to the operation and traffic management subsystem of the rail system within the European Union and [to be updated after publication] and the Appendix D3 [to be updated after publication].
prior version: https://gitlab.com/era-europa-eu/public/interoperable-data-programme/era-ontology/era-ontology/-/releases/v3.1.3
version info: v3.1.4
version URI: https://gitlab.com/era-europa-eu/public/interoperable-data-programme/era-ontology/era-ontology/-/releases/v3.1.4
change note: Revision 17-10-2025 - Added era:RunningTrack as domain of era:vehiclesCompatibleTrafficLoad and era:vehicleTypesCompatibleTrafficLoad Revision 08-10-2025 - Added missing annotations of deprecated properties with dcterms:isReplacedBy for era:passesThroughTunnel and era:platformEdge. Revision 07-10-2025 - Modified range of era:offsetFromOrigin to be xsd:double (see issue Gitlab #165) - Updated the appropriate SHACL file Revision 21-09-2025 - Added era:inNUTS3 and era:passengerFlag with domain era:PrimaryLocation. - Added corresponding shapes in the file era-shacl/RINF-primary-location.ttl Revision 22-09-2025 - Created SHACL validation for era:permitUseReflectivePlates Revision 10-09-2025 - Added skos:altLabel, new comment, and dcterms:source to era:redLightsRequired Revision 08-09-2025 - Added missing era:leagalDeadline for era:lineNationalId, era:startLocation, era:lineReferenceTunnelEnd, era:contactStripMaterialMetallicContent, era:hasEtcsNationalPacket44, and era:maximumInterferenceCurrentEvaluation Revision 05-09-2025 - Changed the range of era:subsetName and era:subsidiaryLocationName to rdf:langString for multilingual labels per language. Revision 03-09-2025 - Added `rdfs:subPropertyOf dcterms:identifier` to era:hotAxleBoxDetectorIdentification, era:lineId, era:platformId, era:radioNetworkId and era:tenGISId. Revision 26-08-2025 - Removed the subClassOf axiom of era:CommonCharacteristicsSubset rdfs:subClassOf rdf:List. - Changed the range of era:primaryLocationName to rdf:langString for multilingual labels per language. Revision 18-08-2025 - Updated the definitions and concepts for era-skos-SignalTypes - Added initial concepts for era-skos-referenceSystems Revision 24-07-2025 - Changed the SHACL validations of era:hasPart to make required relations specific to the subclasses of InrastructureElement Revision 21-07-2025 - Changed the range of era:startsAt and era:endsAt from era:TopologicalCoordinates to era:NetPointReference as outlined in the RINF overview figur…

XML name
type: AnnotationProperty
created: 2023-05-26
modified: 2024-08-13
comment: Corresponding XML name as indicated in the RINF application guide
range: string

affected Class
type: AnnotationProperty
created: 2024-11-04
comment: Annotation property used in SHACL shapes. Name of the classes that are the subject of properties that are being validated in a SHACL shape.
range: anyURI

affected Property
type: AnnotationProperty
created: 2024-11-04
comment: Annotation property used in SHACL shapes. Name of the properties that are being validated in a SHACL shape.
range: anyURI

applicable
type: AnnotationProperty
created: 2024-11-22
comment: Annotation used to point to the applicability of a parameter in RINF. Values are Y/N/NYA
term status: stable
range: string

Canonical URI
type: AnnotationProperty
SHACL shape validation rule: CanonicalURI
created: 2022-12-13
modified: 2024-02-06
comment: The canonical URI is defined for each instance of an Infrastructure element, e.g. section of line, operational point, track, tunnel, siding. Objects of the infrastructure generated through RML mappings include (when provided) their validity start and end dates. With its identifier, plus all identifiers of its "parent" elements, and its validity dates, a hash URI is generated. The canonical URI is the element's URI with its identifiers and without the validity dates. All of the hash URIs of an element point to its canonical URI. Additionally, SoLs point to the canonical URIs of their start OP and end OP.
range: anyURI
domain: Infrastructure element

dependency note
type: AnnotationProperty
created: 2024-12-02
comment: This property is used to specify dependencies in natural language not covered by skos:scopeNote
term status: stable
range: string

ERATV index
type: AnnotationProperty
created: 2020-11-03
modified: 2020-11-03
modified: 2024-08-13
comment: Index code used in the original definition of a parameter in ERATV.
term status: stable
range: string

format note
type: AnnotationProperty
created: 2024-12-03
comment: This property is used to annotate in human readable the format of parameters
term status: stable
range: string

Hash source
type: AnnotationProperty
created: 2024-02-06
comment: This property indicates for each infrastructure element, the source, i.e. the identifier or key that was input to the hash function in order to generate the hash value that is part of the hash URI.
range: string
domain: Infrastructure element

in SKOS Concept Scheme
type: AnnotationProperty
created: 2022-11-17
modified: 2024-08-13
comment: Property that links an object SKOS property to a the URI of the corresponding SKOS Concept Scheme.
term status: stable
range: ConceptScheme
domain: ObjectProperty

legal deadline
type: AnnotationProperty
created: 2024-11-22
comment: Annotation used to point to legal obligation of a parameter in RINF
term status: stable
range: string

RINF index
type: AnnotationProperty
created: 2020-11-03
modified: 2020-11-03
modified: 2024-08-13
comment: Index code used in the original definition of a parameter in RINF.
term status: stable
range: string

scope
type: AnnotationProperty
created: 2024-11-04
comment: Annotation property used in SHACL shapes. Indicates if the SHACL shape is validating a property of a specific instance ("local"), or if it needs to check other instances ("global"). For example, SHACL shape to validate no repeated ids within a specific track.
range: string

SHACL shape validation rule
type: AnnotationProperty
created: 2024-11-04
comment: Annotation used to point to the SHACL shape that implements the validation for a certain RINF parameter (property). Each shape contains constraints for valid datatypes, patterns, min and max count, valid SKOS values and business rules.

TenT reference
type: AnnotationProperty
created: 2024-11-26
comment: Used to annotate properties coming from the TenT regulations, to be used for monitoring the provision of the data.
term status: stable
range: string

TSI operation appendix D1 index
type: AnnotationProperty
created: 2024-11-26
comment: The index of a vocabulary term in Appendix D1 Vehicle and train Route compatibility checks.
term status: stable
alternative label: Appendix D1 index
range: string

TSI operation appendix D2 index
type: AnnotationProperty
created: 2022-11-04
modified: 2024-08-13
modified: 2024-11-26
comment: The index of a vocabulary term in Appendix D2 Elements the infrastructure manager has to provide to the railway undertaking for the Route Book from the document Commission Implementing Regulation (EU) 2019/773 of 16 May 2019 on the technical specification for interoperability relating to the operation and traffic management subsystem of the rail system within the European Union and repealing Decision 2012/757/EU.
alternative label: Appendix D2 index
range: string

TSI operation appendix D3 index
type: AnnotationProperty
created: 2022-11-04
modified: 2024-08-13
modified: 2024-11-26
comment: The index of a vocabulary term in Appendix D3 ERTMS trackside engineering information relevant to operation that the infrastructure manager shall provide to the railway undertaking.
term status: stable
alternative label: Appendix D3 index
range: string

Unit of measure
type: AnnotationProperty
created: 2024-05-16
modified: 2024-08-13
comment: Magnitude of a quantity, defined and adopted by convention or by law, that is used as a standard for measurement of the same kind of quantity.
range: unit
domain: DatatypeProperty

Parameter is used in Route Compatibility Check (RCC) calculations
type: AnnotationProperty
created: 2023-04-12
comment: Indicates whether a RINF parameter is used in Route Compatibility Check calculations according to Commission Implementing Regulation (EU) 2019/773 of 16 May 2019 on the technical specification for interoperability relating to the operation and traffic management subsystem of the rail system within the European Union and repealing Decision.
range: boolean

Existence and TSI compliance of rules for magnetic fields emitted by a vehicle
type: ObjectProperty
range: Concept
applicable: Y/N/NYA
in SKOS Concept Scheme: TSIExistenceAndCompliances
legal deadline: 12 months after publication of Article 7 Guide
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.1.1.3.9.1
RINF index: 1.2.1.1.8.1
created: 2021-08-09
is replaced by: Existence and TSI compliance of rules for magnetic fields emitted by a vehicle
modified: 2021-09-12
modified: 2024-04-25
modified: 2025-03-04
comment: Indication whether rules exist and are compliant with the TSI.
deprecated: true
term status: stable

Existence and TSI compliance of limits in harmonics in the traction current of vehicles
type: ObjectProperty
range: Concept
applicable: Y/N/NYA
in SKOS Concept Scheme: TSICompliances
legal deadline: 12 months after publication of Article 7 Guide for OP tracks
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.1.1.3.9.2
RINF index: 1.2.1.1.8.2
created: 2021-08-09
is replaced by: Existence and TSI compliance of limits in harmonics in the traction current of vehicles
modified: 2021-09-12
modified: 2025-03-04
source: oj
comment: Indication whether rules exist and are compliant with the TSI.
deprecated: true
term status: stable
scope note: 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. none shall be selected when respective national rules do not exist.

Acceleration allowed near level crossing
type: ObjectProperty
sub property of: Health, safety and environment
type: FunctionalProperty
domain: Class
  union of: Subset with common characteristics
  union of: Track
range: ERA Document
XML name: IHS_AccelerationLevelCrossing
applicable: Y/N
dependency note: Mandatory value when the level crossing is defined
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.1.1.1.7.3
SHACL shape validation rule: AccelerationLevelCrossing
SHACL shape validation rule: AccelerationLevelCrossingApplicability
created: 2021-08-03
modified: 2024-01-08
modified: 2024-11-20
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.
term status: stable
scope note: 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.

Documents available by the IM relating to braking performance
type: ObjectProperty
sub property of: Brake related parameters
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: ERA Document
XML name: CBP_BrakePerfDocRef
applicable: Y/N
dependency note: Only applicable when for parameter 1.1.1.3.11.2 True is selected
legal deadline: 16 January 2020
RINF index: 1.1.1.3.11.3
SHACL shape validation rule: AdditionalBrakingInformationDocument
SHACL shape validation rule: AdditionalBrakingInformationDocumentApplicability
used in RCC calculations: true
created: 2020-08-24
modified: 2024-01-08
modified: 2024-04-23
comment: Electronic document available in two EU languages from the IM stored by the Agency providing additional information as defined in point (2) of point 4.2.2.6.2 of TSI OPE.
term status: stable
change note: Change from datatype property to object property in order to point to the class Document (reference document)
scope note: 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.

aggregates
type: ObjectProperty
domain: Non-Linear Element
range: Linear Element
SHACL shape validation rule: Aggregates
created: 2024-11-29
comment: Specifies the linear elements aggregated by a non-linear element.

allocation company
type: ObjectProperty
domain: Subsidiary location
range: Organisation Role
SHACL shape validation rule: AllocationCompany
created: 2024-05-24
modified: 2024-10-24
comment: The organisation in charge to allocate the code for the subsidiary location.

applies to direction
type: ObjectProperty
domain: Net Point Reference
range: Concept
in SKOS Concept Scheme: OrientationDirections
SHACL shape validation rule: AppliesToDirection
SHACL shape validation rule: AppliesToDirectionSKOS
created: 2024-11-29
comment: The direction relative to the origin of the linear element towards the point reference applies.

ATO communication system
type: ObjectProperty
sub property of: Automated Train Operation (ATO)
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: Concept
applicable: Y/N/NYA
dependency note: Applicable when 'ATO Grade of Automation' is applicable
in SKOS Concept Scheme: ATOCommSystem
legal deadline: 12 months after publication of Article 7 Guide
RINF index: 1.1.1.3.13.3
RINF index: 1.2.1.1.10.3
SHACL shape validation rule: AtoCommunicationSystem
SHACL shape validation rule: AtoCommunicationSystemSKOS
TSI operation appendix D2 index: 3.4.9
created: 2023-03-14
modified: 2024-04-18
modified: 2024-12-05
relation: ATO Grade of Automation
relation: ETCS baseline
source: oj
comment: Supported ATO communication systems from trackside.
term status: unstable
scope note: 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

ATO Grade of Automation
type: ObjectProperty
sub property of: Automated Train Operation (ATO)
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: Concept
applicable: Y/N/NYA
dependency note: Parameter only applicable when ETCS Baseline > 4 MR1 and ATO is implemented
in SKOS Concept Scheme: ATOGradeOfAutomation
legal deadline: 12 months after publication of Article 7 Guide
RINF index: 1.1.1.3.13.1
RINF index: 1.2.1.1.10.1
SHACL shape validation rule: AtoGradeAutomation
SHACL shape validation rule: AtoGradeAutomationSKOS
TSI operation appendix D2 index: 3.4.8
created: 2023-03-14
modified: 2024-04-18
modified: 2024-09-19
relation: ETCS baseline
source: oj
comment: ATO grade of automation installed lineside.
term status: stable
scope note: 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
type: ObjectProperty
sub property of: Automated Train Operation (ATO)
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: Concept
applicable: Y/N/NYA
dependency note: Applicable when 'ATO Grade of Automation' is applicable
in SKOS Concept Scheme: ATOSystemVersions
legal deadline: 12 months after publication of Article 7 Guide
RINF index: 1.1.1.3.13.2
RINF index: 1.2.1.1.10.2
SHACL shape validation rule: AtoSystemVersion
SHACL shape validation rule: AtoSystemVersionSKOS
TSI operation appendix D2 index: 3.4.8
created: 2023-03-14
modified: 2024-04-18
modified: 2024-09-19
relation: ATO Grade of Automation
relation: ETCS baseline
source: oj
comment: ATO system version according to the specification referenced in Appendix A-1, index [C]
term status: stable
scope note: 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

authorized country
type: ObjectProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: Concept
in SKOS Concept Scheme: country
created: 2020-09-30
modified: 2020-09-30
comment: Indicates the country(ies) in where a vehicle type has been authorized to operate.
term status: stable

Automated Train Operation (ATO)
type: ObjectProperty
sub property of: Control-command and signalling subsystem
RINF index: 1.1.1.3.13
RINF index: 1.2.1.1.10
created: 2024-10-31

axle bearing condition monitoring
type: ObjectProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: Concept
ERATV index: 4.9.2
in SKOS Concept Scheme: AxleBearingMonitoring
created: 2020-08-24
modified: 2021-08-02
comment: Axle bearing condition monitoring.
term status: stable

belongs to
type: ObjectProperty
inverse of: contains
domain: Infrastructure element
range: Subset with common characteristics
SHACL shape validation rule: BelongsTo
SHACL shape validation rule: BelongsToUniqueIM
created: 2024-05-24
modified: 2024-10-24
comment: Indicates that an infrastructure element belongs to a certain subset that contains common characteristics.

border point of
type: ObjectProperty
inverse of: Border point information per country
domain: Operational Point
range: Operational Point
created: 2023-01-20
is replaced by: Reference border point
is replaced by: reference border point
modified: 2024-10-25
comment: Relates the information that each country maintains on a border point, to the operational point that represents the general information on the border point.
deprecated: true
term status: stable

Brake related parameters
type: ObjectProperty
sub property of: Control-command and signalling subsystem
RINF index: 1.1.1.3.11
created: 2024-10-31

Cant Deficiency used for the basic SSP
type: ObjectProperty
sub property of: TSI compliant train protection system (ETCS)
type: FunctionalProperty
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: Concept
applicable: Y/N/NYA
dependency note: A value has to be provided when ETCS is present (a value is provided on 1.1.1.3.2.1).
in SKOS Concept Scheme: CantDeficiencies
legal deadline: 12 months after publication of Article 7 Guide
RINF index: 1.1.1.3.2.14
RINF index: 1.2.1.1.1.14
SHACL shape validation rule: CantDeficiencyBasicSSP
SHACL shape validation rule: CantDeficiencyBasicSSPApplicability
SHACL shape validation rule: CantDeficiencyBasicSSPSKOS
TSI operation appendix D3 index: 1.3
Unit of measure: MilliM
created: 2023-03-14
modified: 2024-01-08
modified: 2024-04-18
modified: 2024-09-19
modified: 2025-02-28
relation: European Train Control System (ETCS) level
relation: Other Cant Deficiency train categories for which the ETCS trackside is configured to provide SSP
source: oj
comment: Essential information for railway undertakings 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".
term status: stable
scope note: 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.

carrier linear element
type: ObjectProperty
domain: Orientation
range: Linear Element
SHACL shape validation rule: CarrierLinearElement
created: 2025-01-30
comment: The carrier linear element in relation to which the orientation is based on

category
type: ObjectProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: Concept
ERATV index: 1.4
in SKOS Concept Scheme: Categories
created: 2020-07-29
is replaced by: Vehicle category
modified: 2021-08-03
modified: 2025-02-13
comment: (Deprecated) Vehicle category.
deprecated: true
term status: stable

Declarations of verification for track
type: ObjectProperty
sub property of: Control-command and signalling subsystem
RINF index: 1.1.1.3.1
created: 2024-10-31

Control-command and signalling subsystem
type: ObjectProperty
sub property of: RINF Technical characteristic
RINF index: 1.1.1.3
created: 2024-10-31

Certificate
type: ObjectProperty
domain: Vehicle Type
range: Certificate
created: 2022-06-15
modified: 2022-11-15
modified: 2024-04-18
modified: 2024-10-30
comment: For this Vehicle Type, the type or design examination certificate described in the relevant verification module as issued by Notified Bodies, supporting the EC Declaration(s) of Verification for the subsystems in scope of the type's authorisation by an authorizing entity.
deprecated: true
term status: stable

Company code category
type: ObjectProperty
range: Concept
in SKOS Concept Scheme: CompanyCodeCategories
created: 2023-04-04
modified: 2024-10-25
comment: Category of a Railway company. Can be Infrastructure, Freight or Passenger. Deprecated as it will be integrated with the Organisations properties.
deprecated: true
term status: stable

Document with the procedure(s) for static and dynamic route compatibility checks
type: ObjectProperty
sub property of: Performance parameter
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: ERA Document
XML name: IPP_StructureCheckDocRef
applicable: Y/N
legal deadline: 16 January 2020
RINF index: 1.1.1.1.2.4.4
SHACL shape validation rule: CompatibilityProcedureDocument
used in RCC calculations: true
created: 2023-03-14
modified: 2024-04-23
modified: 2024-09-19
comment: Electronic document available in two EU languages from the IM stored by the Agency with: - precise procedures for the static and dynamic route compatibility checks; Or - relevant information for carrying out the checks for specific structures.
term status: stable
change note: Change from datatype property to object property in order to point to the class Document (reference document)
scope note: 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.

Permission for regenerative braking
type: ObjectProperty
sub property of: Track parameters
sub property of: Track resistance to applied loads
type: FunctionalProperty
domain: Contact Line System
range: Concept
XML name: ECS_RegenerativeBraking
applicable: Y/N
dependency note: When `not electrified` is chosen in parameter 1.1.1.2.2.1.1, then this parameter is not applicable.
in SKOS Concept Scheme: RegenerativeBraking
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.1.1.2.2.4
SHACL shape validation rule: ConditionalRegenerativeBrake
SHACL shape validation rule: ConditionalRegenerativeBrakeSKOS
TSI operation appendix D2 index: 3.3.7
used in RCC calculations: true
created: 2020-08-24
modified: 2023-01-20
modified: 2024-09-25
modified: 2024-12-10
modified: 2025-02-28
relation: Type of contact line system
comment: Indication whether regenerative braking is permitted, not permitted, or permitted under specific conditions.
term status: stable
scope note: 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
type: ObjectProperty
sub property of: Contact line system
type: FunctionalProperty
domain: Contact Line System
range: ERA Document
applicable: Y/N/NYA
dependency note: 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.
legal deadline: 12 months after publication of Article 7 Guide
RINF index: 1.1.1.2.2.4.1
SHACL shape validation rule: ConditionsAppliedRegenerativeBraking
SHACL shape validation rule: ConditionsAppliedRegenerativeBrakingApplicability
TSI operation appendix D2 index: 3.3.7
created: 2022-11-10
modified: 2023-03-14
modified: 2024-04-18
modified: 2024-11-04
modified: 2025-02-28
relation: Type of contact line system
source: oj
source: http://data.europa.eu/eli/reg_impl/2019/777/2023-09-28
comment: Name and/or reference of the document specifying the conditions applying in regards to regenerative braking.
term status: stable
scope note: 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
type: ObjectProperty
sub property of: Transitions between systems
type: FunctionalProperty
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: ERA Document
applicable: Y/N/NYA
dependency note: Applicable when at least two different class of protection systems exist.
legal deadline: 12 months after publication of Article 7 Guide
RINF index: 1.1.1.3.8.3
RINF index: 1.2.1.1.7.3
SHACL shape validation rule: ConditionsSwitchClassBSystems
SHACL shape validation rule: ConditionsSwitchClassBSystemsApplicability
TSI operation appendix D2 index: 3.4.3
created: 2022-10-28
modified: 2023-03-14
modified: 2024-04-18
modified: 2024-11-04
modified: 2025-02-28
relation: ETCS
relation: Existence of switch over between different protection, control and warning systems while running
source: oj
comment: Name and/or reference of the document specifying the Special technical conditions required to switch over between ERTMS/ETCS and Class B systems.
term status: stable
scope note: 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.

Conditions for use of reflective plates
type: ObjectProperty
sub property of: Health, safety and environment
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: Concept
applicable: Y/N/NYA
dependency note: A value is mandatory if the value of parameter "Permit of use of reflective plates" is boolean "Yes"
in SKOS Concept Scheme: ConditionsUseReflectivePlates
legal deadline: 12 months after publication of Article 7 Guide
RINF index: 1.1.1.1.7.12.1
SHACL shape validation rule: ConditionsUseReflectivePlates
SHACL shape validation rule: ConditionsUseReflectivePlatesSKOS
created: 2023-03-14
modified: 2024-09-24
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.
see also: 4.2.2.1.3.2 of TSI OPE (Commission Implementing Regulation (EU) 2019/773 of 16 May 2019)
term status: stable
scope note: 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.

connected to
type: ObjectProperty
sub property of: Running track generic information
type: SymmetricProperty
type: IrreflexiveProperty
domain: Track
range: Track
applicable: Y/N/NYA
legal deadline: 12 months after publication of Article 7 Guide
RINF index: 1.1.1.0.1.2
RINF index: 1.2.4.1
created: 2025-03-10
comment: Represents a bidirectional connection between two Track instances.
term status: stable
alternative label: Internal connection
alternative label: Tracks connectivity to operational points
example: Track_A connectedTo Track_B implies Track_B connectedTo Track_A.
scope note: 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.

contact line system
type: ObjectProperty
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: Contact Line System
SHACL shape validation rule: ContactLineSystem
created: 2020-08-24
modified: 2021-09-11
modified: 2025-02-28
comment: System that is used to transmit electrical energy to road or rail vehicles.
term status: stable
scope note: It can be repeated as many times as the number of different contact line system types are present. For RDF data provision: The value of this property is an instance of the era:ContactLineSystem, which has as properties the parameters 1.1.1.2.2.1.2, 1.1.1.2.2.2, 1.1.1.2.2.4 and 1.1.1.2.5.1. 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.2.2.1.2, 1.1.1.2.2.2, 1.1.1.2.2.4 and 1.1.1.2.5.1.

Contact line system
type: ObjectProperty
sub property of: Energy subsystem
RINF index: 1.1.1.2.2
created: 2024-10-31

Type of contact line system
type: ObjectProperty
sub property of: Contact line system
type: FunctionalProperty
domain: Contact Line System
range: Concept
XML name: ECS_SystemType
applicable: Y/N
dependency note: If this parameter is repeated, parameters 1.1.1.2.2.1.2, and 1.1.1.2.2.2 shall be created also for the corresponding type. These two parameters are to be considered children of the current.
in SKOS Concept Scheme: ContactLineSystems
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.1.1.2.2.1.1
SHACL shape validation rule: ContactLineSystemType
SHACL shape validation rule: ContactLineSystemTypeNotElectrifiedApplicability
SHACL shape validation rule: ContactLineSystemTypeSKOS
SHACL shape validation rule: ContactLineSystemTypeThirdOrFourthRailApplicability
used in RCC calculations: true
created: 2021-08-06
modified: 2021-08-06
modified: 2025-02-28
comment: Indication of the type of the contact line system.
term status: stable
scope note: When the value is "not electrified", then all parameters 1.1.1.2.2.1.2 - 1.1.1.2.5.3 are not applicable. When the value is “Third Rail” or “Fourth Rail”, then parameters 1.1.1.2.2.3, 1.1.1.2.2.5 - 1.1.1.2.4.2.3, 1.1.1.2.5.2 and 1.1.1.2.5.3 are not applicable For RINF XML data sets: As long as the data provision through XML data sets is allowed, if this parameter is repeated, parameters 1.1.1.2.2.1.2, 1.1.1.2.2.2, 1.1.1.2.2.4 and 1.1.1.2.5.1 shall be created also for the corresponding type. These four parameters are to be considered children of the current. For grouping “children” parameters of the current parameter, an XML attribute called “set” must be declared at the parent and children levels with the same keyword value.

Permitted contact strip material
type: ObjectProperty
sub property of: Pantograph
sub property of: Vehicle type technical characteristic
type: FunctionalProperty
domain: Class
  union of: Subset with common characteristics
  union of: Running track
  union of: Vehicle Type
range: Concept
XML name: EPA_StripMaterial
applicable: Y/N
dependency note: Mandatory only if “Overhead contact line (OCL)” is selected in 1.1.1.2.2.1.1, otherwise the parameter is not applicable.
ERATV index: 4.10.10
in SKOS Concept Scheme: ContactStripMaterials
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.1.1.2.3.4
SHACL shape validation rule: ContactStripMaterialApplicability
SHACL shape validation rule: ContactStripMaterialSKOS
used in RCC calculations: true
created: 2020-08-25
modified: 2021-09-12
modified: 2024-09-25
modified: 2025-02-28
relation: Type of contact line system
comment: Indication of which contact strip materials are permitted to be used.
see also: LOC&PAS TSI: 4.2.8.2.9.4.2
term status: stable
scope note: [NN] for impregnated carbon concern the metallic content in %. In case of selection of this option, the respective value of the metallic content has to be added. [NN] is the maximum percentage allowed. In case of permitted material different than specified in predefined list, send ERA a change request. When more than one value of the parameter has to be published, then parameter will to be repeated as many times as the number of values.

contains
type: ObjectProperty
domain: Subset with common characteristics
range: Infrastructure element
SHACL shape validation rule: Contains
created: 2024-10-31
comment: Indicates that a subset with common characteristics contains a certain infrastructure element.

Data GSM-R network
type: ObjectProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: Concept
ERATV index: 4.13.2.11
in SKOS Concept Scheme: GSMRNetworks
created: 2020-08-31
modified: 2021-08-02
comment: Data SIM Card GSM-R Home Network.
term status: stable

Radio system compatibility data
type: ObjectProperty
sub property of: TSI compliant radio (RMR)
sub property of: Vehicle type technical characteristic
domain: Class
  union of: Subset with common characteristics
  union of: Running track
  union of: Vehicle Type
range: Concept
applicable: Y/N/NYA
dependency note: GSM-R and ETCS L2 must be installed for this parameter to be applicable.
ERATV index: 4.13.2.8
in SKOS Concept Scheme: RadioSystemCompatibilitiesData
legal deadline: 12 months after publication of Article 7 Guide for OP tracks
legal deadline: 16 January 2020
RINF index: 1.1.1.3.3.10
RINF index: 1.2.1.1.2.10
SHACL shape validation rule: DataRadioCompatible
SHACL shape validation rule: DataRadioCompatibleApplicability
SHACL shape validation rule: DataRadioCompatibleSKOS
used in RCC calculations: true
created: 2020-08-31
modified: 2021-09-12
modified: 2024-04-18
modified: 2024-09-19
modified: 2025-03-04
relation: European Train Control System (ETCS) level
source: oj
comment: Radio requirements used for demonstrating technical compatibility data.
term status: stable
scope note: 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.

Defines subset
type: ObjectProperty
domain: Infrastructure manager
range: Subset with common characteristics
created: 2022-11-04
modified: 2023-03-14
comment: (deprecated) not in use anymore. For the purposes of the register of infrastructure, each infrastructure manager may describe its railway network optionally via common characteristic subsets.
deprecated: true
term status: stable

direction
type: ObjectProperty
domain: Orientation
range: Concept
in SKOS Concept Scheme: OrientationDirections
SHACL shape validation rule: Direction
SHACL shape validation rule: DirectionSKOS
created: 2024-04-23
comment: The direction of the orientation of a railway element, in relation to the carrier linear element
editorial note: To review the orientation direction

Document with restriction related to the position of Multiple Traction unit(s) to comply with contact line separation
type: ObjectProperty
sub property of: Requirements for rolling stock
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: ERA Document
applicable: Y/N/NYA
legal deadline: 12 months after publication of Article 7 Guide
RINF index: 1.1.1.2.5.5
SHACL shape validation rule: DocumentRestrictionPositionContactLineSeparation
created: 2023-03-14
modified: 2024-11-04
comment: Name and/or reference of the document specifying the restriction(s) related to the position of Multiple Traction unit(s) to comply with contact line separation.
term status: stable
scope note: 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 restriction related to power consumption of specific electric traction unit(s)
type: ObjectProperty
sub property of: Requirements for rolling stock
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: ERA Document
applicable: Y/N/NYA
legal deadline: 12 months after publication of Article 7 Guide
RINF index: 1.1.1.2.5.4
SHACL shape validation rule: DocumentRestrictionPowerConsumption
created: 2023-03-14
modified: 2024-11-04
comment: Name and/or reference of the document specifying the restriction(s) related to power consumption of specific electric traction unit(s).
term status: stable
scope note: 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 eddy current brakes
type: ObjectProperty
sub property of: Track parameters
sub property of: Track resistance to applied loads
type: FunctionalProperty
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: Concept
applicable: Y/N/NYA
in SKOS Concept Scheme: EddyCurrentBraking
legal deadline: 12 months after publication of Article 7 Guide for OP tracks
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.1.1.1.6.2
RINF index: 1.2.1.0.4.2
SHACL shape validation rule: EddyCurrentBraking
SHACL shape validation rule: EddyCurrentBrakingSKOS
TSI operation appendix D2 index: 3.4.5
used in RCC calculations: true
created: 2020-08-24
modified: 2022-09-06
modified: 2024-09-19
modified: 2025-02-28
modified: 2025-03-04
source: http://data.europa.eu/eli/reg/2014/1299/2023-09-28
source: oj
comment: Indication of limitations on the use of eddy current brakes.
see also: INF TSI: 4.2.6.2.2 (2) OPE TSI: 4.2.2.6.2 (1) (iv)
term status: stable
editorial note: This property has been modified to be a RINF parameter (its eratvIndex is deleted). It is treated as a SKOS by RINF and as a boolean by ERATV. A new ERATV datatype property has been defined, eddyCurrentBrakingFitted with boolean values.
scope note: 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.

Document with the conditions for the use of eddy current brakes
type: ObjectProperty
sub property of: Track resistance to applied loads
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: ERA Document
XML name: ILR_ECBDocRef
applicable: Y/N
dependency note: 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
legal deadline: 16 January 2020
RINF index: 1.1.1.1.6.4
SHACL shape validation rule: EddyCurrentBrakingConditionsDocument
SHACL shape validation rule: EddyCurrentBrakingConditionsDocumentApplicability
TSI operation appendix D2 index: 3.4.5
used in RCC calculations: true
created: 2020-08-24
modified: 2021-09-10
modified: 2024-04-23
modified: 2024-09-19
source: oj
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.
term status: stable
change note: Change from datatype property to object property in order to point to the class Document (reference document)
scope note: 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.

Element A
type: ObjectProperty
domain: Net Relation
range: Linear Element
RINF index: 1.1.1.0.1.2
RINF index: 1.2.4.1
SHACL shape validation rule: ElementA
created: 2021-04-01
modified: 2023-03-14
modified: 2024-11-29
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.
term status: stable
alternative label: Internal connection

Element B
type: ObjectProperty
domain: Net Relation
range: Linear Element
RINF index: 1.1.1.0.1.2
RINF index: 1.2.4.1
SHACL shape validation rule: ElementB
created: 2021-04-01
modified: 2023-03-14
modified: 2024-11-29
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.
term status: stable
alternative label: Internal connection

Element part
type: ObjectProperty
created: 2021-04-01
modified: 2021-04-01
comment: References the topology object of a higher-granularity level which contains a lower-granularity topology object.
deprecated: true
term status: stable

End coupling type
type: ObjectProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: Concept
ERATV index: 4.9.1
in SKOS Concept Scheme: EndCouplingType
created: 2021-08-31
modified: 2021-08-31
comment: Type of end coupling (indicating tensile and compressive forces).
term status: stable

End of tunnel
type: ObjectProperty
sub property of: Tunnel
sub property of: hasGeometry
type: FunctionalProperty
domain: Tunnel
range: Point
XML name: SOLTunnelEnd
applicable: Y
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.1.1.1.8.4
SHACL shape validation rule: EndLocation
created: 2020-07-29
modified: 2024-02-05
modified: 2024-09-19
comment: Geographical coordinates in decimal degrees and km of the line at the end of a tunnel.
term status: stable
example: Latitude=`51.5479123` Longitude=`-0.076732`
scope note: 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.

ends at
type: ObjectProperty
domain: Net Linear Reference
range: Net Point Reference
SHACL shape validation rule: EndsAt
created: 2024-11-29
comment: Specifies the ending point of a linear reference.

Energy subsystem
type: ObjectProperty
sub property of: RINF Technical characteristic
RINF index: 1.1.1.2
created: 2024-10-31

Energy supply system (Voltage and frequency)
type: ObjectProperty
sub property of: Contact line system
sub property of: Vehicle type technical characteristic
type: FunctionalProperty
domain: Class
  union of: Contact Line System
  union of: Vehicle Type
range: Concept
XML name: ECS_VoltFreq
applicable: Y/N
dependency note: When `not electrified` is chosen in parameter 1.1.1.2.2.1.1, then this parameter is not applicable.
ERATV index: 4.10.1
in SKOS Concept Scheme: EnergySupplySystems
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.1.1.2.2.1.2
SHACL shape validation rule: EnergySupplySystem
SHACL shape validation rule: EnergySupplySystemSKOS
TSI operation appendix D2 index: 3.3.1
used in RCC calculations: true
created: 2020-08-24
modified: 2024-01-08
modified: 2024-09-19
modified: 2025-02-28
relation: Type of contact line system
source: http://data.europa.eu/eli/reg/2014/1301/2023-09-28
source: oj
comment: Indication of the traction supply system (nominal voltage and frequency).
see also: EN 50163:2004+A1:2007+A2:2020+A3:2022: clause 4 ENE TSI:4.2.3
term status: stable
scope note: 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

Error corrections required for the on-board ETCS, GSM-R and/or ATO function
type: ObjectProperty
sub property of: Declarations of verification for track
type: FunctionalProperty
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: Concept
applicable: Y/N
dependency note: A value has to be provided when ETCS is present (a value is provided on 1.1.1.3.2.1).
in SKOS Concept Scheme: OnboardErrorCorrections
legal deadline: 12 months after the entry into force of TSI CCS and at least 12 months after publication of Article 7 Guide
RINF index: 1.1.1.3.1.2
RINF index: 1.2.1.1.1.19
SHACL shape validation rule: ErrorCorrectionsOnboard
SHACL shape validation rule: ErrorCorrectionsOnboardSKOS
created: 2024-04-18
modified: 2025-02-18
modified: 2025-02-28
replaces: (Deprecated) ERTMS error corrections required for the on-board.
replaces: (Deprecated) ETCS error corrections required for the on-board.
replaces: (Deprecated) GSM-R error corrections required for the on-board
source: oj
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). An additional parameter (era:errorCorrectionsOnboardExplanation) must document if a non-implemented CR has been accepted by the IM.
term status: stable
scope note: 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.

TSI compliant train protection system (ETCS)
type: ObjectProperty
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: ETCS
SHACL shape validation rule: Etcs
created: 2021-08-07
modified: 2021-09-12
modified: 2024-08-13
modified: 2024-09-19
modified: 2025-02-28
comment: European Train Control System (ETCS) application level supported by the track side equipment.
term status: stable
scope note: 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.

ETCS baseline
type: ObjectProperty
sub property of: TSI compliant train protection system (ETCS)
sub property of: Vehicle type technical characteristic
type: FunctionalProperty
domain: Class
  union of: ETCS
  union of: Vehicle Type
range: Concept
applicable: Y/N/NYA
dependency note: A value has to be provided when ETCS is present (a value is provided on 1.1.1.3.2.1).
ERATV index: 4.13.1.2
in SKOS Concept Scheme: ETCSBaselines
legal deadline: 12 months after publication of Article 7 Guide for OP tracks
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.1.1.3.2.2
RINF index: 1.2.1.1.1.2
SHACL shape validation rule: EtcsBaseline
SHACL shape validation rule: EtcsBaselineApplicability
SHACL shape validation rule: EtcsBaselineSKOS
TSI operation appendix D2 index: 3.2.7
created: 2021-08-07
modified: 2021-08-31
modified: 2024-04-18
modified: 2024-09-19
modified: 2025-02-28
modified: 2025-03-04
relation: European Train Control System (ETCS) level
source: oj
comment: ETCS baseline installed lineside.
see also: TSI CCS (Table A2)
term status: stable
scope note: The ETCS baseline needs to be provided for each available ETCS Level. See: TSI CCS (Table A2)

ETCS level for degraded situation
type: ObjectProperty
sub property of: Line-side system for degraded situation
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: Concept
applicable: Y/N/NYA
dependency note: Mandatory when ETCS is present.
in SKOS Concept Scheme: ETCSSituations
legal deadline: 12 months after publication of Article 7 Guide for OP tracks
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.1.1.3.10.1
RINF index: 1.2.1.1.9.1
SHACL shape validation rule: EtcsDegradedSituation
SHACL shape validation rule: EtcsDegradedSituationApplicability
SHACL shape validation rule: EtcsDegradedSituationSKOS
TSI operation appendix D2 index: 3.4.1
created: 2021-08-09
modified: 2021-09-12
modified: 2024-04-18
modified: 2024-09-19
modified: 2025-03-04
relation: European Train Control System (ETCS) level
source: http://data.europa.eu/eli/reg_impl/2019/773/2023-09-28
source: oj
comment: ERTMS / ETCS application level for degraded situation related to the track side equipment.
term status: stable
example: Level 1 as a degraded mode for Level 2.
scope note: 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.

ETCS equipment level
type: ObjectProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: Concept
ERATV index: 4.13.1.1
in SKOS Concept Scheme: ETCSEquipmentLevels
created: 2021-08-31
modified: 2021-08-31
comment: ETCS equipment on-board and its level.
term status: stable

ETCS infill installed line-side
type: ObjectProperty
sub property of: TSI compliant train protection system (ETCS)
sub property of: Vehicle type technical characteristic
type: FunctionalProperty
domain: Class
  union of: ETCS
  union of: Vehicle Type
range: Concept
applicable: Y/N/NYA
dependency note: Mandatory in case of ETCS level 1 and infill device(s) are installed. Otherwise it is not applicable.
ERATV index: 4.13.1.3
in SKOS Concept Scheme: ETCSInfills
legal deadline: 12 months after publication of Article 7 Guide for OP tracks
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.1.1.3.2.4
RINF index: 1.2.1.1.1.4
SHACL shape validation rule: EtcsInfill
SHACL shape validation rule: EtcsInfillApplicability
SHACL shape validation rule: EtcsInfillSKOS
created: 2021-08-08
modified: 2021-09-12
modified: 2024-04-18
modified: 2024-09-19
modified: 2025-03-04
relation: European Train Control System (ETCS) level
source: oj
comment: Information about installed trackside equipment capable to transmit infill information by loop or Global System for Mobile communications for Railways (GSM-R) for level 1 installations.
term status: stable
scope note: TSI CCS (4.2.2 & 4.3.3)

European Train Control System (ETCS) level
type: ObjectProperty
sub property of: TSI compliant train protection system (ETCS)
type: FunctionalProperty
domain: ETCS
range: Concept
applicable: Y/N
in SKOS Concept Scheme: ETCSLevels
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.1.1.3.2.1
RINF index: 1.2.1.1.1.1
SHACL shape validation rule: EtcsLevelType
SHACL shape validation rule: EtcsLevelTypeSKOS
TSI operation appendix D2 index: 3.2.7
created: 2021-08-07
modified: 2024-01-08
modified: 2024-04-18
modified: 2024-08-13
modified: 2025-02-28
relation: Cant Deficiency used for the basic SSP
relation: ETCS baseline
relation: ETCS level for degraded situation
relation: ETCS M_version
relation: ETCS system compatibility
relation: Track conditions which can be transmitted
relation: 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
relation: ID of ERTMS/ETCS Radio Block Center
relation: Phone number of ERTMS/ETCS Radio Block Center
source: oj
comment: ETCS application level related to the track side equipment.
see also: TSI CCS (Subset-026, Chapter 2, 2.6)
term status: stable
scope note: 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 M_version
type: ObjectProperty
sub property of: TSI compliant train protection system (ETCS)
type: FunctionalProperty
domain: ETCS
range: Concept
applicable: Y/N/NYA
dependency note: A value has to be provided when ETCS is present (a value is provided on 1.1.1.3.2.1).
in SKOS Concept Scheme: ETCSMVersions
legal deadline: 1 January 2021
legal deadline: 12 months after publication of Article 7 Guide for OP tracks
RINF index: 1.1.1.3.2.10
RINF index: 1.2.1.1.1.10
SHACL shape validation rule: EtcsMVersion
SHACL shape validation rule: EtcsMVersionApplicability
SHACL shape validation rule: EtcsMVersionSKOS
used in RCC calculations: true
created: 2021-08-08
modified: 2021-09-12
modified: 2024-04-18
modified: 2025-02-28
modified: 2025-03-04
relation: European Train Control System (ETCS) level
source: oj
comment: ETCS M_version according to the specification referenced in Appendix A-1, index [C], SRS 7.5.1.9.
term status: stable
scope note: See: TSI CCS (Subset-026, Chapter 7, 7.5.1.79 M_VERSION)

ETCS national packet 44 application implemented
type: ObjectProperty
sub property of: TSI compliant train protection system (ETCS)
domain: Class
  union of: Subset with common characteristics
  union of: Track
range: Concept
applicable: Y/N/NYA
dependency note: A value has to be provided when ETCS is present (a value is provided on 1.1.1.3.2.1).
in SKOS Concept Scheme: ETCSNationalPacket44Functions
SHACL shape validation rule: EtcsNationalPacket44Function
SHACL shape validation rule: EtcsNationalPacket44FunctionSKOS
created: 2024-11-20
modified: 2021-09-12
modified: 2024-04-18
modified: 2025-05-05
relation: European Train Control System (ETCS) level
replaces: ETCS national packet 44 application implemented
source: oj
comment: Indication whether data for national applications is transmitted between track and train.
term status: stable
scope note: 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)

ETCS National Values
type: ObjectProperty
sub property of: TSI compliant train protection system (ETCS)
RINF index: 1.1.1.3.2.16
RINF index: 1.2.1.1.1.16
created: 2024-10-31

document with operating restrictions or conditions
type: ObjectProperty
sub property of: TSI compliant train protection system (ETCS)
type: FunctionalProperty
domain: Class
  union of: Subset with common characteristics
  union of: Track
range: ERA Document
applicable: Y/N/NYA
dependency note: A value has to be provided when ETCS is present (a value is provided on 1.1.1.3.2.1).
SHACL shape validation rule: EtcsRestrictionsConditionsDoc
SHACL shape validation rule: EtcsRestrictionsConditionsDocApplicability
modified: 2025-02-28
modified: 2025-05-05
comment: Indication of the document where restrictions or conditions due to partial compliance with the TSI CCS are described.
scope note: 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 system compatibility
type: ObjectProperty
sub property of: TSI compliant train protection system (ETCS)
sub property of: Vehicle type technical characteristic
domain: Class
  union of: ETCS
  union of: Vehicle Type
range: Concept
applicable: Y/N/NYA
dependency note: A value has to be provided when ETCS is present (a value is provided on 1.1.1.3.2.1).
ERATV index: 4.13.1.8
in SKOS Concept Scheme: ETCSSystemCompatibilities
legal deadline: 12 months after publication of Article 7 Guide for OP tracks
legal deadline: 16 January 2020
RINF index: 1.1.1.3.2.9
RINF index: 1.2.1.1.1.9
SHACL shape validation rule: EtcsSystemCompatibility
SHACL shape validation rule: EtcsSystemCompatibilityApplicability
SHACL shape validation rule: EtcsSystemCompatibilitySKOS
used in RCC calculations: true
created: 2020-08-31
modified: 2021-09-12
modified: 2024-09-19
modified: 2025-03-04
relation: European Train Control System (ETCS) level
source: oj
comment: ETCS requirements used for demonstrating technical compatibility.
term status: stable
scope note: 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.

Track conditions which can be transmitted
type: ObjectProperty
sub property of: TSI compliant train protection system (ETCS)
domain: ETCS
range: Concept
applicable: Y/N/NYA
dependency note: 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.
in SKOS Concept Scheme: TransmittedTrackConditions
legal deadline: 12 months after publication of Article 7 Guide
RINF index: 1.1.1.3.2.12.1
RINF index: 1.2.1.1.1.12.1
SHACL shape validation rule: EtcsTransmittedTrackConditions
SHACL shape validation rule: EtcsTransmittedTrackConditionsApplicability
SHACL shape validation rule: EtcsTransmittedTrackConditionsSKOS
TSI operation appendix D3 index: 1.1
created: 2022-11-16
modified: 2023-03-14
modified: 2023-04-18
modified: 2025-02-28
relation: European Train Control System (ETCS) level
source: oj
comment: Transmittable track conditions by the CCSSubsystem, according to the specification referenced in Appendix A-1, index [C]
term status: unstable
scope note: See: TSI CCS (Subset-026, Chapter 5, section 5.18.1.1)

Fire safety category
type: ObjectProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: Concept
ERATV index: 4.4.1
in SKOS Concept Scheme: Categories
created: 2020-08-29
modified: 2021-08-03
comment: Fire safety category for tunnels.
term status: stable

Part of a Railway Freight Corridor
type: ObjectProperty
sub property of: Performance parameter
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: Concept
XML name: IPP_FreightCorridor
applicable: Y/N
in SKOS Concept Scheme: FreightCorridors
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.1.1.1.2.3
RINF index: 1.2.1.0.2.3
SHACL shape validation rule: FreightCorridor
SHACL shape validation rule: FreightCorridorSKOS
created: 2021-08-03
modified: 2024-01-08
modified: 2024-09-19
source: http://data.europa.eu/eli/reg/2010/913/2024-07-18
comment: Indication whether the line is designated to a Railway Freight Corridor.
see also: [6] Reg 913/2010/EC
term status: stable
scope note: Not applicable if the line is not part of an RFC. If a line belongs to several corridors, repeat the parameter.

Section with train detection limitation, only for the French network
type: ObjectProperty
domain: Train Detection System
range: Concept
in SKOS Concept Scheme: FrenchTrainDetectionSystemLimitations
created: 2020-08-24
is replaced by: Section with train detection limitation
is replaced by: Section with train detection limitation number, only for French network
modified: 2022-04-05
comment: Specific for route compatibility check on French network. The reason for deprecation is because of replacement by a class, an object property and two datatype properties. The reason is that the property is composed of two values: A boolean [Y/N] and a number N is between 1 and 8.
deprecated: true
term status: stable

Section with train detection limitation number, only for French network
type: ObjectProperty
domain: Section with train detection limitation
range: Concept
in SKOS Concept Scheme: FrenchTrainDetectionSystemLimitationNumbers
SHACL shape validation rule: FrenchTrainDetectionSystemLimitationNumber
SHACL shape validation rule: FrenchTrainDetectionSystemLimitationNumberSKOS
created: 2023-04-05
modified: 2024-04-18
modified: 2025-02-18
modified: 2025-03-11
relation: Section with train detection limitation
replaces: Section with train detection limitation, only for the French network
comment: Part of the section with train detection limitation that indicates the type of train detection limitation. Specific for route compatibility check on French network. 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
term status: stable

Frequency bands for detection
type: ObjectProperty
sub property of: Train detection systems defined based on frequency bands
type: FunctionalProperty
domain: Train Detection System
range: Concept
applicable: Y/N/NYA
in SKOS Concept Scheme: FrequencyBandsForDetection
legal deadline: 12 months after publication of Article 7 Guide
RINF index: 1.1.1.3.4.2
RINF index: 1.2.1.1.3.2
SHACL shape validation rule: FrequencyBandsForDetection
SHACL shape validation rule: FrequencyBandsForDetectionSKOS
used in RCC calculations: true
created: 2023-03-14
modified: 2024-04-18
relation: Maximum interference current
relation: Vehicle impedance
relation: Maximum magnetic field
source: oj
comment: Bands of the frequency management of the train detection systems as defined in the TSI CCS, and in the specific cases or technical documents referred to in Article 13 of TSI CCS when they are available.
term status: unstable
scope note: 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

Gauging
type: ObjectProperty
sub property of: Line layout
sub property of: Vehicle type technical characteristic
domain: Class
  union of: Subset with common characteristics
  union of: Running track
  union of: Vehicle Type
range: Concept
XML name: ILL_Gauging
applicable: Y
ERATV index: 3.1.2.3
ERATV index: 4.2.1
in SKOS Concept Scheme: GaugingProfiles
legal deadline: 16 January 2020
RINF index: 1.1.1.1.3.1.1
RINF index: 1.2.1.0.3.4
SHACL shape validation rule: GaugingProfile
SHACL shape validation rule: GaugingProfileSKOS
used in RCC calculations: true
created: 2020-07-29
modified: 2023-03-14
modified: 2024-06-26
modified: 2024-09-19
modified: 2025-03-08
source: http://data.europa.eu/eli/reg/2014/1299/2023-09-28
source: http://data.europa.eu/eli/reg/2014/1302/2023-09-28
comment: Gauges as defined in European standard or other local gauges, including lower or upper part.
term status: stable
scope note: 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

Document with the transversal section of the particular points requiring specific checks
type: ObjectProperty
sub property of: Line layout
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: ERA Document
XML name: ILL_GaugeCheckDocRef
applicable: Y/N
legal deadline: 16 January 2020
RINF index: 1.1.1.1.3.1.3
RINF index: 1.2.1.0.3.6
SHACL shape validation rule: GaugingTransversalDocument
used in RCC calculations: true
created: 2020-08-24
modified: 2024-04-23
modified: 2024-09-19
comment: Electronic document available from the IM stored by the Agency with the transversal section of the particular points requiring specific checks due to deviations from gauging referred to in parameter "Gauging". Where relevant, guidance for the check with the particular point may be attached to the document with the transversal section.
term status: stable
change note: Change from datatype property to object property in order to point to the class Document (reference document)
scope note: 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.

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
type: ObjectProperty
sub property of: TSI compliant radio (RMR)
type: FunctionalProperty
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: Concept
applicable: Y/N/NYA
dependency note: GSM-R and ETCS level 2 must be installed for this parameter to be applicable.
in SKOS Concept Scheme: NumberActiveMobiles
legal deadline: 12 months after publication of Article 7 Guide for OP tracks
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.1.1.3.3.2
RINF index: 1.2.1.1.2.2
SHACL shape validation rule: GsmRActiveMobiles
SHACL shape validation rule: GsmRActiveMobilesApplicability
SHACL shape validation rule: GsmRActiveMobilesSKOS
created: 2021-08-08
modified: 2021-09-12
modified: 2024-04-18
relation: European Train Control System (ETCS) level
source: oj
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.
term status: stable
scope note: 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.

Additional information on network characteristics
type: ObjectProperty
sub property of: TSI compliant radio (RMR)
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: ERA Document
applicable: Y/N/NYA
dependency note: GSM-R must be installed for this parameter to be applicable
legal deadline: 1 January 2021
legal deadline: 12 months after publication of Article 7 Guide for OP tracks
RINF index: 1.1.1.3.3.3.1
RINF index: 1.2.1.1.2.3.1
SHACL shape validation rule: GsmRAdditionalInfo
SHACL shape validation rule: GsmRAdditionalInfoApplicability
created: 2021-08-08
modified: 2021-09-12
modified: 2024-04-18
modified: 2024-09-19
relation: GPRS for ETCS
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.
term status: stable
change note: Change from datatype property to object property in order to point to the class Document (reference document)
scope note: 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.

Optional GSM-R functions
type: ObjectProperty
sub property of: TSI compliant radio (RMR)
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: Concept
applicable: Y/N/NYA
dependency note: GSM-R (parameter 1.1.1.3.3.1) must be installed for this parameter to be applicable
in SKOS Concept Scheme: OptionalFunctions
legal deadline: 12 months after publication of Article 7 Guide for OP tracks
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.1.1.3.3.3
RINF index: 1.2.1.1.2.3
SHACL shape validation rule: GsmROptionalFunctions
SHACL shape validation rule: GsmROptionalFunctionsApplicability
SHACL shape validation rule: GsmROptionalFunctionsSKOS
created: 2021-08-08
modified: 2021-09-12
modified: 2024-04-18
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.
term status: stable
scope note: (*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 protecti…

GSM-R radio data communication
type: ObjectProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: Concept
ERATV index: 4.13.2.7
in SKOS Concept Scheme: GSMRRadioDataCommunications
created: 2021-08-31
modified: 2021-08-31
comment: GSM-R Radio Data communication on board and its Baseline.
term status: stable

GSM-R version
type: ObjectProperty
sub property of: TSI compliant radio (RMR)
sub property of: Vehicle type technical characteristic
domain: Class
  union of: Subset with common characteristics
  union of: Running track
  union of: Vehicle Type
range: Concept
applicable: Y/N/NYA
dependency note: 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.
ERATV index: 4.13.2.1
in SKOS Concept Scheme: GSMRVersions
legal deadline: 12 months after publication of Article 7 Guide for OP tracks
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.1.1.3.3.1
RINF index: 1.2.1.1.2.1
SHACL shape validation rule: GsmRVersion
SHACL shape validation rule: GsmRVersionSKOS
TSI operation appendix D2 index: 3.1.7
created: 2021-08-08
modified: 2021-09-12
modified: 2024-04-18
modified: 2025-02-28
source: oj
comment: GSM-R functional requirements specification and system requirements specification in accordance with the specification respectively referenced in Appendix A-1, index [E] and index [F], version number installed lineside.
see also: Referenced in Appendix A-1, index [E] and index [F]
term status: stable
scope note: 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.

Specific constraints imposed by the GSM-R network operator on ETCS on-board units only able to operate in circuit-switch
type: ObjectProperty
sub property of: TSI compliant radio (RMR)
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: Concept
applicable: Y/N/NYA
dependency note: GSM-R and ETCS L2 must be installed for this parameter to be applicable. Multiple values are allowed.
in SKOS Concept Scheme: GSMRConstraints
legal deadline: 12 months after publication of Article 7 Guide
RINF index: 1.2.1.1.2.12
SHACL shape validation rule: GsmrConstraintsOperateOnlyInCircuitSwitchApplicability
TSI operation appendix D3 index: 2.2
created: 2023-03-14
modified: 2024-04-18
relation: European Train Control System (ETCS) level
source: oj
comment: These constraints, where applicable, are meant to manage the limited number of circuit-switched radio connections that can be handled simultaneously by a Radio Block Center.
term status: stable

GSM-R networks covered by a roaming agreement
type: ObjectProperty
sub property of: TSI compliant radio (RMR)
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: Concept
applicable: Y/N/NYA
dependency note: GSM-R must be installed for this parameter to be applicable
in SKOS Concept Scheme: GSMRNetworks
legal deadline: 12 months after publication of Article 7 Guide for OP tracks
legal deadline: 16 January 2020
RINF index: 1.1.1.3.3.5
RINF index: 1.2.1.1.2.5
SHACL shape validation rule: GsmrNetworkCoverage
SHACL shape validation rule: GsmrNetworkCoverageApplicability
SHACL shape validation rule: GsmrNetworkCoverageSKOS
used in RCC calculations: true
created: 2020-08-31
modified: 2021-09-12
comment: Name of the own GSM-R network and list of GSM-R networks which are covered by a roaming agreement (for CS services).
term status: stable
scope note: 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.

Has abstraction
type: ObjectProperty
domain: Infrastructure element
created: 2020-07-29
modified: 2022-10-27
modified: 2025-02-18
comment: Property that links a physical entity with its topological abstraction representation.
deprecated: true
term status: stable

Has implementation
type: ObjectProperty
range: Infrastructure element
created: 2020-07-29
modified: 2022-10-27
modified: 2025-02-18
comment: Property that links a topological abstraction entity with its physical representation.
deprecated: true
term status: stable

has linear referencing system
type: ObjectProperty
domain: Kilometric Post
range: Linear Positioning System
SHACL shape validation rule: HasLrsCoordinate
created: 2024-11-29
modified: 2025-03-10
comment: Specifies the linear referencing system to which the kilometre post is referenced. The linear referencing system is commonly the main railway line and it provides the framework for identifying the post's location along the railway line, using distance measurements rather than geographical coordinates.

has line referencing system coordinate
type: ObjectProperty
domain: Net Point Reference
range: Linear Positioning System Coordinate
SHACL shape validation rule: HasLrsCoordinate
created: 2024-11-29
comment: Specifies the LRS coordinate associated with a topological coordinate.

has organisation role
type: ObjectProperty
type: FunctionalProperty
domain: Organisation Role
range: Concept
in SKOS Concept Scheme: OrgRoles
SHACL shape validation rule: HasOrganisationRole
SHACL shape validation rule: HasOrganisationRoleSKOS
created: 2024-06-03
comment: Relates the Organisation role instance (the role played by an Organisation) with the specific role in the taxonomy of organisation roles.

has orientation
type: ObjectProperty
domain: Signal
range: Orientation
created: 2024-10-28

has part
type: ObjectProperty
inverse of: is part of
type: IrreflexiveProperty
domain: Infrastructure element
range: Infrastructure element
SHACL shape validation rule: HasPart
SHACL shape validation rule: HasPartOP
SHACL shape validation rule: HasPartSoL
created: 2024-05-24
modified: 2025-01-30
modified: 2025-02-18
modified: 2025-07-24
replaces: Siding
replaces: Track
comment: Indicates that an infrastructure element is composed of one or more other (distinct) infrastructure elements. This property is used to represent part-whole relationships between infrastructure elements. An element cannot be a part of itself.

has sequence
type: ObjectProperty
domain: Net Linear Reference
range: List
SHACL shape validation rule: HasSequence
created: 2024-11-29
comment: The ordered sequence of topological linear elements which create a linear net reference.

has topological coordinate
type: ObjectProperty
domain: Net Point Reference
range: Topological Coordinate
SHACL shape validation rule: HasTopoCoordinate
created: 2024-11-29
comment: Specifies the topological coordinate of a network point reference.

Health, safety and environment
type: ObjectProperty
sub property of: Infrastructure subsystem
RINF index: 1.1.1.1.7
created: 2024-10-31

Direction of measurement of trackside HABD
type: ObjectProperty
sub property of: Health, safety and environment
type: FunctionalProperty
domain: Hot Axle Box Detector
range: Concept
XML name: IHS_HABDDirection
applicable: Y/N
dependency note: Mandatory if the HABD is not TSI compliant (the value of parameter 1.1.1.1.7.5 (Trackside HABD TSI compliant) is 'False')
in SKOS Concept Scheme: HotAxleBoxDetectorDirections
legal deadline: 16 January 2020
RINF index: 1.1.1.1.7.9
SHACL shape validation rule: HotAxleBoxDetectorDirection
SHACL shape validation rule: HotAxleBoxDetectorDirectionApplicability
SHACL shape validation rule: HotAxleBoxDetectorDirectionCountryApplicability
SHACL shape validation rule: HotAxleBoxDetectorDirectionSKOS
used in RCC calculations: true
created: 2022-07-08
modified: 2024-01-08
modified: 2025-02-20
modified: 2025-02-28
comment: Direction of measurement of trackside HABD, specific for the French Italian and Swedish networks.
term status: stable
change note: This property was previously a datatype property with domain Track and range string. As its values are a list of three predefined values, it is now a SKOS.
scope note: 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)

In country
type: ObjectProperty
domain: Class
  union of: Subset with common characteristics
  union of: Infrastructure element
range: Concept
in SKOS Concept Scheme: country
SHACL shape validation rule: InCountry
SHACL shape validation rule: InCountrySKOS
created: 2020-09-01
modified: 2020-11-20
modified: 2025-03-10
comment: Indicates the country in which an entity resides.
term status: stable

In NUTS-3
type: ObjectProperty
type: FunctionalProperty
domain: Primary Location
range: Concept
in SKOS Concept Scheme: nuts
SHACL shape validation rule: InNUTS3
SHACL shape validation rule: InNUTS3SKOS
created: 2025-09-21
comment: Reference to NUTS-3 place or city
term status: stable

includes list of linear references
type: ObjectProperty
domain: Net Area Reference
range: List
SHACL shape validation rule: Includes
created: 2024-11-29
comment: List of linear references included in an network area reference.

Infrastructure subsystem
type: ObjectProperty
sub property of: RINF Technical characteristic
RINF index: 1.1.1.1
created: 2024-10-31
modified: 2024-10-28

infrastructure manager
type: ObjectProperty
domain: Class
  union of: Subset with common characteristics
  union of: Infrastructure element
range: Organisation Role
SHACL shape validation rule: InfrastructureManagerSKOSValue
created: 2024-10-24
modified: 2025-03-10
replaces: Infrastructure manager
comment: Relates a subset with common characteristics with its IM, represented by an instance of organisation role that points to the "infrastructure manager" concept in the taxonomy.
term status: stable

Infrastructure manager
type: ObjectProperty
domain: Infrastructure element
range: Infrastructure manager
created: 2022-07-07
is replaced by: infrastructure manager
comment: (deprecated) not in use. Relates any feature implemented in the European railway infrastructure with its infrastructure manager.
deprecated: true
term status: stable

Special instructions to switch over between different radio systems
type: ObjectProperty
sub property of: Transitions between systems
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: ERA Document
applicable: Y/N/NYA
dependency note: Applicable when at least two different radio systems exist.
legal deadline: 12 months after publication of Article 7 Guide
RINF index: 1.1.1.3.8.2.1
RINF index: 1.2.1.1.7.2.1
SHACL shape validation rule: InstructionsSwitchRadioSystems
SHACL shape validation rule: InstructionsSwitchRadioSystemsApplicability
TSI operation appendix D2 index: 3.4.4
created: 2022-10-28
modified: 2023-03-14
modified: 2024-04-18
modified: 2024-11-04
modified: 2025-02-28
source: oj
comment: Name and/or reference of the document specifying the Special instructions to switch over between different radio systems.
term status: stable
scope note: 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.

is part of
type: ObjectProperty
type: IrreflexiveProperty
domain: Infrastructure element
range: Infrastructure element
SHACL shape validation rule: IsPartOf
created: 2024-05-24
modified: 2025-01-30
comment: Indicates that an infrastructure element is a part of another (distinct) infrastructure element. An element cannot be part of itself. This property is the inverse of era:hasPart and represents the partial or whole-part relationship between infrastructure elements.

km post for reference
type: ObjectProperty
domain: Linear Positioning System Coordinate
range: Kilometric Post
SHACL shape validation rule: KmPost
created: 2024-11-29
modified: 2025-03-10
comment: The closest kilometric post on the line, used as a reference by the LRS coordinate.

Other radio systems installed (Radio Legacy Systems)
type: ObjectProperty
sub property of: Radio Legacy Systems
domain: Class
  union of: Subset with common characteristics
  union of: Running track
  union of: Vehicle Type
range: Concept
applicable: Y/N/NYA
ERATV index: 4.13.2.3
in SKOS Concept Scheme: LegacyRadioSystems
legal deadline: 12 months after publication of Article 7 Guide for OP tracks
legal deadline: 16 January 2020
RINF index: 1.1.1.3.6.1
RINF index: 1.2.1.1.5.1
SHACL shape validation rule: LegacyRadioSystem
SHACL shape validation rule: LegacyRadioSystemSKOS
TSI operation appendix D2 index: 3.1.7
used in RCC calculations: true
created: 2020-08-31
modified: 2021-09-12
modified: 2024-04-18
modified: 2024-09-19
source: oj
comment: Indication of radio legacy systems installed.
term status: stable
scope note: 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.

Category of line
type: ObjectProperty
sub property of: Performance parameter
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: Concept
XML name: IPP_LineCat
applicable: Y/N
in SKOS Concept Scheme: LineCategories
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.1.1.1.2.2
RINF index: 1.2.1.0.2.2
SHACL shape validation rule: LineCategory
SHACL shape validation rule: LineCategorySKOS
created: 2021-08-02
modified: 2024-01-08
modified: 2024-09-19
source: http://data.europa.eu/eli/reg/2014/1299/2023-09-28
comment: Classification of a line according to the TSI INF
term status: stable
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.
scope note: 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.

Line layout
type: ObjectProperty
sub property of: Infrastructure subsystem
RINF index: 1.1.1.1.3
RINF index: 1.2.1.0.3
created: 2024-10-31

(deprecated) National line identification
type: ObjectProperty
domain: Class
  union of: (deprecated) Railway location
  union of: Section Of Line
range: (deprecated) National railway line
XML name: SOLLineIdentification
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.1.0.0.0.2
TSI operation appendix D2 index: 2.2.1.1
created: 2020-09-30
is replaced by: national line identification
modified: 2023-03-14
modified: 2024-09-19
modified: 2024-10-28
comment: Unique line identification or unique line number within Member State.
deprecated: true
term status: stable

(deprecated) Railway location of an infrastructure object
type: ObjectProperty
domain: Infrastructure element
range: (deprecated) Railway location
created: 2021-01-29
is replaced by: national line identification
modified: 2023-03-14
modified: 2024-10-24
modified: 2024-11-29
modified: 2025-01-30
modified: 2025-02-18
comment: Indicates a relationship with a national railway line at a specific kilometer point.
deprecated: true
term status: stable

End of tunnel kilometer
type: ObjectProperty
sub property of: Tunnel
type: FunctionalProperty
domain: Tunnel
range: Net Point Reference
XML name: SOLTunnelEnd
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.1.1.1.8.4
SHACL shape validation rule: LineReferenceTunnelEnd
created: 2024-02-05
modified: 2024-09-19
modified: 2024-10-24
modified: 2024-11-29
modified: 2025-02-18
replaces: (deprecated) End of tunnel kilometer
comment: Part of the End of tunnel that indicates the km of the line at the end of a tunnel. The End of tunnel is the Geographical coordinates in decimal degrees and km of the line at the end of a tunnel.
term status: stable
example: Kilometer=`0.270`
scope note: 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

Start of tunnel kilometer
type: ObjectProperty
sub property of: Tunnel
type: FunctionalProperty
domain: Tunnel
range: Net Point Reference
XML name: SOLTunnelStart
applicable: Y
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.1.1.1.8.3
SHACL shape validation rule: LineReferenceTunnelStart
created: 2024-02-05
modified: 2024-09-19
modified: 2024-10-24
modified: 2024-11-29
modified: 2025-02-18
replaces: (deprecated) Start of tunnel kilometer
comment: Part of the Start of tunnel that indicates the km of the line at the beginning of a tunnel. The Start of tunnel is the Geographical coordinates in decimal degrees and km of the line at the beginning of a tunnel.
term status: stable
example: Kilometer=`0.895`
scope note: 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.

Line-side system for degraded situation
type: ObjectProperty
sub property of: Control-command and signalling subsystem
RINF index: 1.1.1.3.10
RINF index: 1.2.1.1.9
created: 2024-10-31

Lineside distance indication
type: ObjectProperty
sub property of: Running track generic information
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: Lineside indications of distance
format note: [NNNN] frequency in meters Appearance - selectable list [L/R] - the side along the track where the lineside indication is positioned (left or right)
RINF index: 1.1.1.0.0.3
SHACL shape validation rule: LinesideDistanceIndicationCCS
SHACL shape validation rule: LinesideDistanceIndicationRT
TSI operation appendix D2 index: 3.1.3
created: 2024-12-12
modified: 2025-01-30
modified: 2025-03-11
comment: Indication of types of appearance of track lineside distance indications.
term status: stable
scope note: 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.

Lineside distance indication appearance
type: ObjectProperty
type: FunctionalProperty
domain: Lineside indications of distance
range: Concept
in SKOS Concept Scheme: LinesideDistanceIndicationAppearance
SHACL shape validation rule: LinesideDistanceIndicationAppearance
SHACL shape validation rule: LinesideDistanceIndicationAppearanceSKOS
created: 2022-10-27
modified: 2023-03-14
modified: 2024-09-19
modified: 2024-09-24
modified: 2025-01-30
source: oj
comment: Indication of types of appearance of track lineside distance indications.
term status: unstable

Lineside distance indication positioning
type: ObjectProperty
type: FunctionalProperty
domain: Lineside indications of distance
range: Concept
format note: A selection between 3 possible selectable values: - Left, or - Right, or - Left and Right
SHACL shape validation rule: LinesideDistanceIndicationPositioning
SHACL shape validation rule: LinesideDistanceIndicationPositioningSKOS
created: 2022-10-27
modified: 2023-03-14
modified: 2024-09-19
modified: 2025-01-30
source: oj
comment: Indication of the side along the track where the lineside indication is positioned (left or right, or both sides).
term status: stable

linked to primary location
type: ObjectProperty
domain: Subsidiary location
range: Primary Location
SHACL shape validation rule: LinkedToPrimaryLocation
created: 2024-10-28
comment: Relates a subsidiary location with a primary location.

Load Capability
type: ObjectProperty
range: Concept
XML name: IPP_LoadCap
in SKOS Concept Scheme: LoadCapabilities
RINF index: 1.1.1.1.2.4
used in RCC calculations: true
created: 2020-08-24
is replaced by: Load capability
is replaced by: Load capability line category
is replaced by: Load capability speed
modified: 2023-01-20
modified: 2024-09-19
comment: A combination of the line category and speed at the weakest point of the track. The reason for deprecation is that the load capability property 1.1.1.1.2.4 was defined incorrectly as a SKOS property. It is composed of two values: (1) line category, and (2) speed. Only line category is a list of predefined values (SKOS), whereas speed is an integer (according to the RINF application guide).
deprecated: true
term status: stable

Load capability line category
type: ObjectProperty
type: FunctionalProperty
domain: Load capability
range: Concept
in SKOS Concept Scheme: LoadCapabilityLineCategories
SHACL shape validation rule: LoadCapabilityLineCategory
SHACL shape validation rule: LoadCapabilityLineCategorySKOS
created: 2023-01-20
modified: 2025-02-18
modified: 2025-03-11
replaces: Load Capability
comment: Part of the load capability of a track that corresponds to the line category of the load model. The load capability is a value selected from the list of load models representing the line category which is amended by value of speed [km/h] permitted for a specific load model. The list of values may also be Route Availability which is amended by value of speed [miles/h] permitted for a specific load model.
term status: stable

Documents regarding the rules or restrictions of a strictly local nature available by the IM
type: ObjectProperty
sub property of: Rules and restrictions
type: FunctionalProperty
domain: Class
  union of: Subset with common characteristics
  union of: Operational Point
  union of: Running track
range: ERA Document
XML name: RUL_LocalRulesOrRestrictionsDocRef
applicable: Y/N
dependency note: Mandatory to provide at least a document if parameter "Existence of rules and restrictions of a strictly local nature" value is boolean "Yes"
legal deadline: 1 January 2021
RINF index: 1.1.1.4.2
RINF index: 1.2.3.2
SHACL shape validation rule: LocalRulesOrRestrictionsDoc
created: 2021-08-09
modified: 2023-01-20
modified: 2024-04-23
modified: 2025-03-11
comment: Electronic document available from the IM stored by the Agency providing additional information.
see also: IOD: Notification of national rules Art 14. 11
term status: stable
change note: Change from datatype property to object property in order to point to the class Document (reference document)
scope note: 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

type of line referencing system
type: ObjectProperty
domain: Linear Positioning System
range: Concept
in SKOS Concept Scheme: ReferenceSystems
SHACL shape validation rule: LrsMethod
SHACL shape validation rule: LrsMethodSKOS
created: 2024-04-18
modified: 2024-11-29
comment: The preferred line referencing system.
editorial note: TODO: provide example

M_NVCONTACT
type: ObjectProperty
sub property of: ETCS National Values
type: FunctionalProperty
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: Concept
applicable: Y/N/NYA
dependency note: A value has to be provided when ETCS is present (a value is provided on 1.1.1.3.2.1).
in SKOS Concept Scheme: ETCSReactionsNVContact
legal deadline: 12 months after publication of Article 7 Guide
RINF index: 1.1.1.3.2.16.9
RINF index: 1.2.1.1.1.16.9
SHACL shape validation rule: MNvcontact
SHACL shape validation rule: MNvcontactApplicability
SHACL shape validation rule: MNvcontactSKOS
TSI operation appendix D3 index: 1.5.9
created: 2022-11-07
modified: 2023-03-14
modified: 2024-04-18
relation: European Train Control System (ETCS) level
source: oj
comment: On-Board system reaction when T_NVCONTACT expires According to the specification referenced in Appendix A-1, index [C]
term status: stable
scope note: See: TSI CCS (Subset-026, chapter 7. 7.5.1.74 M_NVCONTACT)

Use of magnetic brakes
type: ObjectProperty
sub property of: Track resistance to applied loads
type: FunctionalProperty
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: Concept
applicable: Y/N/NYA
in SKOS Concept Scheme: MagneticBraking
legal deadline: 12 months after publication of Article 7 Guide for OP tracks
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.1.1.1.6.3
RINF index: 1.2.1.0.4.3
SHACL shape validation rule: MagneticBraking
SHACL shape validation rule: MagneticBrakingSKOS
TSI operation appendix D2 index: 3.4.6
used in RCC calculations: true
created: 2020-08-24
modified: 2022-09-12
modified: 2024-09-19
modified: 2025-02-28
modified: 2025-03-04
source: http://data.europa.eu/eli/reg/2014/1299/2023-09-28
source: oj
comment: Indication of limitations on the use of magnetic brakes.
see also: INF TSI: 4.2.6.2.2 OPE TSI: 4.2.2.6.2 (1) (iv)
term status: stable
change note: This property has been modified to be a RINF parameter (its eratvIndex is deleted). It is treated as a SKOS by RINF and as a boolean by ERATV. A new ERATV datatype property has been defined, magneticBrakingFitted with boolean values.

Document with the conditions for the use of magnetic brakes
type: ObjectProperty
sub property of: Track resistance to applied loads
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: ERA Document
XML name: ILR_MBDocRef
applicable: Y/N
dependency note: 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'.
legal deadline: 16 January 2020
RINF index: 1.1.1.1.6.5
SHACL shape validation rule: MagneticBrakingConditionsDocument
SHACL shape validation rule: MagneticBrakingConditionsDocumentApplicability
TSI operation appendix D2 index: 3.4.6
used in RCC calculations: true
created: 2020-08-24
modified: 2021-09-11
modified: 2024-04-23
modified: 2024-09-19
source: oj
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.
term status: stable
change note: Change from datatype property to object property in order to point to the class Document (reference document)
scope note: 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.

manufactured by
type: ObjectProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: Organisation Role
created: 2020-07-29
modified: 2020-11-19
modified: 2024-06-03
modified: 2024-10-24
modified: 2025-02-18
replaces: (deprecated) Manufacturer
comment: Vehicle manufacturer company.
term status: stable

Manufacturing country
type: ObjectProperty
sub property of: Vehicle technical characteristic
sub property of: Vehicle type technical characteristic
domain: Class
  union of: Vehicle
  union of: Vehicle Type
range: Concept
in SKOS Concept Scheme: country
created: 2020-09-30
modified: 2020-11-22
comment: Indicates the country in which a vehicle or vehicle type is manufactured.
term status: stable

Maximum amount of sand
type: ObjectProperty
domain: Train Detection System
range: Concept
XML name: CTD_MaxSandOutput
in SKOS Concept Scheme: MaxAmountSandings
RINF index: 1.1.1.3.7.17
created: 2021-08-08
modified: 2023-03-14
comment: Maximum amount of sand accepted on the track within value of sanding output for 30s, given in grams. Deprecated according to the amendment to the Regulation (EU) 2019/777.
deprecated: true
term status: stable

Minimum axle load vehicle category
type: ObjectProperty
domain: (deprecated) Min axle load vehicle category
range: Concept
XML name: CTD_MinAxleLoadByVehicleCat
in SKOS Concept Scheme: MinAxleLoadVehicleCategories
RINF index: 1.1.1.3.7.11.1
created: 2021-08-08
modified: 2023-03-14
comment: Represents the category of vehicle which is amended by value of minimum permitted axle load [tons] (property minAxleLoad). Deprecated according to the amendment to the Regulation (EU) 2019/777.
deprecated: true
term status: stable

Vehicle impedance
type: ObjectProperty
sub property of: Train detection systems defined based on frequency bands
type: FunctionalProperty
domain: Train Detection System
range: Minimum Vehicle Impedance
applicable: Y/N/NYA
dependency note: Mandatory only for track circuits
format note: The values is an instance of era:MinVehicleImpedance class with its 2 properties. Per voltage : input Capacitance (Cin) and Input Impedance (Zin)
legal deadline: 12 months after publication of Article 7 Guide for OP tracks
legal 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
RINF index: 1.1.1.3.4.2.2
RINF index: 1.2.1.1.3.2.2
SHACL shape validation rule: MinVehicleImpedance
SHACL shape validation rule: MinVehicleImpedanceApplicability
used in RCC calculations: true
modified: 2025-02-28
comment: Impedance as defined in the specification referenced in Appendix A-1, index [D]
scope note: 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.

minimum Vehicle Impedance (Voltage applicable)
type: ObjectProperty
type: FunctionalProperty
domain: Minimum Vehicle Impedance
range: Concept
in SKOS Concept Scheme: EnergySupplySystems
SHACL shape validation rule: MinVehicleImpedanceVoltages
SHACL shape validation rule: MinVehicleImpedanceVoltagesApplicability
SHACL shape validation rule: MinVehicleImpedanceVoltagesSKOS
created: 2024-05-30
modified: 2024-09-19
relation: Type of train detection system
term status: stable

Minimum radius of vertical curve
type: ObjectProperty
sub property of: Siding
domain: Class
  union of: Subset with common characteristics
  union of: Siding
range: Minimum radius of vertical curve
XML name: ILL_MinRadVertCurve
applicable: Y/N
format note: 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
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.2.2.0.3.3
SHACL shape validation rule: MinimumVerticalRadius
Unit of measure: http://qudt.org/vocab/unit/M
used in RCC calculations: true
created: 2020-08-24
modified: 2023-04-05
modified: 2024-09-19
modified: 2024-12-12
modified: 2025-03-11
source: http://data.europa.eu/eli/reg/2014/1299/2019-06-16
comment: Radius of the smallest vertical curve expressed in metres.
see also: INF TSI: 4.2.3.54
term status: stable
scope note: 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.

national line identification
type: ObjectProperty
sub property of: Section of line generic information
domain: Section Of Line
range: Linear Positioning System
XML name: SOLLineIdentification
RINF index: 1.1.0.0.0.2
SHACL shape validation rule: NationalLineSoL
created: 2024-05-24
modified: 2024-10-24
modified: 2024-11-18
modified: 2024-11-29
modified: 2025-02-18
modified: 2025-03-11
replaces: (deprecated) National line identification
replaces: (deprecated) Railway location of an infrastructure object
comment: Indicates a relationship with a national railway line at a specific kilometer point. For a Section of Line: unique line identification or unique line number within Member State.
term status: stable
scope note: 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.

Navigability
type: ObjectProperty
domain: Net Relation
range: Concept
in SKOS Concept Scheme: Navigabilities
RINF index: 1.1.1.0.1.2
RINF index: 1.2.4.1
SHACL shape validation rule: Navigability
SHACL shape validation rule: NavigabilitySKOS
created: 2021-04-01
modified: 2021-08-03
modified: 2024-11-29
comment: Indicates the navigation possibilities between two related topological linear elements.
term status: stable
alternative label: Internal connection
scope note: • 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 element
type: ObjectProperty
created: 2021-04-01
modified: 2022-09-06
comment: References an associated topological object. The reason for deprecating this property is that it is defined as "References an associated topological object." and the vocabulary has already a property "hasAbstraction" which relates the implementation layer with the topological layer, https://citnet.tech.ec.europa.eu/CITnet/confluence/pages/viewpage.action?pageId=1122974879.
deprecated: true
term status: stable

net reference
type: ObjectProperty
domain: Class
  union of: Infrastructure element
  union of: Linear Positioning System
range: Net Basic Reference
SHACL shape validation rule: NetReference
SHACL shape validation rule: NetReferenceOP
SHACL shape validation rule: NetReferenceSOL
created: 2024-11-29
modified: 2025-03-10
comment: The reference that a physical infrastructure element has it on the topology. It may be used to define the positioning or a representation as a point, line or area

Not applicable
type: ObjectProperty
SHACL shape validation rule: NotApplicable
SHACL shape validation rule: NotApplicableShape
created: 2021-09-13
modified: 2021-09-13
modified: 2025-03-10
comment: Reference to a property that is not applicable.
term status: stable

Not provided
type: ObjectProperty
SHACL shape validation rule: NotYetAvailable
SHACL shape validation rule: NotYetAvailableShape
created: 2021-09-13
modified: 2023-10-11
modified: 2025-03-10
comment: Reference to a property that is not provided.
term status: stable

OCL separation sections
type: ObjectProperty
sub property of: Energy subsystem
RINF index: 1.1.1.2.4
created: 2024-10-31

of parameter
type: ObjectProperty
domain: Parameter applicability
SHACL shape validation rule: OfParameter
created: 2024-10-28
modified: 2024-12-10
comment: Indicates the parameter (object or datatype property) for which an applicability is being defined.

on element
type: ObjectProperty
domain: Linear Element Section
range: Linear Element
SHACL shape validation rule: OnElement
created: 2024-11-29
comment: Specifies the linear element a section belongs to.

on linear element
type: ObjectProperty
domain: Topological Coordinate
range: Linear Element
SHACL shape validation rule: OnLinearElement
created: 2024-11-29
comment: Specifies the linear element a coordinate is associated with.

Operational point at end of section of line
type: ObjectProperty
sub property of: Section of line generic information
type: FunctionalProperty
domain: Section Of Line
range: Operational Point
XML name: SOLOPEnd
applicable: Y
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.1.0.0.0.4
SHACL shape validation rule: OpEnd
SHACL shape validation rule: OpEndExists
TSI operation appendix D2 index: 3.1.2
created: 2021-09-09
modified: 2024-01-08
modified: 2024-09-19
modified: 2025-03-11
source: oj
comment: Operational point at the end of section of line (kilometres increasing from start OP to the end OP).
term status: stable
scope note: 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.

Operational point generic information
type: ObjectProperty
sub property of: RINF Technical characteristic
RINF index: 1.2.0.0.0
created: 2025-03-11

Border point information per country
type: ObjectProperty
domain: Operational Point
range: Operational Point
created: 2023-01-20
is replaced by: Reference border point
is replaced by: reference border point
modified: 2024-10-24
comment: Relates an operational point that represents the general information of a border point to the information that each country maintains for the border point.
deprecated: true
term status: stable

Operational point at start of section of line
type: ObjectProperty
sub property of: Section of line generic information
type: FunctionalProperty
domain: Section Of Line
range: Operational Point
XML name: SOLOPStart
applicable: Y
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.1.0.0.0.3
SHACL shape validation rule: OpStart
SHACL shape validation rule: OpStartExists
TSI operation appendix D2 index: 3.1.1
created: 2021-09-09
modified: 2024-01-08
modified: 2024-09-19
modified: 2025-03-11
source: oj
comment: Operational point at the start of section of line (kilometres increasing from start OP to the end OP).
term status: stable
scope note: 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.

Type of operational point
type: ObjectProperty
sub property of: Operational point generic information
domain: Operational Point
range: Concept
XML name: OPType
applicable: Y
in SKOS Concept Scheme: OperationalPointTypes
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.2.0.0.0.4
SHACL shape validation rule: OpTypeP
SHACL shape validation rule: OpTypeSKOS
TSI operation appendix D2 index: 2.2.2
TSI operation appendix D2 index: 2.3.2
created: 2020-07-29
modified: 2021-08-03
modified: 2024-09-19
modified: 2025-03-11
source: oj
comment: Type of facility in relation to the dominating operational functions.
term status: stable
scope note: 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.

Operating language
type: ObjectProperty
sub property of: Route book specific parameters
domain: Infrastructure element
range: Concept
applicable: Y/NYA
format note: http://publications.europa.eu/resource/authority/language
in SKOS Concept Scheme: language
legal deadline: 12 months after publication of Article 7 Guide
RINF index: 1.1.0.0.1.2
RINF index: 1.2.0.0.0.8
TSI operation appendix D2 index: 3.5.1
created: 2022-10-28
modified: 2023-03-14
modified: 2024-09-19
source: oj
comment: The language or languages used in daily operation by infrastructure manager and published in its Network Statement, for the communication of operational or safety related messages between the staff of the infrastructure manager and the railway undertaking.
term status: unstable

Operational regime
type: ObjectProperty
sub property of: Route book specific parameters
domain: Section Of Line
range: Concept
applicable: Y/NYA
in SKOS Concept Scheme: OperationalRegimeTypes
legal deadline: 12 months after publication of Article 7 Guide
RINF index: 1.1.0.0.1.3
SHACL shape validation rule: OperationalRegimeType
SHACL shape validation rule: OperationalRegimeTypeSKOS
TSI operation appendix D2 index: 3.2.7
created: 2022-10-27
modified: 2024-01-08
modified: 2024-09-19
modified: 2024-09-24
source: oj
comment: Double track type.
term status: unstable

Operational restriction
type: ObjectProperty
sub property of: Vehicle technical characteristic
domain: Vehicle
range: Concept
in SKOS Concept Scheme: Restrictions
created: 2020-11-23
modified: 2021-08-03
comment: Indicates an operational restriction of vehicle or wagon. Parking brake type (if the vehicle is fitted with it).
term status: stable

orientation
type: ObjectProperty
domain: Orientation
range: Concept
in SKOS Concept Scheme: OrientationDirections
SHACL shape validation rule: Orientation
SHACL shape validation rule: OrientationSKOS
created: 2024-04-18
comment: The orientation of the object in relation to the carrier linear element. Possible values: Normal, Opposite, Both

Open street map class
type: ObjectProperty
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: Concept
in SKOS Concept Scheme: OSMClasses
comment: (deprecated) not in use anymore
deprecated: true
term status: stable
definition: Additional concept class according to OpenStreetMap.

Other Cant Deficiency train categories for which the ETCS trackside is configured to provide SSP
type: ObjectProperty
sub property of: TSI compliant train protection system (ETCS)
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: Concept
applicable: Y/N/NYA
dependency note: A value has to be provided when ETCS is present (a value is provided on 1.1.1.3.2.1).
in SKOS Concept Scheme: CantDeficiencies
legal deadline: 12 months after publication of Article 7 Guide
RINF index: 1.1.1.3.2.14.1
RINF index: 1.2.1.1.1.14.1
SHACL shape validation rule: OtherCantDeficiencyBasicSSP
SHACL shape validation rule: OtherCantDeficiencyBasicSSPApplicability
SHACL shape validation rule: OtherCantDeficiencyBasicSSPSKOS
TSI operation appendix D3 index: 1.3
Unit of measure: MilliM
created: 2023-03-14
modified: 2024-04-18
modified: 2024-09-19
modified: 2025-02-28
relation: Cant Deficiency used for the basic SSP
relation: European Train Control System (ETCS) level
source: oj
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". According to the specification referenced in Appendix A-1, index [C]
term status: unstable
scope note: 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.

Accepted other pantograph heads
type: ObjectProperty
sub property of: Pantograph
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: Concept
XML name: EPA_OtherHeads
applicable: Y/N
dependency note: Mandatory only if “Overhead contact line (OCL)” is selected in 1.1.1.2.2.1.1, otherwise the parameter is not applicable.
in SKOS Concept Scheme: OtherPantographHeads
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.1.1.2.3.2
SHACL shape validation rule: OtherPantographHeadApplicability
SHACL shape validation rule: OtherPantographHeadSKOS
used in RCC calculations: true
created: 2022-06-03
modified: 2022-06-03
modified: 2024-09-25
modified: 2025-02-28
relation: Type of contact line system
source: http://data.europa.eu/eli/reg/2014/1302/2023-09-28
comment: Indication of pantograph heads which are allowed to be used.
see also: EN 50367:2020+A1:2022: Annex B3 LOC&PAS TSI: 7.3.2.14 (specific cases)
term status: stable
scope note: 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.

Radio Legacy Systems
type: ObjectProperty
sub property of: Control-command and signalling subsystem
sub property of: Vehicle type technical characteristic
RINF index: 1.1.1.3.6
RINF index: 1.2.1.1.5
created: 2024-10-31

Other train detection systems
type: ObjectProperty
sub property of: Control-command and signalling subsystem
RINF index: 1.1.1.3.7
RINF index: 1.2.1.1.6
created: 2024-10-31

Other train protection, control and warning systems for degraded situation
type: ObjectProperty
sub property of: Line-side system for degraded situation
type: FunctionalProperty
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: Concept
applicable: Y/N/NYA
dependency note: Only applicable when for parameter 1.1.1.3.10.1 "none" was selected.
in SKOS Concept Scheme: OtherProtectionControlWarnings
legal deadline: 12 months after publication of Article 7 Guide for OP tracks
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.1.1.3.10.2
RINF index: 1.2.1.1.9.2
SHACL shape validation rule: OtherTrainProtection
SHACL shape validation rule: OtherTrainProtectionApplicability
SHACL shape validation rule: OtherTrainProtectionSKOS
TSI operation appendix D2 index: 3.4.1
created: 2021-08-09
modified: 2021-09-12
modified: 2024-04-18
modified: 2024-09-19
modified: 2025-03-04
relation: European Train Control System (ETCS) level
source: http://data.europa.eu/eli/reg_impl/2019/773/2023-09-28
source: oj
comment: Indication of existence of other system than ETCS for degraded situation.
term status: stable
scope note: 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.

Pantograph
type: ObjectProperty
sub property of: Energy subsystem
RINF index: 1.1.1.2.3
created: 2024-10-31

parameter applicability
type: ObjectProperty
domain: Class
  union of: Subset with common characteristics
  union of: Infrastructure element
range: Parameter applicability
SHACL shape validation rule: ParameterApplicability
created: 2024-05-24
modified: 2024-10-28
comment: Relates an infrastructure element or a common characteristics subset with the applicability of a certain parameter.

parameter value type
type: ObjectProperty
domain: Parameter applicability
range: Concept
in SKOS Concept Scheme: ValueTypes
SHACL shape validation rule: ParameterValueType
SHACL shape validation rule: ParameterValueTypeSKOS
created: 2024-11-29
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”.

Parking brake type
type: ObjectProperty
domain: Vehicle Type
range: Concept
ERATV index: 4.7.3.2
in SKOS Concept Scheme: BrakeParkingType
created: 2021-08-26
modified: 2021-08-26
comment: Parking brake type (if the vehicle is fitted with it).
deprecated: true

Passes through tunnel
type: ObjectProperty
domain: Running track
range: Tunnel
created: 2020-07-29
is replaced by: has part
modified: 2022-10-27
modified: 2024-10-24
modified: 2025-02-18
modified: 2025-10-08
comment: References a tunnel that a track goes through.
deprecated: true

Performance parameter
type: ObjectProperty
sub property of: Infrastructure subsystem
RINF index: 1.1.1.1.2
RINF index: 1.2.1.0.2
RINF index: 1.2.2.0.2
created: 2024-10-31

Platform edge
type: ObjectProperty
domain: Running track
range: Platform edge
created: 2021-08-09
is replaced by: has part
modified: 2023-11-10
modified: 2024-10-24
modified: 2025-02-18
modified: 2025-10-08
comment: Reference to a related platform edge.
deprecated: true
term status: stable

Height of platform
type: ObjectProperty
sub property of: Platform
type: FunctionalProperty
domain: Class
  union of: Subset with common characteristics
  union of: Platform edge
range: Concept
XML name: IPL_Height
applicable: Y/
in SKOS Concept Scheme: PlatformHeights
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.2.1.0.6.5
SHACL shape validation rule: PlatformHeightP
SHACL shape validation rule: PlatformHeightSKOS
TSI operation appendix D2 index: 2.3.7
used in RCC calculations: true
created: 2021-08-02
modified: 2021-08-02
modified: 2024-09-19
modified: 2025-03-11
source: http://data.europa.eu/eli/reg/2014/1299/2023-09-28
source: oj
comment: Distance between the upper surface of platform and running surface of the neighbouring track. It is the nominal value expressed in millimetres.
see also: INF TSI: 4.2.9.2 PRM TSI: 4.2.2.11 OPE TSI: 2.3.7 of Appendix D2
term status: stable
scope note: Values included in the list are taken from PRM and INF TSIs including Specific Cases. They are the values which are mandatory for the design of the platform at the respective part of the network. They are not real values measured at real platforms. Platform dimensions are always related to one neighbouring track at a time. So, if two tracks are along a platform, this platform should be divided into two or more ‘RINF platforms’ to have precise description of each.

Platform
type: ObjectProperty
sub property of: RINF Technical characteristic
RINF index: 1.2.1.0.6
created: 2025-03-11

Position on A
type: ObjectProperty
range: Concept
in SKOS Concept Scheme: RelationPositions
RINF index: 1.1.1.0.1.2
RINF index: 1.2.4.1
created: 2021-04-03
modified: 2021-08-03
comment: Determines the position of the topological object A in a relation.
deprecated: true
term status: stable
alternative label: Internal connection

Position on B
type: ObjectProperty
range: Concept
in SKOS Concept Scheme: RelationPositions
RINF index: 1.1.1.0.1.2
RINF index: 1.2.4.1
created: 2021-04-03
modified: 2021-08-03
comment: Determines the position of the topological object B in a relation.
deprecated: true
term status: stable
alternative label: Internal connection

Previous vehicle type
type: ObjectProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: Vehicle Type
created: 2022-06-15
modified: 2022-06-15
comment: Denotes a the previous VehicleType.
term status: stable

primary location
type: ObjectProperty
sub property of: Operational point generic information
domain: Infrastructure element
range: Primary Location
XML name: OPTafTapCode
applicable: Y/N
dependency note: Applicable only in case when a primary location exists
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.2.0.0.0.3
SHACL shape validation rule: PrimaryLocation
TSI operation appendix D2 index: 2.2.2
modified: 2024-12-03
modified: 2025-01-30
replaces: OP primary location code
comment: Primary location code developed for information exchange in accordance with the TSIs relating to the telematics applications subsystem.

Standard combined transport profile number for semi-trailers
type: ObjectProperty
sub property of: Line layout
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: Concept
XML name: ILL_ProfileNumSemiTrailers
applicable: Y/N
in SKOS Concept Scheme: ProfileNumbersSemiTrailers
legal deadline: by 16 March 2019 at the latest for lines belonging to the TEN (1.1.1.1.2.1)
RINF index: 1.1.1.1.3.5
SHACL shape validation rule: ProfileNumberSemiTrailersSKOS
used in RCC calculations: true
created: 2021-08-03
modified: 2023-03-14
comment: Coding for combined transport for semi-trailers (for all freight and mixed-traffic lines) in accordance with the specification referenced in Appendix A-1, index [B].
term status: stable
scope note: 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.

Standard combined transport profile number for swap bodies
type: ObjectProperty
sub property of: Line layout
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: Concept
XML name: ILL_ProfileNumSwapBodies
applicable: Y/N
in SKOS Concept Scheme: ProfileNumbersSwapBodies
legal deadline: by 16 March 2019 at the latest for lines belonging to the TEN (1.1.1.1.2.1)
RINF index: 1.1.1.1.3.4
SHACL shape validation rule: ProfileNumberSwapBodiesSKOS
used in RCC calculations: true
created: 2021-08-03
modified: 2023-03-14
comment: Coding for combined transport with swap bodies (for all freight and mixed-traffic lines) in accordance with the specification referenced in Appendix A-1, index [B]
term status: stable
scope note: 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).

Train protection legacy system
type: ObjectProperty
sub property of: Train protection legacy systems
sub property of: Vehicle type technical characteristic
domain: Class
  union of: Subset with common characteristics
  union of: Running track
  union of: Vehicle Type
range: Concept
applicable: Y/N/NYA
ERATV index: 4.13.1.5
in SKOS Concept Scheme: OtherProtectionControlWarnings
legal deadline: 12 months after publication of Article 7 Guide for OP tracks
legal deadline: 16 January 2020
RINF index: 1.1.1.3.5.3
RINF index: 1.2.1.1.4.1
SHACL shape validation rule: ProtectionLegacySystemSKOS
used in RCC calculations: true
created: 2020-08-31
modified: 2021-09-12
modified: 2024-04-18
modified: 2024-09-19
source: oj
comment: Indication of which class B system is installed.
term status: stable
scope note: 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.

Q_NVDRIVER_ADHES
type: ObjectProperty
sub property of: ETCS National Values
type: FunctionalProperty
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: Concept
applicable: Y/N/NYA
dependency note: A value has to be provided when ETCS is present (a value is provided on 1.1.1.3.2.1).
in SKOS Concept Scheme: AdhesionFactorChange
legal deadline: 12 months after publication of Article 7 Guide
RINF index: 1.1.1.3.2.16.11
RINF index: 1.2.1.1.1.16.11
SHACL shape validation rule: QNvdriverAdhes
SHACL shape validation rule: QNvdriverAdhesApplicability
SHACL shape validation rule: QNvdriverAdhesSKOS
TSI operation appendix D3 index: 1.5.11
created: 2024-04-18
modified: 2024-09-20
relation: European Train Control System (ETCS) level
source: oj
comment: Qualifier determining whether the driver is allowed to modify the adhesion factor used by the ETCS on-board to calculate the braking curves. According to the specification referenced in Appendix A-1, index [C]
term status: stable
scope note: See: TSI CCS (Subset 26, chapter 7. 7.5.1.122 Q_NVDRIVER_ADHES)

Q_NVEMRRLS
type: ObjectProperty
sub property of: ETCS National Values
type: FunctionalProperty
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: Concept
applicable: Y/N/NYA
dependency note: A value has to be provided when ETCS is present (a value is provided on 1.1.1.3.2.1).
in SKOS Concept Scheme: EBReleaseQualifier
legal deadline: 12 months after publication of Article 7 Guide
RINF index: 1.1.1.3.2.16.2
RINF index: 1.2.1.1.1.16.2
SHACL shape validation rule: QNvemrrls
SHACL shape validation rule: QNvemrrlsApplicability
SHACL shape validation rule: QNvemrrlsSKOS
TSI operation appendix D3 index: 1.5.2
created: 2023-03-14
modified: 2024-04-18
relation: European Train Control System (ETCS) level
source: oj
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. According to the specification referenced in Appendix A-1, index [C]
term status: stable
scope note: According to the specification referenced in Appendix A-1, index [C] - TSI CCS (Subset-026, chapter 7, 7.5.1.123 Q_NVEMRRLS)

Quieter route exempted country
type: ObjectProperty
sub property of: Vehicle technical characteristic
domain: Vehicle
range: Concept
in SKOS Concept Scheme: country
created: 2020-11-23
modified: 2020-11-23
comment: Country where a vehicle may operate without noise restrictions.
term status: stable

Rail inclination
type: ObjectProperty
sub property of: Track parameters
sub property of: Vehicle type technical characteristic
type: FunctionalProperty
domain: Class
  union of: Subset with common characteristics
  union of: Running track
  union of: Vehicle Type
range: Concept
XML name: ITP_RailInclination
applicable: Y
ERATV index: 4.6.5
format note: In XML the accepted value is NN, where N is a digit from 0 to 9.
in SKOS Concept Scheme: RailInclinations
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.1.1.1.4.3
SHACL shape validation rule: RailInclination
SHACL shape validation rule: RailInclinationSKOS
used in RCC calculations: true
created: 2020-08-24
modified: 2022-10-20
modified: 2024-09-19
modified: 2025-02-28
source: http://data.europa.eu/eli/reg/2014/1299/2023-09-28
comment: An angle defining the inclination of the head of a rail relative to the running surface.
see also: INF TSI:4.2.4.7
term status: stable
scope note: 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.

Reasons for which an ETCS Radio Block Center can reject a train
type: ObjectProperty
sub property of: TSI compliant train protection system (ETCS)
type: FunctionalProperty
domain: Radio Block Center
range: Concept
applicable: Y/N/NYA
dependency note: A value has to be provided when ETCS is present (a value is provided on 1.1.1.3.2.1).
in SKOS Concept Scheme: ETCSRBCRejectionReasons
legal deadline: 12 months after publication of Article 7 Guide
RINF index: 1.1.1.3.2.15
RINF index: 1.2.1.1.1.15
SHACL shape validation rule: ReasonsEtcsRadioBlockCenterReject
SHACL shape validation rule: ReasonsEtcsRadioBlockCenterRejectSKOS
TSI operation appendix D3 index: 1.4
created: 2022-11-07
modified: 2023-03-14
modified: 2024-04-18
modified: 2024-09-19
relation: European Train Control System (ETCS) level
source: oj
comment: List of cases subject to system design choices made by the infrastructure manager according to the specification referenced in Appendix A-1, index [C]
term status: stable
scope note: 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.

reference border point
type: ObjectProperty
domain: Operational Point
range: Reference border point
SHACL shape validation rule: ReferenceBorderPoint
created: 2024-10-24
modified: 2025-02-18
modified: 2025-02-24
replaces: border point of
replaces: Border point information per country
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.

Requirements for rolling stock
type: ObjectProperty
sub property of: Energy subsystem
RINF index: 1.1.1.2.5
created: 2024-10-31

RINF Technical characteristic
type: ObjectProperty
created: 2024-10-28
modified: 2025-02-25

role
type: ObjectProperty
inverse of: role of
domain: Body
range: Organisation Role
SHACL shape validation rule: Role
created: 2024-06-03
modified: 2024-10-24
comment: Indicates the relationship of a Body to the organisation roles that it can play.

role of
type: ObjectProperty
type: FunctionalProperty
domain: Organisation Role
range: Body
SHACL shape validation rule: RoleOf
created: 2024-10-24
comment: Indicates the corresponding Body that plays a certain organisation role.

Fire category of rolling stock required
type: ObjectProperty
sub property of: Tunnel
type: FunctionalProperty
domain: Class
  union of: Subset with common characteristics
  union of: Tunnel
range: Concept
XML name: ITU_FireCatReq
applicable: Y/N
dependency note: Mandatory for tunnels longer than 1 km
in SKOS Concept Scheme: Categories
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.1.1.1.8.10
RINF index: 1.2.1.0.5.7
RINF index: 1.2.2.0.5.7
SHACL shape validation rule: RollingStockFireCategory
SHACL shape validation rule: RollingStockFireCategoryApplicability
SHACL shape validation rule: RollingStockFireCategorySKOS
TSI operation appendix D2 index: 3.2.3
used in RCC calculations: true
created: 2020-07-29
modified: 2024-01-08
modified: 2024-09-19
source: http://data.europa.eu/eli/reg/2014/1302/2023-09-28
source: http://data.europa.eu/eli/reg/2014/1303/2024-01-29
source: oj
comment: Categorisation how a passenger train with a fire on board will continue to operate for a defined time period
comment: Passenger train fire category in accordance with point 4.1.4 of TSI LOC&PAS.
see also: SRT TSI: 4.2.3.3.4 LOC&PAS TSI : 4.2.10.4.4
term status: stable
scope note: 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.

Route book specific parameters
type: ObjectProperty
sub property of: RINF Technical characteristic
RINF index: 1.1.0.0.1
created: 2025-01-30

Rules and restrictions
type: ObjectProperty
sub property of: RINF Technical characteristic
RINF index: 1.1.1.4
RINF index: 1.2.3
created: 2025-03-11

Safe consist length information from on-board necessary for access the line and SIL
type: ObjectProperty
sub property of: TSI compliant train protection system (ETCS)
type: FunctionalProperty
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: Concept
applicable: Y/N/NYA
dependency note: A value has to be provided when ETCS is present and the level of ETCS is 2 (parameter 1.1.1.3.2.1).
in SKOS Concept Scheme: SafeConsistLengthNecessary
legal deadline: 12 months after publication of Article 7 Guide
RINF index: 1.1.1.3.2.11
RINF index: 1.2.1.1.1.11
SHACL shape validation rule: SafeConsistLengthInformationNecessary
SHACL shape validation rule: SafeConsistLengthInformationNecessaryApplicability
SHACL shape validation rule: SafeConsistLengthInformationNecessarySKOS
used in RCC calculations: true
created: 2023-03-14
modified: 2024-04-18
modified: 2024-09-19
modified: 2025-02-28
relation: European Train Control System (ETCS) level
source: oj
comment: Indication whether safe consist train length information from on-board is required to access the line for safety reasons and the required safety integrity level.
term status: stable
scope note: See: TSI CCS (Subset-026, Chapter 7, 7.5.1.112.1 and P10)

on side
type: ObjectProperty
domain: Orientation
range: Concept
in SKOS Concept Scheme: Sides
SHACL shape validation rule: Side
SHACL shape validation rule: SideSKOS
created: 2024-04-18
modified: 2025-03-10
comment: Indication of the position of the signal in relation to the track in the running direction from the origin of the referencing system (e.g., direction of the main line)

Siding
type: ObjectProperty
domain: Operational Point
range: Siding
created: 2021-08-10
is replaced by: has part
modified: 2021-08-10
modified: 2024-11-11
comment: Reference to a related siding.
deprecated: true
term status: stable

Siding
type: ObjectProperty
sub property of: RINF Technical characteristic
RINF index: 1.2.2
created: 2025-03-11

Signal
type: ObjectProperty
sub property of: Control-command and signalling subsystem
RINF index: 1.1.1.3.14
created: 2024-10-31

Signal orientation
type: ObjectProperty
sub property of: Signal
type: FunctionalProperty
domain: Class
  union of: Subset with common characteristics
  union of: Signal
range: Concept
applicable: Y/N/NYA
in SKOS Concept Scheme: OrientationDirections
legal deadline: 12 months after publication of Article 7 Guide
RINF index: 1.1.1.3.14.3
RINF index: 1.2.1.0.8.3
SHACL shape validation rule: SignalOrientation
SHACL shape validation rule: SignalOrientationSKOS
TSI operation appendix D2 index: 2.2.3
TSI operation appendix D2 index: 2.3.3
created: 2023-03-14
modified: 2024-04-18
relation: Name of signal
source: oj
comment: Relative position to the line of reference, given in km and indication if the signal refers to normal or opposite track direction
term status: unstable
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 .
scope note: 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.

Type of signal
type: ObjectProperty
sub property of: Signal
domain: Class
  union of: Subset with common characteristics
  union of: Signal
range: Concept
applicable: Y/N/NYA
in SKOS Concept Scheme: SignalTypes
legal deadline: 12 months after publication of Article 7 Guide
RINF index: 1.1.1.3.14.2
RINF index: 1.2.1.0.8.2
SHACL shape validation rule: SignalType
SHACL shape validation rule: SignalTypeSKOS
TSI operation appendix D2 index: 2.2.3
TSI operation appendix D2 index: 2.3.3
created: 2022-10-27
modified: 2024-01-08
modified: 2024-04-18
modified: 2024-09-19
relation: Name of signal
source: oj
comment: Signalling information for Route Book compilation. This list shall include fixed signals that protect danger points
term status: unstable
scope note: Indicates what function the signal (on the track or in OP) executes in relation to the track/switches.

Snow ice hail conditions
type: ObjectProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: Concept
ERATV index: 4.3.3
in SKOS Concept Scheme: IceConditions
created: 2020-08-24
modified: 2021-08-02
comment: Snow, ice and hail conditions.
term status: stable

Section of line generic information
type: ObjectProperty
sub property of: RINF Technical characteristic
RINF index: 1.1.0.0.0
created: 2025-03-11

Nature of Section of Line
type: ObjectProperty
sub property of: Section of line generic information
type: FunctionalProperty
domain: Section Of Line
range: Concept
XML name: SOLNature
applicable: Y
in SKOS Concept Scheme: SoLNatures
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.1.0.0.0.6
SHACL shape validation rule: SolNature
SHACL shape validation rule: SolNatureApplicability
SHACL shape validation rule: SolNatureSKOS
created: 2021-08-08
modified: 2023-03-14
modified: 2025-03-11
comment: Kind of section of line expressing size of presented data which depends on fact whether it connects OPs generated by division of a big node into several OPs or not.
term status: stable

Special area type
type: ObjectProperty
domain: Special area
range: Concept
in SKOS Concept Scheme: SpecialAreaTypes
RINF index: 1.1.0.0.1.1
TSI operation appendix D2 index: 3.2.3
TSI operation appendix D2 index: 3.2.4
TSI operation appendix D2 index: 3.2.5
TSI operation appendix D2 index: 3.2.6
TSI operation appendix D2 index: 3.3.5
TSI operation appendix D2 index: 3.3.6
created: 2022-10-27
modified: 2023-03-14
modified: 2024-04-18
comment: Indicates the special area or location types such as safe areas and restricted area types.
term status: unstable

Special tunnel area
type: ObjectProperty
domain: Tunnel
range: Special tunnel area
TSI operation appendix D2 index: 3.2.3
created: 2022-10-27
modified: 2024-09-19
source: oj
comment: Relates a tunnel with a special area or location.
term status: stable

Standard combined transport profile number for containers
type: ObjectProperty
sub property of: Line layout
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: Concept
applicable: Y/N/NYA
in SKOS Concept Scheme: StandardCombinedTransportContainers
legal deadline: 12 months after the adoption of the Article 7 Guide for lines belonging to the TEN (1.1.1.1.2.1)
RINF index: 1.1.1.1.3.8
SHACL shape validation rule: StandardCombinedTransportContainers
SHACL shape validation rule: StandardCombinedTransportContainersSKOS
used in RCC calculations: true
created: 2023-03-14
modified: 2025-02-20
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]
term status: stable

Standard combined transport profile number for roller units
type: ObjectProperty
sub property of: Line layout
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: Concept
applicable: Y/N/NYA
in SKOS Concept Scheme: StandardCombinedTransportRollerUnits
legal deadline: 12 months after the adoption of the Article 7 Guide for lines belonging to the TEN (1.1.1.1.2.1)
RINF index: 1.1.1.1.3.9
SHACL shape validation rule: StandardCombinedRollerUnits
SHACL shape validation rule: StandardCombinedRollerUnitsSKOS
used in RCC calculations: true
created: 2023-03-14
modified: 2025-02-20
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]
term status: stable

Start of tunnel location
type: ObjectProperty
sub property of: Tunnel
sub property of: hasGeometry
type: FunctionalProperty
domain: Tunnel
range: Point
XML name: SOLTunnelStart
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.1.1.1.8.3
SHACL shape validation rule: StartLocation
created: 2020-07-29
modified: 2024-02-05
comment: Part of the Start of tunnel that indicates the 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. The Start of tunnel is the Geographical coordinates in decimal degrees and km of the line at the beginning of a tunnel.
term status: stable

starts at
type: ObjectProperty
domain: Net Linear Reference
range: Net Point Reference
SHACL shape validation rule: StartsAt
created: 2024-11-29
comment: Specifies the starting point of a linear reference.

State
type: ObjectProperty
domain: Certificate
range: Concept
in SKOS Concept Scheme: States
created: 2022-06-15
modified: 2022-06-15
comment: Denoting the state of the certificate Can be in one of the following: Amended, New, Suspended, Withdrawn.
deprecated: true
term status: stable

subCategory
type: ObjectProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: Concept
ERATV index: 1.5
in SKOS Concept Scheme: Categories
created: 2020-07-29
is replaced by: Vehicle subcategory
modified: 2021-08-03
modified: 2025-02-13
comment: (Deprecated) Vehicle subcategory.
deprecated: true
term status: stable

subset of
type: ObjectProperty
type: IrreflexiveProperty
domain: Subset with common characteristics
range: Subset with common characteristics
SHACL shape validation rule: SubsetOf
created: 2024-10-31
modified: 2025-03-10
comment: Relates a subset with common characteristics with another subset with common characteristics.
scope note: 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 type
type: ObjectProperty
domain: Subsidiary location
range: Concept
in SKOS Concept Scheme: SubsidiaryLocationTypes
SHACL shape validation rule: SubsidiaryLocationType
SHACL shape validation rule: SubsidiaryLocationTypeSKOS
created: 2024-05-24
comment: Indicates the subsidiary location type that belongs to a taxonomy.

Supported platform height
type: ObjectProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: Concept
ERATV index: 4.12.3.1
in SKOS Concept Scheme: PlatformHeights
created: 2020-07-29
modified: 2021-08-02
comment: Platform height for which the vehicle is designed.
term status: stable

Section with train detection limitation
type: ObjectProperty
sub property of: Other train detection systems
type: FunctionalProperty
domain: Train Detection System
range: Section with train detection limitation
applicable: Y/N/NYA
dependency note: Only applicable on running tracks in France
format note: The value of this parameter is an instance of the era:FrenchTrainDetectionSystemLimitation class with all its properties: - true/false for the existence of a section with train detection limitation - list of values from 1 to 8 defined in the taxonomy
legal deadline: 12 months after publication of Article 7 Guide for OP tracks
legal deadline: 16 January 2020
RINF index: 1.1.1.3.7.1.4
RINF index: 1.2.1.1.6.3
SHACL shape validation rule: TdsFrenchTrainDetectionSystemLimitation
used in RCC calculations: true
created: 2023-04-05
modified: 2025-02-18
modified: 2025-03-04
modified: 2025-03-11
relation: Section with train detection limitation
relation: Section with train detection limitation number, only for French network
replaces: Section with train detection limitation, only for the French network
comment: Specific for route compatibility check on French network.
term status: stable
scope note: 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 string 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.

Maximum magnetic field
type: ObjectProperty
sub property of: Train detection systems defined based on frequency bands
type: FunctionalProperty
domain: Train Detection System
range: Maximum magnetic field
applicable: Y/N/NYA
dependency note: Mandatory for train detection systems based on axle counters
legal deadline: 12 months after publication of Article 7 Guide for OP tracks
legal 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
RINF index: 1.1.1.3.4.2.3
RINF index: 1.2.1.1.3.2.3
SHACL shape validation rule: TdsMaximumMagneticField
SHACL shape validation rule: TdsMaximumMagneticFieldApplicability
used in RCC calculations: true
created: 2023-03-14
modified: 2024-04-18
modified: 2024-09-19
modified: 2025-02-28
modified: 2025-03-04
relation: Type of train detection system
source: http://data.europa.eu/eli/reg_impl/2023/1695/2023-09-08
comment: 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.
term status: stable
scope note: 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 detection system min axle load vehicle category
type: ObjectProperty
domain: Train Detection System
range: (deprecated) Min axle load vehicle category
XML name: CTD_MinAxleLoadByVehicleCat
RINF index: 1.1.1.3.7.11.1
created: 2023-01-25
modified: 2023-03-14
comment: Indication of load given in tons depending of the category of vehicle. Deprecated according to the amendment to the Regulation (EU) 2019/777.
deprecated: true
term status: stable

Temperature range
type: ObjectProperty
sub property of: Performance parameter
type: FunctionalProperty
domain: Class
  union of: Subset with common characteristics
  union of: Running track
  union of: Vehicle Type
range: Concept
XML name: IPP_TempRange
applicable: Y/N
ERATV index: 4.3.1
in SKOS Concept Scheme: TemperatureRanges
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.1.1.1.2.6
SHACL shape validation rule: TemperatureRange
SHACL shape validation rule: TemperatureRangeSKOS
used in RCC calculations: true
created: 2023-01-20
modified: 2024-06-26
modified: 2024-09-19
modified: 2025-02-18
replaces: Temperature range (maximum)
replaces: Temperature range (minimum)
comment: Temperature range for unrestricted access to the line.
see also: Loc&Pas TSI: 4.2.6.1.1 4.2.5 Wag TSI
term status: stable
scope note: T1 (-25 to +40) T2 (-40 to +35) T3 (-25 to +45) Tx (-40 to +50)

TEN classification of track
type: ObjectProperty
sub property of: Performance parameter
sub property of: Platform
sub property of: Siding
domain: Class
  union of: Subset with common characteristics
  union of: Platform edge
  union of: Running track
  union of: Siding
range: Concept
XML name: IPL_TENClass
XML name: IPP_TENClass
applicable: Y/N
in SKOS Concept Scheme: TENClassifications
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.1.1.1.2.1
RINF index: 1.2.1.0.2.1
RINF index: 1.2.1.0.6.3
RINF index: 1.2.2.0.0.3
SHACL shape validation rule: TenClassificationP
SHACL shape validation rule: TenClassificationS
SHACL shape validation rule: TenClassificationSKOSP
SHACL shape validation rule: TenClassificationSKOSS
SHACL shape validation rule: TenClassificationSKOST
SHACL shape validation rule: TenClassificationT
created: 2021-08-02
modified: 2024-01-08
modified: 2024-09-19
modified: 2025-03-11
source: http://data.europa.eu/eli/reg/2013/1315/2024-03-18
comment: Indication of the part of the trans-European network the infrastructure element belongs to.
term status: stable
alternative label: Trans-European Network (TEN) classification of track
scope note: 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.

Thermal capacity TSI reference
type: ObjectProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: Concept
ERATV index: 4.7.2.1.1
in SKOS Concept Scheme: ThermalCapacityTSIReferences
created: 2020-08-24
modified: 2021-08-02
comment: Reference case of a TSI thermal capacity.
term status: stable

Track
type: ObjectProperty
domain: Class
  union of: Operational Point
  union of: Section Of Line
  union of: Signal
range: Running track
created: 2021-08-09
is replaced by: has part
modified: 2021-09-09
modified: 2024-11-11
comment: Reference to a related railway track.
deprecated: true
term status: stable

Normal running direction
type: ObjectProperty
sub property of: Running track generic information
type: FunctionalProperty
domain: Running track
range: Concept
XML name: SOLTrackDirection
applicable: Y
in SKOS Concept Scheme: TrackRunningDirections
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.1.1.0.0.2
SHACL shape validation rule: SoLTrackDirectionMaxCount
SHACL shape validation rule: SoLTrackDirectionMinCount
SHACL shape validation rule: TrackDirectionSKOS
TSI operation appendix D2 index: 2.2.1.1
created: 2021-09-09
modified: 2024-01-08
modified: 2025-03-11
comment: The normal running direction 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)
term status: stable

Running track generic information
type: ObjectProperty
sub property of: RINF Technical characteristic
RINF index: 1.1.1.0.0
created: 2025-03-11

Load capability
type: ObjectProperty
sub property of: Performance parameter
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: Load capability
XML name: IPP_LoadCap
applicable: Y
format note: 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.
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.1.1.1.2.4
SHACL shape validation rule: TrackLoadCapability
Unit of measure: KiloM-PER-HR
used in RCC calculations: true
created: 2023-01-20
modified: 2025-02-18
modified: 2025-03-11
replaces: 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.
see also: INF TSI: 4.2.1, 4.2.7.1, 4.2.7.2, 4.2.7.4 Annex D1 OPE TSI
term status: stable
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.
scope note: 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.

Track parameters
type: ObjectProperty
sub property of: Infrastructure subsystem
RINF index: 1.1.1.1.4
RINF index: 1.2.1.0.4
created: 2024-10-31

Information on phase separation
type: ObjectProperty
sub property of: OCL separation sections
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: Phase info
XML name: EOS_InfoPhase
applicable: Y/N
dependency note: 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)
format note: 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 string with the following structure: distance type [MIN/MAX] + length [NNN] + switch off breaker [Y/N] + lower pantograph [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 meters; - 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.
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.1.1.2.4.1.2
SHACL shape validation rule: TrackPhaseInfo
SHACL shape validation rule: TrackPhaseInfoApplicability
created: 2023-04-05
modified: 2025-02-18
modified: 2025-02-28
modified: 2025-06-09
replaces: Information on phase separation
comment: Relates the Track with PhaseInfo. Indication of required several information on phase separation.
see also: ENE TSI: 4.2.15
term status: stable

Requirements for number of raised pantographs and spacing between them, at the given speed
type: ObjectProperty
sub property of: Pantograph
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: Requirements for number of raised pantographs and spacing between them, at the given speed
XML name: EPA_NumRaisedSpeed
applicable: Y/N
dependency note: Mandatory only if “Overhead contact line (OCL)” is selected in 1.1.1.2.2.1.1, otherwise the parameter is not applicable.
format note: Three values: [N] is number of pantographs; [NNN] is minimum distance between pantographs, in metres; [NNN] is the speed considered in km/h.
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.1.1.2.3.3
SHACL shape validation rule: TrackRaisedPantographDistanceAndSpeedApplicability
SHACL shape validation rule: TrackRaisedPantographsDistanceAndSpeed
used in RCC calculations: true
created: 2023-04-05
modified: 2024-09-25
modified: 2025-02-28
relation: Type of contact line system
source: http://data.europa.eu/eli/reg/2014/1301/2023-09-28
source: http://data.europa.eu/eli/reg/2014/1302/2023-09-28
comment: 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 also: ENE TSI: 4.2.13 ; LOC&PAS TSI: 4.2.8.2.9.7
term status: stable
editorial note: Relates the track with the class RaisedPantographsDistanceAndSpeed.
scope note: 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)

Track resistance to applied loads
type: ObjectProperty
sub property of: Infrastructure subsystem
RINF index: 1.1.1.1.6
created: 2024-10-31

Information on system separation
type: ObjectProperty
sub property of: OCL separation sections
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: System separation info
XML name: EOS_InfoSystem
applicable: Y/N
dependency note: Mandatory if there is an indication of existence of system separation (parameter 1.1.1.2.4.2.1)
format note: 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 string with the following structure: length [NNN] + switch off breaker [Y/N] + lower pantograph [Y/N] + km [NNN.NNN]
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.1.1.2.4.2.2
SHACL shape validation rule: TrackSystemSeparationInfo
SHACL shape validation rule: TrackSystemSeparationInfoApplicability
created: 2023-04-05
modified: 2025-02-18
modified: 2025-02-28
modified: 2025-06-09
replaces: (deprecated) Information on system separation
comment: Indication of required several information on system separation
see also: ENE TSI: 4.2.16
term status: stable
scope note: Length - the length of the system separation in meters 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 Km - the location from the start of the line where the new value is valid

hot axle box detector (HABD)
type: ObjectProperty
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: Hot Axle Box Detector
created: 2025-02-20
comment: Link between the running track and the HABD, covering the RINF parameters 1.1.1.1.7.(5-9)

train detection system
type: ObjectProperty
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: Train Detection System
SHACL shape validation rule: TrainDetectionSystem
created: 2020-07-29
modified: 2021-09-12
modified: 2025-02-28
comment: Technical characteristics of the train detection systems installed in the section of line.
term status: stable
scope note: 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.

Train detection systems defined based on frequency bands
type: ObjectProperty
sub property of: Control-command and signalling subsystem
RINF index: 1.1.1.3.4
RINF index: 1.2.1.1.3
created: 2024-10-31

Type of track circuits or axle counters to which specific checks are needed
type: ObjectProperty
sub property of: Other train detection systems
type: FunctionalProperty
domain: Train Detection System
range: Concept
applicable: Y/N/NYA
dependency note: It is applicable only when parameter "Type of train detection system" is applicable
in SKOS Concept Scheme: TrainDetectionSystemsSpecificChecks
legal deadline: 12 months after publication of Article 7 Guide
RINF index: 1.1.1.3.7.1.2
RINF index: 1.2.1.1.6.1
SHACL shape validation rule: TrainDetectionSystemSpecificCheck
SHACL shape validation rule: TrainDetectionSystemSpecificCheckApplicability
SHACL shape validation rule: TrainDetectionSystemSpecificCheckSKOS
used in RCC calculations: true
modified: 2020-08-24
modified: 2021-08-08
modified: 2024-04-18
modified: 2024-09-19
modified: 2024-09-25
modified: 2024-10-31
relation: 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"
relation: Type of train detection system
source: oj
comment: Reference to the technical specification of train detection system, in accordance with the specification referenced in Appendix A-1, index [D]
term status: stable
scope note: 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"
type: ObjectProperty
sub property of: Other train detection systems
type: FunctionalProperty
domain: Train Detection System
range: ERA Document
applicable: Y/N/NYA
dependency note: It is applicable only when parameter "Type of train detection system" is applicable
legal deadline: 12 months after publication of Article 7 Guide for OP tracks
legal deadline: In accordance with TSI CCS Art. 13 and 12 months after publication of Article 7 Guide
RINF index: 1.1.1.3.7.1.3
RINF index: 1.2.1.1.6.2
SHACL shape validation rule: TrainDetectionSystemSpecificCheckDocument
SHACL shape validation rule: TrainDetectionSystemSpecificCheckDocumentApplicability
used in RCC calculations: true
created: 2021-08-03
modified: 2024-01-08
modified: 2024-04-18
modified: 2024-04-23
modified: 2024-09-19
modified: 2025-03-04
relation: Type of train detection system
comment: Electronic document from the IM stored by the Agency with precise values in accordance with TSI CCS Article13 and the specification referenced in Appendix A-1, index [D], for the specific check to be performed for train detection systems identified in parameter "Type of track circuits or axle counters to which specific checks are needed".
term status: stable
change note: Change from datatype property to object property in order to point to the class Document (reference document)
scope note: 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.

Type of train detection system
type: ObjectProperty
sub property of: Other train detection systems
sub property of: Vehicle type technical characteristic
type: FunctionalProperty
domain: Class
  union of: Train Detection System
  union of: Vehicle Type
range: Concept
applicable: Y/N/NYA
dependency note: Not all parameters are applicable to all types of train detection systems; it depends on the applicability condition.
ERATV index: 4.14.1
in SKOS Concept Scheme: TrainDetectionSystems
legal deadline: 12 months after publication of Article 7 Guide for OP tracks
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.1.1.3.7.1.1
RINF index: 1.2.1.1.3.1.1
SHACL shape validation rule: TrainDetectionSystemType
SHACL shape validation rule: TrainDetectionSystemTypeSKOS
used in RCC calculations: true
created: 2021-08-07
modified: 2021-08-07
modified: 2024-04-18
modified: 2025-03-04
comment: Indication of types of train detection systems installed.
term status: stable
scope note: Explanation on data presentation: The option of "wheel detector" has to be also selected for: wheel sensor for axle counter, pedal or treadle.
scope note: 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.

Train protection legacy systems
type: ObjectProperty
sub property of: Control-command and signalling subsystem
RINF index: 1.1.1.3.5
RINF index: 1.2.1.1.4
created: 2024-10-31

Transitions between systems
type: ObjectProperty
sub property of: Control-command and signalling subsystem
RINF index: 1.1.1.3.8
RINF index: 1.2.1.1.7
created: 2024-10-31

TSI compliance of rules on the use of composite brake blocks
type: ObjectProperty
domain: Train Detection System
range: Concept
XML name: CTD_TSICompositeBrakeBlocks
in SKOS Concept Scheme: TSICompliances
RINF index: 1.1.1.3.7.21
created: 2021-08-08
modified: 2023-03-14
comment: Deprecated according to the amendment to the Regulation (EU) 2019/777. TSI compliance of rules on the use of composite brake blocks.
deprecated: true
term status: stable

TSI compliance of Ferromagnetic characteristics of wheel material required
type: ObjectProperty
domain: Train Detection System
range: Concept
XML name: CTD_TSIFerroWheelMat
in SKOS Concept Scheme: TSICompliances
RINF index: 1.1.1.3.7.14
created: 2021-08-08
modified: 2023-03-14
comment: TSI compliance of Ferromagnetic characteristics of wheel material required. Deprecated according to the amendment to the Regulation (EU) 2019/777.
deprecated: true
term status: stable

TSI compliance of maximum permitted distance between two consecutive axles
type: ObjectProperty
domain: Train Detection System
range: Concept
XML name: CTD_TSIMaxDistConsecutiveAxles
in SKOS Concept Scheme: TSICompliances
RINF index: 1.1.1.3.7.2.1
created: 2021-08-07
modified: 2023-03-14
comment: Indication whether required distance between two consecutive axles is compliant with the TSI. Deprecated according to the amendment to the Regulation (EU) 2019/777.
deprecated: true
term status: stable

TSI compliance of maximum permitted impedance between opposite wheels of a wheelset
type: ObjectProperty
domain: Train Detection System
range: Concept
XML name: CTD_TSIMaxImpedanceWheelset
in SKOS Concept Scheme: TSICompliances
RINF index: 1.1.1.3.7.15.1
created: 2021-08-08
modified: 2023-03-14
comment: TSI compliance of maximum permitted impedance between opposite wheels of a wheelset. Deprecated according to the amendment to the Regulation (EU) 2019/777.
deprecated: true
term status: stable

TSI compliance of rules for vehicle metal construction
type: ObjectProperty
domain: Train Detection System
range: Concept
XML name: CTD_TSIMetalConstruction
in SKOS Concept Scheme: TSICompliances
RINF index: 1.1.1.3.7.13
created: 2021-08-08
modified: 2023-03-14
comment: TSI compliance of rules for vehicle metal construction. Deprecated according to the amendment to the Regulation (EU) 2019/777.
deprecated: true
term status: stable

TSI compliance of rules for metal-free space around wheels
type: ObjectProperty
domain: Train Detection System
range: Concept
XML name: CTD_TSIMetalFree
in SKOS Concept Scheme: TSICompliances
RINF index: 1.1.1.3.7.12
created: 2021-08-08
modified: 2023-03-14
comment: TSI compliance of rules for metal-free space around wheels. Deprecated according to the amendment to the Regulation (EU) 2019/777.
deprecated: true
term status: stable

TSI compliance of rules on combination of RST characteristics influencing shunting impedance
type: ObjectProperty
domain: Train Detection System
range: Concept
XML name: CTD_TSIRSTShuntImpedance
in SKOS Concept Scheme: TSICompliances
RINF index: 1.1.1.3.7.23
created: 2021-08-08
modified: 2023-03-14
comment: TSI compliance of rules on combination of RST characteristics influencing shunting impedance. Deprecated according to the amendment to the Regulation (EU) 2019/777.
deprecated: true
term status: stable

TSI compliant radio (RMR)
type: ObjectProperty
sub property of: Control-command and signalling subsystem
RINF index: 1.1.1.3.3
RINF index: 1.2.1.1.2
created: 2024-10-31

TSI Compliance of rules on sand characteristics
type: ObjectProperty
domain: Train Detection System
range: Concept
XML name: CTD_TSISandCharacteristics
in SKOS Concept Scheme: TSICompliances
RINF index: 1.1.1.3.7.19
created: 2021-08-08
modified: 2023-03-14
comment: TSI Compliance of rules on sand characteristics. Deprecated according to the amendment to the Regulation (EU) 2019/777.
deprecated: true
term status: stable

TSI compliance of sanding
type: ObjectProperty
domain: Train Detection System
range: Concept
in SKOS Concept Scheme: TSICompliances
RINF index: 1.1.1.3.7.16
created: 2021-08-08
modified: 2023-03-14
comment: TSI compliance of sanding rules to allow compatibility with track circuits. Too much sand brings the risk of not detecting trains in tracks equipped with track circuits. Deprecated according to the amendment to the Regulation (EU) 2019/777.
deprecated: true
term status: unstable

TSI compliance of rules on shunt assisting devices
type: ObjectProperty
domain: Train Detection System
range: Concept
XML name: CTD_TSIShuntDevices
in SKOS Concept Scheme: TSICompliances
RINF index: 1.1.1.3.7.22
created: 2021-08-08
modified: 2023-03-14
comment: Deprecated according to the amendment to the Regulation (EU) 2019/777. TSI compliance of rules on shunt assisting devices.
deprecated: true
term status: stable

TSI compliant train protection system (ETCS)
type: ObjectProperty
sub property of: Control-command and signalling subsystem
RINF index: 1.1.1.3.2
RINF index: 1.2.1.1.1
created: 2024-10-31

Accepted TSI compliant pantograph heads
type: ObjectProperty
sub property of: Pantograph
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: Concept
XML name: EPA_TSIHeads
applicable: Y/N
dependency note: Mandatory only if “Overhead contact line (OCL)” is selected in 1.1.1.2.2.1.1, otherwise the parameter is not applicable.
in SKOS Concept Scheme: CompliantPantographHeads
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.1.1.2.3.1
SHACL shape validation rule: TsiPantographHeadApplicability
SHACL shape validation rule: TsiPantographHeadSKOS
used in RCC calculations: true
created: 2020-08-25
modified: 2021-09-11
modified: 2024-09-25
modified: 2025-02-28
relation: Type of contact line system
source: http://data.europa.eu/eli/reg/2014/1302/2023-09-28
comment: Indication of TSI compliant pantograph heads which are allowed to be used.
see also: LOC&PAS TSI: 4.2.8.2.9.2 EN 50367 (2012): Annex A.2 and EN 50206-1 (2010): 4.2 and 6.2.3
term status: stable
editorial note: The allowed values for this property belong to the SKOS Concept Scheme http://data.europa.eu/949/concepts/compliant-pantograph-heads/CompliantPantographHeads.
scope note: 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.

Document available from the IM with precise description of the tunnel
type: ObjectProperty
sub property of: Tunnel
domain: Tunnel
range: ERA Document
XML name: ITU_TunnelDocRef
applicable: Y/N
legal deadline: 1 January 2021
RINF index: 1.1.1.1.8.8.2
SHACL shape validation rule: TunnelDocRef
created: 2021-08-03
modified: 2024-01-08
modified: 2024-04-23
modified: 2024-09-19
comment: Electronic document available from the IM stored by the Agency with precise description of the clearance gauge and geometry of the tunnel.
term status: stable
scope note: 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.

Tunnel
type: ObjectProperty
sub property of: Infrastructure subsystem
RINF index: 1.1.1.1.8
RINF index: 1.2.1.0.5
RINF index: 1.2.2.0.5
created: 2024-10-31

Type version id
type: ObjectProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: Concept
in SKOS Concept Scheme: TypeVersionIds
created: 2022-11-03
comment: Indicates the registrationVersion with Ids 10, 20 and 30 indicating registration according to Directive 2008/57/EC and implementing Decision 2011/665/EU, and 40 and 50 indicating registration according to regime described in Directive 2008/57/EC. The allowed values for this property belong to the SKOS Concept Scheme http://data.europa.eu/949/concepts/type-version-ids/TypeVersionIds.
term status: stable

validity
type: ObjectProperty
domain: ERA Feature
range: Temporal Feature
SHACL shape validation rule: Validity
modified: 2024-11-29
comment: Relates a feature with a temporal feature to indicate a validity period.

Vehicle category
type: ObjectProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: Concept
ERATV index: 1.4
in SKOS Concept Scheme: Categories
created: 2025-02-13
modified: 2025-05-09
replaces: category
comment: Indicates the core purpose of a railway vehicle: delivering traction, transporting goods or passengers or serving as a special vehicle.
term status: stable

vehicle keeper
type: ObjectProperty
sub property of: Vehicle technical characteristic
domain: Vehicle
range: Organisation Role
created: 2020-11-23
modified: 2024-06-03
modified: 2024-10-24
modified: 2025-02-18
replaces: (deprecated) Vehicle Keeper
comment: The natural or legal person that, being the owner of a vehicle or having the right to use it, exploits the vehicle as a means of transport and is registered as such in a vehicle register referred to in Article 47 of (EU)2016/797.
term status: stable

Vehicle subcategory
type: ObjectProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: Concept
ERATV index: 1.5
in SKOS Concept Scheme: Categories
created: 2025-02-13
modified: 2025-05-09
replaces: subCategory
comment: Indicates the further classification (but not any family/platform) of vehicles within a vehicle category.
term status: stable

Vehicle technical characteristic
type: ObjectProperty

Vehicle type
type: ObjectProperty
sub property of: Vehicle technical characteristic
domain: Vehicle
range: Vehicle Type
created: 2020-11-22
modified: 2020-11-22
comment: Indicates the vehicle type of a specific vehicle or wagon.
term status: stable

Vehicle type maximum speed and cant deficiency
type: ObjectProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: Maximum speed and cant deficiency
ERATV index: 4.6.4
created: 2023-04-05
modified: 2025-02-18
replaces: Maximum speed and cant deficiency
comment: Relates the vehicle type with its values of maximum speed and cant deficiency.
term status: stable

Vehicle type technical characteristic
type: ObjectProperty
created: 2024-10-31

List of vehicle types already identified as compatible with Traffic load and load carrying capacity of infrastructure and train detection systems
type: ObjectProperty
sub property of: Vehicles for which Route compatibility is verified
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: Class
  union of: ERA Document
  union of: Vehicle Type
applicable: Y/N/NYA
legal deadline: 12 months after publication of Article 7 Guide
RINF index: 1.1.1.5.1
created: 2023-03-14
modified: 2024-10-24
modified: 2025-03-10
modified: 2025-03-11
modified: 2025-10-17
comment: The infrastructure managers shall provide through RINF the information to the RU regarding list of vehicle types compatible with the route for which they have already verified compatibility for parameter Traffic load and load carrying capacity of infrastructure and train detection systems, where such information is available.
term status: unstable

List of vehicles already identified as compatible with Traffic load and load carrying capacity of infrastructure and train detection systems
type: ObjectProperty
sub property of: Vehicles for which Route compatibility is verified
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: Class
  union of: ERA Document
  union of: Vehicle
applicable: Y/N/NYA
legal deadline: 12 months after publication of Article 7 Guide
RINF index: 1.1.1.5.2
created: 2023-03-14
modified: 2024-10-24
modified: 2025-03-10
modified: 2025-03-11
modified: 2025-10-17
comment: The infrastructure managers shall provide through RINF the information or a document to the RU regarding list of vehicles compatible with the route for which they have already verified compatibility for parameter Traffic load and load carrying capacity of infrastructure and train detection systems, where such information is available.
term status: unstable

Vehicles for which Route compatibility is verified
type: ObjectProperty
sub property of: RINF Technical characteristic
RINF index: 1.1.1.5
created: 2025-03-11

Voice GSM-R network
type: ObjectProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: Concept
ERATV index: 4.13.2.10
in SKOS Concept Scheme: GSMRNetworks
created: 2020-08-31
modified: 2021-08-02
comment: Voice SIM Card GSM-R Home Network. The allowed values for this property belong to the SKOS Concept Scheme http://data.europa.eu/949/concepts/gsmr-networks/GSMRNetworks
term status: stable

Radio system compatibility voice
type: ObjectProperty
sub property of: TSI compliant radio (RMR)
sub property of: Vehicle type technical characteristic
domain: Class
  union of: Subset with common characteristics
  union of: Running track
  union of: Vehicle Type
range: Concept
applicable: Y/N/NYA
dependency note: GSM-R must be installed for this parameter to be applicable. In case of RSC-EU-0 or None, no other values are allowed.
ERATV index: 4.13.2.5
in SKOS Concept Scheme: RadioSystemCompatibilitiesVoice
legal deadline: 12 months after publication of Article 7 Guide for OP tracks
legal deadline: 16 January 2020
RINF index: 1.1.1.3.3.9
RINF index: 1.2.1.1.2.9
SHACL shape validation rule: VoiceRadioCompatible
SHACL shape validation rule: VoiceRadioCompatibleApplicability
SHACL shape validation rule: VoiceRadioCompatibleSKOS
used in RCC calculations: true
created: 2020-08-31
modified: 2021-09-12
modified: 2024-04-18
modified: 2024-09-19
comment: Radio requirements used for demonstrating technical compatibility voice.
term status: stable
scope note: 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.

Nominal track gauge
type: ObjectProperty
sub property of: Track parameters
sub property of: Vehicle type technical characteristic
type: FunctionalProperty
domain: Class
  union of: Subset with common characteristics
  union of: Running track
  union of: Vehicle Type
range: Concept
XML name: ITP_NomGauge
applicable: Y
ERATV index: 4.1.3
in SKOS Concept Scheme: NominalTrackGauges
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.1.1.1.4.1
RINF index: 1.2.1.0.4.1
SHACL shape validation rule: WheelSetGauge
SHACL shape validation rule: WheelSetGaugeSKOS
used in RCC calculations: true
created: 2020-07-29
modified: 2024-01-08
modified: 2024-09-19
modified: 2025-02-28
source: http://data.europa.eu/eli/reg/2014/1299/2023-09-28
comment: A single value expressed in millimetres that identifies the track gauge.
see also: INF TSI: 4.2.4.1
term status: stable
scope note: 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.

Wheelset gauge changeover facility
type: ObjectProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: Concept
ERATV index: 4.1.11
in SKOS Concept Scheme: GaugeChangeoverFacilities
created: 2020-09-01
modified: 2021-08-24
comment: Wheelset gauge changeover facility. The allowed values for this property belong to the SKOS Concept Scheme http://data.europa.eu/949/concepts/gauge-changeover-facilities/GaugeChangeoverFacilities
term status: stable

hasGeometry
type: ObjectProperty
domain: Feature
range: Geometry
RINF index: 1.1.0.0.1.1
RINF index: 1.1.1.0.1.1
RINF index: 1.1.1.3.14.6
RINF index: 1.2.0.0.0.5
RINF index: 1.2.1.0.8.5
SHACL shape validation rule: HasGeometry
used in RCC calculations: true
contributor: Matthew Perry
creator: OGC GeoSPARQL 1.0 Standard Working Group
date: 2011-06-16
comment: A spatial representation for a given feature.

has beginning
type: ObjectProperty
sub property of: has time
domain: Temporal entity
range: Time instant
SHACL shape validation rule: HasBeginning
comment: Beginning of a temporal entity
comment: Comienzo de una entidad temporal. @es
label: tiene principio @es
definition: Beginning of a temporal entity.

has end
type: ObjectProperty
sub property of: has time
domain: Temporal entity
range: Time instant
SHACL shape validation rule: HasEnd
comment: End of a temporal entity.
comment: Final de una entidad temporal. @es
label: tiene fin @es

has time
type: ObjectProperty
range: Temporal entity
comment: Proporciona soporte a la asociación de una entidad temporal (instante o intervalo) a cualquier cosa. @es
comment: Supports the association of a temporal entity (instant or interval) to any thing
label: tiene tiempo @es
editorial note: Característica arriesgada -añadida en la revisión del 2017 que no ha sido todavía utilizada de forma amplia. @es
editorial note: Feature at risk - added in 2017 revision, and not yet widely used.

Vehicle Type - Alternative name
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: string
ERATV index: 1.2
created: 2020-07-29
modified: 2020-07-29
modified: 2024-04-18
comment: Alternative name of a vehicle type.
term status: stable

Altitude range
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: string
ERATV index: 4.3.2
created: 2021-08-26
modified: 2021-08-26
comment: Altitude range.
term status: stable

Altitude range detail
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: integer
ERATV index: 4.3.2.1
created: 2021-08-26
modified: 2021-08-26
comment: Altitude range value for 'X' if value 'AX' is selected in altitude range.
term status: stable

applies in both directions
type: DatatypeProperty
type: FunctionalProperty
domain: Linear Element Section
range: boolean
SHACL shape validation rule: AppliesInBothDirections
created: 2024-11-29
comment: Specifies if the section applies in both directions (optional).

Range of use of the platform boarding aid
type: DatatypeProperty
sub property of: Platform
type: FunctionalProperty
domain: Class
  union of: Subset with common characteristics
  union of: Platform edge
range: integer
XML name: IPL_AreaBoardingAid
applicable: Y/N
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.2.1.0.6.7
SHACL shape validation rule: AreaBoardingAid
Unit of measure: MilliM
created: 2021-08-02
modified: 2023-01-20
modified: 2025-03-11
comment: Information of the train access level for which the boarding aid can be used.
term status: stable
scope note: 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.

Existence of platform assistance for starting train
type: DatatypeProperty
sub property of: Platform
type: FunctionalProperty
domain: Class
  union of: Subset with common characteristics
  union of: Platform edge
range: boolean
XML name: IPL_AssistanceStartingTrain
applicable: Y/N
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.2.1.0.6.6
SHACL shape validation rule: AssistanceStartingTrain
created: 2021-08-02
modified: 2021-08-02
modified: 2025-03-11
comment: Indication of existence of equipment or staff supporting the train crew in starting the train.
term status: stable

(Deprecated) ATO error corrections required for the on-board. Use: errorCorrectionsOnboard
type: DatatypeProperty
range: anyURI
RINF index: 1.1.1.3.13.4
created: 2023-03-14
modified: 2024-04-18
comment: List of unacceptable errors impacting the IM network that are required to be solved in the on-board ATO according to the CCS TSI point 7.2.10.3 specification maintenance point.
deprecated: true

Automatic dropping device required
type: DatatypeProperty
sub property of: Requirements for rolling stock
type: FunctionalProperty
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: boolean
XML name: ERS_AutoDropRequired
applicable: Y/N
dependency note: A value is mandatory if the value Overhead contact line (OCL) is selected for parameter "Type of contact line system"
format note: Y/N
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.1.1.2.5.3
SHACL shape validation rule: AutomaticDroppingDeviceRequired
SHACL shape validation rule: AutomaticDroppingDeviceRequiredApplicability
used in RCC calculations: true
created: 2020-08-25
modified: 2021-09-12
comment: Indication of whether an automatic dropping device (ADD) required on the vehicle.
see also: LOC&PAS TSI: 4.2.8.2.9.10 EN 50206-1:2010
term status: stable

Axle spacing
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: string
ERATV index: 4.5.3.4
created: 2020-08-24
modified: 2021-08-26
comment: Position of the axles along the unit. a: Distance between axles; b: Distance from end axle to the end of the nearest coupling plane; c: distance between two inside axles.
term status: stable

Big Metal Mass
type: DatatypeProperty
sub property of: TSI compliant train protection system (ETCS)
type: FunctionalProperty
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: boolean
applicable: Y/N/NYA
dependency note: A value has to be provided when ETCS is present (a value is provided on 1.1.1.3.2.1).
format note: Y/N
legal deadline: 12 months after publication of Article 7 Guide
legal deadline: 12 months after publication of Article 7 Guide for OP tracks
RINF index: 1.1.1.3.2.18
RINF index: 1.2.1.1.1.18
SHACL shape validation rule: BigMetalMass
SHACL shape validation rule: BigMetalMassApplicability
TSI operation appendix D2 index: 3.4.10
created: 2023-03-14
modified: 2024-01-08
modified: 2024-04-18
relation: European Train Control System (ETCS) level
source: oj
comment: Indication of existence of metal mass in the vicinity of the location, susceptible of perturbating the reading of balises by the on-board system.
term status: stable
scope note: According to the specification referenced in TSI CCS.

Boarding aids
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: string
ERATV index: 4.12.3.2
created: 2021-08-31
modified: 2021-08-31
comment: Description of any integrated boarding aids (if provided).
term status: stable

Border point identification
type: DatatypeProperty
sub property of: Identifier
type: FunctionalProperty
domain: Reference border point
range: string
SHACL shape validation rule: BorderPointId
created: 2024-11-26
comment: Border point identification in the list of reference border points in the RINF application guide.
term status: stable

Brake related parameters
type: DatatypeProperty
sub property of: Control-command and signalling subsystem
RINF index: 1.1.1.3.11
created: 2024-10-31

Brake weight percentage
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: string
ERATV index: 4.7.6
created: 2020-08-24
modified: 2021-08-26
comment: Brake weight percentage (lambda) or Braked mass.
term status: stable

Cant defficiency
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: integer
ERATV index: 4.6.1
Unit of measure: MilliM
created: 2021-08-26
modified: 2021-08-26
modified: 2024-06-26
modified: 2025-03-05
comment: Cant deficiency (maximum uncompensated lateral acceleration) for which the vehicle has been assessed. For dual gauge vehicles values for each gauge have to be indicated.
deprecated: true
term status: stable

Cant deficiency
type: DatatypeProperty
sub property of: Track parameters
type: FunctionalProperty
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: integer
XML name: ITP_CantDeficiency
applicable: Y
format note: +/-NNN
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.1.1.1.4.2
SHACL shape validation rule: CantDeficiency
Unit of measure: MilliM
used in RCC calculations: true
created: 2020-08-24
modified: 2021-09-10
modified: 2024-09-19
modified: 2025-02-28
source: http://data.europa.eu/eli/reg/2014/1299/2023-09-28
comment: Maximum cant deficiency expressed in millimetres defined as difference between the applied cant and a higher equilibrium cant the line has been designed for.
see also: INF TSI: 4.2.4.3
term status: stable
scope note: 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.

Catenary max rated current
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: double
ERATV index: 4.10.3
created: 2021-08-31
modified: 2021-08-31
comment: Maximum rated current from the catenary (to be indicated for each electrical energy supply system the vehicle is equipped for), given in A.
term status: stable

Control-command and signalling subsystem
type: DatatypeProperty
sub property of: RINF Technical characteristic
RINF index: 1.1.1.3
created: 2024-10-31

Declarations of verification for track
type: DatatypeProperty
sub property of: Control-command and signalling subsystem
RINF index: 1.1.1.3.1
created: 2024-10-31

Compliance of the tunnel with TSI INF
type: DatatypeProperty
sub property of: Tunnel
type: FunctionalProperty
domain: Class
  union of: Subset with common characteristics
  union of: Tunnel
range: boolean
XML name: ITU_TSITunnel
applicable: Y/N
dependency note: Mandatory if the speed of the line is equal or greater than 200km/h
legal deadline: 1 January 2021
RINF index: 1.1.1.1.8.8.1
SHACL shape validation rule: ComplianceInfTsiApplicability
SHACL shape validation rule: ComplianceInfTsiP
created: 2021-08-03
modified: 2024-01-08
modified: 2024-09-19
comment: Compliance of the tunnel with TSI INF at the maximum permitted speed
see also: [4.2.10.1 of INF TSI on Maximum pressure variations in tunnels | ]
term status: stable

Composite brake block retrofitted
type: DatatypeProperty
sub property of: Vehicle technical characteristic
domain: Vehicle
range: boolean
created: 2020-11-23
modified: 2020-11-23
comment: Indicates if a vehicle's composite brake block is retrofitted
term status: stable

Permitted conditions for charging electric energy storage for traction purposes at standstill
type: DatatypeProperty
sub property of: Contact line system
type: FunctionalProperty
domain: Contact Line System
range: anyURI
applicable: Y/N
legal deadline: Contrary to the Regulation, the deadline is not 30 June 2024 at the latest, but 12 months after publication of Article 7 Guide
RINF index: 1.2.1.0.7.2
SHACL shape validation rule: ConditionsChargingElectricEnergyStorage
created: 2023-03-14
comment: Conditions set by IMs according to a standardised document
term status: stable

Special conditions to switch over between different class B train protection, control and warning systems
type: DatatypeProperty
sub property of: Transitions between systems
type: FunctionalProperty
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: string
applicable: Y/N/NYA
dependency note: Applicable when at least two different protection, control and warning systems exist.
format note: NNN
legal deadline: 12 months after publication of Article 7 Guide
RINF index: 1.1.1.3.8.1.1
RINF index: 1.2.1.1.7.1.1
SHACL shape validation rule: ConditionsSwitchTrainProtectionSystems
TSI operation appendix D2 index: 3.4.2
created: 2022-10-28
relation: Existence of switch over between different protection, control and warning systems while running
source: oj
comment: Conditions to switch over between different class B train protection, control and warning systems.
term status: stable
scope note: Switch over between different systems whilst running. Installation depends on local conditions.

Conditions train formation
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: string
ERATV index: 4.1.4
created: 2021-08-25
modified: 2021-08-25
comment: Conditions of use regarding train formation.
term status: stable

Contact line system
type: DatatypeProperty
sub property of: Energy subsystem
RINF index: 1.1.1.2.2
created: 2024-10-31

Contact strip material metallic content
type: DatatypeProperty
sub property of: Pantograph
type: FunctionalProperty
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: integer
XML name: EPA_StripMaterial
dependency note: Mandatory only if impregnated carbon ([NN] % of metallic content)” is selected in 1.1.1.2.3.4, otherwise no value should be provided
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.1.1.2.3.4
SHACL shape validation rule: ContactStripMaterialMetallicContent
used in RCC calculations: true
created: 2023-01-25
modified: 2024-09-25
modified: 2025-02-28
relation: Type of contact line system
source: http://data.europa.eu/eli/reg/2014/1302/2023-09-28
comment: Indication of max. percentage of contact strip material Impregnated Carbon permitted to be used.
see also: LOC&PAS TSI: 4.2.8.2.9.4.2
term status: stable
scope note: 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.

container handling flag
type: DatatypeProperty
type: FunctionalProperty
domain: Primary Location
range: boolean
SHACL shape validation rule: ContainerHandlingFlag
created: 2024-06-03
term status: stable

Cross section area
type: DatatypeProperty
sub property of: Tunnel
type: FunctionalProperty
domain: Class
  union of: Subset with common characteristics
  union of: Tunnel
range: integer
XML name: ITU_CrossSectionArea
applicable: Y/N
dependency note: Mandatory if the speed of the line is equal or greater than 200km/h
format note: NNN
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.1.1.1.8.8
SHACL shape validation rule: CrossSectionAreaApplicability
SHACL shape validation rule: CrossSectionAreaT
Unit of measure: M2
created: 2021-08-03
modified: 2021-08-03
modified: 2024-09-19
comment: Smallest cross section area in square metres of the tunnel
see also: [4.2.10.1 of INF TSI on Maximum pressure variations in tunnels |
term status: stable
scope note: 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.

Current or power limitation on board required
type: DatatypeProperty
sub property of: Requirements for rolling stock
domain: Contact Line System
range: boolean
XML name: ERS_PowerLimitOnBoard
applicable: Y/N
dependency note: When "not electrified" is chosen in parameter "Type of contact line system", then this parameter is not applicable.
format note: Y/N
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.1.1.2.5.1
SHACL shape validation rule: CurrentLimitationRequired
SHACL shape validation rule: CurrentLimitationRequiredApplicability
used in RCC calculations: true
created: 2020-08-25
modified: 2021-09-12
modified: 2025-02-28
comment: Indication of whether an on board current or power limitation function on vehicles is required.
see also: LOC&PAS TSI: 4.2.8.2.4
term status: stable

Currently valid
type: DatatypeProperty
domain: ERA Feature
range: boolean
created: 2022-12-13
deprecated: true
term status: stable

D_NVOVTRP
type: DatatypeProperty
sub property of: ETCS National Values
type: FunctionalProperty
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: Datatype
  on datatype: decimal
  with restrictions:
    min inclusive: 0.0
  with restrictions:
    max inclusive: 327670.0
applicable: Y/N/NYA
dependency note: A value has to be provided when ETCS is present (a value is provided on 1.1.1.3.2.1).
format note: NNNNNNN.N whereby the last digit is only used when Q_SCALE = 10 CM
legal deadline: 12 months after publication of Article 7 Guide
RINF index: 1.1.1.3.2.16.5
RINF index: 1.2.1.1.1.16.5
SHACL shape validation rule: DNvovtrp
SHACL shape validation rule: DNvovtrpApplicability
TSI operation appendix D3 index: 1.5.5
Unit of measure: http://qudt.org/vocab/unit/M
created: 2022-11-07
modified: 2024-01-08
modified: 2024-04-18
modified: 2024-12-05
relation: European Train Control System (ETCS) level
source: oj
comment: Maximum distance for overriding the train trip in metres, according to the specification referenced in Appendix A-1, index [C].
term status: stable
scope note: 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.

D_NVPOTRP
type: DatatypeProperty
sub property of: ETCS National Values
type: FunctionalProperty
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: Datatype
  on datatype: decimal
  with restrictions:
    min inclusive: 0.0
  with restrictions:
    max inclusive: 327670.0
applicable: Y/N/NYA
format note: NNNNNNN.N whereby the last digit is only used when Q_SCALE = 10 CM
legal deadline: 12 months after publication of Article 7 Guide
RINF index: 1.1.1.3.2.16.7
RINF index: 1.2.1.1.1.16.7
SHACL shape validation rule: DNvpotrp
SHACL shape validation rule: DNvpotrpApplicability
TSI operation appendix D3 index: 1.5.7
Unit of measure: http://qudt.org/vocab/unit/M
created: 2022-11-07
modified: 2023-03-14
modified: 2024-04-18
modified: 2024-12-05
relation: European Train Control System (ETCS) level
source: oj
comment: Maximum distance for reversing in Post Trip mode in metres, according to the specification referenced in Appendix A-1, index [C].
term status: stable
scope note: 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)

D_NVROLL
type: DatatypeProperty
sub property of: ETCS National Values
type: FunctionalProperty
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: Datatype
  on datatype: decimal
  with restrictions:
    min inclusive: 0.0
  with restrictions:
    max inclusive: 327670.0
applicable: Y/N/NYA
dependency note: A value has to be provided when ETCS is present (a value is provided on 1.1.1.3.2.1).
format note: A number of form at NNNNNN.N, from 0 to 327670
legal deadline: 12 months after publication of Article 7 Guide
RINF index: 1.1.1.3.2.16.1
RINF index: 1.2.1.1.1.16.1
SHACL shape validation rule: DNvroll
SHACL shape validation rule: DNvrollApplicability
TSI operation appendix D3 index: 1.5.1
Unit of measure: http://qudt.org/vocab/unit/M
created: 2022-11-07
modified: 2023-03-14
modified: 2024-04-18
modified: 2024-12-05
modified: 2025-02-28
relation: European Train Control System (ETCS) level
source: oj
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 According to the specification referenced in Appendix A-1, index [C]
term status: stable
scope note: Precision: [NNNNNN.N], with N a decimal number (0 9). See: TSI CCS (Subset 26, chapter 7. 7.5.1.17 D_NVROLL)

Dangerous goods tank code
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: string
ERATV index: 4.1.9
created: 2021-08-25
modified: 2021-08-25
comment: Dangerous goods for which the vehicle is suitable (tank code).
term status: stable

EI declaration of demonstration (as defined Recommendation 2014/881/EU) for track relating to compliance with the requirements from TSIs applicable to energy subsystem
type: DatatypeProperty
sub property of: Declarations of verification for track
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: string
XML name: EDE_EIDemonstration
applicable: Y/N
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.1.1.2.1.2
SHACL shape validation rule: DemonstrationENE
created: 2021-08-08
modified: 2024-01-08
modified: 2024-09-19
source: oj
comment: Unique number for EI declarations following the same format requirements as specified for EC declarations in Annex VII of Commission Implementing Regulation (EU) 2019/250.
term status: stable

EI declaration of demonstration (as defined in Commission 2014/881/EU (2)) relating to compliance with the requirements from TSIs applicable to infrastructure subsystem
type: DatatypeProperty
sub property of: Declarations of verification for track
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: string
XML name: IDE_EIDemonstration
applicable: Y/N
format note: CC/RRRRRRRRRRRRRR/YYYY/NNNNNN
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.1.1.1.1.2
RINF index: 1.2.1.0.1.2
RINF index: 1.2.2.0.1.2
SHACL shape validation rule: DemonstrationINF
SHACL shape validation rule: DemonstrationINFS
created: 2021-08-03
modified: 2024-01-08
modified: 2024-09-19
source: oj
source: http://data.europa.eu/eli/reg_impl/2019/777/2023-09-28
comment: Unique number for EI declarations following the same format requirements as specified for EC declarations in Annex VII of Commission Implementing Regulation (EU) 2019/250.
term status: stable
scope note: 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.
scope note: 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.

EI declaration of demonstration (as defined in Recommendation 2014/881/EU) relating to compliance with the requirements from TSIs applicable to railway tunnel
type: DatatypeProperty
sub property of: Tunnel
domain: Class
  union of: Subset with common characteristics
  union of: Tunnel
range: string
XML name: ITU_EIDemonstration
applicable: Y/N
dependency note: 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.
format note: CC/RRRRRRRRRRRRRR/YYYY/NNNNNN
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.1.1.1.8.6
RINF index: 1.2.1.0.5.4
RINF index: 1.2.2.0.5.4
SHACL shape validation rule: DemonstrationSRT
created: 2021-08-03
modified: 2024-01-08
modified: 2024-06-26
modified: 2024-09-19
source: oj
source: http://data.europa.eu/eli/reg/2014/1303/2024-01-29
comment: Unique number for EI declarations following the same format requirements as specified for EC declarations in Annex VII of Commission Implementing Regulation (EU) 2019/250.
see also: [22] Recommendation 2014/881/EU
term status: stable
scope note: (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.

Design mass under exceptional payload
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: integer
ERATV index: 4.5.2.3
Unit of measure: KiloGM
created: 2020-08-24
modified: 2020-11-03
modified: 2024-06-26
comment: Design mass under exceptional payload.
term status: stable

Design mass under normal payload
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: integer
ERATV index: 4.5.2.2
Unit of measure: KiloGM
created: 2020-08-24
modified: 2020-11-03
modified: 2024-06-26
comment: Design mass under normal payload.
term status: stable

Design mass in working order
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: integer
ERATV index: 4.5.2.1
Unit of measure: KiloGM
created: 2020-08-24
modified: 2020-11-03
modified: 2024-06-26
comment: Design mass in working order.
term status: stable

Diesel or other thermal traction allowed
type: DatatypeProperty
sub property of: Tunnel
type: FunctionalProperty
domain: Class
  union of: Subset with common characteristics
  union of: Tunnel
range: boolean
XML name: ITU_DieselThermAllowed
applicable: Y/N
legal deadline: 1 January 2021
RINF index: 1.2.1.0.5.9
SHACL shape validation rule: DieselThermalAllowed
created: 2021-08-09
modified: 2021-08-09
source: http://data.europa.eu/eli/reg/2014/1303/2024-01-29
comment: Indication whether it is allowed to use diesel or other thermal traction in the tunnel
term status: stable

Digital schematic overview
type: DatatypeProperty
sub property of: Operational point generic information
domain: Operational Point
range: wktLiteral
applicable: Y/N/NYA
legal deadline: 12 months after publication of Article 7 Guide for OP tracks
RINF index: 1.2.0.0.0.7.2
SHACL shape validation rule: DigitalSchematicOverview
TSI operation appendix D2 index: 2.1
created: 2023-03-14
modified: 2025-03-11
comment: Diagrammatic representation of the operational point in Well Known Text polyline
term status: stable

Distance between signboard and phase separation ending
type: DatatypeProperty
sub property of: OCL separation sections
type: FunctionalProperty
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: integer
XML name: EOS_DistSignToPhaseEnd
applicable: Y/N
dependency note: It is applicable ( Y ) only if the value Overhead contact line (OCL) is selected for parameter "Type of contact line system"
format note: NNN
legal deadline: 16 January 2020
RINF index: 1.1.1.2.4.3
SHACL shape validation rule: DistSignToPhaseEnd
Unit of measure: http://qudt.org/vocab/unit/M
used in RCC calculations: true
created: 2021-08-08
modified: 2021-09-12
comment: 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.
term status: stable
scope note: Specific for route compatibility check on French network.

Document URL
type: DatatypeProperty
domain: ERA Document
range: anyURI
SHACL shape validation rule: DocumentUrl
created: 2024-04-23
comment: URL that is used to download a document, e.g. url for a reference document in RINF.
term status: stable

Driving cabs
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: integer
ERATV index: 4.1.1
created: 2021-08-24
modified: 2021-08-24
comment: Number of driving cabs. For wagons the number of driving cabs is to be set to zero (0).
term status: stable

Eddy current brake prevention
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: boolean
ERATV index: 4.7.4.1.2
created: 2020-08-24
modified: 2020-11-03
comment: Possibility of preventing the use of the eddy current track brake (only if fitted with eddy current brake)
term status: stable

Eddy current braking fitted
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: boolean
ERATV index: 4.7.4.1.1
created: 2022-09-06
comment: Eddy current track brake fitted. New property defined to distinguish it from eddyCurrentBraking which is a RINF SKOS property.
term status: stable

Emergency braking
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: string
ERATV index: 4.7.5
created: 2020-08-24
modified: 2021-08-26
comment: Stopping distance and deceleration profile for each load condition per design maximum speed.
term status: stable

End intrinsic coordinate
type: DatatypeProperty
range: double
created: 2021-04-01
modified: 2021-04-01
deprecated: true
term status: stable

end offset from the origin
type: DatatypeProperty
domain: Linear Element Section
range: double
SHACL shape validation rule: EndOffsetFromOrigin
Unit of measure: http://qudt.org/vocab/unit/M
created: 2024-11-29
modified: 2025-01-30
comment: End offset of the section from the origin.

Energy meter installed
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: boolean
ERATV index: 4.10.12
created: 2021-08-31
modified: 2021-08-31
comment: TSI conform energy meter for billing purposes installed on board.
term status: stable

Energy subsystem
type: DatatypeProperty
sub property of: RINF Technical characteristic
RINF index: 1.1.1.2
created: 2024-10-31

Declarations of verification for track
type: DatatypeProperty
sub property of: Energy subsystem
RINF index: 1.1.1.2.1
created: 2024-10-31

Energy supply max power
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: double
ERATV index: 4.10.2
created: 2021-08-31
modified: 2021-08-31
comment: Maximum power (to be indicated for each energy supply system the vehicle is equipped for), given in kW.
term status: stable

Energy supply system TSI compliant
type: DatatypeProperty
sub property of: Contact line system
type: FunctionalProperty
domain: Contact Line System
range: boolean
XML name: ECS_TSIVoltFreq
RINF index: 1.1.1.2.2.1.2.1
SHACL shape validation rule: EnergySupplySystemTSICompliant
used in RCC calculations: true
created: 2020-08-24
modified: 2021-08-06
modified: 2023-03-14
comment: Deprecated according to the amendment to the Regulation (EU) 2019/777. Indication if the traction supply system (nominal voltage and frequency) is fully compliant with TSI.
deprecated: true
term status: stable

Reasons for Error corrections required, but accepted by the IM for the on-board ETCS, GSM-R and/or ATO function
type: DatatypeProperty
sub property of: Declarations of verification for track
type: FunctionalProperty
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: string
applicable: Y/N/NYA
dependency note: A value has to be provided when ETCS is present (a value is provided on 1.1.1.3.2.1).
legal deadline: 12 months after the entry into force of TSI CCS and at least 12 months after publication of Article 7 Guide
RINF index: 1.1.1.3.1.2
RINF index: 1.2.1.1.1.19
SHACL shape validation rule: ErrorCorrectionsOnboardExplanation
created: 2024-04-18
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.
term status: stable

(Deprecated) ERTMS error corrections required for the on-board.
type: DatatypeProperty
range: anyURI
created: 2024-01-08
is replaced by: Error corrections required for the on-board ETCS, GSM-R and/or ATO function
modified: 2024-04-18
deprecated: true
term status: stable

ETCS data communication application
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: string
ERATV index: 4.13.2.9
created: 2021-08-31
modified: 2021-08-31
comment: Data communication application for ETCS implementation.
term status: stable

(Deprecated) ETCS error corrections required for the on-board.
type: DatatypeProperty
range: anyURI
created: 2023-03-14
is replaced by: Error corrections required for the on-board ETCS, GSM-R and/or ATO function
modified: 2024-01-08
modified: 2024-04-18
deprecated: true
term status: stable

ETCS trackside implements level crossing procedure or an equivalent solution
type: DatatypeProperty
sub property of: TSI compliant train protection system (ETCS)
type: FunctionalProperty
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: boolean
applicable: Y/N/NYA
dependency note: Applicable and mandatory when ETCS is present (a value is provided on 1.1.1.3.2.1).
legal deadline: 12 months after publication of Article 7 Guide
RINF index: 1.1.1.3.2.13
RINF index: 1.2.1.1.1.13
SHACL shape validation rule: EtcsImplementsLevelCrossingProcedure
SHACL shape validation rule: EtcsImplementsLevelCrossingProcedureApplicability
TSI operation appendix D3 index: 1.2
created: 2022-11-04
modified: 2024-04-18
modified: 2025-02-28
relation: European Train Control System (ETCS) level
source: oj
comment: If the trackside does not implement any solution to cover non-protected LXs (which are normally protected by means of a technical system), then drivers will be required to comply with instructions received from other sources
term status: stable
scope note: See: TSI CCS (Subset-026, Chapter 5, section 5.16)

ETCS infill necessary for line access
type: DatatypeProperty
sub property of: TSI compliant train protection system (ETCS)
type: FunctionalProperty
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: boolean
applicable: Y/N/NYA
dependency note: 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.
legal deadline: 12 months after publication of Article 7 Guide for OP tracks
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.1.1.3.2.3
RINF index: 1.2.1.1.1.3
SHACL shape validation rule: EtcsInfillLineAccess
SHACL shape validation rule: EtcsInfillLineAccessApplicability
created: 2021-08-08
modified: 2021-09-12
modified: 2025-02-28
modified: 2025-03-04
relation: European Train Control System (ETCS) level
source: oj
comment: Indication whether infill is required to access the line for safety reasons.
term status: stable
scope note: 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 national applications
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: string
ERATV index: 4.13.1.4
created: 2021-08-31
modified: 2021-08-31
comment: ETCS national applications implemented (NID_XUSER of Packet 44).
term status: stable

ETCS national packet 44 application implemented
type: DatatypeProperty
sub property of: TSI compliant train protection system (ETCS)
RINF index: 1.1.1.3.2.5
RINF index: 1.2.1.1.1.5
is replaced by: ETCS national packet 44 application implemented
is replaced by: has ETCS national packet 44 application implemented
modified: 2025-05-05
comment: Indication whether data for national applications is transmitted between track and train.
deprecated: true

ETCS National Values
type: DatatypeProperty
sub property of: TSI compliant train protection system (ETCS)
RINF index: 1.1.1.3.2.16
RINF index: 1.2.1.1.1.16
created: 2024-10-31

ETCS on-board implementation
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: string
ERATV index: 4.13.1.7
created: 2021-08-31
modified: 2021-08-31
comment: ETCS on-board implementation.
term status: stable

ETCS optional functions
type: DatatypeProperty
range: string
RINF index: 1.1.1.3.2.7
created: 2021-08-08
modified: 2023-03-14
source: oj
comment: Deprecated according to the amendment to the Regulation (EU) 2019/777. Optional ETCS functions which might improve operation on the line.
deprecated: true
term status: unstable

ETCS system version 2.2 or 3.0 functionalities to be required in the next 5 years
type: DatatypeProperty
range: anyURI
applicable: N
legal deadline: 12 months after publication of Article 7 Guide
RINF index: 1.1.1.3.2.19
RINF index: 1.2.1.1.1.20
created: 2023-03-14
modified: 2024-01-08
modified: 2024-04-18
comment: (Deprecated) List of ETCS system version 2.2 or 3.0 functionalities to be required in the next 5 years according to TSI CCS point 6.1.1.2 and Appendix G
deprecated: true
term status: stable
scope note: Not needed for internal trackside params (no use at the moment). This parameter was intented for a former version of Appendix G, but the requirement is stil in CCS TSI 6.1.1.2.

Is the ETCS trackside engineered to transmit Track Conditions
type: DatatypeProperty
sub property of: TSI compliant train protection system (ETCS)
domain: ETCS
range: boolean
applicable: Y/N/NYA
dependency note: A value has to be provided when ETCS is present (a value is provided on 1.1.1.3.2.1).
legal deadline: 12 months after publication of Article 7 Guide
RINF index: 1.1.1.3.2.12
RINF index: 1.2.1.1.1.12
SHACL shape validation rule: EtcsTransmitsTrackConditions
SHACL shape validation rule: EtcsTransmitsTrackConditionsApplicability
TSI operation appendix D3 index: 1.1
created: 2022-11-04
modified: 2023-03-14
modified: 2024-04-18
modified: 2025-02-28
relation: European Train Control System (ETCS) level
source: oj
comment: If the trackside does not provide Track Conditions, the driver will need to be informed about such conditions via alternative methods. According to the specification referenced in Appendix A-1, index [C]
term status: stable
scope note: 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)

Industrial risks — locations where it is dangerous for the driver to step out
type: DatatypeProperty
sub property of: Route book specific parameters
type: FunctionalProperty
domain: Class
  union of: Subset with common characteristics
  union of: Section Of Line
range: boolean
applicable: Y/NYA
format note: Y/N
legal deadline: 12 months after publication of Article 7 Guide
RINF index: 1.1.0.0.1.1
TSI operation appendix D2 index: 3.2.5
created: 2025-01-30
comment: Indication that the full section of line (or a part of it) it is identified by the Infrastructure Managers (and communicated to the RU) where drivers are not supposed to get off the locomotive.
term status: stable
scope note: 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

Ferromagnetic wheel material
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: boolean
ERATV index: 4.14.2.12
created: 2021-09-01
modified: 2021-09-01
comment: Wheel material is ferromagnetic.
term status: stable

Fixed seats
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: string
ERATV index: 4.12.1.1
created: 2021-08-31
modified: 2021-08-31
comment: Number of fixed seats.
term status: stable

Use of flange lubrication forbidden
type: DatatypeProperty
sub property of: Health, safety and environment
type: FunctionalProperty
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: boolean
XML name: IHS_FlangeLubeForbidden
applicable: Y
format note: in XML: Y/N
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.1.1.1.7.1
SHACL shape validation rule: FlangeLubeForbidden
used in RCC calculations: true
created: 2021-08-08
modified: 2021-09-11
comment: Indication whether the use of on-board device for flange lubrication is forbidden.
term status: stable

Existence of rules on on-board flange lubrication
type: DatatypeProperty
domain: Train Detection System
range: boolean
XML name: CTD_FlangeLubeRules
RINF index: 1.1.1.3.7.20
created: 2021-08-08
modified: 2023-03-14
comment: Deprecated according to the amendment to the Regulation (EU) 2019/777. Indication whether rules for activation or deactivation of flange lubrication exist.
deprecated: true
term status: stable

Flange lubrication fitted
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: boolean
ERATV index: 4.9.3.1
created: 2021-08-31
modified: 2021-08-31
comment: Indicates if the vehicle type is fitted for flange lubrication.
term status: stable

freight flag
type: DatatypeProperty
type: FunctionalProperty
domain: Primary Location
range: boolean
SHACL shape validation rule: FreightFlag
created: 2024-06-03
comment: Freight possible flag attached to a Primary Location.
term status: stable

Section with train detection limitation
type: DatatypeProperty
type: FunctionalProperty
domain: Section with train detection limitation
range: boolean
XML name: CTD_TCLimitation
SHACL shape validation rule: FrenchTrainDetectionSystemLimitationApplicable
used in RCC calculations: true
created: 2023-04-05
modified: 2025-02-18
modified: 2025-03-11
replaces: Section with train detection limitation, only for the French network
comment: Part of the section with train detection limitation that indicates if it is applicable. Only for the French network.
term status: stable

Railway location of particular points requiring specific checks
type: DatatypeProperty
sub property of: Line layout
type: FunctionalProperty
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: string
XML name: ILL_GaugeCheckLoc
applicable: Y/N
legal deadline: 16 January 2020
RINF index: 1.1.1.1.3.1.2
RINF index: 1.2.1.0.3.5
SHACL shape validation rule: GaugingCheckLocation
used in RCC calculations: true
created: 2020-07-29
modified: 2024-01-08
modified: 2024-09-19
modified: 2025-02-28
comment: Location of particular points requiring specific checks due to deviations from gauging referred to in parameter "Gauging"
term status: stable
scope note: 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).

GPRS for ETCS
type: DatatypeProperty
sub property of: TSI compliant radio (RMR)
type: FunctionalProperty
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: boolean
applicable: Y/N/NYA
dependency note: GSM-R and ETCS L2 must be installed for this parameter to be applicable.
legal deadline: 1 January 2021
legal deadline: 12 months after publication of Article 7 Guide for OP tracks
RINF index: 1.1.1.3.3.3.2
RINF index: 1.2.1.1.2.3.2
SHACL shape validation rule: GprsForETCS
SHACL shape validation rule: GprsForETCSApplicability
created: 2021-08-08
modified: 2021-09-12
modified: 2024-04-18
modified: 2025-03-04
relation: European Train Control System (ETCS) level
source: oj
comment: Indication if GPRS can be used for ETCS
term status: stable
scope note: Sections of EIRENE and ETCS subsets for trackside in TSI

Area of implementation of GPRS
type: DatatypeProperty
sub property of: TSI compliant radio (RMR)
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: string
applicable: Y/N/NYA
dependency note: GSM-R, ETCS L2 and GPRS for ETCS must be installed for this parameter to be applicable.
legal deadline: 1 January 2021
legal deadline: 12 months after publication of Article 7 Guide for OP tracks
RINF index: 1.1.1.3.3.3.3
RINF index: 1.2.1.1.2.3.3
SHACL shape validation rule: GprsImplementationArea
SHACL shape validation rule: GprsImplementationAreaApplicability
created: 2021-08-09
modified: 2021-09-12
modified: 2024-04-18
modified: 2024-09-19
modified: 2025-02-28
modified: 2025-03-04
relation: European Train Control System (ETCS) level
relation: GPRS for ETCS
source: oj
comment: Indication of the area in which GPRS can be used for ETCS, expressed as a list of GPRS-enabled RBCs.
see also: Sections of EIRENE optional for trackside in TSI
term status: stable
scope note: 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…)

Gradient for stabling tracks
type: DatatypeProperty
sub property of: Siding
type: FunctionalProperty
domain: Class
  union of: Subset with common characteristics
  union of: Siding
range: double
XML name: ILL_Gradient
applicable: Y/N
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.2.2.0.3.1
SHACL shape validation rule: Gradient
Unit of measure: MilliM-PER-M
used in RCC calculations: true
created: 2021-08-10
modified: 2021-08-10
modified: 2024-09-19
modified: 2025-03-11
source: http://data.europa.eu/eli/reg/2014/1299/2023-09-28
comment: Maximum value of the gradient for stabling tracks expressed in millimetres per metre.
term status: stable

Gradient profile
type: DatatypeProperty
sub property of: Line layout
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: string
XML name: ILL_GradProfile
applicable: Y
format note: in XML: +/-NN.N (+/-NNNN.NNN)
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.1.1.1.3.6
SHACL shape validation rule: GradientProfile
TSI operation appendix D2 index: 3.2.1
TSI operation appendix D2 index: 3.2.2
used in RCC calculations: true
created: 2020-08-24
modified: 2021-09-10
modified: 2024-09-19
modified: 2025-02-28
source: http://data.europa.eu/eli/reg/2014/1299/2023-09-28
comment: Sequence of gradient values and locations of change in gradient
see also: INF TSI: 4.2.3.3
term status: stable
scope note: 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.

No GSMR coverage
type: DatatypeProperty
sub property of: TSI compliant radio (RMR)
type: FunctionalProperty
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: boolean
applicable: Y/N/NYA
dependency note: GSM-R (parameter 1.1.1.3.3.1) must be installed for this parameter to be applicable.
dependency note: GSM-R must be installed for this parameter to be applicable
legal deadline: 1 January 2021
legal deadline: 12 months after publication of Article 7 Guide for OP tracks
RINF index: 1.1.1.3.3.8
RINF index: 1.2.1.1.2.8
SHACL shape validation rule: GsmRNoCoverage
SHACL shape validation rule: GsmRNoCoverageApplicability
created: 2021-08-09
modified: 2021-09-12
modified: 2024-09-19
modified: 2025-03-04
comment: Indication if there is no GSMR coverage
term status: stable
scope note: 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).

GSM-R sets in driving cab
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: integer
ERATV index: 4.13.2.2
created: 2021-08-31
modified: 2021-08-31
comment: Number of GSM-R mobile sets in driving cab for data transmission.
term status: stable

(Deprecated) GSM-R error corrections required for the on-board
type: DatatypeProperty
range: anyURI
created: 2023-03-14
is replaced by: Error corrections required for the on-board ETCS, GSM-R and/or ATO function
modified: 2024-01-08
modified: 2024-04-18
comment: List of unacceptable errors impacting the IM network that are required to be solved in the on-board according to the CCS TSI point 7.2.10.3 specification maintenance point. The reason for deprecation is that this parameter does not appear in the latest legal text.
deprecated: true
term status: stable

GSM-R network is configured to allow forced de-registration of a functional number by another driver
type: DatatypeProperty
sub property of: TSI compliant radio (RMR)
type: FunctionalProperty
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: boolean
applicable: Y/N/NYA
dependency note: GSM-R and ETCS L2 must be installed for this parameter to be applicable.
legal deadline: 12 months after publication of Article 7 Guide
RINF index: 1.1.1.3.3.11
RINF index: 1.2.1.1.2.11
SHACL shape validation rule: GsmrForcedDeregistrationFunctionalNumber
SHACL shape validation rule: GsmrForcedDeregistrationFunctionalNumberApplicability
TSI operation appendix D3 index: 2.1
created: 2022-11-07
modified: 2023-03-14
modified: 2024-04-18
relation: European Train Control System (ETCS) level
source: oj
comment: This feature will determine the applicable operational rules for drivers and signallers when dealing with cab radios registered under wrong numbers.
term status: stable
scope note: See documents regarding Operational Harmonisation ETCS.

handover point flag
type: DatatypeProperty
type: FunctionalProperty
domain: Primary Location
range: boolean
SHACL shape validation rule: HandoverPointFlag
created: 2024-06-03
comment: Handover point flag attached to a Primary location.
term status: stable

Availability by the IM of additional information
type: DatatypeProperty
sub property of: Brake related parameters
type: FunctionalProperty
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: boolean
XML name: CBP_AddInfoAvailable
applicable: Y/N
legal deadline: 16 January 2020
RINF index: 1.1.1.3.11.2
SHACL shape validation rule: HasAdditionalBrakingInformation
used in RCC calculations: true
created: 2020-08-24
modified: 2024-01-08
comment: Availability by the IM of additional information as defined in point (2) of point 4.2.2.6.2 of Regulation (EU) 2023/1693 - TSI OPE
term status: stable
scope note: [See TSI OPE 4.2.2.6.2 (2)]

Has automatic dropping device
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: boolean
ERATV index: 4.10.11
created: 2020-08-25
modified: 2020-11-03
comment: Automatic dropping device (ADD) fitted (to be indicated for each energy supply system the vehicle is equipped for).
term status: stable

Existence of ballast
type: DatatypeProperty
sub property of: Track parameters
type: FunctionalProperty
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: boolean
XML name: ITP_Ballast
applicable: Y/N
dependency note: Mandatory for tracks with permitted speed (parameter 1.1.1.1.2.5) greater than 250km/h
format note: in XML: Y/N
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.1.1.1.4.4
SHACL shape validation rule: HasBallast
SHACL shape validation rule: HasBallastApplicability
created: 2021-08-03
modified: 2021-09-10
modified: 2024-09-19
modified: 2025-02-28
source: http://data.europa.eu/eli/reg/2014/1299/2023-09-28
comment: Specifies whether track construction is with sleepers embedded in ballast or not.
see also: Loc&Pas TSI 4.2.6.2.5 INF TSI : 4.2.10.3
term status: stable
scope note: 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.

Has bridge
type: DatatypeProperty
type: FunctionalProperty
domain: Running track
range: boolean
SHACL shape validation rule: HasBridge
created: 2024-12-10
term status: stable
definition: Whether or not a track is associated with a bridge.

Has cant deficiency compensation
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: boolean
ERATV index: 4.6.2
created: 2021-08-26
modified: 2021-08-26
comment: Vehicle equipped with a cant deficiency compensation system (tilting vehicle).
term status: stable

Has current limitation
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: boolean
ERATV index: 4.10.14
created: 2020-08-24
modified: 2020-11-03
comment: Electric units equipped with power or current limitation function.
term status: stable

Existence of operating restrictions or conditions
type: DatatypeProperty
sub property of: TSI compliant train protection system (ETCS)
type: FunctionalProperty
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: boolean
applicable: Y/N/NYA
dependency note: A value has to be provided when ETCS is present (a value is provided on 1.1.1.3.2.1).
legal deadline: 12 months after publication of Article 7 Guide for OP tracks
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.1.1.3.2.6
RINF index: 1.2.1.1.1.6
SHACL shape validation rule: HasETCSRestrictionsConditions
SHACL shape validation rule: HasETCSRestrictionsConditionsApplicability
created: 2021-08-08
modified: 2024-01-08
modified: 2024-04-18
modified: 2024-11-20
modified: 2025-02-28
relation: European Train Control System (ETCS) level
source: oj
comment: Indication whether restrictions or conditions due to partial compliance with the TSI CCS exist.
term status: stable
scope note: 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.

Existence of electric shore supply
type: DatatypeProperty
sub property of: Fixed installations for servicing trains
type: FunctionalProperty
domain: Class
  union of: Subset with common characteristics
  union of: Siding
range: boolean
XML name: ITS_ElectricShoreSupply
applicable: Y/N
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.2.2.0.4.6
SHACL shape validation rule: HasElectricShoreSupply
created: 2021-08-10
modified: 2021-08-10
modified: 2024-09-19
modified: 2025-03-11
source: http://data.europa.eu/eli/reg/2014/1299/2023-09-28
comment: Indication whether exists an installation of electric shore supply (fixed installation for servicing trains).
term status: stable

Existence of emergency plan
type: DatatypeProperty
sub property of: Tunnel
type: FunctionalProperty
domain: Class
  union of: Subset with common characteristics
  union of: Tunnel
range: boolean
XML name: ITU_EmergencyPlan
applicable: Y/N
dependency note: Mandatory for tunnels longer than 1 km
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.1.1.1.8.9
RINF index: 1.2.1.0.5.6
RINF index: 1.2.2.0.5.6
SHACL shape validation rule: HasEmergencyPlan
SHACL shape validation rule: HasEmergencyPlanApplicability
created: 2021-08-03
modified: 2021-08-10
modified: 2024-09-19
source: http://data.europa.eu/eli/reg/2014/1303/2024-01-29
comment: Indication whether emergency plan exists.
see also: SRT TSI: 4.4.2 OPE TSI: 4.2.3.7
term status: stable
scope note: 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

has ETCS national packet 44 application implemented
type: DatatypeProperty
sub property of: TSI compliant train protection system (ETCS)
type: FunctionalProperty
domain: Class
  union of: Subset with common characteristics
  union of: Track
range: boolean
dependency note: Only applicable when selected value for 1.1.1.3.2.1 (ETCS present).
legal deadline: 12 months after publication of Article 7 Guide
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.1.1.3.2.5
RINF index: 1.2.1.1.1.5
SHACL shape validation rule: HasEtcsNationalPacket44
SHACL shape validation rule: HasEtcsNationalPacket44Applicability
created: 2024-11-20
modified: 2025-05-05
replaces: ETCS national packet 44 application implemented
source: oj
comment: Indication whether data for national packet 44 applications is transmitted between track and train.
term status: stable
scope note: 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 evacuation and rescue points
type: DatatypeProperty
sub property of: Tunnel
type: FunctionalProperty
domain: Class
  union of: Subset with common characteristics
  union of: Tunnel
range: boolean
applicable: Y/N/NYA
dependency note: Mandatory for TSI-compliant tunnels longer than 0.5 km
legal deadline: 12 months after publication of Article 7 Guide
RINF index: 1.1.1.1.8.13
RINF index: 1.2.1.0.5.11
RINF index: 1.2.2.0.5.10
SHACL shape validation rule: HasEvacuationAndRescuePoints
TSI operation appendix D2 index: 3.2.3
created: 2022-10-27
modified: 2023-03-14
modified: 2024-09-19
modified: 2025-02-28
source: oj
comment: Indication of existence of evacuation and rescue points
see also: Point 4.2.1.7. "Evacuation and rescue points" of the Commission Regulation (EU) No 1303/2014 of 18 November 2014 concerning the technical specification for interoperability relating to safety in railway tunnels of the rail system of the European Union|https://eur-lex.europa.eu/legal-content/EN/TXT/?qid=1566396648532&uri=CELEX%3A02014R1303-20190616
term status: stable

Existence of external cleaning facilities
type: DatatypeProperty
sub property of: Fixed installations for servicing trains
type: FunctionalProperty
domain: Class
  union of: Subset with common characteristics
  union of: Siding
range: boolean
XML name: ITS_ExternalCleaning
applicable: Y/N
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.2.2.0.4.2
SHACL shape validation rule: HasExternalCleaning
created: 2021-08-10
modified: 2024-01-08
modified: 2024-09-19
modified: 2025-03-11
source: http://data.europa.eu/eli/reg/2014/1299/2023-09-28
comment: Indication whether exists an installation of external cleaning facility (fixed installation for servicing trains) as defined in TSI INF
term status: stable

Existence of trackside hot axle box detector (HABD)
type: DatatypeProperty
sub property of: Health, safety and environment
type: FunctionalProperty
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: boolean
XML name: IHS_HABDExist
applicable: Y
format note: in XML: Y/N
legal deadline: 16 January 2020
RINF index: 1.1.1.1.7.4
SHACL shape validation rule: HasHotAxleBoxDetector
used in RCC calculations: true
created: 2020-08-24
modified: 2024-01-08
modified: 2025-02-28
comment: Existence of trackside HABD
see also: TSI Loc&Pas: 4.2.10.2.3, 4.2.3.3.2 WAG TSI: 4.2.3.4 EN 15437-1:2009
term status: stable
scope note: 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.

Existence of level crossings
type: DatatypeProperty
sub property of: Health, safety and environment
type: FunctionalProperty
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: boolean
XML name: IHS_LevelCrossing
applicable: Y
format note: in XML: Y/N
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.1.1.1.7.2
SHACL shape validation rule: HasLevelCrossings
created: 2021-08-03
modified: 2021-09-11
modified: 2025-02-28
comment: Indication whether level crossings (including pedestrian track crossing) exist on the section of line.
term status: stable
scope note: 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.

Has lubrication device prevention
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: boolean
ERATV index: 4.9.3.2
created: 2021-08-31
modified: 2021-08-31
comment: Possibility of preventing the use of the lubrication device (only if fitted with flange lubrication).
term status: stable

Existence of other train protection, control and warning systems installed
type: DatatypeProperty
range: boolean
RINF index: 1.1.1.3.5.1
created: 2021-08-09
modified: 2023-03-14
comment: Deprecated according to the amendment to the Regulation (EU) 2019/777. Indication if other train protection, control and warning systems in normal operation are installed lineside.
deprecated: true
term status: unstable

Has parking brake
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: boolean
ERATV index: 4.7.3.4
created: 2021-08-26
modified: 2021-08-26
comment: Indicates if a vehicle type has parking brake.
term status: stable

Phase separation
type: DatatypeProperty
sub property of: OCL separation sections
type: FunctionalProperty
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: boolean
XML name: EOS_Phase
applicable: Y/N
dependency note: 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)
format note: in XML: Y/N
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.1.1.2.4.1.1
SHACL shape validation rule: HasPhaseSeparation
SHACL shape validation rule: HasPhaseSeparationApplicability
created: 2021-08-08
modified: 2021-09-12
relation: Type of contact line system
comment: Indication of existence of phase separation and required information.
term status: stable
scope note: In case of existence of phase separation on the track or on the section of the line the option True shall be selected.

Curvature of the platform
type: DatatypeProperty
sub property of: Platform
domain: Class
  union of: Subset with common characteristics
  union of: Platform edge
range: boolean
applicable: Y/N/NYA
legal deadline: 12 months after publication of Article 7 Guide
RINF index: 1.2.1.0.6.8
SHACL shape validation rule: HasPlatformCurvature
TSI operation appendix D2 index: 2.3.8
created: 2022-10-27
modified: 2023-03-14
modified: 2025-03-11
source: oj
comment: Indication of the existence of the curvature of the platform.
term status: stable

Existence of refuelling
type: DatatypeProperty
sub property of: Fixed installations for servicing trains
type: FunctionalProperty
domain: Class
  union of: Subset with common characteristics
  union of: Siding
range: boolean
XML name: ITS_Refuelling
applicable: Y/N
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.2.2.0.4.4
SHACL shape validation rule: HasRefuelling
created: 2021-08-10
modified: 2024-01-08
modified: 2024-09-19
modified: 2025-03-11
source: http://data.europa.eu/eli/reg/2014/1299/2023-09-28
comment: Indication whether exists an installation of refuelling (fixed installation for servicing trains) as defined in TSI INF.
term status: stable

Permission for regenerative braking
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: boolean
ERATV index: 4.7.4.3.1
created: 2020-08-24
modified: 2021-08-06
comment: Indication whether regenerative braking is permitted or not.
term status: stable

Existence of sand restocking
type: DatatypeProperty
sub property of: Fixed installations for servicing trains
type: FunctionalProperty
domain: Class
  union of: Subset with common characteristics
  union of: Siding
range: boolean
XML name: ITS_SandRestocking
applicable: Y/N
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.2.2.0.4.5
SHACL shape validation rule: HasSandRestocking
created: 2021-08-10
modified: 2021-08-10
modified: 2025-03-11
comment: Indication whether an installation of sand restocking exists (fixed installation for servicing trains).
term status: stable

Has sanding prevention
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: boolean
ERATV index: 4.14.2.12
created: 2021-09-01
modified: 2021-09-01
comment: Possibility of preventing the use of sanding.
term status: stable

Schematic overview of the operational point in digital form
type: DatatypeProperty
sub property of: Operational point generic information
domain: Operational Point
range: boolean
applicable: Y/N/NYA
legal deadline: 12 months after publication of Article 7 Guide
RINF index: 1.2.0.0.0.7
SHACL shape validation rule: HasSchematicOverviewOPDigitalForm
TSI operation appendix D2 index: 2.1
created: 2023-03-14
modified: 2024-01-08
modified: 2025-03-11
comment: The existence of a schematic overview of the operational point in digital form.
term status: stable

Existence of severe climatic conditions
type: DatatypeProperty
sub property of: Performance parameter
type: FunctionalProperty
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: boolean
XML name: IPP_SevereClimateCon
applicable: Y/N
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.1.1.1.2.8
SHACL shape validation rule: HasSevereWeatherConditions
used in RCC calculations: true
created: 2020-08-24
modified: 2021-09-10
modified: 2024-09-19
source: http://data.europa.eu/eli/reg/2014/1302/2023-09-28
comment: Climatic conditions on the line are severe according to European standard.
see also: EN 50125-1 (2014): 4.7 LOC&PAS TSI:4.2.6.1.2
term status: stable
scope note: 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.).

Has shunting restrictions
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: boolean
ERATV index: 4.8.3
created: 2021-08-31
modified: 2021-08-31
comment: Indicates the presence of shunting restrictions.
term status: stable

System separation
type: DatatypeProperty
sub property of: OCL separation sections
type: FunctionalProperty
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: boolean
XML name: EOS_System
applicable: Y/N
dependency note: It is applicable ( Y ) only if the value Overhead contact line (OCL) is selected for parameter "Type of contact line system"
format note: Y/N
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.1.1.2.4.2.1
SHACL shape validation rule: HasSystemSeparation
SHACL shape validation rule: HasSystemSeparationApplicability
created: 2021-08-08
modified: 2021-09-12
comment: Indication of existence of system separation
term status: stable
scope note: 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.

Existence of train detection system fully compliant with the TSI
type: DatatypeProperty
sub property of: Train detection systems defined based on frequency bands
type: FunctionalProperty
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: boolean
applicable: Y/N/NYA
legal deadline: 12 months after publication of Article 7 Guide for OP tracks
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.1.1.3.4.1
RINF index: 1.2.1.1.3.1
SHACL shape validation rule: HasTSITrainDetection
created: 2021-08-09
modified: 2024-01-08
relation: Type of train detection system
source: oj
comment: Indication if there is any train detection system installed and fully compliant with the TSI CCS
term status: stable
scope note: Verification of compliance with TSI includes application of notified national rules (when they exist). See: (Annex I, Appendix A, Table A.2 -Index 77).

Existence of toilet discharge
type: DatatypeProperty
sub property of: Fixed installations for servicing trains
type: FunctionalProperty
domain: Class
  union of: Subset with common characteristics
  union of: Siding
range: boolean
XML name: ITS_ToiletDischarge
applicable: Y/N
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.2.2.0.4.1
SHACL shape validation rule: HasToiletDischarge
created: 2021-08-10
modified: 2024-01-08
modified: 2024-09-19
modified: 2025-03-11
source: http://data.europa.eu/eli/reg/2014/1299/2023-09-28
comment: Indication whether exists an installation of toilet discharge (fixed installation for servicing trains) as defined in TSI INF
term status: stable

Has train integrity confirmation
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: boolean
ERATV index: 4.13.1.9
created: 2020-08-31
modified: 2021-09-12
comment: Indication of on-board management system about completeness of the train information.
term status: stable

Existence of walkways
type: DatatypeProperty
sub property of: Tunnel
type: FunctionalProperty
domain: Class
  union of: Subset with common characteristics
  union of: Tunnel
range: boolean
applicable: Y/NYA
dependency note: Mandatory for TSI-compliant tunnels longer than 0.5 km
format note: [Y/N] If =Y then TSI-Compliant OR NON-TSI-Compliant
legal deadline: 12 months after publication of Article 7 Guide
RINF index: 1.1.1.1.8.12
RINF index: 1.2.1.0.5.10
RINF index: 1.2.2.0.5.9
SHACL shape validation rule: HasWalkway
TSI operation appendix D2 index: 3.2.3
created: 2022-10-27
modified: 2023-03-14
modified: 2024-09-19
modified: 2025-02-28
source: oj
comment: Indication of existence of walkways
see also: Point 4.2.1.6. "Escape walkways" of the Commission Regulation (EU) No 1303/2014 of 18 November 2014 concerning the technical specification for interoperability relating to safety in railway tunnels of the rail system of the European Union|https://eur-lex.europa.eu/legal-content/EN/TXT/?qid=1566396648532&uri=CELEX%3A02014R1303-20190616
term status: stable
alternative label: Existence of walkways in tunnel
scope note: 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 water restocking
type: DatatypeProperty
sub property of: Fixed installations for servicing trains
type: FunctionalProperty
domain: Class
  union of: Subset with common characteristics
  union of: Siding
range: boolean
XML name: ITS_WaterRestocking
applicable: Y/N
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.2.2.0.4.3
SHACL shape validation rule: HasWaterRestocking
created: 2021-08-10
modified: 2024-01-08
modified: 2024-09-19
modified: 2025-03-11
source: http://data.europa.eu/eli/reg/2014/1299/2023-09-28
comment: Indication whether exists an installation of water restocking (fixed installation for servicing trains) as defined in TSI INF
term status: stable

Has wheel slide protection system
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: boolean
ERATV index: 4.7.8
created: 2021-08-31
modified: 2021-08-31
comment: Indicates the presence of a wheel slide protection system.
term status: stable

Health, safety and environment
type: DatatypeProperty
sub property of: Infrastructure subsystem
RINF index: 1.1.1.1.7
created: 2024-10-31

Compliance of structures with the High Speed Load Model (HSLM)
type: DatatypeProperty
sub property of: Performance parameter
type: FunctionalProperty
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: boolean
XML name: IPP_HSLMCompliant
applicable: Y/N
legal deadline: 16 January 2020
RINF index: 1.1.1.1.2.4.2
SHACL shape validation rule: HighSpeedLoadModelCompliance
used in RCC calculations: true
created: 2020-08-24
modified: 2024-01-08
modified: 2024-09-19
source: tocId3
source: tocId30
comment: For sections of line with a maximum permitted speed of 200 km/h or more. Information regarding the procedure to be used to perform the dynamic compatibility check.
see also: Annex D1 OPE TSI INF TSI: 4.2.7.1.2(2)
term status: stable
scope note: (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.

Generation of trackside HABD
type: DatatypeProperty
sub property of: Health, safety and environment
type: FunctionalProperty
domain: Hot Axle Box Detector
range: string
XML name: IHS_HABDGen
applicable: Y/N
dependency note: Mandatory if the HABD is not TSI compliant (the value of parameter 1.1.1.1.7.5 (Trackside HABD TSI compliant) is 'False')
legal deadline: 16 January 2020
RINF index: 1.1.1.1.7.7
SHACL shape validation rule: HotAxleBoxDetectorGeneration
SHACL shape validation rule: HotAxleBoxDetectorGenerationApplicability
SHACL shape validation rule: HotAxleBoxDetectorGenerationCountryApplicability
used in RCC calculations: true
created: 2020-08-24
modified: 2021-09-11
modified: 2025-02-28
comment: Specific for the French Italian and Swedish networks. Generation of trackside hot axle box detector.
term status: stable
scope note: Waiting provision of possible answers by the French, Italian and Swedish NREs

Identification of trackside HABD
type: DatatypeProperty
sub property of: Health, safety and environment
sub property of: Identifier
type: FunctionalProperty
domain: Hot Axle Box Detector
range: string
XML name: IHS_HABDID
applicable: Y/N
dependency note: Mandatory if the HABD is not TSI compliant (the value of parameter 1.1.1.1.7.5 (Trackside HABD TSI compliant) is 'False')
legal deadline: 16 January 2020
RINF index: 1.1.1.1.7.6
SHACL shape validation rule: HotAxleBoxDetectorIdentification
SHACL shape validation rule: HotAxleBoxDetectorIdentificationApplicability
SHACL shape validation rule: HotAxleBoxDetectorIdentificationCountryApplicability
used in RCC calculations: true
created: 2020-08-24
modified: 2021-09-11
modified: 2025-02-28
modified: 2025-09-03
comment: Specific for the French, Italian and Swedish networks. Applicable if trackside HABD is not TSI compliant, identification of trackside hot axle box detector.
term status: stable

Railway location of trackside HABD
type: DatatypeProperty
sub property of: Health, safety and environment
domain: Hot Axle Box Detector
range: double
XML name: IHS_HABDLoc
applicable: Y/N
dependency note: Mandatory if the HABD is not TSI compliant (the value of parameter 1.1.1.1.7.5 (Trackside HABD TSI compliant) is 'False')
legal deadline: 16 January 2020
RINF index: 1.1.1.1.7.8
SHACL shape validation rule: HotAxleBoxDetectorLocation
SHACL shape validation rule: HotAxleBoxDetectorLocationApplicability
SHACL shape validation rule: HotAxleBoxDetectorLocationCountryApplicability
used in RCC calculations: true
created: 2020-08-24
modified: 2021-09-11
modified: 2025-02-28
comment: Specific for the French Italian and Swedish networks. Applicable if trackside HABD is not TSI compliant, localisation of trackside hot axle box detector.
term status: stable
scope note: 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

Trackside HABD TSI compliant
type: DatatypeProperty
sub property of: Health, safety and environment
type: FunctionalProperty
domain: Hot Axle Box Detector
range: boolean
XML name: IHS_TSIHABD
applicable: Y
legal deadline: 16 January 2020
RINF index: 1.1.1.1.7.5
SHACL shape validation rule: HotAxleBoxDetectorTSICompliant
SHACL shape validation rule: HotAxleBoxDetectorTSICompliantCountryApplicability
used in RCC calculations: true
created: 2020-08-24
modified: 2021-09-11
comment: Specific for the French, Italian and Swedish networks. Trackside HABD compliant to TSI means that the HABD Trackside is compliant with: - EN 15437-1:2009 referred in TSIs (LOC&PAS: 4.2.3.3.2.2, WAG TSI: 4.2.3.4), - Specific cases mentioned in TSIs (LOC&PAS TSI, WAG TSI).
see also: TSI LOC&PAS: 4.2.3.3.2.2, and 7.3.2.3 WAG TSI: 4.2.3.4 and 7.3.2.2 EN 15437-1:2009
term status: stable

(deprecated) ID and phone number of ERTMS/ETCS Radio Block Center
type: DatatypeProperty
range: string
applicable: Y/N/NYA
dependency note: A value has to be provided when ETCS is present (a value is provided on 1.1.1.3.2.1).
legal deadline: 12 months after publication of Article 7 Guide
RINF index: 1.1.1.3.2.17
RINF index: 1.2.1.1.1.17
TSI operation appendix D2 index: 3.4.7
created: 2023-03-14
is replaced by: ID of ERTMS/ETCS Radio Block Center
is replaced by: Phone number of ERTMS/ETCS Radio Block Center
modified: 2024-04-18
modified: 2024-12-05
relation: European Train Control System (ETCS) level
source: oj
comment: Unique RBC identification (NID_C+NID_RBC) and calling number (NID_RADIO) as defined in the specification referenced in Appendix A-1, index [C].
deprecated: true
term status: stable
scope note: Non-harmonizable character string: [Contents of P42, not P143]

Infrastructure manager (IM)'s code
type: DatatypeProperty
sub property of: Identifier
type: FunctionalProperty
domain: Organisation Role
range: string
created: 2021-08-02
is replaced by: organisation code
modified: 2024-01-08
modified: 2024-06-03
modified: 2024-09-19
modified: 2024-10-30
modified: 2024-11-12
source: http://data.europa.eu/eli/dec_impl/2018/1614
source: oj
comment: Infrastructure manager means any body or firm responsible in particular for establishing, managing and maintaining railway infrastructure, including traffic management and control-command 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))
deprecated: true
term status: stable

Infrastructure subsystem
type: DatatypeProperty
sub property of: RINF Technical characteristic
RINF index: 1.1.1.1
created: 2024-10-31

Declarations of verification for track
type: DatatypeProperty
sub property of: Infrastructure subsystem
RINF index: 1.1.1.1.1
created: 2024-10-31

is on origin of element A
type: DatatypeProperty
domain: Net Relation
range: boolean
RINF index: 1.1.1.0.1.2
RINF index: 1.2.4.1
SHACL shape validation rule: IsOnOriginOfElementA
created: 2021-04-03
created: 2024-11-29
modified: 2021-08-03
modified: 2024-11-29
comment: Determines if the position of the topological element A in a relation is the origin of element A.
term status: stable
alternative label: Internal connection

is on origin of element B
type: DatatypeProperty
domain: Net Relation
range: boolean
RINF index: 1.1.1.0.1.2
RINF index: 1.2.4.1
SHACL shape validation rule: IsOnOriginOfElementB
created: 2021-04-03
created: 2024-11-29
modified: 2021-08-03
modified: 2024-11-29
comment: Determines if the position of the topological element B in a relation is the origin of element B.
term status: stable
alternative label: Internal connection

Belonging to a quieter route
type: DatatypeProperty
sub property of: Health, safety and environment
type: FunctionalProperty
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: boolean
XML name: IHS_QuietRoute
applicable: Y
format note: in XML: Y/N
legal deadline: 1 January 2021
RINF index: 1.1.1.1.7.11
SHACL shape validation rule: IsQuietRoute
created: 2020-11-04
modified: 2024-01-08
modified: 2025-02-28
comment: Belonging to a 'quieter route' in accordance with Article 5b of TSI NOI.
see also: Art 5b of Regulation (EU) 1304/2014 (amended by Regulation (EU) 2019/774) of 16 May 2019
term status: stable
scope note: 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.

kilometer number
type: DatatypeProperty
sub property of: Signal
sub property of: Tunnel
domain: Kilometric Post
range: double
XML name: OPRailwayLocation
applicable: Y/N
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.2.0.0.0.6
SHACL shape validation rule: Kilometer
TSI operation appendix D2 index: 2.2.2
Unit of measure: KiloM
created: 2021-01-29
modified: 2021-01-29
modified: 2024-09-19
modified: 2024-10-24
modified: 2025-01-30
source: oj
comment: Kilometer number of the kilometric post related to line identification defining the location of an infrastructure element.
term status: stable
alternative label: Railway location of Operational point
scope note: 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] ).

kilometric post name
type: DatatypeProperty
domain: Kilometric Post
range: string
SHACL shape validation rule: KmPostName
created: 2024-05-24
modified: 2024-10-24
modified: 2024-11-29
modified: 2025-03-10
comment: Name of the kilometric post (optional).
term status: stable
alternative label: mileage post

Length
type: DatatypeProperty
Unit of measure: http://qudt.org/vocab/unit/M
used in RCC calculations: true
created: 2021-04-01
modified: 2024-01-08
modified: 2024-11-04
comment: Generic super-property for different types of length
term status: stable
scope note: Position of the start of the walkway: [integer] m (from the same origin point of the kilometer post.) Lenght of the walkway: [integer] m
scope note: 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.

length of net linear element
type: DatatypeProperty
sub property of: Length
type: FunctionalProperty
domain: Linear Element
range: double
SHACL shape validation rule: LengthOfNetLinearElement
Unit of measure: http://qudt.org/vocab/unit/M
created: 2024-11-29
comment: Length of a topological linear element.

Usable length of platform
type: DatatypeProperty
sub property of: Length
sub property of: Platform
type: FunctionalProperty
domain: Platform edge
range: double
XML name: IPL_Length
applicable: Y/N
format note: NNNN
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.2.1.0.6.4
SHACL shape validation rule: LengthP
TSI operation appendix D2 index: 2.3.6
TSI operation appendix D2 index: 3.2.3
Unit of measure: http://qudt.org/vocab/unit/M
used in RCC calculations: true
created: 2024-05-16
modified: 2024-09-19
modified: 2025-03-11
source: http://data.europa.eu/eli/reg/2014/1299/2023-09-28
source: oj
comment: The maximum continuous length (expressed in metres) of that part of platform in front of which a train is intended to remain stationary in normal operating conditions for passengers to board and alight from the train, making appropriate allowance for stopping tolerances.
see also: INF TSI: 4.2.1, 4.2.9.1 OPE TSI: 4.2.2.5.2, 4.2.2.7.2
term status: stable
scope note: Platform dimensions are always related to one neighbouring track at a time. So, if two tracks are along a platform, this platform should be divided into two RINF platforms to have precise description of each.

Length of section of line
type: DatatypeProperty
sub property of: Length
sub property of: Section of line generic information
type: FunctionalProperty
domain: Section Of Line
range: double
XML name: SOLLength
applicable: Y
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.1.0.0.0.5
SHACL shape validation rule: SolLength
TSI operation appendix D2 index: 3.2.3
Unit of measure: KiloM
used in RCC calculations: true
created: 2024-05-16
modified: 2025-03-11
comment: Length between operational points at start and end of section of line.
term status: stable

Usable length of siding
type: DatatypeProperty
sub property of: Length
sub property of: Siding
type: FunctionalProperty
domain: Siding
range: double
XML name: IPP_Length
applicable: Y/N
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.2.2.0.2.1
SHACL shape validation rule: LengthS
TSI operation appendix D2 index: 3.2.3
Unit of measure: http://qudt.org/vocab/unit/M
used in RCC calculations: true
created: 2024-05-16
modified: 2025-03-11
source: oj
comment: Total length of the siding/stabling track expressed in metres where trains can be parked safely.
term status: stable

Length of tunnel
type: DatatypeProperty
sub property of: Length
sub property of: Tunnel
type: FunctionalProperty
domain: Tunnel
range: double
XML name: ITU_Length
applicable: Y
dependency note: Only applicable for a tunnel with length of 100 metres or more.
format note: NNNNN
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.1.1.1.8.7
RINF index: 1.2.1.0.5.5
RINF index: 1.2.2.0.5.5
SHACL shape validation rule: LengthOfTunnel
TSI operation appendix D2 index: 3.2.3
Unit of measure: http://qudt.org/vocab/unit/M
used in RCC calculations: true
created: 2024-05-16
modified: 2024-09-19
modified: 2025-03-08
source: oj
comment: Length of a tunnel in metres from entrance portal to exit portal.
term status: stable
scope note: Length of a tunnel is expressed in metres from portal to portal at the level of the top of rail.

Vehicle length
type: DatatypeProperty
sub property of: Length
type: FunctionalProperty
domain: Vehicle
range: double
ERATV index: 4.8.1
Unit of measure: http://qudt.org/vocab/unit/M
created: 2024-11-04

Letter marking
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: string
ERATV index: 4.1.7
created: 2021-08-25
modified: 2021-08-25
comment: letter marking
term status: stable

line identifier
type: DatatypeProperty
sub property of: Identifier
type: FunctionalProperty
domain: Linear Positioning System
range: string
XML name: SOLLineIdentification
applicable: Y
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.1.0.0.0.2
SHACL shape validation rule: LineId
TSI operation appendix D2 index: 2.2.1.1
modified: 2024-11-18
modified: 2025-09-03
comment: Unique line identification or unique line number within Member State.

Line layout
type: DatatypeProperty
sub property of: Infrastructure subsystem
RINF index: 1.1.1.1.3
RINF index: 1.2.1.0.3
created: 2024-10-31

Linear coordinate
type: DatatypeProperty
range: double
created: 2021-04-01
modified: 2023-11-10
comment: Indicates the position of an object within a linear positioning system. For example, relative to a national railway line
deprecated: true
term status: stable
editorial note: The reason for deprecation is that this property is not specified in the latest legal text nor the RINF application guide. Also, no data has been provided for this property.

Lineside distance indication frequency
type: DatatypeProperty
domain: Lineside indications of distance
range: integer
SHACL shape validation rule: LinesideDistanceIndicationFrequency
Unit of measure: http://qudt.org/vocab/unit/M
created: 2022-10-27
modified: 2023-03-14
source: oj
comment: Frequency of track lineside distance indications.
term status: stable

Load capability speed
type: DatatypeProperty
type: FunctionalProperty
domain: Load capability
range: integer
SHACL shape validation rule: LoadCapabilitySpeed
Unit of measure: KiloM-PER-HR
created: 2023-01-20
modified: 2025-02-18
modified: 2025-03-11
replaces: Load Capability
source: http://data.europa.eu/eli/reg/2014/1299/2023-09-28
comment: Part of the load capability of a track that corresponds to the speed of the load model
term status: stable

Loading platform height
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: integer
ERATV index: 4.8.7
created: 2021-08-31
modified: 2021-08-31
comment: Height of loading platform (for flat wagons and combined transport), given in mm.
term status: stable

Existence of rules and restrictions of a strictly local nature
type: DatatypeProperty
sub property of: Rules and restrictions
type: FunctionalProperty
domain: Class
  union of: Subset with common characteristics
  union of: Operational Point
  union of: Running track
range: boolean
XML name: RUL_LocalRulesOrRestrictions
applicable: Y/N
format note: Y/N
legal deadline: 1 January 2021
RINF index: 1.1.1.4.1
RINF index: 1.2.3.1
SHACL shape validation rule: LocalRulesOrRestrictions
created: 2021-08-09
modified: 2021-09-12
modified: 2025-03-11
comment: Existence of rules and restrictions of a strictly local nature
term status: stable
scope note: 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'

M_NVDERUN
type: DatatypeProperty
sub property of: ETCS National Values
type: FunctionalProperty
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: boolean
applicable: Y/N/NYA
dependency note: A value has to be provided when ETCS is present (a value is provided on 1.1.1.3.2.1).
legal deadline: 12 months after publication of Article 7 Guide
RINF index: 1.1.1.3.2.16.10
RINF index: 1.2.1.1.1.16.10
SHACL shape validation rule: MNvderun
SHACL shape validation rule: MNvderunApplicability
TSI operation appendix D3 index: 1.5.10
created: 2022-11-07
modified: 2023-03-14
modified: 2023-04-18
relation: European Train Control System (ETCS) level
source: oj
comment: Entry of Driver ID permitted while running According to the specification referenced in Appendix A-1, index [C]
term status: stable
scope note: See: TSI CCS (Subset 26, chapter 7. 7.5.1.75 M_NVDERUN)

Magnetic brake prevention
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: boolean
ERATV index: 4.7.4.2.2
created: 2020-08-24
modified: 2021-04-13
comment: Possibility of preventing the use of the magnetic track brake (only if fitted with magnetic brake)
term status: stable

Magnetic braking fitted
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: boolean
ERATV index: 4.7.4.2.1
created: 2022-09-12
comment: Magnetic track brake fitted. New property defined to distinguish it from magneticBraking which is a RINF SKOS property.
term status: stable

Mass per wheel
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: integer
ERATV index: 4.5.6
created: 2021-08-26
modified: 2021-08-26
comment: Mass per wheel, given in kg.
term status: stable

Maximum current at standstill per pantograph
type: DatatypeProperty
sub property of: Contact line system
sub property of: Vehicle type technical characteristic
type: FunctionalProperty
domain: Class
  union of: Contact Line System
  union of: Siding
  union of: Vehicle Type
range: integer
XML name: ECS_MaxStandstillCurrent
applicable: Y/N
dependency note: 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.
ERATV index: 4.10.4
format note: NNN
legal 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
RINF index: 1.1.1.2.2.3
RINF index: 1.2.2.0.6.1
SHACL shape validation rule: MaxCurrentStandstillPantograph
SHACL shape validation rule: MaxCurrentStandstillPantographApplicability
SHACL shape validation rule: MaxCurrentStandstillPantographS
TSI operation appendix D2 index: 3.3.8
Unit of measure: http://qudt.org/vocab/unit/A
used in RCC calculations: true
created: 2020-08-25
modified: 2021-09-12
modified: 2024-05-16
modified: 2024-09-25
modified: 2025-02-28
relation: Type of contact line system
source: oj
comment: Indication of the maximum allowable train current at standstill expressed in amperes.
see also: ENE TSI: 4.2.5, LOC&PAS TSI: 4.2.8.2.5
term status: stable
scope note: 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

Maximum permitted distance between two consecutive axles in case of TSI non-compliance
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: integer
XML name: CTD_MaxDistConsecutiveAxles
ERATV index: 4.14.2.1
Unit of measure: MilliM
created: 2021-08-08
modified: 2023-03-14
comment: Deprecated according to the amendment to the Regulation (EU) 2019/777. However, the parameter remains as it is also an ERATV parameter. Indication of maximum permitted distance between two consecutive axles in case of TSI non-compliance, given in millimetres.
term status: stable

Maximum distance between end of train and first axle
type: DatatypeProperty
domain: Train Detection System
range: integer
XML name: CTD_MaxDistEndTrainFirstAxle
RINF index: 1.1.1.3.7.5
Unit of measure: MilliM
created: 2021-08-08
modified: 2023-03-14
comment: Deprecated according to the amendment to the Regulation (EU) 2019/777. Indication of maximum distance between end of train and first axle, given in millimetres, applicable for both sides (front and rear) of a vehicle or train.
deprecated: true
term status: stable

Maximum permitted height of the flange
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: double
XML name: CTD_MaxFlangeHeight
ERATV index: 4.14.2.9
Unit of measure: MilliM
created: 2021-08-08
modified: 2023-03-14
comment: Deprecated according to the amendment to the Regulation (EU) 2019/777. However, the parameter remains as it is also an ERATV parameter. Maximum permitted flange height, given in millimetres.
term status: stable

Maximum permitted impedance between opposite wheels of a wheelset when not TSI compliant
type: DatatypeProperty
domain: Class
  union of: Train Detection System
  union of: Vehicle Type
range: double
XML name: CTD_MaxImpedanceWheelset
ERATV index: 4.14.2.16
RINF index: 1.1.1.3.7.15.2
created: 2021-08-08
modified: 2023-03-14
comment: The value of maximum permitted impedance given in ohm in case of TSI non-compliance. Deprecated according to the amendment to the Regulation (EU) 2019/777.
deprecated: true
term status: stable

Maximum length vehicle nose
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: integer
ERATV index: 4.14.2.4
created: 2021-09-01
modified: 2021-09-01
comment: Maximum length of the vehicle nose.
term status: stable

Maximum train current
type: DatatypeProperty
sub property of: Contact line system
type: FunctionalProperty
domain: Contact Line System
range: integer
XML name: ECS_MaxTrainCurrent
applicable: Y/N
dependency note: When `not electrified` is chosen in parameter 1.1.1.2.2.1.1, then this parameter is not applicable.
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.1.1.2.2.2
SHACL shape validation rule: MaximumTrainCurrent
TSI operation appendix D2 index: 3.3.2
Unit of measure: http://qudt.org/vocab/unit/A
created: 2021-08-06
modified: 2021-08-06
modified: 2024-05-16
modified: 2024-09-25
modified: 2025-02-28
relation: Type of contact line system
comment: Indication of the maximum allowable train current expressed in amperes.
term status: stable
scope note: 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 altitude
type: DatatypeProperty
sub property of: Performance parameter
type: FunctionalProperty
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: double
XML name: IPP_MaxAltitude
applicable: Y/N
format note: [+/-][NNNN]
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.1.1.1.2.7
SHACL shape validation rule: MaximumAltitude
Unit of measure: http://qudt.org/vocab/unit/M
created: 2021-08-03
modified: 2022-10-20
modified: 2024-09-19
comment: Highest point of the section of line above sea level in reference to Normal Amsterdam's Peil (NAP).
term status: stable
scope note: 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.

Maximum average deceleration
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: double
ERATV index: 4.7.1
Unit of measure: M-PER-SEC2
created: 2021-08-26
modified: 2021-08-26
modified: 2024-06-26
comment: Maximum train deceleration given in m/s².
term status: stable

Maximum brake thermal energy capacity
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: integer
ERATV index: 4.7.2.1.6
Unit of measure: KiloJ
created: 2021-08-26
modified: 2021-08-26
modified: 2024-06-26
comment: Maximum brake thermal energy capacity given in kJ
term status: stable

Maximum braking distance requested
type: DatatypeProperty
sub property of: Brake related parameters
type: FunctionalProperty
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: integer
XML name: CBP_MaxBrakeDist
applicable: Y/N
format note: NNNNN
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.1.1.3.11.1
SHACL shape validation rule: MaximumBrakingDistance
Unit of measure: http://qudt.org/vocab/unit/M
used in RCC calculations: true
created: 2020-08-24
modified: 2021-09-12
modified: 2024-06-26
modified: 2024-09-19
source: oj
comment: The maximum value of the braking distance [in metres] of a train shall be given for the maximum line speed.
term status: stable
scope note: 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

Maximum contact wire height
type: DatatypeProperty
sub property of: Contact line system
sub property of: Vehicle type technical characteristic
type: FunctionalProperty
domain: Class
  union of: Contact Line System
  union of: Siding
  union of: Vehicle Type
range: double
XML name: ECS_MaxWireHeight
applicable: Y/N
dependency note: Mandatory only if “Overhead contact line (OCL)” is selected in 1.1.1.2.2.1.1, otherwise the parameter is not applicable.
ERATV index: 4.10.5
format note: N.NN
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.1.1.2.2.5
SHACL shape validation rule: MaximumContactWireHeight
SHACL shape validation rule: MaximumContactWireHeightApplicability
Unit of measure: http://qudt.org/vocab/unit/M
used in RCC calculations: true
created: 2020-08-25
modified: 2021-09-11
modified: 2024-09-25
modified: 2025-02-28
relation: Type of contact line system
comment: Indication of the maximum contact wire height expressed in metres.
term status: stable
scope note: The value given can be design value or the last known measured value. If there is no change in height, nominal value will be given. Values shall be given in metres with precision of 0.01 m.

Maximum design speed
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: integer
ERATV index: 4.1.2.1
Unit of measure: KiloM-PER-HR
created: 2020-08-24
modified: 2020-11-03
modified: 2024-06-26
comment: Maximum design speed.
term status: stable

Maximum interference current
type: DatatypeProperty
sub property of: Train detection systems defined based on frequency bands
type: FunctionalProperty
domain: Train Detection System
range: double
applicable: Y/N/NYA
dependency note: Evaluation parameters must be added if preferred bands are not used.
format note: NNN. An optional value could be filled in era:maximumInterferenceCurrentEvaluation
legal 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
RINF index: 1.1.1.3.4.2.1
RINF index: 1.2.1.1.3.2.1
SHACL shape validation rule: MaximumInterferenceCurrent
Unit of measure: A-PER-M
used in RCC calculations: true
created: 2023-03-14
modified: 2024-04-18
modified: 2025-02-28
relation: Evaluation parameters if maximum interference current is not measured in the preferred bands
relation: Type of train detection system
source: oj
comment: Maximum interference current limits allowed for track circuits for a defined frequency band.
term status: stable
scope note: 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.

Evaluation parameters if maximum interference current is not measured in the preferred bands
type: DatatypeProperty
sub property of: Train detection systems defined based on frequency bands
type: FunctionalProperty
domain: Train Detection System
range: string
dependency note: 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.
legal deadline: 12 months after publication of Article 7 Guide
legal 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
RINF index: 1.1.1.3.4.2.1
RINF index: 1.2.1.1.3.2.1
SHACL shape validation rule: MaximumInterferenceCurrentEvaluation
used in RCC calculations: true
created: 2024-04-18
relation: Maximum interference current
relation: Type of train detection system
source: oj
comment: Maximum interference current limits allowed for track circuits for a defined frequency band.
term status: stable

Maximum locomotives coupled
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: integer
ERATV index: 4.1.5
created: 2021-08-25
modified: 2021-08-25
comment: Maximum number of trainsets or locomotives coupled together in multiple operation.
term status: stable

Maximum magnetic field direction X
type: DatatypeProperty
type: FunctionalProperty
domain: Maximum magnetic field
range: integer
SHACL shape validation rule: MaximumMagneticFieldDirectionX
created: 2023-03-14
modified: 2024-09-19
relation: Type of train detection system
comment: The maximum magnetic field limits allowed for axle counters (in dB µA/m) for a defined frequency band. Direction X.
term status: stable
scope note: The maximumMagneticFieldDirectionX parameter is only applicable for axle counters.

Maximum magnetic field direction Y
type: DatatypeProperty
type: FunctionalProperty
domain: Maximum magnetic field
range: integer
SHACL shape validation rule: MaximumMagneticFieldDirectionY
created: 2023-03-14
modified: 2024-09-19
relation: Type of train detection system
comment: The maximum magnetic field limits allowed for axle counters (in dB µA/m) for a defined frequency band. Direction Y.
term status: stable
scope note: The maximumMagneticFieldDirectionY parameter is only applicable for axle counters.

Maximum magnetic field direction Z
type: DatatypeProperty
domain: Maximum magnetic field
range: integer
SHACL shape validation rule: MaximumMagneticFieldDirectionZ
created: 2023-03-14
modified: 2024-09-19
relation: Type of train detection system
comment: The maximum magnetic field limits allowed for axle counters (in dB µA/m) for a defined frequency band. Direction Z.
term status: stable
scope note: The maximumMagneticFieldDirectionZ parameter is applicable for axle counters.

Maximum permitted speed
type: DatatypeProperty
sub property of: Performance parameter
type: FunctionalProperty
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: integer
XML name: IPP_MaxSpeed
applicable: Y/N
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.1.1.1.2.5
SHACL shape validation rule: MaximumPermittedSpeed
TSI operation appendix D2 index: 3.1.4
Unit of measure: KiloM-PER-HR
used in RCC calculations: true
created: 2020-08-24
modified: 2023-03-14
modified: 2024-09-19
modified: 2025-02-26
comment: Nominal maximum operational speed on the line as a result of infrastructure, energy and control, command signalling subsystem characteristics expressed in kilometres/hour.
see also: INF TSI, ENE TSI, CCS TSI
term status: stable
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.
scope note: "Speed on the line" shall be understood as speed on the track of the section of line in question.

Maximum service break
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: string
ERATV index: 4.7.7
created: 2021-08-26
modified: 2021-08-26
comment: At maximum service brake: Stopping distance, Maximum deceleration, for the load condition 'design mass under normal payload' at the design maximum speed.
term status: stable

Maximum speed and cant deficiency
type: DatatypeProperty
domain: Vehicle Type
range: string
ERATV index: 4.6.4
created: 2020-08-24
is replaced by: Maximum speed and cant deficiency
is replaced by: Vehicle type maximum cant deficiency
is replaced by: Vehicle type maximum speed
is replaced by: Vehicle type maximum speed and cant deficiency
modified: 2023-04-05
comment: Combination of maximum speed and maximum cant deficiency for which the vehicle was assessed. This property was before an object skos property. The values for this property do not come from a list of predefined values. Thus, the original object property was replaced by this datatype property with range xsd:string. Deprecated because of replacement by a class and two integer properties. The reason is that the property represents two concepts: [number] km/h for maximum speed - [number] mm for maximum cant deficiency.
deprecated: true
term status: stable

Maximum speed empty
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: integer
ERATV index: 4.1.2.2
created: 2021-08-24
modified: 2021-08-24
comment: Maximum speed when empty.
term status: stable

Temperature range (maximum)
type: DatatypeProperty
range: integer
XML name: IPP_TempRange
ERATV index: 4.3.1
RINF index: 1.1.1.1.2.6
used in RCC calculations: true
created: 2020-08-24
is replaced by: Temperature range
modified: 2021-09-10
modified: 2024-09-25
comment: Deprecated because both RINF and ERATV define a temperature range as a set of predefined values (see https://www.era.europa.eu/system/files/2023-04/iu-eratv_application_guide_for_register_2016-797_en_0.pdf). Maximum temperature allowed for unrestricted operation access, according to European standard.
deprecated: true
term status: stable

Maximum train deceleration
type: DatatypeProperty
sub property of: Track resistance to applied loads
type: FunctionalProperty
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: double
XML name: ILR_MaxDeceleration
applicable: Y/N
dependency note: Not applicable if line is not in scope of INF TSI
format note: N.N
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.1.1.1.6.1
SHACL shape validation rule: MaximumTrainDeceleration
Unit of measure: M-PER-SEC2
used in RCC calculations: true
created: 2020-08-24
modified: 2021-09-10
modified: 2024-09-19
modified: 2025-02-28
source: http://data.europa.eu/eli/reg/2014/1299/2023-09-28
comment: Limit for longitudinal track resistance given as a maximum allowed train deceleration and expressed in metres per square second.
see also: INF TSI: 4.2.6
term status: stable
scope note: 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.

measured distance
type: DatatypeProperty
domain: Kilometric Post
range: double
SHACL shape validation rule: MeasuredDistance
Unit of measure: http://qudt.org/vocab/unit/M
created: 2024-11-29
comment: Measured distance from the origin of the LRS.

Meets requirement vehicle authorisation
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: string
ERATV index: 4.1.8
created: 2021-08-25
modified: 2021-08-25
comment: Type meets the requirements necessary for validity of the vehicle authorisation granted by one Member State in other MSs.
term status: stable

Minimum permitted axle load
type: DatatypeProperty
domain: Class
  union of: (deprecated) Min axle load vehicle category
  union of: Vehicle Type
range: double
ERATV index: 4.14.2.10
Unit of measure: TONNE
created: 2021-08-08
modified: 2023-03-14
comment: Minimum permitted axle load, given in tons.
term status: stable
scope note: Should be deprecated according to the amendment to the Regulation (EU) 2019/777 but remains because it is also a parameter of ERATV.

Minimum permitted distance between two consecutive axles
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: integer
ERATV index: 4.14.2.2
Unit of measure: MilliM
created: 2021-08-08
modified: 2023-03-14
comment: Deprecated according to the amendment to the Regulation (EU) 2019/777. However, the parameter remains as it is also an ERATV parameter.
term status: stable
scope note: Indication of minimum permitted distance between two consecutive axles, given in millimetres.

Minimum permitted distance between first and last axle
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: integer
ERATV index: 4.14.2.3
Unit of measure: MilliM
created: 2021-08-08
modified: 2023-03-14
comment: Deprecated according to the amendment to the Regulation (EU) 2019/777. However, the parameter remains as it is also an ERATV parameter.
term status: stable
scope note: Indication of minimum permitted distance between first and last axles, given in millimetres.

Minimum permitted height of the flange
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: double
ERATV index: 4.14.2.8
Unit of measure: MilliM
created: 2021-08-08
modified: 2021-09-01
comment: Deprecated according to the amendment to the Regulation (EU) 2019/777. However, the parameter remains as it is also an ERATV parameter.
term status: stable
scope note: Minimum permitted flange height, given in millimetres.

Minimum permitted thickness of the flange
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: double
ERATV index: 4.14.2.7
Unit of measure: MilliM
created: 2021-08-08
modified: 2021-09-01
comment: Deprecated according to the amendment to the Regulation (EU) 2019/777. However, the parameter remains as it is also an ERATV parameter.
term status: stable
scope note: Minimum permitted flange thickness, given in millimetres.

Minimum permitted width of the rim
type: DatatypeProperty
sub property of: Other train detection systems
domain: Vehicle Type
range: double
ERATV index: 4.14.2.5
Unit of measure: MilliM
created: 2021-08-08
modified: 2023-03-14
comment: Deprecated according to the amendment to the Regulation (EU) 2019/777. However, the parameter remains as it is also an ERATV parameter.
term status: stable

minimal vehicle input capacitance
type: DatatypeProperty
type: FunctionalProperty
domain: Minimum Vehicle Impedance
range: double
format note: For the selected DC voltage: [CCCC], as input capacitance [CCCC](Cin)
SHACL shape validation rule: MinVehicleInputCapacitance
SHACL shape validation rule: MinVehicleInputCapacitanceApplicability
Unit of measure: NanoFARAD
created: 2024-05-30
relation: Type of train detection system
term status: stable

minimal vehicle input impedance
type: DatatypeProperty
type: FunctionalProperty
domain: Minimum Vehicle Impedance
range: double
format note: For the selected DC voltage: [ZZZZ], as input impedance [ZZZZ](Zin)
SHACL shape validation rule: MinVehicleInputImpedance
SHACL shape validation rule: MinVehicleInputImpedanceApplicability
Unit of measure: MilliH
created: 2024-05-30
relation: Type of train detection system
term status: stable

Minimum permitted wheel diameter
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: integer
ERATV index: 4.14.2.6
Unit of measure: MilliM
created: 2021-08-08
modified: 2023-03-14
comment: Deprecated according to the amendment to the Regulation (EU) 2019/777. However, the parameter remains as it is also an ERATV parameter.
term status: stable
scope note: Minimum permitted wheel diameter, given in millimetres.

Minimum concave vertical radius
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: integer
ERATV index: 4.8.6
created: 2020-08-24
modified: 2020-11-03
comment: Minimum vertical concave curve radius capability.
term status: stable

Minimum contact wire height
type: DatatypeProperty
sub property of: Contact line system
sub property of: Vehicle type technical characteristic
type: FunctionalProperty
domain: Class
  union of: Contact Line System
  union of: Vehicle Type
range: double
XML name: ECS_MinWireHeight
applicable: Y/N
dependency note: When `not electrified` is chosen in parameter 1.1.1.2.2.1.1, then this parameter is not applicable.
ERATV index: 4.10.5
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.1.1.2.2.6
SHACL shape validation rule: MinimumContactWireHeight
SHACL shape validation rule: MinimumContactWireHeightApplicability
Unit of measure: http://qudt.org/vocab/unit/M
used in RCC calculations: true
created: 2020-08-25
modified: 2021-09-11
modified: 2024-09-25
relation: Type of contact line system
comment: Indication of the minimum contact wire height expressed in metres.
term status: stable
scope note: The value given can be design value or the last known measured value. If there is no change in height, nominal value will be given. Values shall be given in metres with precision of 0.01 m.

Minimum convex vertical radius
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: integer
ERATV index: 4.8.5
created: 2020-08-24
modified: 2020-11-03
comment: Minimum vertical convex curve radius capability.
term status: stable

Minimum radius of horizontal curve
type: DatatypeProperty
sub property of: Line layout
sub property of: Siding
sub property of: Vehicle type technical characteristic
type: FunctionalProperty
domain: Class
  union of: Subset with common characteristics
  union of: Running track
  union of: Vehicle Type
range: integer
XML name: ILL_MinRadHorzCurve
applicable: Y/N
ERATV index: 4.8.4
format note: NNNNN
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.1.1.1.3.7
RINF index: 1.2.2.0.3.2
SHACL shape validation rule: MinimumHorizontalRadius
SHACL shape validation rule: MinimumHorizontalRadiusS
Unit of measure: http://qudt.org/vocab/unit/M
used in RCC calculations: true
created: 2020-08-24
modified: 2021-09-10
modified: 2024-09-19
modified: 2025-02-28
modified: 2025-03-08
modified: 2025-03-11
source: http://data.europa.eu/eli/reg/2014/1299/2023-09-28
comment: Radius of the smallest horizontal curve, expressed in metres.
see also: INF TSI: 4.2.3.4 EN 13803:2017, Tables N.A and N.2
term status: stable
scope note: To describe a straight section of line value " 99999" shall be used.

Temperature range (minimum)
type: DatatypeProperty
range: integer
XML name: IPP_TempRange
ERATV index: 4.3.1
RINF index: 1.1.1.1.2.6
used in RCC calculations: true
created: 2020-08-24
is replaced by: Temperature range
modified: 2021-09-10
modified: 2024-09-25
comment: Deprecated because both RINF and ERATV define a temperature range as a set of predefined values (see https://www.era.europa.eu/system/files/2023-04/iu-eratv_application_guide_for_register_2016-797_en_0.pdf). Minimum temperature allowed for unrestricted operation access, according to European standard.
deprecated: true
term status: stable

Minimum radius of vertical curve crest
type: DatatypeProperty
type: FunctionalProperty
domain: Minimum radius of vertical curve
range: integer
SHACL shape validation rule: MinimumVerticalRadiusCrest
Unit of measure: http://qudt.org/vocab/unit/M
created: 2023-04-05
comment: Part of the minimum radius of vertical curve that indicates the crest
term status: stable

Minimum radius of vertical curve hollow
type: DatatypeProperty
domain: Minimum radius of vertical curve
range: integer
SHACL shape validation rule: MinimumVerticalRadiusHollow
Unit of measure: http://qudt.org/vocab/unit/M
created: 2023-04-05
comment: Part of the minimum radius of vertical curve that indicates the hollow
term status: stable

Minimum wheel diameter for fixed obtuse crossings
type: DatatypeProperty
sub property of: Switches and crossings
sub property of: Vehicle type technical characteristic
type: FunctionalProperty
domain: Class
  union of: Subset with common characteristics
  union of: Running track
  union of: Vehicle Type
range: integer
XML name: ISC_MinWheelDiaFixObtuseCrossings
applicable: Y
ERATV index: 4.8.2
format note: NNN
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.1.1.1.5.2
SHACL shape validation rule: MinimumWheelDiameter
Unit of measure: MilliM
used in RCC calculations: true
created: 2020-08-24
modified: 2021-09-10
modified: 2024-09-19
modified: 2025-02-28
source: http://data.europa.eu/eli/reg/2014/1299/2023-09-28
comment: Maximum unguided length of fixed obtuse crossings is based on a minimum wheel diameter in service expressed in millimetres.
see also: INF TSI: 4.2.5.3
term status: stable
scope note: 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.

Need for more than one train protection, control and warning system required on board
type: DatatypeProperty
range: boolean
RINF index: 1.1.1.3.5.2
created: 2021-08-09
modified: 2023-03-14
comment: Deprecated according to the amendment to the Regulation (EU) 2019/777. Indication whether more than one train protection, control and warning system is required to be on-board and active simultaneously.
deprecated: true
term status: unstable

National classification for load capability
type: DatatypeProperty
sub property of: Performance parameter
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: string
XML name: IPP_NCLoadCap
applicable: Y/N
legal deadline: 16 January 2020
RINF index: 1.1.1.1.2.4.1
SHACL shape validation rule: NationalLoadCapability
used in RCC calculations: true
created: 2020-08-24
modified: 2021-09-10
modified: 2024-09-19
comment: National classification for load capability
term status: stable
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'.
scope note: 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)

National fire category of rolling stock required
type: DatatypeProperty
sub property of: Tunnel
type: FunctionalProperty
domain: Class
  union of: Subset with common characteristics
  union of: Tunnel
range: string
XML name: ITU_NatFireCatReq
applicable: Y/N
dependency note: Mandatory for tunnels without value for 1.1.1.8.10 and where national values exist.
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.1.1.1.8.11
RINF index: 1.2.1.0.5.8
RINF index: 1.2.2.0.5.8
SHACL shape validation rule: NationalRollingStockFireCategory
SHACL shape validation rule: NationalRollingStockFireCategoryApplicability
used in RCC calculations: true
created: 2020-07-29
modified: 2024-01-08
modified: 2024-09-19
modified: 2025-02-28
source: http://data.europa.eu/eli/reg/2014/1303/2024-01-29
comment: Categorisation of 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.
see also: SRT TSI: 4.2.3.3.4 LOC&PAS TSI : 4.2.10.4.4
term status: stable
scope note: 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

National Values used for the brake model
type: DatatypeProperty
sub property of: ETCS National Values
type: FunctionalProperty
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: string
applicable: Y/N/NYA
dependency note: A value has to be provided when ETCS is present (a value is provided on 1.1.1.3.2.1).
legal deadline: 12 months after publication of Article 7 Guide
RINF index: 1.1.1.3.2.16.13
RINF index: 1.2.1.1.1.16.13
SHACL shape validation rule: NationalValuesBrakeModel
SHACL shape validation rule: NationalValuesBrakeModelApplicability
TSI operation appendix D3 index: 1.5.13
created: 2023-03-14
modified: 2024-01-08
modified: 2024-04-18
modified: 2024-12-05
relation: European Train Control System (ETCS) level
source: oj
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. It copies the content of Packet 3 or of Packet 203 as defined in the specification referenced in Appendix A-1, index [C].
term status: stable
scope note: Non-harmonizable character string: [Contents of P3/P203] (TSI CCS, Annex I, Appendix A, Table A.2 - Subset-026)

Non coded restrictions
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: string
created: 2022-06-15
modified: 2022-06-15
comment: Denotes a non-coded restrictions for this particular vehicleType, as a set of sentences.
term status: stable

Number elements rake freight wagons
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: integer
ERATV index: 4.1.6
created: 2021-08-25
modified: 2021-08-25
comment: Number of elements in the rake of freight wagons (only for subcategory 'rake of freight wagons')
term status: stable

Number of pantographs in contact with OCL
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: integer
ERATV index: 4.10.7
created: 2020-08-25
modified: 2020-11-19
comment: Number of pantographs in contact with the overhead contact line (OCL) (to be indicated for each energy supply system the vehicle is equipped for).
term status: stable

Number of toilets
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: integer
ERATV index: 4.12.1.2
created: 2021-08-31
modified: 2021-08-31
comment: Number of toilets.
term status: stable

OCL separation sections
type: DatatypeProperty
sub property of: Energy subsystem
RINF index: 1.1.1.2.4
created: 2024-10-31

Ocl type
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: string
ERATV index: 4.10.9
created: 2020-08-25
modified: 2020-10-03
comment: OCL type.
term status: stable

offset
type: DatatypeProperty
domain: Linear Positioning System Coordinate
range: double
SHACL shape validation rule: OffsetFromKilometricPost
Unit of measure: http://qudt.org/vocab/unit/M
created: 2024-11-29
comment: Relative distance from a reference kilometric post

offset from origin
type: DatatypeProperty
domain: Topological Coordinate
range: double
SHACL shape validation rule: OffsetFromOrigin
Unit of measure: http://qudt.org/vocab/unit/M
created: 2024-11-29
modified: 2025-01-30
modified: 2025-10-07
comment: Offset from the origin in a topological coordinate.

Operational point generic information
type: DatatypeProperty
sub property of: RINF Technical characteristic
RINF index: 1.2.0.0.0
created: 2025-03-11

Name of operational point
type: DatatypeProperty
sub property of: Operational point generic information
domain: Operational Point
range: langString
XML name: OPName
applicable: Y
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.2.0.0.0.1
SHACL shape validation rule: OpName
TSI operation appendix D2 index: 2.3.1
created: 2021-09-13
modified: 2021-09-13
modified: 2025-03-11
modified: 2025-08-26
source: oj
comment: Name normally related to the town or village or to traffic control purpose.
term status: stable
scope note: Name of OP may not always exist in common use. In such case IM should propose a name for OP.

Type of track gauge changeover facility
type: DatatypeProperty
sub property of: Operational point generic information
type: FunctionalProperty
domain: Operational Point
range: string
XML name: OPTypeGaugeChangeover
applicable: Y/N
legal deadline: 16 January 2020
RINF index: 1.2.0.0.0.4.1
SHACL shape validation rule: OpTypeGaugeChangeover
used in RCC calculations: true
created: 2021-08-11
modified: 2021-08-11
modified: 2025-03-11
comment: Type of track gauge changeover facility.
term status: stable

organisation code
type: DatatypeProperty
sub property of: Platform
sub property of: Siding
sub property of: Section of line generic information
sub property of: Running track generic information
sub property of: Tunnel
sub property of: Identifier
type: FunctionalProperty
domain: Organisation Role
range: string
XML name: OPSidingIMCode
XML name: OPSidingTunnelIMCode
XML name: OPTrackIMCode
XML name: OPTrackPlatformIMCode
XML name: OPTrackTunnelIMCode
XML name: SOLIMCode
XML name: SOLTunnelIMCode
applicable: Y
format note: AAAA
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.1.0.0.0.1
RINF index: 1.1.1.1.8.1
RINF index: 1.2.1.0.0.1
RINF index: 1.2.1.0.5.1
RINF index: 1.2.1.0.6.1
RINF index: 1.2.2.0.0.1
RINF index: 1.2.2.0.5.1
SHACL shape validation rule: OrganisationCode
TSI operation appendix D2 index: 1.1
created: 2024-06-03
modified: 2024-11-06
modified: 2024-11-12
modified: 2025-02-18
modified: 2025-03-08
replaces: Infrastructure manager (IM)'s code
source: http://data.europa.eu/eli/dec_impl/2018/1614
source: oj
comment: Four alpha-numeric code allocated by ERA to a body. It represents 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 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))
comment: Infrastructure manager means any body or undertaking that is responsible in particular for establishing and maintaining railway infrastructure or a part thereof.
alternative label: IM's code
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.
scope note: 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.

Other train detection systems
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
RINF index: 1.1.1.3.7
RINF index: 1.2.1.1.6
created: 2024-10-31
modified: 2025-03-11

Pantograph
type: DatatypeProperty
sub property of: Energy subsystem
RINF index: 1.1.1.2.3
created: 2024-10-31

Parameter value
type: DatatypeProperty
domain: Parameter applicability
range: Literal
SHACL shape validation rule: ParameterValue
created: 2024-12-10
comment: This property is used to link an applicability to the precise value of the parameter

Parking brake
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: boolean
ERATV index: 4.7.3
created: 2022-04-11
modified: 2022-04-11
comment: Indicates whether all vehicles of this type must be equipped with a parking brake.
term status: stable

Parking brake mandatory
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: boolean
ERATV index: 4.7.3.1
created: 2021-08-26
modified: 2021-08-26
comment: All vehicles of this type must be equipped with a parking brake (parking brake mandatory for vehicles of this type).
term status: stable

Parking brake maximum gradient
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: double
ERATV index: 4.7.3.3
created: 2020-08-24
modified: 2020-11-03
comment: Maximum gradient on which the unit is kept immobilised by the parking brake alone (if the vehicle is fitted with it).
term status: stable

Pass-by noise level
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: double
ERATV index: 4.11.1
created: 2021-08-31
modified: 2021-08-31
comment: Pass-by noise level given in dB(A).
term status: stable

passenger flag
type: DatatypeProperty
type: FunctionalProperty
domain: Primary Location
range: boolean
SHACL shape validation rule: PassengerFlag
created: 2025-09-21
comment: Passenger possible flag attached to a Primary Location
term status: stable

Performance parameter
type: DatatypeProperty
sub property of: Infrastructure subsystem
RINF index: 1.1.1.1.2
RINF index: 1.2.1.0.2
RINF index: 1.2.2.0.2
created: 2024-10-31

Permissible payload
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: string
ERATV index: 4.5.1
created: 2020-08-24
modified: 2020-11-03
comment: Permissible payload for different line categories.
term status: stable

Permission for charging electric energy storage for traction purposes at standstill
type: DatatypeProperty
sub property of: Contact line system
type: FunctionalProperty
domain: Contact Line System
range: boolean
applicable: Y/N
legal deadline: Contrary to the Regulation, the deadline is not 30 June 2024 at the latest, but 12 months after publication of Article 7 Guide
RINF index: 1.2.1.0.7.1
SHACL shape validation rule: PermissionChargingElectricEnergyTractionStandstill
created: 2023-03-14
comment: Point at which IM authorises charging of electric energy storage for traction purposes at standstill.
term status: stable

Permit of use of reflective plates
type: DatatypeProperty
sub property of: Health, safety and environment
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: boolean
applicable: Y/N/NYA
legal deadline: 12 months after publication of Article 7 Guide
RINF index: 1.1.1.1.7.12
SHACL shape validation rule: PermitUseReflectivePlates
created: 2023-03-14
modified: 2025-09-22
comment: Sections where is permitted to use the reflective plates on rail freight corridors, with a view to prioritise the current bottlenecks. Specific case for Belgium, France, Italy, Portugal and Spain until 1.1.2026
see also: 4.2.2.1.3.2 of TSI OPE (Commission Implementing Regulation (EU) 2019/773 of 16 May 2019)
term status: stable
scope note: 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.

Contact force permitted
type: DatatypeProperty
sub property of: Requirements for rolling stock
type: FunctionalProperty
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: string
XML name: ERS_ContactForce
applicable: Y/N
dependency note: A value is mandatory if the value Overhead contact line (OCL) is selected for parameter "Type of contact line system"
format note: The force is either given as: a value of the static force and of the maximum force expressed in newtons, or as a formula for function of the speed
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.1.1.2.5.2
SHACL shape validation rule: PermittedContactForce
SHACL shape validation rule: PermittedContactForceApplicability
Unit of measure: http://qudt.org/vocab/unit/N
used in RCC calculations: true
created: 2020-08-25
modified: 2024-01-08
comment: Indication of contact force allowed expressed in newton.
see also: LOC&PAS TSI: 4.2.8.2.9.6 ENE TSI: 4.2.11 EN 50367:2020+A1:2022 Table 6
term status: stable
scope note: The formula of the function shall represent the curve describing the value of the contact force in relation to the speed. Static and maximum forces are given only for the maximum permitted line speed (see parameter number 1.1.1.1.2.5).

Information on phase separation
type: DatatypeProperty
range: string
created: 2021-08-08
is replaced by: Phase info
is replaced by: Phase info Km
is replaced by: Phase info length
is replaced by: Phase info pantograph lowered
is replaced by: Phase info switch off breaker
is replaced by: Information on phase separation
modified: 2023-04-05
deprecated: true
term status: stable
editorial note: Deprecated because of replacement by three properties. The reason is that the property is composed of three values: 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; and 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.

Phase info change supply system
type: DatatypeProperty
domain: Phase info
range: boolean
SHACL shape validation rule: PhaseInfoChangeSupplySystem
created: 2024-02-05
modified: 2025-03-11
modified: 2025-06-09
comment: Part of the phase info of a track that corresponds to the single selection of Y=yes or N=no to show if the energy supply system changes
deprecated: true
term status: stable
scope note: The phase info is the indication of required several information on phase separation.

Phase info distance type
type: DatatypeProperty
type: FunctionalProperty
domain: Phase info
range: string
SHACL shape validation rule: PhaseInfoDistanceType
created: 2024-02-05
modified: 2025-03-11
comment: Part of the phase info of a track that corresponds to 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. Multiple strings for this parameter are accepted.
term status: stable
scope note: The phase info is the indication of required several information on phase separation.

Phase info Km
type: DatatypeProperty
type: FunctionalProperty
domain: Phase info
range: double
SHACL shape validation rule: PhaseInfoKm
created: 2023-04-05
modified: 2025-02-18
modified: 2025-03-11
replaces: Information on phase separation
comment: Part of the phase info of a track that indicates the location from the start of the line where the new value is valid.
term status: stable
scope note: The phase info is the indication of required several information on phase separation.

Phase info length
type: DatatypeProperty
type: FunctionalProperty
domain: Phase info
range: integer
SHACL shape validation rule: PhaseInfoLength
Unit of measure: http://qudt.org/vocab/unit/M
created: 2023-04-05
modified: 2025-02-18
modified: 2025-03-11
replaces: Information on phase separation
comment: Part of the phase info of a track that corresponds to the length of the phase separation in metres.
term status: stable
scope note: The phase info is the indication of required several information on phase separation.

Phase info pantograph lowered
type: DatatypeProperty
type: FunctionalProperty
domain: Phase info
range: boolean
SHACL shape validation rule: PhaseInfoPantographLowered
created: 2023-04-05
modified: 2025-02-18
modified: 2025-03-11
replaces: Information on phase separation
comment: Part of the phase info of a track that shows whether a pantograph has to be lowered.
term status: stable
scope note: The phase info is the indication of required several information on phase separation.

Phase info switch off breaker
type: DatatypeProperty
type: FunctionalProperty
domain: Phase info
range: boolean
SHACL shape validation rule: PhaseInfoSwitchOffBreaker
created: 2023-04-05
modified: 2025-02-18
modified: 2025-03-11
replaces: Information on phase separation
comment: Part of the phase info of a track that shows whether the breaker has to be switched off.
term status: stable
scope note: The phase info is the indication of required several information on phase separation.

Platform
type: DatatypeProperty
sub property of: RINF Technical characteristic
RINF index: 1.2.1.0.6
created: 2025-03-11

Identification of platform
type: DatatypeProperty
sub property of: Platform
sub property of: Identifier
type: FunctionalProperty
domain: Platform edge
range: string
XML name: OPTrackPlatformIdentification
applicable: Y/N
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.2.1.0.6.2
SHACL shape validation rule: NoRepeatedPlatformIdsOP
SHACL shape validation rule: PlatformId
TSI operation appendix D2 index: 2.3.5
created: 2021-09-13
modified: 2023-03-14
modified: 2025-03-11
modified: 2025-09-03
source: oj
comment: Unique platform identification or unique platform number within an Operational Point.
term status: stable

Portable boarding aids
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: string
ERATV index: 4.12.3.3
created: 2021-08-31
modified: 2021-08-31
modified: 2024-04-18
source: http://data.europa.eu/eli/reg/2014/1300/2023-09-28
comment: Description of any portable boarding aids if considered in the design of the vehicle for meeting the PRM TSI requirements.
term status: stable

Prevent regenerative brake use
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: boolean
ERATV index: 4.7.4.3.2
created: 2020-08-24
modified: 2020-11-03
comment: Possibility of preventing the use of the regenerative brake (only if fitted with regenerative brake).
term status: stable

primary location code
type: DatatypeProperty
sub property of: Identifier
type: FunctionalProperty
domain: Primary Location
range: string
XML name: OPTafTapCode
RINF index: 1.2.0.0.0.3
SHACL shape validation rule: PrimaryLocationCode
TSI operation appendix D2 index: 2.2.2
created: 2024-06-03
replaces: OP primary location code
comment: Primary location code developed for information exchange in accordance with the TSIs relating to the telematics applications subsystem.
term status: stable

primary location name
type: DatatypeProperty
domain: Primary Location
range: langString
SHACL shape validation rule: PrimaryLocationName
created: 2024-06-03
modified: 2025-08-29

Priority seats
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: string
ERATV index: 4.12.2.1
created: 2021-08-31
modified: 2021-08-31
modified: 2024-11-25
source: http://data.europa.eu/eli/reg/2014/1300/2023-09-28
comment: Number of priority seats.
term status: stable

Prm accessible toilets
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: integer
ERATV index: 4.12.2.3
created: 2021-08-31
modified: 2021-08-31
modified: 2024-11-25
source: http://data.europa.eu/eli/reg/2014/1300/2023-09-28
comment: Number of PRM accessible toilets.
term status: stable

Existence of GSM-R roaming to public networks
type: DatatypeProperty
sub property of: TSI compliant radio (RMR)
type: FunctionalProperty
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: boolean
applicable: Y/N/NYA
dependency note: GSM-R must be installed for this parameter to be applicable
legal deadline: 1 January 2021
legal deadline: 12 months after publication of Article 7 Guide for OP tracks
RINF index: 1.1.1.3.3.6
RINF index: 1.2.1.1.2.6
SHACL shape validation rule: PublicNetworkRoaming
SHACL shape validation rule: PublicNetworkRoamingApplicability
created: 2021-08-09
modified: 2024-01-08
modified: 2025-03-04
relation: Details on GSM-R roaming to public networks
comment: Existence of roaming to a public network. In case of Y, provide the name of the public network(s) under parameter "Details on GSM-R roaming to public networks".
term status: stable
scope note: Sections of EIRENE not covered by references in TSI.

Details on GSM-R roaming to public networks
type: DatatypeProperty
sub property of: TSI compliant radio (RMR)
type: FunctionalProperty
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: string
applicable: Y/N/NYA
dependency note: Mandatory if GSM-R is installed and era:publicNetworkRoaming is 'true'. Otherwise, it is not applicable.
legal deadline: 1 January 2021
legal deadline: 12 months after publication of Article 7 Guide for OP tracks
RINF index: 1.1.1.3.3.7
RINF index: 1.2.1.1.2.7
SHACL shape validation rule: PublicNetworkRoamingDetails
SHACL shape validation rule: PublicNetworkRoamingDetailsApplicability
created: 2021-08-09
modified: 2024-01-08
modified: 2024-04-18
modified: 2025-03-04
relation: Existence of GSM-R roaming to public networks
comment: If roaming to public networks is configured, please indicate to which networks, for which users and in which areas.
term status: stable
scope note: 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.

Q_NVSBTSMPERM
type: DatatypeProperty
sub property of: ETCS National Values
type: FunctionalProperty
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: boolean
applicable: Y/N/NYA
dependency note: A value has to be provided when ETCS is present (a value is provided on 1.1.1.3.2.1).
legal deadline: 12 months after publication of Article 7 Guide
RINF index: 1.1.1.3.2.16.12
RINF index: 1.2.1.1.1.16.12
SHACL shape validation rule: QNvsbtsmperm
SHACL shape validation rule: QNvsbtsmpermApplicability
TSI operation appendix D3 index: 1.5.12
created: 2023-03-14
modified: 2024-04-18
relation: European Train Control System (ETCS) level
source: oj
comment: Permission to use service brake in target speed monitoring
term status: stable
scope note: See: TSI CCS (Subset-026, chapter 7. 7.5.1.124 Q_NVSBTSMPERM)

Quasi static guiding force
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: double
ERATV index: 4.5.4
created: 2021-08-26
modified: 2021-08-26
comment: Quasi-static guiding force (if exceeds the limit defined in TSI or not defined in the TSI), given in kN.
term status: stable

Radio Network ID
type: DatatypeProperty
sub property of: TSI compliant radio (RMR)
sub property of: Identifier
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: string
applicable: Y/N/NYA
dependency note: GSM-R must be installed for this parameter to be applicable.
format note: NNNNNN with N a decimal number (0 9).
legal deadline: 12 months after publication of Article 7 Guide
RINF index: 1.1.1.3.3.12
RINF index: 1.2.1.1.2.13
SHACL shape validation rule: RadioNetworkId
SHACL shape validation rule: RadioNetworkIdApplicability
TSI operation appendix D2 index: 3.4.4
created: 2023-03-14
modified: 2024-04-18
modified: 2024-09-19
modified: 2024-12-05
modified: 2025-09-03
relation: European Train Control System (ETCS) level
relation: GPRS for ETCS
source: oj
comment: Unique identification of the GSM-R network the calling mobile station has to register with, as defined in the specification referenced in Appendix A-1, index [C]
term status: stable
editorial note: (sh:minCount 1)
scope note: According to the specification referenced in TSI CCS.

Radio switch over special conditions
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: string
ERATV index: 4.13.2.4
created: 2021-08-31
modified: 2021-08-31
comment: Special conditions implemented on-board to switch over between different radio systems. Given as combination of systems installed on board ('System XX'_'System YY').
term status: stable

Rail system type
type: DatatypeProperty
domain: Subset with common characteristics
range: string
created: 2022-11-04
modified: 2024-04-18
comment: (deprecated) Type of railway system. Can be "High-speed" or "Conventional". Deprecated due to the lack of information
deprecated: true
term status: stable

Requirements for spacing between raised pantographs, at the given speed
type: DatatypeProperty
type: FunctionalProperty
domain: Requirements for number of raised pantographs and spacing between them, at the given speed
range: integer
SHACL shape validation rule: RaisedPantographsDistance
Unit of measure: http://qudt.org/vocab/unit/M
created: 2023-04-05
modified: 2024-09-19
modified: 2025-03-11
relation: Type of contact line system
comment: Part of the raised pantographs distance and speed of a track that corresponds to the minimum distance between pantographs, in metres.
term status: stable
definition: 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.

(deprecated) Requirements for number of raised pantographs and spacing between them, at the given speed
type: DatatypeProperty
range: string
created: 2020-08-25
modified: 2023-04-05
comment: 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.
deprecated: true
term status: stable
editorial note: Deprecated because of replacement by a class and three integer properties The reason is that the property is composed of three values: [N] is number of pantographs; [NNN] is minimum distance between pantographs, in metres; [NNN] is the speed considered in km/h.

Requirements for number of raised pantographs, at the given speed
type: DatatypeProperty
type: FunctionalProperty
domain: Requirements for number of raised pantographs and spacing between them, at the given speed
range: integer
SHACL shape validation rule: RaisedPantographsNumber
created: 2023-04-05
modified: 2024-09-19
modified: 2025-03-11
relation: Type of contact line system
comment: Part of the raised pantographs distance and speed of a track that corresponds to the number of pantographs.
term status: stable
definition: 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.

Raised pantographs speed
type: DatatypeProperty
type: FunctionalProperty
domain: Requirements for number of raised pantographs and spacing between them, at the given speed
range: integer
SHACL shape validation rule: RaisedPantographsSpeed
Unit of measure: KiloM-PER-HR
created: 2023-04-05
modified: 2024-09-19
modified: 2025-03-11
modified: 2025-05-12
relation: Type of contact line system
comment: 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.
term status: stable
definition: 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.

ID of ERTMS/ETCS Radio Block Center
type: DatatypeProperty
sub property of: TSI compliant train protection system (ETCS)
sub property of: Identifier
type: FunctionalProperty
domain: Radio Block Center
range: string
applicable: Y/N/NYA
format note: NNNN NNNN with N a decimal number (0÷9)
legal deadline: 12 months after publication of Article 7 Guide
RINF index: 1.1.1.3.2.17
RINF index: 1.2.1.1.1.17
SHACL shape validation rule: RbcID
TSI operation appendix D2 index: 3.4.7
created: 2024-04-18
modified: 2025-02-18
relation: European Train Control System (ETCS) level
replaces: (deprecated) ID and phone number of ERTMS/ETCS Radio Block Center
source: oj
comment: Unique RBC identification (NID_C+NID_RBC) as defined in the specification referenced in Appendix A-1, index [C] (TSI CCS).
term status: stable

Phone number of ERTMS/ETCS Radio Block Center
type: DatatypeProperty
sub property of: TSI compliant train protection system (ETCS)
type: FunctionalProperty
domain: Radio Block Center
range: string
format note: NNNN NNNN NNNN NNNN with N a decimal number (0-9)
legal deadline: 12 months after publication of Article 7 Guide
RINF index: 1.1.1.3.2.17
RINF index: 1.2.1.1.1.17
SHACL shape validation rule: RbcPhone
TSI operation appendix D2 index: 3.4.7
created: 2024-04-18
modified: 2024-12-05
modified: 2025-02-18
relation: European Train Control System (ETCS) level
replaces: (deprecated) ID and phone number of ERTMS/ETCS Radio Block Center
source: oj
comment: Unique RBC calling number (NID_RADIO) as defined in the specification referenced in Appendix A-1, index [C].
term status: stable

Steady red lights required
type: DatatypeProperty
sub property of: Health, safety and environment
type: FunctionalProperty
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: boolean
XML name: IHS_RedLights
applicable: Y/N
format note: in XML: Y/N
legal deadline: 1 January 2021
RINF index: 1.1.1.1.7.10
SHACL shape validation rule: RedLightsRequired
SHACL shape validation rule: RedLightsRequiredCountryApplicability
created: 2021-08-08
modified: 2024-01-08
modified: 2025-02-28
modified: 2025-06-16
modified: 2025-09-10
source: http://data.europa.eu/eli/reg_impl/2019/773/2025-03-31
comment: Sections where permissive driving is possible in accordance with point 4.2.2.1.2 of TSI OPE
comment: Sections where two steady red lights are required in accordance with TSI OPE
see also: art 4.2.2.1.3.2. of Implementing Regulation (EU) 2019/773 'Freight trains'
term status: stable
alternative label: Permissive driving allowed
scope note: 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.

Reference pass-by noise level
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: boolean
ERATV index: 4.11.2
created: 2021-08-31
modified: 2021-08-31
comment: Pass-by noise level was measured under reference conditions.
term status: stable

Parameters related to electromagnetic interferences
type: DatatypeProperty
sub property of: Control-command and signalling subsystem
RINF index: 1.1.1.3.9
RINF index: 1.2.1.1.8
created: 2024-10-31

Relative distance of the danger point
type: DatatypeProperty
sub property of: Signal
domain: Signal
range: integer
applicable: Y/N/NYA
format note: NNN
legal deadline: 12 months after publication of Article 7 Guide
RINF index: 1.1.1.3.14.4
RINF index: 1.2.1.0.8.4
SHACL shape validation rule: RelativeDistanceDangerPoint
TSI operation appendix D2 index: 2.2.3
TSI operation appendix D2 index: 2.3.3
Unit of measure: http://qudt.org/vocab/unit/M
created: 2023-03-14
modified: 2024-04-18
source: oj
comment: Distance in meters to the danger point
term status: stable
scope note: 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.

Relative position
type: DatatypeProperty
range: double
created: 2021-04-01
modified: 2023-11-10
comment: Indicates the position of an object relative to the linear coordinates of the associated topological object.
deprecated: true
term status: stable
editorial note: The reason for deprecation is that this property is not specified in the latest legal text nor the RINF application guide. Also, no data has been provided for this property.

Sanding override by driver required
type: DatatypeProperty
domain: Train Detection System
range: boolean
created: 2021-08-08
modified: 2023-03-14
source: oj
comment: Indication whether possibility to activate/deactivate sanding devices by driver, according to instructions from the Infrastructure Manager, is required or not. Deprecated according to the amendment to the Regulation (EU) 2019/777.
deprecated: true
term status: stable

Requirements for rolling stock
type: DatatypeProperty
sub property of: Energy subsystem
RINF index: 1.1.1.2.5
created: 2024-10-31

RINF Technical characteristic
type: DatatypeProperty
created: 2024-10-31
modified: 2025-02-25

Route book specific parameters
type: DatatypeProperty
sub property of: RINF Technical characteristic
RINF index: 1.1.0.0.1
created: 2025-01-30

Rules and restrictions
type: DatatypeProperty
sub property of: RINF Technical characteristic
RINF index: 1.1.1.4
RINF index: 1.2.3
created: 2025-03-11

Schematic overview of the operational point
type: DatatypeProperty
sub property of: Operational point generic information
domain: Operational Point
range: anyURI
applicable: Y/N/NYA
legal deadline: 12 months after publication of Article 7 Guide
RINF index: 1.2.0.0.0.7.1
TSI operation appendix D2 index: 2.1
created: 2023-03-14
modified: 2025-03-11
comment: Document providing the schematic overview of the operational point
term status: stable

Shortest distance between pantographs in contact with OCL
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: string
ERATV index: 4.10.8
created: 2020-08-25
modified: 2021-09-15
comment: Shortest distance between two pantographs in contact with the OCL (to be indicated for each energy supply system the vehicle is equipped for; to be indicated for single and, if applicable, multiple operation) (only if number of raised pantographs is more than 1).
term status: stable

Siding
type: DatatypeProperty
sub property of: RINF Technical characteristic
RINF index: 1.2.2
created: 2025-03-11

Fixed installations for servicing trains
type: DatatypeProperty
sub property of: Siding
RINF index: 1.2.2.0.4
created: 2025-03-11

Identification of siding
type: DatatypeProperty
sub property of: Siding
sub property of: Identifier
type: FunctionalProperty
domain: Siding
range: string
XML name: OPSidingIdentification
applicable: Y/N
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.2.2.0.0.2
SHACL shape validation rule: NoRepeatedSidingIds
SHACL shape validation rule: SidingId
TSI operation appendix D2 index: 2.2.1
TSI operation appendix D2 index: 2.2.1.4
created: 2021-09-13
modified: 2023-03-14
modified: 2025-03-11
source: oj
comment: Unique siding identification or number within an Operational Point.
term status: stable

Signal
type: DatatypeProperty
sub property of: Control-command and signalling subsystem
RINF index: 1.1.1.3.14
created: 2024-10-31

Name of signal
type: DatatypeProperty
sub property of: Signal
sub property of: Identifier
type: FunctionalProperty
domain: Signal
range: string
applicable: Y/N/NYA
legal deadline: 12 months after publication of Article 7 Guide
RINF index: 1.1.1.3.14.1
RINF index: 1.2.1.0.8.1
SHACL shape validation rule: SignalId
TSI operation appendix D2 index: 2.2.3
TSI operation appendix D2 index: 2.3.3
created: 2023-03-14
modified: 2024-04-18
source: oj
comment: Identifier of signal.
term status: stable
scope note: Operational identifier of the signal (on the track or in OP), as in the operational and maintenance provisions.

Sleeping places
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: string
ERATV index: 4.12.1.3
created: 2021-08-31
modified: 2021-09-15
comment: Number of sleeping places.
term status: stable

Section of line generic information
type: DatatypeProperty
sub property of: RINF Technical characteristic
RINF index: 1.1.0.0.0
created: 2025-03-11

Specific information
type: DatatypeProperty
sub property of: Line layout
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: string
XML name: ILL_SpecificInfo
applicable: Y/N
legal deadline: 1 January 2021
RINF index: 1.1.1.1.3.5.1
SHACL shape validation rule: SpecificInformation
created: 2021-08-03
modified: 2021-09-10
comment: Any relevant information from the IM relating to the line layout
term status: stable
scope note: This parameter allows the IM to provide plain text with specific information about the track

Start intrinsic coordinate
type: DatatypeProperty
range: double
created: 2021-04-01
modified: 2021-04-01
deprecated: true
term status: stable

start offset from origin
type: DatatypeProperty
domain: Linear Element Section
range: double
SHACL shape validation rule: StartOffsetFromOrigin
Unit of measure: http://qudt.org/vocab/unit/M
created: 2024-11-29
modified: 2025-01-30
comment: Start offset of the section from the origin.

Starting noise level
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: double
ERATV index: 4.11.4
created: 2021-08-31
modified: 2021-08-31
comment: starting noise level given in dB(A).
term status: stable

Static axle load under exceptional payload
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: double
ERATV index: 4.5.3.3
created: 2020-08-24
modified: 2020-11-03
comment: Static axle load under exceptional payload.
term status: stable

Static axle load under normal payload
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: double
ERATV index: 4.5.3.2
created: 2020-08-24
modified: 2020-11-03
comment: Static axle load under normal payload.
term status: stable

Static axle load in working order
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: double
ERATV index: 4.5.3.1
created: 2020-08-24
modified: 2020-11-03
comment: Static axle load in working order.
term status: stable

Stationary noise level
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: double
ERATV index: 4.11.3
created: 2021-08-31
modified: 2021-08-31
comment: stationary noise level given in dB(A).
term status: stable

Structural category
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: string
ERATV index: 4.1.10
created: 2021-08-25
modified: 2021-08-25
comment: Structural category.
term status: stable

Railway location of structures requiring specific checks
type: DatatypeProperty
sub property of: Performance parameter
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: double
XML name: IPP_StructureCheckLoc
applicable: Y/N
dependency note: This information is to be linked with parameter 1.1.1.1.2.4.4
legal deadline: 16 January 2020
RINF index: 1.1.1.1.2.4.3
SHACL shape validation rule: StructureCheckLocation
used in RCC calculations: true
created: 2020-08-24
modified: 2023-03-14
modified: 2024-09-19
relation: Document with the procedure(s) for static and dynamic route compatibility checks
comment: Localisation of structures requiring specific checks
term status: stable
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.
scope note: The railway location identifies the location of the structure in the system of reference of the line to which the track belongs.

Name of a subset with common characteristics
type: DatatypeProperty
domain: Subset with common characteristics
range: langString
SHACL shape validation rule: SubsetName
created: 2023-03-14
modified: 2025-09-05
comment: A subset of elements with common characteristics could be identified with a unique name/id.
term status: stable
example: Example: "ETCSbaseline2": describes all ETCS National values (1.1.1.3.2.16 group)

subsidiary location code
type: DatatypeProperty
domain: Subsidiary location
range: string
SHACL shape validation rule: SubsidiaryLocationCode
created: 2024-06-03
comment: The numeric code for the subsidiary location

subsidiary location name
type: DatatypeProperty
domain: Subsidiary location
range: langString
SHACL shape validation rule: SubsidiaryLocationName
created: 2024-06-03
modified: 2025-09-05
comment: The common name given to the subsidiary location

Existence of switch over between different protection, control and warning systems while running
type: DatatypeProperty
sub property of: Transitions between systems
type: FunctionalProperty
domain: Class
  union of: Subset with common characteristics
  union of: Track
range: boolean
applicable: Y/N/NYA
dependency note: Applicable when at least two different protection, control and warning systems exist.
legal deadline: 12 months after publication of Article 7 Guide for OP tracks
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.1.1.3.8.1
RINF index: 1.2.1.1.7.1
SHACL shape validation rule: SwitchProtectControlWarning
SHACL shape validation rule: SwitchProtectControlWarningApplicability
TSI operation appendix D2 index: 3.4.2
created: 2021-08-09
modified: 2021-09-12
modified: 2025-03-04
relation: Special conditions to switch over between different class B train protection, control and warning systems
source: oj
comment: Indication whether a switch over between different systems whilst running exists.
term status: stable
scope note: Switch over between different systems whilst running. Installation depends on local conditions.

Existence of switch over between different radio systems
type: DatatypeProperty
sub property of: Transitions between systems
type: FunctionalProperty
domain: Class
  union of: Subset with common characteristics
  union of: Track
range: boolean
applicable: Y/N/NYA
dependency note: Applicable when at least two different radio systems exist.
legal deadline: 12 months after publication of Article 7 Guide for OP tracks
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.1.1.3.8.2
RINF index: 1.2.1.1.7.2
SHACL shape validation rule: SwitchRadioSystem
SHACL shape validation rule: SwitchRadioSystemApplicability
TSI operation appendix D2 index: 3.4.4
created: 2021-08-09
modified: 2021-09-12
modified: 2024-09-19
modified: 2025-03-04
relation: Other radio systems installed (Radio Legacy Systems)
source: oj
comment: Indication whether a switch over between different radio systems and no communication system whilst running exists.
term status: stable
scope note: 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

Switches and crossings
type: DatatypeProperty
sub property of: Infrastructure subsystem
RINF index: 1.1.1.1.5
created: 2024-10-31

(deprecated) Information on system separation
type: DatatypeProperty
range: string
created: 2021-08-08
is replaced by: System separation info
is replaced by: System separation info Km
is replaced by: System separation info length
is replaced by: System separation info switch off breaker
is replaced by: Information on system separation
modified: 2023-04-05
modified: 2025-02-18
comment: (deprecated) Indication of required several information on system separation. Deprecated because of replacement by four properties. The reason is that the property is composed of four values: length [NNN], the length of the system separation in metres; switch off breaker [Y/N]. Single selection of 'Y=yes' or 'N=no' to show whether the breaker has to be switched off; lower pantograph [Y/N]. Single selection of 'Y=yes' or 'N=no' to show whether the pantograph has to be lowered, and [CharacterString] to show whether the supply system has to be changed.
deprecated: true
term status: stable

System separation info change supply system
type: DatatypeProperty
domain: System separation info
range: string
SHACL shape validation rule: SystemSeparationInfoChangeSupplySystem
created: 2023-04-05
modified: 2025-03-11
modified: 2025-06-09
comment: Part of the system separation info of a track that shows whether the supply system has to be changed. The system separation info is the Indication of required several information on system separation.
deprecated: true
term status: stable

System separation info Km
type: DatatypeProperty
type: FunctionalProperty
domain: System separation info
range: double
SHACL shape validation rule: SystemSeparationInfoKm
created: 2023-04-05
modified: 2025-02-18
modified: 2025-03-11
replaces: (deprecated) Information on system separation
comment: Part of the system separation info of a track. Indicates the location from the start of the line where the new value is valid. The system separation info is the Indication of required several information on system separation.
term status: stable

System separation info length
type: DatatypeProperty
type: FunctionalProperty
domain: System separation info
range: integer
SHACL shape validation rule: SystemSeparationInfoLength
Unit of measure: http://qudt.org/vocab/unit/M
created: 2023-04-05
modified: 2025-02-18
modified: 2025-03-11
replaces: (deprecated) Information on system separation
comment: Part of the system separation info of a track that shows the length of the system separation in metres. The system separation info is the Indication of required several information on system separation.
term status: stable

System separation info pantograph lowered
type: DatatypeProperty
type: FunctionalProperty
domain: System separation info
range: boolean
SHACL shape validation rule: SystemSeparationInfoPantographLowered
created: 2023-04-05
modified: 2025-03-11
comment: Part of the system separation info of a track that shows whether the pantograph has to be lowered. The system separation info is the Indication of required several information on system separation.
term status: stable

System separation info switch off breaker
type: DatatypeProperty
type: FunctionalProperty
domain: System separation info
range: boolean
SHACL shape validation rule: SystemSeparationInfoSwitchOffBreaker
created: 2023-04-05
modified: 2025-02-18
modified: 2025-03-11
replaces: (deprecated) Information on system separation
comment: Part of the system separation info of a track that shows whether the breaker has to be switched off. The system separation info is the Indication of required several information on system separation.
term status: stable

T_NVCONTACT
type: DatatypeProperty
sub property of: ETCS National Values
type: FunctionalProperty
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: Datatype
  on datatype: unsignedInt
  with restrictions:
    min inclusive: 0
  with restrictions:
    max inclusive: 255
applicable: Y/N/NYA
dependency note: A value has to be provided when ETCS is present (a value is provided on 1.1.1.3.2.1).
format note: NNN, with N as a digit from 0 to 9. Value NNN = 255 means ∞ (infinity), so values cannot be higher.
legal deadline: 12 months after publication of Article 7 Guide
RINF index: 1.1.1.3.2.16.8
RINF index: 1.2.1.1.1.16.8
SHACL shape validation rule: TNvcontact
SHACL shape validation rule: TNvcontactApplicability
TSI operation appendix D3 index: 1.5.8
Unit of measure: SEC
created: 2022-11-07
modified: 2023-03-14
modified: 2024-04-18
modified: 2024-12-05
modified: 2025-02-28
relation: European Train Control System (ETCS) level
source: oj
comment: Maximum time without a safe message from Radio Block Center before train reacts in seconds. According to the specification referenced in Appendix A-1, index [C]
term status: stable
scope note: Precision: [NNN], with N a decimal number (0÷9), NNN = 255 means ∞ seconds, so values cannot be higher. See: TSI CCS (Subset 26, chapter 7. 7.5.1.148 T_NVCONTACT)

T_NVOVTRP
type: DatatypeProperty
sub property of: ETCS National Values
type: FunctionalProperty
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: Datatype
  on datatype: unsignedInt
  with restrictions:
    min inclusive: 0
  with restrictions:
    max inclusive: 255
applicable: Y/N/NYA
dependency note: A value has to be provided when ETCS is present (a value is provided on 1.1.1.3.2.1).
format note: NNN, with N as a digit from 0 to 9. Value NNN = 255 means ∞ (infinity), so values cannot be higher.
legal deadline: 12 months after publication of Article 7 Guide
RINF index: 1.1.1.3.2.16.6
RINF index: 1.2.1.1.1.16.6
SHACL shape validation rule: TNvovtrp
SHACL shape validation rule: TNvovtrpApplicability
TSI operation appendix D3 index: 1.5.6
Unit of measure: SEC
created: 2022-11-07
modified: 2023-03-14
modified: 2024-04-18
modified: 2024-12-05
modified: 2025-02-28
relation: European Train Control System (ETCS) level
source: oj
comment: Maximum time for overriding the train trip in seconds. According to the specification referenced in Appendix A-1, index [C]
term status: stable
scope note: Precision: [NNN], with N a decimal number (0÷9) See: TSI CCS (Subset 26, chapter 7. 7.5.1.149 T_NVOVTRP)

OP primary location code
type: DatatypeProperty
sub property of: Identifier
domain: Operational Point
range: string
created: 2020-07-29
is replaced by: primary location
is replaced by: primary location code
modified: 2024-01-08
modified: 2024-06-03
modified: 2025-02-18
comment: Not used anymore. It has been replaced by era:primaryLocationCode.
comment: Primary location code developed for information exchange in accordance with the TSIs relating to the telematics applications subsystem
deprecated: true
term status: stable

TEN geographic information system identity (GIS ID)
type: DatatypeProperty
sub property of: Performance parameter
sub property of: Identifier
type: FunctionalProperty
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: string
XML name: IPP_TENGISID
applicable: Y/N
legal deadline: 1 January 2021
RINF index: 1.1.1.1.2.1.2
SHACL shape validation rule: TenGISId
SHACL shape validation rule: TenGISIdApplicability
created: 2021-08-03
modified: 2024-01-08
modified: 2024-09-19
modified: 2025-09-03
comment: Indication of the GIS identity (GIS ID) of the section of TEN-T database to which the track belongs
term status: stable
scope note: 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

Thermal capacity distance
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: double
ERATV index: 4.7.2.1.4
Unit of measure: KiloM
created: 2020-08-24
modified: 2020-11-03
modified: 2024-06-26
comment: Thermal capacity distance. If no reference case is indicated.
term status: stable

Thermal capacity gradient
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: double
ERATV index: 4.7.2.1.3
created: 2020-08-24
modified: 2020-11-03
comment: Thermal capacity gradient. If no reference case is indicated.
term status: stable

Thermal capacity speed
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: double
ERATV index: 4.7.2.1.2
created: 2020-08-24
modified: 2020-11-03
comment: Thermal capacity speed. If no reference case is indicated.
term status: stable

Thermal capacity time
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: integer
ERATV index: 4.7.2.1.5
created: 2020-08-24
modified: 2020-11-03
comment: Thermal capacity time. If no reference case is indicated.
term status: stable

Indication whether tilting functions are supported by ETCS
type: DatatypeProperty
range: boolean
RINF index: 1.1.1.3.12.1
SHACL shape validation rule: TiltingSupported
created: 2021-08-09
modified: 2023-03-14
comment: Deprecated according to the amendment to the Regulation (EU) 2019/777. Indication whether tilting functions are supported by ETCS.
deprecated: true
term status: stable

Total vehicle mass
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: integer
ERATV index: 4.5.5
created: 2021-08-26
modified: 2021-08-26
comment: Total vehicle mass (for each vehicle of the unit), given in kg.
term status: stable

Track parameters
type: DatatypeProperty
sub property of: Infrastructure subsystem
type: FunctionalProperty
RINF index: 1.1.1.1.4
RINF index: 1.2.1.0.4
created: 2024-10-31

Running track generic information
type: DatatypeProperty
sub property of: RINF Technical characteristic
RINF index: 1.1.1.0.0
created: 2025-03-11

Identification of track
type: DatatypeProperty
sub property of: Running track generic information
sub property of: Identifier
type: FunctionalProperty
domain: Running track
range: string
XML name: OPTrackIdentification
XML name: SOLTrackIdentification
applicable: Y
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.1.1.0.0.1
RINF index: 1.2.1.0.0.2
SHACL shape validation rule: NoRepeatedTrackIdsOP
SHACL shape validation rule: NoRepeatedTrackIdsSoL
SHACL shape validation rule: TrackId
TSI operation appendix D2 index: 2.2.1.1
created: 2021-09-09
modified: 2024-01-08
modified: 2024-09-19
modified: 2025-03-08
modified: 2025-03-11
source: oj
comment: Unique track identification or unique track number within operational point or section of line
term status: stable
scope note: 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).

Track resistance to applied loads
type: DatatypeProperty
sub property of: Infrastructure subsystem
RINF index: 1.1.1.1.6
created: 2024-10-31

Train control switch over special conditions
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: string
ERATV index: 4.13.1.6
created: 2021-08-31
modified: 2021-08-31
comment: Special conditions implemented on-board to switch over between different train protection control and warning systems. Given as combination of systems installed on board ('System XX'_'System YY').
term status: stable

Train detection systems defined based on frequency bands
type: DatatypeProperty
sub property of: Control-command and signalling subsystem
RINF index: 1.1.1.3.4
RINF index: 1.2.1.1.3
created: 2024-10-31

Train integrity confirmation from on-board (not from driver) necessary for line access
type: DatatypeProperty
sub property of: TSI compliant train protection system (ETCS)
type: FunctionalProperty
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: Datatype
  one of: N
  one of: Optional
  one of: Y
applicable: Y/N/NYA
dependency note: A value has to be provided when ETCS Level 2 is present, ETCS Baseline > 4 MR1 and IM confirms train integrity function is required).
dependency note: Parameter only applicable when ETCS Baseline > 4 MR1 with operation requiring train integrity.
legal deadline: 12 months after publication of Article 7 Guide for OP tracks
legal deadline: 16 January 2020
RINF index: 1.1.1.3.2.8
RINF index: 1.2.1.1.1.8
SHACL shape validation rule: TrainIntegrityOnBoardRequired
TSI operation appendix D2 index: 3.4.11
used in RCC calculations: true
created: 2020-08-31
modified: 2021-09-12
modified: 2024-04-18
modified: 2025-02-28
modified: 2025-03-04
source: oj
comment: Indication whether train confirmation from on-board is required to access the line for safety reasons.
term status: stable
scope note: 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))

Transitions between systems
type: DatatypeProperty
sub property of: Control-command and signalling subsystem
RINF index: 1.1.1.3.8
RINF index: 1.2.1.1.7
created: 2024-10-31

Transportable on ferry
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: boolean
ERATV index: 4.8.8
created: 2021-08-31
modified: 2021-08-31
comment: Indicates the suitability for transport on ferries.
term status: stable

Tsi compliant
type: DatatypeProperty
range: boolean
created: 2020-11-03
modified: 2023-01-23
comment: Indicates if a certain property is TSI compliant.The reason for deprecation is that it is used in SKOS "OtherPantographHeads" and "TsiPantographHeads" to indicate in the first case if a SKOS concept is not tsiCompliant (false) and in the second case that the concept is tsiCompliant (true). These two SKOS were originally one SKOS, "PantographHeads". Currently with the two SKOS the property is redundant.
deprecated: true
term status: stable

TSI compliant radio (RMR)
type: DatatypeProperty
sub property of: Control-command and signalling subsystem
RINF index: 1.1.1.3.3
RINF index: 1.2.1.1.2
created: 2024-10-31

TSI compliant train protection system (ETCS)
type: DatatypeProperty
sub property of: Control-command and signalling subsystem
RINF index: 1.1.1.3.2
RINF index: 1.2.1.1.1
created: 2024-10-31

Existence and TSI compliance of rules for magnetic fields emitted by a vehicle
type: DatatypeProperty
sub property of: Parameters related to electromagnetic interferences
type: FunctionalProperty
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: boolean
applicable: Y/N/NYA
dependency note: 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.
format note: Y/N
legal deadline: 12 months after publication of Article 7 Guide for OP tracks
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.1.1.3.9.1
RINF index: 1.2.1.1.8.1
SHACL shape validation rule: TsiMagneticFields
SHACL shape validation rule: TsiMagneticFieldsApplicability
created: 2024-04-18
modified: 2024-09-19
modified: 2025-02-18
modified: 2025-02-28
relation: Type of train detection system
replaces: Existence and TSI compliance of rules for magnetic fields emitted by a vehicle
source: oj
comment: Indication whether rules exist and are compliant with the TSI.
term status: stable
scope note: 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.

TSI compliance of in-service values for switches and crossings
type: DatatypeProperty
sub property of: Switches and crossings
type: FunctionalProperty
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: boolean
XML name: ISC_TSISwitchCrossing
applicable: Y
format note: in XML: Y/N
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.1.1.1.5.1
SHACL shape validation rule: TSISwitchCrossing
created: 2021-08-03
modified: 2021-09-10
modified: 2024-09-19
modified: 2025-02-28
source: http://data.europa.eu/eli/reg/2014/1299/2023-09-28
comment: Switches and crossings are maintained to in service limit dimension as specified in TSI.
see also: INF TSI: 4.2.5 and 4.2.8.6
term status: stable
scope note: If for existing track at least one parameter has less strict value than specified in the TSI, then 'N' (false) shall be selected.

Existence and TSI compliance of limits in harmonics in the traction current of vehicles
type: DatatypeProperty
sub property of: Parameters related to electromagnetic interferences
type: FunctionalProperty
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: boolean
applicable: Y/N/NYA
legal deadline: 12 months after publication of Article 7 Guide for OP tracks
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.1.1.3.9.2
RINF index: 1.2.1.1.8.2
SHACL shape validation rule: TsiTractionHarmonics
SHACL shape validation rule: TsiTractionHarmonicsApplicability
created: 2024-04-18
modified: 2024-09-19
modified: 2025-02-18
relation: Type of train detection system
replaces: Existence and TSI compliance of limits in harmonics in the traction current of vehicles
source: oj
comment: Indication whether rules exist and are compliant with the TSI.
term status: stable
scope note: 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

Tunnel
type: DatatypeProperty
sub property of: Infrastructure subsystem
RINF index: 1.1.1.1.8
RINF index: 1.2.1.0.5
RINF index: 1.2.2.0.5
created: 2024-10-31

Tunnel identification
type: DatatypeProperty
sub property of: Tunnel
sub property of: Identifier
type: FunctionalProperty
domain: Tunnel
range: string
XML name: OPSidingTunnelIdentification
XML name: OPTrackTunnelIdentification
XML name: SOLTunnelIdentification
applicable: Y
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.1.1.1.8.2
RINF index: 1.2.1.0.5.2
RINF index: 1.2.2.0.5.2
SHACL shape validation rule: TunnelIdentification
TSI operation appendix D2 index: 3.2.3
created: 2021-08-03
modified: 2021-09-13
modified: 2024-09-19
modified: 2025-03-08
source: oj
comment: Unique tunnel identification or unique tunnel number within Member State
term status: stable
scope note: 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

(deprecated) End of tunnel kilometer
type: DatatypeProperty
range: double
XML name: SOLTunnelEnd
RINF index: 1.1.1.1.8.4
created: 2023-03-29
is replaced by: End of tunnel kilometer
modified: 2024-02-05
modified: 2024-09-19
comment: Part of the End of tunnel that indicates the km of the line at the end of a tunnel. The End of tunnel is the Geographical coordinates in decimal degrees and km of the line at the end of a tunnel. The reason for deprecation is that the property is now a subproperty of lineReference in order to represent the kilometer in relation to a national railway line
deprecated: true
term status: stable

(deprecated) Start of tunnel kilometer
type: DatatypeProperty
range: double
created: 2023-03-29
is replaced by: Start of tunnel kilometer
modified: 2024-02-05
modified: 2024-09-19
deprecated: true
term status: stable

Type version number
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: string
created: 2020-11-22
modified: 2020-11-22
comment: Serial number that identifies a vehicle type.
term status: stable

Umax2 for the French network
type: DatatypeProperty
sub property of: Contact line system
type: FunctionalProperty
domain: Contact Line System
range: integer
XML name: ECS_Umax2
applicable: Y/N
dependency note: When `not electrified` is chosen in parameter 1.1.1.2.2.1.1, then this parameter is not applicable.
legal deadline: 16 January 2020
RINF index: 1.1.1.2.2.1.3
SHACL shape validation rule: Umax2
Unit of measure: http://qudt.org/vocab/unit/V
used in RCC calculations: true
created: 2020-08-24
modified: 2024-01-08
modified: 2024-09-25
modified: 2025-02-28
relation: Type of contact line system
comment: Highest non-permanent voltage (Umax2) for France on lines not compliant with values defined in the EN50163:2004+A1:2007+A2:2020+A3:2022
see also: ENE TSI: 4.2.4.1
term status: stable
scope note: 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

Unique OP ID
type: DatatypeProperty
sub property of: Operational point generic information
sub property of: Identifier
type: FunctionalProperty
domain: Operational Point
range: string
XML name: UniqueOPID
applicable: Y
format note: 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
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.2.0.0.0.2
SHACL shape validation rule: BorderPointUopidPrefix
SHACL shape validation rule: BorderPointValidCodeAndCoordinates
SHACL shape validation rule: UopidP
TSI operation appendix D2 index: 2.2.2
created: 2020-07-29
modified: 2024-01-08
modified: 2024-09-19
modified: 2025-02-24
modified: 2025-03-11
source: oj
comment: Code composed of country code and alphanumeric operational point code.
see also: ISO 3166-1 alpha 2
term status: stable
scope note: 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.

GSM-R use of group 555
type: DatatypeProperty
sub property of: TSI compliant radio (RMR)
type: FunctionalProperty
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: boolean
applicable: Y/N/NYA
dependency note: GSM-R and ETCS L2 must be installed for this parameter to be applicable.
ERATV index: 4.13.2.12
legal deadline: 12 months after publication of Article 7 Guide for OP tracks
legal deadline: 16 January 2020
RINF index: 1.1.1.3.3.4
RINF index: 1.2.1.1.2.4
SHACL shape validation rule: UsesGroup555
SHACL shape validation rule: UsesGroup555Applicability
used in RCC calculations: true
created: 2020-08-31
modified: 2021-09-12
modified: 2024-04-18
modified: 2025-03-04
relation: European Train Control System (ETCS) level
comment: Indication if group 555 is used.
term status: stable
scope note: 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.

V_NVALLOWOVTRP
type: DatatypeProperty
sub property of: ETCS National Values
type: FunctionalProperty
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: Datatype
  on datatype: unsignedInt
  with restrictions:
    min inclusive: 0
  with restrictions:
    max inclusive: 600
applicable: Y/N/NYA
dependency note: A value has to be provided when ETCS is present (a value is provided on 1.1.1.3.2.1).
format note: NNF, with N a decimal number (0 9), NNF must be divisible by 5, so F=(0|5), max. `600`
legal deadline: 12 months after publication of Article 7 Guide
RINF index: 1.1.1.3.2.16.3
RINF index: 1.2.1.1.1.16.3
SHACL shape validation rule: VNvallowovtrp
SHACL shape validation rule: VNvallowovtrpApplicability
TSI operation appendix D3 index: 1.5.3
Unit of measure: KiloM-PER-HR
created: 2022-11-07
modified: 2023-03-14
modified: 2024-09-19
modified: 2024-12-05
relation: European Train Control System (ETCS) level
source: oj
comment: Speed limit allowing the driver to select the override function in km/h According to the specification referenced in Appendix A-1, index [C]
term status: stable
scope note: 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
type: DatatypeProperty
sub property of: ETCS National Values
type: FunctionalProperty
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: Datatype
  on datatype: unsignedInt
  with restrictions:
    min inclusive: 0
  with restrictions:
    max inclusive: 600
applicable: Y/N/NYA
dependency note: A value has to be provided when ETCS is present (a value is provided on 1.1.1.3.2.1).
format note: NNF, with N a decimal number (0 9), NNF must be divisible by 5, so F=(0|5), max. `600`
legal deadline: 12 months after publication of Article 7 Guide
legal deadline: 12 months after publication of Article 7 Guide for OP tracks
RINF index: 1.1.1.3.2.16.4
RINF index: 1.2.1.1.1.16.4
SHACL shape validation rule: VNvsupovtrp
SHACL shape validation rule: VNvsupovtrpApplicability
TSI operation appendix D3 index: 1.5.4
Unit of measure: KiloM-PER-HR
created: 2022-11-07
modified: 2023-03-14
modified: 2024-09-19
modified: 2024-12-05
relation: European Train Control System (ETCS) level
source: oj
comment: Override speed limit to be supervised when the "override" function is active in km/h. According to the specification referenced in Appendix A-1, index [C]
term status: stable
scope note: 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)

Validity end date
type: DatatypeProperty
domain: Infrastructure element
range: date
created: 2022-10-19
deprecated: true
term status: stable
editorial note: To be deprecated with the introduction of temporal entity

Validity start date
type: DatatypeProperty
domain: Infrastructure element
range: date
created: 2022-10-20
deprecated: true
term status: stable
editorial note: To be deprecated with the introduction of temporal entity

Vehicle contact force
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: integer
ERATV index: 4.10.15
created: 2020-08-25
modified: 2020-11-03
comment: Mean contact force.
term status: stable

Vehicle kinematic gauge other
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: string
ERATV index: 4.2.2
created: 2022-05-30
comment: Vehicle kinematic gauge that corresponds to other gauges assessed using the kinematic method
term status: stable

Vehicle max sanding output
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: string
ERATV index: 4.14.2.13
created: 2021-09-01
modified: 2021-09-01
comment: Vehicle Maximum sanding output, given in grams per second.
term status: stable

Vehicle number
type: DatatypeProperty
sub property of: Vehicle technical characteristic
type: FunctionalProperty
domain: Vehicle
range: string
created: 2020-11-24
modified: 2020-11-24
comment: Identification number of a vehicle or wagon.
term status: stable

Vehicle pantograph head
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: string
ERATV index: 4.10.6
created: 2020-08-25
modified: 2020-11-03
comment: Pantograph head geometry (to be indicated for each energy supply system the vehicle is equipped for).
term status: stable

Vehicle series
type: DatatypeProperty
sub property of: Vehicle technical characteristic
domain: Vehicle
range: string
created: 2020-11-22
modified: 2020-11-22
comment: Manufacturing series of a vehicle.
term status: unstable

Vehicle technical characteristic
type: DatatypeProperty

Vehicle type maximum cant deficiency
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Maximum speed and cant deficiency
range: integer
ERATV index: 4.6.4
created: 2023-04-05
modified: 2025-02-18
replaces: Maximum speed and cant deficiency
comment: Part of the combination of maximum speed and maximum cant deficiency for which the vehicle was assessed. Corresponds to the maximum cant deficiency.
term status: stable

Vehicle type maximum speed
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Maximum speed and cant deficiency
range: integer
ERATV index: 4.6.4
created: 2023-04-05
modified: 2025-02-18
replaces: Maximum speed and cant deficiency
comment: Part of the combination of maximum speed and maximum cant deficiency for which the vehicle was assessed. Corresponds to the maximum speed.
term status: stable

Vehicle type technical characteristic
type: DatatypeProperty

Vehicles composing fixed formation
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: integer
ERATV index: 4.1.12
created: 2021-08-25
modified: 2021-08-25
comment: Number of vehicles composing the fixed formation (for fixed formation only). Note: the value is mandatory for all vehicle categories. If the vehicle is composed of only one car, the indicated value shall be '1'.
term status: stable

EC declaration of verification for track relating to compliance with the requirements from TSIs applicable to control, command signalling subsystem
type: DatatypeProperty
sub property of: Declarations of verification for track
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: string
XML name: CDE_ECVerification
applicable: Y/N
format note: CC/RRRRRRRRRRRRRR/YYYY/NNNNNN
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.1.1.3.1.1
SHACL shape validation rule: VerificationCCS
created: 2021-08-08
modified: 2024-01-08
source: oj
comment: Unique number for EC declarations in accordance with Commission Implementing Regulation (EU) 2019/250.
term status: stable
scope note: (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.

EC declaration of verification for track relating to compliance with the requirements from TSIs applicable to energy subsystem
type: DatatypeProperty
sub property of: Declarations of verification for track
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: string
XML name: EDE_ECVerification
applicable: Y/N
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.1.1.2.1.1
SHACL shape validation rule: VerificationENE
created: 2021-08-08
modified: 2024-01-08
comment: Unique number for EC declarations in accordance with Commission Implementing Regulation (EU) 2019/250.
term status: stable

EC declaration of verification for infrastructure element relating to compliance with the requirements from TSIs applicable to infrastructure subsystem
type: DatatypeProperty
sub property of: Declarations of verification for track
domain: Class
  union of: Subset with common characteristics
  union of: Running track
range: string
XML name: IDE_ECVerification
applicable: Y/N
format note: CC/RRRRRRRRRRRRRR/YYYY/NNNNNN
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.1.1.1.1.1
RINF index: 1.2.1.0.1.1
RINF index: 1.2.2.0.1.1
SHACL shape validation rule: VerificationINF
SHACL shape validation rule: VerificationINFS
created: 2021-08-03
modified: 2024-01-08
modified: 2024-09-19
source: http://data.europa.eu/eli/reg/2014/1299/2023-09-28
source: oj
comment: Unique number for EC declarations in accordance with Commission Implementing Regulation (EU) 2019/250.
term status: stable
scope note: 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

EC declaration of verification relating to compliance with the requirements from TSIs applicable to railway tunnel
type: DatatypeProperty
sub property of: Tunnel
domain: Class
  union of: Subset with common characteristics
  union of: Tunnel
range: string
XML name: ITU_ECVerification
applicable: Y/N
format note: CC/RRRRRRRRRRRRRR/YYYY/NNNNNN
legal deadline: In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
RINF index: 1.1.1.1.8.5
RINF index: 1.2.1.0.5.3
RINF index: 1.2.2.0.5.3
SHACL shape validation rule: VerificationSRT
created: 2021-08-03
modified: 2024-01-08
modified: 2024-09-19
source: http://data.europa.eu/eli/reg/2014/1303/2024-01-29
comment: Unique number for EC declarations in accordance with Commission Implementing Regulation (EU) 2019/250.
see also: Document about practical arrangements for transmitting interoperability documents ERA/INF/10-2009/INT
term status: stable
scope note: (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

Voice operational communication implementation
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: string
ERATV index: 4.13.2.6
created: 2021-08-31
modified: 2021-08-31
comment: Voice and operational communication implementation.
term status: stable

Wheel set gauge transformation method
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: string
ERATV index: 4.1.3.b
created: 2021-08-25
modified: 2021-08-25
comment: Wheel gauge transformation method. Defined if more than one wheel gauges have been selected.
term status: stable

Wheelchair sleeping spaces
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: string
ERATV index: 4.12.2.4
created: 2021-08-31
modified: 2021-08-31
comment: Number of wheelchair accessible sleeping places.
term status: stable

Wheelchair spaces
type: DatatypeProperty
sub property of: Vehicle type technical characteristic
domain: Vehicle Type
range: integer
ERATV index: 4.12.2.2
created: 2021-08-31
modified: 2023-01-23
comment: Number of wheelchair spaces.
term status: stable

Identifier
type: DatatypeProperty
range: Literal
comment: An unambiguous reference to the resource within a given context.
example: Examples include International Standard Book Number (ISBN), Digital Object Identifier (DOI), and Uniform Resource Name (URN).

asWKT
type: DatatypeProperty
applicable: Y/N/NYA
legal deadline: 12 months after publication of Article 7 Guide
RINF index: 1.1.0.0.1.1
RINF index: 1.1.1.0.1.1
RINF index: 1.1.1.3.14.6
RINF index: 1.2.0.0.0.5
RINF index: 1.2.1.0.8.5
SHACL shape validation rule: AsWKT
SHACL shape validation rule: BorderPointValidCoordinates
SHACL shape validation rule: BorderPointValidCoordinatesViaNetReference
TSI operation appendix D2 index: 2.1.1
TSI operation appendix D2 index: 2.1.2
TSI operation appendix D2 index: 2.2.2
TSI operation appendix D2 index: 3.2.5
contributor: Matthew Perry
creator: OGC GeoSPARQL 1.0 Standard Working Group
date: 2011-06-16
comment: The WKT serialization of a geometry
comment: Well Known Text line string representing the geographical shape of the track
comment: Well Known Text polygonal shape
see also: ERA - TWG Route Book
alternative label: Accurate geographical description
alternative label: Industrial risks locations where it is dangerous for the driver to step out

identifier
type: DatatypeProperty
sub property of: notation
domain: Organization
comment: Código o identificador, como por ejemplo el CIF de una empresa, que permite identificar de forma inequívoca a una organización. Existen muchos códigos de identificación tanto nacionales como internacionales. Esta ontología no obliga al uso de ningún esquema en concreto. Los códigos de identificación utilizados en cada caso se deberían indicar mediante el uso de la propiedad “datatype” del valor del identificador. El uso de la propiedad “datatype” para especificar el esquema de notación utilizado está en consonancia con las buenas prácticas recomendadas para el uso de la propiedad `skos:notation`, de la que esta propiedad es una especialización. @es
comment: Donne un identifiant, comme par exemple le numéro d'enregistrement d'une entreprise, qui peut être utilisé comme identifiant unique pour l'Organisation. De nombreux schémas nationaux et internationaux sont disponibles. Cette ontologie reste neutre par rapport au schéma utilisé. Le schéma particulier utilisé devrait être indiqué par le `datatype` de la valeur de l'identifiant. Utiliser les datatypes pour distinguer les schémas de notation est cohérent avec les bonnes pratiques pour `skos:notation` dont cette propriété est une spécialisation. @fr
comment: Gives an identifier, such as a company registration number, that can be used to used to uniquely identify the organization. Many different national and international identier schemes are available. The org ontology is neutral to which schemes are used. The particular identifier scheme should be indicated by the datatype of the identifier value. Using datatypes to distinguish the notation scheme used is consistent with recommended best practice for `skos:notation` of which this property is a specialization.
comment: Indica un identificatore univoco per l'organizzazione, come ad esempio la partita IVA di un'azienda. Molti schemi di identificazione a livello nazionale e internazionale sono disponibili allo scopo. L'ontologia ORG è neutrale rispetto allo schema da utilizzare. Lo schema di identificazione dovrebbe essere indicato dal datatype del valore dell'identificatore. L'uso del datatype per distinguere lo schema di identificazione è coerente con le best practice per `skos:notation`, di cui questa proprietà è una specializzazione. @it
comment: 組織を一意に識別するために使用できる会社登録番号などの識別子を与えます。 @ja
label: identifiant @fr
label: identificatore @it
label: tiene identificador @es

name
type: DatatypeProperty
domain: Thing
range: Literal
comment: A name for some thing.
term status: testing

Body
type: Class
subclass of: Class
  union of: Organization
  union of: Person
disjoint with: Infrastructure element
disjoint with: Organisation Role
SHACL shape validation rule: BodyShape
created: 2024-06-03
modified: 2025-02-18
replaces: Infrastructure manager
replaces: (deprecated) Manufacturer
replaces: (deprecated) Vehicle Keeper
comment: Is an organisation or a physical person

Bridge
type: Class
subclass of: Infrastructure element
disjoint with: Hot Axle Box Detector
disjoint with: Kilometric Post
disjoint with: Level crossing
disjoint with: Operational Point
disjoint with: Platform edge
disjoint with: Primary Location
disjoint with: Radio Block Center
disjoint with: Running track
disjoint with: Section Of Line
disjoint with: Siding
disjoint with: Signal
disjoint with: Special area
disjoint with: Switch
disjoint with: Track
disjoint with: Tunnel
modified: 2025-01-30
modified: 2025-03-01
comment: It is a structure constructed for the exclusive purpose of carrying railroad traffic across an obstruction. It can be used for defining non-stopping areas, big metal mass, resistance to traffic load etc.

Certificate
type: Class
created: 2022-06-15
modified: 2022-06-15
modified: 2024-10-24
comment: Certificate of a vehicle type. Can be in one of the following states: Amended, New, Suspended, Withdrawn.
deprecated: true
term status: stable

Subset with common characteristics
type: Class
SHACL shape validation rule: CommonCharacteristicsSubsetShape
created: 2022-11-04
modified: 2023-03-14
modified: 2024-10-31
modified: 2025-08-26
comment: A set of different infrastructure objects sharing the same common technical characteristics. The parameters may not be restricted to only one railway subsystem, but it can include common characteristics from each one of them (infrastructure, energy, track-side CCS)
term status: stable

Contact Line System
type: Class
SHACL shape validation rule: ContactLineSystemShape
created: 2021-08-04
modified: 2021-08-04
comment: System that is used to transmit electrical energy to road or rail vehicles.
term status: stable

ERA Document
type: Class
subclass of: Document
SHACL shape validation rule: DocumentShape
created: 2024-04-23
comment: Document in any of the ERA systems, e.g. reference document in RINF.
term status: stable

ETCS
type: Class
SHACL shape validation rule: ETCSShape
created: 2021-08-07
modified: 2021-08-07
comment: TSI compliant train protection system ERTMS / ETCS application level and baseline related to the track side equipment.
term status: stable

ERA Feature
type: Class
subclass of: Feature
disjoint with: Temporal Feature
SHACL shape validation rule: FeatureShape
created: 2022-07-07
modified: 2022-10-27
comment: Class that encompasses the features that are part of the physical infrastructure (class InfrastructureElement) and the topological objects (class TopologicalObject). It is a subclass of the geographical Feature class that has a spatial representation.

Section with train detection limitation
type: Class
SHACL shape validation rule: FrenchTrainDetectionSystemLimitationShape
created: 2023-04-05
comment: Specific for route compatibility check on French network.
term status: stable

Hot Axle Box Detector
type: Class
subclass of: Infrastructure element
disjoint with: Kilometric Post
disjoint with: Level crossing
disjoint with: Operational Point
disjoint with: Platform edge
disjoint with: Primary Location
disjoint with: Radio Block Center
disjoint with: Section Of Line
disjoint with: Signal
disjoint with: Special area
disjoint with: Switch
disjoint with: Track
disjoint with: Tunnel
created: 2025-02-20
modified: 2025-03-01
comment: A trackside Hot Axle Box Detector (HABD), necessary for the route compatibility check. Specific for the French, Italian and Swedish networks

Infrastructure element
type: Class
subclass of: ERA Feature
SHACL shape validation rule: InfrastructureElementShape
created: 2022-07-07
modified: 2022-10-27
modified: 2024-10-28
modified: 2025-04-30
comment: This class encompasses all those classes that represent features that are implemented in the European railway infrastructure. It is a subclass of the ERA Feature that has a spatial representation. It covers tracks, platforms, signals, tunnels, operational points, and sections of line. A feature that belongs to the infrastructure can be abstracted (hasAbstraction) as a topological object. It also is related to the infrastructure manager through the property infrastructureMgr.

Infrastructure manager
type: Class
subclass of: Organization
is replaced by: Body
comment: (deprecated) The infrastructure manager owns and operates the railway network and related infrastructure.
deprecated: true
scope note: See point (2) of Article 3 of Directive 2012/34/EU of the European Parliament and of the Council establishing a single European railway area.

Kilometric Post
type: Class
subclass of: Infrastructure element
disjoint with: Level crossing
disjoint with: Operational Point
disjoint with: Platform edge
disjoint with: Primary Location
disjoint with: Radio Block Center
disjoint with: Section Of Line
disjoint with: Signal
disjoint with: Special area
disjoint with: Switch
disjoint with: Track
disjoint with: Tunnel
SHACL shape validation rule: KilometricPostShape
created: 2024-11-29
modified: 2025-01-30
modified: 2025-03-01
comment: Represents a kilometric post in the linear positioning system.

Level crossing
type: Class
subclass of: Infrastructure element
disjoint with: Operational Point
disjoint with: Platform edge
disjoint with: Primary Location
disjoint with: Radio Block Center
disjoint with: Running track
disjoint with: Section Of Line
disjoint with: Siding
disjoint with: Signal
disjoint with: Special area
disjoint with: Switch
disjoint with: Track
disjoint with: Tunnel
modified: 2025-01-30
modified: 2025-03-01
comment: A level crossing is an intersection where a railway line crosses a road or a path at the same level. It can be used for the implementation of the ETCS trackside or to identify potential collision scenarios

(deprecated) Railway location
type: Class
created: 2021-01-29
is replaced by: Linear Positioning System
modified: 2021-01-29
modified: 2024-10-24
modified: 2024-11-29
comment: A reference to a specific railway line.
deprecated: true
term status: stable
alternative label: Line reference

Linear Element
type: Class
subclass of: Net element
disjoint with: Non-Linear Element
SHACL shape validation rule: LinearElementShape
modified: 2024-11-29
modified: 2025-03-01
comment: Pieces of tracks composing the topology
scope note: This class represents an edge in the topological graph. It represents a linear element in the network.

Linear Element Section
type: Class
subclass of: Linear Element
SHACL shape validation rule: LinearElementSectionShape
comment: Represents a section of a linear element.
scope note: A linear element section is a finer granularity of a linear element, representing a specific portion of it. This concept is introduced to address the cases when a linear element needs to be split such as a part of it is used by a net referencing (more in the paragraph describing the positioning on the network). By using start and end offsets measured from origin of the element in ascending order, sections eliminate the need for intrinsic coordinates and instead rely on distances along the linear element.

Linear Positioning System
type: Class
disjoint with: Linear Positioning System Coordinate
SHACL shape validation rule: LinearPositioningSystemShape
created: 2024-11-29
modified: 2025-02-18
replaces: (deprecated) Railway location
comment: Represents a linear positioning system used for referencing positions on the network. It can also represent a sequence of one or more sections of line, used for regular railway operations.

Linear Positioning System Coordinate
type: Class
SHACL shape validation rule: LinearPositioningSystemCoordinateShape
created: 2024-11-29
comment: Represents coordinates in a linear positioning system.

Lineside indications of distance
type: Class
SHACL shape validation rule: LinesideDistanceIndicationShape
created: 2024-12-12
modified: 2025-01-30
comment: Frequency, appearance and positioning of a sign indicating distance as reference post. Two types of signs are normally available: kilometre post and hectometre post. - A kilometre post is a lineside sign indicating the distance from a specific point, usually being the starting point of the railway line. - A hectometre post is a lineside sign indicating a relative distance.

Load capability
type: Class
SHACL shape validation rule: LoadCapabilityShape
created: 2023-03-14
modified: 2024-09-19
modified: 2025-02-18
replaces: Load Capability
comment: A combination of the line category and speed at the weakest point of the track. Each track can have several load capability (structured) values, and each one has values for load model line category and load model speed.
comment: This class together with properties loadCapabilityLineCategory and loadCapabilitySpeed replaces the previous loadCapability SKOS property.
term status: stable
scope note: 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”. It represents the ability of the infrastructure to withstand the vertical loads imposed by vehicles on the track for regular service as a combination of Line Category with a permitted speed according to EN 15528:2021 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:20021categories 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)

(deprecated) Manufacturer
type: Class
subclass of: Organization
created: 2020-11-19
is replaced by: Body
is replaced by: manufactured by
modified: 2020-11-19
modified: 2024-06-03
comment: (deprecated) Replaced by the era:Body class and era:manufacturer property. A company or organization that manufactures vehicles.
deprecated: true
term status: stable

Maximum magnetic field
type: Class
SHACL shape validation rule: MaximumMagneticFieldShape
created: 2023-03-14
relation: Type of train detection system
term status: stable

Maximum speed and cant deficiency
type: Class
created: 2023-04-05
modified: 2025-02-18
replaces: Maximum speed and cant deficiency
comment: Combination of maximum speed and maximum cant deficiency for which the vehicle was assessed.
term status: stable

(deprecated) Min axle load vehicle category
type: Class
created: 2023-01-25
modified: 2023-03-14
deprecated: true
term status: stable

Minimum Vehicle Impedance
type: Class
SHACL shape validation rule: MinVehicleImpedanceShape
created: 2024-05-30
source: oj
comment: Impedance as defined in the TSI CCS (Annex I, Appendix A, Table A.2 -Index 77). Minimum vehicle impedance (between wheels and pantograph) (only for vehicles equipped for 1500V or 3000V DC). Per Voltage: [1500]: [CCCC]+[ZZZZ], with input capacitance [CCCC](Cin) and input impedance [ZZZZ](Zin) [3000]: [CCCC]+[ZZZZ], idem.
term status: stable
scope note: The MinVehicleImpedance class is applicable for track circuits.

Minimum radius of vertical curve
type: Class
SHACL shape validation rule: MinimumVerticalRadiusShape
created: 2021-12-12
term status: stable
scope note: Presentation of parameter 1.2.2.0.3.3 'Minimum radius of vertical curve'

(deprecated) National railway line
type: Class
subclass of: Infrastructure element
disjoint with: Primary Location
created: 2021-01-25
modified: 2021-08-03
modified: 2024-11-29
comment: Railway line within a member state. A line is a sequence of one or more sections of line, which connects operational points and which may consist of several tracks used for regular railway operation.
deprecated: true
term status: stable

Net Area Reference
type: Class
subclass of: Net Basic Reference
SHACL shape validation rule: NetAreaReferenceShape
created: 2024-11-29
comment: Represents an area reference in the network.
example: Example: non-stopping area, cross section area, area of implementation of GPRS etc.
scope note: It is used for infrastructure elements positioned in relation to the topology as a subnetwork. (e.g.: tunnels, non-stopping area, stations etc.)

Net Basic Reference
type: Class
subclass of: ERA Feature
SHACL shape validation rule: NetBasicReferenceShape
created: 2024-11-29
comment: Basic positioning reference within the ERA ontology. It represents different types of geographical locations. Geographical coordinates are provided according to the standard World Geodetic System (WGS84).

Net element
type: Class
subclass of: ERA Feature
disjoint with: Net Relation
SHACL shape validation rule: NetElementShape
created: 2024-11-29
modified: 2025-04-30
comment: It is a representation of all building blocks of the topology. It references an associated topological network element.

Net Linear Reference
type: Class
subclass of: Net Basic Reference
SHACL shape validation rule: NetLinearReferenceShape
created: 2024-11-29
comment: Represents a linear reference in the network.
example: Example: tracks, tunnels, bridges, platform edges etc.
scope note: It is used for infrastructure elements positioned in relation to the topology as a line, or along a path. (e.g.: tracks, bridges, platform edges, etc.)

Net Point Reference
type: Class
subclass of: Net Basic Reference
SHACL shape validation rule: NetPointReferenceShape
created: 2024-11-29
comment: Represents a point reference in the network.
scope note: It is used for infrastructure elements positioned in relation to the topology as a point. (e.g.: signals, ETCS balises, buffer stops, etc.)

Net Relation
type: Class
subclass of: Restriction
  on property: Element A
  qualified cardinality: 1
  on class: Linear Element
subclass of: Restriction
  on property: Element B
  qualified cardinality: 1
  on class: Linear Element
subclass of: Restriction
  on property: Navigability
  qualified cardinality: 1
  on class: Concept
subclass of: Restriction
  on property: is on origin of element A
  qualified cardinality: 1
  on data range: boolean
subclass of: Restriction
  on property: is on origin of element B
  qualified cardinality: 1
  on data range: boolean
SHACL shape validation rule: NetRelationShape
created: 2024-11-29
modified: 2025-03-10
comment: Defines a relation between two elements.
scope note: Connectivity and the navigability between consecutive linear elements are resolved by using net relations. It models how different elements are related to each other, representing a transition from one element to another. Net relations specify where two linear elements connect. This could be at the origin of one element, the end of another, or even at specific offsets along their lengths. For example, two tracks might connect at a junction, with one ending at offset 1500 and the other beginning at offset 0. NetRelation explicitly models these connections by linking two linear elements (elementA and elementB) and defining their physical or logical relationship. Net relations also specify the permitted directions of travel: • 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. To make this even more precise, net relations include information about whether the connection is at the origin of each element. For example, a relation might indicate that Track A ends at its origin (offset 0) and connects to Track B at its start (isOnOriginOfElementA and isOnOriginOfElementB).

Non-Linear Element
type: Class
subclass of: Net element
SHACL shape validation rule: NonLinearElementShape
created: 2024-11-29
comment: Represents a non-linear element in the network.
scope note: Non-linear elements complement the linear structure by serving as connection or interaction points. They represent features such as stations, depots, or complex junctions. They often serve as aggregation points for linear elements, where multiple tracks meet or like logical entities that support operations like passenger boarding or train storage. These elements may optionally aggregate linear elements.

Operational Point
type: Class
subclass of: Infrastructure element
disjoint with: Platform edge
disjoint with: Primary Location
disjoint with: Radio Block Center
disjoint with: Section Of Line
disjoint with: Signal
disjoint with: Special area
disjoint with: Switch
disjoint with: Track
disjoint with: Tunnel
SHACL shape validation rule: OperationalPointShape
created: 2020-07-29
modified: 2022-07-07
modified: 2025-01-30
modified: 2025-03-01
comment: An operational point (OP) means any location for train service operations, where train services may begin and end or change route, and where passenger or freight services may be provided; operational point also means any location at boundaries between Member States or infrastructure managers.
term status: stable

Organisation Role
type: Class
SHACL shape validation rule: OrganisationRoleShape
comment: Represents an n-ary relationship between a Body and a role

Orientation
type: Class
SHACL shape validation rule: OrientationShape
comment: Represents the orientation of a railway object in relation to a carrier linear element. It can be described by direction, orientation and side.

Parameter applicability
type: Class
subclass of: Temporal Feature
SHACL shape validation rule: ParameterApplicabilityShape
modified: 2024-10-28
comment: Applicability interval 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.

Phase info
type: Class
SHACL shape validation rule: PhaseInfoShape
created: 2023-04-05
modified: 2025-02-18
replaces: Information on phase separation
comment: Indication of required several information on phase separation.
term status: stable

Platform edge
type: Class
subclass of: Infrastructure element
disjoint with: Primary Location
disjoint with: Radio Block Center
disjoint with: Running track
disjoint with: Section Of Line
disjoint with: Siding
disjoint with: Signal
disjoint with: Special area
disjoint with: Switch
disjoint with: Track
disjoint with: Tunnel
SHACL shape validation rule: PlatformEdgeShape
created: 2021-08-02
modified: 2023-11-10
modified: 2025-01-30
modified: 2025-03-01
comment: Platform for the purpose of RINF is understood as a platform edge. A platform concerns only the part of the structure neighbouring to the track (interfaced with trains).
term status: stable

Primary Location
type: Class
subclass of: Infrastructure element
subclass of: Restriction
  on property: net reference
  all values from: Net Point Reference
disjoint with: Radio Block Center
disjoint with: Section Of Line
disjoint with: Signal
disjoint with: Special area
disjoint with: Subsidiary location
disjoint with: Switch
disjoint with: Track
disjoint with: Tunnel
SHACL shape validation rule: PrimaryLocationShape
modified: 2024-10-28
modified: 2025-03-01
modified: 2025-06-06
comment: Primary Location is a place used by IM to define a path for a train in TAF/TAP TSI framework/messages. This location is a rail point inside the rail network where train starts, ends, stops, or runs through or change line. This location must be managed by an Infrastructure Manager (IM) identified by company code. Primary locations are identified by single and unique Primary Location codes. Primary location code is allocated based on processes defined by national entity. Primary location codes are used in any kind of TAF/TAP communication. See: Handbook 9.3.3 / page 60
example: Primary locations are for example: stations, yards, halts, handover points, border points, open access terminals.

Radio Block Center
type: Class
subclass of: Infrastructure element
disjoint with: Section Of Line
disjoint with: Signal
disjoint with: Special area
disjoint with: Switch
disjoint with: Track
disjoint with: Tunnel
SHACL shape validation rule: RadioBlockCenterShape
source: oj
comment: ETCS trackside centralised unit controlling ETCS train movements in level 2. A centralised safety unit that receives train position information via radio and sends movement authorities via radio to trains.

Requirements for number of raised pantographs and spacing between them, at the given speed
type: Class
SHACL shape validation rule: RaisedPantographsDistanceAndSpeedShape
created: 2023-04-05
comment: 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. Each track can have several raised pantographs per train allowed (structured) values, and each one has values for number of pantographs, minimum distance between pantographs, in metres, and speed considered in km/h.
term status: stable
scope note: This class 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 class can be repeated to present all of them.

Reference border point
type: Class
subclass of: ERA Feature
SHACL shape validation rule: ReferenceBorderPointShape
created: 2024-10-24
modifed: 2025-02-24
replaces: border point of
replaces: Border point information per country
comment: List of reference border points that are specified in the RINF Application Guide.

Running track
type: Class
subclass of: Track
disjoint with: Siding
disjoint with: Signal
disjoint with: Switch
disjoint with: Tunnel
SHACL shape validation rule: RunningTrackShape
created: 2020-07-29
modified: 2022-07-07
modified: 2024-09-19
modified: 2024-11-20
comment: A running track means any track used for train service movements; passing loops and meeting loops on plain line or track connections only required for train operation are not published
term status: stable
scope note: There might be more than one track within the Section of Line, so then the whole set of data for track has to be repeated for each track within the SoL.

Section Of Line
type: Class
subclass of: Infrastructure element
subclass of: Restriction
  on property: national line identification
  qualified cardinality: 1
  on class: Linear Positioning System
subclass of: Restriction
  on property: Operational point at end of section of line
  qualified cardinality: 1
  on class: Operational Point
subclass of: Restriction
  on property: Operational point at start of section of line
  qualified cardinality: 1
  on class: Operational Point
disjoint with: Signal
disjoint with: Special area
disjoint with: Switch
disjoint with: Track
disjoint with: Tunnel
SHACL shape validation rule: SectionOfLineShape
created: 2021-04-02
modified: 2022-07-07
modified: 2024-09-19
modified: 2025-01-30
modified: 2025-03-01
source: oj
comment: A section of line means the part of line between adjacent operational points and may consist of several tracks.
term status: stable
scope note: Each network shall be described using as many SoLs as necessary. Each SoL is generated and identified by OP IDs at start and at end. A SoL only belongs to one Line.

Siding
type: Class
subclass of: Track
disjoint with: Signal
disjoint with: Switch
disjoint with: Tunnel
SHACL shape validation rule: SidingShape
created: 2021-08-10
modified: 2022-10-27
modified: 2024-09-19
modified: 2024-11-20
source: http://data.europa.eu/eli/reg_impl/2019/773/2020-06-16
comment: Sidings are all those tracks where running trains in service movements ends and which are not used for operational routing of a train.
term status: stable
definition: Siding - Any track(s) within an operational point which is not used for operational routing of a train.

Signal
type: Class
subclass of: Infrastructure element
disjoint with: Special area
disjoint with: Switch
disjoint with: Track
disjoint with: Tunnel
SHACL shape validation rule: SignalShape
created: 2021-04-01
modified: 2022-10-27
modified: 2024-09-19
modified: 2025-01-30
modified: 2025-03-01
source: http://data.europa.eu/eli/reg_impl/2019/773/2023-09-28
comment: A railway signal is a visual display device (next to the tracks or via a DMI in the cabin) that conveys instructions or provides advance warning of instructions regarding the driver's authority to proceed.
term status: stable
definition: Apparatus by means of which a conventional visual or acoustic indication is given, generally concerning the movements/movement authorities of railway vehicles.

Special area
type: Class
subclass of: Infrastructure element
disjoint with: Switch
disjoint with: Track
disjoint with: Tunnel
created: 2022-10-27
modified: 2024-04-18
modified: 2025-03-01
source: oj
comment: Encompasses all those areas (outside of the operational gauge) or sections (those in tunnels excluded) which influence operation in the gauge itself, such as - safe areas, - restricted areas (non-stopping areas or industrial risk locations). For these areas in tunnels, use era:SpecialTunnelArea.
term status: stable
definition: Non-stopping Area: Area defined by the Infrastructure Manager where it may not be safe or suitable to stop a train. Safe Area: Area defined by the Infrastructure Manager where it is safe or suitable to stop and evacuate a train. Industrial Risk Area: locations where it is dangerous for the driver to step out.
editorial note: TODO review the definition

Special tunnel area
type: Class
subclass of: Special area
created: 2022-10-27
source: oj
comment: Area or location within a tunnel where there are: - a safe area: a walkway, evacuation and rescue points; - a restricted area (non-stopping area or industrial risk location in a tunnel).
term status: stable
editorial note: TODO review the definition

Subsidiary location
type: Class
subclass of: ERA Feature
subclass of: Restriction
  on property: linked to primary location
  qualified cardinality: 1
  on class: Primary Location
SHACL shape validation rule: SubsidiaryLocationShape
created: 2024-05-24
modified: 2025-03-10
comment: Subsidiary location must be linked to a Primary Location and specifies in more detailed way part, attributes, or usage of Primary location. It may be also a non-rail point or a rail point that is not managed by an Infrastructure Manager (IM). It may be defined by entity having company code according to their needs. The Subsidiary location is optional and dependent upon business needs.

Switch
type: Class
subclass of: Infrastructure element
disjoint with: Track
disjoint with: Tunnel
modified: 2025-01-30
modified: 2025-03-01
source: oj
comment: A unit of track comprising two fixed rails (stock rails) and two movable rails (switch rails) used to direct vehicles from one track to another track.
term status: stable

System separation info
type: Class
SHACL shape validation rule: SystemSeparationInfoShape
created: 2023-04-05
modified: 2025-02-18
replaces: (deprecated) Information on system separation
comment: Indication of required several information on system separation.
term status: stable

Temporal Feature
type: Class
subclass of: Class
  union of: Temporal duration
  union of: Temporal entity
created: 2024-05-24
comment: The union of TemporalDuration that represents a time extent and TemporalEntity that represents a temporal interval or instant.

Topological Coordinate
type: Class
SHACL shape validation rule: TopologicalCoordinateShape
created: 2024-11-29
comment: Represents a topological coordinate.

Track
type: Class
subclass of: Infrastructure element
disjoint with: Tunnel
created: 2024-11-20
modified: 2025-01-30
modified: 2025-03-01
comment: A pair of rails over which rail borne vehicles can run.

Train Detection System
type: Class
SHACL shape validation rule: TrainDetectionSystemShape
created: 2021-08-07
modified: 2021-08-07
comment: Safety system used to detect the presence of vehicles on the railway track.
term status: stable

Tunnel
type: Class
subclass of: Infrastructure element
SHACL shape validation rule: TunnelShape
created: 2020-07-29
modified: 2022-07-07
modified: 2024-09-19
modified: 2025-01-30
source: http://data.europa.eu/eli/reg/2014/1303/2024-01-29
comment: A railway tunnel is an excavation or a construction around the track provided to allow the railway to pass for example higher land, buildings or water.
term status: stable
definition: A railway tunnel is an excavation or a construction around the track provided to allow the railway to pass for example higher land, buildings or water. The length of a tunnel is defined as the length of the fully enclosed section, measured at rail level. A tunnel in the context of this TSI is 0.1 km or longer. Where certain requirements apply only to longer tunnels, thresholds are mentioned in the relevant clauses.

Vehicle
type: Class
disjoint with: Vehicle Type
created: 2020-11-22
modified: 2020-11-22
comment: A specific vehicle or wagon able and allowed to operate over railway infrastructure.
term status: stable

(deprecated) Vehicle Keeper
type: Class
subclass of: Organization
created: 2020-11-23
is replaced by: Body
is replaced by: vehicle keeper
modified: 2020-11-23
modified: 2024-04-18
modified: 2024-06-03
comment: The natural or legal person that, being the owner of a vehicle or having the right to use it, exploits the vehicle as a means of transport and is registered as such in a vehicle register referred to in Article 47 of (EU)2016/797.
deprecated: true
term status: stable

Vehicle Type
type: Class
created: 2020-07-29
modified: 2020-07-29
modified: 2024-04-18
modified: 2024-06-03
comment: A vehicle type that has been authorized to operate on the EU railway infrastructure. Type means a vehicle type defining the basic design characteristics of the vehicle as covered by a type or design examination certificate described in the relevant verification module. Basic design characteristics means the parameters that are used to identify the vehicle type as specified in the issued vehicle type authorisation and recorded in the European Register of Authorised Vehicle Types ('ERATV'). The above mentioned certificate should be documented using era:certificate.
term status: stable

Feature
type: Class

Geometry
type: Class
SHACL shape validation rule: GeometryShape

Point
type: Class

List
type: Class

Concept
type: Class

Time instant
type: Class

Temporal duration
type: Class

Temporal entity
type: Class

Organization
type: Class
label: Organisation @fr
label: Organizzazione @it
label: organización @es

Document
type: Class

Person
type: Class

Designated RINF Topical Working Groups

Ghislain Atemezing
source: https://orcid.org/0000-0003-1562-6922
member of: ERA

Dragos Patru
member of: ERA