Data Panda brings Kadaster parcel, address and building data together with the data from the rest of your business. From one place, we turn it into dashboards, automations, AI workflows and custom apps your team uses every day.
Kadaster is the Dutch national land registry and mapping agency, an autonomous government body under the Ministry of Housing and Spatial Planning. It has run the registers since 1832 from its head office in Apeldoorn and maintains the data that the rest of the country leans on for property, address, building and topographic information.
Practically, Kadaster operates several base registers that businesses pull from: BAG for addresses and buildings, BRK for cadastral parcels and ownership rights, BGT and BRT for topography, WOZ for valuation, and KLIC for underground cables and pipelines. Public datasets are exposed through PDOK and the BAG API, with restricted ownership data served through BRK Bevragen for authorised parties. Pulled into a warehouse next to your customer, contract and policy data, those base registers turn one-off lookups into a permanent operational view of the physical assets your business touches.
Every address in your book sitting next to its parcel, building and WOZ value.
Validate, enrich and refresh addresses against the source register, not against last year's CSV.
Use parcel, building and ownership history to score risk, value property and flag mismatches.
Small tools on Kadaster-plus-internal data for the people who deal with property every day.
A list of concrete reports, automations and AI features we have built on Kadaster data. Pick the one that matches your situation.
Which buildings in our book have changed since we last looked?
Every BAG status change on a registered pand or verblijfsobject in your portfolio, dated and tagged: new build, renovation, demolition, function change. The asset list stops drifting away from the physical reality between policy renewals or property reviews.
What is the parcel and building exposure behind this loan?
Per loan: the parcel surface area, registered rights at the BRK, building footprint and function from the BAG, and the latest WOZ valuation, with the delta against last year. Loan-to-value moves from a static intake number to a tracked figure backed by the source register.
Where can we site the next project without a zoning surprise?
Parcel candidates filtered on surface area, owner type, BGT topography and the relevant zoning overlays from PDOK, with KLIC cable density on top. The shortlist that lands on the desk is already pre-cleared on the constraints that usually kill the deal late.
Loan and asset book backed by the actual cadastral record, with WOZ trends, registered rights and parcel changes feeding into provisioning and revaluation. Audit and risk get a primary-source view rather than a stale snapshot in a spreadsheet.
Quotes, proposals and renewals that already know the parcel, the building and the owner behind the address. Account managers walk in with the right surface area, build year and zoning context, not a generic postcode lookup.
Field and back-office teams pulling parcel, building and KLIC data straight from the same view as their work order. Routing, dispatch and project planning rest on the same base map the rest of the country uses.
Salesforce accounts and addresses are validated against the BAG and enriched with parcel surface area, build year, building function and current WOZ value. Account managers walking into a property prospect already know what is on the ground, and a status change on the building drops back into Salesforce as a fresh activity.
HubSpot company and contact addresses are matched to BAG nummeraanduidingen and verblijfsobjecten, with build year and function attached. Marketing campaigns can segment on building type and parcel size, and sales sees the actual property profile next to the deal stage.
Property and equipment records in Business Central are linked to their underlying BAG building and BRK parcel, with WOZ values feeding into book-value reviews and depreciation runs. The fixed-asset module stops being a separate spreadsheet exercise from the property reality.
Real estate held in Exact Online as fixed assets is matched to its BAG identifier and BRK parcel, with the latest WOZ value pulled in for the year-end revaluation. Bookkeepers stop juggling municipal letters into a separate ledger column.
Construction, infra and renovation projects on monday.com are seeded with the parcel, building footprint and KLIC cable density underneath. Tasks, milestones and risk items move with the actual site data instead of a stale brief in a planning document.
Status changes on a tracked pand, parcel right or yearly WOZ delta above a threshold are posted in the right Slack channel for underwriters, asset managers or relationship teams. The change shows up the day the register moves, not at the next quarterly portfolio review.
These are the 1 tables we currently pull from Kadaster into your warehouse. Query them directly in SQL, join them to the rest of your stack, or build reports on top.
Missing a table you need? We can extend the sync. Tell us what is missing and we will build it for you.
You keep the reporting tool you already have. We connect it to the warehouse where your Kadaster data lives.
OAuth authentication. Read-only by default. We sign a DPA and your admin keeps the keys.
Data flows into your warehouse on your schedule. Near real time or nightly, your call. You own the data.
We build the first dashboard, workflow or AI feature with you, then hand over the keys. Or we stay on for ongoing delivery.
We set up the foundation. Your team builds on top.
Best fit Teams that already have a BI analyst or data engineer and want to own the build.
We build the whole thing, end to end.
Best fit Teams without in-house BI or dev capacity. You tell us what you need and we deliver it.
You do. It lands in your warehouse, on your cloud account. We don't resell or aggregate it. If you stop working with us, the warehouse stays yours and keeps running.
Near real time for most operational systems. For heavier sources we schedule hourly or nightly. You pick based on what the reports need.
No. If you don't have one, we help you pick one and set it up as part of the first delivery. Common starting points are Snowflake, Microsoft Fabric, or a small Postgres start.
The open registers (BAG for addresses and buildings, BGT and BRT for topography, parts of WOZ, and the PDOK datasets) come in cleanly through the public APIs and downloads. BRK ownership data is restricted: bulk and API access is gated by Kadaster authorisation, with separate channels for government, notaries and qualified parties. The warehouse path for BRK therefore depends on the access route your organisation already has with Kadaster.
Owner-level BRK data identifies natural persons and is treated as personal data: access is scoped to roles with a doelbinding agreed with Kadaster, identifiable columns ring-fenced and retention policies set before any owner table lands in the warehouse. BAG itself does not contain personal data on residents, so address and building tables are broadly accessible inside your organisation.
The BAG API Individuele Bevragingen is meant for individual lookups and not for bulk dumps, with usage limits in place. For full-portfolio refreshes we use the BAG extract or Digilevering pattern, so live lookups stay inside the published limits and the warehouse holds the full picture for analytics and joins.
We review your Kadaster setup and the systems around it. Together we pick the first thing worth building.