Home › FAQ

Frequently Asked Questions

What is the URI template structure?

There is no single template. The wrapper serves every ERA IRI http://data.europa.eu/949/{path} at {path} (the document) and {path}#it (the object), so its URIs are exactly as varied as ERA's. And ERA's are minted by whoever delivered the data: each infrastructure manager either has its RINF data converted by ERA, or converts it itself, in its own style. Measured on 2026-10-27 over every operational point, primary location, section of line, track, siding, platform edge, tunnel, bridge, level crossing, switch, signal, border point and kilometre post, there are nine schemes. Within a scheme, every class follows the same pattern.

{class}/{hash} — ERA's own conversion
Most infrastructure managers: DB (Germany), SNCF Réseau (France), SBB and BLS (Switzerland), RFI (Italy), Adif (Spain), Správa železnic (Czechia), MÁV (Hungary), Infrabel (Belgium), Trafikverket (Sweden) and others. A lower-case class name and a ten-digit hex hash: operationalPoint/{hash}, sectionOfLine/{hash}, track/{hash}, siding/{hash}, platformEdge/{hash}, tunnel/{hash}, kilometricPost/{hash}; 56,702 of 65,798 operational points. Each hash is one version of the object, valid for a period (era:validity). For example operationalPoint/f77033cc06#it, Arlanda nedre. Primary locations are not versioned and carry the RINF code instead: primaryLocation/DE17845#it (Nürnberg Hbf), primaryLocation/{country}{code}.
functionalInfrastructure/{classes}/AT/{IM code}/{local id} — Austria
ÖBB (0081) and the other Austrian infrastructure managers (3023, 3035, 3764, 3782, 3787, 3865, 3882), each under its own company code. The local id is the RINF code where there is one, else ÖBB's own number: functionalInfrastructure/operationalPoints/AT/0081/AT01003#it (Wien Hauptbahnhof), functionalInfrastructure/runningtracks/AT/0081/10946#it, functionalInfrastructure/switches/AT/0081/{number}. Border points use referenceBorderPoints/AT/{IM code}/{EU code}.
functionalInfrastructure/{classes}/{sha1} — Lithuania
LTG Infra (1224): a 40-digit hex hash, no country or company code: functionalInfrastructure/operationalPoints/9466f4150c9cfedc3f1f1718ee17470e616dc70f#it (Vilnius). Its border points are functionalInfrastructure/operationalPoints/LTU/{EU code}.
{Classes}/{uuid} — Portugal
Infraestruturas de Portugal (0094): the class capitalised and plural, then a UUID: OperationalPoints/19828f9d-d5a9-46ef-856a-cd811c01fcb4#it (Lisboa Oriente), SectionsOfLine/{uuid}, RunningTracks/{uuid}, PlatformEdges/{uuid}, Tunnels/{uuid}.
{Class}_{code} — Croatia
HŽ Infrastruktura (0078): the class capitalised, an underscore, and the RINF code, with no slash at all: OperationalPoint_HR75560#it (Rijeka), SectionOfLine_{line}__{code}, PlatformEdge_{code}_{n}__kolosijek_{n}.
{Class}/{nn}-{XX}-{line km}-{name} — Greece
OSE (0073): the class capitalised, then a numeric prefix and a two-letter code per class (89-OP operational point, 91-SOL section of line, 72-BR bridge, 87-TN tunnel, 75-LC level crossing, 80-SW switch, 90-SIG signal, 57-PL primary location), the line kilometre, and a name: OperationalPoint/89-OP-22.07.00-THESSALONIKI_PASS_RS#it. The dots belong to the id; they are not format suffixes.
{class}/{PREFIX}_{code} — Poland
PKP PLK (0051): ERA's lower-case class name, then a readable id with a prefix per class (OP_, SOL_, TR_, PE_, SG_): operationalPoint/OP_EU00048#it, sectionOfLine/SOL_PL0051106_PL08272_PL11748#it.
{class}/{code}_{from}_{until} — the Netherlands
ProRail (0084): the validity period is part of the IRI, so each version has a readable name: operationalPoint/EU00001_2026-05-08_2099-12-31#it, sectionOfLine/Ah-Vl_NLBmr_NLVlb_2026-05-29_2099-12-31#it.
https://data.banenor.no/data/_{kind}_{id} — Norway
Bane NOR (0076) mints outside ERA's namespace altogether (_primaryLocation_NO00002_2000-01-01, _switch_{uuid}, _undercrossing_{uuid} for bridges), so this wrapper does not serve them; see below.

Border points shared by two countries are ERA's own: referenceBorderPoint/EU00068#it. One resource can sit in two publishers' graphs: SBB (0085) and BLS (3915) deliver the same Swiss operational points, under the same IRIs.

Does the index page show examples of all classes in ERA?

No. Of the 104 classes in the ERA ontology, 49 have instances; the index page shows the 11 with geometries, so that every example shows on the map. The others are reached by following links, e.g. from a running track to its ETCS: functionalInfrastructure/runningtracks/AT/0081/10946#it.

How do I find a station by its RINF code?

Only where the code is in the IRI. For the infrastructure managers ERA converts, the primary location carries it: primaryLocation/{country}{code}, as primaryLocation/DE17845#it; its document lists the operational points that name it as theirs. Austria, Croatia, Poland and the Netherlands put the code in their own IRIs (above). Elsewhere (Portugal, Lithuania, versions with a hash) the code is only inside the data (era:uopid, era:primaryLocationCode); find the object by position with a box search.

Why are there several operational points for one station?

RINF is versioned. With ERA's conversion every version of an operational point or section of line is a resource of its own, with its period in era:validity and in its label („Nürnberg Hbf (from 2026-01-01 until 2026-12-31)“). The versions share an era:canonicalURI (operationalPoint/DE000NN), but ERA describes none of those, so the wrapper keeps them as ERA IRIs rather than links that would 404.

Why are some ids hashes?

They are minted by whoever converted the data, ERA itself for most managers. The hash says nothing about the object: nothing in it can be read off or recomputed here. The RINF code is in the data, and the label usually names the place.

Why does an RDF browser get “Not Acceptable” for the ERA ontology?

That answer comes from ERA, not from this wrapper. The terms of the ERA ontology (era:PrimaryLocation, era:inCountry, and the namespace http://data.europa.eu/949/ itself) redirect to a GraphDB page, https://graph.data.era.europa.eu/resource?uri=…, that serves only HTML. Measured 2026-10-27: text/html gets 200; text/turtle gets 500; application/rdf+xml and application/ld+json get 400; and an RDF browser's mixed Accept (Turtle, RDF/XML and JSON-LD first, HTML last) gets 406. So ERA's terms do not resolve for RDF clients, as its instance IRIs do not. The wrapper serves the instances and leaves the terms as ERA's IRIs: their definitions are in ERA's ontology repository, by SPARQL, and on ERA's own HTML pages.

What countries does the wrapper cover?

Every country in ERA's knowledge graph, as documents. On the map and in a box search, only features ERA gives a geometry appear, and most RINF data has none: about 11,800 of 52,700 operational points have a position. Geometries come from Germany, Austria, Portugal, Croatia, Lithuania, Greece and Luxembourg, plus the border points; France, Italy, Spain and others report the topology without coordinates. Norway reports a great deal with geometry, but Bane NOR mints its IRIs in its own namespace (https://data.banenor.no/…), which this wrapper does not serve; such features appear in box searches with their Bane NOR IRIs (see below). Regions: ERA's graph contains the NUTS classification, but RINF links to it only from 212 Greek primary locations (era:inNUTS3); everything else carries era:inCountry only.

Why is Norway missing?

Bane NOR is one of the richest sources of geometries (bridges, signals, kilometre posts), but it mints its IRIs under https://data.banenor.no/, outside ERA's namespace, and this wrapper serves ERA's. Norwegian features still appear in box searches and on the map, with their Bane NOR IRIs.


RINF data from the European Union Agency for Railways, licensed EUPL 1.2.