Designated RINF Topical Working Groups
ERA Ontology
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].
Revision 24-04-2026: - Changed rdfs:range for the era:alternativeTypeName to rdf:langString. Revision 21-04-2026: - Added era:Siding to the domain of era:verificationINF, era:demonstrationINF and era:minimumHorizontalRadius, and adapted the SHACL shapes accordingly. - Added missing era:XMLName "CRG_Needof555" on era:usesGroup555. - Changed rdfs:domain of era:conditionsChargingElectricEnergyStorage and era:permissionChargingElectricEnergyTractionStandstill from era:ContactLineSystem to era:PlatformEdge. Revision 20-04-2026: - Removed era:Siding from the domain of era:maximumContactWireHeight and adapted the SHACL shapes accordingly. Revision 07-04-2026: - Removed useless shape references on era:etcsDegradedSituation, era:axleSpacingExplanation, era:etcsDataCommApp and era:linesideDistanceIndicationFrequency. - Added property mapping to ERATV legislation. Revision 30-03-2026: - Removed functional Property for era:contactStripMaterial ; harmonized range of era:maximumContactWireHeight to xsd:double in the ontology and adapted the SHACL shapes. Revision 26-03-2026: - Fixed owl:versionIRI (formerly owl:versionURI used). Revision 18-03-2026: - Added missing labels for prov:Activity, rdf:Bag and rdf:List. Revision 17-03-2026: - Removed functional property for era:frequencyBandsForDetection, update the list of SKOS - Introduced concept scheme - DocStates (former States) and updated property era:state to refering this Concept Scheme + refering to updated shapes era-sh:DocState Revision 16-03-2026: - Clarified era:lineCategory as a RINF infrastructure property by removing ERATV-specific metadata. - Introduced era:compatibleWithLineCategory for ERATV VehicleType usage. - Updated ERATV SHACL shapes accordingly; RINF SHACL shapes remain unchanged. Revision 14-03-2026: - Added range rdf:List for era:hasSequence and era:includes to align with the SHACL constraints that expect a list of elements for these properties. - Added the strict of misusage of ERA ontology into RINF SHACL shapes. Revision 12-03-2026: - For archaic `era:oclType`, work with list instead of Skos CS. - Fixed `conditionsAppliedRegenerativeBraking` (1.1.1.2.2.4.1) SHACL SPARQL constraint: inverted FILTER logic so the field is required only when regenerative braking is "under conditions" (20) or "under conditions only for emergency brake" (40), and corrected concept scheme from contact-line-systems to regenerative-braking (see https://gitlab.com/era-europa-eu/public/interoperable-data-programme/era-ontology/era-ontology/-/work_items/301). - Deprecated the parameter tenGISId (1.1.1.1.2.1.2). - Removed the corresponding SHACL validation rules. - Changed the range of era:gsmrConstraintsOperateOnlyInCircuitSwitch to xsd:string. - Converted the property from owl:ObjectProperty to owl:DatatypeProperty. - Removed the link to the SKOS concept scheme as the parameter is no longer represented as a controlled vocabulary. - Corrected the RINF index referenced in the related SHACL validation rule. Revision 11-03-2026: - Clarified Special(Tunnel)Area related aspects in line with updated skos CS (Gitlab public Work Item 304) Revision 04-03-2026 (ERATV): - Merged classes, properties and SHACL shapes from ERATV extension branch into ERA ontology. - Introduced era:compatibleWithLineCategory for ERATV VehicleType usage. - Updated ERATV SHACL shapes accordingly; RINF SHACL shapes remain unchanged. Revision 03-03-2026: - Fixed HasPartTrackOP SPARQL constraint: replaced broken UNION/FILTER pattern with rdf:type/rdfs:subClassOf* property path for matching era:Track and its subclasses. - Added era-op-types:140 (domestic border points) to the exclusion list in HasPartTrackOP SPARQL constraint. Revision 27-02-2026: - Updated domain definitions of properties with era:rinfIndex in the range 1.1.1.3.2.1–1.1.1.3.2.15 and 1.1.1.3.2.16.1–1.1.1.3.2.16.13 (excluding 1.1.1.3.2.16). - Preserved existing owl:unionOf domain expressions and replaced occurrences of era:Track or era:RunningTrack within those unions with era:ETCS. - Change rdfs:range of era:canonicalURI to rdfs:Resource Revision 26-02-2026: - Moved rdfs:label SHACL constraint to era:InfrastructureElement level, removing redundant per-subclass bindings (Bridge, LevelCrossing, SpecialArea, SpecialTunnelArea, Switch) and replacing the dedicated LinearPositioningSystem Label shape with the generic RdfsLabel shape. - Added RINF concept era-lrs:100 "None" and renamed era-lrs-eratv:None prefLabel to "None - eratv" to disambiguate RINF and ERATV None concepts in LegacyRadioSystems. Revision 25-02-2026: - Restricted MaxPermittedTrainLengthApplicability SPARQL constraint to only check tracks that are part of a era:SectionOfLine (see https://gitlab.com/era-europa-eu/public/interoperable-data-programme/era-ontology/era-ontology/-/issues/285). - Corrected URIs of referenced concept schemes from the ERA Ontology. - Corrected URIs of referenced shapes from the ERA Ontology. - Added missing backward relationships to ERA Ontology from shapes. Revision 24-02-2026: - Removed dcterms:relation to non existing era:bridgeWindRestriction. - Fixed REGEX type error in SKOS concept scheme SPARQL constraints: wrapped IRI-typed ?concept in STR() so REGEX receives an xsd:string as required by SPARQL 1.1 (see https://gitlab.com/era-europa-eu/public/interoperable-data-programme/era-ontology/era-ontology/-/issues/276). - Fixed SolNatureApplicability SPARQL constraint to also match tracks linked via era:hasPart (not only deprecated era:track) (see https://gitlab.com/era-europa-eu/public/interoperable-data-programme/era-ontology/era-ontology/-/issues/275). - Fixed EddyCurrentBrakingConditionsDocumentApplicability SPARQL constraint to use concept URIs from the eddy-current-braking scheme instead of magnetic-braking (see https://gitlab.com/era-europa-eu/public/interoperable-data-programme/era-ontology/era-ontology/-/issues/273). - Fixed NoRepeatedTrackIdsSoL SPARQL constraint: removed wrongful a era:OperationalPoint type checks, as the constraint targets era:SectionOfLine subjects (see https://gitlab.com/era-europa-eu/public/interoperable-data-programme/era-ontology/era-ontology/-/issues/270). - Added "passenger stop" (era-op-types:70) to the exclusion list in HasPartTrackOP SPARQL constraint (see https://gitlab.com/era-europa-eu/public/interoperable-data-programme/era-ontology/era-ontology/-/issues/269). - Removed owl:FunctionalProperty from era:lineReferenceTunnelStart and era:lineReferenceTunnelEnd, and removed the corresponding sh:maxCount 1 SHACL constraints, as tunnels may span multiple tracks (see https://gitlab.com/era-europa-eu/public/interoperable-data-programme/era-ontology/era-ontology/-/issues/263). Revision 23-02-2026: - Fixed SPARQL constraint messages: ensure ?label-like variables are always bound using COALESCE, preventing message construction failures when nolabel exists (see https://gitlab.com/era-europa-eu/public/interoperable-data-programme/era-ontology/era-ontology/-/issues/264). - Added ?path binding to all SPARQL constraint SELECT clauses, enabling SHACL result paths to be reported in validation results (see https://gitlab.com/era-europa-eu/public/interoperable-data-programme/era-ontology/era-ontology/-/issues/265). - Moved sh:severity from sh:SPARQLConstraint instances to sh:NodeShape definitions to comply with the SHACL specification (domain of sh:severity is sh:Shape). Created dedicated *SPARQLWarning NodeShapes for constraints with sh:Warning severity (see https://gitlab.com/era-europa-eu/public/interoperable-data-programme/era-ontology/era-ontology/-/issues/280). - Fixed conditionsAppliedRegenerativeBraking applicability constraint to also check the conditionalRegenerativeBrake value, excluding cases where regenerative braking is not applicable or not present (see https://gitlab.com/era-europa-eu/public/interoperable-data-programme/era-ontology/era-ontology/-/issues/268). - Fixed NoRepeatedPlatformIdsOP SPARQL constraint to correctly detect duplicate platformId values (see https://gitlab.com/era-europa-eu/public/interoperable-data-programme/era-ontology/era-ontology/-/issues/271). - Fixed NoRepeatedSidingIds SPARQL constraint to correctly detect duplicate sidingId values (see https://gitlab.com/era-europa-eu/public/interoperable-data-programme/era-ontology/era-ontology/-/issues/272). - Fixed HABD SPARQL constraints: added missing $this in SELECT clauses (see https://gitlab.com/era-europa-eu/public/interoperable-data-programme/era-ontology/era-ontology/-/issues/274). - Fixed SoLTrackDirectionMaxCount SPARQL constraint to use STR() for IRI comparison in duplicate track direction filter (see https://gitlab.com/era-europa-eu/public/interoperable-data-programme/era-ontology/era-ontology/-/issues/277). - Fixed unbound variables in SPARQL constraint SELECT clauses: bound ?uopid in ReferenceBorderPointApplicability, removed unbound ?value from NoRepeatedTrackIdsSoL, and fixed ?opLabel to ?slLabel with COALESCE in SubsidiaryLocationTypeSKOS (see https://gitlab.com/era-europa-eu/public/interoperable-data-programme/era-ontology/era-ontology/-/issues/278). Revision 19-02-202: - Removed restriction 1:1 for era:linesideDistanceIndicationAppearance and updates the list of SKOS values (see issue #252) Revision 17-02-2026: - Created rdfs:seeAlso for mentions of see: inside skos:scopeNote to streamline the references. - Fixed missing era:applicable values for era:platformHeight and era:rbcPhone. Revision 16-02-2026: - Added the property era:alternativeCode for managing RISC code for OCR+. Revision 13-02-2026: - Introduced class era:Activity as subclass of prov:Activity to support ERA-specific activity modelling. - Introduced SKOS concept scheme era-act:Activities for typing ERA activities. - Added concept era-act:RevocationCodeActivity to classify revocation events. - Added object property era:changeActivity to link ERA resources (e.g. Body) to change activities. - Added datatype property era:revokedCode (xsd:string) to represent the revoked organisation code value. - Adopted dct:valid to express the effective date of the revocation. - Clarified alignment with PROV-O (activities correspond to prov:Activity). Revision 04-02-2026 - Added vs:term_status "unstable" to era:exemptSpecialVehiclesFromATO, era:exemptSpecialVehiclesFromETCS and era:exemptSpecialVehiclesFromRMR. - Added skos:editorialNote indicating that these three properties will be reviewed after the vote of the CCS TSI next amendment. Revision 28-01-2026: - Changed the range of era:trainIntegrityOnBoardRequired to xsd:boolean. - Removed the legacy enumerated values ("Y","N","Optional") from the ontology. - Updated SHACL validation to require a boolean value (true/false). - Aligned the parameter with its RINF definition as a binary required / not required indication. - Updated version number to v3.1.7 and prior version to v3.1.6 Revision 23-01-2026: - Added clarification on era:etcsLevelType. Revision 22-01-2026 - Removed era:orientation (not used yet; overlaps with era:direction). - Removed skos:editorialNote from era:direction. - Removed the corresponding references to era:orientation from SHACL validation rules. - Deprecated era:permitUseReflectivePlates and era:conditionsUseReflectivePlates. - Updated their status to vs:term_status "archaic". - Deactivated the corresponding SHACL validation rules. Revision 11-01-2026 - Added subclassOf era:Feature for CommonCharacteristicsSubset. - Added era:inSkosConceptScheme annotations for era:linesideDistanceIndicationPositioning and added the corresponding SKOS file. Revision 27-11-2025 - Changed the domain of era:organisationCode from era:OrganisationRole to era:Body according to internal ERA decision on November 26th, 2025. Revision 25-11-2025 - Added era:maxPermittedTrainLength and the respective SHACL shapes Revision 21-11-2025 - Added missing owl:SubClassOf from era:NetRelation and era:Feature. Revision 19-11-2025 - Removed rdf:type owl:FunctionalProperty from era:wheelSetGauge and era:gaugingCheckLocation (issue 205) Revision 17-11-2025 - Created era:partOfTENT, era:typeOfTraffic, and era:europeanTransportCorridor Revision 12-11-2025 - Added era:XMLName annotations to new properties Revision 31-10-2025 - Created the TrainDetectionSystemsSpecificChecks SKOS ConceptScheme and the respective SKOS Concepts Revision 29-10-2025 - Added era:exemptSpecialVehiclesFromATO, era:exemptSpecialVehiclesFromRMR, and era:exemptSpecialVehiclesFromETCS, along with the respective SHACL shapes Revision 22-10-2025 - Added shapes for missing classes - Added shapes for time related classes and property - renamed metadata version for v3.1.5 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 30-09-2025 - finished adding 20 properties for Network statements - Todo: create shapes for those properties Revision 29-09-2025 - Added proposals for network statements proposed by RNE, see https://github.com/jeropadillaRNE/RNE_Network_Statement_RINF/blob/main/NS_new_parameters.md - Todo: add corresponding shacl validation 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 figures Revision 24-06-2025 - Added SHACL validations for border points Revision 16-06-2025 - Added SHACL constraint for era:redLightsRequired country applicability Revision 09-06-2025 - Updated the formatNote of era:trackPhaseInfo and era:trackSystemSeparationInfo - Deprecated era:phaseInfoChangeSupplySystem and era:systemSeparationInfoChangeSupplySystem - Fixed unitOfMeasure annotations that used https://qudt.org/vocab/unit/ (with https) instead of the defined prefix unit (which is with http) Revision 06-06-2025 - Add missing axiom era:PrimaryLocation rdfs:subClassOf era:InfrastructureElement Revision 26-05-2025 - Fixed the typo in the name of existanceOfIndustrialRisk (-> existenceOfIndustrialRisk) and corrected the legalDeadline according to the legislation Revision 21-05-2025 -Removed the XMLName annotation from the new entities Revision 09-05-2025 - Added rdfs:label, rdfs:comment, and rdfs:seeAlso to era:vehicleCategory and era:vehicleSubCategory Revision 06-05-2025 - Removed the rdfs:subPropertyOf annotation from era:minVehicleImpedanceVoltages Revision 05-05-2025 - Removed the RINF annotations (XMLname, rinfIndex, and legalDeadline) from etcsNationalPacket44Function - Added the deprecated and isReplacedBy annotations to etcsNationalPacket44 that was missing, and the respective dct:replaces annotations to etcsNationalPacket44Function and hasEtcsNationalPacket44 - Removed the RINF annotations (XMLname, rinfIndex, and legalDeadline) from etcsRestrictionsConditionsDoc Revision 30-04-2025 - added rdfs:subClassOf era:Feature annotation for era:InfrastructureElement and era:NetElement Revision 25-04-2025 - fixed double type on some properties; - added SubsidiaryLocation ->subclass of era:Feature - removed transitivity to fix the reasoner issue - removed the parent-child relation from the era:PrimaryLocation Revision 26-03-2025 - remove external unused external classes and properties - remove the wgs: prefix and include sf: prefix for the sf:Point Revision 24-03-2025 - small revision based on the input of the internal control group Revision 17-03-2025 - harmonize the explanation on the RINF parameters as documents - remove any unnecessary dcterms:description annotations. - overall review of general explanations, examples, following the input of ERA TSI experts Revision 11-03-2025: annotations harmonization - Removed dcterms:source duplicates with same URI different by https - Reused rdfs:seeAlso instead of dcterms:source pointing to URLs different from ELI URI legal reference - Simple editorial changes based on orthography review - Add missing levels in the parameters hierarchy and link them to properties representing RINF parameters - Reintroduction of rinfINndex annotations to the hierarchical properties Revision 10-03-2025 - Changed the axiom for the era:SubsidiaryLocation - Fixes on the relations between kilometric posts and the linear positioning system - Property era:inCountry can be part of a subset with common characteristics - Property era:infrastructureManager was missing the domain of infrastructure elements - Addition of the era:connectedTo property to address a simple connectivity between tracks, as RINF parameter 'internal connectivity'. - Adding missing domains on the properties for the RINF parameters 1.1.1.5.x - Adding missing domains on the era:notApplicable and era:notYetAvailable property flags - Adding axioms on the NetRelation to ensure that all properties are provided - Removed duplicate values for era:applicable Revision 07-03-2025 - Removed grouping Object properties without subproperties in use: + era:switchesAndCrossingsObjParameter + era:relatedElectromagneticInterferencesObjParameter + era:energySubsystemDeclarationsVerificationTrackObjParameter + era:infraSubsystemDeclarationsVerificationTrackObjParameter Revision 05-03-2025 - Deprecated era:cantDefficiency Revision 01-03-2025 - Updated disjointWith axioms in the following cases: + all subclasses of era:InfrastructureElement + era:Body, era:InfrastructureElement + era:SubsidiaryLocation, era:PrimaryLocation + era:NetRelation and era:NetElement + era:LinearPositioningSystem and era:LinearPositioningSystemCoordinate + era:Feature and era:TemporalFeature + all subclasses of era:NetElement Revision 28-02-2025 - General review of the RINF parameters following the comments received from the RINF Work Group and topical Working Groups members and the ERA experts. - Additions on the general explanations, format notes and dependency nodes, cleanup duplicate applicability flags, doubles definitions, etc. - Addition of missing unit of measure for era:cantDeficiencyBasicSSP - Change the domain of some properties to point to the correctgroup of parameters (era:ContactLineSystem) - Addition of explanation whenever the XML data set upload is maintained Revision 20-02-2025 - Introduction of the era:HABD class for representing the Hot Axle Box Detector - Introduction of the era:tracksideHabd property for linking the InfrastructureElement with the HABD Revision 18-02-2025 - Added era:inSKOSConceptScheme for the property standardCombinedTransportContainers - Updated to stable the term_status for the properties standardCombinedTransportContainers and standardCombinedTransportRollerUnits. Revision 18-02-2025 - Added dcterms:replaces in cases where there was a dcterms:isReplacedBy pointing to an entity, but no corresponding replaces in the opposite direction, and vice versa. - Removed dcterms:isReplacedBy statements that pointed to entities no longer present in the ontology. Revision 13-02-2025 - Deprecation of era:category and era:subCategory and creation of era:vehicleCategory and era:vehicleSubCategory. Revision 11-02-2025 - Added annotations to era:etcsNationalPacket44 - Fixed label and definition of era:linesideDistanceIndication 1.1.1.0.0.3 - Changed the domain of era:reasonsEtcsRadioBlockCenterReject 1.1.1.3.2.15, 1.2.1.1.1.15 to era:RadioBlockCenter - Added axiom subpropertyOf contactLineSystemObjParameter to era:conditionsAppliedRegenerativeBraking 1.1.1.2.2.4.1 - Deleted editorial note from era:minimumVerticalRadius 1.2.2.0.3.3 - Added axiom subpropertyOf tunnelDataParameter to era:hasWalkway 1.1.1.1.8.12 - Removed RINF index from properties used to represent the data format of the RINF parameters (i.e. all ObjParameter and DataParameter properties) Revision 30-01-2025 - Fix Issue #145 - remove the era:BasicElement and era:AggregatedElement classes and move the properties with them as domain to the super-class InfrastructureElement. Update of all the classes concerned by the hierarchy of InfrastructureElement based on sub-classes. - Partially fix issue #148 with comment: topology is on micro level - Changed the range of era:startOffsetFromOrigin and era:endOffsetFromOrigin into xsd:double and the unit of measure M was added for clarification. - Added era:existanceOfIndustrialRisk property for defining the RINF parameter 1.1.0.0.1.1 - Changed era:linesideDistanceIndication according to the decisions of TWG for route book - Added era:routeBookDataParameter for the route book parameters hierarchy - Added domains for era:operatingLanguage and era:operationalRegimeType - Added hierarchy for generic route book related parameter - Remove the era:SignalsGrid and all the relations, following the request during a bilateral meeting with Infrabel - remove redundant era:kilometerNumber and add more details on era:kilometer - Fix issue #104 - adding era:carrierLinearElement Revision 13-12-2024 - Added annotations for all SHACL shapes Revision 12-12-2024: - deleted deprecated property http://data.europa.eu/949/signallingSystemType following review, there is no instance of it. - Deleted annotation XMLName from properties that are part of FrenchTrainDetectionSystemLimitation, LoadCapability, MaximumMagneticField, MinVehicleImpedance, PhaseInfo, RaisedPantographsDistanceAndSpeed, SystemSeparationInfo Revision 10-12-2024: - Added the axiom era:Applicability subClassOf era:TemporalFeature - Added range of era:ofParameter - Renamed era:bridge property to era:hasBridge - Added a property era:parameterValue(era:Applicability, rdfs:Resource) Revision 05-12-2024: - Added restricted ranges for the dataproperties era:dNvovtrp, era:dNvpotrp, era:dNvroll, era:tNvcontact, era:tNvovtrp, era:vNvallowovtrp and era:vNvsupovtrp. This partially solves issue #135 for our needs. Revision 03-12-2024: - Fixed domain kmPostName to KilometricPost or LinearPositioningSystem - Deleted RINF index for "parts" of compund properties: PhaseInfo, RaisedPantographsDistanceAndSpeed, SystemSeparationInfo, MinVehicleImpedance, frenchTrainDetectionSystemLimitationApplicable, LoadCapability, MaximumMagneticField. - Completed some missing property and classes definitions. - fix explicit definition of the primary and subsidiary locations. - Added era:formatNote property and annotations. Revision 02-12-2024: - added the Turtle file generated from excel file annotated by ERA. - added annotation era:dependencyNote + language tag @en for corresponding annotations Revision 27-11-2024 - Introduced topology and positioning classes and properties (closer to well known topological models) - Removed obsolete classes and properties involved in topology and positioning - Introduced era:parameterValueType to describe parameter applicability value meaning - Bug fixes - renamed era:tsiOPEappendixD1Index to era:tsiOPEAppendixD1Index, same for era:tsiOPEappendixD2Index to era:tsiOPEAppendixD2Index and s/era:tsiOPEappendixD3Index/era:tsiOPEAppendixD3Index Revision 26-11-2024 - Added definitions to object properties that denote relationships among classes - Fixes in hierarchies of CCS, Energy and Infra subsystems - Added CommonCharacteristicsSubset to domain of parameterApplicability - Added functional property axiom to some properties with domain TrainDetectionSystem and ContactLineSystem - Added porperty borderPointId to the class ReferenceBorderPoint - Fix RINF index 1.1.1.3.14.5 to 1.1.1.3.14.6 for location - Added definition to class Track - Renamed the annotation properties era:appendixD2Index and era:appendixD3Index to the corresponding era:tsiOPEAppendixD2Index and era:tsiOPEAppendixD3Index. Created annotation properties era:tsiOPEappendixD1Index Revision 22-11-2024 - Added two annotation properties: era:applicable and era:legalDeadline Revision 20-11-2024 - Fix on hierarchy transitionsBetweenSystems parameters and its subproperties - Fix domain etcsSytemCompatibilitiy, etcsTransmitsTrackConditions, ETCSTransmittedTrackConditions to ETCS - Delete property hasSetOfParameters (duplicate with belongsTo) - Added CommonCharacteristics subset to domain of some of the parameters of PlatformEdge, Siding, and Tunnel parameters - Removed CommonCharacteristicsSubset from domain of ContactLineSystem, Train DetectionSystem and ETCS - Fix 1.1.1.1.8 delete @en tag in RINF index - Removed annotation RINF index and change Domain from those RINF parameters that have been deprecated but that are maintained because there also ERATV and removed Track, CommonCharacteristicsSubset from Domain - Remove deprecated axiom from trainDetectionSystemSpecificCheck, 1.1.1.3.8.2 - Added transitive axiom to subsetOf property between two CommonCharacteristicsSubset - Deleted datatype property NationalLineIdentification, its metadata added to object property nationalLine netween (Position or SectionOfLin)e and NationalRailwayLine. Added metadata to nationalLineId of NationalRailwayLine. -Added functional property axiom to: errorCorrectionsOnBoard, errorCorrectionsOnboardExplanation, conditionsSwitchClassBSystems, roleOf - Added CommonCharacteristicsSybset to domain of localRulesOrRestrictions, localRulesOrRestrictionsDoc - Modified accelerationLevelCrossing to an object property with range Document - Added Siding to domain maxCurrentStandstillPantograph - Fix on hierarchy transitionsBetweenSystems Obj and Data properties and its subProperties - Added functional property axiom to properties where the domain is ETCS - Added rbcID axiom subproperty of dcterms:identifier - Added VehicleType to domain in TemperatureRange - Divided etcsNationalPacket44 (deprecated) into boolean hasEtcsNationalPacket44 etcsNationalPacket44Function that points to a taxonomy. - Create placeholder skos concept scheme forETCS national packet 44 functions. - Changed range hasETCSRestrictionConditions to boolean. Created an object property etcsRestrictionConditionsDoc to point to its Document. Revision 12-11-2024 - Deprecated era:imCode. Replaced by organisationCode Revision 04-11-2024 - Added metadata (dcterms:modified and rdfs:isDefinedBy to all ObjParameter and DataParameter properties in the hierarchy of Energy, Infra and CCS subsystems - Deleted annotation properties dcterms:modifief and dcterms:modifed - Added annotation properties era:affectedProperty, era:affectedClass, era:scope for annotating SHACL shapes - Added annotation property era:shaclShapeValidationRule to point from properties to the corresponding shape. - Added functional axiom to properties according to RINF app guide (1.6.1) to those properties that have "Can be repeated: N" - Removed metadata from length, now a grouping property and place the relevant definitions in the corresponding subproperties. Added subproperty lengthOfVehicle - Imported propeties time:hasBeginning and time:hasEnd from Time ontology - Updated domain to the class ETCS: era:etcsInfill, era:etcsMVersion, era:etcsSystemCompatibility, era:etcsTransmittedTrackConditions - Changed domain kilometer and kmPostName to Position - Changed data properties instructionsSwitchRadioSystems, documentRestrictionPowerConsumption, documentRestrictionPositionContactLineSeparation, conditionsSwitchClassBSystems, conditionsAppliedRegenerativeBraking to object properties with range era:Document Revision 31-10-2024 - Added hierarchies for Vehicle and VehicleType characteristics. - Deprecated datatype property trainDetectionSystemSpecificCheck, as the same object property exists (points to a SKOS concept scheme) - Changes in network and subset with common characteristics proposal (decision meeting 31-10-2024) Revision 30-10-2024 - Created the hierarchy of object and datatype properties for CCS system. Updated domain to Track. Added Subset of Common characteristics to domain. Deleted the class CCS subsystem - Changed names for classes InfrastructureObject to InfrastructureElement and also their subclasses now BasicElement and AggregatedElement. - Axiom for deprecation was deleted for imCode. Its domain is OrganisationRole. - Deleted the class TechnicalCharacteristic. Change all domain and ranges where this class appears. Delete the era:parameter property. - Deprecated properties certificate, state of VehicleType as the class Certificate was also deprecated. The skos concept scheme for certificate states is moved to folder of deprecated skos. - Deleted the property organization between InfrastructureElement and Body (now infrastructureManager is the property that relates the Infrastructure element with the organisation role) - Deleted RINF indexes from minAxleLoad and minDistConsecutiveAxles. Properties remain as there are also eratv properties. - Deleted lineNationalId as lineNationalIdentification also exists (with complete metadata) - Changed name of class and property ETCSLevel and etcsLevel to ETCS and etcs respectively. - Added deprecated axiom to property platformEdge. Revision 29-10-2024 - Created hierarchy of properties for ccs subsystem and energy subsystem object parameters and ccs subsystem and energy subsystem data parameters. Changed domain to corresponding infrastructure object and added SubsetWithCommonCharacteristics to domain of these properties. - Changed names clases InfrastructureObject, BasicObject and AggregatedObject to InfrastructureElement, BasicElement and AggregatedElement Revision 28-10-2024 - Move company code categories SKOS to deprecated SKOS as corresponding property has been deprecated. - Deprecated lineNationalId, replaced by nationalLine property. Create a string datatype property nationalLineIdentfication with same annotations than lineNationalId - Created property hasOrientation between Signal and Orientation - Fixed dcterms:isReplacedBy to hasPosition in deprecated lineReference property Proposal representation of hierarchy of parameters in the RINF app guide: - Add RINF index 1.1.0.0.0.1 and 1.1.1.1.8.1 to the property infrastructureManager - Created hierarchy of properties for infrastructure subsystem object parameters and infrastructure subsystem data parameters. Changed domain to corresponding infrastructure object and added SubsetWithCommonCharacteristics to domain of these properties. - Proposal for BaseLocation, PrimaryLocation and SubsidiaryLocation + Linear Location is now a subclass of BaseLocation + Changed domain of location from TopologicalObject to InfrstructureObject + Delete axiom InfrastructureObject is subclass of Feature. + PrimaryLocation is now a subclass of SpotLocation (no more subclass of an AggregatedObject) + Created linkedToPrimaryLocation between a SubsidiaryLocation and a PrimaryLocation + Added domain PrimaryLocation to hasPosition - Proposal on applicability + Changed the name of the class Applicability to ParameterApplicability. + Changed the name of the property applicability to parameterApplicability with domain InfrastructureObject and range ParameterApplicability + Created property era:ofparameter to relate the ParameterApplicability to the parameter it is denoting (a property in the ontology) Revision 25-10-2024 -Changes according to agreed Organisation proposal: + Changed domain of property infrastructureManager to include Network or PrimaryLocation or InfrastructureObject + Added roleOf as an inverse property of role. Relation that goes from OrganisationRole to Organisation + Updated range of properties vehicleKeeper, manufacturer, allocationCompany to OrganisationRole - Changes according to agreed Border point proposal: + Created class ReferenceBorderPoint that will contain all the listed border points in the RINF application guide. + Created object property referenceBorderPoint relating an OP with a reference border point. + Deprecated properties opInfoPerCountry and borderPointOf - property companyCodeCategory was deprecated. companu code categories SKOS was moved to the folder of deprectaed SKOS - Class Certificate is deprecated, belongs to the EVR ontology. - Properties vehicleTypesCompatibleTrafficLoad and vehiclesCompatibleTrafficLoad are now object properties pointing to the classes VehicleType and Vehicle respectively Revision 24-10-2024 - Fix skos:definition to rdfs:label in era:direction property - Change in Network and Network Resource proposal: + Deleted class NetworkResource + belongsTo has as domain InfrastructureObject + added new property subNetworkOf that relates two networks. + added new property infrastructureManager to relate Network with the Organisation (OrganisationRole). + Add axiom Network is a subclass of AreaLocation - Change in Position layer proposal + Deprecated LineReference class and lineReference property + Created LinePosition and TrackPosition as subclasses of Position. + Deleted the Referent class. + The domain of kilometer and kmPostName is now LinePosition. + Deleted the carrierObject property + Changed domain of hasPosition to InfrastructureObject + Changed domain of nationalLine to LinePosition + Changed range of lineReferenceTunnelStart and lineReferenceTunnelEnd to LinePosition. Subproperties of hasPosition. + Changed domain and range of referent property to TrackPosition and Track respectively. Revision 25-09-2024 - Deprecated minimumTemperature and maximumTemperature as both RINF and ERATV define a temprature range with a list of predefined values. - Changed era:trainDetectionSystemSpecificChecks from a data property to an object property (It is a list of predefined values). Added the pointer to its SKOS Concept Scheme. - Fixed annotation inSKOSConceptScheme for property era:osmClass - Deleted from definitions (rdfs:comment) URIs referring to the source and added them as dcterms:source annotations. Replaced all rdfs:seeAlso to dcterms:source for consistency in the annotations. - Removed duplicate properties appendixD2Index and appendixD3Index, fixed references to point to remaining properties. - Fixed 1.2.1.1.2.12 Specific constraints imposed by the GSM-R network, deleted 1.1... RINF index. Fixed 1.1.1.3.3.12 & 1.2.1.1.2.13 as the correct RINF indexes of "Radio Network ID". - Added isReplacedBy annotations to deprecated classes era:Manufacturer and era.VehicleKeeper. - Fixed typo ammendment for amendment. - Added annotation dcterms:isReplacedBy era:errorCorrectionsOnBoard for era:gsmrErrorCorrectionsOnBoard, era:etcsErrorCorrectionsOnBoard, era:ertmsErrorCorrectionsOnBoard. Revision 24-09-2024 - Add annotation in SKOSConceptScheme to era:operationalRegimeType, era:subsidiaryLocationType, era:conditionsUseReflectivePlates, era:standardCombinedTransportRollerUnit, era:linesideDistanceIndicationAppearance (currently placeholder concept schemes to be developed) - Deleted foaf:Project, no Usage in ontology and the concept is not part of the domain. - Fix bug era:direction, change skos:definition to rdfs:label - Fix Typo definition NationalRailwayLine, Network - According to conceptual design import gsp:SpatialObject sf:LineString, sf:MultiPolygon, sf:Point and also other superclasses in the hierarchy of these classes. Revision 20-09-2024 - Change era:qNvdriverAdhes to an object property that points to a SKOS concept scheme (currently a boolean data property) - Add era:inSkosConceptScheme for era:hasOrganisationRole - Add era:inSkosConceptScheme for era:operatingLanguage: http://publications.europa.eu/resource/authority/language Revision 19-09-2024: - Added annotations for use of ontology as the RINF AG technical annex; - `dcterms:source` refers to ELI URI of the applicable reference legislation (TSI's, regulations) - Fixed anyURI for links using skos:seeAlso Revision 13-08-2024: - clarified the comment and label for ORG pattern as per issue #74. - renamed prefix qudt: to unit: to avoid confusion as per issue #47. - merged annexD2Index with appendixD2index as per issue #50. - added range and/or domain for annotation properties as per issue #56. - fixed label and comment for the properties era:ETCSLevel and era:ETCSLevelType as per issue #60. Revision 12-08-2024: - removed owl:incompatibleWith in a property as per issue #71. - Reduced some long labels + split off notes from definition (see issue #45) Revision 02-08-2024: - removed comments from wgs ontology, keeping mininal annotations (issue #51) - removed owl:imports axiom (issue #73) - Added annotations of time classes used (time:TemporalDuration and time:TemporalEntity) - Replaced dcterms:requires by skos:scopeNote per suggested in issue #58. - Fixed typos in the range of the properties era:side, era:orientation, era:lrsMethod and era:direction. (issue #69) Revision 05-07-2024: - removed empty prefix and base - Changed the reference to previous version to point to release in Github - changed dcterms:description with skos:changeNote. - removed owl:topDataProperty , owl:topObjectProperty and ^^rdfs:Literal Revision 05-06-2024: - linked with existing (updated) or new SKOS Concepts, related to the TWG RINF CCS; - included references and guidelines as in Table 5 of the RINF Application Guide. Revision 03-06-2024: - added properties for the primary and subsidiary locations - reuse the organisation ontology to address the ERA stakeholder organisations (bodies) and their roles - deprecated classes related to organisation - error corrections - added several definitions Revision 24-05-2024: - remove of the owl:FunctionalProperty from every object or data property; - addition of new classes for the purpose of the Topical Wrokgroup micro-level; - reshaping the topology layer, deprecating unused properties and renaming some of the classes - reuse of the time ontology for addressing the validity and applicability; - remove of the axiom era:TopologicalObject as subclass of era:Feature; - changing the domains of multiple data and object properties to subclasses of era:TechnicalCharacteristics; - removed some of the relations between tracks, sidings, tunnels, etc.; - deprecated the properties addressing the validity; - TODO: deprecate unused properties from version 3.0.0; Revision 18-04-2024: - updated as per results of the Topical Working Group RINF-CCS (Draft report 0.2); - include upcoming remarks from TWG members (inclusing those as documented in Report 0.3); - linked with existing (updated) or new SKOS Concepts, related to the TWG RINF CCS; - included references and guidelines as in Table 5 of the RINF Application Guide.
Corresponding XML name as indicated in the RINF application guide
XML name
Annotation property used in SHACL shapes. Name of the classes that are the subject of properties that are being validated in a SHACL shape.
affected Class
Annotation property used in SHACL shapes. Name of the properties that are being validated in a SHACL shape.
affected Property
Annotation used to point to the applicability of a parameter in RINF. Values are Y/N/NYA
applicable
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.
Canonical URI
This property is used to specify dependencies in natural language not covered by skos:scopeNote
dependency note
Index code used in the original definition of a parameter in ERATV.
ERATV index
This property is used to annotate in human readable the format of parameters
format note
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.
Hash source
Property that links an object SKOS property to the URI of the corresponding SKOS Concept Scheme.
in SKOS Concept Scheme
Annotation used to point to legal obligation of a parameter in RINF
legal deadline
Index code used in the original definition of a parameter in RINF.
RINF index
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.
scope
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.
SHACL shape validation rule
Used to annotate properties coming from the TenT regulations, to be used for monitoring the provision of the data.
TenT reference
The index of a vocabulary term in Appendix D1 Vehicle and train Route compatibility checks.
TSI operation appendix D1 index
Appendix D1 index
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.
TSI operation appendix D2 index
Appendix D2 index
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.
TSI operation appendix D3 index
Appendix D3 index
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.
Unit of measure
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.
Parameter is used in Route Compatibility Check (RCC) calculations
Annotation property used to express that a property is no more valid for a given legal regime.
was invalidated by
It is recommended to use a URI for the range of this annotation
12 months after publication of Article 7 Guide
In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest
Indication whether rules exist and are compliant with the TSI.
Existence and TSI compliance of rules for magnetic fields emitted by a vehicle
12 months after publication of Article 7 Guide for OP tracks
Existence and TSI compliance of limits in harmonics in the traction current of vehicles
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.
Mandatory value when the level crossing is defined
Existence of limit for acceleration of train if stopping or recovering speed close to a level crossing expressed in a specific reference acceleration curve.
Acceleration allowed near level crossing
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.
Only applicable when for parameter 1.1.1.3.11.2 True is selected
16 January 2020
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.
Documents available by the IM relating to braking performance
Change from datatype property to object property in order to point to the class Document (reference document)
Specifies the linear elements aggregated by a non-linear element.
aggregates
The organisation in charge to allocate the code for the subsidiary location.
allocation company
The direction relative to the origin of the linear element towards the point reference applies.
applies to direction
(32) ‘area of use of a vehicle’ means a network or networks within a Member State or a group of Member States in which a vehicle is intended to be used;
Area of Use
Not applicable for Authorisation Cases of `vpa:permissionType era-va-authcase:PRE4RP`.
Parameter only applicable when ETCS Baseline > 4 MR1 and ATO is implemented
Supported ATO communication systems from trackside.
ATO communication system
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 installed lineside.
ATO Grade of Automation
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 according to the specification referenced in TSI CCS 2023/1695
ATO System version
Indicates the member state where a vehicle type has been authorized. Not to be confused with Area Of Use.
Member State of authorisation
Present and unchanged since <http://data.europa.eu/eli/dec_impl/2011/665>
Indicates the country(ies) in where a vehicle type has been authorized to operate.
Automated Train Operation (ATO)
Axle bearing condition monitoring.
axle bearing condition monitoring
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.
Axle spacing
The parameter should currently be considered independent of a Vehicle Configuration.
Indicates that an infrastructure element belongs to a certain subset that contains common characteristics.
belongs to
Relates the information that each country maintains on a border point, to the operational point that represents the general information on the border point.
border point of
Brake related parameters
A value has to be provided when ETCS is present (a value is provided on 1.1.1.3.2.1).
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".
Cant Deficiency used for the basic SSP
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.
The carrier linear element in relation to which the orientation is based on
carrier linear element
(Deprecated) Vehicle category.
Declarations of verification for track
Control-command and signalling subsystem
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. Use only if no link can be made with the underlying authorisation and its presented certificates.
Type or Design Examination Certificate, supporting the Vehicle Type's authorisation process.
The direct link between era:VehicleType and era:CLD via this property is only allowed for VT's of which no authorisation process can be traced.
Links an ERA resource (e.g. Body) to an activity representing a change affecting that resource.
change activity
Category of a Railway company. Can be Infrastructure, Freight or Passenger. Deprecated as it will be integrated with the Organisations properties.
Company code category
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.
Document with the procedure(s) for static and dynamic route compatibility checks
Indicates the EN line categories with which a vehicle type is compatible.
compatible with line category
The EN line categories upon which the type can operate.
When `not electrified` is chosen in parameter 1.1.1.2.2.1.1, then this parameter is not applicable.
Indication whether regenerative braking is permitted, not permitted, or permitted under specific conditions.
Permission for regenerative braking
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
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.
Name and/or reference of the document specifying the conditions applying in regards to regenerative braking.
Conditions applying in regards to regenerative braking
Applicable when at least two different class of protection systems exist.
Name and/or reference of the document specifying the Special technical conditions required to switch over between ERTMS/ETCS and Class B systems.
Special technical conditions required to switch over between ERTMS/ETCS and Class B systems
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.
A value is mandatory if the value of parameter "Permit of use of reflective plates" is boolean "Yes"
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.
Conditions for use of reflective plates
4.2.2.1.3.2 of TSI OPE (Commission Implementing Regulation (EU) 2019/773 of 16 May 2019)
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.
This property is used to link a vehicle type with its conformity checks, through the authorisation case(s)
configuration dependent conformities/compliances
``` eratv:vac-uuid(type) a era:VehicleTypeAuthorisationCase ; era:configDependentCompliance [ a era:VehicleTypeAuthorisationCheck ; vpa:checkedSection <URI-to-TSI-Section checked> ; # always available vpa:checkedRequirement <URI-to-TSI> ; # always available vpa:withRestriction eratv:nccfu-uuid(type) ; ] . eratv:nccfu-uuid(type) a era:VehicleTypeAuthorisationRestriction ; era:forConfiguration <URI-to-Configuration-1> , <URI-to-Configuration-2> ; # all configs sharing the same conformity result # if any conditions result from this check, they can be added here. ```
This property is used to link a vehicle type with its restrictions, through the authorisation case(s)
configuration dependent conditions of use and other restrictions
``` eratv:vac-uuid(type) a era:VehicleTypeAuthorisationCase ; era:configDependentCondition [ a era:VehicleTypeAuthorisationCheck ; vpa:checkedSection <URI-to-TSI-Section checked> ; # if available vpa:checkedRequirement <URI-to-TSI> ; # if available vpa:withRestriction eratv:nccfu-uuid(type) ; ] . eratv:nccfu-uuid(type) a era:VehicleTypeAuthorisationRestriction ; era:forConfiguration <URI-to-Configuration-1> , <URI-to-Configuration-2> ; # all configs sharing the same restrictions era:nonCodedRestrictions ""{{Text of the non-coded restrictions}}""@en ; era:minimumHorizontalRadius 150^^xsd:integer ; era:maximumDesignSpeed 200^^xsd:integer ; era:temperatureRange <URI-climatic zone> ; # other coded CfU. ```
This property is used to link a vehicle type with a configuration parameter set, which is a group of parameters which depend on a VehicleTypeConfiguration.
configuration dependent parameter
Represents a bidirectional connection between two Track instances.
connected to
Internal connection
Tracks connectivity to operational points
Track_A connectedTo Track_B implies Track_B connectedTo Track_A.
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.
System that is used to transmit electrical energy to road or rail vehicles.
contact line system
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
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.
Indication of the type of the contact line system.
Type of contact line system
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.
Mandatory only if “Overhead contact line (OCL)” is selected in 1.1.1.2.2.1.1, otherwise the parameter is not applicable.
Indication of which contact strip materials are permitted to be used on the infrastructure or with which the vehicles (of the VehicleType) may be equipped with.
Permitted contact strip material
[ERATV] When used for VehicleType, the parameter must have as range a VehicleTypeConfigParameterSet, of which the VehicleTypeConfiguration at least contains one EnergySystem, from the ones recorded under `era:energySupplySystem`. Further, all of the ENE supply systems mentioned under that parameter must have a value for this parameter `era:contactStripMaterial`. [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, the option other shall be selected.
[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.
Indicates that a subset with common characteristics contains a certain infrastructure element.
contains
Data SIM Card GSM-R Home Network.
Data GSM-R network
GSM-R and ETCS L2 must be installed for this parameter to be applicable.
Radio requirements used for demonstrating technical compatibility data.
Radio system compatibility data
Harmonised restriction code 2.4.21 (if Class A data system is installed, so not `era-rscd-eratv:not-applicable` nor `era-rscd-rinf:10`).
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.
(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.
Defines subset
The direction of the orientation of a railway element, in relation to the carrier linear element
direction
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.
Document with restriction related to the position of Multiple Traction unit(s) to comply with contact line separation
Name and/or reference of the document specifying the restriction(s) related to power consumption of specific electric traction unit(s).
Document with restriction related to power consumption of specific electric traction unit(s)
Indication of limitations on the use of eddy current brakes.
Use of eddy current brakes
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.
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.
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
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.
Document with the conditions for the use of eddy current brakes
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.
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.
Element A
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.
Element B
References the topology object of a higher-granularity level which contains a lower-granularity topology object.
Element part
Emergency Brake: Stopping distance and deceleration profile for each load condition per design maximum speed.
Emergency braking
Type of end coupling (indicating tensile and compressive forces).
End coupling type
Geographical coordinates in decimal degrees and km of the line at the end of a tunnel.
End of tunnel
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.
Specifies the ending point of a linear reference.
ends at
Energy subsystem
Indication of the traction supply system (nominal voltage and frequency).
Energy supply system (Voltage and frequency)
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
12 months after the entry into force of TSI CCS and at least 12 months after publication of Article 7 Guide
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.
Error corrections required for the on-board ETCS, GSM-R and/or ATO function
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.
European Train Control System (ETCS) application level supported by the track side equipment.
TSI compliant train protection system (ETCS)
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 installed lineside.
ETCS baseline
The ETCS baseline needs to be provided for each available ETCS Level. See: TSI CCS (Table A2)
If the ETCS Baseline.Version is not fully compatible, it shall be indicated (use era:etcsBaselineIncompleteCompatibility for textual).
Mandatory when ETCS is present.
ERTMS / ETCS application level for degraded situation related to the track side equipment.
ETCS level for degraded situation
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 on-board and its level.
ETCS equipment level
Harmonised restriction code 2.3 (if era-eeobl-eratv:None) and 2.4.10 (any other ETCS installed).
Mandatory in case of ETCS level 1 and infill device(s) are installed. Otherwise it is not applicable.
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.
ETCS infill installed line-side
TSI CCS (4.2.2 & 4.3.3)
ETCS application level related to the track side equipment.
European Train Control System (ETCS) level
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)
1 January 2021
ETCS M_version according to the specification referenced in Appendix A-1, index [C], SRS 7.5.1.9.
ETCS M_version
See: TSI CCS (Subset-026, Chapter 7, 7.5.1.79 M_VERSION)
Indication whether data for national applications is transmitted between track and train.
ETCS national packet 44 application implemented
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.
ETCS National Values
Envelope of legally operated ETCS system versions
onboard system versions
See: TSI CCS (Subset-026, Chapter 7, 7.5.1.79 M_VERSION, and 7.5.1.9.)
Indication of the document where restrictions or conditions due to partial compliance with the TSI CCS are described.
document with operating restrictions or conditions
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 requirements used for demonstrating technical compatibility.
ETCS system compatibility
TSI CCS, Appendix A, Table A 1, 4.2.17 a.
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.
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.
Transmittable track conditions by the CCSSubsystem, according to the specification referenced in Appendix A-1, index [C]
Track conditions which can be transmitted
TSI CCS (Subset-026, Chapter 5, section 5.18.1.1)
Indication of which European Transport Corridor the element belongs to.
European transport corridor
Fire safety category for tunnels.
Fire safety category
The configuration for which the ParameterSet or Restriction is valid.
for Configuration
(evr) VehicleRegistrationRestriction is an `era:Restriction`.
Configuration corresponding to the rinf concept in energy supply system.
for energy supply system
Allows to link a configuration parameter set to a line category
for line category
Example usage would be - TODO: complete example
Configuration corresponding to the rinf concept in ETC CCS.
for onboard class A
Configuration corresponding to the rinf concept in "Other Protection Control and Warnings concepts.
for onboard class B
TODO: add the corresponding conceptscheme with the era:inSkosConceptScheme annotation and remove this text
Configuration corresponding to the rinf concept in wheel set gauge concepts
for wheel set gauge
Indication whether the line is designated to a Railway Freight Corridor.
Part of a Railway Freight Corridor
It is recommended to use the property era:europeanTransportCorridor with the respective SKOS concepts instead of this property. Not applicable if the line is not part of an RFC. If a line belongs to several corridors, repeat the parameter.
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.
Section with train detection limitation, only for the French network
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
Section with train detection limitation number, only for French network
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.
Frequency bands for detection
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
Gauges as defined in European standard or other local gauges, including lower or upper part.
Gauging
[ERATV] Reference profile
former label: Vehicle kinematic gauge
Harmonised restriction code 2.1
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
[ERATV] It is possible to include other 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 EN15273-3: (2013)+A1:2016: Annex C and Annex D INF TSI: 4.2.3.1
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.
Document with the transversal section of the particular points requiring specific checks
GSM-R and ETCS level 2 must be installed for this parameter to be applicable.
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.
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
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.
GSM-R must be installed for this parameter to be applicable
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.
Additional information on network characteristics
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.
GSM-R (parameter 1.1.1.3.3.1) must be installed for this parameter to be applicable
Use of optional GSM-R functions which might improve operation on the line. They are for information only and not for network access criteria.
Optional GSM-R functions
(*1) These inputs refer to the expected behaviour by the network, i.e. if there is any area or point where an automatic selection of network should be done or if there is any location where balises to instruct a change of radio network have been installed. In order to be able to attend to these indications (automatic network, network change by balise) some configuration is needed in the mobile. In case there is a balise used to announce the change of the network, or if there are locations where the network selection is planned by the IM to be done automatically (and not manually, as stated in the requirements). It should be considered as an item that is related to the design of the infrastructure. (*2) the possibility to dial 112 is something specific to the network that should be communicated to the vehicles accessing it. (*3) the use of broadcast calls is something specific to the network that has to be configured in it. (*4) it is something specific to the network that has to be configured in it if the service is provided. (*5) it is something specific to the network that has to be configured in it if the service is provided; something may need to be configured on the network but also in the mobile subscriber data if it wants to use the service. What is requested here is the information of the network capability. (*6) if they are configured on the network. Please indicate which in the "Other information" box. (*7) To be selected if other data applications, different from ETCS L2, can be used within the network - (*8) if it is configured on the network. "GSM-R Shunting used" in order to make public if the GSM-R is used in the network for shunting activities. (*9) Please specify in the "Other information" box for which services /applications are they planned and which are the frequencies in use. (*11) Please use this field to indicate any additional information on network characteristics, e.g.; interference level, leading to the need of additional on-board protection;
GSM-R Radio Data communication on board and its Baseline.
GSM-R radio data communication
Harmonised restriction code 2.4.21 (if Class A data system is installed, so not `era-gsmrrdc-eratv:None`).
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.
GSM-R functional requirements specification (FRS) and system requirements specification (SRS) in accordance with the specification respectively referenced in Appendix A-1, index [E] and index [F], version number or baseline installed.
GSM-R version
Referenced in Appendix A-1, index [E] and index [F]
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.
Name of the own GSM-R network and list of GSM-R networks which are covered by a roaming agreement (for CS services).
GSM-R networks covered by a roaming agreement
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.
Property that links a physical entity with its topological abstraction representation.
Has abstraction
Braking performance of a vehicle type (configuration).
Has braking performance
Property that links a topological abstraction entity with its physical representation.
Has implementation
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 linear referencing system
Specifies the LRS coordinate associated with a topological coordinate.
has line referencing system coordinate
Relates the Organisation role instance (the role played by an Organisation) with the specific role in the taxonomy of organisation roles.
has organisation role
has orientation
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 part
The ordered sequence of topological linear elements which create a linear net reference.
has sequence
Specifies the topological coordinate of a network point reference.
has topological coordinate
It is used to link a vehicle type configuration set with a vehicle type configuration
has vehicle type configuration
Health, safety and environment
Mandatory if the HABD is not TSI compliant (the value of parameter 1.1.1.1.7.5 (Trackside HABD TSI compliant) is 'False')
Direction of measurement of trackside HABD, specific for the French Italian and Swedish networks.
Direction of measurement of trackside HABD
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.
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)
Indicates the country in which an entity resides.
In country
Reference to NUTS-3 place or city
In NUTS-3
List of linear references included in an network area reference.
includes list of linear references
Infrastructure subsystem
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.
infrastructure manager
(deprecated) not in use. Relates any feature implemented in the European railway infrastructure with its infrastructure manager.
Infrastructure manager
Applicable when at least two different radio systems exist.
Name and/or reference of the document specifying the Special instructions to switch over between different radio systems.
Special instructions to switch over between different radio systems
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.
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.
is part of
The closest kilometric post on the line, used as a reference by the LRS coordinate.
km post for reference
Indication of radio legacy systems installed.
Class B or other radio systems installed (Radio Legacy Systems)
Harmonised restriction code 2.5.2XX
The list is in line with ERA/TD/2011-09/INT (v1.17), Table 4, and is now in 3.4 of the annex II of TSI CCS.
Classification of a line according to the TSI INF
Category of line
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.
For RINF: 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
Unique line identification or unique line number within Member State.
(deprecated) National line identification
Indicates a relationship with a national railway line at a specific kilometer point.
(deprecated) Railway location of an infrastructure object
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.
End of tunnel kilometer
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
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.
Start of tunnel kilometer
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
[NNNN] frequency in meters Appearance - selectable list [L/R] - the side along the track where the lineside indication is positioned (left or right)
Indication of types of appearance of track lineside distance indications.
Lineside distance indication
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
There is a proposal to rename the property to be linesideDistanceIndicationType
A selection between 3 possible selectable values: - Left, or - Right, or - Left and Right
Indication of the side along the track where the lineside indication is positioned (left or right, or both sides).
Lineside distance indication positioning
Relates a subsidiary location with a primary location.
linked to primary location
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).
Load Capability
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.
Load capability line category
Mandatory to provide at least a document if parameter "Existence of rules and restrictions of a strictly local nature" value is boolean "Yes"
Electronic document available from the IM stored by the Agency providing additional information.
Documents regarding the rules or restrictions of a strictly local nature available by the IM
IOD: Notification of national rules Art 14. 11
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
The preferred line referencing system.
type of line referencing system
On-Board system reaction when T_NVCONTACT expires According to the specification referenced in Appendix A-1, index [C]
M_NVCONTACT
TSI CCS (Subset-026, chapter 7. 7.5.1.74 M_NVCONTACT)
Indication of limitations on the use of magnetic brakes.
Use of magnetic brakes
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.
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'.
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.
Document with the conditions for the use of magnetic brakes
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.
Vehicle manufacturer company.
manufactured by
Indicates the country in which a vehicle or vehicle type is manufactured.
Manufacturing country
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.
Maximum amount of sand
Represents the category of vehicle which is amended by value of minimum permitted axle load [tonnes] (property minAxleLoad).
Minimum axle load vehicle category
Deprecated as a RINF-parameter according to the amendment to the Regulation (EU) 2019/777.
The values is an instance of era:MinVehicleImpedance class with its 2 properties. Per voltage : input Capacitance (Cin) and Input Impedance (Zin)
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
Impedance as defined in the specification referenced in Appendix A-1, index [D]
Vehicle impedance
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)
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
Radius of the smallest vertical curve expressed in metres.
Minimum radius of vertical curve
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.
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.
national line identification
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.
Indicates the navigation possibilities between two related topological linear elements.
Navigability
• 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.
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.
Net element
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
net reference
Reference to a property that is not applicable.
Not applicable
Reference to a property that is not provided.
Not provided
OCL separation sections
Indicates the parameter (object or datatype property) for which an applicability is being defined.
of parameter
Specifies the linear element a section belongs to.
on element
Specifies the linear element a coordinate is associated with.
on linear element
Onboard equipment - recording device
Harmonised restriction code 5.1.X
The list is in line with ERA/TD/2011-09/INT (v1.17), Table 7, and is now in 3.4 of the annex II of TSI CCS.
Operational point at the end of section of line (kilometres increasing from start OP to the end OP).
Operational point at end of section of line
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
Relates an operational point that represents the general information of a border point to the information that each country maintains for the border point.
Border point information per country
Operational point at the start of section of line (kilometres increasing from start OP to the end OP).
Operational point at start of section of line
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 facility in relation to the dominating operational functions.
Type of operational point
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.
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.
Operating language
Double track type.
Operational regime
Indicates an operational restriction of vehicle or wagon. Parking brake type (if the vehicle is fitted with it).
Operational restriction
Additional concept class according to OpenStreetMap.
Open street map class
Other CCS radio systems onboard
Harmonised restriction code 2.6.2XX
Selected value shall answer the question whether any other CCS system than ETCS exists for the vehicle (type). The list is in line with ERA/TD/2011-09/INT (v1.17), Table 6.
Other CCS systems onboard
Harmonised restriction code 2.6.1XX
Selected value shall answer the question whether any other CCS system than ETCS exists for the vehicle (type). The list is in line with ERA/TD/2011-09/INT (v1.17), Table 5.
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]
Other Cant Deficiency train categories for which the ETCS trackside is configured to provide SSP
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.
Indication of pantograph heads which are allowed to be used.
Accepted other pantograph heads
EN 50367:2020+A1:2022: Annex B3 LOC&PAS TSI: 7.3.2.14 (specific cases)
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.
Other train detection systems
Only applicable when for parameter 1.1.1.3.10.1 "none" was selected.
Indication of existence of other system than ETCS for degraded situation.
Other train protection, control and warning systems for degraded situation
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
Relates an infrastructure element or a common characteristics subset with the applicability of a certain parameter.
parameter applicability
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”.
parameter value type
Parking brake type (if the vehicle is fitted with it).
Parking brake type
Links an element to its TEN-T network classification, which includes network level, type of traffic, and European transport corridor information.
part of TEN-T
References a tunnel that a track goes through.
Passes through tunnel
Performance parameter
Permissible payload for different line categories.
Permissible payload
Reference to a related platform edge.
Platform edge
Distance between the upper surface of platform and running surface of the neighbouring track. It is the nominal value expressed in millimetres.
Height of platform
INF TSI: 4.2.9.2 PRM TSI: 4.2.2.11 OPE TSI: 2.3.7 of Appendix D2
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
Determines the position of the topological object A in a relation.
Position on A
Determines the position of the topological object B in a relation.
Position on B
Denotes the opinion on the approach proposed by the applicant in the pre-engagement application, including a determination of the version of the TSIs and national rules that are to be applied for the subsequent application for authorisation
Pre-engagement baseline
Denotes a previous VehicleType.
Previous vehicle type
Applicable only in case when a primary location exists
Primary location code developed for information exchange in accordance with the TSIs relating to the telematics applications subsystem.
primary location
by 16 March 2019 at the latest for lines belonging to the TEN (1.1.1.1.2.1)
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].
Standard combined transport profile number for semi-trailers
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.
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]
Standard combined transport profile number for swap bodies
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).
Indication of which class B system is installed.
Train protection legacy system
Harmonised restriction code 2.5.1XX
The list is in line with ERA/TD/2011-09/INT (v1.17), Table 3, and is now in 3.3 of the annex II of TSI CCS.
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]
Q_NVDRIVER_ADHES
TSI CCS (Subset 26, chapter 7. 7.5.1.122 Q_NVDRIVER_ADHES)
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]
Q_NVEMRRLS
According to the specification referenced in Appendix A-1, index [C] - TSI CCS (Subset-026, chapter 7, 7.5.1.123 Q_NVEMRRLS)
Country where a vehicle may operate without noise restrictions.
Quieter route exempted country
Harmonised restriction codes 2.7.5, 2.7.6
The quieter routes apply only to wagons in the scope of the Wagon TSI (refer to Article 5a of the Noise TSI).
Harmonised restriction codes - noise category (2.7.X)
In XML the accepted value is NN, where N is a digit from 0 to 9.
An angle defining the inclination of the head of a rail relative to the running surface.
Rail inclination
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.
[ERATV] This inclination is in most cases expressed for MS RINF 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. [NN] represents the denominator of the rail inclination expressed as 1/NN. The typical values are 1:20, 1:30, 1:40. For a VehicleType, the value should currently be considered independent of a Vehicle Configuration.
List of cases subject to system design choices made by the infrastructure manager according to the specification referenced in Appendix A-1, index [C]
Reasons for which an ETCS Radio Block Center can reject a train
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.
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.
reference border point
Requirements for rolling stock
RINF Technical characteristic
Indicates the relationship of a Body to the organisation roles that it can play.
role
Indicates the corresponding Body that plays a certain organisation role.
role of
Mandatory for tunnels longer than 1 km
Categorisation how a passenger train with a fire on board will continue to operate for a defined time period
Passenger train fire category in accordance with point 4.1.4 of TSI LOC&PAS.
Fire category of rolling stock required
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
Rules and restrictions
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.
Safe consist length information from on-board necessary for access the line and SIL
TSI CCS (Subset-026, Chapter 7, 7.5.1.112.1 and P10)
Service Brake: Stopping distance and deceleration profile for specific load condition at design maximum speed.
maximum service braking
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)
on side
Reference to a related siding.
Siding
Signal
Relative position to the line of reference, given in km and indication if the signal refers to normal or opposite track direction
Signal orientation
@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 .
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.
Signalling information for Route Book compilation. This list shall include fixed signals that protect danger points
Type of signal
Indicates what function the signal (on the track or in OP) executes in relation to the track/switches.
Snow, ice and hail conditions.
Snow ice hail conditions
Section of line generic information
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.
Nature of Section of Line
Indicates the special area or location types such as safe areas and restricted area types.
Special area type
Relates a tunnel with a special area or location.
Special tunnel area
12 months after the adoption of the Article 7 Guide for lines belonging to the TEN (1.1.1.1.2.1)
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]
Standard combined transport profile number for containers
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]
Standard combined transport profile number for roller units
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.
Start of tunnel location
Specifies the starting point of a linear reference.
starts at
Denoting the state of the certificate/declaration. Can be in one of the following: Amended, New, Suspended, Withdrawn.
State
The state for CLD is being examined by NBRail, and will be reused for the other classes as well.
(Deprecated) Vehicle subcategory.
Sub categery
Relates a subset with common characteristics with another subset with common characteristics.
subset of
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).
Indicates the subsidiary location type that belongs to a taxonomy.
subsidiary location type
Platform height for which the vehicle is designed.
Supported platform height
Only applicable on running tracks in France
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
Specific for route compatibility check on French network.
Section with train detection limitation
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.
Mandatory for train detection systems based on axle counters
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.
Maximum magnetic field
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).
Indication of load given in tonnes depending of the category of vehicle.
Train detection system min axle load vehicle category
Temperature range for unrestricted access to the line.
Temperature range
Harmonised restriction code 3.1.X
Indication of the part of the trans-European network the infrastructure element belongs to.
TEN classification of track
Trans-European Network (TEN) classification of track
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.
Classification of the element according to its level in the Trans-European Transport Network (TEN-T).
TEN-T network level
Reference case of a TSI thermal capacity.
Thermal capacity TSI reference
Reference to a related railway track.
Track
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)
Normal running direction
Running track generic information
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.
Relates the track with the class LoadCapability. A combination of the line category and speed at the weakest point of the track.
Load capability
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.
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
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)
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.
Relates the Track with PhaseInfo. Indication of required several information on phase separation.
Information on phase separation
Three values: [N] is number of pantographs; [NNN] is minimum distance between pantographs, in metres; [NNN] is the speed considered in km/h.
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.
Requirements for number of raised pantographs and spacing between them, at the given speed
Relates the track with the class RaisedPantographsDistanceAndSpeed.
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
Mandatory if there is an indication of existence of system separation (parameter 1.1.1.2.4.2.1)
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]
Indication of required several information on system separation
Information on system separation
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
Link between the running track and the HABD, covering the RINF parameters 1.1.1.1.7.(5-9)
hot axle box detector (HABD)
Technical characteristics of the train detection systems installed in the section of line.
train detection system
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
It is applicable only when parameter "Type of train detection system" is applicable
Reference to the technical specification of train detection system, in accordance with the specification referenced in Appendix A-1, index [D]
Type of track circuits or axle counters to which specific checks are needed
String containing the name of the TD system for which checks are mentioned in 1.1.1.3.7.1.3.
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".
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"
Not all parameters are applicable to all types of train detection systems; it depends on the applicability condition.
Indication of types of train detection systems installed.
Type of train detection system
Explanation on data presentation: The option of "wheel detector" has to be also selected for: wheel sensor for axle counter, pedal or treadle.
Verification of compliance with TSI includes application of notified national rules (when they exist). Explanation on data presentation: The option of "wheel detector" has to be also selected for: wheel sensor for axle counter, pedal or treadle. If there is no train detection system (if this parameters is not applicable) it has an impact on parameters "Type of track circuits or axle counter to which specific checks are needed" and "Document with the procedure(s) related to the type of train detection systems declared in 1.1.1.3.7.1.2 ( 1.2.1.1.6.1, if in OP)", making them also not applicable.
Train protection legacy systems
Transitions between systems
Deprecated according to the amendment to the Regulation (EU) 2019/777. TSI compliance of rules on the use of composite brake blocks.
TSI compliance of rules on the use of composite brake blocks
TSI compliance of Ferromagnetic characteristics of wheel material required. Deprecated according to the amendment to the Regulation (EU) 2019/777.
TSI compliance of Ferromagnetic characteristics of wheel material required
Indication whether required distance between two consecutive axles is compliant with the TSI. Deprecated according to the amendment to the Regulation (EU) 2019/777.
TSI compliance of maximum permitted distance between two consecutive axles
TSI compliance of maximum permitted impedance between opposite wheels of a wheelset. Deprecated according to the amendment to the Regulation (EU) 2019/777.
TSI compliance of maximum permitted impedance between opposite wheels of a wheelset
TSI compliance of rules for vehicle metal construction. Deprecated according to the amendment to the Regulation (EU) 2019/777.
TSI compliance of rules for vehicle metal construction
TSI compliance of rules for metal-free space around wheels. Deprecated according to the amendment to the Regulation (EU) 2019/777.
TSI compliance of rules for metal-free space around wheels
TSI compliance of rules on combination of RST characteristics influencing shunting impedance. Deprecated according to the amendment to the Regulation (EU) 2019/777.
TSI compliance of rules on combination of RST characteristics influencing shunting impedance
TSI compliant radio (RMR)
TSI Compliance of rules on sand characteristics. Deprecated according to the amendment to the Regulation (EU) 2019/777.
TSI Compliance of rules on sand characteristics
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.
TSI compliance of sanding
Deprecated according to the amendment to the Regulation (EU) 2019/777. TSI compliance of rules on shunt assisting devices.
TSI compliance of rules on shunt assisting devices
Indication of TSI compliant pantograph heads which are allowed to be used.
Accepted TSI compliant pantograph heads
The allowed values for this property belong to the SKOS Concept Scheme http://data.europa.eu/949/concepts/compliant-pantograph-heads/CompliantPantographHeads.
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.
Electronic document available from the IM stored by the Agency with precise description of the clearance gauge and geometry of the tunnel.
Document available from the IM with precise description of the tunnel
Tunnel
Classification of the type of traffic carried on the element.
Type of traffic
The registration method which was used in the vehicle type authorisation process.
Type registration method
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.
Type version id
Relates a feature with a temporal feature to indicate a validity period.
validity
Indicates the core purpose of a railway vehicle: delivering traction, transporting goods or passengers or serving as a special vehicle.
Vehicle category
Indicates the organization that owns/operated a vehicle or wagon.
vehicle keeper
Pantograph head geometry (to be indicated for each energy supply system the vehicle is equipped for).
Vehicle pantograph head
The parameter must have as range a VehicleTypeConfigParameterSet, of which the VehicleTypeConfiguration at least contains one EnergySystem, from the ones recorded under `era:energySupplySystem`. Further, all of the ENE supply systems mentioned under that parameter must have a value for this parameter `era:vehiclePantographHead`.
Indicates the further classification (but not any family/platform) of vehicles within a vehicle category.
Vehicle subcategory
Vehicle technical characteristic
Indicates the vehicle type of a specific vehicle or wagon.
Vehicle type
Indicates the vehicle type authorisation holder.
Vehicle type authorisation holder
Vehicle type category.
Certain era:Certificates also apply only on a certain VehicleType (Sub)Category
VehicleType Manufacturer identification and contact data
Present since <http://data.europa.eu/eli/dec_impl/2011/665/2019-06-16>
Relates the vehicle type with its values of maximum speed and cant deficiency.
Vehicle type maximum speed and cant deficiency
The parameter depended on the [INF, ENE, CCS]-configuration, but should currently be considered dependent only of the INF Configuration.
Vehicle type technical characteristic
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.
List of vehicle types already identified as compatible with Traffic load and load carrying capacity of infrastructure and train detection systems
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.
List of vehicles already identified as compatible with Traffic load and load carrying capacity of infrastructure and train detection systems
Vehicles for which Route compatibility is verified
Voice SIM Card GSM-R Home Network
Voice GSM-R network
The allowed values for this property belong to the SKOS Concept Scheme http://data.europa.eu/949/concepts/gsmr-networks/GSMRNetworks
GSM-R must be installed for this parameter to be applicable. In case of RSC-EU-0 or None, no other values are allowed.
Radio requirements used for demonstrating technical compatibility voice.
Radio system compatibility voice
Harmonised restriction code 2.4.20 (if Class A radio system is installed, so not `era-rscv-eratv:not-applicable` nor `era-rscv-rinf:10`).
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.
Presence and type of derailment detection and prevention function(s).
Freight Wagon DDF/DPF
The parameter is only applicable for VehicleTypes with the FreightWagon category.
A single value expressed in millimetres that identifies the track gauge.
Nominal track gauge
Harmonised restriction code 2.2.X, with X depending on the selected track gauge.
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. The allowed values for this property belong to the SKOS Concept Scheme http://data.europa.eu/949/concepts/gauge-changeover-facilities/GaugeChangeoverFacilities
Wheelset gauge changeover facility
OGC GeoSPARQL 1.0 Standard Working Group
A spatial representation for a given feature.
hasGeometry
Beginning of a temporal entity
Comienzo de una entidad temporal.
has beginning
tiene principio
Beginning of a temporal entity.
End of a temporal entity.
Final de una entidad temporal.
has end
tiene fin
Proporciona soporte a la asociación de una entidad temporal (instante o intervalo) a cualquier cosa.
Supports the association of a temporal entity (instant or interval) to any thing
has time
tiene tiempo
Característica arriesgada -añadida en la revisión del 2017 que no ha sido todavía utilizada de forma amplia.
Feature at risk - added in 2017 revision, and not yet widely used.
Alternative code resulting of the integration of RISC into SRMO for managing organisation code
Alternative Code
RISC code
Historically a 4 numeric code managed by UIC
Alternative name of a vehicle type. For the type name, use `rdfs:label`.
Vehicle Type - Alternative name
Altitude range A1, A2 or A<integer> (integer era:altitudeRangeDetail).
Altitude range
Altitude range value for 'X' if value 'AX' is selected in altitude range.
Altitude range detail
Specifies if the section applies in both directions (optional).
applies in both directions
Information of the train access level for which the boarding aid can be used.
Range of use of the platform boarding aid
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.
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.
Assessed Cant Deficiency
For dual gauge vehicles, values for each gauge shall be indicated.
Indication of existence of equipment or staff supporting the train crew in starting the train.
Existence of platform assistance for starting train
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) ATO error corrections required for the on-board. Use: errorCorrectionsOnboard
ATO on-board implementation.
ATO on-board implementation
A value is mandatory if the value Overhead contact line (OCL) is selected for parameter "Type of contact line system"
Indication of whether an automatic dropping device (ADD) required on the vehicle.
Automatic dropping device required
Position of the axles along the unit: a: Distance between axles
Axle spacing, distance a
Position of the axles along the unit: b: Distance from end axle to the end of the nearest coupling plane
Axle spacing, distance b
Position of the axles along the unit: c: distance between two inside axles.
Axle spacing, distance c
Explanation of the values for a, b and c
Axle spacing, explanation for a, b, c
Indication of existence of metal mass in the vicinity of the location, susceptible of perturbating the reading of balises by the on-board system.
Big Metal Mass
According to the specification referenced in TSI CCS.
Description of any integrated boarding aids (if provided).
Boarding aids
Border point identification in the list of reference border points in the RINF application guide.
Border point identification
Brake weight percentage (lambda) or Braked mass.
Brake weight percentage
Cant defficiency
Maximum cant deficiency expressed in millimetres defined as difference between the applied cant and a higher equilibrium cant the line has been designed for.
Cant deficiency
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.
Maximum rated current from the catenary (to be indicated for each electrical energy supply system the vehicle is equipped for), given in A.
Catenary max rated current
The parameter must have as range a VehicleTypeConfigParameterSet, of which the VehicleTypeConfiguration at least contains one EnergySystem, from the ones recorded under `era:energySupplySystem`. Further, all of the ENE supply systems mentioned under that parameter must have a value for this parameter `era:catenaryMaxRatedCurrent`.
Indicates whether the given ERTMS error change request may prevent the system from providing normal service if not implemented or applied.
change request prevents service
Mandatory if the speed of the line is equal or greater than 200km/h
Compliance of the tunnel with TSI INF at the maximum permitted speed
Compliance of the tunnel with TSI INF
[4.2.10.1 of INF TSI on Maximum pressure variations in tunnels | ]
Contrary to the Regulation, the deadline is not 30 June 2024 at the latest, but 12 months after publication of Article 7 Guide
Conditions set by IMs according to a standardised document
Permitted conditions for charging electric energy storage for traction purposes at standstill
Applicable when at least two different protection, control and warning systems exist.
Conditions to switch over between different class B train protection, control and warning systems.
Special conditions to switch over between different class B train protection, control and warning systems
Switch over between different systems whilst running. Installation depends on local conditions.
Conditions of use regarding train formation.
Conditions train formation
Mandatory only if impregnated carbon ([NN] % of metallic content)” is selected in 1.1.1.2.3.4, otherwise no value should be provided
Indication of max. percentage of contact strip material Impregnated Carbon permitted to be used.
Contact strip material metallic content
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.
Indicates whether a primary location is suitable for handling containers and loading or unloading of containers.
container handling flag
Smallest cross section area in square metres of the tunnel
Cross section area
[4.2.10.1 of INF TSI on Maximum pressure variations in tunnels |
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.
When "not electrified" is chosen in parameter "Type of contact line system", then this parameter is not applicable.
Indication of whether an on board current or power limitation function on vehicles is required.
Current or power limitation on board required
Currently valid
NNNNNNN.N whereby the last digit is only used when Q_SCALE = 10 CM
Maximum distance for overriding the train trip in metres, according to the specification referenced in Appendix A-1, index [C].
D_NVOVTRP
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.
Maximum distance for reversing in Post Trip mode in metres, according to the specification referenced in Appendix A-1, index [C].
D_NVPOTRP
TSI CCS (Subset 26, chapter 7. 7.5.1.16 D_NVPOTRP)
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.
A number of form at NNNNNN.N, from 0 to 327670
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]
D_NVROLL
TSI CCS (Subset 26, chapter 7. 7.5.1.17 D_NVROLL)
Precision: [NNNNNN.N], with N a decimal number (0 9).
Dangerous goods for which the vehicle is suitable (tank code).
Dangerous goods tank code
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.
EI declaration of demonstration (as defined Recommendation 2014/881/EU) for track relating to compliance with the requirements from TSIs applicable to energy subsystem
EI declaration of demonstration (as defined in Commission 2014/881/EU (2)) relating to compliance with the requirements from TSIs applicable to infrastructure subsystem
EI declaration of demonstration (as defined Commission 2014/881/EU) for track relating to compliance with the requirements from TSIs applicable to infrastructure subsystem. It may happen that several EI declarations were issued - then parameter has to be repeated as many times as many declarations were issued. The procedure for demonstration that existing network fits to requirements of the TSIs is executed on voluntary basis, so when EI declaration do not exist then the parameter is optional. If EI declaration was not issued, then field shall be left empty.
It may happen that several EI declarations were issued - then parameter has to be repeated as many times as many declarations were issued. The procedure for demonstration that existing network fits to requirements of the TSIs is executed on voluntary basis, so when EI declaration do not exist then the parameter is optional. If EI declaration was not issued, then field shall be left empty.
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.
EI declaration of demonstration (as defined in Recommendation 2014/881/EU) relating to compliance with the requirements from TSIs applicable to railway tunnel
(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.
Design mass under exceptional payload
Design mass under normal payload.
Design mass under normal payload
Design mass in working order.
Design mass in working order
Indication whether it is allowed to use diesel or other thermal traction in the tunnel
Diesel or other thermal traction allowed
Diagrammatic representation of the operational point in Well Known Text polyline
Digital schematic overview
It is applicable ( Y ) only if the value Overhead contact line (OCL) is selected for parameter "Type of contact line system"
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.
Distance between signboard and phase separation ending
URL that is used to download a document, e.g. url for a reference document in RINF.
Document URL
Number of driving cabs. For vehicle types without driving cabs, this property should not be used, or the number of driving cabs is to be set to zero (0).
Driving cabs
Stopping distance and deceleration profile for each load condition per design maximum speed.
End intrinsic coordinate
End offset of the section from the origin.
end offset from the origin
Maximum power (to be indicated for each energy supply system the vehicle is equipped for), given in kW.
Energy supply max power
The parameter must have as range a VehicleTypeConfigParameterSet, of which the VehicleTypeConfiguration at least contains one EnergySystem, from the ones recorded under `era:energySupplySystem`. Further, all of the ENE supply systems mentioned under that parameter must have a value for this parameter `era:energySupplyMaxPower`.
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.
Energy supply system TSI compliant
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.
Reasons for Error corrections required, but accepted by the IM for the on-board ETCS, GSM-R and/or ATO function
(Deprecated) ERTMS error corrections required for the on-board.
Data communication application for ETCS implementation.
ETCS data communication application
For ATO communication application, use 'era:atoCommunicationSystem'
(Deprecated) ETCS error corrections required for the on-board.
Applicable and mandatory when ETCS is present (a value is provided on 1.1.1.3.2.1).
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
ETCS trackside implements level crossing procedure or an equivalent solution
TSI CCS (Subset-026, Chapter 5, section 5.16)
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.
Indication whether infill is required to access the line for safety reasons.
ETCS infill necessary for line access
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.
ETCS national applications implemented (NID_XUSER of Packet 44).
ETCS national applications
ETCS on-board implementation.
ETCS on-board implementation
Deprecated according to the amendment to the Regulation (EU) 2019/777. Optional ETCS functions which might improve operation on the line.
ETCS optional functions
(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
ETCS system version 2.2 or 3.0 functionalities to be required in the next 5 years
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.
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]
Is the ETCS trackside engineered to transmit Track Conditions
TSI CCS (Subset-026, Chapter 5, section 5.18)
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)
Indicates whether special vehicles are exempted from the need to install ATO (Automatic Train Operation) for this infrastructure element.
exempt special vehicles from ATO
Indicates whether special vehicles are exempted from the need to install ETCS (European Train Control System) for this infrastructure element.
exempt special vehicles from ETCS
Indicates whether special vehicles are exempted from the need to install RMR (Railway Mobile Radio) for this infrastructure element.
exempt special vehicles from RMR
Indicate, if there are any wind restrictions for a bridge.
Existence of bridge wind restriction
Indicate, if there are any opening hours of the section of a line or Tunnel or Bridge.
Existence of opening hours limitation
Indicate, if there are any limits on transportation of dangerous goods.
Existence of restricted dangerous goods
Indicate, if there are any limits on specific time of a day for transport of dangerous goods.
Existence of restricted periods of time for dangerous goods transportation
Indicate, if there are any limits on specific type of vehicle in the tunnel.
Existence of restricted type of vehicle in tunnel
Indicate, if passenger and freight trains meeting together in a tunnel is allowed
Exclusion of simultaneity
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.
Industrial risks — locations where it is dangerous for the driver to step out
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
Number of fixed seats (min to max number).
Fixed seats
Indication whether the use of on-board device for flange lubrication is forbidden.
Use of flange lubrication forbidden
Deprecated according to the amendment to the Regulation (EU) 2019/777. Indication whether rules for activation or deactivation of flange lubrication exist.
Existence of rules on on-board flange lubrication
Indicates whether a freight train can perform commercial freight activity at a primary location.
freight flag
Part of the section with train detection limitation that indicates if it is applicable. Only for the French network.
Location of particular points requiring specific checks due to deviations from gauging referred to in parameter "Gauging"
Railway location of particular points requiring specific checks
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).
Indication if GPRS can be used for ETCS
GPRS for ETCS
Sections of EIRENE and ETCS subsets for trackside in TSI
GSM-R, ETCS L2 and GPRS for ETCS must be installed for this parameter to be applicable.
Indication of the area in which GPRS can be used for ETCS, expressed as a list of GPRS-enabled RBCs.
Area of implementation of GPRS
Sections of EIRENE optional for trackside in TSI
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…)
Maximum value of the gradient for stabling tracks expressed in millimetres per metre.
Gradient for stabling tracks
Sequence of gradient values and locations of change in gradient
Gradient profile
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.
Indication if there is no GSMR coverage
No GSMR coverage
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).
Number of GSM-R mobile sets in driving cab for data transmission.
GSM-R sets in driving cab
Allowed values: 1, 2, 3. Parameter not used when no GSM-R sets are in the cab.
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) GSM-R error corrections required for the on-board
This feature will determine the applicable operational rules for drivers and signallers when dealing with cab radios registered under wrong numbers.
GSM-R network is configured to allow forced de-registration of a functional number by another driver
See documents regarding Operational Harmonisation ETCS.
Indicates whether a primary location is a point where legal responsibility changes between Infrastructure Managers. This can be, but does not have to be, in conjunction with a state border.
handover point flag
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
Availability by the IM of additional information
[See TSI OPE 4.2.2.6.2 (2)]
Automatic dropping device (ADD) fitted (to be indicated for each energy supply system the vehicle is equipped for).
Has automatic dropping device
The parameter must have as range a VehicleTypeConfigParameterSet, of which the VehicleTypeConfiguration at least contains one EnergySystem, from the ones recorded under `era:energySupplySystem`. Further, all of the ENE supply systems mentioned under that parameter must have a value for this parameter `era:hasAutomaticDroppingDevice`.
Mandatory for tracks with permitted speed (parameter 1.1.1.1.2.5) greater than 250km/h
Specifies whether track construction is with sleepers embedded in ballast or not.
Existence of ballast
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.
Whether or not a track is associated with a bridge.
Has bridge
Vehicle equipped with a cant deficiency compensation system (tilting vehicle).
Has cant deficiency compensation
Indicates if a vehicle's composite brake block is retrofitted
Composite brake block retrofitted
Indicates whether any neighbouring section of line belongs to different Infrastructure Manager
Connecting Infrastructure Manager
Electric units equipped with power or current limitation function.
Has current limitation
The parameter must have as range a VehicleTypeConfigParameterSet, of which the VehicleTypeConfiguration at least contains one EnergySystem, from the ones recorded under `era:energySupplySystem`. Further, all of the ENE supply systems mentioned under that parameter must have a value for this parameter `era:hasCurrentLimitation`. Older VehicleTypes did not distinguish between the onboard energy supply systems.
Indication whether restrictions or conditions due to partial compliance with the TSI CCS exist.
Existence of operating restrictions or conditions
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.
Eddy current track brake fitted. New property defined to distinguish it from eddyCurrentBraking which is a RINF SKOS property.
Eddy current braking fitted
Possibility of preventing the use of the eddy current track brake (only if fitted with eddy current brake)
Eddy current brake prevention
Indication whether exists an installation of electric shore supply (fixed installation for servicing trains).
Existence of electric shore supply
Indication whether emergency plan exists.
Existence of emergency plan
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
Only applicable when selected value for 1.1.1.3.2.1 (ETCS present).
Indication whether data for national packet 44 applications is transmitted between track and train.
has ETCS national packet 44 application implemented
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.
Mandatory for TSI-compliant tunnels longer than 0.5 km
Indication of existence of evacuation and rescue points
Existence of evacuation and rescue points
Indication whether exists an installation of external cleaning facility (fixed installation for servicing trains) as defined in TSI INF
Existence of external cleaning facilities
Wheel material is ferromagnetic.
Ferromagnetic wheel material
Indicates if the vehicle type is fitted for flange lubrication.
Flange lubrication fitted
Existence of trackside HABD
Existence of trackside hot axle box detector (HABD)
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.
Indication whether level crossings (including pedestrian track crossing) exist on the section of line.
Existence of level crossings
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.
Possibility of preventing the use of the lubrication device (only if fitted with flange lubrication).
Has lubrication device prevention
Magnetic track brake fitted. New property defined to distinguish it from magneticBraking which is a RINF SKOS property.
Magnetic braking fitted
Possibility of preventing the use of the magnetic track brake (only if fitted with magnetic brake)
Magnetic brake prevention
All vehicles of this type must be equipped with a parking brake (parking brake mandatory for vehicles of this type).
Parking brake mandatory
Indicate, if there are any limits on noise levels.
Has noise level limits
Vehicle equipped with electric energy storage for traction purposes and with the function of charging with OCL at standstill.
Has OCL-chargeable onboard storage system for traction
The parameter must have as range a VehicleTypeConfigParameterSet, of which the VehicleTypeConfiguration at least contains one EnergySystem, from the ones recorded under `era:energySupplySystem`. Further, all of the ENE supply systems mentioned under that parameter must have a value for this parameter `era:hasOCLChargeableTractionStorage`.
Presence of derailment prevention and detection function.
Has onboard DDF/DPF
Only applicable for Traction Locomotives, which are intended to detect derailments or precursors to derailments in freight wagons hauled by the locomotive, with equipment fulfilling this function shall be located entirely on board the locomotive.
TSI conform energy meter for billing purposes installed on board.
Energy meter installed
The parameter must have as range a VehicleTypeConfigParameterSet, of which the VehicleTypeConfiguration at least contains one EnergySystem, from the ones recorded under `era:energySupplySystem`. Further, all of the ENE supply systems mentioned under that parameter must have a value for this parameter `era:energyMeterInstalled`.
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.
Existence of other train protection, control and warning systems installed
Indicates if a vehicle type (configuration) has a parking brake.
Indicates whether all vehicles of this type are equipped with a parking brake.
Has parking brake
Parking brake
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)
Indication of existence of phase separation and required information.
Phase separation
In case of existence of phase separation on the track or on the section of the line the option True shall be selected.
Indication of the existence of the curvature of the platform.
Curvature of the platform
Indication whether exists an installation of refuelling (fixed installation for servicing trains) as defined in TSI INF.
Existence of refuelling
Indication whether regenerative braking is permitted or not.
Possibility of preventing the use of the regenerative brake (only if fitted with regenerative brake).
Prevent regenerative brake use
Indication whether an installation of sand restocking exists (fixed installation for servicing trains).
Existence of sand restocking
Possibility of preventing the use of sanding.
Has sanding prevention
The existence of a schematic overview of the operational point in digital form.
Schematic overview of the operational point in digital form
Climatic conditions on the line are severe according to European standard.
Existence of severe climatic conditions
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.).
Indicates the presence of shunting restrictions.
Has shunting restrictions
Presence of derailment prevention and detection by signal processing.
Only applicable for Traction Locomotives, intended to process signals emitted by freight wagons, if provided with Derailment Prevention Function (‘DPF’) or Derailment Detection Function (‘DDF’) as defined in point 4.2.3.5.3 of TSI WAG.
Strictly local, historical or tourist use
Harmonised restriction code 4.3
Indication of existence of system separation
System separation
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.
Indication if there is any train detection system installed and fully compliant with the TSI CCS
Existence of train detection system fully compliant with the TSI
Annex I, Appendix A, Table A.2 -Index 77
Verification of compliance with TSI includes application of notified national rules (when they exist).
Indication whether exists an installation of toilet discharge (fixed installation for servicing trains) as defined in TSI INF
Existence of toilet discharge
Managing information about the completeness of the train
Has train completeness information
[Y/N] If =Y then TSI-Compliant OR NON-TSI-Compliant
Indication of existence of walkways
Existence of walkways
Existence of walkways in tunnel
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.
Indication whether exists an installation of water restocking (fixed installation for servicing trains) as defined in TSI INF
Existence of water restocking
Indicates the presence of a wheel slide protection system.
Has wheel slide protection system
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.
Compliance of structures with the High Speed Load Model (HSLM)
(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.
Specific for the French Italian and Swedish networks. Generation of trackside hot axle box detector.
Generation of trackside HABD
Waiting provision of possible answers by the French, Italian and Swedish NREs
Specific for the French, Italian and Swedish networks. Applicable if trackside HABD is not TSI compliant, identification of trackside hot axle box detector.
Identification of trackside HABD
Specific for the French Italian and Swedish networks. Applicable if trackside HABD is not TSI compliant, localisation of trackside hot axle box detector.
Railway location of trackside HABD
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
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).
Trackside HABD TSI compliant
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) ID and phone number of ERTMS/ETCS Radio Block Center
Non-harmonizable character string: [Contents of P42, not P143]
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))
Infrastructure manager (IM)'s code
Reserved for VehicleTypes authorised before the Fourth Railway Package. Complementing the vehicleTypeNumber of 10 characters, is maximally one 3-digit group ('XXX'), which represent the type's evolution after creation.
Type number
Reserved for VehicleTypes authorised under the Fourth Railway Package (Since 2018/545). Complementing the vehicleTypeNumber of 10 characters, is a combination of maximally two 3-digit groups ('ZZZ[-VVV]'), which represent the type's evolution after creation, as versions (of variants), variants (of variants), be it never as variants of versions.
The values to be mentioned are the ones defined in the issued vehicle type authorisation and/or vehicle authorisation for placing on the market.
Condition based restriction of use
Harmonised restriction code 4.2
The details of any specified condition is to be specified within a non-coded restriction (e.g. concerned constituents where CV modules apply).
Determines if the position of the topological element A in a relation is the origin of element A.
is on origin of element A
Determines if the position of the topological element B in a relation is the origin of element B.
is on origin of element B
Pass-by noise level was measured under reference conditions.
Reference pass-by noise level
Determines if the Application for Vehicle (Type) Authorisation is determining a preEngagementBaseline, and not yet the authorisation itself.
is pre-engagement application
is about pre-engagement
Belonging to a 'quieter route' in accordance with Article 5b of TSI NOI.
Belonging to a quieter route
Art 5b of Regulation (EU) 1304/2014 (amended by Regulation (EU) 2019/774) of 16 May 2019
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.
Some issued authorisation can include time-limited conditions for use. Time limitation is not a data provided by the applicant but a consequence of an authorisation decision (see Art 46(6) or regulation 2018/545)
Time based restriction of use
Harmonised restriction code 4.1
Indicates the suitability for transport on ferries.
Transportable on ferry
Kilometer number of the kilometric post related to line identification defining the location of an infrastructure element.
kilometer number
Railway location of Operational point
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] ).
Name of the kilometric post (optional).
kilometric post name
mileage post
Generic super-property for different types of length
Length
Position of the start of the walkway: [integer] m (from the same origin point of the kilometer post.) Lenght of the walkway: [integer] m
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 a topological linear element.
length of net linear element
Length of a Non-stopping area.
length of the non-stopping area
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.
Usable length of platform
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 between operational points at start and end of section of line.
Length of section of line
Total length of the siding/stabling track expressed in metres where trains can be parked safely.
Usable length of siding
Only applicable for a tunnel with length of 100 metres or more.
Length of a tunnel in metres from entrance portal to exit portal.
Length of tunnel
Length of a tunnel is expressed in metres from portal to portal at the level of the top of rail.
Length of individual Vehicles must use the `era:length` property.
letter marking
Letter marking
line identifier
Indicates the position of an object within a linear positioning system. For example, relative to a national railway line
Linear coordinate
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.
Frequency of track lineside distance indications.
Lineside distance indication frequency
Part of the load capability of a track that corresponds to the speed of the load model
Load capability speed
Maximum physical dimensions (height and width) to which an open rail wagon can be loaded
Loading gauge
TODO- review the range as it might be a list of SKOS concepts
Height of loading platform (for flat wagons and combined transport), given in mm.
Loading platform height
Existence of rules and restrictions of a strictly local nature
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'
Entry of Driver ID permitted while running According to the specification referenced in Appendix A-1, index [C]
M_NVDERUN
TSI CCS (Subset 26, chapter 7. 7.5.1.75 M_NVDERUN)
Mass per wheel, given in kg.
Mass per wheel
Maximum permitted axle load, given in tons.
Maximum Axle load
UIC leaflet 700-0
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] This parameter is applicable only if Overhead contact line (OCL) is selected for parameter 1.1.1.2.2.1.1.
In accordance with Implementing Decision 2014/880/EU and - by 16 March 2019 at the latest for DC systems; - by 30 June 2024 for AC systems.
Indication of the maximum allowable train current at standstill expressed in amperes.
Maximum current at standstill per pantograph
[ERATV] Parameter related to current taken by the vehicle when it is not in a traction or regenerative mode, e.g. preheating, air-condition, etc. When used for VehicleType, the parameter must have as range a VehicleTypeConfigParameterSet, of which the VehicleTypeConfiguration at least contains one EnergySystem, from the ones recorded under `era:energySupplySystem`. Further, all of the ENE supply systems mentioned under that parameter must have a value for this parameter `era:maxCurrentStandstillPantograph`.
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
Indication of maximum permitted distance between two consecutive axles in case of TSI non-compliance, given in millimetres.
Maximum permitted distance between two consecutive axles in case of TSI non-compliance
Deprecated as a RINF-parameter according to the amendment to the Regulation (EU) 2019/777. In ERATV, it was deprecated with (EU) 2019/776, but was used before that amendment..
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.
Maximum distance between end of train and first axle
Deprecated according to the amendment to the Regulation (EU) 2019/777. However, the parameter remains as it is also an ERATV parameter. Maximum flange height, given in millimetres.
Maximum height of the flange
RINF: The value of maximum permitted impedance given in ohm in case of TSI non-compliance. ERATV: Maximum impedance between opposite wheels of a wheelset.
Maximum permitted impedance between opposite wheels of a wheelset when not TSI compliant
Maximum length of the vehicle nose.
Maximum length vehicle nose
A value of `true`should be previously set for the property era:hasNoiseLevelLimit to be able to provide value for this property
Maximum allowed noise level in decibels (dB).
Maximum noise level
Applicable only to sections of lines belonging to TEN-T corridors. It applies to sections of lines where tracks have a TEN classification (1.1.1.1.2.1) that is neither 'off-TEN' nor not applicable ('N')
Maximum train length in meters allowed on a section of line, without special permission, for the operation of freight trains. In accordance with Regulation (EU) 2024/1679, Article 15(2)(c), this maximum length must be supported by the infrastructure manager's ability to allocate sufficient train paths for freight trains of at least 740 meters (including the locomotive or locomotives), as required for the TEN-T network.
Maximum train length allowed
The specific allocation requirements for single and double-track lines are as follows: - Double-track lines: At least one train path every 2 hours per direction on average daily. - Single-track lines: At least one train path every 3 hours per direction, with a minimum of 12 daily train paths allocated. These allocation conditions must be met if requested by a railway undertaking, as specified in Regulation (EU) 2024/1679, Article 16(2)(b)(i)-(ii).
Indication of the maximum allowable train current expressed in amperes.
Maximum train current
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
Indicate the speed limit in a tunnel
Tunnel speed limit
Indicates the maximun wind speed for which the bridge can operate
Maximun bridge wind
Highest point of the section of line above sea level in reference to Normal Amsterdam's Peil (NAP).
Maximum altitude
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 train deceleration given in m/s².
Maximum average deceleration
Maximum train deceleration
Maximum brake thermal energy capacity given in kJ
Maximum brake thermal energy capacity
The maximum value of the braking distance [in metres] of a train shall be given for the maximum line speed.
Maximum braking distance requested
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
Indication of the maximum contact wire height expressed in metres.
Maximum contact wire height
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.
When used for VehicleType, the parameter must have as range a VehicleTypeConfigParameterSet, of which the VehicleTypeConfiguration at least contains one EnergySystem, from the ones recorded under `era:energySupplySystem`. Further, all of the ENE supply systems mentioned under that parameter must have a value for this parameter `era:maximumContactWireHeight`.
Maximum design speed.
Maximum design speed
Exceptional vehicles have decimal values for this speed.
Harmonised restriction code 1.3.X, with X the value in km/h of this property.
Evaluation parameters must be added if preferred bands are not used.
NNN. An optional value could be filled in era:maximumInterferenceCurrentEvaluation
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
Maximum interference current limits allowed for track circuits for a defined frequency band.
Maximum interference current
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.
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.
Evaluation parameters if maximum interference current is not measured in the preferred bands
Maximum number of trainsets or locomotives coupled together in multiple operation.
Maximum locomotives coupled
Harmonised restriction code 1.4.X, with X the value of this property.
The maximum magnetic field limits allowed for axle counters (in dB µA/m) for a defined frequency band. Direction X.
Maximum magnetic field direction X
The maximumMagneticFieldDirectionX parameter is only applicable for axle counters.
The maximum magnetic field limits allowed for axle counters (in dB µA/m) for a defined frequency band. Direction Y.
Maximum magnetic field direction Y
The maximumMagneticFieldDirectionY parameter is only applicable for axle counters.
The maximum magnetic field limits allowed for axle counters (in dB µA/m) for a defined frequency band. Direction Z.
Maximum magnetic field direction Z
The maximumMagneticFieldDirectionZ parameter is applicable for axle counters.
Maximum permitted meter load, given in tons
Maximum permitted meter load
Nominal maximum operational speed on the line as a result of infrastructure, energy and control, command signalling subsystem characteristics expressed in kilometres/hour.
Maximum permitted speed
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.
"Speed on the line" shall be understood as speed on the track of the section of line in question.
At maximum service brake: Stopping distance, Maximum deceleration, for the load condition 'design mass under normal payload' at the design maximum speed.
Maximum service brake
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.
Maximum speed and cant deficiency
Maximum speed when empty
Maximum speed empty
Harmonised restriction code 1.3.X (empty)
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.
Temperature range (maximum)
Not applicable if line is not in scope of INF TSI
Limit for longitudinal track resistance given as a maximum allowed train deceleration and expressed in metres per square second.
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.
Maximum train length allowed on a line or section
Maximum Train Length
Measured distance from the origin of the LRS.
measured distance
Type meets the requirements necessary for validity of the vehicle authorisation granted by one Member State in other MSs.
Meets requirement vehicle authorisation
Minimum (permitted) axle load, given in tonnes.
Minimum (permitted) axle load
In RINF, it is Deprecated as a RINF-parameter according to the amendment to the Regulation (EU) 2019/777 and in ERATV with (EU) 2019/776, but was used before that amendment.
Minimum (permitted) distance between two consecutive axles
Indication of minimum permitted distance between two consecutive axles, given in millimetres.
Minimum permitted distance between first and last axle
Indication of minimum permitted distance between first and last axles, given in millimetres.
Minimum height of the flange
Minimum flange height, given in millimiters.
Minimum thickness of the flange
Minimum flange thickness, given in millimiters.
For impedance data coming from ERATV, frequency in Hertz (Hz)
minimum impedance frequency
For impedance data coming from ERATV, resistance in Ohm (Ω)
minimum impedance resistance
Minimum wheel rim width
Minimum width of the rim
For the selected DC voltage: [CCCC], as input capacitance [CCCC](Cin)
minimal vehicle input capacitance
For the selected DC voltage: [ZZZZ], as input impedance [ZZZZ](Zin)
minimal vehicle input impedance
Minimum wheel diameter
Minimum wheel diameter, given in millimiters.
Minimum vertical concave curve radius capability.
Minimum concave vertical radius
Indication of the minimum contact wire height expressed in metres.
Minimum contact wire height
When used for VehicleType, the parameter must have as range a VehicleTypeConfigParameterSet, of which the VehicleTypeConfiguration at least contains one EnergySystem, from the ones recorded under `era:energySupplySystem`. Further, all of the ENE supply systems mentioned under that parameter must have a value for this parameter `era:minimumContactWireHeight`.
Minimum vertical convex curve radius capability.
Minimum convex vertical radius
Radius of the smallest horizontal curve of the track in metres.
Minimum radius of horizontal curve
ERATV: Radius of the smallest horizontal curve capability of the vehicle, expressed in metres.
Harmonised restriction 1.1.X, with X the value in meters of this property.
To describe a straight section of line value " 99999" shall be used.
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.
Temperature range (minimum)
Part of the minimum radius of vertical curve that indicates the crest
Minimum radius of vertical curve crest
Part of the minimum radius of vertical curve that indicates the hollow
Minimum radius of vertical curve hollow
Maximum unguided length of fixed obtuse crossings is based on a minimum wheel diameter in service expressed in millimetres.
Minimum wheel diameter for fixed obtuse crossings
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.
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.
Need for more than one train protection, control and warning system required on board
National classification for load capability
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'.
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)
Mandatory for tunnels without value for 1.1.1.8.10 and where national values exist.
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.
National fire category of rolling stock required
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
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].
National Values used for the brake model
Non-harmonizable character string: [Contents of P3/P203] (TSI CCS, Annex I, Appendix A, Table A.2 - Subset-026)
Groups the non-coded restrictions, as a set of sentences. Can be used for any subClassOf `era:Restriction`.
Non coded restrictions
Number of elements in the rake of freight wagons (only for subcategory 'rake of freight wagons')
Number elements rake freight wagons
Number of pantographs in contact with the overhead contact line (OCL) (to be indicated for each energy supply system the vehicle is equipped for).
Number of pantographs in contact with OCL
The parameter must have as range a VehicleTypeConfigParameterSet, of which the VehicleTypeConfiguration at least contains one EnergySystem, from the ones recorded under `era:energySupplySystem`. Further, all of the ENE supply systems mentioned under that parameter must have a value for this parameter `era:numberOfPantographsInContactWithOCL`.
Number of toilets.
Number of toilets
Type of OCL used for the test of current collection performance (to be indicated for each energy supply system the vehicle is equipped for) (only if number of raised pantographs is more than 1).
Ocl type during current collection performance test
Given only present for initial types only, implemented without a Concept Scheme
The parameter is not applicable if `era:numberOfPantographsInContactWithOCL` < 2. The parameter must have as domain a VehicleTypeConfigParameterSet, of which the VehicleTypeConfiguration at least contains one EnergySystem, from the ones recorded under `era:energySupplySystem`. Further, all of the ENE supply systems mentioned under that parameter must have a value for this parameter `era:oclType`.
Relative distance from a reference kilometric post
offset
Offset from the origin in a topological coordinate.
offset from origin
Name normally related to the town or village or to traffic control purpose.
Name of operational point
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 of track gauge changeover facility
Opening hours of the section of a line or tunnel or a bridge
Opening hours limitation
Operational mass under normal payload.
Operational mass under normal payload
Operational mass in working order.
Operational mass in working order
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))
Infrastructure manager means any body or undertaking that is responsible in particular for establishing and maintaining railway infrastructure or a part thereof.
IM's code
Simplified example: :ABCD_IM rdf:type era:OrganisationRole; era:hasOrganisationRole era-skos:InfrastructureManager ; era:roleOf :ABCD . :ABCD rdf:type era:Body, org:Organization ; era:organisationCode "ABCD" ; era:role :ABCD_IM . :0000_IM rdf:type era:OrganisationRole; era:hasOrganisationRole era-skos:InfrastructureManager. era:roleOf :0000_ORG. :0000_ORG rdf:type era:Body, org:Organization; era:organisationCode "0000". #IM Code parameter - directly attached to a track :track2 rdf:type era:RunningTrack; era:infrastructureManager :0000_IM.
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.
This property is used to link an applicability to the precise value of the parameter
Parameter value
Maximum gradient on which the unit is kept immobilised by the parking brake alone (if the vehicle is fitted with it).
Parking brake maximum gradient
Pass-by noise level given in dB(A).
Pass-by noise level
Indicates whether a passenger train can perform commercial passenger activity at a primary location.
passenger flag
The parameter depended on the INF configuration, but should currently be considered independent of a Vehicle Configuration.
Permissible payload mass
Point at which IM authorises charging of electric energy storage for traction purposes at standstill.
Permission for charging electric energy storage for traction purposes at standstill
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
Permit of use of reflective plates
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
Indication of contact force allowed expressed in newton.
Contact force permitted
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).
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.
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
Phase info change supply system
The phase info is the indication of required several information on phase separation.
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.
Phase info distance type
Part of the phase info of a track that indicates the location from the start of the line where the new value is valid.
Phase info Km
Part of the phase info of a track that corresponds to the length of the phase separation in metres.
Phase info length
Part of the phase info of a track that shows whether a pantograph has to be lowered.
Phase info pantograph lowered
Part of the phase info of a track that shows whether the breaker has to be switched off.
Phase info switch off breaker
Unique platform identification or unique platform number within an Operational Point.
Identification of platform
Description of any portable boarding aids if considered in the design of the vehicle for meeting the PRM TSI requirements.
Portable boarding aids
primary location code
primary location name
Number of priority seats (min to max number).
Priority seats
Number of PRM accessible toilets.
Prm accessible toilets
Maximum train deceleration given in m/s² for a certain braking profile, at design maximum speed.
max deceleration for braking profile at max speed
Load Condition mass defining the braking profile, at design maximum speed.
profile defining load condition
The mass, defined by the load condition, as under - era:designMassExceptionalPayload - era:designMassNormalPayload - era:designMassWorkingOrder.
Maximum train stopping distance given in m for a certain braking profile, at design maximum speed.
max train stopping distance for braking profile at max speed
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".
Existence of GSM-R roaming to public networks
Sections of EIRENE not covered by references in TSI.
Mandatory if GSM-R is installed and era:publicNetworkRoaming is 'true'. Otherwise, it is not applicable.
If roaming to public networks is configured, please indicate to which networks, for which users and in which areas.
Details on GSM-R roaming to public networks
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.
Permission to use service brake in target speed monitoring
Q_NVSBTSMPERM
TSI CCS (Subset-026, chapter 7. 7.5.1.124 Q_NVSBTSMPERM)
Quasi-static guiding force (if exceeds the limit defined in TSI or not defined in the TSI), given in kN.
Quasi static guiding force
Value to be provided per supported track gauge.
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]
Radio Network ID
Special conditions implemented on-board to switch over between different radio systems. Given as combination of systems installed on board ('System XX'_'System YY').
Radio switch over special conditions
(deprecated) Type of railway system. Can be "High-speed" or "Conventional". Deprecated due to the lack of information
Rail system type
Part of the raised pantographs distance and speed of a track that corresponds to the minimum distance between pantographs, in metres.
Requirements for spacing between raised pantographs, at the given speed
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
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.
Part of the raised pantographs distance and speed of a track that corresponds to the number of pantographs.
Requirements for number of raised pantographs, at the given speed
Raised pantographs speed
Unique RBC identification (NID_C+NID_RBC) as defined in the specification referenced in Appendix A-1, index [C] (TSI CCS).
ID of ERTMS/ETCS Radio Block Center
NNNN NNNN NNNN NNNN with N a decimal number (0-9)
Unique RBC calling number (NID_RADIO) as defined in the specification referenced in Appendix A-1, index [C].
Phone number of ERTMS/ETCS Radio Block Center
Sections where permissive driving is possible in accordance with point 4.2.2.1.2 of TSI OPE
Sections where two steady red lights are required in accordance with TSI OPE
Steady red lights required
art 4.2.2.1.3.2. of Implementing Regulation (EU) 2019/773 'Freight trains'
Permissive driving allowed
From Regulation (EU) 2019/773 (TSI OPE) on tail marking in normal operation: this parameter is only for - freight trains during the transition phase until 31st December 2025 and - specific cases of Belgium, France, Italy, Portugal, and Spain who 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.
Parameters related to electromagnetic interferences
Distance in meters to the danger point
Relative distance of the danger point
TSI OPE Appendix D2 (2.3.3), the danger point relative distance from the signal itself.
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.
Indicates the position of an object relative to the linear coordinates of the associated topological object.
Relative position
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.
Sanding override by driver required
Description of the type of dangerous good that are not allowed in the tunnel
Restricted dangerous goods
Describes the period of time for which the transport of dangerous goods is not allowed in the Section of Line
Restricted periods of time for dangerous goods transportation
The use of string for this property is temporary until there is harmonization of the concrete type from time ontology.
Specific types of vehicles restricted in the tunnel.
Restricted type of vehicle in tunnel
Organisation code value that was revoked.
revoked code
Reference to the written declaration by the proposer referred to in Article 3(11) of Regulation (EU) No 402/2013
CSM-REA Safety Declaration
Document providing the schematic overview of the operational point
Schematic overview of the operational point
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).
Shortest distance between pantographs in contact with OCL
Strings have the format: `Single: ___(; Multiple: ___)` (values in meter) and no StubClass is foreseen
The parameter is not applicable if `era:numberOfPantographsInContactWithOCL` < 2. The parameter must have as range a VehicleTypeConfigParameterSet, of which the VehicleTypeConfiguration at least contains one EnergySystem, from the ones recorded under `era:energySupplySystem`. Further, all of the ENE supply systems mentioned under that parameter must have a value for this parameter `era:shortestDistanceBetweenPantographsInContactWithOCL`. Parameter must be given also for multiple operation, if `era:maximumLocomotivesCoupled` > 1.
Fixed installations for servicing trains
Unique siding identification or number within an Operational Point.
Identification of siding
Identifier of signal.
Name of signal
Operational identifier of the signal (on the track or in OP), as in the operational and maintenance provisions.
Number of sleeping places (min to max number)
Sleeping places
Special type of service on a line or a section of a line.
Specialized infrastructure
Any relevant information from the IM relating to the line layout
Specific information
This parameter allows the IM to provide plain text with specific information about the track
Start intrinsic coordinate
Start offset of the section from the origin.
start offset from origin
starting noise level given in dB(A).
Starting noise level
Static axle load under exceptional payload.
Static axle load under normal payload.
Static axle load under normal payload
Static axle load in working order.
Static axle load in working order
stationary noise level given in dB(A).
Stationary noise level
Structural category.
Structural category
This information is to be linked with parameter 1.1.1.1.2.4.4
Localisation of structures requiring specific checks
Railway location of structures requiring specific checks
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.
The railway location identifies the location of the structure in the system of reference of the line to which the track belongs.
A subset of elements with common characteristics could be identified with a unique name/id.
Name of a subset with common characteristics
Example: "ETCSbaseline2": describes all ETCS National values (1.1.1.3.2.16 group)
The numeric code for the subsidiary location
subsidiary location code
The common name given to the subsidiary location
subsidiary location name
Indication whether a switch over between different systems whilst running exists.
Existence of switch over between different protection, control and warning systems while running
Indication whether a switch over between different radio systems and no communication system whilst running exists.
Existence of switch over between different radio systems
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
(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) Information on system separation
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.
System separation info change supply system
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.
System separation info Km
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.
System separation info length
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.
System separation info pantograph lowered
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.
System separation info switch off breaker
NNN, with N as a digit from 0 to 9. Value NNN = 255 means ∞ (infinity), so values cannot be higher.
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]
T_NVCONTACT
TSI CCS (Subset 26, chapter 7. 7.5.1.148 T_NVCONTACT)
Precision: [NNN], with N a decimal number (0÷9), NNN = 255 means ∞ seconds, so values cannot be higher.
Maximum time for overriding the train trip in seconds. According to the specification referenced in Appendix A-1, index [C]
T_NVOVTRP
TSI CCS (Subset 26, chapter 7. 7.5.1.149 T_NVOVTRP)
Precision: [NNN], with N a decimal number (0÷9)
Not used anymore. It has been replaced by era:primaryLocationCode.
OP primary location code
Indication of the GIS identity (GIS ID) of the section of TEN-T database to which the track belongs
TEN geographic information system identity (GIS ID)
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. If no reference case is indicated.
Thermal capacity distance
Thermal capacity gradient (If no reference case is indicated)
Thermal capacity gradient
Thermal capacity speed (If no reference case is indicated)
Thermal capacity speed
Thermal capacity time (If no reference case is indicated)
Thermal capacity time
Deprecated according to the amendment to the Regulation (EU) 2019/777. Indication whether tilting functions are supported by ETCS.
Indication whether tilting functions are supported by ETCS
Total vehicle mass (for each vehicle of the unit), given in kg.
Total vehicle mass
Unique track identification or unique track number within operational point or section of line
Identification of track
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).
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').
Train control switch over special conditions
A value has to be provided when ETCS Level 2 is present, ETCS Baseline > 4 MR1 and IM confirms train integrity function is required).
Parameter only applicable when ETCS Baseline > 4 MR1 with operation requiring train integrity.
Indication whether train confirmation from on-board is required to access the line for safety reasons.
Train integrity confirmation from on-board (not from driver) necessary for line access
Value is modeled as xsd:boolean: - true = required - false = not required In hybrid operation, the requirement may depend on the operational mode; represent the applicable case using true/false, or omit the statement when not applicable.
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.
Tsi compliant
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.
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.
Switches and crossings are maintained to in service limit dimension as specified in TSI.
TSI compliance of in-service values for switches and crossings
If for existing track at least one parameter has less strict value than specified in the TSI, then 'N' (false) shall be selected.
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
Unique tunnel identification or unique tunnel number within Member State
Tunnel identification
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
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) End of tunnel kilometer
(deprecated) Start of tunnel kilometer
Serial number that identifies a vehicle type.
Type version number
Highest non-permanent voltage (Umax2) for France on lines not compliant with values defined in the EN50163:2004+A1:2007+A2:2020+A3:2022
Umax2 for the French network
ENE TSI: 4.2.4.1
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
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
Code composed of country code and alphanumeric operational point code.
Unique OP ID
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.
Indication if group 555 is used trackside or whether onboard has Voice SIM Card support for Group ID 555.
GSM-R use of group 555
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.
NNF, with N a decimal number (0 9), NNF must be divisible by 5, so F=(0|5), max. `600`
Speed limit allowing the driver to select the override function in km/h According to the specification referenced in Appendix A-1, index [C]
V_NVALLOWOVTRP
TSI CCS (Subset-026, Chapter 7. 7.5.1.161)
Format: [NNF], with N a decimal number (0÷9), [NNF] must be divisible by 5, so F=(0|5), max. `600`.
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]
V_NVSUPOVTRP
TSI CCS (Subset-026, chapter 7. 7.5.1.163 V_NVSUPOVTRP)
Format: [NNF], with N a decimal number (0÷9), [NNF] is divisible by 5 so F=(0|5), max. `600`.
Validity end date
To be deprecated with the introduction of temporal entity
Validity start date
Mean contact force.
Mean contact force
The parameter must have as range a VehicleTypeConfigParameterSet, of which the VehicleTypeConfiguration at least contains one EnergySystem, from the ones recorded under `era:energySupplySystem`. Further, all of the ENE supply systems mentioned under that parameter must have a value for this parameter `era:vehicleContactForce`. Older VehicleTypes did not distinguish between the onboard energy supply systems.
The force is given as a formula with a function of the speed. The value of the static force and of the maximum force expressed in newtons must be given with `era:vehicleContactForce`
Contact force formula.
Contact force formula
RCC *cannot* be executed if this parameter remains a xsd:string! See `era:vehicleContactForce`, a stub class is required for the RINF parameter.
Vehicle kinematic gauge that corresponds to other gauges assessed using the kinematic method
Vehicle kinematic gauge other
Vehicle Maximum sanding output, given in grams per second.
Vehicle max sanding output
Identification number of a vehicle or wagon.
Vehicle number
Manufacturing series of a vehicle.
Vehicle series
Part of the combination of maximum speed and maximum cant deficiency for which the vehicle was assessed. Corresponds to the maximum cant deficiency.
Vehicle type maximum cant deficiency
The parameter depended on the [INF, ENE, CCS]-configuration, but should currently be considered dependent only of the INF Vehicle Configuration.
Part of the combination of maximum speed and maximum cant deficiency for which the vehicle was assessed. Corresponds to the maximum speed.
Vehicle type maximum speed
Each type of vehicle shall receive a number consisting of 10 digits with the structure as in Annex III of the ERATV Decision. For the full Vehicle Identifier, use `dcterms:identifier`. For the complement before Fourth Railway package, use `era:includedVersions`. For the complements after the Fourth Railway Package, use `era:includedVersionsVariant`.
The Type Holder's name for the Type's Family/Platform, as encoded in the first set of 3 numbers in the `dcterms:identifier` of the Type.
Vehicle Type platform
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'.
Vehicles composing fixed formation
Unique number for EC declarations in accordance with Commission Implementing Regulation (EU) 2019/250.
EC declaration of verification for track relating to compliance with the requirements from TSIs applicable to control, command signalling subsystem
(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
EC declaration of verification for infrastructure element relating to compliance with the requirements from TSIs applicable to infrastructure subsystem
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
Document about practical arrangements for transmitting interoperability documents ERA/INF/10-2009/INT
(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 and operational communication implementation.
Voice operational communication implementation
Wheel gauge transformation method. Defined if more than one wheel gauges have been selected.
Wheel set gauge transformation method
Number of wheelchair accessible sleeping places (min to max number).
Wheelchair sleeping spaces
Number of wheelchair spaces (min to max number).
Wheelchair spaces
Braked mass.
Braked mass
Braked mass percentage (lambda).
Braked mass percentage
An unambiguous reference to the resource within a given context.
Identifier
Examples include International Standard Book Number (ISBN), Digital Object Identifier (DOI), and Uniform Resource Name (URN).
The WKT serialization of a geometry
Well Known Text line string representing the geographical shape of the track
Well Known Text polygonal shape
asWKT
Accurate geographical description
Industrial risks locations where it is dangerous for the driver to step out
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.
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.
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.
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.
組織を一意に識別するために使用できる会社登録番号などの識別子を与えます。
identifiant
identificatore
identifier
tiene identificador
ERA-specific activity aligned with prov:Activity (W3C PROV-O), used to describe changes affecting ERA resources.
Activity
Stub class for axle spacing
Is an organisation or a physical person
Body
Stub class for braking performance expressed as (lambda) brake weight/braked mass percentage, or braked mass
Braking performance
Stub class for braking profile under applicable load condition, stopping distance, deceleration and initial speed
Braking profile
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.
Bridge
Certification Level Document, as issued by a NoBo in the process of its certification/verification activities [RFU-STR-001]. The class can be reused as well for DeBo and AsBo certificates.
Certification Level Document
Every CLD is the result of a process by a recognised/accredited body (`vpa:AppropriateBody`) which is allowed to issue it to a `vpa:RequestingBody` needing it for a specific purpose, as defined in the IOD or SD. Several CLDs can support EC Declarations.
Certificate of a vehicle type. Can be in one of the following states: Amended, New, Suspended, Withdrawn.
Certificate
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)
Subset with common characteristics
A Compliance result, having its origin in a railway verification/certification/assessment process.
Contact Line System
Document in any of the ERA systems, e.g. reference document in RINF.
ERA Document
A collection of documents belonging together, as they contain - as a set - evidence in an ERA process like registration or authorisation.
Application Document Set
EC Declaration of Verification/Conformity/Suitability for Use, as issued by an Applicant in the process of certification/verification activities for IC's or subsystems.
EC Declaration of Verification/Conformity
Every EC Declaration is the outcome of a process assisted by a recognised/accredited body (`vpa:AppropriateBody`) which is allowed to issue the supporting CLD's to the `vpa:RequestingBody` needing it for a specific purpose, as defined in the IOD or SD. EC Declarations MUST refer to the required CLDs using `dcterms:requires` which can be grouped as `vpa:Evidence` in authorisation/registration processes.
SKOS concept representing a change request (CR) classified as an error in the ERTMS specifications and analysed by the Agency to identify whether it may prevent the system from providing normal service under Article 10 of the CCS TSI.
ERTMS error change request
TSI compliant train protection system ERTMS / ETCS application level and baseline related to the track side equipment.
ETCS
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.
ERA Feature
A trackside Hot Axle Box Detector (HABD), necessary for the route compatibility check. Specific for the French, Italian and Swedish networks
Hot Axle Box Detector
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 element
(deprecated) The infrastructure manager owns and operates the railway network and related infrastructure.
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.
Represents a kilometric post in the linear positioning system.
Kilometric Post
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
Level crossing
A reference to a specific railway line.
(deprecated) Railway location
Pieces of tracks composing the topology
Linear Element
This class represents an edge in the topological graph. It represents a linear element in the network.
Represents a section of a linear element.
Linear Element Section
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.
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
Represents coordinates in a linear positioning system.
Linear Positioning System Coordinate
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.
Lineside indications of distance
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.
This class together with properties loadCapabilityLineCategory and loadCapabilitySpeed replaces the previous loadCapability SKOS property.
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) Replaced by the era:Body class and era:manufacturer property. A company or organization that manufactures vehicles.
(deprecated) Manufacturer
Combination of maximum speed and maximum cant deficiency for which the vehicle was assessed.
(deprecated) Min axle load vehicle category
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.
Minimum Vehicle Impedance
The MinVehicleImpedance class is applicable for track circuits.
Presentation of parameter 1.2.2.0.3.3 'Minimum radius of vertical curve'
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) National railway line
Represents an area reference in the network.
Net Area Reference
Example: non-stopping area, cross section area, area of implementation of GPRS etc.
It is used for infrastructure elements positioned in relation to the topology as a subnetwork. (e.g.: tunnels, non-stopping area, stations etc.)
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 Basic Reference
It is a representation of all building blocks of the topology. It references an associated topological network element.
Represents a linear reference in the network.
Net Linear Reference
Example: tracks, tunnels, bridges, platform edges etc.
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.)
Represents a point reference in the network.
Net Point Reference
It is used for infrastructure elements positioned in relation to the topology as a point. (e.g.: signals, ETCS balises, buffer stops, etc.)
Defines a relation between two elements.
Net Relation
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).
Represents a non-linear element in the network.
Non-Linear Element
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.
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.
Operational Point
Represents an n-ary relationship between a Body and a role
Organisation Role
Represents the orientation of a railway object in relation to a carrier linear element. It can be described by direction, orientation and side.
Orientation
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.
Parameter applicability
Permissible Payload
Indication of required several information on phase separation.
Phase info
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).
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.
Primary Location
Primary locations are for example: stations, yards, halts, handover points, border points, open access terminals.
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.
Radio Block Center
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.
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.
List of reference border points that are specified in the RINF Application Guide.
Reference border point
A restriction, condition of use, having its origin in a railway verification/certification/permission process.
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
Running track
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.
A section of line means the part of line between adjacent operational points and may consist of several tracks.
Section Of Line
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.
Any track(s) within an operational point which is not used for operational routing of a train.
Sidings are all those tracks where running trains in service movements ends and which are not used for operational routing of a train.
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.
Apparatus by means of which a conventional visual or acoustic indication is given, generally concerning the movements/movement authorities of railway vehicles.
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.
Special area
Cover era-specialareatypes:SpecialAreaTypes when they are not located in Tunnels
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, with the location value provided as Kilometric point of the start; - restricted areas (non-stopping areas or industrial risk locations). For these areas in tunnels, use era:SpecialTunnelArea. Their length MUST be expressed using `era:length`.
Area or location within a tunnel: - a safe area: a walkway, evacuation and rescue points, with the location value provided as Kilometric point of the start; - a restricted area (non-stopping area or industrial risk location in a tunnel); - an area with special passing protocols
Cover special areas as in RINF 1.1.1.1.8/1.2.1.0.5 or other era-specialareatypes:SpecialAreaTypes when they are located in Tunnels
Their length MUST be expressed using `era:length`.
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.
Subsidiary location
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.
Switch
System separation info
Represents the TEN-T network classification of an element, including its network level, type of traffic, and associated European transport corridors.
TEN-T Corridor
The union of TemporalDuration that represents a time extent and TemporalEntity that represents a temporal interval or instant.
Temporal Feature
Represents a topological coordinate.
Topological Coordinate
A pair of rails over which rail borne vehicles can run.
Safety system used to detect the presence of vehicles on the railway track.
Train Detection System
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.
A specific vehicle or wagon able and allowed to operate over railway infrastructure.
Vehicle
(15) the decision issued by the authorising entity based on a reasonable assurance that the applicant and the entities involved in the design, manufacture, verification and validation of the vehicle have fulfilled their respective obligations and responsibilities in order to ensure conformity with essential requirements of the applicable legislation or to ensure conformity with the authorised type enabling that the vehicle may be placed on the market and may be used safely in the area of use according to the conditions for use and other restrictions, when applicable, specified in the vehicle authorisation and in the vehicle type authorisation;
Vehicle Authorisation for Placing on the Market
The process allowing the vehicle authorisation for placing in service (APIS). This authorisation case supported a Vehicle Application for APIS and was determined by exactly one set of Vehicles and if available a VehicleType. For the Authorisation as per EU 2018/545, use era:VehicleTypeAuthorisationCase, which covers all authorisations types under that legislation.
Vehicle APIS Case
Class strictly reserved to model APIS of vehicles as registered in EVR before the 2018/545
The notification, as submitted by the Applicant in line with (EU)2018/545, informs the authorising entity of the vehicle(s set) to be updated according to Article 16. The notification consists of one case as described in Art. 16 of (EU)2018/545, containing the vehicle type and EVNs, and linking to the required Evidence. The outcome of the notification process is an added comment in the `era:VehicleAuthorisation`, if accepted by the Authorising Entity.
Vehicle Authorisation Notification
The class could cover for some vehicle-specific updates, belonging to the VehicleType, given the Art. 16 notification process.
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) Vehicle Keeper
An `era:Restriction` which originates from a compliance check during the Vehicle's Registration.
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.
Vehicle Type
(16) the decision issued by the authorising entity based on reasonable assurance that the applicant and the entities involved in the design, manufacture, verification and validation of the vehicle type have fulfilled their obligations and responsibilities in order to ensure conformity with the essential requirements of the applicable legislation enabling that a vehicle manufactured according to this design may be placed on the market and may be used safely in the area of use of the vehicle type according to the conditions for use of the vehicle and other restrictions, when applicable, specified in the vehicle type authorisation and to be applied to all vehicle authorised in conformity to this type;
Vehicle Type Authorisation
The request, as submitted by the Applicant in line with (EU)2018/545, to allow the vehicle type authorisation and/or the vehicle authorisation for placing on the market. The application consists of one or more authorisation cases as described in Art. 14 of (EU)2018/545, and for authorisations before the Fourth Railway Package, a HistoricalAuthorisationCase must be used. The outcome of the application process is a `era:VehicleAuthorisation` or `era:VehicleTypeAuthorisation`.
Vehicle Type Authorisation Case
The process, as selected by the Applicant in line with (EU)2018/545, allowing the vehicle type authorisation and/or the vehicle authorisation for placing on the market. The type of authorisation cases are described in Art. 14 of (EU)2018/545, and for authorisations before the Fourth Railway Package, a HistoricalAuthorisationCase must be used. Each authorisation case supports a VehicleTypeAuthorisationApplication and is determined by exactly one VehicleType, and a set of Vehicles, which can be empty in some cases. For authorisations before the (EU)2018/545 legislation, use `era:VehicleAuthorisationCase.
A verification result as executed by a competent body on a section of a legal reference. The check can be positive or negative, and in the latter case, a restriction is expected. This Class is used to improve the link between verification outcomes and the verified scope of that process, and support its structured documentation.
Vehicle Type Authorisation Compliance Check
Restrictions, like coded and non-coded conditions for use, to be taken into account in the context of a Vehicle (Type) Authorisation. The restrictions are recorded by the Authorising Entities, possibly deduced during underlying verification and certification processes by competent bodies, and if possible are documented with a link to the legal reference and sections therein. In most cases, the Restriction will be dependent of a VehicleTypeConfiguration.
Vehicle Type Authorisation Restriction
Stub class linking a VehicleTypeConfiguration (`era:forConfiguration`) with parameters of the VehicleType that depend on that configuration.
Vehicle type configuration parameter set
The combination of supported Gauge, Energy Systems and/or CCO Systems for a vehicle type
Vehicle type configuration
1435mm / DC 3kV / Implementing Regulation (EU) 2019/776 Set_1
A set of vehicles together forming the Scope of a registration/authorisation case or involved as on whole in another process.
Vehicles Set
Feature
Geometry
Point
Bag
List
Concept
Time instant
Temporal duration
Temporal entity
Organisation
Organization
Organizzazione
organización
Document
Person
A clearly separated part of a Request, identified clearly by its Scope(s). Each Case has an individual PermissionType as objective. A Request consists out of minimally one Case.
Case
Regroups the result of a compliance check on a specific section of an applicable Requirement as registered in Documented Evicence. If needed, links this examined section to a specific Restriction.
Compliance
Evidence
Issued by an AppropriateBody, it is the summary of its formal and accredited verification process, enabling the receiver (RequestingBody) to issue a Request for a Permission to the PermittingBody.
Evidence Document
Issued by a PermittingBody, it enables - mostly because of legal frameworks in place - the RequestingBody to execute the processes covered under these requirement frameworks.
Permission
Issued by a Requesting Body to a PermittingBody, and supported by at least one Case, while being supported by the necessary DocumentedEvidence, it intends to enable the reception of a Permission.
Request
Issued by an Appropriate Body in connection with its documented evidence on a certain requirement, it contains all aspects to take into account in order to accept the DocumentedEvidence as proof, enabling the scope of the Permission. It is possible that the Restriction limits the Permission in the same way.
Restriction
A collection of Scopes together defining a Case. Scope is mostly the specific material object of the Case, where the Case groups them together.
Scope
If the version is not fully compatible it shall be indicated in brackets.
ETCS baseline incompatibility indication
GSM-R and ETCS L2 must be installed for this parameter to be applicable. Multiple values are allowed.
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.
Specific constraints imposed by the GSM-R network operator on ETCS on-board units only able to operate in circuit-switch
ADDITIONAL COMMENTS ON: Class B or other radio systems installed
Additional comments on Class B / Legacy Radio Systems installed
Is a comment field provided in the ERATV User interface when documenting 4.13.2.3
ADDITIONAL COMMENTS ON: Class B or other train protection, control and warning systems installed
Additional comments on Class B / Legacy train protection, control and warning systems installed