In 2016, FutureWater released a new dataset: HiHydroSoil v1.2, containing global maps with a spatial resolution of 1 km of soil hydraulic properties to support hydrological modeling. Since then, the maps of the HiHydroSoil v1.2 database have been used a lot in hydrological modeling throughout the world in numerous (scientific) projects. A few examples of the use of HiHydoSoil v1.2 are shown in the report.
Important input of the HiHydroSoil database is ISRICS’ SoilGrids database: a high resolution dataset with soil properties and classes on a global scale. In May 2020, ISRIC has released the latest version (v2.0) of its Soilgrids250m product. This release has made it possible for FutureWater to update its HiHydroSoil v1.2 database with newer, more precise and with a higher resolution soil data, which resulted in the development and release of HiHydroSoil v2.0.
Soil information is the basis for all environmental studies. Since local soil maps of good quality are often not available, global soil maps with a low resolution are used. Furthermore, soil maps do not include information about soil hydraulic properties, which are of importance in, for example, hydrological modeling, erosion assessment and crop yield modelling. HiHydroSoil v2.0 can fill this data gap. HiHydroSoil v2.0 includes the following data:
- Organic Matter Content
- Soil Texture Class
- Saturated Hydraulic Conductivity
- Mualem van Genuchten parameters Alfa and N
- Saturated Water Content
- Residual Water Content
- Water content at pF2, pF3 and pF4.2
- Hydrologic Soil Group (USDA)
Download HiHydroSoil v2.0
The HiHydroSoil v2.0 database can be accessed after filling the brief request form below. A download link to the full dataset will then be provided. The HiHydroSoil v2.0 dataset is organized in two folders, one containing the original data for each of the six depths, and one with the aggregated subsoil and topsoil data. All data layers are delivered in geotiff raster format.
Important! To avoid lengthy download times, the data layers originally consisting of float data type were multiplied by a factor of 10,000, and subsequently converted to integer type. It is therefore required to translate the data to the proper units by multiplying with 0.0001. These steps are also described in the readme file delivered with the data.