SPADE 1

The idea of incorporating profile data into the Soil Database was to extend the SGDBE data with quantitative data [whereas SGDBE attribute values are qualitative (e.g high, low, medium) and taken from a discrete set of predefined values]. Such quantitative data should allow better modeling. Two types of profile data are provided: estimated profiles and measured profiles.

Measured profile data come from geo-located profiles taken in the field, analyzed according to own (non-harmonized) procedures in order to fill in a specific measured-profile form (Proforma I .xls file [19Kb], according to specific instructions .doc file [934Kb]); ideally these measured profiles should correspond to an STU from the SGDBE.

Estimated profile data come from profiles that should be representative for a specific STU and have been estimated by experts in order to fill in a specific estimated-profile form (Proforma II .xls file [18Kb], according to specific instructions .doc file [934Kb]). The values that had to be reported in this form were subject to a kind of harmonization.

The database includes the following analytical results for the different soil horizons :

  • Texture (& particle size grades)
  • Organic matter content (C, N)
  • Structure
  • Total nitrogen content
  • pH
  • ESP or SAR
  • Calcium carbonate content
  • Calcium sulphate content
  • Electric conductivity
  • CEC and exchangeable bases
  • Soil water retention
  • Bulk density
  • Root depth
  • Groundwater level
  • Parent material

The result of the profile data collection and compilation are :

  • A set of spreadsheet documents that hold the measured profile data (Proforma I). Since the gathered data were quite heterogeneous, hardly any attempt has been made to harmonize the data which are delivered as received.
  • A table that holds the estimated profiles (Proforma II). An attempt has been made by the data provider or the data compiler to link each profile to an existing STU; however some profiles could not be linked. Note that estimated profiles are not geo-located.

A more in-depth discussion of the database can be found in SPADBE Metadata, also available as .doc file [118Kb], while SPADBE Dictionary, also available as .doc file [130Kb] explains the data structures (in the Arc/Info GIS software environment) and SPADBE Attricod, also available as .doc file [340Kb] provides a list of the reported attributes with their accepted values.

Go Back to