Key Takeaways:
- INSPIRE (Directive 2007/2/EC) is the EU law that requires public authorities to make spatial data findable, viewable and, for many themes, downloadable in an interoperable format
- Germany transposed it through a federal law (the Geodatenzugangsgesetz) plus sixteen separate state implementing laws, because spatial data falls under state responsibility in Germany's federal system
- INSPIRE organises data into 34 themes across three Annexes, and Annex I themes (like cadastral parcels) had far earlier compliance deadlines than Annex III themes (like land use plans or natural risk zones)
- That phased, theme-by-theme rollout is a big part of why some German layers are nearly complete nationwide while others are still published by only a handful of states
- INSPIRE guarantees a service exists somewhere; it does not guarantee that service stays online, stays current, or publishes data in a schema two states describe the same way
If you have ever wondered why one German geodata layer covers all sixteen federal states cleanly while a seemingly similar one only covers half of them, the answer usually isn't bureaucratic inconsistency. It traces back to a single piece of EU law from 2007, how Germany's federal structure implemented it, and which data themes that law prioritised first. This post explains what the INSPIRE Directive actually requires, how it became sixteen separate implementations instead of one, and why "the source publishes it" and "the source publishes it reliably, in a usable format" turned out to be two very different promises.
What is the INSPIRE Directive?
INSPIRE, short for Infrastructure for Spatial Information in the European Union, is Directive 2007/2/EC: an EU law requiring public authorities in every member state to make the spatial data they hold discoverable, viewable and, for most themes, downloadable through standardised online services. It was written to support environmental policy, but its scope reaches far beyond environmental data alone. It covers everything from administrative boundaries and addresses to cadastral parcels, land use, buildings, hydrography and natural hazard zones, on the reasoning that environmental decisions depend on all of that context too.
INSPIRE does not create a single EU database. It requires each member state to expose its own data through a shared technical framework, so a discovery service, a view service (typically WMS) and, for most themes, a download service (typically WFS or an equivalent) all become part of the deal, along with metadata that lets someone outside the publishing authority actually find the dataset in the first place.
What does INSPIRE actually require, in practice?
INSPIRE groups spatial data into 34 themes spread across three Annexes, and the Annex a theme sits in matters more than most people realise. Annex I covers nine foundational themes, among them Cadastral Parcels, Administrative Units and Addresses, and these carried the earliest compliance deadlines. Annex II covers a handful of themes like Elevation and Land Cover. Annex III is the largest group, roughly twenty themes including Buildings, Land Use, Natural Risk Zones and Statistical Units, and it received the latest compliance deadlines of the three.
That staggered timeline was a practical concession, not an oversight: harmonising something as foundational as a cadastral parcel is a smaller technical lift than harmonising land use designations, which vary enormously in local legend and legal meaning from one municipality to the next. But it means two datasets that look equally "official" to an outside user can be years apart in how mature their INSPIRE-driven publication actually is.
How did Germany turn one directive into sixteen implementations?
Germany transposed INSPIRE nationally through the Geodatenzugangsgesetz (GeoZG), a federal law on access to spatial data. But surveying, cadastre and most spatial planning functions in Germany sit constitutionally with the states, not the federal government, so GeoZG alone couldn't do the whole job. Each of the sixteen federal states passed its own Landesgeodatenzugangsgesetz to carry the same obligations into state law, and each state's own surveying and mapping authority (Vermessungsverwaltung) became responsible for actually standing up the services INSPIRE requires. Coordination across all of that runs through GDI-DE (Geodateninfrastruktur Deutschland), the national body that aligns federal and state geoportals, but GDI-DE coordinates; it does not centrally publish.
The result is structurally exactly what you would expect from a federal law implemented by sixteen separately resourced state authorities on their own procurement cycles: the same legal obligation, sixteen technical realisations, sixteen update cadences, and sixteen geoportals with their own quirks.
Why does coverage still vary so much by theme and by state?
Two mechanisms compound each other here. First, the Annex timeline: Cadastral Parcels, an Annex I theme, has had over a decade longer to mature than Land Use or Natural Risk Zones, both Annex III themes. That alone explains a pattern you'll see across German open data generally: parcel-level cadastral data (ALKIS) is close to nationwide, while zoning designations (Flächennutzungsplan, Bebauungsplan) and hazard layers are published by a subset of states, with the rest still catching up.
Second, INSPIRE's minimum bar is lower than most downstream use cases need. A discovery service plus a view service satisfies real obligations under the directive, but a WMS view service only lets someone look at a map in a browser. It does not hand over queryable, joinable data. Plenty of German authorities are fully INSPIRE-compliant on paper while still making the underlying data hard to get as anything other than a rendered image or a PDF, which is exactly the gap between "published" and "usable" that a screening workflow runs into.
What does this mean for anyone actually trying to use German geodata?
It means treating "covered by INSPIRE" and "usable in a query" as two separate questions, because they are. INSPIRE is the reason a WFS or WMS endpoint for a given German dataset almost certainly exists somewhere. It is not a guarantee that endpoint is complete, current, or structured the same way as the equivalent endpoint one state over, and it says nothing about what happens when that endpoint changes address, drops a field, or goes quiet for a quarter.
That is the layer Mapular sits on top of: not replacing the sources INSPIRE obligated into existence, but watching them, re-pulling them when they change, and mapping sixteen states' worth of locally-legended, differently-paced publications onto one documented schema. Where a state genuinely hasn't published yet, the geospatial data catalog states that as a gap rather than papering over it, because "not yet compliant" and "compliant but stale" both look identical from the outside unless someone is checking.
Where to go from here
If you want to see what sixteen states' worth of INSPIRE-driven publication looks like once it's harmonised into one model, the geospatial data catalog lists every layer with its exact per-state coverage stated openly. It's the practical answer to the question this post has been building toward: not whether a dataset exists somewhere in Germany, but whether you can actually query it today.
