How “country” is defined here. RINF is published as national datasets, one named graph per
infrastructure manager. A country’s scope is the union of its IMs’ graphs — .
This is used rather than the per-resource era:inCountry property because many parameters sit on
sub-objects that carry no country of their own: querying era:maximumPermittedSpeed for Austria by
era:inCountry returns zero values, while the dataset scope returns the real 43.
An empty result is a fact, not a failure — and the tool now says which. Coverage is very
uneven: Estonia publishes 56 of the 294 live RINF parameters, against Ireland's 82,
Germany's 113, Spain's 126 and France's 145. So for most parameters a single sparse country returns nothing,
which used to look identical to a broken query. Every run now reports one chip per selected parameter saying
either how many values it found or no data and where, empty parameters appear as explicit rows in the
table rather than being omitted, and a failed request is labelled query error so the two can never be
confused. The By location export writes no data into the cell for the same reason.
Both full-data sheets are the same rows seen two ways — long, one row per value, and wide,
one row per location with the parameters pivoted into columns — so they share their location block, their
value/label naming and their rule for dropping a column nobody filled in. A parameter that hangs off an
operational point leaves Start OP and End OP empty on every row, and one that hangs off a
section of line leaves Operational point empty; that column is dropped rather than shipped blank.
Each parameter's value column is named after the parameter itself, with a — label column beside it
wherever the ontology labels those values — which matters more than it sounds: nominal track gauge
80 is the concept's identifier, and 760 is the gauge in millimetres.
The network map is topology, not alignment. Sections of line publish no geometry of their
own in any dataset except Croatia's — 581 of 583 there, zero in Germany, France, the Netherlands and Estonia —
but every operational point does , through
era:netReference/geo:hasGeometry: 101 of 101 in Estonia, 17,797 of 17,797 in Germany. A section is
therefore drawn as the straight chord between the two points it runs between, which is exact for what connects
to what and wrong for the shape of the route. It is drawn on
Leaflet , over standard OpenStreetMap tiles
with the OpenRailwayMap
standard layer overlaid for real track, station and line-number context — the “Railway overlay”
checkbox turns that layer off. Unlike the rest of the tool, this panel is not offline and not third-party-free:
it fetches map tiles from openstreetmap.org and openrailwaymap.org as you pan and zoom.
Known limits. One dataset is not single-country: Austria’s 0081 is 99.76 % Austrian
(13 of 5 402 country-tagged resources are Liechtenstein, Swiss or German border objects). Liechtenstein and the
United Kingdom appear in the data but publish no dataset of their own, so they have no country entry. The shared
borders graph (248 border-point geometries) is counted only under “All countries”.
“Resources” counts distinct subjects carrying the value inside the selected scope.
The full-data sheet. One row per location where the value applies. A running track hangs off
a section of line, giving its start and end operational point; a station track hangs off an operational point,
which is named instead. Where a value sits on a shared sub-object — a contact line system, ETCS or train
detection system, reused across many tracks — the row reports the track that points at it, since the
sub-object carries no location of its own. 216 of the 227 populated parameters have such a path; the rest
have the option greyed out. The row budget is split evenly across the countries you pick, so a large
selection never drops one of them entirely.
Parameter list snapshot — .
Value counts shown next to each parameter are RINF-wide and were measured at that snapshot; every extraction
you run is live against the endpoint.
← Back to the ERA Graph Explorer (bubble-graph “follow your nose” demo)
· RDF Exporter (export any resource URI as RDF/XML)
· RCC Parameters (route-compatibility parameters along one national line, by kilometre)
· Route Book (TSI OPE Appendix D2 elements for one national line).