Release notes of Kadaster
Driver Release Note - Cloud
Kadaster driver 27.0, from 26.0
| Build | Date | Description |
|---|---|---|
26.0.4 |
22-03-2026 | first build of release 26.0 |
27. |
10-11-2026 | latest build of release 27.0 at the time of writing |
Data models compared: 26.0.340-PROD+6295 and 27.0.6-PROD+6293.
The older end is the first build of release 26.0, not its last, because later builds of 26.0 received ports of changes made for 27.0. The data model of a release is the model that a later build of the same release generated.
- 16 changes
- 4 can break a statement
- 0 groups not available
This Note
Groups
- Data model 11
- Provider attributes 3
- Capabilities 0
- Performance 1
- Bug fixes 0
- Enhancements 0
- Log-on and platform 1
More
What Changed, by Group
Every change is in one group: the group answers the question that you ask before you upgrade.
- Data model
- 11
- 3 can break a statement
- Do my statements and views still work?
- Provider attributes
- 3
- Do I have to change my connection string, provider file or settings?
- Capabilities
- 0
- What can the driver do with a table?
- Performance
- 1
- Is it faster, and does it call the platform less?
- Bug fixes
- 0
- Is the defect that I met repaired?
- Enhancements
- 0
- What can I do now that I could not?
- Log-on and platform
- 1
- 1 can break a statement
- Do I have to log on again, or change something because of the platform?
Before You Upgrade
These changes can stop an existing statement, view, connection string or script from working:
- Kadaster driver rebuilt on the OGC API of the PDOK Kadastrale Kaart
- Replace statements that use the table functions percelen, percelen_op_coordinaat and percelen_geojson of the Kadaster schema by the tables of the Features schema, for example percelen filtered on the columns that start with properties_. The columns and their names differ.
- Table function Kadaster.Kadaster.percelen is removed
- Check statements, views and scripts that use it before the upgrade.
- Table function Kadaster.Kadaster.percelen_geojson is removed
- Check statements, views and scripts that use it before the upgrade.
- Table function Kadaster.Kadaster.percelen_op_coordinaat is removed
- Check statements, views and scripts that use it before the upgrade.
Top 12 Changes
Changes that can break a statement first, then by importance. Columns are summarised per table in the data model.
- Kadaster driver rebuilt on the OGC API of the PDOK Kadastrale Kaart
- Log-on and platform
- Breaks an existing statement or script.
- Table function Kadaster.Kadaster.percelen is removed
- Data model
- Breaks an existing statement or script.
- Table function Kadaster.Kadaster.percelen_geojson is removed
- Data model
- Breaks an existing statement or script.
- Table function Kadaster.Kadaster.percelen_op_coordinaat is removed
- Data model
- Breaks an existing statement or script.
- Table function Kadaster.Features.bebouwingen is added
- Data model
- Importance 3 of 5.
- Table function Kadaster.Features.kadastrale_grenzen is added
- Data model
- Importance 3 of 5.
- Table function Kadaster.Features.nummeraanduidingreeksen is added
- Data model
- Importance 3 of 5.
- Table function Kadaster.Features.openbare_ruimtenamen is added
- Data model
- Importance 3 of 5.
- Table function Kadaster.Features.percelen is added
- Data model
- Importance 3 of 5.
- Attribute max-discovered-column-count is added
- Provider attributes
- Importance 3 of 5.
- Driver setting technical documentation url changes
- Provider attributes
- Importance 3 of 5.
- Lower memory use when reading JSON answers
- Performance
- Importance 1 of 5.
Data model
Do my statements and views still work? Tables, views, table functions, columns, parameters, keys, code values, packages and procedures that appear, disappear, are renamed or change type.
- 11 changes
- model files
Tables, Views and Table Functions
Table function Kadaster.Kadaster.percelen is removed
A statement that reads Kadaster.Kadaster.percelen fails after the upgrade. It had 8 columns. Statements that call these table functions must be rewritten to the tables of the Features schema.
What to Do
Check statements, views and scripts that use it before the upgrade.
- can break a statement
- importance 5
Table function Kadaster.Kadaster.percelen_geojson is removed
A statement that reads Kadaster.Kadaster.percelen_geojson fails after the upgrade. It had 8 columns. Statements that call these table functions must be rewritten to the tables of the Features schema.
What to Do
Check statements, views and scripts that use it before the upgrade.
- can break a statement
- importance 5
Table function Kadaster.Kadaster.percelen_op_coordinaat is removed
A statement that reads Kadaster.Kadaster.percelen_op_coordinaat fails after the upgrade. It had 8 columns. Statements that call these table functions must be rewritten to the tables of the Features schema.
What to Do
Check statements, views and scripts that use it before the upgrade.
- can break a statement
- importance 5
Table function Kadaster.Features.bebouwingen is added
The table function has 14 columns and can select.
- importance 3
Table function Kadaster.Features.kadastrale_grenzen is added
The table function has 18 columns and can select.
- importance 3
Table function Kadaster.Features.nummeraanduidingreeksen is added
The table function has 9 columns and can select.
- importance 3
Table function Kadaster.Features.openbare_ruimtenamen is added
The table function has 18 columns and can select.
- importance 3
Table function Kadaster.Features.percelen is added
The table function has 22 columns and can select.
- importance 3
Columns
0 added, 0 removed, 2 changed, in 1 tables.
Kadaster.Native.NATIVEPLATFORMSCALARREQUESTS: 0 added, 0 removed, 2 changed
Kadaster.Native.NATIVEPLATFORMSCALARREQUESTS: 0 added, 0 removed, 2 changed~DURATION_MS(database_data_type:int64→double)~DURATION_MS(dotnet_data_type:int64→double)
Parameters, Packages and Procedures, Keys and Code Values
Procedure dcr_metadata.get_partitions is added
- importance 1
Provider attributes
Do I have to change my connection string, provider file or settings? Attributes of the connection and settings of the driver that appear, disappear or change default or place where they can be set.
- 3 changes
- model files
Driver setting technical documentation url changes
Technical documentation url changes from https://app.swaggerhub.com/api/pdok/brk to https://api.pdok.nl/kadaster/brk-kadastrale-kaart/ogc/v1?f=html.
https://app.swaggerhub.com/api/pdok/brk→https://api.pdok.nl/kadaster/brk-kadastrale-kaart/ogc/v1?f=html- importance 3
Engine-wide connection attributes change
45 attributes added, 2 removed and 5 settings of attributes changed. These attributes belong to the SQL engine and exist for every driver; the Query Tool notes describe them.
- importance 2
Attribute max-discovered-column-count is added
Can be set from connection string, SET statement, provider file, log-on. Default 250.
- importance 3
Capabilities
What can the driver do with a table? Whether a table or table function can be selected from, inserted into, updated and deleted from.
- 0 changes
- model files
No changes in this group.
Performance
Is it faster, and does it call the platform less? Paging, batching, caching, filters and projections sent to the platform, fewer requests, less memory.
- 1 changes
- commits
Lower memory use when reading JSON answers
The driver reads the answers of the platform with a lighter JSON reader that allocates less memory, and prepares a buffer of a fitting size.
- importance 1
- confidence medium
Bug fixes
Is the defect that I met repaired? Wrong or missing rows, wrong values, crashes and wrong messages, repaired in a release line that had the defect.
- 0 changes
- commits
No changes in this group.
Enhancements
What can I do now that I could not? New functions and options that are not a table or a column.
- 0 changes
- commits
No changes in this group.
Log-on and platform
Do I have to log on again, or change something because of the platform? Log-on and token handling, scopes and permissions, a new version of the platform API, retired endpoints and changed limits.
- 1 changes
- commits
Kadaster driver rebuilt on the OGC API of the PDOK Kadastrale Kaart
The driver now reads the feature collections of the Kadastrale Kaart (parcels, cadastral boundaries, buildings, public space names and address number ranges) from the OpenAPI specification that PDOK publishes. The three table functions of the former driver are no longer offered. Equality filters on parcel properties and row limits are sent to the platform, and pages of up to 1,000 features are read.
What to Do
Replace statements that use the table functions percelen, percelen_op_coordinaat and percelen_geojson of the Kadaster schema by the tables of the Features schema, for example percelen filtered on the columns that start with properties_. The columns and their names differ.
- can break a statement
- importance 5
- confidence medium
In Numbers
Objects of the data model at both ends of the step.
| Objects | 26.0 | 27.0 | Change |
|---|---|---|---|
| tables | 0 | 0 | +0 |
| views | 1 | 1 | +0 |
| table functions | 0 | 0 | +0 |
| columns | 53 | 110 | +57 |
| function parameters | 7 | 73 | +66 |
| attributes of driver | 0 | 1 | +1 |
| tables that can insert | 1 | 1 | +0 |
| tables that can update | 0 | 0 | +0 |
| tables that can delete | 0 | 0 | +0 |
More Information
- Data model documentation of the driver
- Questions and answers on the forum
- Invantive Cloud page of the driver
- Documentation of the platform
- All release notes
How This Note Was Made
- 2026-11-01T10:17:38.535328Z
- 2026-11-01T12:54:18.4472055Z
- Fields that only the newer model has.
- Fields that only the newer model has.
- Fields that only the newer model has.
- Fields that only the newer model has.
- Fields that only the newer model has.
- Fields that only the newer model has.
- Commit items were classified by one reader; the model changes are derived and need no reading.
- Commits: the commits of the driver directory in the range that have no equivalent patch in the older state, without merges and version stamps; each was classified by reading its message and change.
- Model: the NDJSON files of data-models/database of the workspace of each release are compared record by record; only fields that both models have are compared, and texts are counted, not listed.
- A model generated from a later build of the same release (for example 26.0.340 for 26.0) stands for the release.
- 15 links between a change and a source commit are recorded.