pictures/imod_logo.png

iMOD User Manual version 4.4 (html)


7.12RO-tool

WHY?
The iMOD RO-tool is based on the ArcGIS WaterNOOD-application (“WaterNOOD”approach: “Watersysteemgericht NOrmeren, Ontwerpen en Dimensioneren”) by Stichting Toegepast Onderzoek Waterbeheer ( STOWA).

The WaterNOOD-application provides water managers with information on hydrological requirements of farm crops and vegetation types, and helps them to predict the effects of water management measures on crop-yields and vegetation. The application is used in the water management of nature conservation areas and surrounding agricultural or urban areas.

The iMOD RO-tool (like the ArcGIS WaterNOOD-application) incorporates two knowledge/database/ model-based tools, that are widely used in the Netherlands to determine productivity of farm-crops and potential for development of groundwater dependent vegetation types under various abiotic conditions (soil type and soil-hydrology):

Note: Because this is a Dutch spatial planning tool, based on a Dutch policy-makers’approach for optimizing groundwater regimes for agriculture and nature restoration, Dutch remarks are included.

WHAT?
Abiotic conditions determine productivity of farm-crops and potential for development of groundwater dependent vegetation types. The tool calculates productivity of farm-crops and potential for development of groundwater dependent vegetation types, as a function of abiotic conditions (soil type, seasonal groundwatertables).

Agriculture: actual crop-yield, compared to crop-yield under optimal conditions. The RO-tool calculates the actual crop-yield (relative to crop-yield under optimal abiotic conditions) and decrease of crop-yield due to moisture-stress (“natschade landbouw”) or respiration-stress (“droogteschade landbouw”), given the actual, site specific abiotic conditions (soil type, seasonal groundwatertables). Decrease of crop-yield is calculated in % and/or Euros. doelrealisaties (= 1 –[opbrengstreductiepercentage t.o.v. optimale condities]/100)

Natural vegetation: potential for development of groundwater dependent vegetation types. The RO-tool calculates the potential for development of pre-defined groundwater dependent vegetation types. The potential is expressed as a percentage, relative to the potential for development under optimal abiotic conditions. doelrealisaties (= 1 –[actuele ontwikkeling vegetatie/ontwikkeling vegetaties onder optimale condities]

Urban area: suitability for urban development, as a function of groundwatertable-depth. The RO-tool calculates the suitability for urban development, based on a range of drainage-level, defined in a lookup-table. Groundwatertable above the upper range results in a 0% suitability for building, groundwatertable between upper and lower range results in a 50% suitability for building, and groundwatertable below the lower range results in a 100% suitability for building.

HOW?
The RO-tool is a post-processing scenario-tool. The user can use pre-defined maps of soil types, landuse (crop types) and vegetation types and pre-defined tables of hydrological requirements for vegetation and/or habitat types. All these maps and tables can also be modified by the user, to meet special interests. Input for the hydrological conditions are the Dutch groundwater-table-depth statistics maps (“GHG, GLG, GVG”). They are the result of a groundwate rmodel simulation. The user can run the RO-tool for different groundwater model scenarios.

Explanation of the Dutch groundwatertable-depth statistics (“GHG, GLG, GVG”): The groundwater-table-depth statistics (Mean Highest, Mean Lowest or Mean Spring Watertable depth). The Mean Highest Watertable (MHW or GHG) is defined as the mean value of the three shallowest groundwater depths measured in one year (in meter beneath soil surface), averaged over a period of 8 years with bi-weekly measurements or simulation-results. The Mean Lowest Watertable (MLW or GLG) is defined likewise, with the deepest groundwater depths. The groundwater depths measured at three dates nearest to April 1, are used for calculation of the Mean Spring Watertable (MSW or GVG). The period to calculate MHW is defined between October 1st and April 1st.

Important Note: Despite the fact that the iMOD RO-tool is based on version 2 of the “WaterNOOD”application, it is possible to implement tables with hydrological requirements for user defined vegetation/habitat-types, created with “WaterNOOD”version 3. The tables can be created with and exported from the “WaterNOOD”application, version 3. To download “WaterNOOD”version 3 go to: http://www.synbiosys.alterra.nl/waternood/ and follow the instructions in the manual to export the user created tables for later use in iMOD RO-tool.

Before starting the RO-tool, the desired settings need to be defined in the Preference file (see Section 9.1). The preference tab at the RO-tool window is filled with these settings. The keywords in the preference file are linked to the required input files of the RO-tool. Section 7.12.2 contains a list and description of these files. In Section 7.12.3 the operational setup of the RO-tool is explained and in Section 7.12.4 a list of output files and a short explanation can be found. To start the RO-tool window, select the Toolbox option from the main menu and then choose RO-tool from the bottom of the menu-list.


7.12.1RO-tool window

In this section an explanation is given about each tab on the RO-tool window. General settings on the RO-tool window are:

Compute...

Click on this button to start the scenario based map calculation with the given settings.

Help…

Click on this button to search for relevant information in the iMOD-manual if the directory of the file is defined in the PRF-file (see Section 9.1).

Cancel

Click on this button to Quit the RO tool without saving or computing anything.

After all settings are selected the user can click on the Compute... button to start the scenario computation. Directly after starting the calculation iMOD checks continuously which input files and lookup-tables are needed. The computation is performed per selected subtype. In case one scenario is chosen in combination with a reference situation, iMOD creates, additionally to the reference/scenario related result maps, a map with the difference between reference results and scenario results. Result-files are immediately loaded in the iMOD Manager.

Compute Settings tab:

pictures/h72-end/ro_tool_computesettings.png

Select type

Choose the preferred group of investigation questions. (Note: at this moment only the RO (flood related) type is available.)

Subtype

Depending on the selected type a list of scenario related subtypes appears. Selecting 1 or more subtypes enables the Scenario Input tab.

Compare with reference situation

Check this option if it is preferred to compare the selected scenario with a reference (or other) situation. Checking this option enables the Reference Input tab.

Sprinkling on

This option is only available in drought related scenarios. Check this option if re-wetting through sprinkling during a period of drought is wished. By applying this option, respiration-stress of farm crops is eliminated.

Output directory

Enter the name of the output directory where iMOD stores the scenario results. Default: TMP-folder in the USER directory.

Scenario Input tab:

pictures/h72-end/ro_tool_scenario_input.png

GHG

Enter the directory and name of the GHG-file to be used in the scenario.

GLG

Enter the directory and name of the GLG-file to be used in the scenario.

LUSE (Optional)

Enter the directory and name of the landuse type related file to be used in the scenario (Note: only available if at least an Agriculture-subtype is chosen, or a combination of Agriculture- and Nature-subtypes; not available if only a Nature-subtype is chosen).

NDT (Optional)

Enter the directory and name of the file with the vegetation type(s),"natuurdoeltype kaart" (Note: only available if a Nature-subtype is chosen, or in a combination with a Nature-subtype and Agriculture-subtype).

Result

Enter the directory and name of the result file (Note: not available if more than 1 subtype is selected). On default the Output Folder is selected and the name of the results file equals the chosen subtype description *.idf, e.g. subtype="natschade_landbouw" the name of the file is "natschade_landbouw_SCEN.IDF".

Legend

Enter the directory and name of the legend file (Note: not available if more than 1 subtype is selected).


pictures/h6-h71/image955.png


Click on this button to search for the needed file.

Reference Input tab:
Only available if option Compare with reference situation on tab Compute Settings is checked.

pictures/h72-end/ro_tool_reference_input.png

GHG

Enter the directory and name of the GHG-file to be used in the scenario.

GLG

Enter the directory and name of the GLG-file to be used in the scenario.

LUSE (Optional)

Enter the directory and name of the landuse type related map to be used in the scenario (Note: only available if at least an Agriculture-subtype is chosen, or a combination of Agriculture- and Nature-subtypes; not available if only a Nature-subtype is chosen).

NDT (Optional)

Enter the directory and name of the file with the vegetation type(s), "natuurdoeltype kaart" (Note: only available if a Nature-subtype is chosen, or in a combination with a Nature-subtype and Agriculture-subtype).

Result

Enter the directory and name of the result file (Note: not available if more than 1 subtype is selected). On default the Output Folder is selected and the name of the results file equals the chosen subtype description *.idf, e.g. subtype="natschade_landbouw" the name of the file is "natschade_landbouw_SCEN.IDF".

Legend

Enter the directory and name of the legend file (Note: not available if more than 1 subtype is selected).


pictures/h6-h71/image955.png

Click on this button to search for the needed file.

On the Scenario Input tab and Reference Input tab, it is not necessary to fill in the fields for LUSE ("landgebruik") and NDT ("natuurdoeltype"). When empty, iMOD uses the defined file as given in the Preference file; defined with keyword LANDUSE in case of LUSE and keyword NDT in case of NDT. As mentioned, it is not possible to fill in the fields for Result and Legend whenever more than 1 scenario objective is chosen.

Input Preferences tab:
This tab contains all information as defined in the Preference file (Section 9.1), including cross reference tables, lookup tables and basic files. Files may be placed in any directory and/or different directories on user’s harddisk(s).

pictures/h72-end/ro_tool_input_preferences.png

Item

List of the preference keywords.

Assigned file

Name and directory of a file referring to Item.


7.12.2Preprocessing

The needed input files to be prepared:

As mentioned in Section 7.12 “WHY?”, actual crop-yield, decrease of crop-yield and potential for development of selected vegetation types are determined by use of the two knowledge/database/ model-based tools:

The RO-tool requires maps, tables and binary files that represent the above mentioned knowledge/database/ model-based tools.

To calculate Agriculture-subtypes, these files from “HELP2005-tabellen”are required:

To calculate Nature-subtypes, these files from “WATERNOOD - Hydrologische randvoorwaarden natuur”are required:

To calculate Urban area:

Realization of the RFC soil map
A soil map containing 1:50000 soil codes is needed for this realization as well as a field with an assimilation of the fields "VOOR", "LETTER", "CIJFER", and "KALK". In case a new field needs to be added, ArcView3.x can be used by fill in the following line in the Field calculator:
[VOOR]+[LETTER]+[CIJFER].ASSTRING+[KALK]. The associations are not included in the conversion table and therefore the value of the field "EERSTE_BOD" can be used as a replacement. In the soil map, the codes related to excavated soils starting with a "|"-character are represented in the conversion table with the first two characters of the soil code (RFC-value = 99). All codes starting with a "|"-character can be selected by making use of a query function (in ArcView3.x), e.g. ([fieldname]).contains("|"). Via the calculator the specific field can be filled with the first 2 characters by making use of [CODE].LEFT(2). Similar functions are available in ArcGis. A final step in the preparation of a RFC soil map is joining the soil map with the table RFCCODES.DBF.

Realization of the HELP soil map
The same soil map (1:50000 soil codes) as was used for the realization of the RFC soil map, is needed for realization of the HELP soil map. Only now an additional field is needed, containing the groundwater tables. Accordingly, a compilation of the following fields is included in the map: "VOOR", "LETTER", "CIJFER", "KALK", and "GWT". This field is available in most of the soil maps labeled as "CODE". Next, the "BOD50_2_HLP.DBF" table needs to be joined to the "GWT"-field and converted to a raster format on field "HELPID".


7.12.3Operational setup

To start the computation of the RO-tool, it is necessary to define at least a GHG- and/or a GLG-file (depending on chosen subtype) on the scenario tab. If iMOD cannot find all needed files, an explanatory error is raised. In case a scenario has to be compared with a reference situation, computation is only possible if all required files are defined in the Scenario Input and Reference Input tabs. At the moment everything is correctly defined, clicking on Compute... executes the computation.

In case of comparing a scenario with a reference situation, the output contains:

In case the computation is limited to 1 situation (either scenario, or reference), the output only contains one IDF and table with either actual crop-yield, decrease of crop-yield, or potential for development of chosen vegetation types, depending on the chosen subtype(s).

Calculation of subtype “Urban Area” returns an IDF and table with suitability for urban development (values 0, 50 and 100). A range for drainage-level is defined in a lookup-table. Groundwatertable above the upper range results in a 0% suitability for building, groundwatertable between upper and lower range results in a 50% suitability for building, and groundwatertable below the lower range results in a 100% suitability for building.


7.12.4Output

The output of the computation contains:

The output per subtype is managed over the surface area for which the computation was performed. Cells within the area but lacking any information (nodata values), are not taken into account and therefore these cells are not visible in the output totals.