gSSURGO Ready2map NE FY2013
This dataset contains the common Map Unit attributes for each polygon within the gSSURGO database plus NRCS derived attributes from a data summary table called the National Valu Added Look Up (valu) Table #1. It is comprised of 57 pre-summarized or “ready to map” derived soil survey geographic database attributes including soil organic carbon, available water storage, crop productivity indices, crop root zone depths, available water storage within crop root zone depths, drought vulnerable soil landscapes, and potential wetland soil landscapes. Related metadata values for themes are included. These attribute data are pre-summarized to the map unit level using best practice generalization methods intended to meet the needs of most users. The generalization methods include map unit component weighted averages and percent of the map unit meeting a given criteria. These themes were prepared to better meet the mapping needs of users of soil survey information and can be used with both SSURGO and Gridded SSURGO (gSSURGO) datasets. Gridded SSURGO (gSSURGO) Database is derived from the official Soil Survey Geographic (SSURGO) Database. SSURGO is generally the most detailed level of soil geographic data developed by the National Cooperative Soil Survey (NCSS) in accordance with NCSS mapping standards. The tabular data represent the soil attributes, and are derived from properties and characteristics stored in the National Soil Information System (NASIS). The gSSURGO data were prepared by merging traditional SSURGO digital vector map and tabular data into State-wide extents, and adding a State-wide gridded map layer derived from the vector, plus a new value added look up (valu) table containing “ready to map” attributes. The gridded map layer is offered in an ArcGIS file geodatabase raster format. The raster and vector map data have a State-wide extent. The raster map data have a 10 meter cell size that approximates the vector polygons in an Albers Equal Area projection. Each cell (and polygon) is linked to a map unit identifier called the map unit key. A unique map unit key is used to link to raster cells and polygons to attribute tables, including the new value added look up (valu) table that contains additional derived data.VALU Table Content:The map unit average Soil Organic Carbon (SOC) values are given in units of g C per square meter for eleven standard layer or zone depths. The average thickness of soil map unit component horizons used in these layer/zone calcuations is also included. The standard layers include: 0-5cm, 5-20cm, 20-50cm, 50-100cm, 100-150cm, and 150-150+cm (maximum reported soil depth). The standard zones include: 0-5cm (also a standard layer), o-20cm, 0-30cm, 0-100cm, and 0-150+cm (full reported soil depth). Zero cm represents the soil surface.The map unit average Available Water Storage (AWS) values are given in units of millimeters for eleven standard layer or zone depths. The average thickness of soil map unit component horizons used in these layer/zone calcuations is also included. The standard layers include: 0-5cm, 5-20cm, 20-50cm, 50-100cm, 100-150cm, and 150-150+cm (maximum reported soil depth). The standard zones include: 0-5cm (also a standard layer), 0-20cm, 0-30cm, 0-100cm, and 0-150+cm (full reported soil depth). Zero cm represents the soil surface.The map unit average National Commodity Crop Productivity Index (NCCPI) values (low index values indicate low productivity and high index values indicate high productivity) are provided for major earthy components. NCCPI values are included for corn/soybeans, small grains, and cotton crops. Of these crops, the highest overall NCCPI value is also identified. Earthy components are those soil series or higher level taxa components that can support crop growth. Major components are those soil components where the majorcompflag = ‘Yes’ in the SSURGO component table. A map unit percent composition for earthy major components is provided. See Dobos, R. R., H. R. Sinclair, Jr, and M. P. Robotham. 2012. National Commodity Crop Productivity Index (NCCPI) User Guide, Version 2. USDA-NRCS. Available at: ftp://ftp-fc.sc.egov.usda.gov/NSSC/NCCPI/NCCPI_user_guide.pdfThe map unit average root zone depth values for commodity crops are given in centimeters for major earthy components. Criteria for root-limiting soil depth include: presence of hard bedrock, soft bedrock, a fragipan, a duripan, sulfuric material, a dense layer, a layer having a pH of less than 3.5, or a layer having an electrical conductivity of more than 12 within the component soil profile. If no root-restricting zone is identified, a depth of 150 cm is used to approximate the root zone depth (Dobos et al., 2012). The map unit average available water storage within the root zone depth for major earthy components value is given in millimeters.Drought vulnerable soil landscapes comprise those map units that have available water storage within the root zone for commodity crops that is less than or equal to 6 inches (152 mm) expressed as “1” for a drought vulnerable soil landscape map unit or “0” for a nondroughty soil landscape map unit or NULL for miscellaneous areas (includes water bodies).The potential wetland soil landscapes (PWSL version 1) information is given as the percentage of the map unit (all components) that meet the criteria for a potential wetland soil landscape. See table column (field) description for criteria details. If water was determined to account for 80 or greater percent of a map unit, a value of 999 was used to indicate a water body. This is not a perfect solution, but is helpful to identifying a general water body class for mapping.The map unit sum of the component percentage representative values is also provided as useful metadata. For all valu table columns, NULL values are presented where data are incomplete or not available. How NoData or NULL values and incomplete data were handled during VALU table SOC and AWS calculations:The gSSURGO calculations for SOC and AWS as reported in the VALU table use the following data checking and summarization rules. The guiding principle was to only use the official data in the SSURGO database, and not to make assumptions in case there were some data entry errors. However, there were a few exceptions to this principle if there was a good reason for a Null value in a critical variable, or to accommodate the data coding conventions used in some soil surveys.Horizon depths considerations:If the depth to the top of the surface horizon was missing, but otherwise the horizon depths were all okay, then the depth to the top of the surface horizon (hzdept_r) was set to zero.If the depth to the bottom of the last horizon was missing, and the horizon represented bedrock or had missing bulk density, the depth to the bottom was set to equal to the depth to the top of the same horizon (hzdepb_r = hzdept_r), effectively giving the horizon zero thickness (and thus zero SOC or AWS), but not blocking calculation of other horizons in the profile due to horizon depth errors.Other types of horizon depth errors were considered uncorrectable, and led to all horizon depths for the component being set to a NoData value, effectively eliminating the component from the analysis. The errors included gaps or overlaps in the horizon depths of the soil profile, other cases of missing data for horizon depths, including missing data for the bottom depth of the last horizon if the soil texture information did not indicate bedrock and a bulk density value was coded. The SOC or AWS values were effectively set to zero for components eliminated in this way, so the values at the map unit level could be an underestimate for some soils.Horizon rock fragment considerations:Part of the algorithm for calculating the SOC requires finding the volume of soil that is not rock. This requires three SSURGO variables that indicate rock fragments (fraggt10_r, frag3to10_r, and sieveno10_r). If the soil is not organic, and any of these are missing, then the ratio of the volume of soil fines to the total soil volume was set to “NoData”, and the SOC results were coded as “NoData” and effectively set to zero for the horizon. If the soil is organic, then it may be logical that no measurement of rock fragments was made, and default values for the “zero rock” situation was assumed for these variables (i.e., fraggt10_r = 0, frag3to10_r = 0, sieveno10_r = 100). Organic soils were identified by an “O” in the horizon designator or the texture code represented “Peat”, “Muck” or “Decomposed Plant Material”. If all three of the fragment variables were present, but indicated more than 100% rock, then 100% rock was assumed (zero volume of soil and thus zero for SOC). The rock fragment variables do not influence the AWS calculation because rock content is already accounted for in the available water capacity (awc_r) variable at the horizon level.Horizon to component summary:To summarize data from the horizon level to the component level, the evaluation proceeded downward from the surface. If a valid value for AWS could not be calculated for any horizon, then the result for that horizon and all deeper horizons was set to NoData. The same rule was separately applied to the SOC calculation, so it was possible to have results for SOC but not AWS, or vice versa.Component to mapunit summary:To summarize data from the component level to the map unit level, the component percentages must be valid. There are tests both of the individual component percentage (comppct_r) data, and also of the sum of the component percentages at the map unit level (mu_sum_comppct_r). For the gSSURGO VALU table, the following rules were applied for the individual components: 1) The comppct_r must be in the range from 0 to 100, inclusive. 2) Individual components with a comppct_r that was Null (nothing coded) were ignored. A zero comppct_r value excludes the component from having an effect on the map unit calculation. No values more than 100% were found in the data for individual comppct_r.Two additional rules were applied for the sum of the component percentages in a map unit (ignoring NoData for comppct_r): 3) The mu_sum_comppct_r must be in the range from 1 to 100, inclusive, otherwise map unit level output was set to NoData, and 4) The mu_sum_comppct_r were not scaled to equal 100%. With these rules, the results may be an under-estimate of the value for AWS or SOC compared to what would have been calculated if there were complete data and/or no comppct_r errors.Metadata variables: sums of component percentages:Several metadata variables are provided in the VALU table to help understand when the AWS and SOC values are underestimated because of these component percentage issues. The sum of the component percentages for the map unit are reported in “mu_sum_comppct_r”. If this is greater than 100% or the comppct_r was NoData for all components, then no results will be given for the map unit. If the mu_sum_comppct_r is less than 100%, then the soil scientists likely did not report on all soils in the map unit. The AWS and SOC values will only reflect the reported soils, and therefore would be an underestimate if the unreported soils would have had values for these measures.The sums of the component percentages that were used in the AWS and SOC calculations are also reported (mu_sum_comppct_aws and mu_sum_comppct_soc, respectively). If these values are less than the mu_sum_comppct_r, it is an indication that there was insufficient data to compute the AWS and/or SOC values for all of the components. These variables essentially represent metadata for each map unit. In some cases, the lack of an AWS or SOC value may be appropriate (for example, for non-soils such as bedrock at the surface, gravel pits, or water).A full discussion of these rules and their implications, including explicit examples, will be given in a forthcoming publication as Soil Survey Investigations Report No. 53, USDA NRCS, Lincoln, NE.
[Keywords: SSURGO Geospatial Data Gateway soils vector GDG Soil Survey gSSURGO farming environment ]