Technical Annex on the application of the common specifications of the Register of Infrastructure

Body ^C

IRI: http://data.europa.eu/949/Body

Is subclass of

Organization

Person

Has Properties

Role

Bridge ^C

IRI: http://data.europa.eu/949/Bridge

Is subclass of

Infrastructure element

Contact Line System ^C

IRI: http://data.europa.eu/949/ContactLineSystem

Has RINF parameters

Type of contact line system ( 1.1.1.2.2.1.1 )

Energy supply system (Voltage and frequency) ( 1.1.1.2.2.1.2 )

Umax2 for the French network ( 1.1.1.2.2.1.3 )

Maximum train current ( 1.1.1.2.2.2 )

Maximum current at standstill per pantograph ( 1.1.1.2.2.3 | 1.2.2.0.6.1 )

Permission for regenerative braking ( 1.1.1.2.2.4 )

Conditions applying in regards to regenerative braking ( 1.1.1.2.2.4.1 )

Maximum contact wire height ( 1.1.1.2.2.5 )

Minimum contact wire height ( 1.1.1.2.2.6 )

Current or power limitation on board required ( 1.1.1.2.5.1 )

Permission for charging electric energy storage for traction purposes at standstill ( 1.2.1.0.7.1 )

Permitted conditions for charging electric energy storage for traction purposes at standstill ( 1.2.1.0.7.2 )

Validation

Validation Rules:

Contact Line System Shape

ERA Document ^C

IRI: http://data.europa.eu/949/Document

Is subclass of

Document

Has Properties

Document URL

ERA Feature ^C

IRI: http://data.europa.eu/949/Feature

Is subclass of

Feature

Is superclass of

Net Basic Reference

Has Properties

Validity

ETCS ^C

IRI: http://data.europa.eu/949/ETCS

Has RINF parameters

European Train Control System (ETCS) level ( 1.1.1.3.2.1 | 1.2.1.1.1.1 )

ETCS M_version ( 1.1.1.3.2.10 | 1.2.1.1.1.10 )

Is the ETCS trackside engineered to transmit Track Conditions ( 1.1.1.3.2.12 | 1.2.1.1.1.12 )

Track conditions which can be transmitted ( 1.1.1.3.2.12.1 | 1.2.1.1.1.12.1 )

ETCS baseline ( 1.1.1.3.2.2 | 1.2.1.1.1.2 )

ETCS infill installed line-side ( 1.1.1.3.2.4 | 1.2.1.1.1.4 )

ETCS system compatibility ( 1.1.1.3.2.9 | 1.2.1.1.1.9 )

Validation

Validation Rules:

Etcsshape

Hot Axle Box Detector ^C

IRI: http://data.europa.eu/949/HABD

Is subclass of

Infrastructure element

Has RINF parameters

Trackside HABD TSI compliant ( 1.1.1.1.7.5 )

Identification of trackside HABD ( 1.1.1.1.7.6 )

Generation of trackside HABD ( 1.1.1.1.7.7 )

Railway location of trackside HABD ( 1.1.1.1.7.8 )

Direction of measurement of trackside HABD ( 1.1.1.1.7.9 )

Infrastructure element ^C

IRI: http://data.europa.eu/949/InfrastructureElement

Is superclass of

Bridge

Hot Axle Box Detector

Kilometric Post

Level crossing

Operational Point

Platform edge

Radio Block Center

Section Of Line

Signal

Special area

Switch

Track

Tunnel

Has RINF parameters

Operating language ( 1.1.0.0.1.2 | 1.2.0.0.0.8 )

Primary location ( 1.2.0.0.0.3 )

Has Properties

Belongs to

Has part

In country

Infrastructure manager

Is part of

Net reference

Parameter applicability

Validation

Validation Rules:

Infrastructure Element Shape

Kilometric Post ^C

IRI: http://data.europa.eu/949/KilometricPost

Is subclass of

Infrastructure element

Has RINF parameters

Kilometer number ( 1.2.0.0.0.6 )

Has Properties

Has linear referencing system

Kilometric post name

Measured distance

Level crossing ^C

IRI: http://data.europa.eu/949/LevelCrossing

Is subclass of

Infrastructure element

Linear Element ^C

IRI: http://data.europa.eu/949/LinearElement

Is subclass of

Net element

Is superclass of

Linear Element Section

Has Properties

Length of net linear element

Additional Information

General explanation:

This class represents a node in the topological graph. It represents a linear element in the network.

Linear Element Section ^C

IRI: http://data.europa.eu/949/LinearElementSection

Is subclass of

Linear Element

Has Properties

Applies in both directions

End offset from the origin.

On element

Start offset from origin

Additional Information

General explanation:

A linear element section is a finer granularity of a linear element, representing a specific portion of it. This concept is introduced to address the cases when a linear element needs to be split such as a part of it is used by a net referencing (more in the paragraph describing the positioning on the network). By using start and end offsets measured from origin of the element in ascending order, sections eliminate the need for intrinsic coordinates and instead rely on distances along the linear element.

Linear Positioning System ^C

IRI: http://data.europa.eu/949/LinearPositioningSystem

Has Properties

Line identifier

Net reference

Type of line referencing system

Linear Positioning System Coordinate ^C

IRI: http://data.europa.eu/949/LinearPositioningSystemCoordinate

Has Properties

Km post for reference

Offset

Lineside indications of distance ^C

IRI: http://data.europa.eu/949/LinesideDistanceIndication

Has Properties

Lineside distance indication appearance

Lineside distance indication frequency

Lineside distance indication positioning

Validation

Validation Rules:

Lineside Distance Indication

Validation Messages:

linesideDistanceIndication (1.1.1.0.0.3) : The track must have exactly one value of a lineside distance indication that must be an instance of LinesideDistanceIndication. This error may be due to the track having no value, having more than one value or having a value that is not an instance of the class LinesideDistanceIndication.

Load capability ^C

IRI: http://data.europa.eu/949/LoadCapability

Has Properties

Load capability line category

Load capability speed

Additional Information

General explanation:

At this step, RINF does not allow to enter additional data referred to additional speed regulations and operating requirements relating to locomotives (e.g., locomotive classes and associated maximum speed) or traffic types (e.g., maximum speed of freight traffic or passenger traffic).

The load capability describes the weakest point of this track within this section of line (which is normally a bridge or other sub-track structure). It is expressed as a combination of the line category and speed permitted for trains exerting loads defined for this line category. The result of the classification process is set out in EN 15528:2021 (Annex A) and referred to in that standard as “Line Category”.

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)

Maximum magnetic field ^C

IRI: http://data.europa.eu/949/MaximumMagneticField

Has Properties

Maximum magnetic field direction X

Maximum magnetic field direction Y

Maximum magnetic field direction Z

Minimum radius of vertical curve ^C

IRI: http://data.europa.eu/949/MinimumVerticalRadius

Has Properties

Minimum radius of vertical curve crest

Minimum radius of vertical curve hollow

Validation

Validation Rules:

Minimum Vertical Radius

Validation Messages:

minimumVerticalRadius (1.2.2.0.3.3) : The siding or subset with common characteristics must have at most one value of minimum vertical radius that must be an instace of MinimumVerticalRadius. This error may be due to the track having more than one value or having a value that is not an instance of the class MinimumVerticalRadius.

Additional Information

General explanation:

Presentation of parameter 1.2.2.0.3.3 'Minimum radius of vertical curve'

Minimum Vehicle Impedance ^C

IRI: http://data.europa.eu/949/MinVehicleImpedance

Has RINF parameters

Minimum Vehicle Impedance (Voltage applicable)

Has Properties

Minimal vehicle input capacitance

Minimal vehicle input impedance

Validation

Validation Rules:

Min Vehicle Impedance Shape

Additional Information

General explanation:

The MinVehicleImpedance class is applicable for track circuits.

See also:

https://www.era.europa.eu/system/files/2023-09/index077_-_ERA_ERTMS_033281_v5.pdf

Net Area Reference ^C

IRI: http://data.europa.eu/949/NetAreaReference

Is subclass of

Net Basic Reference

Has Properties

Includes list of linear references

Additional Information

General explanation:

It is used for infrastructure elements positioned in relation to the topology as a subnetwork. (e.g.: tunnels, non-stopping area, stations etc.)

Example:

Example: non-stopping area, cross section area, area of implementation of GPRS etc.

Net Basic Reference ^C

IRI: http://data.europa.eu/949/NetBasicReference

Is subclass of

ERA Feature

Is superclass of

Net Area Reference

Net Linear Reference

Net Point Reference

Additional Information

General explanation:

See also:

https://wiki.railtopomodel.org/wiki/Object_positioning_in_the_network

Net element ^C

IRI: http://data.europa.eu/949/NetElement

Is superclass of

Linear Element

Non-Linear Element

Additional Information

See also:

https://wiki.railtopomodel.org/wiki/Topological_structure_(network)

Net Linear Reference ^C

IRI: http://data.europa.eu/949/NetLinearReference

Is subclass of

Net Basic Reference

Has Properties

Ends at

Has sequence

Starts at

Additional Information

General explanation:

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.)

Example:

Example: tracks, tunnels, bridges, platform edges etc.

Net Point Reference ^C

IRI: http://data.europa.eu/949/NetPointReference

Is subclass of

Net Basic Reference

Has Properties

Applies to direction

Has line referencing system coordinate

Has topological coordinate

Additional Information

General explanation:

It is used for infrastructure elements positioned in relation to the topology as a point. (e.g.: signals, ETCS balises, buffer stops, etc.)

Net Relation ^C

IRI: http://data.europa.eu/949/NetRelation

Has Properties

Element A

Element B

Is on origin of element A

Is on origin of element B

Navigability

Additional Information

General explanation:

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).

See also:

https://wiki.railtopomodel.org/wiki/Topological_structure_(network)

Non-Linear Element ^C

IRI: http://data.europa.eu/949/NonLinearElement

Is subclass of

Net element

Has Properties

Aggregates

Additional Information

General explanation:

Non-linear elements complement the linear structure by serving as connection or interaction points. They represent features such as stations, depots, or complex junctions. They often serve as aggregation points for linear elements, where multiple tracks meet or like logical entities that support operations like passenger boarding or train storage. These elements may optionally aggregate linear elements.

Operational Point ^C

IRI: http://data.europa.eu/949/OperationalPoint

Is subclass of

Infrastructure element

Has RINF parameters

Existence of rules and restrictions of a strictly local nature ( 1.1.1.4.1 | 1.2.3.1 )

Documents regarding the rules or restrictions of a strictly local nature available by the IM ( 1.1.1.4.2 | 1.2.3.2 )

Name of operational point ( 1.2.0.0.0.1 )

Unique OP ID ( 1.2.0.0.0.2 )

Type of operational point ( 1.2.0.0.0.4 )

Type of track gauge changeover facility ( 1.2.0.0.0.4.1 )

Schematic overview of the operational point in digital form ( 1.2.0.0.0.7 )

Schematic overview of the operational point ( 1.2.0.0.0.7.1 )

Digital schematic overview ( 1.2.0.0.0.7.2 )

Has Properties

Reference border point

Validation

Validation Rules:

Operational Point Shape

Organisation Role ^C

IRI: http://data.europa.eu/949/OrganisationRole

Has RINF parameters

Organisation code ( 1.1.0.0.0.1 | 1.1.1.1.8.1 | 1.2.1.0.0.1 | 1.2.1.0.5.1 | 1.2.1.0.6.1 | 1.2.2.0.0.1 | 1.2.2.0.5.1 )

Has Properties

Has organisation role

Role of

Validation

Validation Rules:

Organisation Role Shape

Orientation ^C

IRI: http://data.europa.eu/949/Orientation

Has Properties

Carrier linear element

Direction

On side

Orientation

Parameter applicability ^C

IRI: http://data.europa.eu/949/ParameterApplicability

Is subclass of

Temporal Feature

Has Properties

Of parameter

Parameter value

Parameter value type

Validation

Validation Rules:

Parameter Applicability Shape

Phase info ^C

IRI: http://data.europa.eu/949/PhaseInfo

Has Properties

Phase info change supply system

Phase info distance type

Phase info Km

Phase info length

Phase info pantograph lowered

Phase info switch off breaker

Platform edge ^C

IRI: http://data.europa.eu/949/PlatformEdge

Is subclass of

Infrastructure element

Has RINF parameters

TEN classification of track ( 1.1.1.1.2.1 | 1.2.1.0.2.1 | 1.2.1.0.6.3 | 1.2.2.0.0.3 )

Identification of platform ( 1.2.1.0.6.2 )

Usable length of platform ( 1.2.1.0.6.4 )

Height of platform ( 1.2.1.0.6.5 )

Existence of platform assistance for starting train ( 1.2.1.0.6.6 )

Range of use of the platform boarding aid ( 1.2.1.0.6.7 )

Curvature of the platform ( 1.2.1.0.6.8 )

Validation

Validation Rules:

Platform Edge Shape

Primary Location ^C

IRI: http://data.europa.eu/949/PrimaryLocation

Is subclass of

Operational Point

Section Of Line

Has Properties

Container handling flag

Freight flag

Handover point flag

Primary location code

Primary location name

Validation

Validation Rules:

Primary Location Shape

Additional Information

Example:

Primary locations are for example: stations, yards, halts, handover points, border points, open access terminals.

See also:

http://taf-jsg.info/wp-content/uploads/2024/01/20231018-JGS-Handbook-3.4-with-XSD-3.4.0.0.pdf

Radio Block Center ^C

IRI: http://data.europa.eu/949/RadioBlockCenter

Is subclass of

Infrastructure element

Has RINF parameters

Reasons for which an ETCS Radio Block Center can reject a train ( 1.1.1.3.2.15 | 1.2.1.1.1.15 )

Phone number of ERTMS/ETCS Radio Block Center ( 1.1.1.3.2.17 | 1.2.1.1.1.17 )

ID of ERTMS/ETCS Radio Block Center ( 1.1.1.3.2.17 | 1.2.1.1.1.17 )

Validation

Validation Rules:

Radio Block Center Shape

Additional Information

See also:

https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32023R1693&qid=1698394526534

https://www.era.europa.eu/system/files/2023-09/index003_-_SUBSET-023_v400.pdf

Reference border point ^C

IRI: http://data.europa.eu/949/ReferenceBorderPoint

Has Properties

Border point identification

Requirements for number of raised pantographs and spacing between them, at the given speed ^C

IRI: http://data.europa.eu/949/RaisedPantographsDistanceAndSpeed

Has Properties

Raised Pantographs Speed

Requirements for number of raised pantographs, at the given speed

Requirements for spacing between raised pantographs, at the given speed

Additional Information

General explanation:

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.

Running track ^C

IRI: http://data.europa.eu/949/RunningTrack

Is subclass of

Track

Has RINF parameters

Identification of track ( 1.1.1.0.0.1 | 1.2.1.0.0.2 )

Normal running direction ( 1.1.1.0.0.2 )

Lineside distance indication ( 1.1.1.0.0.3 )

EC declaration of verification for infrastructure element relating to compliance with the requirements from TSIs applicable to infrastructure subsystem ( 1.1.1.1.1.1 | 1.2.1.0.1.1 | 1.2.2.0.1.1 )

EI declaration of demonstration (as defined in Commission 2014/881/EU (2)) relating to compliance with the requirements from TSIs applicable to infrastructure subsystem ( 1.1.1.1.1.2 | 1.2.1.0.1.2 | 1.2.2.0.1.2 )

TEN classification of track ( 1.1.1.1.2.1 | 1.2.1.0.2.1 | 1.2.1.0.6.3 | 1.2.2.0.0.3 )

TEN geographic information system identity (GIS ID) ( 1.1.1.1.2.1.2 )

Category of line ( 1.1.1.1.2.2 | 1.2.1.0.2.2 )

Part of a Railway Freight Corridor ( 1.1.1.1.2.3 | 1.2.1.0.2.3 )

Load capability ( 1.1.1.1.2.4 )

National classification for load capability ( 1.1.1.1.2.4.1 )

Compliance of structures with the High Speed Load Model (HSLM) ( 1.1.1.1.2.4.2 )

Railway location of structures requiring specific checks ( 1.1.1.1.2.4.3 )

Document with the procedure(s) for static and dynamic route compatibility checks ( 1.1.1.1.2.4.4 )

Maximum permitted speed ( 1.1.1.1.2.5 )

Temperature range ( 1.1.1.1.2.6 )

Maximum altitude ( 1.1.1.1.2.7 )

Existence of severe climatic conditions ( 1.1.1.1.2.8 )

Gauging ( 1.1.1.1.3.1.1 | 1.2.1.0.3.4 )

Railway location of particular points requiring specific checks ( 1.1.1.1.3.1.2 | 1.2.1.0.3.5 )

Document with the transversal section of the particular points requiring specific checks ( 1.1.1.1.3.1.3 | 1.2.1.0.3.6 )

Standard combined transport profile number for swap bodies ( 1.1.1.1.3.4 )

Standard combined transport profile number for semi-trailers ( 1.1.1.1.3.5 )

Specific information ( 1.1.1.1.3.5.1 )

Gradient profile ( 1.1.1.1.3.6 )

Minimum radius of horizontal curve ( 1.1.1.1.3.7 | 1.2.2.0.3.2 )

Standard combined transport profile number for containers ( 1.1.1.1.3.8 )

Standard combined transport profile number for roller units ( 1.1.1.1.3.9 )

Nominal track gauge ( 1.1.1.1.4.1 | 1.2.1.0.4.1 )

Cant deficiency ( 1.1.1.1.4.2 )

Rail inclination ( 1.1.1.1.4.3 )

Existence of ballast ( 1.1.1.1.4.4 )

TSI compliance of in-service values for switches and crossings ( 1.1.1.1.5.1 )

Minimum wheel diameter for fixed obtuse crossings ( 1.1.1.1.5.2 )

Maximum train deceleration ( 1.1.1.1.6.1 )

Use of eddy current brakes ( 1.1.1.1.6.2 | 1.2.1.0.4.2 )

Use of magnetic brakes ( 1.1.1.1.6.3 | 1.2.1.0.4.3 )

Document with the conditions for the use of eddy current brakes ( 1.1.1.1.6.4 )

Document with the conditions for the use of magnetic brakes ( 1.1.1.1.6.5 )

Use of flange lubrication forbidden ( 1.1.1.1.7.1 )

Steady red lights required ( 1.1.1.1.7.10 )

Belonging to a quieter route ( 1.1.1.1.7.11 )

Permit of use of reflective plates ( 1.1.1.1.7.12 )

Conditions for use of reflective plates ( 1.1.1.1.7.12.1 )

Existence of level crossings ( 1.1.1.1.7.2 )

Existence of trackside hot axle box detector (HABD) ( 1.1.1.1.7.4 )

EC declaration of verification for track relating to compliance with the requirements from TSIs applicable to energy subsystem ( 1.1.1.2.1.1 )

EI declaration of demonstration (as defined Recommendation 2014/881/EU) for track relating to compliance with the requirements from TSIs applicable to energy subsystem ( 1.1.1.2.1.2 )

Accepted TSI compliant pantograph heads ( 1.1.1.2.3.1 )

Accepted other pantograph heads ( 1.1.1.2.3.2 )

Requirements for number of raised pantographs and spacing between them, at the given speed ( 1.1.1.2.3.3 )

Contact strip material metallic content ( 1.1.1.2.3.4 )

Permitted contact strip material ( 1.1.1.2.3.4 )

Phase separation ( 1.1.1.2.4.1.1 )

Information on phase separation ( 1.1.1.2.4.1.2 )

System separation ( 1.1.1.2.4.2.1 )

Information on system separation ( 1.1.1.2.4.2.2 )

Distance between signboard and phase separation ending ( 1.1.1.2.4.3 )

Contact force permitted ( 1.1.1.2.5.2 )

Automatic dropping device required ( 1.1.1.2.5.3 )

Document with restriction related to power consumption of specific electric traction unit(s) ( 1.1.1.2.5.4 )

Document with restriction related to the position of Multiple Traction unit(s) to comply with contact line separation ( 1.1.1.2.5.5 )

EC declaration of verification for track relating to compliance with the requirements from TSIs applicable to control, command signalling subsystem ( 1.1.1.3.1.1 )

Reasons for Error corrections required, but accepted by the IM for the on-board ETCS, GSM-R and/or ATO function ( 1.1.1.3.1.2 | 1.2.1.1.1.19 )

Error corrections required for the on-board ETCS, GSM-R and/or ATO function ( 1.1.1.3.1.2 | 1.2.1.1.1.19 )

ETCS level for degraded situation ( 1.1.1.3.10.1 | 1.2.1.1.9.1 )

Other train protection, control and warning systems for degraded situation ( 1.1.1.3.10.2 | 1.2.1.1.9.2 )

Maximum braking distance requested ( 1.1.1.3.11.1 )

Availability by the IM of additional information ( 1.1.1.3.11.2 )

Documents available by the IM relating to braking performance ( 1.1.1.3.11.3 )

ATO Grade of Automation ( 1.1.1.3.13.1 | 1.2.1.1.10.1 )

ATO System version ( 1.1.1.3.13.2 | 1.2.1.1.10.2 )

ATO communication system ( 1.1.1.3.13.3 | 1.2.1.1.10.3 )

Safe consist length information from on-board necessary for access the line and SIL ( 1.1.1.3.2.11 | 1.2.1.1.1.11 )

ETCS trackside implements level crossing procedure or an equivalent solution ( 1.1.1.3.2.13 | 1.2.1.1.1.13 )

Cant Deficiency used for the basic SSP ( 1.1.1.3.2.14 | 1.2.1.1.1.14 )

Other Cant Deficiency train categories for which the ETCS trackside is configured to provide SSP ( 1.1.1.3.2.14.1 | 1.2.1.1.1.14.1 )

D_NVROLL ( 1.1.1.3.2.16.1 | 1.2.1.1.1.16.1 )

M_NVDERUN ( 1.1.1.3.2.16.10 | 1.2.1.1.1.16.10 )

Q_NVDRIVER_ADHES ( 1.1.1.3.2.16.11 | 1.2.1.1.1.16.11 )

Q_NVSBTSMPERM ( 1.1.1.3.2.16.12 | 1.2.1.1.1.16.12 )

National Values used for the brake model ( 1.1.1.3.2.16.13 | 1.2.1.1.1.16.13 )

Q_NVEMRRLS ( 1.1.1.3.2.16.2 | 1.2.1.1.1.16.2 )

V_NVALLOWOVTRP ( 1.1.1.3.2.16.3 | 1.2.1.1.1.16.3 )

V_NVSUPOVTRP ( 1.1.1.3.2.16.4 | 1.2.1.1.1.16.4 )

D_NVOVTRP ( 1.1.1.3.2.16.5 | 1.2.1.1.1.16.5 )

T_NVOVTRP ( 1.1.1.3.2.16.6 | 1.2.1.1.1.16.6 )

D_NVPOTRP ( 1.1.1.3.2.16.7 | 1.2.1.1.1.16.7 )

T_NVCONTACT ( 1.1.1.3.2.16.8 | 1.2.1.1.1.16.8 )

M_NVCONTACT ( 1.1.1.3.2.16.9 | 1.2.1.1.1.16.9 )

Big Metal Mass ( 1.1.1.3.2.18 | 1.2.1.1.1.18 )

ETCS infill necessary for line access ( 1.1.1.3.2.3 | 1.2.1.1.1.3 )

Existence of operating restrictions or conditions ( 1.1.1.3.2.6 | 1.2.1.1.1.6 )

Train integrity confirmation from on-board (not from driver) necessary for line access ( 1.1.1.3.2.8 | 1.2.1.1.1.8 )

GSM-R version ( 1.1.1.3.3.1 | 1.2.1.1.2.1 )

Radio system compatibility data ( 1.1.1.3.3.10 | 1.2.1.1.2.10 )

GSM-R network is configured to allow forced de-registration of a functional number by another driver ( 1.1.1.3.3.11 | 1.2.1.1.2.11 )

Radio Network ID ( 1.1.1.3.3.12 | 1.2.1.1.2.13 )

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 ( 1.1.1.3.3.2 | 1.2.1.1.2.2 )

Optional GSM-R functions ( 1.1.1.3.3.3 | 1.2.1.1.2.3 )

Additional information on network characteristics ( 1.1.1.3.3.3.1 | 1.2.1.1.2.3.1 )

GPRS for ETCS ( 1.1.1.3.3.3.2 | 1.2.1.1.2.3.2 )

Area of implementation of GPRS ( 1.1.1.3.3.3.3 | 1.2.1.1.2.3.3 )

GSM-R use of group 555 ( 1.1.1.3.3.4 | 1.2.1.1.2.4 )

GSM-R networks covered by a roaming agreement ( 1.1.1.3.3.5 | 1.2.1.1.2.5 )

Existence of GSM-R roaming to public networks ( 1.1.1.3.3.6 | 1.2.1.1.2.6 )

Details on GSM-R roaming to public networks ( 1.1.1.3.3.7 | 1.2.1.1.2.7 )

No GSMR coverage ( 1.1.1.3.3.8 | 1.2.1.1.2.8 )

Radio system compatibility voice ( 1.1.1.3.3.9 | 1.2.1.1.2.9 )

Existence of train detection system fully compliant with the TSI ( 1.1.1.3.4.1 | 1.2.1.1.3.1 )

Train protection legacy system ( 1.1.1.3.5.3 | 1.2.1.1.4.1 )

Other radio systems installed (Radio Legacy Systems) ( 1.1.1.3.6.1 | 1.2.1.1.5.1 )

Special conditions to switch over between different class B train protection, control and warning systems ( 1.1.1.3.8.1.1 | 1.2.1.1.7.1.1 )

Special instructions to switch over between different radio systems ( 1.1.1.3.8.2.1 | 1.2.1.1.7.2.1 )

Special technical conditions required to switch over between ERTMS/ETCS and Class B systems ( 1.1.1.3.8.3 | 1.2.1.1.7.3 )

Existence and TSI compliance of rules for magnetic fields emitted by a vehicle ( 1.1.1.3.9.1 | 1.2.1.1.8.1 )

Existence and TSI compliance of limits in harmonics in the traction current of vehicles ( 1.1.1.3.9.2 | 1.2.1.1.8.2 )

Existence of rules and restrictions of a strictly local nature ( 1.1.1.4.1 | 1.2.3.1 )

Documents regarding the rules or restrictions of a strictly local nature available by the IM ( 1.1.1.4.2 | 1.2.3.2 )

Specific constraints imposed by the GSM-R network operator on ETCS on-board units only able to operate in circuit-switch ( 1.2.1.1.2.12 )

Has Properties

Contact line system

Has bridge

Hot axle box detector (HABD)

Train detection system

TSI compliant train protection system (ETCS)

Validation

Validation Rules:

Running Track Shape

Additional Information

General explanation:

There might be more than one track within the Section of Line, so then the whole set of data for track has to be repeated for each track within the SoL.

Section Of Line ^C

IRI: http://data.europa.eu/949/SectionOfLine

Is subclass of

Infrastructure element

Has RINF parameters

National line identification ( 1.1.0.0.0.2 )

Operational point at start of section of line ( 1.1.0.0.0.3 )

Operational point at end of section of line ( 1.1.0.0.0.4 )

Length of section of line ( 1.1.0.0.0.5 )

Nature of Section of Line ( 1.1.0.0.0.6 )

Industrial risks — locations where it is dangerous for the driver to step out ( 1.1.0.0.1.1 )

Operational regime ( 1.1.0.0.1.3 )

Validation

Validation Rules:

Section Of Line Shape

Additional Information

General explanation:

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.

Section with train detection limitation ^C

IRI: http://data.europa.eu/949/FrenchTrainDetectionSystemLimitation

Has Properties

Section with train detection limitation

Section with train detection limitation number, only for French network

Siding ^C

IRI: http://data.europa.eu/949/Siding

Is subclass of

Track

Has RINF parameters

TEN classification of track ( 1.1.1.1.2.1 | 1.2.1.0.2.1 | 1.2.1.0.6.3 | 1.2.2.0.0.3 )

Maximum current at standstill per pantograph ( 1.1.1.2.2.3 | 1.2.2.0.6.1 )

Maximum contact wire height ( 1.1.1.2.2.5 )

Identification of siding ( 1.2.2.0.0.2 )

Usable length of siding ( 1.2.2.0.2.1 )

Gradient for stabling tracks ( 1.2.2.0.3.1 )

Minimum radius of vertical curve ( 1.2.2.0.3.3 )

Existence of toilet discharge ( 1.2.2.0.4.1 )

Existence of external cleaning facilities ( 1.2.2.0.4.2 )

Existence of water restocking ( 1.2.2.0.4.3 )

Existence of refuelling ( 1.2.2.0.4.4 )

Existence of sand restocking ( 1.2.2.0.4.5 )

Existence of electric shore supply ( 1.2.2.0.4.6 )

Validation

Validation Rules:

Siding Shape

Signal ^C

IRI: http://data.europa.eu/949/Signal

Is subclass of

Infrastructure element

Has RINF parameters

Name of signal ( 1.1.1.3.14.1 | 1.2.1.0.8.1 )

Type of signal ( 1.1.1.3.14.2 | 1.2.1.0.8.2 )

Signal orientation ( 1.1.1.3.14.3 | 1.2.1.0.8.3 )

Relative distance of the danger point ( 1.1.1.3.14.4 | 1.2.1.0.8.4 )

Has Properties

Has orientation

Validation

Validation Rules:

Signal Shape

Additional Information

See also:

https://www.era.europa.eu/system/files/2023-09/index003_-_SUBSET-023_v400.pdf

Special area ^C

IRI: http://data.europa.eu/949/SpecialArea

Is subclass of

Infrastructure element

Is superclass of

Special tunnel area

Has Properties

Special area type

Special tunnel area ^C

IRI: http://data.europa.eu/949/SpecialTunnelArea

Is subclass of

Special area

Subset with common characteristics ^C

IRI: http://data.europa.eu/949/CommonCharacteristicsSubset

Is subclass of

List

Has RINF parameters

Industrial risks — locations where it is dangerous for the driver to step out ( 1.1.0.0.1.1 )

Lineside distance indication ( 1.1.1.0.0.3 )

EC declaration of verification for infrastructure element relating to compliance with the requirements from TSIs applicable to infrastructure subsystem ( 1.1.1.1.1.1 | 1.2.1.0.1.1 | 1.2.2.0.1.1 )

EI declaration of demonstration (as defined in Commission 2014/881/EU (2)) relating to compliance with the requirements from TSIs applicable to infrastructure subsystem ( 1.1.1.1.1.2 | 1.2.1.0.1.2 | 1.2.2.0.1.2 )

TEN classification of track ( 1.1.1.1.2.1 | 1.2.1.0.2.1 | 1.2.1.0.6.3 | 1.2.2.0.0.3 )

TEN geographic information system identity (GIS ID) ( 1.1.1.1.2.1.2 )

Category of line ( 1.1.1.1.2.2 | 1.2.1.0.2.2 )

Part of a Railway Freight Corridor ( 1.1.1.1.2.3 | 1.2.1.0.2.3 )

Load capability ( 1.1.1.1.2.4 )

National classification for load capability ( 1.1.1.1.2.4.1 )

Compliance of structures with the High Speed Load Model (HSLM) ( 1.1.1.1.2.4.2 )

Railway location of structures requiring specific checks ( 1.1.1.1.2.4.3 )

Document with the procedure(s) for static and dynamic route compatibility checks ( 1.1.1.1.2.4.4 )

Maximum permitted speed ( 1.1.1.1.2.5 )

Temperature range ( 1.1.1.1.2.6 )

Maximum altitude ( 1.1.1.1.2.7 )

Existence of severe climatic conditions ( 1.1.1.1.2.8 )

Gauging ( 1.1.1.1.3.1.1 | 1.2.1.0.3.4 )

Railway location of particular points requiring specific checks ( 1.1.1.1.3.1.2 | 1.2.1.0.3.5 )

Document with the transversal section of the particular points requiring specific checks ( 1.1.1.1.3.1.3 | 1.2.1.0.3.6 )

Standard combined transport profile number for swap bodies ( 1.1.1.1.3.4 )

Standard combined transport profile number for semi-trailers ( 1.1.1.1.3.5 )

Specific information ( 1.1.1.1.3.5.1 )

Gradient profile ( 1.1.1.1.3.6 )

Minimum radius of horizontal curve ( 1.1.1.1.3.7 | 1.2.2.0.3.2 )

Standard combined transport profile number for containers ( 1.1.1.1.3.8 )

Standard combined transport profile number for roller units ( 1.1.1.1.3.9 )

Nominal track gauge ( 1.1.1.1.4.1 | 1.2.1.0.4.1 )

Cant deficiency ( 1.1.1.1.4.2 )

Rail inclination ( 1.1.1.1.4.3 )

Existence of ballast ( 1.1.1.1.4.4 )

TSI compliance of in-service values for switches and crossings ( 1.1.1.1.5.1 )

Minimum wheel diameter for fixed obtuse crossings ( 1.1.1.1.5.2 )

Maximum train deceleration ( 1.1.1.1.6.1 )

Use of eddy current brakes ( 1.1.1.1.6.2 | 1.2.1.0.4.2 )

Use of magnetic brakes ( 1.1.1.1.6.3 | 1.2.1.0.4.3 )

Document with the conditions for the use of eddy current brakes ( 1.1.1.1.6.4 )

Document with the conditions for the use of magnetic brakes ( 1.1.1.1.6.5 )

Use of flange lubrication forbidden ( 1.1.1.1.7.1 )

Steady red lights required ( 1.1.1.1.7.10 )

Belonging to a quieter route ( 1.1.1.1.7.11 )

Permit of use of reflective plates ( 1.1.1.1.7.12 )

Conditions for use of reflective plates ( 1.1.1.1.7.12.1 )

Existence of level crossings ( 1.1.1.1.7.2 )

Acceleration allowed near level crossing ( 1.1.1.1.7.3 )

Existence of trackside hot axle box detector (HABD) ( 1.1.1.1.7.4 )

Fire category of rolling stock required ( 1.1.1.1.8.10 | 1.2.1.0.5.7 | 1.2.2.0.5.7 )

National fire category of rolling stock required ( 1.1.1.1.8.11 | 1.2.1.0.5.8 | 1.2.2.0.5.8 )

Existence of walkways ( 1.1.1.1.8.12 | 1.2.1.0.5.10 | 1.2.2.0.5.9 )

Existence of evacuation and rescue points ( 1.1.1.1.8.13 | 1.2.1.0.5.11 | 1.2.2.0.5.10 )

EC declaration of verification relating to compliance with the requirements from TSIs applicable to railway tunnel ( 1.1.1.1.8.5 | 1.2.1.0.5.3 | 1.2.2.0.5.3 )

EI declaration of demonstration (as defined in Recommendation 2014/881/EU) relating to compliance with the requirements from TSIs applicable to railway tunnel ( 1.1.1.1.8.6 | 1.2.1.0.5.4 | 1.2.2.0.5.4 )

Cross section area ( 1.1.1.1.8.8 )

Compliance of the tunnel with TSI INF ( 1.1.1.1.8.8.1 )

Existence of emergency plan ( 1.1.1.1.8.9 | 1.2.1.0.5.6 | 1.2.2.0.5.6 )

EC declaration of verification for track relating to compliance with the requirements from TSIs applicable to energy subsystem ( 1.1.1.2.1.1 )

EI declaration of demonstration (as defined Recommendation 2014/881/EU) for track relating to compliance with the requirements from TSIs applicable to energy subsystem ( 1.1.1.2.1.2 )

Accepted TSI compliant pantograph heads ( 1.1.1.2.3.1 )

Accepted other pantograph heads ( 1.1.1.2.3.2 )

Requirements for number of raised pantographs and spacing between them, at the given speed ( 1.1.1.2.3.3 )

Contact strip material metallic content ( 1.1.1.2.3.4 )

Permitted contact strip material ( 1.1.1.2.3.4 )

Phase separation ( 1.1.1.2.4.1.1 )

Information on phase separation ( 1.1.1.2.4.1.2 )

System separation ( 1.1.1.2.4.2.1 )

Information on system separation ( 1.1.1.2.4.2.2 )

Distance between signboard and phase separation ending ( 1.1.1.2.4.3 )

Contact force permitted ( 1.1.1.2.5.2 )

Automatic dropping device required ( 1.1.1.2.5.3 )

Document with restriction related to power consumption of specific electric traction unit(s) ( 1.1.1.2.5.4 )

Document with restriction related to the position of Multiple Traction unit(s) to comply with contact line separation ( 1.1.1.2.5.5 )

EC declaration of verification for track relating to compliance with the requirements from TSIs applicable to control, command signalling subsystem ( 1.1.1.3.1.1 )

Reasons for Error corrections required, but accepted by the IM for the on-board ETCS, GSM-R and/or ATO function ( 1.1.1.3.1.2 | 1.2.1.1.1.19 )

Error corrections required for the on-board ETCS, GSM-R and/or ATO function ( 1.1.1.3.1.2 | 1.2.1.1.1.19 )

ETCS level for degraded situation ( 1.1.1.3.10.1 | 1.2.1.1.9.1 )

Other train protection, control and warning systems for degraded situation ( 1.1.1.3.10.2 | 1.2.1.1.9.2 )

Maximum braking distance requested ( 1.1.1.3.11.1 )

Availability by the IM of additional information ( 1.1.1.3.11.2 )

Documents available by the IM relating to braking performance ( 1.1.1.3.11.3 )

ATO Grade of Automation ( 1.1.1.3.13.1 | 1.2.1.1.10.1 )

ATO System version ( 1.1.1.3.13.2 | 1.2.1.1.10.2 )

ATO communication system ( 1.1.1.3.13.3 | 1.2.1.1.10.3 )

Type of signal ( 1.1.1.3.14.2 | 1.2.1.0.8.2 )

Signal orientation ( 1.1.1.3.14.3 | 1.2.1.0.8.3 )

Safe consist length information from on-board necessary for access the line and SIL ( 1.1.1.3.2.11 | 1.2.1.1.1.11 )

ETCS trackside implements level crossing procedure or an equivalent solution ( 1.1.1.3.2.13 | 1.2.1.1.1.13 )

Cant Deficiency used for the basic SSP ( 1.1.1.3.2.14 | 1.2.1.1.1.14 )

Other Cant Deficiency train categories for which the ETCS trackside is configured to provide SSP ( 1.1.1.3.2.14.1 | 1.2.1.1.1.14.1 )

D_NVROLL ( 1.1.1.3.2.16.1 | 1.2.1.1.1.16.1 )

M_NVDERUN ( 1.1.1.3.2.16.10 | 1.2.1.1.1.16.10 )

Q_NVDRIVER_ADHES ( 1.1.1.3.2.16.11 | 1.2.1.1.1.16.11 )

Q_NVSBTSMPERM ( 1.1.1.3.2.16.12 | 1.2.1.1.1.16.12 )

National Values used for the brake model ( 1.1.1.3.2.16.13 | 1.2.1.1.1.16.13 )

Q_NVEMRRLS ( 1.1.1.3.2.16.2 | 1.2.1.1.1.16.2 )

V_NVALLOWOVTRP ( 1.1.1.3.2.16.3 | 1.2.1.1.1.16.3 )

V_NVSUPOVTRP ( 1.1.1.3.2.16.4 | 1.2.1.1.1.16.4 )

D_NVOVTRP ( 1.1.1.3.2.16.5 | 1.2.1.1.1.16.5 )

T_NVOVTRP ( 1.1.1.3.2.16.6 | 1.2.1.1.1.16.6 )

D_NVPOTRP ( 1.1.1.3.2.16.7 | 1.2.1.1.1.16.7 )

T_NVCONTACT ( 1.1.1.3.2.16.8 | 1.2.1.1.1.16.8 )

M_NVCONTACT ( 1.1.1.3.2.16.9 | 1.2.1.1.1.16.9 )

Big Metal Mass ( 1.1.1.3.2.18 | 1.2.1.1.1.18 )

ETCS infill necessary for line access ( 1.1.1.3.2.3 | 1.2.1.1.1.3 )

ETCS national packet 44 application implemented ( 1.1.1.3.2.5 | 1.2.1.1.1.5 )

Has ETCS national packet 44 application implemented ( 1.1.1.3.2.5 | 1.2.1.1.1.5 )

Existence of operating restrictions or conditions ( 1.1.1.3.2.6 | 1.2.1.1.1.6 )

Document with operating restrictions or conditions ( 1.1.1.3.2.6 | 1.2.1.1.1.6 )

Train integrity confirmation from on-board (not from driver) necessary for line access ( 1.1.1.3.2.8 | 1.2.1.1.1.8 )

GSM-R version ( 1.1.1.3.3.1 | 1.2.1.1.2.1 )

Radio system compatibility data ( 1.1.1.3.3.10 | 1.2.1.1.2.10 )

GSM-R network is configured to allow forced de-registration of a functional number by another driver ( 1.1.1.3.3.11 | 1.2.1.1.2.11 )

Radio Network ID ( 1.1.1.3.3.12 | 1.2.1.1.2.13 )

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 ( 1.1.1.3.3.2 | 1.2.1.1.2.2 )

Optional GSM-R functions ( 1.1.1.3.3.3 | 1.2.1.1.2.3 )

Additional information on network characteristics ( 1.1.1.3.3.3.1 | 1.2.1.1.2.3.1 )

GPRS for ETCS ( 1.1.1.3.3.3.2 | 1.2.1.1.2.3.2 )

Area of implementation of GPRS ( 1.1.1.3.3.3.3 | 1.2.1.1.2.3.3 )

GSM-R use of group 555 ( 1.1.1.3.3.4 | 1.2.1.1.2.4 )

GSM-R networks covered by a roaming agreement ( 1.1.1.3.3.5 | 1.2.1.1.2.5 )

Existence of GSM-R roaming to public networks ( 1.1.1.3.3.6 | 1.2.1.1.2.6 )

Details on GSM-R roaming to public networks ( 1.1.1.3.3.7 | 1.2.1.1.2.7 )

No GSMR coverage ( 1.1.1.3.3.8 | 1.2.1.1.2.8 )

Radio system compatibility voice ( 1.1.1.3.3.9 | 1.2.1.1.2.9 )

Existence of train detection system fully compliant with the TSI ( 1.1.1.3.4.1 | 1.2.1.1.3.1 )

Train protection legacy system ( 1.1.1.3.5.3 | 1.2.1.1.4.1 )

Other radio systems installed (Radio Legacy Systems) ( 1.1.1.3.6.1 | 1.2.1.1.5.1 )

Existence of switch over between different protection, control and warning systems while running ( 1.1.1.3.8.1 | 1.2.1.1.7.1 )

Special conditions to switch over between different class B train protection, control and warning systems ( 1.1.1.3.8.1.1 | 1.2.1.1.7.1.1 )

Existence of switch over between different radio systems ( 1.1.1.3.8.2 | 1.2.1.1.7.2 )

Special instructions to switch over between different radio systems ( 1.1.1.3.8.2.1 | 1.2.1.1.7.2.1 )

Special technical conditions required to switch over between ERTMS/ETCS and Class B systems ( 1.1.1.3.8.3 | 1.2.1.1.7.3 )

Existence and TSI compliance of rules for magnetic fields emitted by a vehicle ( 1.1.1.3.9.1 | 1.2.1.1.8.1 )

Existence and TSI compliance of limits in harmonics in the traction current of vehicles ( 1.1.1.3.9.2 | 1.2.1.1.8.2 )

Existence of rules and restrictions of a strictly local nature ( 1.1.1.4.1 | 1.2.3.1 )

Documents regarding the rules or restrictions of a strictly local nature available by the IM ( 1.1.1.4.2 | 1.2.3.2 )

List of vehicle types already identified as compatible with Traffic load and load carrying capacity of infrastructure and train detection systems ( 1.1.1.5.1 )

List of vehicles already identified as compatible with Traffic load and load carrying capacity of infrastructure and train detection systems ( 1.1.1.5.2 )

Diesel or other thermal traction allowed ( 1.2.1.0.5.9 )

Height of platform ( 1.2.1.0.6.5 )

Existence of platform assistance for starting train ( 1.2.1.0.6.6 )

Range of use of the platform boarding aid ( 1.2.1.0.6.7 )

Curvature of the platform ( 1.2.1.0.6.8 )

Specific constraints imposed by the GSM-R network operator on ETCS on-board units only able to operate in circuit-switch ( 1.2.1.1.2.12 )

Gradient for stabling tracks ( 1.2.2.0.3.1 )

Minimum radius of vertical curve ( 1.2.2.0.3.3 )

Existence of toilet discharge ( 1.2.2.0.4.1 )

Existence of external cleaning facilities ( 1.2.2.0.4.2 )

Existence of water restocking ( 1.2.2.0.4.3 )

Existence of refuelling ( 1.2.2.0.4.4 )

Existence of sand restocking ( 1.2.2.0.4.5 )

Existence of electric shore supply ( 1.2.2.0.4.6 )

Has Properties

Contact line system

Contains

Hot axle box detector (HABD)

In country

Infrastructure manager

Name of a subset with common characteristics

Parameter applicability

Subset of

Train detection system

TSI compliant train protection system (ETCS)

Validation

Validation Rules:

Common Characteristics Subset Shape

Subsidiary location ^C

IRI: http://data.europa.eu/949/SubsidiaryLocation

Has Properties

Allocation company

Linked to primary location

Subsidiary location code

Subsidiary location name

Subsidiary location type

Validation

Validation Rules:

Subsidiary Location Shape

Additional Information

See also:

http://taf-jsg.info/wp-content/uploads/2024/01/20231018-JGS-Handbook-3.4-with-XSD-3.4.0.0.pdf

Switch ^C

IRI: http://data.europa.eu/949/Switch

Is subclass of

Infrastructure element

System separation info ^C

IRI: http://data.europa.eu/949/SystemSeparationInfo

Has Properties

System separation info pantograph lowered

System separation info change supply system

System separation info Km

System separation info length

System separation info switch off breaker

Temporal Feature ^C

IRI: http://data.europa.eu/949/TemporalFeature

Is subclass of

Temporal duration

Temporal entity

Is superclass of

Parameter applicability

Topological Coordinate ^C

IRI: http://data.europa.eu/949/TopologicalCoordinate

Has Properties

Offset from origin

On linear element

Track ^C

IRI: http://data.europa.eu/949/Track

Is subclass of

Infrastructure element

Is superclass of

Running track

Siding

Has RINF parameters

Connected to ( 1.1.1.0.1.2 | 1.2.4.1 )

Acceleration allowed near level crossing ( 1.1.1.1.7.3 )

ETCS national packet 44 application implemented ( 1.1.1.3.2.5 | 1.2.1.1.1.5 )

Has ETCS national packet 44 application implemented ( 1.1.1.3.2.5 | 1.2.1.1.1.5 )

Document with operating restrictions or conditions ( 1.1.1.3.2.6 | 1.2.1.1.1.6 )

Existence of switch over between different protection, control and warning systems while running ( 1.1.1.3.8.1 | 1.2.1.1.7.1 )

Existence of switch over between different radio systems ( 1.1.1.3.8.2 | 1.2.1.1.7.2 )

Train Detection System ^C

IRI: http://data.europa.eu/949/TrainDetectionSystem

Has RINF parameters

Frequency bands for detection ( 1.1.1.3.4.2 | 1.2.1.1.3.2 )

Evaluation parameters if maximum interference current is not measured in the preferred bands ( 1.1.1.3.4.2.1 | 1.2.1.1.3.2.1 )

Maximum interference current ( 1.1.1.3.4.2.1 | 1.2.1.1.3.2.1 )

Vehicle impedance ( 1.1.1.3.4.2.2 | 1.2.1.1.3.2.2 )

Maximum magnetic field ( 1.1.1.3.4.2.3 | 1.2.1.1.3.2.3 )

Type of train detection system ( 1.1.1.3.7.1.1 | 1.2.1.1.3.1.1 )

Type of track circuits or axle counters to which specific checks are needed ( 1.1.1.3.7.1.2 | 1.2.1.1.6.1 )

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" ( 1.1.1.3.7.1.3 | 1.2.1.1.6.2 )

Section with train detection limitation ( 1.1.1.3.7.1.4 | 1.2.1.1.6.3 )

Validation

Validation Rules:

Train Detection System Shape

Tunnel ^C

IRI: http://data.europa.eu/949/Tunnel

Is subclass of

Infrastructure element

Has RINF parameters

Fire category of rolling stock required ( 1.1.1.1.8.10 | 1.2.1.0.5.7 | 1.2.2.0.5.7 )

National fire category of rolling stock required ( 1.1.1.1.8.11 | 1.2.1.0.5.8 | 1.2.2.0.5.8 )

Existence of walkways ( 1.1.1.1.8.12 | 1.2.1.0.5.10 | 1.2.2.0.5.9 )

Existence of evacuation and rescue points ( 1.1.1.1.8.13 | 1.2.1.0.5.11 | 1.2.2.0.5.10 )

Tunnel identification ( 1.1.1.1.8.2 | 1.2.1.0.5.2 | 1.2.2.0.5.2 )

Start of tunnel kilometer ( 1.1.1.1.8.3 )

Start of tunnel location ( 1.1.1.1.8.3 )

End of tunnel ( 1.1.1.1.8.4 )

End of tunnel kilometer ( 1.1.1.1.8.4 )

EC declaration of verification relating to compliance with the requirements from TSIs applicable to railway tunnel ( 1.1.1.1.8.5 | 1.2.1.0.5.3 | 1.2.2.0.5.3 )

EI declaration of demonstration (as defined in Recommendation 2014/881/EU) relating to compliance with the requirements from TSIs applicable to railway tunnel ( 1.1.1.1.8.6 | 1.2.1.0.5.4 | 1.2.2.0.5.4 )

Length of tunnel ( 1.1.1.1.8.7 | 1.2.1.0.5.5 | 1.2.2.0.5.5 )

Cross section area ( 1.1.1.1.8.8 )

Compliance of the tunnel with TSI INF ( 1.1.1.1.8.8.1 )

Document available from the IM with precise description of the tunnel ( 1.1.1.1.8.8.2 )

Existence of emergency plan ( 1.1.1.1.8.9 | 1.2.1.0.5.6 | 1.2.2.0.5.6 )

Diesel or other thermal traction allowed ( 1.2.1.0.5.9 )

Has Properties

Special tunnel area

Validation

Validation Rules:

Tunnel Shape

Section of line generic information ^{DP OP}

General Information

Number:

1.1.0.0.0

Belongs to parameters group

RINF Technical characteristic

Related parameters

Organisation code ( 1.1.0.0.0.1 | 1.1.1.1.8.1 | 1.2.1.0.0.1 | 1.2.1.0.5.1 | 1.2.1.0.6.1 | 1.2.2.0.0.1 | 1.2.2.0.5.1 )

National line identification ( 1.1.0.0.0.2 )

Operational point at start of section of line ( 1.1.0.0.0.3 )

Operational point at end of section of line ( 1.1.0.0.0.4 )

Length of section of line ( 1.1.0.0.0.5 )

Nature of Section of Line ( 1.1.0.0.0.6 )

Organisation code ^DP

Parameter of

Organisation Role

General Information

Number:

1.1.0.0.0.1

1.1.1.1.8.1

1.2.1.0.0.1

1.2.1.0.5.1

1.2.1.0.6.1

1.2.2.0.0.1

1.2.2.0.5.1

XML Name:

SOLIMCode

Deadline:

In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest

Belongs to parameters group

Section of line generic information ( 1.1.0.0.0 )

Running track generic information ( 1.1.1.0.0 )

Tunnel ( 1.1.1.1.8 | 1.2.1.0.5 | 1.2.2.0.5 )

Platform ( 1.2.1.0.6 )

Siding ( 1.2.2 )

Identifier

Data Format

Data Presentation

String

Format:

AAAA

Flags

Applicability Flags:

Y

Validation

Validation Rules:

Organisation Code

Validation Messages:

organisationCode (1.2.1.0.6.1, 1.1.0.0.0.1, 1.1.1.1.8.1, 1.2.1.0.0.1, 1.2.1.0.5.1, 1.2.2.0.0.1, 1.2.2.0.5.1): An OrganisationRole must have exactly one value of organisationCode. This error may be due to not having a value, having more than one value, having a value that is not a string or having a value that is not a four character code

OPE TSI References

Appendix D2 Index

1.1

Additional Information

General explanation:

The Code is a unique identifier for the Infrastructure Manager and it shall be verified on national level.
- If the IM is subject to TAF/TAP TSIs, it corresponds to the code used in TAF/TAP TSIs.
- In other cases, it corresponds to the "organisation code" assigned by the Agency for the specific needs of the RINF.
Each Section of Line shall concern only one IM.
To be able to follow the "only once" principle, the infrastructure manager code is a property of the organisation having the role of infrastructuer manager. For data provision, a subset of elements with common characteristics should be created with the era:infrastructureManager property having as value the instance of the infrastructure mananger role.

Example:

Simplified example:
:ABCD_IM rdf:type era:OrganisationRole;
era:hasOrganisationRole era-skos:InfrastructureManager.
era:organisationCode "ABCD".

:0000_IM rdf:type era:OrganisationRole;
era:hasOrganisationRole era-skos:InfrastructureManager.
era:organisationCode "0000".

:imNetwork rdf:type era:SubsetWithCommonCharacteristics;
era:infrastructureManager :ABCD_IM.
#IM code parameter as a common characteristic
:track1 rdf:type era:Track;
era:belongsTo :imNetwork.
#IM Code parameter - directly attached to a track
:track2 rdf:type era:Track;
era:infrastructureManager :0000_IM.

National line identification ^OP

Parameter of

Section Of Line

General Information

Number:

1.1.0.0.0.2

XML Name:

SOLLineIdentification

Belongs to parameters group

Section of line generic information ( 1.1.0.0.0 )

Data Format

Data Presentation

Linear Positioning System

Validation

Validation Rules:

National Line So L

Validation Messages:

nationalLine (1.1.0.0.0.2): Each SoL belongs to exactly one linear positioning system. This error is due to not having a value, having more than one value, or having a value that is not an instance of LinearPositioningSystem.

Additional Information

General explanation:

Each SoL can belong to only one national line.

In case when SoL is the track connecting between OPs within big node (resulting from division of big station into several smaller) the line can be identified using the name of this track.

Operational point at start of section of line ^OP

Parameter of

Section Of Line

General Information

Number:

1.1.0.0.0.3

XML Name:

SOLOPStart

Deadline:

In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest

Belongs to parameters group

Section of line generic information ( 1.1.0.0.0 )

Data Format

Data Presentation

Operational Point

Flags

Applicability Flags:

Y

Validation

Validation Rules:

Op Start Exists

Op Start

Validation Messages:

opStart (1.1.0.0.0.3): There is an error with the SoL {$this} ({?solLabel}) and its OP start which does not exist.

opStart (1.1.0.0.0.3): There must be at most one OP start for this section of line and it must be different from the OP end.

OPE TSI References

Appendix D2 Index

3.1.1

Additional Information

General explanation:

Each SoL may have only one start OP, and each OP has unique OP ID within the MS. The “uniqueOPID” is defined in parameter 1.2.0.0.0.2.
Each SoL has the principal direction of the traffic defined by increasing kilometres running from the start OP to the end OP.
That is why the start OP is always located at lowest kilometre of the line within the SoL.
No validation will be performed by RINF application regarding which is the start and which the end OP. This requires IM's verification.

Operational point at end of section of line ^OP

Parameter of

Section Of Line

General Information

Number:

1.1.0.0.0.4

XML Name:

SOLOPEnd

Deadline:

In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest

Belongs to parameters group

Section of line generic information ( 1.1.0.0.0 )

Data Format

Data Presentation

Operational Point

Flags

Applicability Flags:

Y

Validation

Validation Rules:

Op End

Op End Exists

Validation Messages:

opEnd (1.1.0.0.0.4): There must be at most one OP end for this section of line and it must be different from the OP start.

opEnd (1.1.0.0.0.4): There is an error with the SoL {$this} ({?solLabel}) and its OP end which does not exist.

OPE TSI References

Appendix D2 Index

3.1.2

Additional Information

General explanation:

Each SoL may have only one end OP, and each OP has unique OP ID within the MS. The “uniqueOPID” is defined in parameter 1.2.0.0.0.2.
Each SoL has the principal direction of the traffic defined by increasing kilometres running from the start OP to the end OP.
That is why the end OP is always located at highest kilometre of the line within the SoL.
No validation will be performed by RINF application regarding which is the start and which the end OP. This requires IM's verification.

Length of section of line ^DP

Parameter of

Section Of Line

General Information

Number:

1.1.0.0.0.5

XML Name:

SOLLength

Deadline:

In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest

Belongs to parameters group

Section of line generic information ( 1.1.0.0.0 )

Length

Data Format

Data Presentation

Double

Flags

Applicability Flags:

Y

Validation

Validation Rules:

Sol Length

Validation Messages:

lengthOfSectionOfLine (1.1.0.0.0.5): Each SoL has exactly one length. This error is due to that either there is no length for the specified SoL, more than one length has been defined, or the datatype cannot be converted into an xsd:double.

OPE TSI References

Part of RCC Algorithm:

true

Appendix D2 Index

3.2.3

Nature of Section of Line ^OP

Parameter of

Section Of Line

General Information

Number:

1.1.0.0.0.6

XML Name:

SOLNature

Deadline:

In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest

Belongs to parameters group

Section of line generic information ( 1.1.0.0.0 )

Data Format

Data Presentation

Concept

Taxonomy Reference:

Section of Line Natures

Values :

Code	Value
10	Regular SoL
20	Link

Flags

Applicability Flags:

Y

Validation

Validation Rules:

Sol Nature Skos

Sol Nature Applicability

Sol Nature

Validation Messages:

SoL nature (1.1.0.0.0.6): The SOL {$this} with label {?label} has a value {?concept} that is not one of the predefined values and cannot be converted into a SKOS concept on this list: http://data.europa.eu/949/concepts/sol-natures/SoLNatures.

SoL nature (1.1.0.0.0.6): The SoL {$this} ({?solLabel}), with opStart {?opStartID} and opEnd {?opEndID}, has a SOLnature of type Link, and at least one of its tracks has values for at least one of the groups of parameters 1.1.1.1, 1.1.1.2 or 1.1.1.3. This happens at least with the track {?track} ({?trackLabel}), with property {?p} (RINF index {?index}).

SoL nature (1.1.0.0.0.6): Either no SOL nature is specified for this SoL, or more than one SoL nature has been specified.

Route book specific parameters ^{DP OP}

General Information

Number:

1.1.0.0.1

Belongs to parameters group

RINF Technical characteristic

Related parameters

Industrial risks — locations where it is dangerous for the driver to step out ( 1.1.0.0.1.1 )

Operating language ( 1.1.0.0.1.2 | 1.2.0.0.0.8 )

Operational regime ( 1.1.0.0.1.3 )

Industrial risks — locations where it is dangerous for the driver to step out ^DP

Parameter of

Section Of Line

Subset with common characteristics

General Information

Number:

1.1.0.0.1.1

Deadline:

In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest

Belongs to parameters group

Route book specific parameters ( 1.1.0.0.1 )

Data Format

Data Presentation

Boolean

Format:

Y/N

Flags

Applicability Flags:

Y/N

OPE TSI References

Appendix D2 Index

3.2.5

Additional Information

General explanation:

Although it is just an indication of existence of an industrial risk, the area covering the industrial risk should be references on the topological network.
For the route book purpose, the industrial risks should be defined as linear references instead of area. SpecialArea of type "industrial risk" should be used

Operating language ^OP

Parameter of

Infrastructure element

General Information

Number:

1.1.0.0.1.2

1.2.0.0.0.8

Deadline:

12 months after publication of Article 7 Guide

Belongs to parameters group

Route book specific parameters ( 1.1.0.0.1 )

Data Format

Data Presentation

Concept

Format:

http://publications.europa.eu/resource/authority/language

Flags

Applicability Flags:

Y/NYA

OPE TSI References

Appendix D2 Index

3.5.1

Operational regime ^OP

Parameter of

Section Of Line

General Information

Number:

1.1.0.0.1.3

Deadline:

12 months after publication of Article 7 Guide

Belongs to parameters group

Route book specific parameters ( 1.1.0.0.1 )

Data Format

Data Presentation

Concept

Taxonomy Reference:

Operational regime types

Values :

Code	Value
10	Mono-directional single track line
20	Bi-directional single track line
30	Reversible multiple track line
40	Double or multiple track line

Flags

Applicability Flags:

Y/N/NYA

OPE TSI References

Appendix D2 Index

3.2.7

Running track generic information ^{DP OP}

General Information

Number:

1.1.1.0.0

Belongs to parameters group

RINF Technical characteristic

Related parameters

Organisation code ( 1.1.0.0.0.1 | 1.1.1.1.8.1 | 1.2.1.0.0.1 | 1.2.1.0.5.1 | 1.2.1.0.6.1 | 1.2.2.0.0.1 | 1.2.2.0.5.1 )

Identification of track ( 1.1.1.0.0.1 | 1.2.1.0.0.2 )

Normal running direction ( 1.1.1.0.0.2 )

Lineside distance indication ( 1.1.1.0.0.3 )

Connected to ( 1.1.1.0.1.2 | 1.2.4.1 )

Identification of track ^DP

Parameter of

Running track

General Information

Number:

1.1.1.0.0.1

1.2.1.0.0.2

XML Name:

SOLTrackIdentification

Deadline:

In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest

Belongs to parameters group

Running track generic information ( 1.1.1.0.0 )

Identifier

Data Format

Data Presentation

String

Flags

Applicability Flags:

Y

Validation

Validation Rules:

No Repeated Track Ids So L

Track Id

No Repeated Track Ids Op

Validation Messages:

trackId (1.1.1.0.0.1): Each track shall have unique identification or number within the SoL. This number cannot be used for naming any other track in the same SoL. There is a problem with SoL {$this} ({?solLabel}) and tracks {?track1} ({?track1Label}) and {?track2} ({?track2Label}), since they have the same identifier: {?value}.

trackId (1.1.1.3.3.3.3, 1.2.1.1.2.3.3): The identification of a track must be a string. This error may be due to having a track with no identification or with more than one value as identification, or having a value that is not a string.

trackId (1.2.1.0.0.2):: Each track shall have unique identification or number within the OP. This number cannot be used for naming any other track in the same OP. There is a problem with OP {$this} ({?opLabel}) and tracks {?track1} ({?track1Label}) and {?track2} ({?track2Label}), since they have the same identifier: {?value}.

OPE TSI References

Appendix D2 Index

2.2.1.1

Additional Information

General explanation:

Each track shall have unique identification or number within the SoL. This number cannot be used for naming any other track in the same SoL.
The check regarding the uniqueness of the ID within the SoL has to be done on national level (preferably by IM).

Normal running direction ^OP

Parameter of

Running track

General Information

Number:

1.1.1.0.0.2

XML Name:

SOLTrackDirection

Deadline:

In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest

Belongs to parameters group

Running track generic information ( 1.1.1.0.0 )

Data Format

Data Presentation

Concept

Taxonomy Reference:

Track Running Directions

Values :

Code	Value
10	N
20	O
30	B

Flags

Applicability Flags:

Y

Validation

Validation Rules:

So Ltrack Direction Max Count

So Ltrack Direction Min Count

Track Direction Skos

Validation Messages:

There should be at most one Track Direction. There is a problem with SoL {$this} ({?solLabel}) and its track {?track} ({?trackLabel}). This track has at least two different values for this property: {?value1} and {?value2}

There should be at least one Track Direction. There is a problem with SoL {$this} ({?solLabel}) and its track {?track} ({?trackLabel}). This track has no values for this property

Indication of the trackDirection (1.1.1.0.0.2):): The track {?track} in the Section of Line {$this} has a value {?concept} that is not one of the predefined values and cannot be converted into a SKOS concept on this list: http://data.europa.eu/949/concepts/track-running-directions/TrackRunningDirections.

OPE TSI References

Appendix D2 Index

2.2.1.1

Lineside distance indication ^OP

Parameter of

Running track

Subset with common characteristics

General Information

Number:

1.1.1.0.0.3

Belongs to parameters group

Running track generic information ( 1.1.1.0.0 )

Data Format

Data Presentation

Lineside indications of distance

Format:

[NNNN] frequency in meters
Appearance - selectable list
[L/R] - the side along the track where the lineside indication is positioned (left or right)

OPE TSI References

Appendix D2 Index

3.1.3

Additional Information

General explanation:

Frequency, appearance and positioning of a sign indicating distance as reference post. Two types of sign are normally available: kilometer post and hectometer post.
- A kilometer post is a lineside sign indicating the distance from a specific point, usually being the strarting point of the railway line.
- An hectometer post is a lineside sign indicating a relative distance.

Connected to ^OP

Parameter of

Track

General Information

Number:

1.1.1.0.1.2

1.2.4.1

Deadline:

12 months after publication of Article 7 Guide

Belongs to parameters group

Running track generic information ( 1.1.1.0.0 )

Data Format

Data Presentation

Track

Flags

Applicability Flags:

Y/N/NYA

Additional Information

General explanation:

This property defines a connection between two tracks. It is symmetric, meaning if a track A is connected to track B, then track B is also connected to track A. A track cannot be connected to itself (irreflexive property).
Used to indicate connectivity between track instances in a network, ensuring that connections are non-self-referential and in the normal running direction of the track.

This is a simplistic representation of the internal connectivity of the tracks in an operational point or the connectivity of the tracks between operational points and sections of line.
For a more detailed representation of connectivity and navigability, this information should be available on the topology of the network.

Example:

Track_A connectedTo Track_B implies Track_B connectedTo Track_A.

Infrastructure subsystem ^{DP OP}

General Information

Number:

1.1.1.1

Belongs to parameters group

RINF Technical characteristic

Related parameters

Declarations of verification for track ( 1.1.1.1.1 )

Performance parameter ( 1.1.1.1.2 | 1.2.1.0.2 | 1.2.2.0.2 )

Line layout ( 1.1.1.1.3 | 1.2.1.0.3 )

Track parameters ( 1.1.1.1.4 | 1.2.1.0.4 )

Switches and crossings ( 1.1.1.1.5 )

Track resistance to applied loads ( 1.1.1.1.6 )

Health, safety and environment ( 1.1.1.1.7 )

Tunnel ( 1.1.1.1.8 | 1.2.1.0.5 | 1.2.2.0.5 )

Declarations of verification for track ^DP

General Information

Number:

1.1.1.1.1

Belongs to parameters group

Infrastructure subsystem ( 1.1.1.1 )

Related parameters

EC declaration of verification for infrastructure element relating to compliance with the requirements from TSIs applicable to infrastructure subsystem ( 1.1.1.1.1.1 | 1.2.1.0.1.1 | 1.2.2.0.1.1 )

EI declaration of demonstration (as defined in Commission 2014/881/EU (2)) relating to compliance with the requirements from TSIs applicable to infrastructure subsystem ( 1.1.1.1.1.2 | 1.2.1.0.1.2 | 1.2.2.0.1.2 )

EC declaration of verification for infrastructure element relating to compliance with the requirements from TSIs applicable to infrastructure subsystem ^DP

Parameter of

Running track

Subset with common characteristics

General Information

Number:

1.1.1.1.1.1

1.2.1.0.1.1

1.2.2.0.1.1

XML Name:

IDE_ECVerification

Deadline:

In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest

Belongs to parameters group

Declarations of verification for track ( 1.1.1.1.1 )

Data Format

Data Presentation

String

Format:

CC/RRRRRRRRRRRRRR/YYYY/NNNNNN

Flags

Applicability Flags:

Y/N

Validation

Validation Rules:

Verification Infs

Verification Inf

Validation Messages:

verificationINF (1.2.2.0.1.1, 1.2.1.0.1.1, 1.2.2.0.1.1): Each Siding or subset with common characteristics may have one or more verificationINF. This error is due to the value not being a string or the value not following this pattern: country code/national registration number/year between 1900 and 2100/progressive counter.

verificationINF (1.1.1.1.1.1, 1.2.1.0.1.1): The verificationINF must be a string following the format 'XX/XXXXXXXXXXXXXX/YYYY/DDDDDD' where XX is the country code, XXXXXXXXXXXXXX is the unique number for EC declarations, YYYY is the year of the declaration (1900-2100) and DDDDDD is the sequential number of the declaration. This error is due to the value not following the pattern.

Additional Information

General explanation:

The parameter may be repeated only when several EC declarations were issued related to the INF subsystem.
With the extension of scope according to the IOD, geographical scope of the INF TSI now includes all the networks (TEN and off-TEN) with the following nominal track gauges: 1435, 1520, 1524, 1600 and 1668 mm

EI declaration of demonstration (as defined in Commission 2014/881/EU (2)) relating to compliance with the requirements from TSIs applicable to infrastructure subsystem ^DP

Parameter of

Running track

Subset with common characteristics

General Information

Number:

1.1.1.1.1.2

1.2.1.0.1.2

1.2.2.0.1.2

XML Name:

IDE_EIDemonstration

Deadline:

In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest

Belongs to parameters group

Declarations of verification for track ( 1.1.1.1.1 )

Data Format

Data Presentation

String

Format:

CC/RRRRRRRRRRRRRR/YYYY/NNNNNN

Flags

Applicability Flags:

Y/N

Validation

Validation Rules:

Demonstration Infs

Demonstration Inf

Validation Messages:

demonstrationINF (1.1.1.1.1.2, 1.2.1.0.1.2, 1.2.2.0.1.2): Each siding or subset with common characteristics may have one or more demonstrationINF. This error is due to the value not being a string or the value not following this pattern: country code/national registration number/year between 1900 and 2100/progressive counter.

demonstrationINF (1.1.1.1.1.2, 1.2.1.0.1.2): The demonstrationINF must be a string following the format 'XX/XXXXXXXXXXXXXX/YYYY/DDDDDD' where XX is the country code, XXXXXXXXXXXXXX is the unique number for EI declarations, YYYY is the year of the declaration (1900-2100) and DDDDDD is the sequential number of the declaration. This error is due to the value not following the pattern.

Additional Information

General explanation:

EI declaration of demonstration (as defined Commission 2014/881/EU) for track relating to compliance with the requirements from TSIs applicable to infrastructure subsystem.

It may happen that several EI declarations were issued - then parameter has to be repeated as many times as many declarations were issued.

The procedure for demonstration that existing network fits to requirements of the TSIs is executed on voluntary basis, so when EI declaration do not exist then the parameter is optional. If EI declaration was not issued, then field shall be left empty.

It may happen that several EI declarations were issued - then parameter has to be repeated as many times as many declarations were issued.

The procedure for demonstration that existing network fits to requirements of the TSIs is executed on voluntary basis, so when EI declaration do not exist then the parameter is optional. If EI declaration was not issued, then field shall be left empty.

Performance parameter ^{DP OP}

General Information

Number:

1.1.1.1.2

1.2.1.0.2

1.2.2.0.2

Belongs to parameters group

Infrastructure subsystem ( 1.1.1.1 )

Related parameters

TEN classification of track ( 1.1.1.1.2.1 | 1.2.1.0.2.1 | 1.2.1.0.6.3 | 1.2.2.0.0.3 )

TEN geographic information system identity (GIS ID) ( 1.1.1.1.2.1.2 )

Category of line ( 1.1.1.1.2.2 | 1.2.1.0.2.2 )

Part of a Railway Freight Corridor ( 1.1.1.1.2.3 | 1.2.1.0.2.3 )

Load capability ( 1.1.1.1.2.4 )

National classification for load capability ( 1.1.1.1.2.4.1 )

Compliance of structures with the High Speed Load Model (HSLM) ( 1.1.1.1.2.4.2 )

Railway location of structures requiring specific checks ( 1.1.1.1.2.4.3 )

Document with the procedure(s) for static and dynamic route compatibility checks ( 1.1.1.1.2.4.4 )

Maximum permitted speed ( 1.1.1.1.2.5 )

Temperature range ( 1.1.1.1.2.6 )

Maximum altitude ( 1.1.1.1.2.7 )

Existence of severe climatic conditions ( 1.1.1.1.2.8 )

TEN classification of track ^OP

Parameter of

Platform edge

Running track

Siding

Subset with common characteristics

General Information

Number:

1.1.1.1.2.1

1.2.1.0.2.1

1.2.1.0.6.3

1.2.2.0.0.3

XML Name:

IPP_TENClass

Deadline:

In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest

Belongs to parameters group

Performance parameter ( 1.1.1.1.2 | 1.2.1.0.2 | 1.2.2.0.2 )

Platform ( 1.2.1.0.6 )

Siding ( 1.2.2 )

Data Format

Data Presentation

Concept

Taxonomy Reference:

TEN Classifications

Values :

Code	Value
10	Part of the TEN-T Comprehensive Network
20	Part of the TEN-T Core Freight Network
30	Part of the TEN-T Core Passenger Network
40	Off TEN
50	Part of the TEN-T Extended Core Freight Network
60	Part of the TEN-T Extended Core Passenger Network

Flags

Applicability Flags:

Y/N

Validation

Validation Rules:

Ten Classification Skost

Ten Classification S

Ten Classification P

Ten Classification T

Ten Classification Skoss

Ten Classification Skosp

Validation Messages:

TEN classification (1.1.1.1.2.1, 1.2.1.0.2.1): The track or subset with common characteristics {$this} (label {?label}) has a value {?concept} that is not one of the predefined values and cannot be converted into a SKOS concept on this list: http://data.europa.eu/949/concepts/ten-classifications/TENClassifications.

TEN classification (1.1.1.1.2.1, 1.2.1.0.2.1, 1.2.1.0.6.3, 1.2.2.0.0.3): This error may be due to having a Platform with a TEN classification that is not an URI.

TEN classification (1.2.1.0.6.3): This error may be due to having a Platform with a TEN classification that is not an URI.

tenClassification (1.1.1.1.2.1, 1.2.1.0.2.1): The track or subset with common characteristics has a TEN classificaion value (Indication of the part of the trans-European network the line belongs to) that must be an IRI.

TEN classification (1.1.1.1.2.1, 1.2.1.0.2.1, 1.2.1.0.6.3, 1.2.2.0.0.3): The siding or subset with common characteristics {$this} with label {?sidingLabel} has a value {?concept} that is not one of the predefined values and cannot be converted into a SKOS concept on this list: http://data.europa.eu/949/concepts/ten-classifications/TENClassifications.

TEN classification (1.2.1.0.6.3): The platform {$this} with label {?label} has a value {?concept} that is not one of the predefined values and cannot be converted into a SKOS concept on this list: http://data.europa.eu/949/concepts/ten-classifications/TENClassifications.

Additional Information

General explanation:

Article 39 2. freight lines of the core network as indicated in Annex I: at least 22,5 t axle load, 100 km/h line speed and the possibility of running trains with a length of 740 m.

TEN geographic information system identity (GIS ID) ^DP

Parameter of

Running track

Subset with common characteristics

General Information

Number:

1.1.1.1.2.1.2

XML Name:

IPP_TENGISID

Deadline:

1 January 2021

Belongs to parameters group

Performance parameter ( 1.1.1.1.2 | 1.2.1.0.2 | 1.2.2.0.2 )

Data Format

Data Presentation

String

Flags

Applicability Flags:

Y/N

Validation

Validation Rules:

Ten Gisid Applicability

Ten Gisid

Validation Messages:

tenGISId (1.1.1.1.2.1.2): This error is due to the track or subset with common characteristics {?trackLabel} , violating the rule: Y if the answer to parameter 1.1.1.1.2.1 is not off TEN.

tenGISId (1.1.1.1.2.1.2): The track or subset with common characteristics must have at most one character string value (GIS Id) of the section of TEN-T database to which the track belongs. This error may be due to having a track with more than one TEN GIS identity or that the value is not a string.

Additional Information

General explanation:

This parameter will be deprecated in a next revision. Please use value "Not applicable" until the RINF regulation is aligned. The information below remains for reference only.

TENtec is the European Commission's information system to coordinate and support the Trans-European Transport Network Policy (TEN-T). For more details about the system and the legal background please follow the link to the TENtec Public Portal.

The list of sections of the TEN networks with their GIS IDs can be requested via MOVE-TENTEC-PUBLIC@ec.europa.eu

Category of line ^OP

Parameter of

Running track

Subset with common characteristics

General Information

Number:

1.1.1.1.2.2

1.2.1.0.2.2

XML Name:

IPP_LineCat

Deadline:

In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest

Belongs to parameters group

Performance parameter ( 1.1.1.1.2 | 1.2.1.0.2 | 1.2.2.0.2 )

Data Format

Data Presentation

Concept

Taxonomy Reference:

Line Categories

Values :

Code	Value
10	P1
20	P2
30	P3
40	P4
50	P5
60	P6
70	P1520
80	P1600
90	F1
100	F2
110	F3
120	F4
130	F1520
140	F1600

Flags

Applicability Flags:

Y/N

Validation

Validation Rules:

Line Category Skos

Line Category

Validation Messages:

lineCategory (1.1.1.1.2.2, 1.2.1.0.2.2): The track or subset with common characteristics {$this} (label {?label}) has a value {?concept} that is not one of the predefined values and cannot be converted into a SKOS concept on this list: http://data.europa.eu/949/concepts/line-category/LineCategories.

lineCategory (1.1.1.1.2.2, 1.2.1.0.2.2): The track or subset with common characteristics must have a classification of a line value that is an IRI.

Additional Information

General explanation:

INF TSI (4.2.1) classifies lines based on the type of traffic (traffic code).

TSI categories of line shall be used for the classification of existing lines to define a target system so that the relevant performance parameters will be met.

The TSI category of line is a combination of traffic codes. For lines where only one type of traffic is carried (for example a freight only line), a single code can be used to describe the requirements; where mixed traffic runs the category will be described by one or more codes for passenger and freight in case of two types of traffic. Then the parameter is repeated if relevant. The combined traffic codes describe the envelope within which the desired mix of traffic can be accommodated.

Technical scope of the INF TSI includes all the networks (TEN and off-TEN) for nominal track gauges 1435, 1520, 1524, 1600 and 1668 mm.
It is not applicable when track is not included in technical scope of the TSI.
When more than one value of the parameter has to be published, then parameter has to be repeated as many times as many values of the parameter will be published.

Example:

If a line is operated by passenger trains with speed of 250 km/h, local commuter trains with speed of 120 km/h and heavy freight trains in the night, then the best combination of traffic codes seems to be P2, P5 and F1.
Then, the TSI category of line for this case would simply be P2-P5-F1.

Part of a Railway Freight Corridor ^OP

Parameter of

Running track

Subset with common characteristics

General Information

Number:

1.1.1.1.2.3

1.2.1.0.2.3

XML Name:

IPP_FreightCorridor

Deadline:

In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest

Belongs to parameters group

Performance parameter ( 1.1.1.1.2 | 1.2.1.0.2 | 1.2.2.0.2 )

Data Format

Data Presentation

Concept

Taxonomy Reference:

Freight Corridors

Values :

Code	Value
10	Rhine-Alpine RFC
20	North Sea-Mediterranean RFC
30	Scandinavian – Mediterranean RFC
40	Atlantic RFC
50	Baltic-Adriatic RFC
60	Mediterranean RFC
70	Orient-EastMed RFC
80	North Sea-Baltic RFC
90	Rhine – Danube RFC
100	Alpine-Western Balkan RFC
110	Amber RFC

Flags

Applicability Flags:

Y/N

Validation

Validation Rules:

Freight Corridor Shape

Freight Corridor Skos

Validation Messages:

freightCorridor (1.1.1.1.2.3, 1.2.1.0.2.3): Each track or subset with common characteristics may have an indication whether the line is designated to a Railway Freight Corridor that is an IRI. This error is due to having a value that is not an IRI.

Indication whether the line is designated to a Railway Freight Corridor (1.1.1.1.2.3, 1.2.1.0.2.3): The National Line {$this} has a value {?concept} that is not one of the predefined values and cannot be converted into a SKOS concept on this list: http://data.europa.eu/949/concepts/freight-corridor/FreightCorridors.

Additional Information

General explanation:

Not applicable if the line is not part of an RFC. If a line belongs to several corridors, repeat the parameter.

Load capability ^OP

Parameter of

Running track

Subset with common characteristics

General Information

Number:

1.1.1.1.2.4

XML Name:

IPP_LoadCap

Deadline:

In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest

Belongs to parameters group

Performance parameter ( 1.1.1.1.2 | 1.2.1.0.2 | 1.2.2.0.2 )

Data Format

Data Presentation

Load capability

Format:

The value of this parameter is an instance of the era:LoadCapability class which consists of 2 properties:
- era:loadCapabilityLineCategory - as a taxonomy of load models representing line category
- era:loadCapabilitySpeed - integer for the value of speed [km/h] permitted for a specific load model

For RINF XML data sets:
As long as the data provision through XML data sets is allowed, the data format is:
[CCCC] [NNN],
where:
- [CCCC] is a single selection from the predefined list of load models representing line category
- [NNN] is the value of speed [km/h] permitted for a specific load model.

Flags

Applicability Flags:

Y

Validation

Validation Rules:

Track Load Capability

Validation Messages:

trackLoadCapability (1.1.1.1.2.4): The track or subset with common characteristics defines a load capability value that must be an instance of LoadCapability.

OPE TSI References

Part of RCC Algorithm:

true

Additional Information

General explanation:

At this step, RINF does not allow to enter additional data referred to additional speed regulations and operating requirements relating to locomotives (e.g., locomotive classes and associated maximum speed) or traffic types (e.g., maximum speed of freight traffic or passenger traffic).

The load capability describes the weakest point of this track within this section of line (which is normally a bridge or other sub-track structure).
It is expressed as a combination of the line category and speed permitted for trains exerting loads defined for this line category.
The result of the classification process is set out in EN 15528:2021 (Annex A) and referred to in that standard as Line Category.

The Load capability for UK in respect of Northern Ireland consists of RA and speed in miles per hour. RA shall be applied according to UK Railway Group Standard GE/RT8006, Issue Two, September 2010.

More than one combination may be published for the same track if applicable, but it has to be done by repetition of the parameter with one value selected only that is why Y is given in line Can be repeated.
For the following cases, it is not possible to use EN 15528:2021 categories of line classification:
- TSI categories of line P1520 and F1520 (passenger traffic or freight traffic at any speed)
- TSI categories of line P1600 and F1600 (passenger traffic or freight traffic at any speed)

When more than one value of the parameter has to be published, then parameter has to be repeated as many times as many values of the parameter will be published.

Example:

The set of selected data may include: B2-160, D4-120 and E5-100
When classifying infrastructure lines into line categories, the following options shall be used by the infrastructure manager to optimize freight traffic:
Option 1: determination of the line category at maximum freight traffic speed (maximum 120 Km/h)
Option 2: determination of a line category at an associated lower speed (less than the maximum freight traffic speed)
Example of option 1 (Annex F of EN 15528:2021): In a given track, if the traffic is mixed, the local speed of the line is 90 Km/h and the determined line category is D4 at a maximum of 90 Km/h, the information displayed should be: D4/90.
Example of option 2 (Annex F of EN 15528:2021): In a given track, if the traffic is mixed, the local speed of the line is 120 Km/h and the determined line category is C4 at a maximum of 120 Km/h and D4 at maximum of 90 Km/h, the information displayed should be: C4/120 and D4/90.

National classification for load capability ^DP

Parameter of

Running track

Subset with common characteristics

General Information

Number:

1.1.1.1.2.4.1

XML Name:

IPP_NCLoadCap

Deadline:

16 January 2020

Belongs to parameters group

Performance parameter ( 1.1.1.1.2 | 1.2.1.0.2 | 1.2.2.0.2 )

Data Format

Data Presentation

String

Flags

Applicability Flags:

Y/N

Validation

Validation Rules:

National Load Capability

Validation Messages:

nationalLoadCapability (1.1.1.1.2.4.1): The track or subset with common characteristics has a national load capability value that must be a string. This error may be due to the track having a value of national load capability that is not a character string.

OPE TSI References

Part of RCC Algorithm:

true

Additional Information

General explanation:

Some Networks are using National classification for load capability (instead of parameter 1.1.1.1.2.4 Load capability that provide load capability in accordance with EN 15528)

Example:

The French IM SNCF reseau is using the concept of 'groupe Demeaux' with the following definition is 'Groupe de classification de la voie tenant compte de la resistance de son armement en flexion verticale'.

Compliance of structures with the High Speed Load Model (HSLM) ^DP

Parameter of

Running track

Subset with common characteristics

General Information

Number:

1.1.1.1.2.4.2

XML Name:

IPP_HSLMCompliant

Deadline:

16 January 2020

Belongs to parameters group

Performance parameter ( 1.1.1.1.2 | 1.2.1.0.2 | 1.2.2.0.2 )

Data Format

Data Presentation

Boolean

Flags

Applicability Flags:

Y/N

Validation

Validation Rules:

High Speed Load Model Compliance

Validation Messages:

highSpeedLoadModelCompliance (1.1.1.1.2.4.2): The track or subset with common characteristics must have at most one high speed load model compliance value that must be Y/N (boolean). This error may be due to the track having more than one value or having a value of high speed load model compliance that is not Y/N.

OPE TSI References

Part of RCC Algorithm:

true

Additional Information

General explanation:

(TSI INF 4.2.7.1.2(2)) Applicable if the maximum permitted speed of the running track is more than 200km/h and the structures within the section of line are all compatible with the High Speed Load Model (HSLM); information regarding the procedure to be used to perform the dynamic compatibility check shall be provided as well.

Railway location of structures requiring specific checks ^DP

Parameter of

Running track

Subset with common characteristics

General Information

Number:

1.1.1.1.2.4.3

XML Name:

IPP_StructureCheckLoc

Deadline:

16 January 2020

Belongs to parameters group

Performance parameter ( 1.1.1.1.2 | 1.2.1.0.2 | 1.2.2.0.2 )

Data Format

Data Presentation

Double

Flags

Applicability Flags:

Y/N

Validation

Validation Rules:

Structure Check Location

Validation Messages:

structureCheckLocation (1.1.1.1.2.4.3): The track or subset with common characteristics has a location of the structure check value that must be a double (real) number and follow the format [±NNNN.NNN]. This error may be due to the track having a value that does not follow the pattern or is not a double (real) number.

OPE TSI References

Part of RCC Algorithm:

true

Additional Information

General explanation:

The railway location identifies the location of the structure in the system of reference of the line to which the track belongs.

Example:

The IM A knows that its bridge X might have problems with combination of speed and load above a certain limit values Z, and for that the IM A has a specific procedure W for the check to be done; if the vehicle operation is intended to be within this case (above the limit Z), then RU shall proceed in accordance to the procedure W; therefore the bridge X shall be referred to in the parameter of the RINF: 1.1.1.1.2.4.3 / Railway location of structures requiring specific checks.

Document with the procedure(s) for static and dynamic route compatibility checks ^OP

Parameter of

Running track

Subset with common characteristics

General Information

Number:

1.1.1.1.2.4.4

XML Name:

IPP_StructureCheckDocRef

Deadline:

16 January 2020

Belongs to parameters group

Performance parameter ( 1.1.1.1.2 | 1.2.1.0.2 | 1.2.2.0.2 )

Data Format

Data Presentation

ERA Document

Flags

Applicability Flags:

Y/N

Validation

Validation Rules:

Compatibility Procedure Document

Validation Messages:

compatibilityProcedureDocument (1.1.1.1.2.4.4): The track or subset with common characteristics has a name of the compatibility procedure document that must be a Document.

OPE TSI References

Part of RCC Algorithm:

true

Additional Information

General explanation:

The value of this parameter should be either a reference to a file name or an external link to a document.
If a file name is provided, the Infrastructure Manager (IM) must upload a document with the same file name using the "Reference Documents Management" functionality in the RINF application. The document must be in electronic format and available in two official EU languages. In this case, the parameter value must be repeated for each document.
If an external link is provided, the IM must ensure that the document is available at the provided link.

Maximum permitted speed ^DP

Parameter of

Running track

Subset with common characteristics

General Information

Number:

1.1.1.1.2.5

XML Name:

IPP_MaxSpeed

Deadline:

In accordance with Implementing Decision 2014/880/EU and by 16 March 2019 at the latest

Belongs to parameters group

Performance parameter ( 1.1.1.1.2 | 1.2.1.0.2 | 1.2.2.0.2 )