NSSH Part 639
National Soil Information System
(NASIS)
Definition and Purpose
(639.00)
The National Soil Information System integrates soil survey
information, operations, and management. It divides soil survey data
into four major categories: 1) map unit records, 2) geographic area
records, 3) point characteristics, and 4) standards, criteria, and
guidelines. The system also includes ancillary tools, functions, and
records to assure the security, integrity, and utility of the soil
survey data.
Policy and Responsibility (639.01)
The National Soil Information System (NASIS) is the official
depository for the latest soil survey information. Official changes are
maintained by the MLRA office. Distribution of information is through
this official file. A file of all nationwide data is stored at Iowa
State University Statistical Laboratory.
Map Unit Records (639.02)
Map unit records include soil survey area legends, map units, and the
physical, chemical, and morphological properties and interpretations for
map units and their components. Map unit records are subdivided into
three parts: the legend object, the data mapunit object,
and the map unit record text.
The National Soil Information System (NASIS) introduces some new
terminology to soil survey. The phrases "legend mapunit" and "data
mapunit" are invented terms for concepts to describe data relationships.
The term "legend mapunit" has now been shortened to "legend". An object
is either a record or a collection of records. Within NASIS the
legend object contains the map unit symbol, map unit name, kind of
map unit (consociation, complex, etc.), and correlation notes. The
identification used for the legend is the map unit symbol that is
common to the soil survey map and the soil survey legend. The data
mapunit object includes the map unit composition, physical,
chemical, morphological, and interpretation records for a map unit and
its components. The identification used for the data mapunit is a
system assigned unique number that is used only in the database to
identify a set of map unit attributes. The map unit record text
contains additional notes, nontechnical descriptions, and other
documentation related to either the legend or the data mapunit
and is a part of the records of either the legend object or the
data mapunit object.
(a) The Legend Object
The purpose of the legend object is to maintain map unit
symbol, name, and correlation records for each map unit in the legend
and provide a link to both areas and data mapunits. It provides a
continuous record of legend development and correlation decisions made
throughout the survey. These records are used to create the map unit
identification legend, conversion legends, and correlation status
reports for the survey area. The legend object is created at the
beginning of the survey and retained as part of the historical records.
The legend object includes several tables in the National Soil
Information System. Responsibility and ownership of a specific legend is
indicated by the database and group columns in the legend table.
Authority to edit the legend object is limited to users who are
members of the group that is responsible for the legend. The user who
creates or changes any part of the legend object is recorded in
the legend table, as well as the date and time of that change.
Generally, the legend in an on-going survey is the responsibility of the
soil survey project office. Responsibility is transferred to the MLRA
office at completion of the survey.
The tables in the legend object are defined below.
Descriptions for legend object data elements are available in the
National Soil Information System on-line help. Some data elements are
restricted to specific entries, others allow any appropriate entry.
(1) Legend table: legend description
(i) Definition. The legend description is the name of
a short text field used to describe a particular soil survey area
legend. Survey areas typically have two legends, a detailed soil map
legend and a general soil map legend. Some survey areas have a field
legend and a final publication legend.
(ii) Entry. Enter an appropriate description for the legend
such as "detailed soil map legend". Operational status for the survey
area legend, whether published or out-of-date, is recorded in the
legend table as survey status.
(2) Mapunit table: mapunit symbol
(i) Definition. The mapunit symbol is the name of the
field used for a soil map unit symbol. The mapunit symbol
uniquely identifies the soil map unit in the soil survey. It is
alphabetic (AcA), numeric (54), or alphanumeric (129B). Once a map
unit symbol has been used in the survey area legend, it is permanently
recorded in the mapunit table and on original soil maps so that
a conversion legend may be produced and original field work accurately
reproduced. A soil map unit symbol in the mapunit symbol field
of the legend object is linked to the data mapunit object
through the correlation table. Consequently, different soil map
unit symbols in either the same or different legends can be linked to
the same data within the data mapunit object providing
the capability to create conversion legends, join map units between
survey areas, and coordinate MLRA or statewide legends.
(3) Mapunit table: mapunit status
(i) Definition. Mapunit status is the name of a field
for specific terms that identify the current status of the map unit.
(ii) Classes and Definitions.
Provisional - A provisional soil map unit is a map unit
used in the soil survey that has not been officially approved for
use. Typically, a provisional map unit is either approved for use at
the next progress field review and changed to approved status, or is
disapproved, changed to additional status, correlated with another
map unit, and maintained in the map unit table.
Approved - An approved soil map unit is a map unit on the
current, signed review report for the survey area. Typically, a map
unit is approved at a progress field review after sufficient field
investigation indicates a need for the map unit. In some cases, an
approved map unit will not be retained on the active legend, but
changed to additional status, correlated with another map unit, and
maintained in the map unit table.
Correlated - A correlated soil map unit is a map unit on
the signed final correlation document.
Additional - An additional soil map unit is a map unit
that has been used in the soil survey area, but that has been
combined with another unit in the survey.
(iii) Entry. Enter the appropriate status class for each map
unit.
(4) Correlation table: representative DMU
(i) Definition. A representative DMU indicates whether or
not data in the particular data mapunit (DMU) is representative
for a particular map unit. Map unit symbols may be linked to more than
one data mapunit in the correlation table, but only one of the
data mapunits is representative for the map unit.
(ii) Classes and Definitions.
Yes - Indicates the representative data mapunit.
No - Indicates non-representative links to other data
mapunits which generally represent correlation of additional
symbols.
(iii) Entry. Enter the appropriate class term.
(5) Correlation table: mapunit constituent acres
(i) Definition. Mapunit constituent acres is the
portion of a data mapunit that is linked to a map unit as a
part or as a whole of that map unit. Acres recorded for
non-representative data mapunits are acres mapped for the
additional map unit symbol and data mapunit intersection. Acres
recorded for the representative data mapunit are acres for the
current map unit symbol. The sum of constituent acres is the total
acreage of the correlated map unit.
(6) Mapunit history table: mapunit history date
(i) Definition. Mapunit history date is the date of a
name or status change for a particular map unit.
(7) Mapunit history table: mapunit name historical
(i) Definition. Mapunit name historical is a name
that was previously used for the soil map unit. This entry provides
documentation of each name change for the map unit.
(8) Mapunit history table: mapunit status historical
(i) Definition. Mapunit status historical is a map
unit status term used to describe a previous status for the soil map
unit from the time it was added to the soil survey legend. This entry
provides documentation of each status change for the map unit. The
classes used are the same as those used for mapunit status.
(9) Legend area overlap table: area overlap acres
(i) Definition. Area overlap acres is the portion of
the geographic overlap of the soil survey area and another geographic
area. Typically, an area overlap is recorded for each county, MLRA,
Climate factor area, and Rainfall factor area in the survey area even
if acreages are not entered.
(10) Mapunit area overlap table: area overlap acres
(i) Definition. For this table, area overlap acres is
the portion of the map unit in a particular geographic area.
Typically, the occurrence of a map unit in a geographic area is
recorded even if acreages are not entered. Acreages are entered for
map units in each county in the survey area.
(b) The Data Mapunit Object
The data mapunit object is a record or a collection of records
concerning composition, physical, chemical, morphological, and
interpretation properties and performance for a map unit and each of its
components. A data mapunit object is a set of data records and as
such is not related to any geographic area or map unit delineation
unless linked to a delineated area in a soil survey area legend. These
records are used to document map unit characteristics and create reports
of soil properties and interpretations. Data mapunit objects are
created as needed and retained as part of the historical records.
The data mapunit object includes several tables in the
National Soil Information System. Ownership of a specific data
mapunit object is indicated by NASIS site and group columns in the
data mapunit table. Authority to edit the data mapunit object
is limited to users who are members of the group that is responsible for
the data mapunit. The user who creates or changes any part of the
data mapunit object is recorded in the data mapunit table,
as well as the date and time of that change. Generally, responsibility
for data mapunits that were created by users at the soil survey
project office is transferred to the MLRA office at the completion of
the soil survey.
Descriptions for data mapunit object data elements are
available in the National Soil Information System on-line help. Some
data elements are restricted to specific entries, others allow any
appropriate entry.
(1) Data mapunit table: data mapunit description
(i) Definition. Data mapunit description is a short
text field used to identify a data mapunit. A connotative
alphabetic or numeric text such as "Tunbridge complex, steep", "NE611,
27B", or "609005" is used. A data mapunit description is not
required but is useful to identify the intended meaning of the data
mapunit. Data mapunits may be linked to several map units
in different soil survey area legends. Consequently, the data
mapunit description does not uniquely identify the data mapunit.
Linkages through the correlation table accurately identify the map
unit names and symbols associated with the data mapunit.
(2) Data mapunit table: data mapunit ID
(i) Definition. Data mapunit ID is a unique number to
identify the set of records within the data mapunit object. The
number is non-connotative and used for linking data with geographic
areas.
(c) Map Unit Record Text
The purpose of map unit record text is to maintain additional
notes, nontechnical descriptions, and other documentation related to
horizons, components, data mapunits, map units, correlation
decisions, and legends. This text is used to document decisions and
create reports.
Map unit record text is part of either a legend object
or data mapunit object. Ownership and authority is determined by
the object to which it is attached.
Descriptions of text data elements are available in the National Soil
Information System on-line help. Some data elements are restricted to
specific terms, others allow any appropriate entry. A text entry is
identified by its kind, category, and subcategory. The table data
elements are described below:
(1) Any of the text tables: text kind
(i) Definition. Text kind is a specific term that
describes the kind of text. It is the highest division of text
classification.
(ii) Classes and Definitions.
Correlation notes - Correlation notes is a class name for
text entries related to correlation decisions. Typically correlation
notes are used in the legend text table or the map unit history text
table.
Nontechnical description - Nontechnical description is a
class name for text entries related to non technical descriptions.
Typically nontechnical descriptions are used in the map unit text
table.
S5 description - S5 description is a class name for text
related to components of data mapunits, specifically
accommodating conversion from previous systems. Typically S5
descriptions are used in the component text table.
Miscellaneous notes - Miscellaneous notes is a class name
for text not in any other specific kind. Miscellaneous notes are
used in any text table.
(iii) Entry. Enter the appropriate class name.
(2) Any of the text tables: text category
(i) Definition. Text category is any appropriate term
necessary to subdivide the kind of text. Typically used with non
technical descriptions in the map unit text table to identify the
category of non technical description. Examples are "SOI" or "soil"
for the soil paragraph, and "AGR" or "crop" for the agricultural
cropland paragraph.
(3) Any of the text tables: text subcategory
(i) Definition. Text subcategory is Any appropriate
term necessary to subdivide the kind and category of text.
(4) Any of the text tables: text
(i) Definition. Text is the actual narrative portion
of a text entry. The system displays the expression "Text..." to
indicate that text is contained in a separate text edit window that is
activated from this column. Text volume is nearly unlimited.
Geographic Area Records (639.03)
Geographic area records include symbols, names, and acreages for soil
survey areas as well as other political and physiographic areas.
Geographic area records are maintained in the area type object.
(a) The Area Type Object
The purpose of the area type object is to maintain soil
survey, political, and physiographic area records. The area type
object provides a complete list of approved soil survey areas and
standard acreages for official soil survey areas, states, counties, and
Major Land Resource Areas. These records are used in soil survey
operations management. An area type object is created as
necessary and retained as part of the historical records.
The area type object includes the area type, area, and area
text tables in the National Soil Information System. Responsibility for
a specific area type object is indicated by the database and
group columns in the area type table. Authority to edit an
area type object is limited to users who are members of the group
that is responsible. The user who creates or changes any part of the
area type object is recorded in the area type table, as well as the
date and time of that change. Official area type objects are the
responsibility of the National Soil Survey Center.
Descriptions for area type object data elements are available
in the National Soil Information System on-line help. Some data elements
are restricted to specific entries, others allow any appropriate entry.
Data elements for the area type object tables are described
below.
(1) Area type table: area type name
(i) Definition. Area type name is the name of the
particular type of area. Several types of areas are recorded in
addition to soil survey areas. Typical area types are State, County,
Climate factor areas, and MLRA Soil Survey Areas.
(2) Area table: area symbol
(i) Definition. Area symbol is a symbol, unique
within a particular area type, that is used to identify the area (e.g.
Lancaster County, NE is NE109). Typically, symbols for political areas
such as states and counties are Federal Information Processing
Standards (FIPS) codes. A survey area and a county may have the same
area symbol because each is recorded under a different area type.
(3) Area table: area name
(i) Definition. Area name is the name given to the
specific area. Although a soil survey area may be named for a county,
the soil survey area name is recorded under the soil survey area type
and the county name is recorded under the county area type, even if
the names are the same.
(4) Area table: area acres
(i) Definition. Area acres is the total acreage of
all land and water areas in a specified geographic area. For example,
the total acreage of a multi-county soil survey area is recorded in
this table, as well as the total acreage for each of the counties.
Parts of the soil survey area that occur in each county are recorded
in the legend area overlap table. Acreages are not recorded for some
area types.
Point Characterizations (639.04)
Point characteristics include soil profile descriptions, laboratory
characterization data, field measurements, transect observations, and
other soil survey data collected at individual sites. Some of these data
are currently in PEDON or the Soil Survey Laboratory soil
characterization database. Capabilities to coordinate these data in
NASIS are under development.
Standards, Criteria, and Guidelines
(639.05)
Standards, criteria, and guidelines include taxonomic class limits,
series ranges in characteristics, interpretation criteria, and other
data and documents used to establish concepts, assist aggregation, and
communicate policy in soil survey. Some standards, criteria, and
guidelines, such as interpretation criteria, are managed as data in
NASIS. Other standards, criteria, and guidelines, such as the National
Soil Survey Handbook and Soil Survey Manual are managed as
printed or as on-line documents.
(a) The Interpretation Criteria Object
The purpose of the interpretation criteria object is to maintain a
list of soil properties, class limits, ranking terms, and restriction
terms for each soil survey interpretation. Records in the interpretation
criteria object are used to create interpretations or predictions of
behavior from the soil physical, chemical, and morphological properties
of individual components of map units. Interpretive results are stored
and maintained independently from the interpretation criteria object.
Interpretation criteria objects include official criteria as well as
regionally or locally developed criteria. They are created as needed and
retained as part of the historical records.
The interpretation criteria object includes several tables in the
National Soil Information System. Facilities to create and maintain
interpretation criteria in these tables are under development.
Ancillary Tools, Functions, and
Records (639.06)
NASIS maintains additional records and provides editing tools and
functions to assure the security, integrity, and utility of the soil
survey data.
(a) The NASIS site object
The purpose of the NASIS site object is to maintain security
and communication of soil survey data objects and ancillary objects in
NASIS. It provides a complete list of networked NASIS sites and
authorized users. Each NASIS site has an entry in the NASIS site
object and that entry is maintained for as long as that NASIS site
exists.
The NASIS site object includes the NASIS site, group, user,
and group member tables.
The NASIS site table lists all NASIS sites and users. This
table enables the National Soil Information System to share data from
site to site. NASIS site records accompany requested data. The fields in
this table identify the NASIS site and who to contact if you have any
questions about that data.
The group table records the groups established at your site as
well as all groups associated with any data you have that belongs to
another site.
Descriptions for data elements in the NASIS site object are
available in National Soil Information System on-line documentation.
The group member table associates users with groups, not only
for the database but also for groups and users associated with any data
that belongs to another site. A user can be removed from a group at any
time. Group member table data elements are automatically populated by
the system.
The user table records the National Soil Information System
users that have been established at your site as well as all users
associated with any data you have that belongs to another site. A person
may have a UNIX login ID, but they cannot use the National Soil
Information System unless a National Soil Information System user name
is associated with their UNIX login ID in this table.
Authority to edit a NASIS site object is limited to a user who
has NASIS manager privileges for that object.
(1) NASIS site table: database iid (on screen label: Rec ID)
(i) Definition. Database iid is the identification
number of the database that created a particular entity. This is a
required integer field that uniquely identifies the local database.
This number must be obtained from the soil hotline staff BEFORE the
National Soil Information System site is installed.
(ii) Entry. The entry must be a number that is not already
assigned. The numbers 0 through 100 are reserved for use by the
National Soil Information System development staff.
(2) NASIS site table: database name (on screen label: NASIS site
name)
(i) Definition. Database name is the name of a
particular National Soil Information System site. The database name
has a required 30 character field that records the name that
identifies the local site. This name must be obtained from the soil
hotline staff BEFORE the National Soil Information System site is
installed. This is the source of the NASIS site name that is displayed
in the National Soil Information System edit windows.
(ii) Entry. Enter the desired name in the form of location |
| office type.
Example: MD_State_Office
(3) NASIS site table: database description (on screen label:
Description)
(i) Definition. Database description is a narrative
text entry that contains information about a particular National Soil
Information System site. The database description has an
optional 60 character field that describes the site to other
locations.
(ii) Entry. Enter the desired narrative description.
(4) NASIS site table: database state (on screen label: State)
(i) Definition. Database state is the name of the
state in which a particular National Soil Information System site
resides. It is expressed as the Federal Information Processing
Standards (FIPS) alpha state code.
(ii) Entry. Enter the appropriate Federal Information
Processing Standards code for the state, e.g. "AL" for Alabama.
(5) NASIS site table: database county (on screen label: County)
(i) Definition. Database county is the name of the
county or other division in which a particular National Soil
Information System site resides.
(ii) Entry. Enter the county or other division name in mixed
case.
Example: Lancaster (not Lancaster County)
(6) NASIS site table: database city (on screen label: City)
(i) Definition. Database city is the name of the city
or other location in which a particular National Soil Information
System site resides.
(ii) Entry. Enter the city or other name in mixed case.
Example: Temple
(7) NASIS site table: database office type (on screen label: Off
Type)
(i) Definition. Database office type is the name for
the type of office in which a particular National Soil Information
System site resides.
(ii) Classes.
area - Area office
field - Field office
mo - MLRA office
nhq - National headquarters
nssc - National Soil Survey Center
project - Project soil survey office
state - State office
other - Other type of office
(iii) Entry. Enter the appropriate office type name.
(8) NASIS site table: database contact (on screen label: Contact)
(i) Definition. Database contact is the name of the
primary contact person for a particular National Soil Information
System site.
(ii) Entry. Enter the name in the form first name | | last
name in mixed case.
Example: Jane Doe
(9) NASIS site table: database phone (on screen label: Phone)
(i) Definition. Database phone is the phone number of
the person identified by "database contact".
(ii) Entry. Enter the appropriate phone number.
Example: (402) 437-5423x1234
(10) Group table: group name (on screen label: Group)
(i) Definition. Group name is the name of a
particular National Soil Information System group in a particular
National Soil Information System site.
(ii) Entry. Enter the group name in mixed case.
Example: state office
(11) Group table: group description (on screen label: Description)
(i) Definition. Group description is a narrative text
entry that contains information about a particular National Soil
Information System group.
(ii) Entry. Enter text as desired.
(12) Group table: group contact (on screen label: Contact)
(i) Definition. Group contact is the name of the
primary contact for a particular National Soil Information System
group.
(ii) Entry. Enter the name in the form first name | | last
name in mixed case.
Example: John Doe
(13) Group table: group phone (on screen label: Phone)
(i) Definition. Group phone is the phone number of
the person identified by "group contact".
(ii) Entry. Enter the appropriate phone number.
Example: (402) 437-5423x1234
(14) User table: user name (on screen label: User)
(i) Definition. User name is the name of a particular
National Soil Information System user in a particular National Soil
Information System site.
(ii) Entry. Enter the name of the user in the form of first
name | | last name in mixed case.
Example: John Doe
(15) User table: unix user name (on screen label: Login)
(i) Definition. Unix user name is the UNIX user name
of a particular National Soil Information System user, i.e. the name
the user enters when logging into UNIX. The combination of user
name and unix user name is how National Soil Information
System makes the association between a particular National Soil
Information System user and a particular UNIX login ID.
(ii) Entry. Enter the "user's" UNIX login.
(16) User table: user description (on screen label: Description)
(i) Definition. User description is a narrative text
entry that contains information about a particular National Soil
Information System user.
(ii) Entry. Enter desired information. Perhaps the user's
title, such as "Soil Dataset Manager" or "Soil Correlator".
(17) User table: user phone (on screen label: Phone)
(i) Definition. User phone is the phone number of the
person identified by "user name".
(ii) Entry. Enter the appropriate phone number.
Example: (402) 437-5423x1234
(18) User table: dataset manager flag (on screen label: DSM)
(i) Definition. Dataset manager flag is notation that
indicates if a particular National Soil Information System user has
dataset manager privileges.
(ii) Entry. Choices are restricted to "yes" and "no".
(b) The Query Object
The purpose of the query object is to maintain the name, selection
criteria, description, and default target table developed for individual
queries. Queries are used to select specific records from local NASIS
data into a current NASIS session for viewing, editing, or reporting.
Queries are also used to retrieve NASIS data from other NASIS sites.
Query objects are created as needed and retained at the discretion of
the owner of the query.
The query object comprises the query table. Ownership of a specific
query object is indicated by the site and group columns in the query
table. Authority to edit the query object is limited to users who are
members of the group that owns the query.
A specialized editor is used to edit the selection criteria included
in the query. Descriptions for data elements in the query object and
instructions for use of the editor are in the National Soil Information
System on-line documentation. Facilities to create and maintain query
specification are under development.
(c) The Report Object
The purpose of the report object is to maintain the style, format,
content, and layout specifications developed for individual reports.
Reports are used to view or print soil survey data.
The report object comprises several tables in the National Soil
Information System. Facilities to create and maintain report
specifications in these tables are under development.
< Back to Part 639 Contents
| 
About Us
Back to Top