Key Takeaways:
- A Flurstück (cadastral parcel) is the smallest unit of land registration in Germany, and the unit a deal, a permit or a lease actually attaches to
- ALKIS (Amtliches Liegenschaftskatasterinformationssystem), Germany's official real-estate cadastre, is maintained by the state surveying authorities (Vermessungsverwaltungen) and standardised nationwide by the AdV, the working committee of German surveying administrations
- ALKIS records geometry, identifiers and area; ownership sits in the Grundbuch (land register), a separate system that parcels underpin but that ALKIS itself does not contain
- Parcel geometry is what makes zoning, hazard and portfolio data joinable at all: a region cannot be transacted, but a parcel can be shortlisted, checked and referenced in correspondence with an authority
- Publication is state by state, which is why most teams still resolve parcels one lookup at a time instead of screening with them as data; Bavaria does not publish its ALKIS parcel data at source at all, so it sits outside a harmonised 15-of-16-state layer
Shortlists are made of parcels, not polygons of interest. A drawn radius or a hand-picked area is a starting point for a search, but the moment a search narrows to specific sites, every question that matters (can you build here, is this in a flood zone, does this touch a competitor's catchment, who do you approach) resolves to a Flurstück, the legal land unit Germany's cadastre is built on. This post explains what a Flurstück is, why ALKIS parcel data is deceptively hard to assemble at scale, and how the ALKIS Flurstücke layer turns that unit into something you can query instead of chase.
What is a Flurstück, and why does it matter more than a region?
A Flurstück is the smallest cadastral land unit in Germany: a contiguous area recorded in the official cadastre with its own stable identifier, built from three parts: Gemarkung (the cadastral district), Flur (a subdivision within it) and Flurstücksnummer (the parcel number within that subdivision). Combined, these form the Flurstückskennzeichen, the reference authorities, notaries and (as we will get to) the land register all use to point at one unambiguous piece of ground.
Regions, catchments and radii are useful for finding candidate areas. But nothing gets built, leased, sold or permitted against a region. It gets built, leased, sold or permitted against one or more Flurstücke. A site search that stays at region level is still doing reconnaissance; a site search that resolves to Flurstücke is doing due diligence. That resolution step is where most of the real work, and most of the friction, sits.
What is ALKIS, and what does it actually contain?
ALKIS, the Amtliches Liegenschaftskatasterinformationssystem, is Germany's official real-estate cadastre: the authoritative record of land parcels, their boundaries and their official area. It is maintained by each state's surveying authority (Vermessungsverwaltung), and its data model is standardised nationwide by the AdV so that a Flurstück in Brandenburg and a Flurstück in Baden-Württemberg carry the same core structure even though a different authority maintains each. ALKIS is the successor to the older ALB (Automatisiertes Liegenschaftsbuch, the textual register) and ALK (Automatisierte Liegenschaftskarte, the map), which it merged into a single digital system.
What ALKIS carries, in practical terms, is geometry (the boundary polygon of each Flurstück, as maintained by the cadastre, not a value estimated after the fact), identifiers (the Gemarkung, Flur and Flurstücksnummer that combine into the Flurstückskennzeichen) and official area (a registered figure, not a GIS calculation from the polygon). Depending on the state, it can also carry the tatsächliche Nutzung, the actually recorded land use.
What ALKIS does not carry is ownership. Ownership sits in the Grundbuch (the land register), a separate legal system that references Flurstücke but is not part of ALKIS itself. This distinction matters for how you use the data: ALKIS tells you what a parcel is and where it sits; it does not tell you who owns it. For screening, valuation and planning work, that is usually enough, because the Flurstückskennzeichen it gives you is exactly what you need to reference the parcel unambiguously once you do approach an owner or authority.
It is also worth being precise about certification. What a harmonised data layer delivers is a data copy of the cadastral record, useful for analysis at scale. Where a transaction or a court requires a certified extract, that comes only from the competent Katasteramt as a beglaubigter Auszug. The two serve different purposes: one lets you screen and analyse across hundreds or thousands of sites, the other is the legal document a specific deal needs.
Why is parcel geometry the thing that makes other data joinable?
Here is the part that is easy to underrate: parcel geometry is not just one more layer, it is the join key that makes every other layer usable at the site level. A Bebauungsplan (a binding zoning plan) tells you what may be built somewhere; a flood hazard layer tells you what risk exists somewhere; a portfolio of leases tells you what you already hold somewhere. None of those "somewheres" become a decision until they are pinned to the same parcel.
Once you have a Flurstück boundary as clean geometry, everything else becomes a spatial join instead of a manual lookup:
- Overlay a zoning plan against parcel boundaries and you get a filter: which parcels sit fully inside a Gewerbegebiet, which straddle a boundary, which fall outside any plan at all
- Overlay a hazard layer and you get a screen: which parcels in a shortlist carry flood or contamination exposure before anyone visits a site
- Overlay your own portfolio, lease or CRM records and you get a map of what you already control, keyed to a stable identifier rather than a fuzzy address match
This is the practical reason Flurstücke matter as a data layer rather than as a legal curiosity. The parcel is the geometry every other dataset ultimately needs to sit on top of.
Why is this data so hard to get across all of Germany?
If parcel data is this useful, the obvious question is why every GIS team does not already have it. The answer is structural, not technical.
Each of Germany's federal states runs its own surveying authority, and each authority publishes its own extract of the same underlying ALKIS standard. The AdV standardises the core model, but publication itself, formats, access routes, open-data terms, licensing, is a state-by-state decision. Some states publish clean vector geodata through open geoportals; others gate access behind different terms, formats or request processes. Assembling a nationwide, consistent view means dealing with sixteen separate authorities, sixteen separate publication decisions, and no single federal switch that turns it all on at once.
And then there is Bavaria. Bavaria does not publish its ALKIS parcel data at source in a form that can be carried into a harmonised layer at all. That is not a data-quality complaint, it is simply the current state of publication in that state. A layer that claims full national coverage while quietly working around that gap is not being honest about what it delivers. A layer that states the gap plainly, 15 of 16 federal states, Bavaria excluded because it does not publish at source, is telling you exactly what you are buying and what you are not. That honesty is itself a credibility signal: if a vendor is straight about the one state it cannot cover, you can trust what it says about the fifteen it does.
What does the ALKIS Flurstücke layer actually carry?
Mapular's ALKIS Flurstücke layer takes the published cadastral data from the 15 states that publish it and delivers it as one harmonised dataset, with the same schema at every scope. On every parcel:
- Parcel geometry, the boundary polygon as maintained in the cadastre, ready for overlay, intersection and area analysis in any GIS
- Cadastral identifiers, the Gemarkung, Flur and Flurstücksnummer combined into the Flurstückskennzeichen used by authorities, notaries and the land register
- Official area, the registered figure carried by the cadastre, not a value estimated from the geometry
- Actual land use, the tatsächliche Nutzung, where the state publishes it
Because ALKIS is an AdV standard, this core holds everywhere. What differs from state to state is what gets published beyond that core, and Mapular keeps what a state publishes rather than filling the gaps with estimates. Coverage is stated openly per state on the layer page, the same way it is for every dataset in the geospatial data catalog: where a state does not publish, that gap is shown, not smoothed over.
With that schema in place, a workflow like "flag every Flurstück inside this shortlist that overlaps a flood zone or falls outside the zoned use we need" stops being a set of manual lookups across sixteen portals and becomes a query with a consistent answer, across every state that publishes.
Where should you go from here?
If your team is still resolving sites to parcels one Katasteramt or geoportal at a time, the ALKIS Flurstücke layer page lays out the attributes, the per-state coverage and the access routes, including the honest statement of where Bavaria sits outside it. You can request sample data and validate the schema against your own workflow, whether that is site search, due diligence or portfolio mapping, before committing to anything.
