Repository navigation
CBS area division
The neighbourhoods, districts, municipalities, COROP regions and provinces of the model come from the area division of CBS (CBS gebiedsindelingen): one gpkg per year, cbsgebiedsindelingen<year>.gpkg in %NetworkModel_Dir%/RegioIndelingen. SourceData/RegioIndelingen/Divisions reads them per year, as Divisions/Y<year>. This page describes how the map of a new year becomes usable as origins and destinations.
A region set uses a CBS year in one of two ways. The neighbourhood sets with a year in their name, Buurt2023 and Buurt2025, always read the map of that year (#126). The sets without a year of their own (Buurt, the districts, municipalities, COROP regions, provinces and the other sets under SourceData/RegioIndelingen) read the year of the analysis moment: the column Regios of AnalysisMomentPresets, in group 7 of ModelParameters.dms (the attribute RegioIndelingen_year). The steps below add a year. Their example is the map of 2026. The point of each neighbourhood is weighted with the dwellings of the BAG of 1 January of the same year; see BAG and centroids.
- Step 1: get the gpkg
- Step 2: check its tables
- Step 3: add the year to the years that the model reads
- Step 4: choose the year
- Step 5: check the neighbourhoods and their points
- Which caches the new year replaces
Download the area division of the year from the page of CBS above and put the gpkg in %NetworkModel_Dir%/RegioIndelingen as cbsgebiedsindelingen<year>.gpkg, for example cbsgebiedsindelingen2026.gpkg.
CBS does not publish all divisions of a year at once: an early gpkg of a year can have the municipalities, COROP regions and provinces, generalised and with provisional label points, without the neighbourhoods and districts. A year can be used once its gpkg has the tables that the model reads:
| Division | Table from 2020 on | Table before 2020 |
|---|---|---|
| neighbourhoods, districts, municipalities |
buurt_niet_gegeneraliseerd, wijk_niet_gegeneraliseerd, gemeente_niet_gegeneraliseerd
|
cbs_buurt_<year>_niet_gegeneraliseerd and so on for 2019, cbs_buurt_<year>_gegeneraliseerd and so on before 2019 |
| COROP regions, COROP-plus regions, provinces, care office regions |
coropgebied_gegeneraliseerd, coropplusgebied_gegeneraliseerd, provincie_gegeneraliseerd, zorgkantoorregio_gegeneraliseerd
|
cbs_coropgebied_<year>_gegeneraliseerd and so on |
The model takes the boundaries that are not generalised wherever CBS delivers them; with these boundaries it places the dwellings of the BAG in their neighbourhood, district and municipality. CBS delivers them for the neighbourhoods, districts and municipalities from 2019 on, and for the other divisions not at all; the generalised versions fill the rest (Divisions_years/IsGeneralised, Path_str and Path_Gen_str in cfg/main/SourceData/RegioIndelingen.dms). Any tool that reads a gpkg, such as QGIS, shows the tables.
Divisions_years in cfg/main/SourceData/RegioIndelingen.dms sets the years that Divisions reads, as range(uint32, 2000, <last year + 1>). Raise the upper bound so that the new year is in it: range(uint32, 2000, 2027) for 2026.
For the sets without a year of their own, put the year in the column Regios of the analysis moments that use it, in AnalysisMomentPresets (group 7 of ModelParameters.dms).
For a neighbourhood set of its own, add a row Buurt<year> to Advanced/org_domain_list and to Advanced/dest_domain_list in ModelParameters.dms, with the path SourceData/RegioIndelingen/Divisions/Y<year>/Buurt/Centroids, as the rows of Buurt2025, and raise nrofrows of each list by one. Choose the set as Orgset and Destset, in ModelParameters.dms or with -set Orgset Buurt<year> -set Destset Buurt<year> for a call of UpdateAll.cmd. The names of caches and output files then hold b<year> (Impl/OrgSet_PathTag).
Both ways need the BAG of 1 January of the year in the BAG delivery of BAG_file_date; a delivery made after that date holds it.
Read the neighbourhoods of the year and their points, in a GeoDmsRun of its own. Open a command prompt in the folder NetworkModel_PBL:
set "GEODMS_EXE=C:\Program Files\ObjectVision\GeoDms20.28.0.m\GeoDmsRun.exe"
set "Y=/SourceData/RegioIndelingen/Divisions/Y2025"
if not exist batch\log md batch\log
"%GEODMS_EXE%" /Lbatch\log\CBS_read.log "%CD%\cfg\main.dms" @statistics %Y%/Buurt/statcode @statistics %Y%/Buurt/CalcAddressCentroids/HasAddresses @statistics %Y%/Buurt/CalcAddressCentroids/IsStatcode_equal
The example reads 2025; put the new year in the second line. No line of the log may start with [E]. The console shows per item Count and, for the two yes-no items, Sum, the number that is true. A new year gives about the same numbers as 2025:
| Item | 2025 | What it counts |
|---|---|---|
Buurt/statcode, Count
|
14,729 | the neighbourhoods |
HasAddresses, Sum
|
14,281 | the neighbourhoods with at least one dwelling |
IsStatcode_equal, Sum
|
13,669 | the neighbourhoods whose mean dwelling point lies in the neighbourhood itself; the others get the point of their area (centroid_or_mid) |
The 2025 numbers come from the BAG delivery of 8 October 2026.
The model makes the caches of the new year by itself. A set without a year of its own carries the year in Impl/OrgDest_Tag (-cbs<year>), which is in the signatures of the pre- and post-transport caches, the car caches and the output. A new neighbourhood set has its own name in them. So nothing has to be removed.
A new delivery of a year that is already used, for example a corrected gpkg of CBS, is not noticed, because the signatures hold the year and not the content. Then remove, in %LocalDataProjDir%, the caches of the sets of that year (in IntermediateResults the Legs_... files and the DirectCar_... folders) and the output made with them. The chain cache does not depend on the origins and destinations and stays.
NetworkModel PBL documentation