Each record in this table corresponds to either an intrinsic soil property or a soil interpretation that is available in the Soil Data Viewer application.  A record in this table is also referred to as an "SDV rule".  A rule provides most of the information necessary for the Soil Data Viewer application to be able to create a thematic map for the corresponding soil attribute.  Some additional information needed in order to be able to create a thematic map may be collected at run time.
The Component Canopy Cover table lists the overstory plants that typically occur on the referenced map unit component.
The Component Crop Yield table lists commonly grown crops and their expected range in yields when grown on the referenced map unit component.  Yields for the map unit as a whole are given in the Mapunit Crop Yield table.
The Component Diagnostic Features table lists the typical soil features, such as ochric epipedon or cambic horizon, for the referenced map unit component.
The Component Ecological Classification table identifies the ecological sites typically associated with the referenced map unit component.  These may include the official NRCS forestland and rangland ecological sites, as well as those of other classification systems, such as the USFS Habitat Types.
The Component Erosion Accelerated table lists the kinds of accelerated erosion that occur on the referenced map unit component.  One row in this table is marked as the representative kind of accelerated erosion for that component.
The Component Existing Plants table lists the plants, either rangeland or forestland plants, that typically occur on the referenced map unit component.
The Component Forest Productivity - Other table lists the site index and annual productivity of forest overstory tree species in units other than cubic feet per acre per year for trees that typically occur on the referenced map unit component.
The Component Forest Productivity table lists the site index and the annual productivity in cubic feet per acre per year (CAMI) of forest overstory tree species that typically occur on the referenced map unit component.
The Component Geomorphic Description table lists the geomorphic features on which the referenced map unit component typically occurs.
The Component Hydric Criteria table lists the hydric soil criteria met for those referenced map unit components that are classified as a "hydric soil."
The Component Interpretation table lists the predictions of behavior and limiting features for specified uses made for the referenced map unit component.
The Component Microrelief Surface Morphometry table lists microrelief features associated with the referenced geomorphic (microfeature) feature shown in the Component Geomorphic Description table.
The Component Month table lists the monthly flooding and ponding characteristics for the referenced map unit component.  This table has one row for each month of the year.
The Component Parent Material Group table lists the concatenated string of parent material(s) in which the referenced map unit component formed based on entries in the Component Parent Material table.  For example, a component formed in one parent material, such as loess, or one vertical sequence of parent materials, such as loamy glacial drift over silty residuum weathered from shale, has one row in this table.  A component formed in one parent material in some locations, but another parent material (or sequence of parent materials) in other locations has two rows in this table, one for each parent material (or sequence of parent materials).  One row is identified as the representative parent material.
The Component Parent Material table lists the individual parent material(s) for the referenced map unit component.    In some cases where soils developed in multiple materials in a vertical sequence, that sequence will be noted.  In other cases multiple entries with no vertical sequence noted indicates the soil may have formed in one of the materials listed.
The Component Potential Windbreak table lists the windbreak plant species commonly recommended for the referenced map unit component.  A windbreak plant listed in this table may be used alone or in combination with other plants.
The Component Restrictions table lists the root restrictive feature(s) or layer(s) for the referenced map unit component.  If the thickness of the restrictive layer is greater than zero (low=5, RV=8, high=10), the restrictive layer exists in all delineations of the map unit where the component occurs.  If the thickness of the restrictive layer includes zero (low=0, RV=2, high=5), the restrictive layer may exist in some delineations, but not in others.  This table will be empty if the component does not have restrictive features, but could have several rows if several restrictive features occur in the soil.
The Component Slope Shape Surface Morphometry table lists the geomorphic shape(s) of the referenced map unit component, in slope shape terms.  The slope shape terms listed in this table apply to the referenced geomorphic feature shown in the Component Geomorphic Description table.
The Component Soil Moisture table describes the typical soil moisture profile for the referenced map unit component during the month referenced in the Component Month table.  The soil moisture profiles for each month, taken as a group of twelve months, describe the representative situation for the component throughout the year.
The Component Soil Temperature table describes the typical soil temperature profile for the referenced map unit component during the month referenced in the Component Month table.  The soil temperature profiles for each month, taken as a group of twelve months, describe the representative situation for the component throughout the year.
The Component Surface Fragments table lists the organic or mineral fragments that generally occur on the surface of the referenced map unit component.  If the cover percent is greater than zero (low=0.1, RV=1, high=3) for a row in this table, the fragment is in every delineation of the map unit where the referenced component occurs.  If the Cover % includes zero (low=0, RV=0.01, high=1) for a row in this table, the fragment may exist in some delineations and not in others.
The Component table lists the map unit components identified in the referenced map unit, and selected properties of each component.  If the Component % is greater than zero (low=65, RV=75, high=90) for a component, that component exists in every delineation of that mapunit.  If the Component % includes zero (low=0, RV=50, high=90), the component may exist in some delineations, but not in others.
The Component Taxonomic Family Mineralogy table lists the mineralogy characteristics, as defined in Soil Taxonomy, that apply to the referenced map unit component.
The Component Taxonomic Family Other Criteria table lists the other taxonomic characteristics, such as classes of coatings or permanent cracks, as defined in Soil Taxonomy, that apply to the referenced map unit component.  The characteristics listed in this table describe the representative situation for the component.
The Component Taxonomic Moisture Class table provides clear identification of the intended taxonomic moisture class, as defined in Soil Taxonomy, that apply to the referenced map unit component, even though moisture class is implied at a higher taxonomic level.  The class or classes listed in this table describe the representative situation for the component.
The Component Text table contains notes and narrative descriptions for the referenced map unit component.  In many cases, the table will be empty for a particular component.
The Component Three Dimensional Surface Morphometry table lists the typical geomorphic position (s) of the referenced map unit component, in three dimension terms.  The geomorphic position(s) listed in this table apply to the geomorphic feature referenced in the Component Geomorphic Description table.
The Component Trees To Manage table lists the trees commonly recommended for managing on the referenced map unit component.
The Component Two Dimensional Surface Morphometry table lists the geomorphic position(s) of the referenced map unit component, in two dimensional hillslope profile terms.  The geomorphic position(s) listed in this table apply to the geomorphic feature referenced  in the Component Geomorphic Description table.
The Distribution Interp Metadata table records the set of NASIS fuzzy logic interpretations which were generated for the map unit components included in a set of distribution data.
The Distribution Legend Metadata table records information about the legends or soil survey areas selected for inclusion in a set of distributed data.  The presence of a legend in this table does not imply that all of the available data for that legend was included in the set of data that was distributed.  Only certain map units and components for that legend may have been selected.  The record of the criteria used for selecting map units and components may be found in the Distribution Metadata table.
The Distribution Metadata table records information associated with the selection of a set of data for distribution to some entity or information system external to NASIS.  A set of distribution data may include only selected map units from a legend or legends, and only selected components of those map units.  This table records the criteria used for selecting map units and components for inclusion in the set of distributed data.  Other recorded information includes the name of the NASIS user who initiated a distribution request, and the times when that request was made, and when that request was ultimately processed.
The Domain Detail Static Metadata table records the individual domain members for all domains associated with the tabular data set.  Each record in this table represents one member of a particular domain.
The Domain Master Static Metadata table records the metadata that pertains to a domain as a whole, for all domains associated with the tabular data set.  A domain is a fixed set of choices to which a column's value is restricted.  Each column in the Table Column Static Metadata table whose logical data type is "choice", has a corresponding domain.  Each record in this table represents a particular domain.  A particular domain may serve as the domain for more than one column.  Information about the members that make up a particular domain is found in the Domain Detail Static Metadata table.
The Horizon AASHTO table contains the American Association of State Highway Transportation Officials classification(s) for the referenced horizon.  One row in this table is marked as the representative AASHTO classification for the horizon.
The Horizon Consistence table contains descriptive terms of soil consistence -- rupture resistance, plasticity, and stickiness -- for the referenced horizon.  One row in this table is marked as having the representative characteristics for the horizon.
The Horizon Designation Suffix table contains the designation suffix(es), one per row,  for the referenced horizon.  For example, the "h" and "s" of a Bhs horizon appear as two rows in this table.
The Horizon Fragments table lists the mineral and organic fragments that generally occur in the referenced horizon.  If the Volume % is greater than zero (low=5, RV=10, high=15) in a row, the kind and size of fragment in that row exists everywhere this horizon and component occur in the map unit.  If the Volume % includes zero (low=0, RV=5, high=10), the kind and size of fragment may exist in some places, but not in others.
The Horizon Pores table lists the voids for the referenced horizon.  If the Quantity is greater than zero (low=2, RV=5, high=10) in a row, the voids in that row exist everywhere the horizon and component occur in the map unit.  If the Quantity includes zero (low=0, RV=2, high=5), the voids may exist in some places, but not in others.  More than one row can be marked as an RV row because a horizon may have more than one size or shape of void.
The Horizon Structure Group table lists the ranges of  soil structure for the referenced horizon.  The row with the typically occurring structure is marked as being representative.  The entry in this table is based on grouping of entries in the Horizon Structure table.
The Horizon Structure table lists the individual soil structure size, grade, and shape terms for the referenced horizon.  Terms in this table are assembled into a structure group string which is recorded in the Horizon Structure Group table.
The Horizon table lists the horizon(s) and related data for the referenced map unit component.  If the horizon thickness is greater than zero (low=5, RV=8, high=12), the horizon exists everywhere this component occurs.  If the horizon thickness includes zero (low=0, RV=1, high=3), the horizon may exist in some places, but not in other places.
Horizons that have two distinct parts, such as E/B or E&Bt horizons, are recorded twice.  Once for the characteristics of the first part; and again on another row, using the same depths and thicknesses, for the characteristics of the other part.
The Horizon Text table contains notes and narrative descriptions related to the referenced horizon.  Some notes may provide additional information about the horizon for which there is no explicit column for such data.  In many cases, the table is empty for a particular horizon.
The Horizon Texture Group table lists the range of textures for the referenced horizon as a concatenation of horizon texture and texture modifier(s).  For example, a horizon that is gravelly loamy sand in some places and gravelly loamy coarse sand in other places is shown as GR-LS on one row and GR-LCOS on another row in this table.  The row with the typically occurring texture is identified as the RV row.  Stratified textures are shown in one row.  For example, a horizon that is stratified gravelly loamy fine sand and cobbly coarse sand is shown as SR- GR-LFS CB-COS on one row and the Stratified? column for that row is marked "yes".  If two or more textures always occur together but are not stratified, all of the textures are listed on one row and the Stratified? column for that row is marked "no".
The Horizon Texture Modifier table lists the texture modifier(s) for the referenced texture.  For example, a gravelly loamy sand is shown as "GR-LS" in the Horizon Texture Group table, "ls" in the Horizon Texture table, and "gr" in this table.
The Horizon Texture table lists the individual texture(s), or term(s) used in lieu of texture, for the referenced horizon.  Only the unmodified texture terms are listed in the Horizon Texture table; modifiers are listed in the Horizon Texture Modifier table.  For example, a gravelly loamy sand is shown as "GR-LS" in the Horizon Texture Group table, "ls" in the Horizon Texture table, and "gr" in the Horizon Texture Modifier table.
The Horizon Unified table contains the Unified Soil Classification(s) for the referenced horizon.  One row in the Horizon Unified table is marked as the representative Unified classification for the horizon.
The Index Detail Static Metadata table records what columns of a table make up a particular index.  Each record in this table represents one column of a particular index.
The Index Master Static Metadata table records the metadata that pertains to an index, as a whole, for all indexes defined for the tabular data set.  Each record in this table represents one index for a particular table.  An index is based on one or more columns from a particular table.  Information about the columns that make up an index is found in the Index Detail Static Metadata table.
The Legend Area Overlap table lists the geographic areas that are coincident with the soil survey area identified in the Legend table.  For example, a survey area that covers two counties would have two rows in this table, one for each county.  Other types of geographic areas listed might include state, MLRA, rainfall (R) factor area, climate (C) factor area, etc.
The Legend table identifies the soil survey area that the legend is related to, and related information about that legend.
The Legend Text table contains notes and narrative descriptions related to the referenced legend.  Legend text is optional.  In many cases, this table is empty.
The Mapunit Aggregated Attribute table records a variety of soil attributes and interpretations that have been aggregated from the component level to a single value at the map unit level. They have been aggregated by one or more appropriate means in order to express a consolidated value or interpretation for the map unit as a whole.
The Mapunit Area Overlap table lists the map units that exist in the overlap between the entire soil survey area and the referenced geographic area in the Legend Area Overlap table.
The Mapunit Crop Yield table lists commonly grown crops and their expected yields for the referenced map unit as a whole.  Yields for individual map unit components are given in the Component Crop Yield table.
The Mapunit table identifies the map units included in the referenced legend.  Data related the map unit as a whole are also given.
The Mapunit Text table contains notes and narrative descriptions related to the referenced map unit.
The records in this table represent the folders and subfolders by which soil attributes (SDV rules) are grouped and displayed in the Soil Data Viewer application.  One record in this table may be related to another record in this table, i.e. a subfolder must identify its corresponding parent folder.
The Relationship Detail Static Metadata table records the pairs of join columns that define a particular relationship.  Each record in this table represents one pair of join columns for a particular relationship.
The Relationship Master Static Metadata table records the metadata that pertains to a relationship, as a whole, for all relationships defined for the tabular data set.  Each record in this table represents one particular relationship between two related tables.  A relationship involves one or more pairs of join columns, and more than one relationship may exist between the same two tables.  Information about the join columns involved in a relationship is found in the Relationship Detail Static Metadata table.
The Table Column Static Metadata table records the metadata for all columns of all tables that make up the tabular data set.  Each record in this table represents one column of a particular table.
The Table Static Metadata table records metadata about the tables that make up the tabular data set.  Each record in this table represents one table.
This associative table resolves the many to many relationship between Soil Data Viewer folders and soil attributes (SDV rules).
This is a lookup table for months of the year.
This lookup table records the valid algorithms for aggregating soil property values or soil interpretation results to the map unit level.
This table records all of the soil map units of a soil survey area that are represented as one or more lines.  This table is not like other tabular data tables that are delivered as ASCII delimited files.  How the information is delivered depends on the spatial format that was requested at the time the corresponding soil survey area was exported.  Spatial information is typically delivered in GIS vendor specific format, and more than one output file may be produced when the information for this spatial entity is exported.  Consequently, no spatially oriented columns are shown, because the name and number of columns necessary to portray spatial characteristics vary depending on spatial format.

This table is documented in order to show attributes that will always be available when working with the corresponding spatial entity in a GIS.  These attributes have two purposes.  One purpose is to identify each instance of the corresponding spatial entity.  The other purpose is to identify each instance of the corresponding tabular entity.  The tabular entity corresponding to a map unit line is represented by a record in the Map Unit table.
This table records all of the soil map units of a soil survey area that are represented as one or more points.  This table is not like other tabular data tables that are delivered as ASCII delimited files.  How the information is delivered depends on the spatial format that was requested at the time the corresponding soil survey area was exported.  Spatial information is typically delivered in GIS vendor specific format, and more than one output file may be produced when the information for this spatial entity is exported.  Consequently, no spatially oriented columns are shown, because the name and number of columns necessary to portray spatial characteristics vary depending on spatial format.

This table is documented in order to show attributes that will always be available when working with the corresponding spatial entity in a GIS.  These attributes have two purposes.  One purpose is to identify each instance of the corresponding spatial entity.  The other purpose is to identify each instance of the corresponding tabular entity.  The tabular entity corresponding to a map unit point is represented by a record in the Map Unit table.
This table records all of the soil map units of a soil survey area that are represented as one or more polygons.  This table is not like other tabular data tables that are delivered as ASCII delimited files.  How the information is delivered depends on the spatial format that was requested at the time the corresponding soil survey area was exported.  Spatial information is typically delivered in GIS vendor specific format, and more than one output file may be produced when the information for this spatial entity is exported.  Consequently, no spatially oriented columns are shown, because the name and number of columns necessary to portray spatial characteristics vary depending on spatial format.

This table is documented in order to show attributes that will always be available when working with the corresponding spatial entity in a GIS.  These attributes have two purposes.  One purpose is to identify each instance of the corresponding spatial entity.  The other purpose is to identify each instance of the corresponding tabular entity.  The tabular entity corresponding to a map unit polygon is represented by a record in the Map Unit table.
This table records all of the spot features of a soil survey area that are represented as one or more lines.  This table is not like other tabular data tables that are delivered as ASCII delimited files.  How the information is delivered depends on the spatial format that was requested at the time the corresponding soil survey area was exported.  Spatial information is typically delivered in GIS vendor specific format, and more than one output file may be produced when the information for this spatial entity is exported.  Consequently, no spatially oriented columns are shown, because the name and number of columns necessary to portray spatial characteristics vary depending on spatial format.

This table is documented in order to show attributes that will always be available when working with the corresponding spatial entity in a GIS.  These attributes have two purposes.  One purpose is to identify each instance of the corresponding spatial entity.  The other purpose is to identify each instance of the corresponding tabular entity.  The tabular entity corresponding to a spot feature line is represented by a record in the Feature Description table.
This table records all of the spot features of a soil survey area that are represented as one or more points.  This table is not like other tabular data tables that are delivered as ASCII delimited files.  How the information is delivered depends on the spatial format that was requested at the time the corresponding soil survey area was exported.  Spatial information is typically delivered in GIS vendor specific format, and more than one output file may be produced when the information for this spatial entity is exported.  Consequently, no spatially oriented columns are shown, because the name and number of columns necessary to portray spatial characteristics vary depending on spatial format.

This table is documented in order to show attributes that will always be available when working with the corresponding spatial entity in a GIS.  These attributes have two purposes.  One purpose is to identify each instance of the corresponding spatial entity.  The other purpose is to identify each instance of the corresponding tabular entity.  The tabular entity corresponding to a spot feature point is represented by a record in the Feature Description table.
This table records information about the soil interpretations that were generated for a soil survey area.
This table records the description of all spot features that occur in a soil survey area.
This table records the primary dynamic cetadata associated with a soil survey area.  This includes such things as survey area version, tabular data version, etc. The remaining dynamic metadata, which soil interpretations were generated for the corresponding soil survey area, is recorded in the Survey Area Interpretation table.
This table records the set of polygons that make up a soil survey area boundary.  The table is not like other tabular data tables that are delivered as ASCII delimited files.  How the information in this table is delivered depends of the spatial format that was requested at the time the corresponding soil survey area data was exported.  Spatial information is typically delivered in GIS vendor specific format, and more than one output file may be produced when the information for this spatial entity is exported.  Consequently, no spatially oriented columns are shown, because the name and number of columns necessary to portray spatial characteristics vary depending on spatial format.

This table is documented in order to show attributes that will always be available when working with the corresponding spatial entity in a GIS.  These attributes have two purposes.  One purpose is to identify each instance of the corresponding spatial entity.  The other purpose is to identify each instance of the corresponding tabular entity.  The tabular entity corresponding to the survey area boundary is represented by a record in the Legend table.