Superseded descriptions are dropped, and the comparison is made place by place — never line by
line. Some managers republish the same stretch every year under a new validity window: German line
4000 returns 16,615 rows unfiltered and 8,281 once each stretch keeps only its own latest window.
Others date a section by the day it opened: French line 830000-1 spreads 25 different beginnings
across its 570 sections, so a line-wide "newest date" would keep two sections and delete the rest. The newest
window is therefore picked per stretch of line, and at operational points per era:uopid and then
per track within the point — France repeats tracks inside a point, Germany repeats the whole station
as separate resources sharing one uopid, and both rules run.
Managers model their networks differently, and all 27 are supported. A query written against
one publication style returns nothing at all for the others, silently. Four variations are handled: a line is
identified by era:lineId where it is published and by the English rdfs:label of its
era:LinearPositioningSystem where it is not (9,543 of 9,642 carry era:lineId; the 99
that do not are Croatia's 55 and Norway's 32); operational points are reached by kilometric post
or by the era:opStart/era:opEnd of a section, which also takes French
line 830000-1 from 327 points to 603; kilometre position is optional, since Croatia's net point
references carry a geometry and no era:hasLrsCoordinate at all, so its rows show
— and sort last; and the part-whole link between a place and its tracks is published as
era:isPartOf by every dataset except Croatia's, which publishes only era:hasPart.
Places are resolved first, then their parameters. Asking for places, parameters and two
validity rules in one query put the operational-point side over the endpoint's 120 s limit for every
country tried. Resolving the places once and pinning them into the parameter query with VALUES
takes German line 4000 from 33 s to 3.6 s and French line 830000-1 from
21 s to 6.6 s, for identical results. The part-whole direction is probed once per run rather than
queried both ways, because asking for both costs the German line 1.4 s → 57 s: the optimiser can no
longer push the parameter join.
Countries that publish no dates are untouched. Ten of the countries offered here — Sweden,
Spain, Ireland, Estonia, Greece, Finland, Romania, Croatia, Austria and Luxembourg — carry no dated validity
at all, and Liechtenstein publishes no sections of line to date. Filtering on the newest date would delete
every one of their rows, so a resource with no validity is always kept.
Retired parameters are excluded. 4 of the 87 properties flagged
era:usedInRCCCalculations are owl:deprecated and are left out, as in the other tools
here — three of them are replaced by a live property under the same RINF number, so only
1.1.1.2.2.1.2.1 disappears entirely. Values that are concepts are resolved to their English label
where one exists, and a track carrying several values for one parameter has them joined with
“ | ”.
The line search spans every country you tick, and lines are fetched once per country and cached
— ticking and unticking the same country again costs no further query. Because a line identifier is unique
only within a Member State, the picker keeps each line's country attached rather than matching on the bare
identifier, so two countries publishing the same number (say, line 1) can never be picked by
mistake. The RCC parameter filter works the same way as the line picker: search, pick as many as you need, and
the underlying query adds FILTER(?rinfIndex IN (…)) for exactly those — leave it empty and every
RCC parameter is returned, as before.
The network map draws this run's sections geographically , over a plain Esri basemap;
the “Railway overlay” checkbox adds the OpenRailwayMap
“standard” layer for real track, station and line-number context, off by default so its own
colours never compete with the parameter colours you're there to read — the same approach as
the RINF Parameter Values network map. It draws only the “along the
line” side: sections now publish their own geometry almost everywhere too, and every operational point
does as well, but each section is still the straight chord between the two operational points it runs
between regardless — topology, not alignment, exactly
as for the table above. It reuses the parameter values already fetched for the table rather than re-querying
them, so drawing the map only costs one further request for geometry. One RCC parameter colours by its
distinct values; several colour by parameter instead, one flat colour each, since mixing unrelated value
domains into one legend would not mean anything — hover a section to see every value regardless of which
colour is on top. With none picked, or none applicable to this line, the map still draws the topology in one
colour. “Open in new window” pops the same drawing out into its own browser window — no further
query either, just the current segments redrawn there — so it can be dragged to a second monitor or given
more room than the panel embedded here, the same as the RINF Parameter Values
map. Unlike the rest of this tool, the map is not offline and not third-party-free: it fetches tiles from
arcgisonline.com and, if you turn the Railway overlay on, openrailwaymap.org as you pan and zoom.
← Back to the ERA Graph Explorer · RDF Exporter ·
RINF Parameter Values · Route Book ·
Ask the Graph · Eurostat Exporter