Hi Mat
This is a copy of information from my metadata file on how I managed
to get different raster layers for the different data available in the
HWSD data set. (Hence all the file names in the brackets.) I'm not
quite sure from your description if it is what you need. I have
managed to get the soil data working in Maxent, R and ArcGIS by
following the steps below. I hope it helps.
Regards,
Michelle
Michelle Greve
Aarhus University
Department of Biological Science
Ny Munkegade Bygning 1540
DK-8000 Aarhus C
Denmark
Methods used:
The original .bil raster file was exported to a grid format
(hwsd_raster). The Access database was used to produce a query
containing the MU_Global, SU_Symbol and SU_Code columns. (The other
FAO parameters, such as SU_SYM74, which is the original, more detailed
FAO classification, were not available across the whole world or even
the whole of Africa, and were thus not used to construct the soil
map.) There are 36 different soil classes represented by the
‘SU_Symbol’, and SU_Code is a numerical code for the major soil group
(FAO90), used for the HWSD. This query was exported to a .dbf file
(HWSD_SMU_query.dbf), which was then joined to the original grid file
using the ‘Join’ function in ArcGIS. The join was conducted using the
‘Value’ column of hwsd_raster (which is a unique number for each grid
cell) and the MU_Global column of HWSD_SMU_query.dbf. The grid was
then exported, so that it contained the values from the query table as
attributes in the attribute table of the grid. This new grid with the
attributes was called hwsd_grd_join.
In order to change the ‘Value’ of the raster dataset from the original
unique raster cell values to soil characteristics, the Lookup function
in Spatial Analyst Toolbox was used. The above-mentioned procedure can
only be done using numerical characters, therefore SU_Code was used as
the lookup field. The raster that was produced was saved as
soilcode_hwsd. This file was a floating point table, and was therefore
converted to integer (as the SU_Symbols are categorical integers) in
the raster calculator, using the calculation int([soilcode_hwsd]). The
resulting grid was named hwsd_soil.
Therefore hwsd_soil is the final dataset (other files might be useful
if somebody wanted to extract other information from the dataset – I
have therefore placed the files that were used in the processing of
the data in the folder Edited/Files used in processing).
On Aug 31, 11:16 pm, "Peter Wilson" <
pwil...@bio.mq.edu.au> wrote:
> Mat,
>
> The HWSD contains a large number of soil attributes, including topsoil and subsoil sodium exchange capacity (related to salinity). Which one(s) are you trying to use? Many attributes are coded into a few classes and may need recoding to be used in MaxEnt or a GIS. Also, the classes are based on agronomically relevant tolerance limits.
>
> Also, all climate datasets are highly inter-correlated (i.e. have high levels of collinearity). This is particularly true for derived data like the Bioclim variables commonly used in species distribution modelling. The question of how high levels of collinearity affect MaxEnt is a matter of debate (see many posts to this list). Remember that MaxEnt does not need to invert the covariance or correlation matrix so, unlike a generalized linear model, you can still get a model even when very high levels of collinearity exist in the data. How stable and interpretable the model is is still a matter of debate.
>
> An alternate global climate dataset is available on-line from the Climate Research Unit (CRU), University of East Anglia. It is at 10 arc minute resolution and requires some pre-processing to import it into a GIS grid format as well as re-gridding to finer grids if that is needed. You will also have to generate the Bioclim variables if you need them.
>
> Peter Wilson
>
> ==========================================
> Dr Peter D. Wilson
> Postdoctoral Research Fellow
> Department of Biological Sciences
> Macquarie University, New South Wales, Australia 2109
> Email:
pwil...@bio.mq.edu.au
>
> >>> Mat Bond <
matjb...@hotmail.co.uk> 09/01/09 3:17 AM >>>