|
| |
NSSH Part 608
Program
Management
Definition and Purpose (608.00)
- Definition. Soil survey program management is the administrative
phase of the National Cooperative Soil Survey (NCSS) that provides a
systematic approach and guidelines for administering and coordinating
soil survey activities.
- Purpose. Soil survey program management ensures the effective
planning, scheduling, coordination, and organization needed to produce
and maintain quality soil survey information, initiated as timely and
as efficiently as possible. All initial soil surveys and Major Land
Resource Area (MLRA) soil surveys
are to be managed on a project basis. In some rare cases traditional
soil surveys (i.e. Non-MLRA
soil survey areas) may have an extensive revision done, but they
must first go through the evaluation process in the context of the MLRA
(see Part 610). These particular surveys are referred to elsewhere
in the NSSH as “update soil surveys requiring extensive revision”.
Responsibilities and Organization (608.01)
This section describes the roles of the various offices within NRCS.
Soil scientists and other specialists carry out soil survey activities
at numerous management and technical support levels within the NRCS and
through coordination with National Cooperative Soil Survey partners.
Additional information about responsibilities at various levels of the
organization can be found in Part 608.07(b) and in the
General Manual, Title 430, Part 402.
- National Headquarters Office (NHQ).
- provides overall direction, policy, guidance, and leadership for
the National Cooperative Soil Survey within NRCS
- coordinates the National Cooperative Soil Survey with NCSS
partners
- distributes fund allocations for soil survey program activities
to the states
- establishes soil survey goals for the program and monitors
progress made
- National Soil Survey Center (NSSC).
- Includes five functional areas:
- Soil Survey Laboratory
- Soil Survey Standards
- Soil Survey Research
- Soil Survey Interpretations
- Technical Soil Services
- The National Leaders, under the direction of the NSSC Director
or the Soil Survey Division Director, are responsible for support to
the National Cooperative Soil Survey program through:
- functions in their respective areas
- coordinating national technical standards
- policy and procedures that guide soil survey operations
- training
- investigations and laboratory assistance
- providing leadership and support to states for Technical Soil
Service activities
- maintaining soil survey data and information systems
- NASIS technical support
- coordination with the Information Technology Center
- maintenance of area symbols, names, and acreage, and
- the Soils Hotline and Soil Survey Division web pages
- MLRA Soil Survey Regional Offices (MO).
- provide leadership in the production and quality assurance of soil
survey information;
- provide leadership in classification, correlation,
interpretation, and joining of spatial and attribute data within and
between MLRA
Soil Survey Areas;
- provide quality assurance of maps, manuscripts, official series
descriptions, and attribute and spatial databases in the region;
- coordinate with federal lands agencies to assure that both NCSS
standards and partner needs are met;
- provide legend administration for MLRA
Soil Survey Areas;
- report progress related to field reviews and correlations; and
- where applicable, report compilation certification status.
- National Cartography and Geospatial Center (NCGC).
- assists in the acquisition and processing of imagery, orthophotography,
map compilation materials, and other digital data layers;
- stores and distributes geospatial data;
- develops standards, specifications, and provides quality assurance for spatial soil data
capture;
- develops geospatial web services;
- maintains print-on-demand map services;
- coordinates soil survey publications;
- maintains digital files of soil survey area boundaries for
publishing and distributing graphics depicting status of soil surveys;
and
- provides assistance to the National Cooperative Soil Survey
program in the development and application of new technology related
to cartography, remote sensing, GPS, and geospatial data.
- National Geospatial and Development Center (NGDC).
- develops and integrates spatial science and technologies that
bring the full wealth of soil and resource data and information to
the user community;
- researches and develops soil data and information products that
meet new and emerging customer needs;
- researches and develops field-based technologies for efficient
data collection;
- develops and tests information display systems that facilitate
the interpretation, understanding, and use of soil data; and
- develops applications that are functional and user-friendly.
- State Offices.
As program managers, state soil scientists:
- advise and assist their state conservationist in allocating
resources as effectively as possible to carry out all soil survey
and technical soil services in their area of responsibility;
- provide technical soil services within their state;
- develop local soil interpretations;
- direct (and in some instances supervise) resource soil
scientists;
- supervise MLRA
Soil Survey Office Leaders located within their state;
- develop cooperative relationships and serve as liaisons to the
State Cooperative Soil Survey cooperators and to the MLRA
Soil Survey Regional Offices;
- provide leadership to ensure that existing non-MLRA
soil surveys in their state are evaluated effectively by utilizing
the MLRA
Soil Survey Office Technical Team, as well as other appropriate,
knowledgeable sources such as cooperators, Resource Soil Scientists,
and others to identify deficiencies for consideration in the long
range plan (see 610.03);
- provides leadership to the MLRA
Soil Survey Management Team(s) for the MLRA
Soil Survey Offices located within the state, and serves as a member
of the MLRA
Soil Survey Area Management Team for all other MLRA Soil Survey
Offices serving the state (see parts
610.03 and 610.04 for more
details);
- monitor progress to ensure that work schedules and timelines are
being met according to the plan of operations;
- develop schedules to meet soil survey program objectives and to
assist the state conservationist in technical soil services
activities for conservation operations;
- provide legend administration for delivery of data to customers;
- identify needs for imagery, orthophotography, digital elevation
models (DEM), and other data layers;
- coordinate mapping goals and progress reporting with the MLRA
Soil Survey Regional Office; and
- in general, assist all users of soil survey information.
- Area and Field Offices.
Resource soil scientists and other specialists:
- provide coordinated soil information to all users;
- respond to user needs for new interpretations and collect
performance data;
- evaluate the adequacy of soil survey information;
- provide support for USDA programs and to MLRA
Soil Survey Offices;
- assist field offices with technical soil services;
- update and maintain the field office technical guide; and
- train field personnel in the use of soil survey information.
- MLRA Soil Survey Offices.
These are the official soil survey offices created as part of the
2008 reorganization of the National Soil Survey Program.
Responsibilities include:
- Summarizing details from individual Non-MLRA
soil survey evaluations and integrating them into a long range plan
of needed enhancements for the MLRA
soil survey area;
- scheduling routine work activities in plans of operations and
monthly and weekly schedules, as appropriate, in consultation with
the responsible state soil scientist and MLRA
Soil Survey Regional Office;
- providing leadership for the MLRA
Soil Survey Area Technical Team;
- supporting update of soil surveys within and among MLRA
administrative areas;
- providing management and support of soil survey activities over
a large geographic region;
- keeping soil survey maps and data throughout their assigned area
current to meet the changing needs of users;
- improving the quality of digital line work to conform to
landscape models;
- performing investigations throughout their assigned area,
maintaining soil survey datasets, and preparing and revising
official series descriptions;
- conducting quality control of all soil survey activities in the MLRA
Soil Survey Area, including any initial or extensive update soil
surveys conducted from soil survey project offices;
- developing project plans and annual plans to address the goals
and activities identified by the Management Team and Board of
Directors as priority work to be accomplished;
- conducting work in a manner that follows
NCSS standards, policy, and procedure; and
- collecting data in support of
NCSS initiatives.
- Soil Survey Project Offices.
These offices are established only with the concurrence of the
Director of the Soil Survey Division, when there is a special need
that cannot be met by the MLRA Soil Survey Office. In limited
instances, where initial mapping remains or previously completed survey areas require extensive
revision, a project soil survey office may be established as a subset
of the MLRA Soil Survey Office. However, it is Soil Survey Division
policy to transition all field operations into MLRA Soil Survey
Offices as soon as is practical.
- schedule routine work activities in plans of operations and
monthly and weekly schedules, as appropriate, in consultation with the
responsible state soil scientist and
MLRA Soil Survey Office;
- manage their project within the context of the overall
MLRA Soil
Survey Area and participate in quality control activities performed
by the MLRA Soil Survey Office;
- carry out mapping and related field data collections and
investigations needed to complete the soil survey of their assigned
area;
- conduct day-to-day quality control at the field level in a manner that
follows NCSS policy, standards, and procedures; and
- prepare maps, collect performance data, document map unit
composition, develop and maintain databases, prepare taxonomic
descriptions, and prepare manuscripts and tables to meet the
requirements of the soil survey and that are coordinated with the
MLRA Soil Survey Area.
- Digitizing Units.
NRCS digitizing units are responsible for digitizing soils data,
quality control of digital data, and certification review of final
spatial data, including tabular data and metadata, for soil surveys.
(see part 647).
Soil Survey Area Designation (608.02)
- Definition.
- A soil survey area is a geographic area that has a
size and shape defined for efficient field operations and timely
release of products. A soil survey area is an administrative unit
for project management (staffing and equipment), progress reporting,
and delivery of products.
- Soil survey area coverage includes all lands of the United
States, Puerto Rico, the U.S. Virgin Islands, and the Pacific Basin
Territories.
- National Soil Survey Center personnel follow the policy set out
in this section to identify soil survey areas in the NASIS
database. Each soil survey area receives a unique area name and
alpha-numeric area symbol that are used in the National Soil
Information System (NASIS),
Soil Data Warehouse and Mart, in cooperative agreements, memoranda
of understanding, all survey area publications, correlation
documents, and other official reports and correspondence.
- Two kinds of soil survey areas are recognized.
- MLRA Soil
Survey Areas
- Non-MLRA
Soil Survey Areas
- Refer to part 608.08 for guidance on legend
administration and acreage management in the NASIS
database.
- MLRA
Soil Survey Areas.
- These areas, which were established as part of the 2008
reorganization of the National Soil Survey Program, follow
physiographic boundaries reflecting natural features such as similar
soils, geology, land use and climate. They are the basis for soil
survey legend development to meet interpretive needs and for all
related classification, correlation, quality control, and quality
assurance functions.
- Boundary Designation
- The boundaries of MLRA
Soil Survey Areas may encompass all or parts of one or more MLRAs.
- Changes in boundaries of the MLRA
Soil Survey Areas and office locations are to be approved by the
Director of the Soil Survey Division.
- Naming and Symbolization
- MLRA Soil
Survey Areas are identified with an area symbol constructed by the
area symbol of the MLRA
Soil Survey Regional Office to which they are assigned, followed by
a consecutive integer number. The area name is the city in which the
office is located.
- Examples
- Chehalis, Washington (1-2)
- Elko, Nevada (3-3)
- Non-MLRA
Soil Survey Areas.
- These are the county-based areas (or other similar area like
parish or part of county) that have been traditionally used in the
soil survey program and remain to be used for exporting datasets
from NASIS
to the Soil Data Warehouse and product delivery from the Soil Data
Mart. These areas may be used for completion of the initial soil
survey and extensive revision work. They are subsets of MLRA
Soil Survey Areas.
- Boundary Designation
- Cooperating agencies of the National Cooperative Soil Survey
designate the boundaries of Non-MLRA
Soil Survey Areas in consultation with major users of soil
information.
- The boundaries of can correspond to county boundaries,
physiographic boundaries, tribal boundaries, federal agency
management boundaries, or other land management areas.
- Two or more small counties may be combined to form the
survey area; or
- Large counties and physiographic areas may be subdivided for
efficiency of field operations and publication of a final
product.
- The boundaries used for Non-MLRA
Soil Survey Areas can be changed by the state soil scientist, in
consultation with National Cooperative Soil Survey cooperators and
coordination with the National Soil Survey Center and National
Cartography and Geospatial Center as needed. Refer to
part 608.10.
- Considerations for defining boundaries include:
- efficiency of managing legends and databases for different
and overlapping spatial areas in the information system;
- project management for extensive updating (personnel and
equipment);
- timely and efficient delivery of the final product; and
- other factors important to cooperators.
- Naming and Symbolization
- The state soil scientist and
MLRA Soil Survey
Regional Office Leader coordinate the soil survey area names and
symbols for Non-MLRA
Soil Survey Areas with the National Soil Survey Center for
registration in the National Soil Information System (NASIS).
The name is not to exceed 135 characters.
- Non-MLRA
Soil Survey Areas that correspond to a single county, parish, or
independent city boundary: The symbol consists of the state
abbreviation followed by the Federal Information Processing
Standards (FIPS) code for the county, parish, or independent city.
The FIPS codes are in the Federal Information Processing Standards
Publication Series of the National Bureau of Standards, U.S.
Department of Commerce.
- For all other Non-MLRA
Soil Survey Areas: Use the state abbreviation and assign a unique
600, 700, or 800 series number in lieu of the FIPS code.
- Below are examples of names and symbols for Non-MLRA
Soil Survey Areas that have differing boundary designations:
- Soil Survey Area corresponds to a single county boundary.
- Baldwin County, Alabama (AL003)
- Terrebonne Parish, Louisiana (LA109)
- Soil Survey Area corresponds to two or more county boundaries.
- Beaver and Lawrence Counties, Pennsylvania (PA603)
- James City and York Counties and the City of Williamsburg,
Virginia (VA695)
- Soil Survey Area includes only part of a single county. Select a name that clearly distinguishes the survey area from
other survey areas in the county, or from adjoining counties. If a
clear designation cannot be made, use the term “Area” to indicate
that the survey area boundary does not include the entire county.
- Washoe County, Nevada, South Part (NV628)
- Socorro County Area, New Mexico (NM664)
- Soil Survey Area includes parts of two or more counties in one
state. Use the name of a well-known place or geographic feature, and
list the counties.
- Jicarilla Apache Area, New Mexico, Parts of Rio Arriba and
Sandoval Counties (NM698)
- Wenatchee National Forest, Naches Area, Washington, Parts of
Kittitas and Yakima Counties (WA680)
- Soil Survey Area includes all of one or more counties and part
of another.
- Soil Survey of Curry County and Southwest Part of Quay County,
New Mexico (NM669)
- Menifee and Rowan Counties and Northwestern Morgan County,
Kentucky (KY632)
- Soil Survey Area includes parts of two or more counties in
adjoining states.
- Great Smokey Mountains National Park, Tennessee and North
Carolina (TN640)
- Great Smokey Mountains National Park, Tennessee and North
Carolina (NC640)
- Shiprock Area, Parts of San Juan County, New Mexico and Apache
County, Arizona (NM717)
- Shiprock Area, Parts of San Juan County, New Mexico and Apache
County, Arizona (AZ717)
Note: In order to maintain acreage integrity for all states,
separate Project entries are made in
NASIS for survey areas that
cross state boundaries.
- Soil Survey Area in a region with no counties. Use the name of a
well-known place or geographic feature in the area.
- San German Area, Southwestern Puerto Rico (PR787)
- North Star Area, Alaska (AK642)
- Small Geographic Areas.
- Special management areas such as small political subdivisions,
areas of tribal lands, and federal management areas are ordinarily
handled as special projects or subsets (overlaps) of a larger soil
survey area.
- State soil scientists designate small geographic areas as soil
survey areas. Legends for these areas are linked to the appropriate
Area Types in NASIS
as needed.
Limited and Denied Access Areas (608.03)
- Limited Access Areas.
- Soil survey area coverage includes all lands (refer to
part
608.02), and the goal of the National Cooperative Soil Survey is to
survey all lands. Many survey areas include parts that have
difficult or limited access to personnel conducting field
operations, and occasionally landowners deny access to their
property.
- Do not necessarily exclude land from a soil survey area based on
difficult or limited access or because of difficulty in obtaining
permission to gain access. Use all available resources, such as old
soil survey maps (if available), geology and topographic maps,
aerial photography, and other available remote sensing materials to
apply common field procedures and techniques to delineate map units.
- For relatively small areas, mapping surrounding lands and
projecting soil lines across the area of denied access may be
feasible.
- For relatively large areas, more broadly defined map units may
be appropriate. In these cases, describe the reduced reliability
in the map unit description.
- Surveying Denied Access Areas.
State soil scientists, in consultation with the state conservationist
and local cooperators, determine the feasibility of mapping areas of
denied access. Reliability of the mapping for anticipated use and
interpretations should be the final determining factor.
- Judgment should be used in deciding whether to attempt to gain
permission to map areas of denied access. In some instances, such as
areas restricted for national security purposes or where there is a
desire by Native American officials for some tribal lands to remain
unmapped, the decision may be made to not pursue the issue further.
- In situations other than those described in (1) above, use all
reasonable means to obtain permission to map. Enlist the aid of
community leaders, district cooperators and supervisors, county and
state officials, and others, as appropriate.
- If reasonable efforts to gain access are unsuccessful, apply
techniques and resources discussed above in part 608.04(a) to map
the area.
- Reporting Denied Access Areas.
- Delineate the area as a map unit with a name “Area not surveyed,
access denied.”
- In the map unit description, tactfully describe the rationale
for not mapping the area.
- Include the symbol and the acreage in the soil survey acreage
table of the final report.
- Acreage is reported as mapping progress using standard
progress reporting procedures.
- In rare instances where the area of denied access is very
large, the soil survey area may be revised to exclude the unmapped
area. Acres are not reported.
- General Soil Maps.
Whether or not areas are excluded from detailed mapping, do not
exclude areas from the general soil map for the survey area and the
U.S. General Soil Map (STATSGO2) database. Use standard procedures for
delineating general soil map and STATSGO2 map units. The STATSGO2 map
is the basis for the survey area general soil maps.
Determining Workloads (608.04)
- The NRCS General Manual Title 340 describes agency policy for
workload analysis. Other cooperating agencies have their own policy
for workload analysis.
- The workload analysis planning process.
The workload analysis planning process considers the work to be done,
estimates the amount of time required to complete each task, and
provides a timetable for completing the work.
- A Long-Range Plan of Operations for initial soil survey projects
(or update soil surveys requiring extensive revision) details the
activities needed to complete the project in a realistic amount of
time (i.e. about 5 years or less). (See Exhibit 608-1).
- An Annual Plan of Operations for initial soil survey projects
(or update soil surveys requiring extensive revision) is used to
guide and provide specific focus to staff as the Long-Range Plan is
being implemented. (See Exhibit 608-2).
- A Long-range plan for the MLRA Soil Survey Area considers
all aspects of bringing all soil surveys in the area to a common
standard to meet user needs. (See Exhibit 608-3
and Exhibit 608-4). In addition to the needs of
the private lands in the area, it should include the needs
identified by the cooperators responsible for the federal lands
within the area so that a coordinated effort is achieved in all soil
survey work. The format and level of detail for the long-range plan
can vary. The purpose is not to develop detailed plans to accomplish
all of the needs, but rather to identify the needs in enough detail
to allow them to be prioritized effectively. Detailed planning to
accomplish the highest priority needs then takes place through
project plans.
- A Project Plan(s) for an MLRA
Soil Survey Area is used for planning to accomplish one or more of
the highest priority needs, The actual length of time needed to
complete the project will be dependent upon the scope of the project
and how it is defined. While there is no mandated limit to the time
a project can take to complete, projects expected to require more
than about three to five years should be reevaluated to see if they
can be subdivided into smaller projects with shorter individual time
lines. Shorter-term projects are preferred because they can be
managed more effectively. Some projects might be completed in less
than a year while others will require multiple years. Multi-year
project plans can be broken down into reportable milestones in order
to show annual progress. (See Exhibit 608-5 for
an example).
- An Annual Plan of Operations (or Business Plan) is used to
identify objectives, goals, responsibilities and timelines during a
fiscal year.
Priorities for Soil Surveys (608.05)
- State cooperative soil survey conferences, led by the State Soil
Scientist, convene annually to
discuss soil survey activities, consider the priorities of all
cooperators, and recommend action. Other interested user groups
recommend priorities, such as for special or interim soil reports.
Considerations for preparing the priority list are:
- status of initial soil surveys and update soil surveys requiring
extensive revision,
- NRCS needs for carrying out
Farm Bill and technical or financial assistance programs and
projects,
- cooperating agency needs for meeting their program and project
needs,
- requests for soil surveys by local people,
- needs of federal partners on federal lands,
- needs for information that aids in land use planning and
decisions,
- rapid land use changes in areas where critical soil problems are
expected,
- contributions of funds or staffing,
- needs for tax evaluation, and
- other factors of specific local importance.
- State soil scientists, in cooperation with lead scientists of
cooperating partners, the MLRA Soil Survey Regional Office leader,
and the MLRA Soil Survey leader work with the above
information to evaluate the needs for each MLRA Soil Survey Area
(see 610.03). Where federal lands are
included within the MLRA
Soil Survey Area, it is important to
coordinate with appropriate representatives of those agencies.
- The MLRA Soil Survey Area Technical Team, made up of the MLRA
Soil Survey Office staff, Soil Data Quality Specialists, Resource
Soil Scientists, applicable NCSS partner soil scientists, and if
needed, other discipline specialists, consolidate each state’s needs
into a combined list of needs for the MLRA Soil Survey Area
long range plan.
- The MLRA Management Team, consisting of the State Soil
Scientists for each state serviced by the MLRA Soil Survey Office,
and if applicable, Federal NCSS partners responsible for federal
lands in the area, determine which of the identified needs are the
highest priority. The MLRA Soil Survey Regional Office leader is
also included in the process of priority setting. These are reviewed
with the Board of Directors (or applicable subset of the Board) for
concurrence. The Management Team then provides guidance and support
to the MLRA Soil Survey
Area Technical Team to incorporate the priorities
into one or more individual project plans.
- The long-range plan is revised periodically as work progresses
and new information or unforeseen circumstances arise. Additional
issues to be addressed may come from a variety of sources, such as
Resource Soil Scientists, field offices, cooperators, customers, the
MO, or State Soil Scientists. Reports from the Soil Data Mart or
NASIS may also reveal issues and deficiencies to be prioritized and
addressed. As identified projects are completed, the MLRA Management
Team provides guidance as to the next priorities to be addressed by
the MLRA Soil Survey Office staff and new project plans are
then developed.
- Give consideration to the lead time required to prepare the
geospatial data and analyze existing information.
Planning Workflow (608.06)
The MLRA project
plan directs the use of resources to accomplish identified activities as
described above. At least one such plan is required for all MLRA
Soil Survey Areas. The plan identifies the activities that are to be
accomplished during the time period covered by the plan. The plan
includes the responsibility for each activity, projected completion
dates, and goals.
Exhibits 608-1 through 6 show sample formats for
long-range plans, a project evaluation ranking procedure, project plans, and annual plans of operations for
initial soil surveys or update soil surveys requiring extensive revision and for MLRA
soil surveys. Adapt them to fit the needs identified for the soil survey
area.
Part 610.02 contains information about
workflow for updating by MLRA
Soil Survey Area.
Goals and Progress (608.07)
-
Definition.
The National Soil Information System (NASIS)
includes a number of tables and data elements for planning, managing,
and tracking status, milestone events, and progress of the National
Cooperative Soil Survey. These data are stored in the Project data
object in NASIS.
Projects for initial soil survey work are linked to Non-MLRA
Soil Survey Areas. Projects for ongoing update work are defined by the
set of map units they cover and are not linked to Non-MLRA
Soil Survey Areas.
- Program managers use this information to assess workloads,
develop activity schedules and budgets, and plan for resources
needed to complete the national soil inventory and related
databases.
- Included as projects in NASIS
are all active initial mapping or extensive update Non-MLRA
Soil Survey Areas, as defined in part 608.02.
- Projects linked to each Non-MLRA
Soil Survey Area contain administrative and other data that track
the key business processes of the initial survey from field data
collection through final publication.
- Various soil survey business areas populate progress in the
database related to their individual areas of responsibility, and
use the information to plan and manage their operations. See
608.08(b)(4) for a list of soil survey business areas.
- A “Milestone” is an item or task identified to be completed for
the Project Plan. Milestones are intermediate tasks such as number
of transects collected, number of pedon descriptions gathered,
spatial line work editing, OSDs revised, etc. The milestone
information is entered into the Project Milestone table, the child
table of the parent Project table in NASIS.
The use of milestones allows the manager to divide the project into
reportable items and track the progress. Progress towards completion
of each milestone is entered into the Project Milestone Progress
table, the child table of the parent Project Milestone table.
- Projects are also to be defined to describe work to be done
while updating existing soil survey data. These projects are to be
linked to the set of map units that they encompass by listing the
map units in the Project Mapunit table. Milestones associated with
these projects and progress towards them should be documented as
described in (5) above.
- NASIS
also includes the capability to record scheduled activities related
to technical soil services, and progress made related to these
activities. See part 608.09(b)(2) for more information.
-
Responsibilities.
Data stewards for the various soil survey business areas are
responsible for populating data elements and ensuring data quality in NASIS.
Soil survey business areas include all inventory-related activities at
the field level, and support and enabling activities for generating soil
survey products.
- The business area responsible for either initiating or completing
a soil survey business process also is responsible for populating
appropriate data elements and reporting progress associated with the
process.
- Exhibit 608-8, Business Area Responsibilities
for Goals and Progress, identifies broad soil survey business
processes, along with associated data elements and the business area
that is responsible for populating the schedule. Some data elements
in Exhibit 608-8 indicate more than one responsible business area;
for these situations, the appropriate business area program managers
designate the responsible data steward. See part
608.01 for additional information.
- State Office and MLRA
Soil Survey Regional Office program managers may delegate
responsibility to populating some data elements to the field. For
example, MLRA
Soil Survey Offices may be designated to report mapping and
compilation progress for their respective area.
-
Accessing the Data.
- Soil survey area legends and projects are accessible through the
National Soil Information System (NASIS) interface.
- The interface provides authorized users with full capability to
create, edit, and report data.
- Individuals need to be extremely careful not to populate or
change data that falls under the responsibility of another business
unit.
- Various reports are available in NASIS
to summarize the data.
-
Data Management.
Exhibit 608-7 identifies soil survey business areas
and related data elements, including key terminology and protocols,
necessary for administration and maintenance of the data.
Exhibit 608-8 provides an overview of the data elements and
responsible soil survey business areas.
-
Soil Survey Performance Measurement.
The NRCS
Performance Results System (PRS) is the official progress reporting
instrument used by the agency to prepare national-level reports.
Agency-accountable items such as soil mapping progress, first-time
archival of SSURGO
digitizing, and public release of soil surveys are assembled from NASIS
and the Soil Data Mart nightly and automatically uploaded to the PRS.
Goals for these agency-accountable items are also taken from NASIS
and recorded in the PRS.
Other data from NASIS
are used to assess program
performance and analyze budgets. Examples include signed memoranda of
understanding, progress reviews and correlations completed, manuscripts
edited, acres compiled and digitized, and the status of imagery and orthophotography acquisition. Both individual and business area
performance can be analyzed.
- Performance Goals.
- At the beginning of the fiscal year, establish individual and team
goals for soil survey business functions.
- In addition to initial and update soil surveys, mapping goals may
be set for non-project survey areas based on anticipated requests for
conservation planning. Refer to Exhibit 608-6 for more discussion about
goal setting.
- State program managers and supervisors:
- Base performance goals on the individuals’ job description,
experience, training, complexity, and other factors;
- Monitor progress throughout the year; and
- Revise individual or team performance goals as needed, in consultation
with the employee(s).
- Goals are not always based on acres mapped. Goals for other
aspects of soil survey can be established, especially for local
project management.
- Performance goals can be set for:
- technical services and soil survey support activities;
- mapping goals – do not include large water bodies (census water);
however, report census water acres as a land category in the Project
Land Category Breakdown table;
- gathering field documentation;
- database development;
- GIS analysis;
- correlations; and
- manuscript development.
- Refer to Exhibit 608-7 for more discussion about goal setting.
- Progress and Progress Reporting.
- Soil survey progress records the inventory of the nation’s soil
resources, development of related databases, soil survey products, and
interpretative materials.
- State Soil Scientists are responsible for ensuring that
progress is reported.
- Reportable items include all activities, including intermediate
products (e.g. milestones) that lead to a final product meeting National Cooperative Soil
Survey standards.
- acres mapped;
- correlations completed;
- acres compiled and digitized;
- manuscripts edited; and
- • documentation collected (e.g., pedon descriptions, transects,
photographs, monitoring data, laboratory samples, vegetation data,
special studies).
- Report progress in NASIS as it occurs. As a
minimum, report mapping progress quarterly, and all other progress
monthly.
- Mapping Progress.
- Refer to Exhibit 608-7 for more discussion about reporting mapping
progress.
- Discuss progress reporting issues with the Soil Survey Program
manager in the Soil Survey Division Headquarters before revising
them.
- For each Non-MLRA
Soil Survey Area, create a Project in NASIS
and enter mapping progress into the Project Mapping Progress
table by land category (refer to acreage accountability below).
- The reporting date entered in the Project Mapping Progress
table determines the fiscal year for which progress is counted.
- Report progress as initial or update mapping.
- Distinguish NRCS from cooperator personnel.
- Enter each individual’s progress or progress for the project
team as a whole.
- Initial soil surveys are closely monitored. Report initial
mapping progress only once and never delete it from the system
once it is reported, except for data entry errors that are
immediately recognized and corrected.
- Upon completion of the initial soil survey, all initial
acres that are reported as progress should equal the land
category acres and the sum of all land category acres should
equal the area acres for the respective Non-MLRA
soil survey area.
-
Project Administration and Acreage Management.
The National Soil Information System (NASIS) provides a variety of ways
in which data can be managed. Therefore, in order for the system to
function optimally, a uniform approach is required.
In NASIS,
projects that are linked to Non-MLRA
Soil Survey Areas provide data about goals and progress for
mapping and other milestone activities for initial soil survey work. A
project is created for each initial soil survey project. Projects
describing soil survey update activities are to be developed as needed.
- Unique Spatial Areas.
- All Non-MLRA
Soil Survey Areas represent a unique geographical (spatial)
area, i.e., an entire county, multiple counties, or parts of one or
more counties; they receive a unique area symbol and area name (see
part 608.02).
- With the data conversion to NASIS
6.0, a project was created for each legend linked to a Non-MLRA
Soil Survey Area. The resulting project was named for the survey
area and the status shown in the Legend table – e.g. Allen County,
Kansas - Update needed. Data from the Legend data object related to
goals and progress in NASIS
5.4 were moved to this new Project and related tables.
- Projects for the same geographical area are linked to the same
area symbol and area name.
- For survey areas having multiple projects, the soil survey area
status identifies the most current project, as discussed in
608.08(d).
- Exhibit 608-7 provides additional discussion
and examples of various project scenarios and protocols.
- Acreage Accountability.
NRCS annual congressional appropriations are limited to non-federal
lands, including Tribal and Trust Territories. The cost of soil survey
activities by NRCS on federal lands must be reimbursed to
NRCS
by the respective agency.
However, the NRCS as federal lead for the National Cooperative Soil
Survey maintains records of soil survey mapping for all lands of the
nation.
- Seven land categories distinguish between non-federal and federal
ownership. Additionally, federal lands are categorized according to the
responsible federal land management agency.
- Native American land
- Other non-federal land
- Bureau of Land Management
- U. S. Forest Service
- National Park Service
- Other federal land
- Census water
- Refer to Exhibit 608-7 for definitions of the land categories and
for additional discussion of acreage management and accountability.
- Acreage Allocation.
Federal and private land ownership and their acreages constantly change.
State program managers must periodically access land ownership for all
soil survey areas.
This information is maintained in the Project Land Category
Breakdown table in NASIS.
- If ownership acres have changed in a soil survey area:
- Re-allocate acreage assigned to the seven land categories.
- Re-allocate progress assigned to each land category.
- The sum of all land category acres within a project for a Non-MLRA
Soil Survey Area must equal the area acreage for the survey
area.
- The sum of all land category acres within a project for a Non-MLRA
Soil Survey Area equals the state-total acreage from the 1992
National Resource Inventory.
- To re-allocate acres for soil surveys with more than one project
or that partially overlap with another survey, refer to the
discussion of acreage management and accountability in
Exhibit 608-7.
- Acreage Base.
County-based 1992 National Resources Inventory (NRI) data for total
surface area (land and water) is used within
NRCS
as the official acreage for Non-MLRA
Soil Survey Areas that coincide with county or parish
boundaries, and for state totals. Acreages for Non-MLRA
Soil Survey Areas that do not coincide with county or parish
boundaries must be balanced with the respective state totals.
- Use the exact county-based figures or round to the nearest hundred.
- Coordinate acreage assigned to all survey areas with the National NASIS data steward at the National Soil Survey Center for inclusion in
NASIS.
Developing Other Schedules for Soil Survey
Operations (608.08)
- Soil Survey Operations.
Schedules and timelines for soil survey activities are detailed in
long-range plans, project plans, annual plans of operation, and
monthly or weekly schedules. Exhibit 608-1 is an
example of a long-range plan of operations for initial surveys or
update surveys requiring extensive revision. Exhibit
608-2 provides an example of an annual plan of operations for
these types of surveys. Exhibit 608-3 is an
example of the identified needs that long-range plans should address
for MLRA
Soil Survey Areas.
- Soil survey leaders schedule soil survey activities and
coordinate routine work in consultation with the responsible state
soil scientist and MLRA Soil Survey Regional Office. Quality control
activities are carried out and documented by the MLRA Soil Survey
Leader.
- MLRA Soil Survey Regional Offices schedule quality assurance reviews and
field assistance visits in consultation with the MLRA Soil Survey
Offices, State Offices, and National Cooperative Soil Survey partners.
- Technical Soil Services.
- State offices and field offices develop annual plans of
operation and monthly or weekly schedules, as appropriate, for
technical soil services-related activities.
- Resource soil scientists and, in some instances, other soil
scientists assigned to nearby soil survey offices provide soil
information as needed for conservation planning and other special
local needs. These efforts ensure efficient use of soil scientist
time and timely delivery of soil information. These activities are
to be reported in the Technical Soil Service table in NASIS.
A choice list of activities is provided. New activities can be added
to the list by coordinating with the National Leader of Technical
Soil Services and the NASIS
data steward at the National Soil Survey Center. Scheduled start and
end dates can be recorded for each service provided, as well as the
actual start and end dates. The person providing the service, the
geographic location where the service was provided, the name of the
person or entity receiving the service, and the benefits realized
are to be documented also.
- Individual Schedules.
- Individual soil scientists prepare monthly or weekly schedules, as
required by supervisors.
- These schedules include
- routine soil survey activities;
- training to be given and received;
- staff conferences; and
- information and public relations needs.
Status Maps (608.09)
Maps indicating the progress and status of soil surveys and soil
survey products are important management and public relations tools.
Maps may be on a national, regional, MLRA region, and state basis.
- Source Data.
- The primary source of attribute data is NASIS and the
Soil Data Mart. Part 608.08 identifies soil survey business
areas that are responsible for populating and maintaining
the data.
- Base map cartography and spatial data for soil survey
areas is maintained by the National Cartography and
Geospatial Center (NCGC).
- Responsibilities.
- The National Cartography and Geospatial Center maintains
a digital file of soil survey area boundaries for all Non-MLRA
Soil Survey Areas listed in NASIS. Boundaries are taken from
SSURGO data archived on the Soil Data Mart where SSURGO data
is complete.
- State Soil Scientists:
- assure the accuracy and completeness of Non-MLRA
Soil Survey Area boundaries. The states will provide
NCGC with a boundary layer for survey areas that are not
yet in SSURGO;
- initiate revisions and corrections to the boundaries
as needed.
- Data Availability.
- Soil Data Availability Status Map.
- The Soil Data Availability Status map at
http://soildatamart.nrcs.usda.gov/StatusMap.aspx
portrays the availability of digital official soil data
in the Soil Data Mart. This map is automatically updated
daily based on contents of the Soil Data Mart. The map
legend indicates the data available for each soil survey
area. Partial surveys are also shown. Access the map at
http://soildatamart.nrcs.usda.gov/StatusMap.aspx.
- Standard map legend categories and colors
- Dark green – digital spatial and tabular data
are available
- Light green – digital tabular data only are
available
- White – no digital data available
- Other Status Maps.
- Program managers at the national, regional, MO
region, or state levels may determine other types of
soil survey status maps useful for management and
information purposes within their operational area.
Long-Range Plan
of Operations for Initial Soil Surveys and for Update Soil Surveys
Requiring Extensive Revision (Exhibit 608-1)
| United States Department of
Agriculture - Natural Resources Conservation Service |
| ____________________________ County,
____________________________ |
| Date ________________________ Project
staff _________________________ |
|
|
|
|
| Narrative of Plan Items |
|
FY-______ FY-______
FY-______ FY-______
FY-______ |
| |
|
|
|
|
|
| 1. Memo of understanding (optional with MLRA
Region-wide MOU on file) |
|
|
| |
a. Meet with locals |
|
______
______ ______
______ ______ |
|
b. Prepare draft MOU |
|
______
______ ______
______ ______ |
|
c. Obtain review |
|
______
______ ______
______ ______ |
|
d. Obtain signatures |
|
______
______ ______
______ ______ |
|
|
|
|
| 2. Collect references |
|
|
|
a. Geology |
|
______
______ ______
______ ______ |
|
b. Water resources |
|
______
______ ______
______ ______ |
|
c. Statistical reports |
|
______
______ ______
______ ______ |
|
|
1. Farm |
|
______
______ ______
______ ______ |
|
|
2. NRI |
|
______
______ ______
______ ______ |
|
|
3. SWCD |
|
______
______ ______
______ ______ |
|
|
4. Climate |
|
______
______ ______
______ ______ |
|
|
5. Other |
|
______
______ ______
______ ______ |
|
d. County roads |
|
______
______ ______
______ ______ |
|
e. Adjoining soil survey data |
|
______
______ ______
______ ______ |
|
f. Topo quad sheets, DEMs |
|
______
______ ______
______ ______ |
|
|
|
|
| 3. Prepare field sheets (if used) |
|
|
|
a. Edging |
|
______
______ ______
______ ______ |
|
b. Identification |
|
______
______ ______
______ ______ |
|
c. Advance copy ident. |
|
______
______ ______
______ ______ |
|
d. Acreage determination |
|
______
______ ______
______ ______ |
|
e. Other |
|
______
______ ______
______ ______ |
|
|
|
|
| 4. Preliminary field studies |
|
|
|
a. Area reconnaissance |
|
______
______ ______
______ ______ |
|
b. Develop landform map |
|
______
______ ______
______ ______ |
|
c. Field test STATSGO2 for GSM use |
|
______
______ ______
______ ______ |
|
d. Test map areas |
|
______
______ ______
______ ______ |
|
e. Correlate studies and field
observations |
|
______
______ ______
______ ______ |
|
|
|
|
| 5. Prepare draft descriptive legend (ensure
NASIS is populated for) |
|
|
|
a. Taxonomic desc. |
|
______
______ ______
______ ______ |
|
b. Map unit desc. |
|
______
______ ______
______ ______ |
|
c. Features and Symbols legend |
|
______
______ ______
______ ______ |
|
d. Identification Legend |
|
______
______ ______
______ ______ |
|
e. Classification of soils |
|
______
______ ______
______ ______ |
|
|
|
|
| 6. Documentation and supporting data |
|
|
|
a. Transect studies |
|
______
______ ______
______ ______ |
|
b. Field notes |
|
______
______ ______
______ ______ |
|
c. Identify problem areas |
|
______
______ ______
______ ______ |
|
d. Field descriptions |
|
______
______ ______
______ ______ |
|
e. Pedon program |
|
______
______ ______
______ ______ |
|
f. Transect program |
|
______
______ ______
______ ______ |
| |
g. Soil mapping procedures, relationships, soil surveyor's model |
|
______
______ ______
______ ______ |
|
h. Other |
|
______
______ ______
______ ______ |
|
|
|
|
| 7. Special studies |
|
|
|
a. Crop yields |
|
______
______ ______
______ ______ |
|
b. Forestland site |
|
______
______ ______
______ ______ |
|
c. Geomorphic |
|
______
______ ______
______ ______ |
|
d. Characterization |
|
______
______ ______
______ ______ |
|
e. Surficial geology |
|
______
______ ______
______ ______ |
|
f. Other |
|
______
______ ______
______ ______ |
|
|
|
|
| 8. Field mapping |
|
|
|
a. Joining |
|
______
______ ______
______ ______ |
|
b. Acreage goals |
|
______
______ ______
______ ______ |
|
c. Compile sheets (if needed) |
|
______
______ ______
______ ______ |
|
d. Digitize |
|
______
______ ______
______ ______ |
|
e. Run SSURGO AMLs |
|
______
______ ______
______ ______ |
|
|
|
|
| 9. Sampling and lab data |
|
|
|
a. Sampling for NSSL |
|
______
______ ______
______ ______ |
|
b. Sampling for University |
|
______
______ ______
______ ______ |
|
c. Sampling for highway dept. |
|
______
______ ______
______ ______ |
|
|
|
|
| 10. QA reviews and field visit
assist. |
|
|
|
a. Pre-initial review |
|
______
______ ______
______ ______ |
|
b. Initial review |
|
______
______ ______
______ ______ |
|
c. Progress review |
|
______
______ ______
______ ______ |
|
d. Final review |
|
______
______ ______
______ ______ |
|
e. Prelim. correlation |
|
______
______ ______
______ ______ |
|
f. Final correlation |
|
______
______ ______
______ ______ |
|
g. Field visit assist. |
|
______
______ ______
______ ______ |
|
|
|
|
| 11. General soil map (STATSGO2)
revise and update |
|
|
|
a. Adjust delineation of units |
|
______
______ ______
______ ______ |
|
b. Develop legend |
|
______
______ ______
______ ______ |
|
c. Describe units |
|
______
______ ______
______ ______ |
|
d. Develop diagrams |
|
______
______ ______
______ ______ |
|
|
|
|
| 12. Develop survey area soil handbook |
|
|
|
a. Introduction to area |
|
______
______ ______
______ ______ |
|
b. General nature |
|
______
______ ______
______ ______ |
|
c. Crops and pasture |
|
______
______ ______
______ ______ |
|
d. Forestland and windbreaks |
|
______
______ ______
______ ______ |
|
e. Range |
|
______
______ ______
______ ______ |
|
f. Engineering |
|
______
______ ______
______ ______ |
|
g. Recreation |
|
______
______ ______
______ ______ |
|
h. Wildlife |
|
______
______ ______
______ ______ |
|
i. Factors of soil formation |
|
______
______ ______
______ ______ |
|
j. Classification of soil |
|
______
______ ______
______ ______ |
|
|
|
|
| 13. Interpretation tables |
|
|
|
a. Prepare and update data elements |
|
______
______ ______
______ ______ |
|
b. Generate tables for review |
|
______
______ ______
______ ______ |
|
c. Review tables with technical
specialists |
|
______
______ ______
______ ______ |
|
|
|
|
| 14. Take manuscript photos |
|
|
|
a. Select sites |
|
______
______ ______
______ ______ |
|
b. Review photos with editors |
|
______
______ ______
______ ______ |
|
c. Select final photos |
|
______
______ ______
______ ______ |
|
|
|
|
| 15. Prepare soil survey manuscript |
|
|
|
a. Select from survey area soil
handbook or generate from NASIS |
|
______
______ ______
______ ______ |
|
b. Obtain technical review |
|
______
______ ______
______ ______ |
|
c. Obtain English edit |
|
______
______ ______
______ ______ |
Annual Plan of
Operations for Initial Soil Surveys and for Update Soil Surveys Requiring
Extensive Revision (Exhibit 608-2)
| United States Department of
Agriculture - Natural Resources Conservation Service |
| ____________________________
County, ____________________________ |
| Date ________________________
Project staff _________________________ |
|
|
|
|
|
|
Responsibility of |
Number Amount |
Hours Per Quarter |
FY Total |
|
|
|
|
1 |
2 |
3 |
4 |
|
| Section A: Long-range Plan of
Operation |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1. Memo of understanding |
|
|
|
|
|
|
|
|
|
a. Meet with locals |
|
__________ |
______ |
___ |
___ |
___ |
___ |
______ |
|
b. Review specifications |
|
__________ |
______ |
___ |
___ |
___ |
___ |
______ |
|
c. |
|
__________ |
______ |
___ |
___ |
___ |
___ |
______ |
|
d. |
|
__________ |
______ |
___ |
___ |
___ |
___ |
______ |
|
|
|
|
|
|
|
|
|
|
| 2. Collect references |
|
|
|
|
|
|
|
|
|
a. Geology reports |
|
__________ |
______ |
___ |
___ |
___ |
___ |
______ |
|
b. Flood data |
|
__________ |
______ |
___ |
___ |
___ |
___ |
______ |
|
c. Local history |
|
__________ |
______ |
___ |
___ |
___ |
___ |
______ |
|
d. County road maps |
|
__________ |
______ |
___ |
___ |
___ |
___ |
______ |
|
e. Land use |
|
__________ |
______ |
___ |
___ |
___ |
___ |
______ |
|
f. Water quality info |
|
__________ |
______ |
___ |
___ |
___ |
___ |
______ |
|
|
|
|
|
|
|
|
|
|
| 3. Prepare field sheets (if used) |
|
|
|
|
|
|
|
|
|
a. Edging |
|
__________ |
______ |
___ |
___ |
___ |
___ |
______ |
|
b. Identification |
|
__________ |
______ |
___ |
___ |
___ |
___ |
______ |
|
c. Advance copy identification |
|
__________ |
______ |
___ |
___ |
___ |
___ |
______ |
|
d. Designate acreage |
|
__________ |
______ |
___ |
___ |
___ |
___ |
______ |
|
|
|
|
|
|
|
|
|
|
| 4. Preliminary field studies |
|
|
|
|
|
|
|
|
|
a. Develop landforms map |
|
__________ |
______ |
___ |
___ |
___ |
___ |
______ |
|
b. Draft
initial STATSGO2 update |
|
__________ |
______ |
___ |
___ |
___ |
___ |
______ |
|
c. Test
map areas |
|
__________ |
______ |
___ |
___ |
___ |
___ |
______ |
|
|
|
|
|
|
|
|
|
|
| 5. Descriptive legend (complete data
in NASIS) |
|
|
|
|
|
|
|
|
|
a. Prepare taxonomic unit descriptions |
|
__________ |
______ |
___ |
___ |
___ |
___ |
______ |
|
b. Prepare map unit descriptions |
|
__________ |
______ |
___ |
___ |
___ |
___ |
______ |
|
|
|
|
|
|
|
|
|
|
| 6. Documentation and supporting data |
|
|
|
|
|
|
|
|
|
a. Record transects |
|
__________ |
______ |
___ |
___ |
___ |
___ |
______ |
|
b. Yield data |
|
__________ |
______ |
___ |
___ |
___ |
___ |
______ |
|
c. Forest transects |
|
__________ |
______ |
___ |
___ |
___ |
___ |
______ |
|
d. Describe pedons |
|
__________ |
______ |
___ |
___ |
___ |
___ |
______ |
|
e. Analyze transect data |
|
__________ |
______ |
___ |
___ |
___ |
___ |
______ |
|
|
|
|
|
|
|
|
|
|
| 7. Field mapping |
|
|
|
|
|
|
|
|
|
a. Acreage goal by individual |
|
__________ |
______ |
___ |
___ |
___ |
___ |
______ |
|
|
|
|
|
|
|
|
|
|
| 8. Field reviews |
|
|
|
|
|
|
|
|
|
a. Pre-initial review |
|
__________ |
______ |
___ |
___ |
___ |
___ |
______ |
|
b. Progress review |
|
__________ |
______ |
___ |
___ |
___ |
___ |
______ |
|
|
|
|
|
|
|
|
|
|
| Section B: Soil Management and
Interpretations Support Services |
|
|
|
|
|
|
|
|
|
a. Onsite investigations |
|
__________ |
______ |
___ |
___ |
___ |
___ |
______ |
|
b. FOTG |
|
__________ |
______ |
___ |
___ |
___ |
___ |
______ |
|
c. Special evaluation |
|
__________ |
______ |
___ |
___ |
___ |
___ |
______ |
|
|
|
|
|
|
|
|
|
|
| Section C: Information Activities |
|
|
|
|
|
|
|
|
|
a. Talk to service club |
|
__________ |
______ |
___ |
___ |
___ |
___ |
______ |
|
b. Prepare news article |
|
__________ |
______ |
___ |
___ |
___ |
___ |
______ |
|
c. Report to cooperators |
|
__________ |
______ |
___ |
___ |
___ |
___ |
______ |
|
|
|
|
|
|
|
|
|
|
| Section D: Leave and Holiday |
|
|
|
|
|
|
|
|
|
a. Annual leave |
|
__________ |
______ |
___ |
___ |
___ |
___ |
______ |
|
b. Sick leave |
|
__________ |
______ |
___ |
___ |
___ |
___ |
______ |
|
c. Holidays |
|
__________ |
______ |
___ |
___ |
___ |
___ |
______ |
Example of Needs Identified for an MLRA Soil
Survey Area Long-Range Plan (Exhibit
608-3)
Correlation Needs
Potential New Series
- Non-mollic Sioux and Coe analogous to Langhei and Sisseton
- Moderately well drained phases of Sioux and Coe
- Shaly Divide, Marysland, and Wyrene
- A phase of Wyard for coarse-loamy till areas
- Series for shaly sands (e.g., shaly Hecla, Hamar, Venlo)
- Two-story series for coarse-loamy till (e.g., Dickey, Towner, Swenoda,
Lanona)
- Colluvial soil analogous to Darnen for the coarse-loamy till
- Other variants and out of date series
Classification Issues
- Hapludolls vs. Calciudolls
- Binford
- Brantford
- Sverdrup
- Aquic or Oxyaquic
- Clontarf
- Describe OSDs to 2 meters
- Evaluate the use of spot symbols throughout the MLRA
- Evaluate sandy-skeletal soils for loamy-skeletal and sandy substrata
- Evaluate the need for a fine textured Manfred
- Out-of-date series
Soil-Landscape Issues
- Evaluate use of upland sodium-affected soils (e.g., Aberdeen) on
floodplains
- Evaluate use of Southam, Parnell, and Tonka on outwash plains
- Evaluate use of Southam, Parnell, and Tonka on coarse-loamy till plains
- Evaluate use of Lindaas and Perella in depressions in lacustrine areas
- Evaluate the use and develop mapping criteria for separating drainage
phases of Maddock and Hecla
- Evaluate the use and develop mapping criteria for separating drainage
phases of Dickey, Towner, and Foldahl
- Evaluate the need for separating till and lacustrine substrata
(Towner, Swenoda, etc.)
- Evaluate well drained outwash map units such as Renshaw and Brantford
for correct drainage
- Evaluate Barnes-Hamerly map units (Towner and Rolette Counties)
- Evaluate Barnes-Buse and Svea-Buse map units in Cavalier and other
counties
- Evaluate selected map units in Lamoure County for proper drainage
- Evaluate high terrace map units along the Sheyenne River in Ransom
County to determine if they are till or outwash
- Evaluate Edgeley map units in Lamoure and Dickey Counties
- Evaluate the surface texture of Walsh in the Sheyenne River Valley
- Evaluate the use and develop mapping criteria for separating Falsen and
Lohnes
- Define relevant slope groups for specific landscapes
- Evaluate doughnut topography (composition, hydric soils, etc.)
- Evaluate dissected topography (composition, etc.)
- Evaluate high density pothole landscapes (composition, hydric soils,
etc.)
- Evaluate low-relief eroded landscapes (composition)
- Evaluate small lake plains (upland soils) on till plain
- Evaluate use of poorly and very poorly drained lacustrine soils (Fargo,
Grano) in potholes on the till plain
- Evaluate the potential of a till substratum under lacustrine soils in
Ramsey and Towner Counties
- Evaluate use of till substratum phases of Divide, Marysland, and Wyrene
- Evaluate wooded map units (composition, components, O horizon)
- Evaluate fluvial systems (consistent use of channeled map units,
continuity of flood plains, frequency of flooding etc.)
- Evaluate textures and drainage (somewhat poorly) in the Sheyenne River
Valley
- Evaluate stony phases (percent surface fragments, stony areas in Barnes
County)
- Evaluate the design of sand-mantled till map units
- Evaluate the design of till-outwash map units
- Evaluate the need for identifying various till lobes/members (shaly
till, fine till)
- evaluate the near surface stratigraphy (loam surface, clay loam
parent material)
- evaluate possible lacustrine influence on natric soils
- Evaluate linear, esker-like surface features to determine composition
- Evaluate the spatial distribution of sodium affected soils (relationship
with depth to shale, lacustrine soils)
Soil Data/Interpretation Issues
- Document saturation/water tables on sands
- Evaluate salinity levels (Vallers, saline-Parnell, etc.)
- Evaluate saline undifferentiated map units (Vallers and Hamerly)
- Establish reference components for land use (range versus crop, drained
versus undrained)
- Summarize ponding duration investigation
- Summarize hydric soil investigation
- WSG for sandy soils
- Determine surface textures for coarse-loamy till
- Evaluate soil lengths for MLRA map units
- Document PIs
- Evaluate eco-site for Stirum
Miscellaneous
- Review “official” field office
hard copy soil survey manuscripts for any identified errors that need to be
corrected in the digital product
- Correct previously identified
join errors that easily correctable with on-screen digitizing tools (not
requiring field investigations)
- Complete the placement of MLRA
lines on
SSURGO product
- Update
STATSGO for MLRA
55A and 55B
Example of a Project Plan Evaluation
Ranking Procedure
(Exhibit 608-4)
Rank each factor from 1 to 3, with 1 being low and 3 being high.
Determine the overall priority ranking from the Key at the end.
A. Scientific Merit. How important is the Project for soil science
and the soil resource inventory? Examples: updating or investigating
taxonomic classifications; revising series concepts; updating or
correcting pedon descriptions; sampling to fill data voids for series.
| Score |
Criteria |
| 1 |
Little or no scientific merit. |
| 2 |
Some merit; minor changes to benchmark soils; changes to soils
of small extent, etc. |
| 3 |
High merit; major advances in scientific knowledge about
benchmark soils.
|
B. Agency Merit. How important is the Project for NRCS or Partners
programs? Included here are all the Farm Bill programs, conservation
planning, state cost-share, etc. Examples: K factors (affects HEL and
CRP), hydric soils (wetlands), prime farmland issues, suitability
groups.
| Score |
Criteria |
| 1 |
Little or no scientific merit. |
| 2 |
Minor or incidental effects on some properties or areas of concern;
affects one or programs in a minor way. |
| 3 |
Significant revision to properties of benchmark soils used in programs
or areas of significant concern to conservation efforts; affects several
programs, or has a major impact on one or more programs. |
C. External Merit. How important is the Project for external customers,
either government or private?
| Score |
Criteria |
| 1 |
Little or no interest from external customers. |
| 2 |
Some effect on soil survey users or agencies; one user group impacted. |
| 3 |
Major impact on land use planning, interpretations, or agency programs
or lands; more than one user group impacted. |
D. Financial/Partnership Inputs. Are there inputs from other sources or
partners, such as funding, staffing, equipment, or technical support?
| Score |
Criteria |
| 1 |
Little or no partnership involvement. |
| 2 |
Some commitment of staff time, equipment, and/or technical support; one
partner involved. |
| 3 |
Major commitment of staff time and equipment, and/or financial support;
more than one partner involved; strong support or guidance of NRCS or
partner administration.
|
E. Synergy. Does the Project serve or support another project or
proposal?
| Score |
Criteria |
| 1 |
None. |
| 2 |
Some advantage to another project. |
| 3 |
Closely related to another Project; significantly improves the
efficiency of both Projects. |
F. County Soil Survey Deficiencies. Does the Project address
deficiencies identified in the county soil survey evaluations and/or
digital flags?
| Score |
Criteria |
| 1 |
No deficiencies previously noted; affects newer surveys with 5-digit
numbers. |
| 2 |
Minor deficiencies are addressed; affects published surveys with
mnemonic symbols (e.g., 27B, MeB). |
| 3 |
Significant deficiencies in the existing soil surveys are addressed;
affects “out-of-date” surveys. |
G. Efficiency. How much “bang for the buck” is in this project?
Evaluate, in part, on the ratio of acreage affected to time required to
complete.
| Score |
Criteria |
| 1 |
Low. Lots of work for a few acres; e.g., < 300 acres / person-day. Or,
few and minor NASIS changes per person-day. |
| 2 |
Moderate. Reasonable return for the labor; 300 to 1000 acres /
person-day, numerous NASIS changes per person-day, etc. |
| 3 |
High. Big changes with little effort; >1000 acres / person-day, major
NASIS revisions per person-day, etc. |
Key:
- If (G=3) and (D=3) and (2 or more of A or B or C or F = 3) OR Score =
3 on 3 of A, B, C, or F Then Priority = High
- If (D=1) and (G=1) and (none=3) and (composite score <11) Then
Priority = Low
- All other; Priority = Medium
Example of a Project Plan (Exhibit
608-5)
PROJECT PLAN
Evaluation of MLRA 55A Map Unit F144B
Objective
Evaluate map unit composition of eroded fine-loamy
glacial till found on 3-6 percent slopes in cropland. From determined
composition percentages, a map unit name will be developed and an MLRA
Symbol assigned. A new map unit will potentially be correlated across
MLRA 55A.
Justification and Significance
The eroded fine-loamy till landscape on 3 to 6 percent
slopes is a common feature throughout MLRA 55A (see figure 1). Two map
units have been used to identify this terrain in the past. These map
units are Barnes-Buse 3-6% slopes and Svea-Buse 3-6% slopes. Experience
in the field suggests that these two map units may not correctly
represent the terrain and further study is needed. This correlation is
significant as the above map units exist in thirteen of sixteen counties
in MLRA 55A. These map units encompass a total of 580,000 acres (85% on
cropland) across MLRA 55A and include the Benchmark soils such as the
Barnes Series and Svea Series. These soils are among the most productive
in the state and are extremely important to conservation planning (e.g.
RUSLE II, wind erosion). Future work will potentially include additional
investigations on other map units related to the eroded study, the
progression of erosion to the landscape, the impact of erosion on the
North Dakota Soil Productivity Index, and the impact on MLRA 55B.
Potential Reportable Acres: 25,000 acres
Figure 1. Landscape of Barnes-Buse loams, 3-6% slopes.

Background
Anthropogenic influences, most commonly traditional cultivation
practices in the last 50 years, have had a negative impact to the
fine-loamy till landscapes found on 3 to 6 percent slopes located across
MLRA 55A. Continuous tillage to cropland has accelerated machine, water
and wind erosion and progressively altered dynamic soil properties
commonly found on undisturbed landscapes. In addition to eroding the
tops of rises, the deposition of calcareous material has affected the
down slope portion of productive agricultural lands. Erosion has
noticeably affected cropped landscapes to a point where past soil
correlations may no longer be correct. An investigation on these types
of landscapes and associated map units is needed in order to truly
represent what is happening on the ground.
Benefits
Completion of this project will end in better identifying a
soil-landscape relationship found extensively throughout MLRA 55A. Soils
found on this landscape include Benchmark Soils such as the Barnes
Series and Svea Series. Spatial and tabular data available to users will
be updated. Updated soil interpretations for these cropped landscapes
can lead to better conservation practices being implemented in MLRA 55A.
General Procedure
Locate the eroded fine-loamy till landscapes found on 3 to 6 percent
slopes in cropland across MLRA
55A and identify map units used. Choose representative map units to
investigate. Complete detailed transects of the eroded landscape,
focusing on eroded areas and depositional areas. Select random transects
to be performed. Determine composition
percentages and develop map unit name and assign MLRA Symbol. Identify
map unit trends across MLRA 55A. Correlate the map unit across MLRA 55A.
Needs
Equipment used for this project will include:
- ATV
- Bucket auger
- ArcMap GIS 9.2
- Fujitsu ST5111 Tablet PC
- Transect forms
Duration
| Procedure |
Time Table |
| Office Preparation and Investigation |
10 days |
| Field Investigation |
25 days |
| Summary of Field Work |
5 days |
| Correlation Process |
10 days |
| SSURGO Download of MLRA 55A |
2 days |
| Total |
52 days |
Personnel
- Lance Duey (Soil Scientist): Conducting Field Investigation and
Summary
- Earnie Jensen (MLRA Soil Survey Leader): Quality Control
- Joe Brennan (Soil Scientist/GIS): Assisting in GIS
Applications/Use/Training
- Mike Ulmer (Senior Regional Soil Scientist): Quality Assurance
- County Field Offices: District Conservationists will be
contacted prior to working in a county
Contact Person
Earnie Jensen
MLRA Soil Survey Leader
USDA-NRCS
706 8th Ave SE, Suite 1
Devils Lake, ND 58301
Tele: (701) 662-6283 ext. 135
Earnie.jensen@nd.usda.gov
I. Office Preparation and Investigation
- Reviewing Existing Correlation Documentation
- Historical transect data will be evaluated.
- Review correlation decisions of the eroded fine-loamy till,
3-6% slopes in MLRA 55A.
- Choose map units which will be investigated during the
project.
- Review of Spatial Data
- Evaluate the existing MLRA
legend, and non-updated Non-MLRA
Soil Survey Area legends. Choose map units to be queried using GIS (see chart 1).
Chart 1: MLRA 55A Eroded B-slope Fine-loamy till Map Units
| County
Symbol |
MLRA
Symbol |
Existing Correlated
Map Unit Name |
County |
Total
Acres |
Total Acres
Cropland |
| 118
|
F144B
|
Barnes-Buse loams, 3-6% slopes |
Towner
|
134,715 |
118,093 |
| 11B
|
F144B
|
Barnes-Buse loams, 3-6% slopes |
Nelson
|
49,396 |
37,547 |
12B 11B
|
F144B F154B
|
Barnes-Buse loams, 3-6% slopes Svea-Buse loams 3-6% slopes
|
Cavalier
|
120,058 |
107,278 |
| 130B
|
F144B
|
Barnes-Buse loams, 3-6% slopes |
Grand Forks
|
2,006 |
1,746 |
| 140B
|
F144B
|
Barnes-Buse loams, 3-6% slopes |
Benson
|
51,012 |
43,998 |
| 19B
|
F144B
|
Barnes-Buse loams, 3-6% slopes |
Ramsey
|
74,840 |
64,427 |
| 53B
|
F144B
|
Barnes-Buse loams, 3-6% slopes |
Pierce
|
2,471 |
2,308 |
| BkB2
|
F144B
|
Barnes-Buse loams, 3-6% slopes |
Walsh
|
41,174 |
28,256 |
| 118
|
|
Barnes-Buse loams, 3-6% slopes |
Rolette
|
75,787 |
63,373 |
| 24B
|
|
Barnes-Buse loams, 3-6% slopes |
McHenry
|
22,744 |
19,477
|
| BbB
|
|
Barnes-Buse loams, undulating |
Ward
|
3,210 |
2,985 |
| BdB
|
|
Barnes-Buse loams, 3-6% slopes |
Renville
|
3,023 |
2,695 |
| Total Acres |
|
|
|
580,436 |
492,183 |
- Using ArcMap 9.2 GIS
software, query the eroded fine-loamy till map
units, 3-6% slopes and develop a physiographic map of MLRA 55A
(see figure 2).
Figure 2. Locations of All Eroded Fine-loamy till, 3-6% slope
(cropland and rangeland).

- Review spatial distribution for trends such as map unit
clustering and voids.
- Map units are heavily populated in the Eastern half of
MLRA 55A because Eastern counties have had MLRA
legend
updates
- Map units are thinly populated in the Western half of
MLRA 55A because Western counties have not been updated to a
MLRA legend
- Bottineau County and Pierce County are void of eroded,
fine-loamy till 3 to 6 percent slope map units because
Bottineau County did not recognize an eroded fine-
loamy till map unit on 3 to 6 percent slopes. The eroded
fine-loamy till map unit was correlated on 3 to 9 percent
slopes. Additional investigation needs to be conducted in
Pierce County
- Identify map units that exist only on cropland.
- Choose map units in cropland across MLRA 55A that correctly
represent the landscape and investigate each using techniques
outlined in the project plan.
- Office Evaluation of Ortho-Imagery Photo Tones (see figure 3)
Figure 3. Analysis of Ortho-Imagery Photo Tones

- Analyze photo tones of selected map units and choose areas
for transecting.
- Conclude that three photo tones influence the landscape
- Black = Possible zones of wetness or potholes
- Grey tones = Possible zones of deposition and other
- White tones = Possible zones of erosion
- Determining Photo-Tone Coverage
- What percentage of the map units are white tones?
- What percentage of the map units are black tones?
Who: Duey, Jensen, Brennan When: Spring 2007 Quality Control: Jensen
Quality Assurance: MO-7 Staff
II. Field Investigation
- Transecting
- Choose 10 representative map units and investigate black, grey,
and white photo tones.
- Determine areas to transect.
- Identify soil series and record stops.
- Example of data to be collected:
- Bk depth and thickness
- Bt depth
- Bw depth
- E depth and thickness
- C depth and texture
- 2C depth and texture
- Depth to redox
- Color of redox features
- Percent redox
- Color of soil matrix
- Landscape position
- Soil Series
- Slope shape & percent
- Surface texture
- Surface carbonates depth & thickness
- Mollic epipedon thickness
- Surface carbonate thickness
Who: Duey
When: Summer/Fall 2007, Spring 2008
Quality Control: Jensen
Quality Assurance: MO-7 Staff
III. Summary of Field Investigation
- Review data collected in the field
- Check for inconsistencies, patterns, and/or voids in collected
data.
- Collect additional data if needed.
- Review Ortho-Imagery
- Review transects determine if black, grey, and white areas were
represented in all 10 sites.
- Compare identified Soil Series to ortho-imagery photo tone.
Who: Duey
When: Fall 2007
Quality Control: Jensen
Quality Assurance: MO-7 Staff
IV. Additional Field Investigation
- Application of Transects to Photo-Tone
- Select 20 additional sites across the MLRA and apply knowledge
gained from landscape transects.
- Using photo tone of the Ortho-imagery to identify the soil series
Who: Duey
When: Spring/Summer 2008
Quality Control: Jensen
Quality Assurance: MO-7 Staff
V. Correlation Process
- Component Determination
- Major Component(s)
- Minor Component(s)
- Assigning Map Unit Name and Symbol
- Revise or create new Reference Components
- Changes to WEG (e.g., 5 changes to 4L)
- Select a new map unit name if needed
- Select a new MLRA Symbol if needed
- Add the new MLRA map unit to the MLRA
legend
- Spatially assign MLRA
map unit symbol to counties where the eroded,
fine-loamy till on 3 to 6 percent slopes landscape occur
- Component Data will be entered in NASIS at Level II
- Populate Data Map Unit(s) at Level II
- Validate Data Map Unit(s)
Who: Duey, Jensen
When: Winter/Spring 2008-2009
Quality Control: Jensen
Quality Assurance: MO-7 Staff
VI. SSURGO Download
- Download map unit changes to SSURGO
Who: MO-7 Staff
When: Winter 2008
______________________________
MLRA Soil Survey Leader Signature
______________________________
MO-7 Leader Signature
Annual Plan of Operations for an MLRA
Soil Survey (Exhibit
608-6)
| United States Department of
Agriculture - Natural Resources Conservation Service |
| ____________________________
MLRA SSA, ____________________________ |
| Date ________________________
Project staff _________________________ |
|
|
|
|
|
|
Responsibility of |
Number Amount |
Hours Per Quarter |
FY Total |
|
|
|
|
1 |
2 |
3 |
4 |
|
| Section A: Long-range Plan of
Operation |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1. Collect and analyze references |
|
|
|
|
|
|
|
|
|
a. Geology reports |
|
__________ |
______ |
___ |
___ |
___ |
___ |
______ |
|
b. Flood data |
|
__________ |
______ |
___ |
___ |
___ |
___ |
______ |
|
c. Local history |
|
__________ |
______ |
___ |
___ |
___ |
___ |
______ |
|
d. County road maps |
|
__________ |
______ |
___ |
___ |
___ |
___ |
______ |
|
e. Land use |
|
__________ |
______ |
___ |
___ |
___ |
___ |
______ |
|
f. Water quality info |
|
__________ |
______ |
___ |
___ |
___ |
___ |
______ |
|
|
|
|
|
|
|
|
|
|
| 2. Prepare digital data |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 3. Field studies |
|
|
|
|
|
|
|
|
|
a. Develop landforms map |
|
__________ |
______ |
___ |
___ |
___ |
___ |
______ |
|
b. Draft
initial STATSGO2 update |
|
__________ |
______ |
___ |
___ |
___ |
___ |
______ |
|
|
|
|
|
|
|
|
|
|
| 4. Project area legend |
|
|
|
|
|
|
|
|
|
a. Revise and circulate OSEDs |
|
__________ |
______ |
___ |
___ |
___ |
___ |
______ |
|
b. Review map unit descriptions |
|
__________ |
______ |
___ |
___ |
___ |
___ |
______ |
|
|
|
|
|
|
|
|
|
|
| 5. Documentation and supporting data |
|
|
|
|
|
|
|
|
|
a. Record transects |
|
__________ |
______ |
___ |
___ |
___ |
___ |
______ |
|
b. Yield data |
|
__________ |
______ |
___ |
___ |
___ |
___ |
______ |
|
c. Forest transects |
|
__________ |
______ |
___ |
___ |
___ |
___ |
______ |
|
d. Describe pedons |
|
__________ |
______ |
___ |
___ |
___ |
___ |
______ |
|
e. Analyze transect data |
|
__________ |
______ |
___ |
___ |
___ |
___ |
______ |
|
|
|
|
|
|
|
|
|
|
| 6. Project reviews |
|
|
|
|
|
|
|
|
|
a. Field assistance visit |
|
__________ |
______ |
___ |
___ |
___ |
___ |
______ |
|
b. Completion review |
|
__________ |
______ |
___ |
___ |
___ |
___ |
______ |
|
|
|
|
|
|
|
|
|
|
| Section B: Soil Management and
Interpretations Support Services |
|
|
|
|
|
|
|
|
|
a. Onsite investigations |
|
__________ |
______ |
___ |
___ |
___ |
___ |
______ |
|
b. FOTG coordination |
|
__________ |
______ |
___ |
___ |
___ |
___ |
______ |
|
c. Special evaluations |
|
__________ |
______ |
___ |
___ |
___ |
___ |
______ |
|
|
|
|
|
|
|
|
|
|
| Section C: Information Activities |
|
|
|
|
|
|
|
|
|
a. Talk to service club |
|
__________ |
______ |
___ |
___ |
___ |
___ |
______ |
|
b. Prepare news article |
|
__________ |
______ |
___ |
___ |
___ |
___ |
______ |
|
c. Report to cooperators |
|
__________ |
______ |
___ |
___ |
___ |
___ |
______ |
|
|
|
|
|
|
|
|
|
|
| Section D: Leave and Holiday |
|
|
|
|
|
|
|
|
|
a. Annual leave |
|
__________ |
______ |
___ |
___ |
___ |
___ |
______ |
|
b. Sick leave |
|
__________ |
______ |
___ |
___ |
___ |
___ |
______ |
|
c. Holidays |
|
__________ |
______ |
___ |
___ |
___ |
___ |
______ |
Soil Survey Schedule Guidelines (Exhibit 608-7)
This exhibit provides additional guidance for administering data in NASIS
related to goals and progress reporting. It is primarily intended for
soil survey program managers and data stewards. It is divided into major
soil survey program business areas for ease of reference. Data elements
relevant to the business areas are listed and discussed. Also refer to
Exhibit 608-8, a quick reference companion which
provides a snapshot of business area responsibilities.
Definitions of data elements are in NASIS,
and therefore, are NOT repeated in this document. Additional
explanations are provided for some data elements.
I. PROJECT ADMINISTRATION and ACREAGE MANAGEMENT
Timely administration of Projects and acreage accountability are
critical functions to the usefulness of the NASIS
database as a management tool. Projects serve as “place-holders” to
project future needs, identify progress, and track milestone events
leading to completion of soil survey products.
Guiding Principles for Administration and
Maintenance:
- The tables and data elements related to goals and progress are
imbedded in the NASIS
database, which is a multi-user database. They serve as the official
reporting instrument for production soil survey activities of the
National Cooperative Soil Survey.
- Administration is the responsibility of state offices; updating
maps and data is the responsibility of soil survey business area
data stewards.
- For the initial soil survey, data are maintained in Projects
linked to Non-MLRA
Soil Survey Areas owned by Pangaea.
- Each Non-MLRA
Soil Survey Area will be linked to a Project in NASIS.
All geographic areas of the Nation are covered in at least one
such survey area.
- With the data conversion to NASIS
6.0, a project was created for each legend linked to a Non-MLRA
Soil Survey Area. The resulting project was named for the survey
area and the status shown in the Legend table – e.g. Allen
County, Kansas - Update needed. Data from the Legend data object
related to goals and progress in NASIS
5.4 were moved to this new Project and related tables.
- Mapping progress and milestones may be reported
continuously, but as a minimum, is reported at the end of each
quarter. Other data entries may be maintained continuously, but
as a minimum, are current at the end of each month.
- For update soil survey work, a Project is created for each
project plan developed for the MLRA
Soil Survey Area. This includes extensive revision projects. These
projects are linked to the appropriate MLRA
Soil Survey Area.
- Mapping progress and milestones may be reported
continuously, but as a minimum, is reported at the end of each
quarter. Other data entries may be maintained continuously, but
as a minimum, are current at the end of each month.
- Administrative Data Elements:
- Area table
- Area Name. This data element applies to the Area, Project, Legend, and
Legend Area Overlap tables.
- Area Symbol. This data element applies to the Area, Project, Legend, and
Legend Area Overlap tables.
- Area Acres
- Legend table
- MLRA Office
- MOU Agency Responsible
- Legend Description
- Geographic Applicability. This data element specifies the currency of
soil survey information, including both attribute and spatial data
- Project table
- Project Name
- MLRA Soil Survey
Area Responsible
- State Responsible
- Legend Certification History table
- Legend Certification Status
- Certification Date
- Certification Kind
- Export Certification History table
- Export Certification Status
- Certification Date
- Certification Kind
- Project Product table
- Product Availability Status
- Acreage Management Protocols for Initial Soil Survey Projects linked
to Non-MLRA Soil Survey Areas:
Seven land categories are used to identify the ownership of all lands of the
United States and its Trust Territories. The land categories are: Native
American Land, Other Non-federal Land, Bureau of Land Management, U.S.
Forest Service, National Park Service, Other Federal Land, and Census Water.
Accordingly, acreage is assigned in each project linked to a Non-MLRA
Soil Survey Area, subject to the following conventions:
- Land categories reflect current land ownership as it occurs in the survey
area.
- The sum of all land category acres from all Projects linked to Non-MLRA
Soil Survey Areas in a state equals the 1992 NRI acres for the
state.
- Land category acres are balanced across projects that cover the same
geographic area, such that each acre is recorded only once.
- Survey areas that cover parts of two or more states will have a separate
project for each state. Each project will have land categories, land
category acres, goals, and progress for the respective state. A Non-MLRA
Soil Survey Area will be needed for each state involved. The
area symbol will be assigned for the respective state. The area name will be
the same for both. Area acres will be for the whole survey area, and will be
recorded as the same in each survey area.
- Acres are recorded to the actual acre, or rounded to 100 acres.
- Areas in Alaska identified as “Alaska Native Lands”, or in Hawaii as
“Hawaiian Homelands” are included in the meaning of Native American Land.
- Census Water applies to all contiguous water polygons that are 40 acres
in size or larger. If a water polygon is less than 40 acres in size in the
survey area, but extends into an adjoining survey area such that the total
extent in both survey areas is more than 40 acres, then the water qualifies
as Census Water. Census Water acreage is NOT to be part of mapping goals; it
is administratively managed in NASIS
as a land category in the Project Land Category Breakdown table
to account for total survey acres and progress.
Project Scenarios and Protocols:
- Survey Areas with One Project. Only one project is linked to a Non-MLRA
Soil Survey Area in NASIS,
and no other survey areas have been established that coincide geographically
with any part of the survey area. The actual (or best estimate of) land
category acres are recorded in the Project Land Category Breakdown table.
The sum of all acres recorded in the table are to equal the survey area
acreage.
- Survey Areas with Two or More Projects. These areas typically
have an older out-of-date legend and corresponding project, and a newer
update or published legend and project. Acres in the Project Land Category
Breakdown table should be re-balanced such that the older project shows zero
acres in each land category. The newer project should reflect the actual (or
best estimate of) land category acres in the Project Land Category Breakdown
table, thus land category acres will be recorded only once for the survey
area. Mapping progress should be retained in both the older and newer
Projects as appropriate (see section on mapping goals and progress).
- Survey Areas That Partly Coincide With Another Survey Area(s).
These areas typically consist of a newer survey area that covers part of an
older survey area, or a newer survey that covers all or parts of two or more
previous survey areas. Acres in the Project Land Category Breakdown table
should be re-balanced in all affected survey area projects such that current
land category acres are recorded in the newest project and subtracted from
older projects. The sum of land category acres in the newest project will
equal the survey area acreage. The resulting sum of land category acres in
each of the other affected project will equal less than their respective
survey area acreage. Mapping progress should be retained in both older and
newer projects as appropriate (see section on mapping goals and progress).
- Acreage Management Protocols for Update Soil Survey Projects linked
to Non-MLRA Soil Survey Areas:
Seven land categories are used to identify the ownership of all
lands of the United States and its Trust Territories. The land categories
are: Native American Land, Other Non-federal Land, Bureau of Land
Management, U.S. Forest Service, National Park Service, Other Federal Land,
and Census Water. Accordingly, acreage is assigned in each project linked to
a Non-MLRA
Soil Survey Area, subject to the following conventions:
- Land categories reflect current land ownership as it occurs in the survey
area.
- For each such project developed, the appropriate land category(s) and
acres will be entered into the Project Land Category Breakdown table.
- As these projects stand on their own and the same acre of land may be
covered by more than one project, there is no need to balance land category
acres across projects or within a state. The same acre may be reported as
being updated more than once.
- Acres are recorded to the actual acre, or rounded to 100 acres.
- Areas in Alaska identified as “Alaska Native Lands”, or in Hawaii as
“Hawaiian Homelands” are included in the meaning of Native American Land.
- Census Water applies to all contiguous water polygons that are 40 acres
in size or larger. If a water polygon is less than 40 acres in size in the
survey area, but extends into an adjoining survey area such that the total
extent in both survey areas is more than 40 acres, then the water qualifies
as Census Water. Census Water acreage is NOT to be part of mapping goals; it
is administratively managed in NASIS
as a land category in the Project Land
Category Breakdown table to account for total survey acres and progress.
II. MAPPING GOALS and PROGRESS
Goals and progress are recorded in the Project Mapping Goal and
Project
Mapping Progress tables for each defined project. Goals and progress may be
recorded for each individual project staff member or for the
project staff as a whole. Use the following protocols:
- Project Staff. First, enter individual project member names
in the Project Staff table before entering goals or progress. A
choice list is provided based on NASIS
User names. If a name is needed for the whole staff, contact the
Soils Hotline to have the name added to the NASIS
User table.
- Goals. Enter fiscal year goals in the Project Mapping
Goal table at the beginning of each fiscal year.
- Progress. Enter mapping progress and show the effective
progress reporting date in the Project Mapping Progress table under
the appropriate land category. NOTE: The reporting date determines
the fiscal year for progress reporting. Show initial and update
mapping under NRCS or cooperator columns, as appropriate. Update
acres may be reported in any Project where update activity has
occurred.
- Progress. Once initial soil survey mapping progress has
been reported in a Project, that progress should not be moved to
another Project, unless an error was made in data entry. However, in
order to show the current progress for all land categories, progress
may need to be re-allocated among land categories within the same
Project to reflect any changes in land ownership. NOTE: For
situations where land category acres have been re-balanced across
Projects, acres of mapping progress reported for a land category may
be more than the land category acres shown for that Project, and in
some cases the land category acres may even be zero.
- GOAL SETTING - Project Mapping Goal table
- Fiscal Year
- Initial NRCS Acres Goal
- Initial Cooperator Acres Goal
- Update NRCS Acres Goal
- Update Cooperator Acres Goal
- Staff Member
- REPORTING MAPPING PROGRESS - Project Mapping Progress table
- Progress Reporting Date
- Initial NRCS Acres
- Initial Cooperator Acres
- Update NRCS Acres
- Update Cooperator Acres
- Staff Member
INITIAL ACRES. This refers to mapping a soil survey
area and reporting progress for the first time. The cumulative initial
acres reported for a completed survey area always equals 100% of the
survey area acres. This applies to all lands of the Nation, and mapping
by both NRCS
and cooperator personnel, and it applies to mapping at any order of
detail or scale. Typically, initial acres are reported only for surveys
having a non-project or initial status, but may apply to surveys with
update status where areas that were not mapped during the initial survey
are mapped and reported for the first time. Initial Acres are reported
only once for a given geographic area. All subsequent mapping on the
same ground is reported as update acres.
UPDATE ACRES. This refers to re-mapping, or updating on
parts or all of a survey area and reporting progress on acres previously
reported. The cumulative update acres for a survey area may exceed 100%
of the survey area acres. This applies to all lands of the Nation, and
mapping by both NRCS and cooperator personnel, and it applies to mapping
at any order of detail or scale.
III. IMAGERY, ORTHOPHOTOGRAPHY, MAP COMPILATION MATERIALS, AND OTHER
DATA LAYERS
These data elements are primarily the responsibility of state offices in
their administrative and liaison capacity between MLRA Soil Survey Regional
Offices
and National Cooperative Soil Survey partners within a state. Field
imagery, orthophotography, and map compilation materials may be needed
for project survey operations, or SSURGO initiatives.
Acquisition of field imagery, orthophotography, map compilation
materials, and other digital data layers is coordinated with the National Cartography and Geospatial
Center. Development of new imagery and orthophotography, along with
related funding and cost-share issues, is coordinated with the National
Office. The primary source of new orthophotography development is
through the National Agricultural Imagery Program (NAIP).
Beginning in NASIS
6.0 these needs are recorded in the Project Data Need table.
Each type of product or data needed is to be recorded on a separate row
in the Project Data Type column using the choice list provided.
Applicable dates are to be recorded in the “date” columns.
- Project Data Need table
- Project Data Type
- Date Needed
- Date Ordered
- Date Received
IV. INITIAL and UPDATE SURVEY OPERATIONS
These data elements relate most directly to production soil survey
operations, and therefore, are the responsibility of MLRA Soil Survey Regional
Offices. Data elements relative to the memorandum of understanding for
project areas and product types are jointly shared by state offices and MLRA
Soil Survey
Regional Offices.
- ADMINISTRATIVE and FIELD ACTIVITIES
- Legend table
- MOU Signed
- MOU Projected Completion
- Project Scale. Standard National map scales are 1:12,000 in quarter
quad format or 1:24,000 in full quad format. Puerto Rico is approved for
1: 20,000 and Alaska is approved for 1: 25,000; any other scale and/or
format must be approved by the Director, Soil Survey Division, prior to
development of the long range plan for the survey area.
- Project Field Review table
- Correlation Event = “Initial Field Review”
- Correlation Event = “Final Field Review”
- Date = date of the respective correlation event report
- Project table
- English Edit Site
- Digital Map Finishing Site
- Digitizing Unit
- MAP COMPILATION
- Project Milestone table
- Milestone Type Name = “Map Compilation”
- Milestone Date Started = date compilation project was started
- Milestone Date Completed = date compilation project was
completed
- Milestone Type Name = “Map Compilation Certification”
- Milestone Date Completed = date of certification
- Project Milestone Progress table
- Milestone Progress Amount
- Milestone Progress Unit = “percent”
- MAP FINISHING
- Project Table
- Map Finish Method. Choices are digital (preferred) and manual.
- Project Milestone table
- Milestone Type Name = “Digital map finishing”
- Milestone Date Started = date map finishing project was started
- Milestone Date Completed = date map finishing project was
completed
- Project Milestone Progress table
- Milestone Progress Amount
- Milestone Progress Unit = “percent”
- Project Milestone table
- Milestone Type Name = “Maps to NCGC”
- Milestone Date Started = date map finishing project was sent to
NCGC
- Milestone Date Completed = date map finishing project was
received at NCGC
- Milestone Type Name = “Maps to printer”
- Milestone Date Completed = date finished maps were sent to
printer
- SSURGO DIGITIZING, CERTIFICATION, and ARCHIVING
SSURGO
Operations. As part of the National Cooperative Soil Survey, a
SSURGO
database is to be developed for all areas. The Soil Survey Division
coordinates with
NCGC in
SSURGO
database development; states have responsibility for recompilation
of soil survey maps; MLRA
Soil Survey Regional Offices have soil business responsibility for
correlation, for map compilation quality assurance, and for
digitizing quality assurance; and digitizing units have
responsibility for digitizing and for certification review. The
dataset is archived in the Soil Data Warehouse and delivered via the
Soil Data Mart, Web Soil Survey and Geospatial Data Gateway. Quality
assurance of the SSURGO
product is completed at the National Cartography and Geospatial
Center.
SSURGO
Progress Reporting. Progress and status for
SSURGO
development are tracked continuously in
NASIS
and the Soil Data Mart. Business areas with responsibilities for
SSURGO
development also have responsibility to populate the appropriate
data elements in NASIS;
refer to Exhibit 608-7, Business Area Responsibilities for Goals and
Progress. Data stewards are designated to insure timely and accurate
progress reporting.
SSURGO
Certification. After
SSURGO
data has passed a certification review by the digitizing unit, and
all paper work and quality assurance is completed by the
MLRA
Soil Survey Regional Office, the survey is certified as meeting
SSURGO
standards by the responsible
MLRA
Soil Survey Regional Office leader and the state conservationist.
These data elements are the primary responsibility of the
digitizing units and the National Cartography and Geospatial Center.
If actual digitizing is not done by the designated digitizing unit,
states have responsibility to populate digitizing started,
digitizing percent, and digitizing completed prior to sending the
job to the digitizing unit for certification review. Dates and
progress for the following milestones are recorded in the Project
Milestone and Project Milestone Progress tables as outlined in
Exhibit 608-8.
- Project Milestone table
- Milestone Type Name = “Digitize maps”
- Milestone Date Started = Date the digitizing was started. For
completed surveys the correlation document, compilation
certification, and attribute data are on file at the office doing
the digitizing is started, or correspondence granting an exception
is on file from the MLRA
Soil Survey Regional Office.
- Milestone Date Completed = Date the digitizing was completed.
Quality control work by the state or the digitizing unit, and
quality assurance by the MLRA
Soil Survey Regional Office, is normally done after the digitizing
is complete, and before the
SSURGO
review is started.
- Project Milestone Progress table
- Milestone Progress Amount
- Milestone Progress Unit = “percent”
- Project Milestone table
- Milestone Type Name = “SSURGO
Digital review”
- Milestone Date Started = Date the digital review was started.
- Milestone Type Name = “SSURGO
Certification”
- Milestone Date Completed = Date the
SSURGO
dataset was certified.
- Milestone Type Name = “SSURGO
Archived”
- Milestone Date Completed = Date the
SSURGO
dataset was archived.
- MANUSCRIPT and PRODUCT DEVELOPMENT
- Manuscript Technical Edit and Review
- Project Milestone table
- Milestone Type Name = “Technical Edit”
- Milestone Date Started = Date the technical edit was
started
- Milestone Date Completed = Date the technical edit was
completed
- English Edit
- Project Milestone table
- Milestone Type Name = “English edit received”
- Milestone Date Completed = date the manuscript was
received by the editor
- Project Milestone table
- Milestone Type Name = “English Edit”
- Milestone Date Started = Date the English edit was
started
- Milestone Date Completed = Date the English edit was
completed
- Project Milestone table
- Milestone Type Name = “Text received at
NCGC”
- Milestone Date Completed = date the manuscript was
received by
NCGC
- Project Milestone table
- Milestone Type Name = “Text to printer”
- Milestone Date Completed = date the manuscript was sent
to the printer
- Products Data Elements
- Project Product table
- Product Type. Six final product types are available from
a choice list. All that apply for a survey area are
identified according to their publication date. Choices are:
- Interim Report
- Soil Attribute/Spatial on CD-ROM
- Soil Survey Report on CD-ROM
- Three Ring Bound Manuscript
- Traditional Bound Manuscript
- Web Publication
- Product Description
- Scheduled Delivery (date)
- Actual Delivery (date)
- Availability Status
Business Area
Responsibilities for Goals and Progress (Exhibit
608-8)
I. PROJECT ADMINISTRATION and ACREAGE MANAGEMENT
A. Administration
| NASIS
Table Name |
Data Element |
State
Office |
MLRA
Office |
NSSC |
NHQ |
DU |
DMF |
NCGC |
|
area |
area name |
X |
|
X |
|
|
|
|
| area |
area symbol |
X |
|
X |
|
|
|
|
| area |
area acres |
X |
|
X |
|
|
|
|
| legend |
mlra office |
|
X |
|
|
|
|
|
| legend |
mou agency responsible |
X |
X |
|
|
|
|
|
| legend |
legend description |
X |
X |
|
|
|
|
|
| legend |
geographic applicability |
X |
|
|
|
|
|
|
| legend certification history |
legend certification status |
X |
|
|
|
|
|
|
| legend certification history |
certification date |
X |
|
|
|
|
|
|
| legend certification history |
certification kind |
X |
|
|
|
|
|
|
| legend certification history |
export certification status |
X |
|
|
|
|
|
|
| legend certification history |
certification date |
X |
|
|
|
|
|
|
| legend certification history |
certification kind |
X |
|
|
|
|
|
|
| project |
project name |
X |
X |
|
|
|
|
|
| project |
project description |
X |
X |
|
|
|
|
|
| project |
mlra soil survey office area responsible |
X |
X |
|
|
|
|
|
| project |
state responsible |
X |
X |
|
|
|
|
|
| project product |
product availability status |
X |
|
|
|
|
|
|
| project data type |
project data type name |
|
|
X |
|
|
|
|
| project data type |
project data type description |
|
|
X |
|
|
|
|
| milestone type |
milestone type name |
|
|
X |
|
|
|
|
| milestone type |
milestone type description |
|
|
X |
|
|
|
|
| technical soil service type |
technical soil service type name |
|
|
X |
X |
|
|
|
| technical soil service type |
technical soil service type description |
|
|
X |
X |
|
|
|
B. Acreage Management
| NASIS
Table Name |
Data Element |
State
Office |
MLRA
Office |
NSSC |
NHQ |
DU |
DMF |
NCGC |
| legend area overlap |
area overlap acres |
X |
X |
|
|
|
|
|
| project land category breakdown |
project land category acres |
X |
X |
|
|
|
|
|
| project land category breakdown |
project land category |
X |
X |
|
|
|
|
|
II. MAPPING GOALS and PROGRESS
A. Goal Setting
| NASIS
Table Name |
Data Element |
State
Office |
MLRA
Office |
NSSC |
NHQ |
DU |
DMF |
NCGC |
| project staff |
staff member name |
X |
X |
|
|
|
|
|
| project mapping goal |
staff member name |
X |
X |
|
|
|
|
|
| project mapping goal |
fiscal year |
X |
X |
|
|
|
|
|
| project mapping goal |
initial nrcs acres goal |
X |
X |
|
|
|
|
|
| project mapping goal |
initial cooperator acres goal |
X |
X |
|
|
|
|
|
| project mapping goal |
update nrcs acres goal |
X |
X |
|
|
|
|
|
| project mapping goal |
update cooperator acres goal |
X |
X |
|
|
|
|
|
B. Reporting Mapping Progress
| NASIS
Table Name |
Data Element |
State
Office |
MLRA
Office |
NSSC |
NHQ |
DU |
DMF |
NCGC |
| project mapping progress |
staff member name |
X |
X |
|
|
|
|
|
| project mapping progress |
progress reporting date |
X |
X |
|
|
|
|
|
| project mapping progress |
initial nrcs acres |
X |
X |
|
|
|
|
|
| project mapping progress |
initial cooperator acres |
X |
X |
|
|
|
|
|
| project mapping progress |
update nrcs acres |
X |
X |
|
|
|
|
|
| project mapping progress |
update cooperator acres |
X |
X |
|
|
|
|
|
III. IMAGERY, ORTHOPHOTOGRAPHY, MAP COMPILATION MATERIALS, and OTHER DATA
LAYERS
A. Field Imagery
| NASIS
Table Name |
Data Element |
State
Office |
MLRA
Office |
NSSC |
NHQ |
DU |
DMF |
NCGC |
| project data need |
project data type = “field imagery” |
X |
|
|
|
|
|
|
| project data need |
date needed |
X |
|
|
|
|
|
|
| project data need |
date ordered |
|
|
|
|
|
|
X |
| project data need |
date received |
X |
|
|
|
|
|
|
B. Orthophotography
| NASIS
Table Name |
Data Element |
State
Office |
MLRA
Office |
NSSC |
NHQ |
DU |
DMF |
NCGC |
| project data need |
project data type = “digital orthophoto quads” |
X |
|
|
|
|
|
|
| project data need |
date needed |
X |
|
|
|
|
|
|
| project data need |
date ordered |
|
|
|
X |
|
|
X |
| project data need |
date received |
X |
|
|
|
|
|
|
C. Compilation Materials
| NASIS
Table Name |
Data Element |
State
Office |
MLRA
Office |
NSSC |
NHQ |
DU |
DMF |
NCGC |
| project data need |
project data type = “compilation materials” |
X |
|
|
|
|
|
|
| project data need |
date needed |
X |
|
|
|
|
|
|
| project data need |
date ordered |
|
|
|
|
|
|
X |
| project data need |
date received |
X |
|
|
|
|
|
|
IV. INITIAL and UPDATE SURVEY OPERATIONS
A. Administrative and Field Activities
| NASIS
Table Name |
Data Element |
State
Office |
MLRA
Office |
NSSC |
NHQ |
DU |
DMF |
NCGC |
| legend |
mou signed |
X |
X |
|
|
|
|
|
| legend |
mou projected completion |
X |
X |
|
|
|
|
|
| legend |
project scale |
X |
X |
|
|
|
|
|
| project field review |
correlation event = “initial field review” |
|
X |
|
|
|
|
|
| project field review |
date |
|
X |
|
|
|
|
|
| project field review |
correlation event = “final field review” |
|
X |
|
|
|
|
|
| project field review |
date |
|
X |
|
|
|
|
|
| project |
dmf site |
|
|
X |
X |
|
X |
|
| project |
english edit site |
|
X |
X |
X |
|
|
|
| project |
digitizing unit |
|
X |
|
X |
|
|
|
B. Map Compilation
| NASIS
Table Name |
Data Element |
State
Office |
MLRA
Office |
NSSC |
NHQ |
DU |
DMF |
NCGC |
| project milestone |
milestone type = “map compilation” |
|
X |
|
|
|
|
|
| project milestone |
milestone date started |
|
X |
|
|
|
|
|
| project milestone progress |
milestone progress amount |
|
X |
|
|
|
|
|
| project milestone progress |
milestone progress unit = “percent” |
|
X |
|
|
|
|
|
| project milestone |
milestone date completed |
|
X |
|
|
|
|
|
| project milestone |
milestone type = “map compilation certification” |
|
X |
|
|
|
|
|
| project milestone |
milestone date completed |
|
X |
|
|
|
|
|
C. Map Finishing
| NASIS
Table Name |
Data Element |
State
Office |
MLRA
Office |
NSSC |
NHQ |
DU |
DMF |
NCGC |
| project |
map finish method |
|
X |
|
|
|
|
|
| project milestone |
milestone type = “digital map finishing” |
|
X |
|
|
|
X |
|
| project milestone |
milestone date started |
|
X |
|
|
|
X |
|
| project milestone progress |
milestone progress amount |
|
X |
|
|
|
X |
|
| project milestone progress |
milestone progress unit = “percent” |
|
X |
|
|
|
X |
|
| project milestone |
milestone date completed |
|
X |
|
|
|
X |
|
| project milestone |
milestone type = “maps to ncgc” |
|
X |
|
|
|
X |
|
| project milestone |
milestone date started |
|
X |
|
|
|
X |
|
| project milestone |
milestone date completed |
|
X |
|
|
|
X |
|
| project milestone |
milestone type = “maps to printer” |
|
|
|
|
|
|
X |
| project milestone |
milestone date completed |
|
|
|
|
|
|
X |
D. SSURGO Digitizing, Certification, and Archiving
| NASIS
Table Name |
Data Element |
State
Office |
MLRA
Office |
NSSC |
NHQ |
DU |
DMF |
NCGC |
| project milestone |
milestone type = “digitize maps” |
|
X |
|
|
|
|
|
| project milestone |
milestone date started |
|
|
|
|
X |
|
|
| project milestone progress |
milestone progress amount |
|
|
|
|
X |
|
|
| project milestone progress |
milestone progress unit = “percent” |
|
|
|
|
X |
|
|
| project milestone |
milestone date completed |
|
|
|
|
X |
|
|
| project milestone |
milestone type = “ssurgo digital review” |
|
|
|
|
X |
|
|
| project milestone |
milestone date started |
|
|
|
|
X |
|
|
| project milestone |
milestone type = “ssurgo certification” |
|
|
|
|
X |
|
|
| project milestone |
milestone date completed |
|
|
|
|
X |
|
|
| project milestone |
milestone type = “ssurgo archived” |
|
|
|
|
|
|
X |
| project milestone |
milestone date completed |
|
|
|
|
|
|
X |
E. Manuscript and Project Development
1. Technical Edit and Review
| NASIS
Table Name |
Data Element |
State
Office |
MLRA
Office |
NSSC |
NHQ |
DU |
DMF |
NCGC |
| project milestone |
milestone type = “technical edit” |
|
X |
|
|
|
|
|
| project milestone |
milestone date started |
|
X |
|
|
|
|
|
| project milestone |
milestone date completed |
|
X |
|
|
|
|
|
| project milestone |
milestone type = “technical review” |
|
X |
|
|
|
|
|
| project milestone |
milestone date completed |
|
X |
|
|
|
|
|
2. English Edit
| NASIS
Table Name |
Data Element |
State
Office |
MLRA
Office |
NSSC |
NHQ |
DU |
DMF |
NCGC |
| project |
english edit site |
|
X |
X |
|
|
|
|
| project milestone |
milestone type = “english edit received” |
|
X |
|
|
|
|
|
| project milestone |
milestone date completed |
|
X |
|
|
|
|
|
| project milestone |
milestone type = “english edit” |
|
X |
|
|
|
|
|
| project milestone |
milestone date started |
|
X |
|
|
|
|
|
| project milestone |
milestone date completed |
|
X |
|
|
|
|
|
| project milestone |
milestone type = “text received at ncgc” |
|
|
|
|
|
|
X |
| project milestone |
milestone date completed |
|
|
|
|
|
|
X |
| project milestone |
milestone type = “text to printer” |
|
|
|
|
|
|
X |
| project milestone |
milestone date completed |
|
|
|
|
|
|
X |
3. Products
| NASIS
Table Name |
Data Element |
State
Office |
MLRA
Office |
NSSC |
NHQ |
DU |
DMF |
NCGC |
| project product |
product type |
X |
X |
|
|
|
|
|
| project product |
product description |
X |
X |
|
|
|
|
|
| project product |
product scheduled |
|
X |
|
|
|
|
|
| project product |
product delivered |
X |
|
|
|
|
|
X |
| project product |
product availability status |
X |
|
|
|
|
|
|
< Back to Part 608
Contents
| |
|