Custom BRP Crop Parcels integration
The Basisregistratie Gewaspercelen (Crop Parcels Register) shows which crop is grown on each agricultural parcel, along with the parcel's location. It is an open dataset from RVO, published via PDOK, with a new annual edition each year. Note that this is not the same as the Basisregistratie Personen (Personal Records Database), which is also abbreviated to BRP. Appfront builds the integration that uses crop parcels in your own systems: retrieving parcels in an area, comparing crops year on year and linking the results to your own data.
What is a BRP Crop Parcels integration?
A BRP Crop Parcels integration retrieves the location of agricultural parcels and the crop grown from RVO's open dataset and makes it usable in your own systems. According to PDOK, the file is a selection from the register of the Netherlands Enterprise Agency (RVO). The user of a parcel marks out their parcels each year and indicates which crop is grown on them; this is registered with RVO in Mijn percelen (My parcels). A dataset is created for each year with a reference date of 15 May. The parcel boundaries are based on RVO's reference register, the former Agrarisch Areaal Nederland (Agricultural Area of the Netherlands). The dataset is free to use; PDOK publishes it with a Public Domain Mark.
PDOK offers the latest year as WMS, WFS, OGC API Features and an ATOM download service; older years, going back to 2009, are available as downloads. For each parcel, the OGC API includes the geometry, crop category, crop, crop code, year and status, among other things. It says nothing about who uses the parcel: it is a map of crops, not a register of farmers. RVO publishes the crop codes themselves in annual lists. So here BRP stands for Basisregistratie Gewaspercelen (the crop parcel register). If you are looking for data from the Basisregistratie Personen (the personal records database), that is a completely different register with its own rules, and we have a separate page for it.
We build custom solutions because the dataset only becomes valuable when combined with your own data. A water board wants to know which crops are growing in a water level area, a consultancy wants to see cultivation in a project area over several years, a supplier wants to overlay parcels with its own customer area. The integration retrieves the parcels in an area, translates crop codes into the crop groups you use yourself, compares years and puts the result into your map, database or report. With every new year's data, the same processing runs again.
Per parcel
Location and crop.
Per year
Years side by side.
With your data
Linked to your areas.
How we build your BRP crop parcels integration
We start with your question: which area you need crop information for, which years, which crop classification you use yourself and which system the result needs to end up in. Then we choose the route: the OGC API for targeted queries or the download service for complete years. We first build the processing for one area and one year, translate the crop codes into your classification and let you review the result on the map. More areas, older years and the link with your own data follow once that works well. After that, the integration processes each new year in the same way.
Area, years, crop classification.
OGC API or download.
Reviewed on the map.
Go-live, monitoring and maintenance per year.
What a BRP crop parcels integration actually does
The components below appear in almost every integration with the crop parcels. Which ones you need depends on your area, the number of years and what you do with the result.
Requesting
Parcels per area.
Crop codes
Translated to your classification.
Annual releases
Cultivation over the years.
Linking
To your own areas.
Statements
Acreage per crop group.
Log
Every query can be traced.
Who we build a BRP crop parcels integration for
The integration is intended for organisations that regularly want to know what is being grown in an area and currently work this out with separate downloads and manual work in a GIS package. The larger the area and the more years, the more it delivers.
Water boards
Crops per water level area.
Consultancies
Cultivation in a project area.
Chain partners
Acreage in your working area.
Researchers
Years side by side.
Technology and integrations
This page is about the open crop parcels dataset. If you are looking for data about individuals from the Basisregistratie Personen, our BRP integration for personal data is the right page. If you want to register your own farm's parcels, including crop plan and operations, take a look at parcel registration for arable farming or VVAK parcel registration. For other open geodata, there is the PDOK integration. You can read about our approach on building software.
Why Appfront for your BRP crop parcels integration?
A vintage that has to be downloaded and clipped by hand every year, crop codes that are grouped differently by each employee, or a report that mixes up the Basisregistratie Personen and the crop parcels all cost time and produce figures that nobody can trace back. We build on a different footing: one processing run per vintage, a fixed translation of crop codes and a log in which you can see which data was used.
Repeatable
Every vintage processed the same way.
Unambiguous
Fixed crop classification.
Traceable
Source and year with every figure.
Security and privacy in a BRP Gewaspercelen integration
The dataset itself is open and contains no information about the user of a parcel. As soon as you link the parcels to your own data, such as customers, members or land users, that can change: personal data then comes into play and the GDPR applies. The integration keeps the open data and your own data separate, links them only where you ask it to and records which queries have been made.
The integration runs in a European data centre, with encrypted connections and storage. Because the crop parcels are a snapshot with a reference date of 15 May, the integration shows the year and status of the data with every result. We agree with you in advance who may start processing runs and who may view the linked data.
Frequently asked questions about a BRP Gewaspercelen integration
Questions that water authorities, consultancies and supply chain partners ask before they get started.
An open dataset from RVO (the Netherlands Enterprise Agency) with the location of agricultural parcels and the crop grown on them. It is a selection from RVO's base registry, in which parcel users register their parcels and declare the crop every year. PDOK publishes the dataset.
No. Here, BRP stands for the Basisregistratie Gewaspercelen (the crop parcels base registry). The Basisregistratie Personen is a completely different registry, containing personal data and with strict rules on who may access it. We have a separate page on the BRP integration for that registry.
Per parcel, among other things, the geometry, crop category, crop, crop code, year and status. It does not contain any data about the user of the parcel. RVO publishes the meaning of the crop codes in annual lists.
A dataset is created for each year with a reference date of 15 May. PDOK offers the latest vintage as a view service and download service, and older vintages, going back to 2009, as a download. Any changes to a parcel after the reference date only appear in a later vintage.
PDOK's OGC API publishes the dataset with a Public Domain Mark, and the Nationaal Georegister lists no access restrictions. If you link the parcels to your own data about persons, the GDPR rules apply to that combination.
With parcel registration, a grower records their own parcels, crop plan and operations. The Basisregistratie Gewaspercelen is a national overview of all declared agricultural parcels and crops. An integration uses that overview to look at an area, not to administer a farm.
For organisations that need crop information about a large area every year or more often, or that want to link the parcels to their own areas and data. If you only want to view a map once, the PDOK Viewer will do.
Want to use the crop parcels in your own systems?
Tell us which area and which years you need crop information for, and where it needs to end up. We will show you how an integration does this in the same way every year.