NL Kadastrale Perceelgrenzen Lookup per Adres

Looks up the Dutch cadastral parcel (Kadaster) that contains a given address, postcode, or coordinate — parcel identification (gemeente/sectie/nummer), area in m², and validity date — straight from the official PDOK Kadastralekaart. Deliberately excludes owner data: that requires the paid BRK ownership-information API and a documented legitimate interest under GDPR, which is out of scope for this actor.

When should an AI agent use this?

• "Which cadastral parcel (kadastraal perceel) is this address registered on?"
• "What is the official cadastral area (m²) of this plot?"
• "Get the parcel identification (gemeente/sectie/nummer) for a list of addresses."
• "Check the registered parcel size before a land or property transaction."
• "Add cadastral parcel metadata to a real-estate due-diligence dossier."

What this Actor does

• Geocodes any Dutch address, postcode, place name, or "lat,lon" coordinate via the official PDOK Locatieserver
• Queries the official PDOK Kadastralekaart WFS (Kadaster/PDOK, CC0) for the cadastral parcels near that point
• Determines the parcel that actually contains the point via real polygon geometry — not just a bounding-box guess, so a neighboring parcel's overlapping bounding box never gets mistaken for the right one
• Returns the parcel's identification (gemeente sectie nummer, e.g. "RLD00 R 302"), section, area in m², area-value provenance ("Vastgesteld"/"Berekend"), and validity date
• Returns null for the parcel field when the point falls outside any registered parcel (e.g. open water) — not an error
• Processes up to 50 locations per run, with configurable concurrency

Input

Field	Type	Description	Example
locaties	array of strings	Address, postcode, place name, or "lat,lon" per location (1-50)	["Bathseweg 27, Rilland"]
concurrency	integer	How many locations to process in parallel	3

Output

{
  "invoer": "Bathseweg 27, Rilland",
  "gevonden": true,
  "fout": null,
  "foutcode": null,
  "weergavenaam": "Bathseweg 27, 4411BA Rilland",
  "postcode": "4411BA",
  "gemeente": "Reimerswaal",
  "provincie": "Zeeland",
  "lat": 51.41533763,
  "lon": 4.18586885,
  "geocodingScore": 19.1,
  "geocodingBetrouwbaarheid": "hoog",
  "perceel": {
    "identificatie": "RLD00 R 302",
    "kadastraleGemeenteCode": "830",
    "kadastraleGemeenteNaam": "Rilland",
    "akrGemeenteCode": "RLD00",
    "sectie": "R",
    "perceelnummer": 302,
    "oppervlakteM2": 528,
    "oppervlakteHerkomst": "Vastgesteld",
    "beginGeldigheid": "2006-12-15T10:44:34Z"
  },
  "bron": "PDOK Kadastralekaart WFS (service.pdok.nl/kadaster/kadastralekaart) + PDOK Locatieserver (geocoding)"
}

fout is a human-readable error message (null on success). foutcode is a machine-readable classification for agents/automation, one of:

Code	Retryable?	Meaning
null	—	No error.
GEEN_GEOCODING_MATCH	No	PDOK Locatieserver found no match for this input — retrying the same input won't help.
UPSTREAM_ERROR	Yes	Temporary HTTP/connectivity failure at PDOK Locatieserver or the PDOK Kadastralekaart WFS (after built-in retries) — a later run may succeed.
ONBEKENDE_FOUT	No	Unexpected error that doesn't fit the categories above.

Use cases

• Add cadastral parcel identification and area to a real-estate or land-transaction dossier
• Validate a plot's registered area before a purchase agreement or subdivision
• Batch-check parcel identification for a portfolio of addresses
• Support a neighbor-dispute or boundary-orientation review with the official parcel reference

Pricing

This Actor uses Apify's Pay-Per-Event (PPE) pricing model.

• Actor Start: $0.00005 (Apify default)
• locatie-resultaat: $0.006 per location checked

Legal

Uses only official, open, CC0-licensed government data: the PDOK Kadastralekaart WFS (Kadaster/PDOK) for parcel geometry/identification, and the PDOK Locatieserver for geocoding. Deliberately excludes owner names/ownership data — that requires the paid BRK ownership-information API and a documented legitimate interest under GDPR, which is out of scope for this actor. No personal data is processed.

FAQ

Q: Does this return who owns the parcel? A: No. Owner data (BRK eigendomsinformatie) requires a separate, paid Kadaster API and a documented legitimate interest under GDPR — this actor only returns the public parcel geometry, identification, and area.

Q: What if the address doesn't fall on a registered parcel? A: The perceel field is null — this happens for locations like open water or unregistered land, and is not treated as an error.

Q: How is the correct parcel determined when several parcels are nearby? A: The actor checks real polygon geometry (point-in-polygon), not just bounding-box overlap — so a neighboring parcel whose bounding box happens to overlap the point is never mistaken for the actual containing parcel.

Q: What does "oppervlakteHerkomst" mean? A: The Kadaster's own qualification of the area value — "Vastgesteld" (surveyed/fixed) or "Berekend" (calculated) — included as-is from the source.

Related Actors

• NL Bodemrisico Check — same geocoding pattern, checks soil contamination instead of the cadastral parcel.
• NL Natura2000 Afstandscheck — same geocoding pattern, checks distance to protected nature areas.
• Vastgoed XXL — combines multiple official Dutch geo-data sources into one property dossier; a natural companion enrichment.

---

Zoekwoorden: kadastraal perceel opzoeken, perceelgrenzen adres, kadastrale kaart, perceeloppervlakte, kadastrale aanduiding, sectie perceelnummer.

Keywords

kadaster, cadastral, perceel, netherlands, pdok, kadastrale-kaart, parcel, land-registry, geocoding

Changelog

0.1.0

• Initial release.