EN Impact modules and indicators

This is an English translation of the Dutch page Effectmodules en indicatoren, which is leading. Translated on 8 November 2026 from wiki commit 428045e.

Overview of the impact modules and indicators in RSopen, grouped by theme.

The indicators are computed per case and per projection year and are stored under /Indicatoren/<casus>/Zichtjaren/<zichtjaar>/, plus a base-year version under /Indicatoren/<casus>/Basisjaar/. A case is a scenario plus a variant, for example WLO_hoog_NbSGenuanceerd. Which variants exist belongs to the application and not to the model: NL2120 application (in Dutch) computes with BAU, BAU2, NbSGenuanceerder and NbSGenuanceerd, the Ruimtelijke Verkenningen 2023 and the pilot application Friesland with others. Variant names on these pages are therefore examples; see Part III for the applications.

Output and export

Each indicator writes its maps as GeoTIFF to %LocalDataProjDir%/Indicatoren/<casus>/, with the projection year and the study area in the file name. Maps of the base year go to the base-year folder.

In addition, Templates/Indicatoren_T/Export.dms bundles the indicators needed for a delivery. By default that bundle writes the last projection year; you choose an earlier projection year with the environment variable ExportZichtjaar, without changing the configuration. The base year is not an export year: every export item reads the projection-year container, and the base year is a container of its own with part of the indicators. What does have a meaning there is in a base-year table of its own, see below.

Next to every exported map there is also a table row (#658). Export/Tabellen/PerIndeling (template RegionaleIndicatoren_T) has a column per indicator, aggregated to one regional division that applies to all indicators at once. Which one that is, is set in ModelParameters/Advanced/IndicatorRegio_ref: NL, Provincie, COROP, Gemeente, NVM or one of the four landscape areas Landschap_Kust, Landschap_Rivieren, Landschap_Veen and Landschap_Zand, the boundaries that the landscape teams deliver (#760). Those four overlap, so each is a run with its own mask; see Landscape areas (in Dutch). In addition, each run writes a second table, NationaleIndicatoren, which always covers the whole country and does not depend on the switch. The sum columns count over the cells that the division assigns at 25 metres (Per_AdminDomain_Fijn, #748); a national figure from the table can therefore differ slightly from the same sum over the map. The choice affects only the tables; the maps stay at cell level, and the national totals at the indicators themselves, with suffix _Per_NL, are separate from it.

With ModelParameters/TabellenUitExport on, an environment variable just like ExportZichtjaar, the regional and national aggregations read back the per-cell maps that the export of the same projection year has written, instead of computing them again. That changes the way of computing and not the outcome; a table per division then does not have to compute the heavy chains of the projection year once more (#824).

Two tables put the base year next to it. Basisjaar_NationaleIndicatoren and Basisjaar_Indicatoren_<indeling> carry the columns that have a meaning in the base year, with the same names and calculation rules as the projection-year table: the stock of dwellings and jobs, the densities, the sealed surface, the cloudburst storage requirement, the accessibility of greenery and of jobs, and the flood damage; not what is a change, a cumulative or a present value since the base year. And Claims_Reeks gives the demand for space of the scenario as a series: the state of the base year and then the claim per projection year, nationally, per housing segment and for jobs.

Two things fall outside the indicator table, and that is on purpose. Claim realisation (in Dutch) belongs per allocation region of the sector concerned, because that is where the claim is imposed as well; those tables carry, next to the state and the claim of the projection year, also the state of the base year. And a land-use map is a class per cell and does not aggregate to one number per region but to an area per class. Those areas are in Export/Grondgebruik: Landgebruik_Areaal (main classes, base year and projection year nationally), LandgebruikNL2120_Areaal and LandgebruikHoofdklasse_Areaal (per class, nationally and per landscape area), LandgebruikNatDroog_Areaal (the nature summarised as wet, dry and still to be converted, on the twofold division that LU_NL2120 carries per class) and of the last three a _Basisjaar counterpart with the same columns.

Amounts over time

Every cost and value indicator has, next to the nominal amount, a counterpart with the net present value in the base year, recognisable by the suffix _NCW. How that factor is determined per kind of amount is on Discounting and net present value (in Dutch).

Land use and agriculture

Land-use map (in Dutch)
Classes of the land-use map (in Dutch)
Land-use change (in Dutch)
Sealed surface (in Dutch)
Fertile agricultural land (in Dutch)
Yield loss (in Dutch)

Allocation

Housing, value and costs

Value of new dwellings (in Dutch)
Dwelling value due to changes in greenery (in Dutch)
Demolition and new construction of dwellings (in Dutch)
Dwelling stock by construction year (in Dutch)
Buy-out and demolition costs (in Dutch)
Costs of housing construction (in Dutch)
Land development budget (in Dutch)
Costs of work locations: the extra raising against water on allocated work locations, see Flood damage (with HIS-SSM) (in Dutch)
Foundation damage (in Dutch)

Climate, water and soil

CO2 emissions from peat areas (with SOMERS) (in Dutch)
Carbon storage and sequestration (in Dutch)
Flood damage (with HIS-SSM) (in Dutch)
Cloudburst storage in built-up areas (in Dutch)
Rainwater reuse (in Dutch)
Water storage: the indicator and the sector (in Dutch)

Greenery, accessibility and health

Accessibility of greenery (in Dutch)
Accessibility of jobs (in Dutch)
Mortality due to changes in greenery (in Dutch)