![](media/image1.png){width="6.495833333333334in"
height="0.5993055555555555in"}

Natural Resources Conservation Service

Southern Rocky Mts. Regional Soil Survey Office

655 Parfet Street

Lakewood, CO 80215

**MLRA OFFICE 6 TECHNICAL NOTE NO. 8 Updated:** January 25, 2008

**(2008 Reissue)**

**SUBJECT:** SOI -- Suggested Order and Guidelines for Populating a New
Map Unit in

> NASIS

[Purpose.]{.underline} To transmit instructions and worksheets for
populating data for a new map unit in NASIS.

[Effective Date.]{.underline} This technical note is effective when
received. Previous versions should be discarded.

[Background.]{.underline} This tech note was originally issued in 2004.
It has been updated in 2008 to reflect changes to the NASIS database.
The attached tech note provides guidance on the orderly approach to
populating data into NASIS for a new map unit, including how and when to
run "calculations and validations." Guidance on populating landforms and
ecological site data that was originally included in the 2004 version is
not included in this version. In addition, the blank data entry
worksheets included in 2004 version have not been included with the 2008
updated release. This reissued instruction is based upon the NASIS 5.4
version in existence at the time of release.

[Filing Instructions.]{.underline} File after MLRA Office 7 Technical
Note No. 7. Discard the previous tabulation sheet and insert the current
tabulation sheet.

![](media/image2.jpeg){width="2.7597222222222224in"
height="0.9847222222222223in"}

STEVE PARK

MLRA Team Leader

Attachment

DIST: All MO6 Soil Scientists

**MLRA OFFICE 6 TECHNICAL NOTE SERIES**

###### TABULATION SHEET

+---------+--------+------------------------------------+-------------+
| **TECH  | #      | #                                  | ##          |
| NOTE**  |  ISSUE |                                    |             |
|         |        | # TITLE                            | ## COMMENTS |
| **NO.** | **     |                                    |             |
|         | DATE** |                                    |             |
+---------+--------+------------------------------------+-------------+
|         |        |                                    |             |
+---------+--------+------------------------------------+-------------+
| 1       | 22-    | Key to the Use of Cation-Exchange  |             |
|         | May-97 | Activity Classes                   |             |
+---------+--------+------------------------------------+-------------+
|         |        |                                    |             |
+---------+--------+------------------------------------+-------------+
| 2       | 20-    | Identification and Description of  | ###         |
|         | Apr-98 | Albic Horizons, Glossic            |             |
|         |        | Horizons,\...                      |             |
+---------+--------+------------------------------------+-------------+
|         |        |                                    |             |
+---------+--------+------------------------------------+-------------+
| 3       | 2-     | Template for Taxonomic Unit        | Made        |
|         | Feb-99 | Descriptions                       | obsolete by |
|         |        |                                    | Feb 2004    |
|         |        |                                    | Reissue     |
+---------+--------+------------------------------------+-------------+
|         | 3-     | NASIS Reports and Instructions for | Reissue of  |
|         | Feb-04 | Generating Taxonomic Unit          | Tech Note 3 |
|         |        | Descriptions                       | dated Feb   |
|         |        |                                    | 1999        |
+---------+--------+------------------------------------+-------------+
|         |        |                                    |             |
+---------+--------+------------------------------------+-------------+
| 4       | 14-    | Metric-English Conversion Guides   |             |
|         | Jun-99 |                                    |             |
+---------+--------+------------------------------------+-------------+
|         |        |                                    |             |
+---------+--------+------------------------------------+-------------+
| 5       | 30-    | Macro to Format Map Unit           |             |
|         | Mar-00 | Descriptions                       |             |
+---------+--------+------------------------------------+-------------+
|         |        |                                    |             |
+---------+--------+------------------------------------+-------------+
| 6       | 30-    | Report to Generate Map Unit        |             |
|         | Mar-00 | Descriptions in NASIS              |             |
+---------+--------+------------------------------------+-------------+
|         |        |                                    |             |
+---------+--------+------------------------------------+-------------+
| 7       | 24-    | Guidelines for Populating Slope    |             |
|         | Aug-04 | Aspect in NASIS                    |             |
+---------+--------+------------------------------------+-------------+
|         |        |                                    |             |
+---------+--------+------------------------------------+-------------+
| 8       | 16-    | Suggested Order and Guidelines for | Made        |
|         | Sep-04 | Populating a New Map Unit in NASIS | obsolete by |
|         |        |                                    | updated     |
|         |        |                                    | 2008        |
|         |        |                                    | version.    |
+---------+--------+------------------------------------+-------------+
|         | 25-    | Suggested Order and Guidelines for | Update 2008 |
|         | Jan-08 | Populating a New Map Unit in NASIS | version to  |
|         |        |                                    | account for |
|         |        |                                    | NASIS       |
|         |        |                                    | changes.    |
+---------+--------+------------------------------------+-------------+
|         |        |                                    |             |
+---------+--------+------------------------------------+-------------+
| 9       | 18 Oct | Guidelines for Populating Surface  | Correction  |
|         | 05     | Organic Layers in NASIS            | to previous |
|         |        |                                    | guide (was  |
|         |        |                                    | not a-Tech  |
|         |        |                                    | Note)       |
+---------+--------+------------------------------------+-------------+
|         |        |                                    |             |
+---------+--------+------------------------------------+-------------+
| 10      | 5      | Guidelines for Estimating and      |             |
|         | April  | Interpreting Carbonate Clay        |             |
|         | 07     |                                    |             |
+---------+--------+------------------------------------+-------------+
|         |        |                                    |             |
+---------+--------+------------------------------------+-------------+
| 11      | 25-    | Guide for Populating Horizons with |             |
|         | Jan-08 | Stratified Textures                |             |
+---------+--------+------------------------------------+-------------+
|         |        |                                    |             |
+---------+--------+------------------------------------+-------------+
|         |        |                                    |             |
+---------+--------+------------------------------------+-------------+
|         |        |                                    |             |
+---------+--------+------------------------------------+-------------+
|         |        |                                    |             |
+---------+--------+------------------------------------+-------------+

**SUGGESTED ORDER AND GUIDELINES FOR POPULATING**

**A NEW MAP UNIT IN NASIS**

The primary purpose of this tech note is to provide guidance for the
necessary sequential population, calculation, and validation of NASIS
data. Although the guidance is focused on populating a new map unit from
scratch it does serve as a guide for editing previously populated map
units.

Prior to populating a map unit in NASIS, it is critical that
documentation for a component has been collected, compiled, and
analyzed, and that a representative pedon has been selected to provide
data population RV values for the map unit component. It is vital that
the range of component properties values used are representative of the
datamapunit, and do not include ranges from other map units. Refer to
the MO6 guidance document named, "Policy on Using Unique NASIS Pedons"
for more detailed guidance on this issue.

This suggested order is based on the assumption that the Area and Legend
Tables have already been populated. As you populate data it is strongly
recommended that you save your data frequently. You can open a new row
in any table by clicking anywhere in that table and pressing "F8." As
one becomes more proficient with NASIS one can make use of "Copy and
Paste" functionality which eliminates some of the manual entry process.
This document is intended for new users to NASIS. It is based on the
NASIS 5.4 Version in place in January 2008.

The order below also includes the sequence of NASIS Calculations and
Validations that should be run. It also includes a list of reports that
compares populated values against a calculated value. Both calculations
and validations can be run on one or more records. Beginning NASIS users
should run calculations and validations on one, or very few, records. As
more proficiency is gained one can run calculations and validations on
larger sets of records. It should be noted that, typically, validations
should not be run until all the basic properties have been populated and
all the calculations have been run. It is critical that calculations and
validations be run in sequential order.

It should be noted that a calculation should not be used in lieu of
representative lab data that is accurate and complete. If a pedon has
representative lab data available you should use the lab data values
rather than relying on calculated values. However, calculations that
have been sanctioned nationally should be used when actual lab data is
not available.

When populating data you may need to copy data from one cell to the
other. Following is a sequence of keystrokes that shows you how to copy
from one cell to the other:

1.  Click in the cell you want to copy - hold the Ctrl key down then
    press Insert one time.

2.  Click in the cell where you want to paste -- hold the Shift key down
    then press Insert one time, release Shift key and press Enter key
    one time.

Following is some guidance on when to use "null" values. "Null" implies
that the property has not been evaluated or is not applicable. A "0" or
"None" entry implies the property was evaluated and it is absent. For
example, a horizon is tested/evaluated for gypsum and it is determined
gypsum is not present. The correct entry for percent gypsum would be
"0". A "null" entry for gypsum would imply the horizon was never tested
or evaluated for the presence of gypsum. Conversely, data elements such
as pH CaCl~2~ or Free Iron are not normally measured, or are not
applicable for many soils. A "null" entry for such elements would be
appropriate for many soils.

Begin:

1.  Load Selected Set (Area and Legend Only)

    a.  Start NASIS

    b.  Run MO6 Query named "Major Components by Area Name (Non-MLRA
        Only)." Set target tables to Area and Legend. Type in Area Name
        and select status. The MO6 Query named "Major Components by
        SSAID (Non-MLRA Only)" can also be used to load a selected set
        using the SSAID rather than the area name.

2.  Mapunit Table

    a.  Open a row in Mapunit Table. Enter Mapunit Symbol, Name, Kind,
        and status of "provisional." Enter total acres if known. If this
        is a point or linear map unit then enter width and area.

    b.  Run the calculation named "Mapunit Name Capitalization."

    c.  Click "Save."

3.  Mapunit Area Overlap Table

    a.  This table is populated by copying a map unit from the
        Legend-Mapunit table, selecting the appropriate Area-Type-Name
        from the Legend Area Overlap table, then doing a \"down table\"
        (click on orange down table arrow) to the Mapunit Area Overlap
        table, and then pasting the copied map unit into the Mapunit
        Area Overlap table. The acres are not copied over so you will
        need to populate the correct acres for that overlap table.
        However, acres can be copied and pasted from one overlap table
        to another (i.e. from State to MLRA or County). Most of the time
        a map unit will need to be pasted at least 3 times. Once for the
        State, at least once for the county, and once for the MLRA. Map
        units with \"additional\" status should not be pasted into the
        overlap tables. If the map unit occurs in more than one county
        it will need to be pasted into all the appropriate county
        overlap tables. Refer to the MO6 Guidance Document named
        "Populating Acres in the Legend Area Overlap Tables" for more
        detailed instruction.

    b.  Click "Save."

4.  Data Mapunit Table

    a.  Go to Data Mapunit Table, open a row.

    b.  Type in DMU Description. The DMU Description should follow the
        format: "SSAID-Map unit Symbol". For example, 680001 or 680Mf.

    c.  Enter the Order in the "Order of Mapping" element,

5.  The DMU created in step 4 needs to be linked to the map unit created
    in step 2. This linkage is stored in the Correlation Table. The
    steps for creating this linkage are:

    a.  Click anywhere on the DMU created in step 4 and then click
        \"Copy\"

    b.  Go back to Mapunit Table and click on the corresponding map unit
        created in step 2.

    c.  Do a \"down\" table to the Correlation table.

    d.  Click anywhere in the Correlation table and then click "Paste."

    e.  Make sure Rep DMU is \"yes."

    f.  Click "Save."

6.  Component Table. This table contains many data elements. To make it
    easier to input similar types of data it is suggested you use edit
    setups.

    a.  Change edit setup to "6MO Component Data Entry Setup 1."
        Populate the pertinent data elements shown in this setup.

    b.  Run calculation named "Component Name Capitalization."

    c.  Change edit setup to "6MO Classification Edit Setup." Enter
        classification data except Taxonomic Class. Make sure the
        Component Taxonomic Family Mineralogy Table, Component Taxonomic
        Family Other Table, and the Component Taxonomic Moisture Class
        Table are also populated. Calculate the Taxonomic Class by
        clicking in the "Taxonomic Class" element, then clicking
        "Options-Calculate Data Elements-Taxonomic Classification."

    d.  Click on "Save."

    e.  Change the edit setup back to the default setup by clicking
        "Options-Change Edit Setup-National-Default."

7.  Other Component Child Tables. There are many other Component Child
    Tables that may need to be populated. Which ones are populated is
    dependant on the survey area and the map unit's land use. Below is a
    list of those tables.

    a.  Parent Material and Parent Material Group

    b.  Diagnostic Features

    c.  Restrictions. Note---The Top Depth RV value in the Component
        Restrictions Table must match the Top Depth RV value of that
        restrictive layer in the Horizon Table. For example, a bedrock
        (R layer) occurs at 60 cm in the typical profile. The Top Depth
        RV value in the Component Restrictions Table must also be 60 cm.

    d.  Surface Fragments (if present.) See item 10 for additional
        instructions.

    e.  Month -- This table must be populated even if flooding or
        ponding do not occur. The table must have all 12 months entered.
        If flooding or ponding do not occur then enter "None" for
        flooding and ponding frequency for every month. Frequency is
        defined on an annual basis not a monthly basis. If a soil is
        occasionally flooded then "occasional" gets populated in every
        month that floods. (Note -- The easiest way to populate a blank
        Month Table for soils that do not flood or pond is to copy the
        Month Table from a soil that also does not flood or pond and has
        already been populated.)

    f.  Soil Moisture (if water table present). This table is populated
        for every month in which a water table is present. Top Depth (L,
        RV, H), Bottom Depth (L, RV, H), and Moisture Status required.
        Examples of endosaturation and episaturation are:

> Endosaturation

  ---------- ---------- ---------- ---------- ---------- ---------- ----------
  Top Depth                        Bottom                           Moisture
                                   Depth                            Status

  L          RV         H          L          RV         H          

  0          0          0          30         46         61         moist

  30         46         61         203        203        203        wet
  ---------- ---------- ---------- ---------- ---------- ---------- ----------

> Episaturation

  ---------- ---------- ---------- ---------- ---------- ---------- ----------
  Top Depth                        Bottom                           Moisture
                                   Depth                            Status

  L          RV         H          L          RV         H          

  0          0          0          30         46         61         dry

  30         46         61         76         102        127        wet

  76         102        127        203        203        203        moist
  ---------- ---------- ---------- ---------- ---------- ---------- ----------

g.  Pedon (if linked to a pedon in NASIS pedon).

h.  Component Text (if needed for MUDs, TUDs, or other unique
    information) Refer to MO6 Tech Note 3 and Tech Note 6 for
    instructions on using the Component Text Table for MUDs and TUDs.

i.  Geomorphic Description. See the MO6 Guide for Populating Landforms
    for more detailed instruction

j.  Two Dimensional Surface Morphometry. Populate only when "hills" is
    the landform.

k.  Three Dimensional Surface Morphometry. Populate where appropriate.
    Some landforms such as Mesas and Cuestas will not have a 3D
    morphometry.

l.  Microrelief Surface Morphometry. Populate where appropriate.

m.  Slope Shape Morphometry. Populate with the one most predominant
    shape.

n.  Ecological Site.

o.  Other Vegetative Classification (for habitat types).

p.  Canopy Cover (if data is available).

q.  Existing Plants. See the MO6 Guide for Populating ESD and Vegetation
    Information.

r.  Forest Productivity (if relevant).

s.  Forest Productivity-Other (if relevant).

t.  Potential Windbreak (if relevant).

u.  Trees to Manage (if relevant).

```{=html}
<!-- -->
```
8.  Horizon Table. There are many elements in the Horizon Table as well
    as a number of Horizon Child Tables. Many of the elements in the
    Horizon Table are dependent on elements in some of the Horizon Child
    Tables. For example, the sieve and particle size distribution values
    in the Horizon Table are directly linked to values in the Horizon
    Texture and Horizon Fragment Tables. Therefore, the order in which
    these tables are populated is critical. **[Note -- All RV values
    should match the RV values of the typifying pedon representing the
    map unit component.]{.underline}**

    a.  Horizon Table

        i.  Open the number of rows equal to the number of horizons you
            need to populate. Keep in mind that individual horizons
            should be populated in NASIS, not layers of combined
            horizons. Generally, you should not combine horizons into
            layers in NASIS.

        ii. Manually populate the Horizon "Designation" data element for
            all horizons. The Horizon Designation data element will
            later be calculated after all the other Horizon designation
            elements are populated ("Disc", "Master", "Prime", "Sub",
            and "Suffix")

        iii. Populate the "Disc", "Master", "Prime", and "Sub" data
             elements in the Horizon Table as appropriate.

        iv. Populate the "Suffix" data element in the Horizon Suffix
            Table for those horizons with one or more suffixes.

        v.  Populate the Horizon "Top Depth RV" and the Horizon "Bottom
            Depth RV" (centimeters) for each horizon.

        vi. Run the NASIS Calculation named "Horizon Designation." This
            calculation can be run on one or all horizons. Recheck your
            Horizon Designations after running the calculation to make
            sure they are correct. Make any needed corrections, and
            rerun the calculation.

        vii. At this point "Seq" can be populated for the purpose of
             grouping similar horizons together so that when the TUD is
             generated , using the MO6 TUD generation report (See MO6
             Tech Note 3), horizons with similar properties are grouped
             together in the Range in Characteristics section of the
             TUD. For example, a pedon has an "A-Bt1-Bt2-C" horizon
             sequence. The Bt1 and Bt2 have similar properties and
             should be grouped together on the TUD. In this case the A
             horizon would be Seq "1", the Bt1 and Bt2 horizons would
             both be Seq "2", and the C horizon would be Seq "3". If the
             profile was "A-Bt-Bky-C", no horizons would be sequenced
             together and the Seq would be A=1, Bt=2, Bky=3, and C=4.

        viii. Click "Save."

Because there are multiple data elements in the Horizon Table that are
dependent on texture and rock fragments it is necessary for the Horizon
Texture and Horizon Fragment Tables to be populated before any
additional data elements in the Horizon Table are populated.

9.  Horizon Texture

> Populating texture is somewhat complicated and therefore requires some
> explanation and a few examples.

a.  For horizons with only one texture (or in lieu texture)

    i.  Open row in Horizon Texture Group Table

    ii. Open row in Horizon Texture Table

    iii. Open row in Horizon Texture Modifier (if needed)

    iv. Populate the modifier in the Horizon Texture Modifier table (if
        needed)

    v.  Populate the Texture data element (or In Lieu texture) in
        Horizon Texture Table

    vi. Go to Horizon Texture Group Table and run calculation named
        "Texture Group Name."

    vii. Populate "RV?" with "yes."

    viii. Click "Save."

b.  For horizons with more than one texture -- Textures should be
    limited to those that are common and typical. Atypical textures
    should not be included. The fine earth textures listed should be
    adjacent to each other on the Textural Triangle. For example, it
    would not be appropriate to have only sandy loam and clay loam
    populated for the same horizon. Generally, you should not have more
    than 3 textures for a horizon.

    i.  Open the number of rows in the Horizon Texture Group Table equal
        to the number of textures for the horizon.

    ii. Open one row in the Horizon Texture Table for each row in the
        Horizon Texture Group Table. Except for stratified textures,
        there must be **one and only one** row in the Horizon Texture
        table for each row in the Horizon Texture Group table.

    iii. Open row(s) in the Horizon Texture Modifier table (if needed)

    iv. Populate the modifier(s) in the Horizon Texture Modifier table
        (if needed)

    v.  Populate the Texture data element for each row in the Horizon
        Texture Table

    vi. Go to Horizon Texture Group Table, highlight all rows in table
        and run calculation named "Texture Group Name."

    vii. Find your representative texture and populate "RV?" with "yes."
         **[(Note -- You can have only one representative texture in the
         Horizon Texture Group Table. The representative texture must
         match that of your corresponding typifying
         pedon).]{.underline}**

    viii. Populate "RV?" with "no" for those textures that are not
          representative.

    ix. Click "Save."

c.  For horizons with stratified textures - Horizons with stratified
    textures pose a unique problem when populating NASIS. Please refer
    to MO6 Tech Note 11 -- Guide for Populating Horizons with Stratified
    Textures for detailed instruction.

    i.  Determine the weighted average texture for the horizon. (The
        properties of the average texture will be input into NASIS and
        all subsequent calculations and derivations, with the exception
        of Ksat, will be based on this average texture. Once all
        population, calculation, and validation are complete the average
        texture will be removed and the end point textures representing
        the stratification will be entered into the Horizon Texture
        Table.)

    ii. Populate the average texture in the Horizon Texture Table using
        the directions listed in 9a above.

    iii. Complete all population, calculation, and validation using
         properties of the average texture, except for Ksat. Values for
         Ksat are based on the most water restrictive stratum in the
         stratified horizon.

> **After all population, calculation, and validation of the average
> texture are completed you must go back and enter the end point
> textures representing the stratified textures.**

iv. Go back to the Horizon Texture Table and take out the previously
    populated average texture.

v.  Open another row in the Horizon Texture Table. Unlike step 9b for
    multiple nonstratified textures, for stratified textures there will
    be **multiple rows** in the Horizon Texture Table for the one row in
    the Horizon Texture Group Table.

vi. Open another row(s) in Horizon Texture Modifier (if needed)

vii. Populate the modifier(s) of the end point textures in the Horizon
     Texture Modifier table (if needed)

viii. Populate the Texture data element in each row of the Horizon
      Texture Table with the end point textures. For example, the
      horizon is stratified with sandy loam, loam, and clay loam. Sandy
      loam is populated in one row and clay loam in the other.

ix. Go to the one row in Horizon Texture Group Table and populate "RV?"
    with "yes" and "Stratified?" with "yes."

x.  Run calculation named "Texture Group Name."

xi. Click "Save."

```{=html}
<!-- -->
```
10. Horizon Fragments - These fragment instructions also apply to the
    Component Surface Fragments Table.

    a.  Populate the Horizon Fragments Table for each Horizon that
        contains fragments. All elements with the exception of
        "Roundness" are required. Concerning "Hardness", parafragments
        range in hardness from extremely weakly through moderately
        cemented. All rock fragments are at least strongly cemented or
        indurated. Generally, the individual gravel size classes are not
        used except in unique soils where the rock fragments are
        dominated by one gravel class. For example, granitic soils
        typically have a high proportion of fine gravel, so for those
        soils the gravel should b subdivided into fine gravel (2-5mm)
        and medium and coarse gravel (5-75mm). This ensures more
        accurate calculation of the #4 sieve. Most of the time the
        default gravel class of 2-75 mm is used. Follow the reference
        charts below when populating the Horizon Fragments Table. Do not
        split, or customize, the "size" ranges in the chart. Do not
        create overlaps of size classes on one line. Use the chart
        ranges. Note---the sum of the Vol % RV must not range outside
        the range for the modifier; e.g. the sum of the Vol % for a
        "gravelly loam" must fall within 15 to \< 35%.

  ---------- ------------ ---------------------- ------ ------- --------- --------------
  Fragment                Rock Fragment Modifier                          
  Content %               Usage                                           
  By Volume                                                               

  \< 15                   No texture adjective                            
                          is used (noun only;                             
                          e.g. loam).                                     

  15 to \<                Use adjective for                               
  35                      appropriate size; e.g.                          
                          *gravelly*.                                     

  35 to \<                Use *"very"* with the                           
  60                      appropriate size                                
                          adjective; e.g. *very                           
                          gravelly*.                                      

  60 to \<                Use *"extremely"* with                          
  90                      the appropriate size                            
                          adjective; e.g.                                 
                          extremely *gravelly*.                           

  ≥ 90                    No adjective or                                 
                          modifier. If ≤ 10%                              
                          fine earth, use the                             
                          appropriate noun for                            
                          the dominant size                               
                          class; e.g. gravel.                             
                          Use **Terms in Lieu of                          
                          Texture**.                                      

             Fragment                            Size           Shape     
                                                 (mm)                     

                                                 L      H                 

             fine                                2      5       nonflat   
             gravel\*                                                     

             medium                              5      20      nonflat   
             gravel\*                                                     

             coarse                              20     75      nonflat   
             gravel\*                                                     

             fine and                            2      20      nonflat   
             medium                                                       
             gravel\*                                                     

             medium and                          5      75      nonflat   
             coarse                                                       
             gravel\*                                                     

             gravel                              2      75      nonflat   

             channers                            2      150     flat      

             cobbles                             75     250     nonflat   

             stones                              250    600     nonflat   

             stones                              380    600     flat      

             flagstones                          150    380     flat      

             boulders                            600    \>600             
  ---------- ------------ ---------------------- ------ ------- --------- --------------

> \* Generally not used.

11. Horizon Table

    a.  Change edit setup to "6MO Texture, Total Frag Volume, and
        Particle Size."

    b.  Change View to "Horizon-Horizon Texture Group"

    c.  Referring to the textures identified in the Horizon Texture
        Group Table, enter:

        i.  Total Fragment Volume L, RV, H. This includes rock,
            pararock, and wood fragments. The Total Fragment Volume RV
            should match the sum of the RVs in the Horizon Fragment
            Table. The Total Fragment Volume L and H values may range
            beyond the allowed range of the RV texture to include ranges
            for the non-representative textures (RV=no). The sum of the
            L or H values in Horizon Fragments can be outside the L or H
            value of Total Fragments. This is because all the L or H
            values for gravel, cobble, stone, etc. may not occur
            together. Conversely, the sum of the L or H values must not
            be inside the L or H value of Total Fragments.

        ii. Total Clay L, RV, and H values for each horizon. The Total
            Clay RV value must match that of the representative texture.
            The Total Clay L and H values may range beyond the allowed
            range of the RV texture to include the clay ranges for the
            non-representative textures (RV=no).

        iii. CaCO~3~ clay L, RV, and H (if present). Refer to the MO6
             Tech Note 10 for further guidance on populating CaCO~3~.

        iv. Total Sand L, RV, and H for each horizon. This will produce
            more accurate results when the Particle Size Estimator and
            the Rock Frags & Percent Passing Sieves calculations are
            run. If Total Sand is not known it can be left blank but
            calculated results will be less precise.

    d.  You do not need to populate the RV values for the sand fractions
        or the Total Silt as the Particle Size Estimator calculation
        will do this.

    e.  Run the calculation named "Particle Size Estimator" (click
        anywhere in the Horizon table, then click "Options-Calculate
        Data Elements-Particle Size Estimator." Refer to the MO6 Guide
        for Using the NASIS Particle Size Estimator Calculation for more
        detailed instructions.

    f.  Review calculated results, edit if needed, and rerun calculation
        if needed.

12. Horizon Pores & Horizon Consistence Tables -- As of January 2008
    these tables are not required to be populated by MO6. However,
    calculations are being developed for Ksat and Bulk Density that will
    use data elements from the Horizon Pore and Horizon Consistence
    tables. In addition, some models use these elements. With this in
    mind you are encouraged to populate these tables.

13. Horizon Table

    a.  At this point the next step is to populate those Horizon Table
        data elements that currently (as of 1/08) do not have a
        calculation available to derive the data. These elements require
        manual derivation and input into NASIS. Please refer to the MO6
        Guidance Documents for assistance with populating some of these
        data elements.

    b.  Change the edit setup to "6MO Horizon Table (manually derived
        data elements)." Derive and populate these data elements. Note
        -- There are other data elements such as Dp, Sum of Bases, Free
        Iron, Excavation Difficulty, etc. that were not included in this
        edit setup. They are optional data elements that can be
        populated if the data is available and pertinent.

    c.  Click "Save" and change edit setup back to "Default."

14. Horizon Table -- Rock Fragments and Percent Passing Sieve Data.

    a.  Change the edit setup to "6MO Rock Frags (\>10, 3-10) and
        Sieves" and run the calculation named "Rock Frags & Percent
        Passing Sieves." The calculated values are rounded to the
        nearest whole number. Do not round to the nearest "5".

    b.  Click "Save" and change edit setup back to "Default."

15. Horizon Structure

    a.  Open row in Horizon Structure Group Table.

    b.  Open row in Horizon Structure Table.

    c.  Populate the Horizon Structure Table using the corresponding
        structure from your representative pedon.

    d.  Go to Horizon Structure Group Table and run calculation named
        "Structure Group Name."

    e.  Populate "RV?" with "yes."

    f.  Click "Save" and change the edit setup back to "Default".

16. Horizon Table - Run calculations for the following data elements:

    i.  "Water Content"

    ii. "CEC/ECEC"

    iii. "Liquid Limit and PI"

Note---As of January 2008 NASIS calculations for AASHTO and Unified
classes do not exist. However, a report exists that compares stored
values for AASHTO and Unified with calculated values. These calculated
values from the report can be manually populated into NASIS. The report
is on the MO6 site and is named "UTIL -- AASHTO and Unified, stored
values vs. calculated values." The MO6 report identifies a calculated
"RV" along with calculated "Low" and a calculated "High" values. These
Low and High calculated values are additional classes that need to be
listed along with the RV class.

17. Horizon AASHTO Table

    a.  Run the MO6 report named, "UTIL -- AASHTO and Unified, stored
        values vs. calculated values.

    b.  Use the report results to populate the AASHTO Classes. Choose
        only one to be representative (RV=yes).

    c.  Click in the Horizon Table and run the calculation named "AASHTO
        Group Index".

18. Horizon Unified Table

    a.  Using the report results from step 16, populate the Unified
        Classes. Choose only one to be representative (RV=yes).

At this point there are remaining unpopulated elements in the Mapunit,
Data Mapunit Crop Yield, and Component tables that need to be populated.
The elements are dependent on the properties that have been populated to
this point.

19. Mapunit Table - Populate Farm Class (Prime Farmland). Use NSSH
    guidance supplemented with State guides for Unique and Farmland of
    Statewide Importance classification.

20. Data Mapunit Crop Yield Table -- Populate Crop Name, Units, NIRR
    Yield, IRR Yield (if appropriate).

21. Component Table -- Change edit setup to "6MO Component Data Entry
    2".

    a.  T factor -- As of January 2008 an officially sanctioned
        calculation does not exist. Follow the guidance for T factors in
        part 618.62 and exhibit 618-14 in the NSSH.

    b.  WEI and WEG -- As of January 2008 an officially sanctioned
        calculation does not exist. However, the NSSC Pangaea NASIS
        report named, "UTIL -- Comparison of WEG/WEI, stored vs.
        calculated (TEST)" is based upon exhibit 618-16 in the NSSH and
        is suitable for use.

    c.  Hydric Rating. Enter "yes" or "no". If "yes" open row in
        Component Hydric Criteria table and enter the Hydric Criterion.

    d.  Drainage -- See MO6 Guide for Drainage

    e.  Albedo Dry -- If linked to a representative pedon this can be
        calculated. If a representative pedon is not available refer to
        the chart in the MO6 Guide for Albedo Dry for the correct Albedo
        Dry value.

    f.  Land Capability Class and Subclass (NIRR LCC, NIRR Subclass, IRR
        LCC, and IRR Subclass) -- Use appropriate State guidance. As of
        January 2008 an MO6 Region wide guide does not exist. However,
        these will be required to join across State lines.

    g.  Cons Tree Shrub Group -- As of January 2008 an officially
        sanctioned calculation does not exist. Follow State Guidance or
        use the NSSC Pangaea NASIS report named, "UTIL -- Comparison of
        WSG and CTSG Calculation".

    h.  Frost Action - As of January 2008 an officially sanctioned
        calculation does not exist. However, the NSSC Pangaea NASIS
        report named, "UTIL -- Comparison of Frost Action, stored vs.
        calc. (Test)" is based upon exhibit 618-5 in the NSSH. Caution
        when using this report -- if the Family particle size class is
        different from the part of the soil that freezes, manual
        adjustments may be needed.

    i.  Hydrologic Group - As of January 2008 an officially sanctioned
        calculation does not exist. However, the NSSC Pangaea NASIS
        report named, "UTIL -- Hydrologic Soil Group Validation Check"
        can be used.

    j.  Corrosion Concrete - As of January 2008 an officially sanctioned
        calculation does not exist. Use your existing guides.

    k.  Corrosion Steel - As of January 2008 an officially sanctioned
        calculation does not exist. Use your existing guides.

    l.  Brief Soil Description -- Run the calculation named "Generated
        Brief Soil Description".

    m.  Click "Save".

22. After a Mapunit and a Data Mapunit have been populated you should
    run Validations to check your data. In general, no validations
    should be run until all data has been populated, derived, or
    calculated.

**[PLEASE KEEP IN MIND, IF YOU GO BACK AND CHANGE A DATA ELEMENT AT THIS
POINT, YOU MUST REPEAT ALL THE DATA POPULATION, DERIVATION,
CALCULATIONS, AND VALIDATIONS THAT ARE DEPENDENT ON THAT DATA
ELEMENT]{.underline}**.

Detailed descriptions of Calculations and Validations are available
through a NASIS report. To view a Calculation or Validation report:

1.  Start NASIS

2.  Click Options-Standard Reports-National-UTIL Calculation and
    Validation Scripts-"select calculation or validation name."

**[A SUGGESTED SEQUENCE FOR RUNNING CALCULATIONS]{.underline}**

  ------- -------------- ------------------------- -------------------------
  Run     Table Name     Calculation Name          Comments
  Order                                            

  1       Mapunit        Mapunit Name              
                         Capitalization            

  2       Component      Component Name            
                         Capitalization            

  3       Component      Taxonomic Classification  

  4       Component      Albedo Dry                Works only if linked to a
                                                   representative pedon.

  5       Component      Parent Material Group     
          Parent         Name                      
          Material Group                           
          Name                                     

  6       Horizon        Horizon Designation       

  7       Horizon        Texture Group Name        
          Texture Group                            

  8       Horizon        Particle Size Estimator   

  9       Horizon        Rock Frags & Percent      
                         Passing Sieves            

  10      Horizon        Structure Group Name      
          Structure                                
          Group                                    

  11      Horizon        Water Content             

  12      Horizon        CEC/ECEC                  

  13      Horizon        LL and PI                 

  14      Horizon        AASHTO Group Index        
  ------- -------------- ------------------------- -------------------------

**[A SUGGESTED SEQUENCE FOR RUNNING VALIDATIONS]{.underline}**

  ------- -------------- ------------------------- -------------------------
  Run     Table Name     Validation Name           Comments
  Order                                            

  1       Horizon        Multiple textures         
          Texture Group                            

  2       Horizon        Texture RV indicator      

  3       Horizon        Texture Modifier (by      
                         fragment volume)          

  4       Horizon        Particle Size             
                         Distribution              

  5       Horizon        Texture Class vs.         
                         Particle Size Separates   

  6       Horizon        Percent Passing Sieves    

  7       Horizon        Ksat Population           

  8       Horizon        Unified & AASHTO RV       
                         Indicator                 

  9       Horizon        AASHTO Class              

  10      Horizon        Unified Class             

  11      Component      Check for Null Component  
                         Name                      

  12      Data Mapunit   Component Percentages     Need minor components
                                                   loaded into selected set.
                                                   This validation currently
                                                   does not identify map
                                                   units where the sum of
                                                   the component percentages
                                                   is less than 100 percent.

  13      Component      Horizon Depth             

  14      Component      Horizon Table             This validation replaces
                                                   all the former FOTG
                                                   validations. It will
                                                   check for NULLs in the
                                                   horizon table data for
                                                   any items found on
                                                   National Bulletin 430-5-7
                                                   and should be run prior
                                                   to submitting a data set
                                                   to the Soil Data Mart.

  15      Component      Horizon Structure         

  16      Component      Aspect                    

  17      Component      Geomorphology             

  18      Component      Month                     

  19      Component      Parent Material           

  20      Component      Range and Understory      
                         Production Percentages    

  21      Component      Restriction               

  22      Component      Surface Fragments         

  23      Component      Component Table           This validation will
                                                   check for NULLs for
                                                   compname, comppct_r,
                                                   compkind, slope_l,
                                                   slope_r, slope_h, tfact,
                                                   wei, weg, hydgrp,
                                                   taxorder, drainagecl,
                                                   albedodry_r. It filters
                                                   to exclude miscellaneous
                                                   areas.

  24      Component      FOTG/Models/SDM Export    This validation replaces
                         Validation 12/2006        all the former FOTG
                                                   validations. It will
                                                   check for NULLs for any
                                                   items found on National
                                                   Bulletin 430-5-7 and
                                                   should be run prior to
                                                   submitting a data set to
                                                   the Soil Data Mart. This
                                                   validation includes the
                                                   ASPECT and STRUCTURE.

  25      Component      Taxonomic Classes         

  26      Component      WEPS Required Data        

  27      Component      Bulk Density on Andic     
                         Soils                     

  28      Legend         Legend Acres              

  29      Legend Area    Overlap Acres             
          Overlap                                  

  30      Legend         Land Category Acres       
  ------- -------------- ------------------------- -------------------------