Appendix 5: Database objects/GWSI E 16

From Agri4castWiki
Jump to: navigation, search



content
1. CROP-datasets
2. GRID-datasets
3. SOILS-datasets
4. other datasets


CROP-datasets

content
1.1 CROPS
1.2 CROP_COEFFICIENTS
1.3 CROP_MASKS
1.4 CROP_SEASONS
1.5 CROP_SEASON_AREAS



CROPS

  • Description: Crops
  • Use: To store the crop names and to maintain db integrity via idcrop as reference key
  • Type: Table
  • Remarks: In this implementation, the implemented crops represent generalized crops, rather than actual crops.


CROP_COEFFICIENTS

  • Description: Single crop coefficients (Kc) and crop rooting depth per crop on a 25x25 km resolution.
  • Use: To calculate crop evapotranspiration (ETc) under standard conditions needed for deriving the Water Satisfaction Index (WSI).
  • Type: Table
  • Remarks:

KC values: Single crop coefficients (Kc) incorporate crop characteristics and averaged effects of evaporation from the soil. Currently two crops are implemented that represent landcover types arable land and grassland. The crop coefficients are area-weighted averages of crop coefficients of individual crops assigned to that landcover type. Arable land represents: Maize, Spring wheat, Winter wheat, Millet, Sorghum. Grassland represents: Rotated grazing and Extensive Grazing. Areas used for calculating the weighted average crop coefficients are derived from MAPSPAM (aggregated to 25x25 km resolution). Crop coefficient values are obtained from coefficients FAO.

CROP_ROOTING_DEPTH are area-weighted averages of maximum crop rooting depth of individual crops assigned to that landcover type. Areas used for calculating the weighted average crop rooting depth are derived from MAPSPAM (aggregated to 25x25 km resolution).



CROP_MASKS

  • Description: Crop mask storing the area where the crops are grown on a grid_1km resolution
  • Use: To hide or exclude crop simulations outside the mask, or with a limited area. etc.
  • Type: Table
  • Remarks: The table contains all 1km grids of a crop that have an area > 0. The mask also includes grids for which no seasons are available. Grids for which no seasons are available are currently not stored in grid_1km. Therefore the foreign key referencing grid_1km.idgrid_1km is not installed.


CROP_SEASONS

  • Description: Crop seasons storing unique season id per 1 km grid per crop
  • Use: To link multiple seasons and multiple crops to each grid cell of the grid_1km table
  • Type: Table
  • Remarks:


CROP_SEASON_AREAS

  • Description: support table to holds several mappings between 1 and 25 km grids and SMU and unique seasons for different crops and seasons
  • Use: This result can actually be obtained by different join queries on input tables but because of performance reasons (joining results of unique calculation units to the full 1 km grid) the result of these joins is stored in this support table used to fill table UNITS_CALC_INPUT
  • Type: Table
  • Remarks:

GRID-datasets

content
2.1 GRID_1KM
2.2 GRID_25KM
2.3 GRID_25KMJOBS




GRID_1KM

  • Description: The full grid
  • Use: Specifies the visualization grid and maps each grid cell to a soil, weather, season and set of crop coefficients.
  • Type: Table
  • Remarks: The resolution is equal to spot images which is around 1kmx1km. The table only contains land grid cells. At the moment the table also only contains grid cells for which a seasons could be derived (based on ndvi time series).


GRID_25KM

  • Description: Weather grid
  • Use: Specifies the weather grid.
  • Type: View
  • Remarks:


GRID_25KMJOBS

  • Description: 25 km grid list
  • Use: 25 km grid list to support parallel processing, 25 km grid cells are mapped to jobs
  • Type: Table
  • Remarks:

SOILS-datasets

content
3.1 SOILS_SMU
3.2 SOILS_STU
3.3 HW30S_FULL
3.4 HW30S_MAPUNIT



SOILS_SMU

  • Description: unique list of soil mapping units (soil associations)
  • Use: unique list of soil mapping units (soil associations)
  • Type: Table
  • Remarks:



SOILS_STU

  • Description: mapping between soil mapping unit (SMU) and soil type units (STU) and soil physical characteristics per soil type unit, averaged to a single layer.
  • Use: provides soil physical characteristics per soil type unit, averaged to a single layer
  • Type: Table
  • Remarks:



HW30S_FULL

  • Description: List of layer specific derived soil types given for all map units (soil associations) (full unmodified WISE30SEC_V_1_0 data)
  • Use: as background data (sBatjes, N.H., 2015. World soil property estimates for broad-scale modelling (WISE30sec, ver. 1.0). Report 2015/01, ISRIC—World Soil Information, Wageningen (available via: http://www.isric.org/data/datadownload)
  • Type: Table
  • Remarks:



HW30S_MAPUNIT

  • Description: full composition of each map unit in terms of its main soil units (FAO 1988), their relative extent, and the identifier for the corresponding synthetic soil profile, and climate class. The contents of this table can be joined to the spatial data using the NEWSUID field.
  • Use: To derive a full list of unique soil map units to fill SOILS_SMU
  • Type: Table
  • Remarks: -

other datasets

content
5.1 AREA
5.2 JOBS
5.3 SEASONS
5.4 SYSPARAMETERS
5.5 SYSTABLES
5.6 UNITS_CALC_INPUT
5.7 WEATHER_HRES_GRID_10



AREA

  • Description: support table to hold areas of each location across the latitude range for one longitude
  • Use: to fill areas in table GRID_1KM
  • Type: Table
  • Remarks:



JOBS

  • Description: List of jobs, all connected to a set of grid cells, where for each job the status of processing is registered
  • Use: Allow parallel calculation of GWSI by starting more than one GWSI application
  • Type: Table
  • Remarks:


SEASONS

  • Description: The unique combinations of phenology metric per season
  • Use: Input for the calculations
  • Type: Table
  • Remarks:


SYSPARAMETERS

  • Description: Includes configuration parameters
  • Use: To trigger and manage the WSI calculations
  • Type: Table
  • Remarks:


SYSTABLES

  • Description: Normally used for the configuration of internal IDs
  • Use: In this project only rarely used. In this project the configuration of internal IDs is organized in ORACLE sequences making the content not relevant. However the table must exist because certain components in the daemon by default check the existence
  • Type: Table
  • Remarks:


UNITS_CALC_INPUT

  • Description: list of unique calculation (simulation) units by defining unique combinations of soil mapping units and seasons per 25 km grid cell for the two generic crops
  • Use: List of units for which the WSI must be calculated
  • Type: Table
  • Remarks:


WEATHER_HRES_GRID_10

  • Description: Dekadal weather data (1989-present)
  • Use: input for WSI calculations
  • Type: View
  • Remarks: