DOCUMENTATION - PowerPoint PPT Presentation

1 / 18
About This Presentation
Title:

DOCUMENTATION

Description:

Soil survey documentation is scientific data from measurements and observations ... Cupcakes baking pans or ice cube trays are great for placing the different ... – PowerPoint PPT presentation

Number of Views:64
Avg rating:3.0/5.0
Slides: 19
Provided by: steve194
Category:

less

Transcript and Presenter's Notes

Title: DOCUMENTATION


1
DOCUMENTATION
  • MO6 SOILS WORKSHOP
  • MARCH 2009

2
Documentation
  • Guidance for documentation can be found in the
    NSSH, part 627.08
  • Soil survey documentation is scientific data from
    measurements and observations of basic soil
    properties and qualities and of spatial
    arrangements, that are collected in the field or
    remotely sensed using standardized procedures.
    This data is systematically recorded.
  • The information is presented as geographical
    descriptions of landscapes and boundaries, soil
    profiles, soil layers, chemical and physical
    properties, or temporal condition.
  • Documentation assures proper soil classification,
    uniform and consistent mapping, and supports
    inferences for application of the information to
    similar landscapes.

3
Why Collect Documentation?
  • To be able to develop science based
    soil-landscape models so we can delineate
    polygons of like soils
  • To be able to build and store property data in a
    permanent database accessible to users.
  • To quantify soil spatial variability in order to
    make logical breaks in soil landscapes.
  • To better communicate with soil scientists and
    related professions (nomenclature, taxonomy, etc)
  • To correlate ecological sites with soils
  • To be able to classify and correlate soils
    consistently
  • To be able to develop and test interpretations
  • To be able to test and report the reliability of
    soil survey information

4
Why Collect Documentation?
  • To be able to communicate and support your
    concepts/work to those who come after you.
    Steve Park

5
Kinds of Documentation
  • Map Unit Composition
  • Transect Sample points collected at equidistance
    along a line.
  • Usually 10 points in a transect.
  • Can be stretched out over the whole polygon, or
    focused on a particular position on the landform.
  • More suited to open easily traversed landforms.
  • Traverse Sample points collected at selected
    representative locations on the landform.
  • Usually non-linear, often zig-zag shape.
  • Suited for use on rough broken landforms not
    easily traversed.
  • Can be stretched out over the whole polygon, or
    focused on a particular position on the landform.

6
Kinds of Documentation
  • Map Unit Composition
  • Field Notes General notes about observations,
    thoughts, analysis for the map unit.
  • Geospatial Analysis
  • Some components are easily distinguishable from
    others in the map unit.
  • GIS tools can break out components by slope
    shape, aspect, moisture index, etc.

7
Kinds of Documentation
  • Map Unit Soil Component Characterization
  • Pedon Descriptions
  • Full
  • Partial Depth, Horizons, Texture, Color,
  • Usually documented on a 232 form but can also be
    documented on transect/traverse stops.
  • Field Notes - General notes about observations,
    thoughts, analysis for the soil component.

8
How Much Documentation?
  • From NSSH, 627.08 5 e)
  • The memorandum of understanding for the survey
    area provides guidance for the type and amount of
    documentation.
  • Documentation needs and standards may vary by map
    unit within the same survey area.
  • Flexibility of guidance allows for sufficient
    data collection for each map, yet avoids the
    excess time and expense of redundant or
    superfluous data.

9
Sharing Documentation
  • Documentation can be shared between soil survey
    areas.
  • This is National Policy as well as MO6 policy.
  • Progressive correlation facilitates the
    distribution and sharing of documentation on an
    MLRA basis.

10
How Much Documentation?
  • Map Units
  • NSSH, 627.08
  • 30 points when lt 2,000 acres
  • 10 additional points for each additional 4,000
    acres
  • Typically 60 points is considered sufficient
  • MO6 Guidance
  • Each map unit should have at least 3 transects
    and/or traverses.

11
How Much Documentation?
  • Proposed Series
  • NSSH 627.08
  • 5 complete pedon descriptions for lt 2,000 acres
  • 10 complete pedon descriptions for gt 20,000 acres
  • MO6 Guidance
  • At least 3 complete pedon descriptions
    supplemented by up to 7 partial descriptions
    and/or notes.

12
How Much Documentation?
  • Map Unit Soil Component
  • NSSH 627.08
  • Each major soil component requires 1 complete
    unique representative pedon description.
  • MO6 Guidance
  • Same as NSSH. Each major soil component requires
    1 complete unique representative pedon
    description. Along with the description there
    should also be a box sample.

13
How Much Documentation?
  • To Correlate a Taxon on the Legend
  • NSSH 627.08
  • 3 pedon descriptions for the taxon
  • MO6 Guidance
  • Same as NSSH, 3 pedon descriptions for the taxon

14
Summary of MO6 General Guidance on Documentation
  • The NSSH is the National Standard and should be
    followed as much as possible.
  • The MOU specifies the quantity and kind of
    documentation.
  • The quantity, quality, and kind of documentation
    required will depend a lot on the extent,
    complexity, and history of the map unit. IT
    DEPENDS!!!
  • There is no one pat answer for every map unit or
    taxon. Common sense, judgment, and flexibility
    must be used.
  • In general, the quantity and quality of
    documentation should be adequate to support the
    map unit concept.
  • Prefer fewer high quality documentation rather
    than numerous partial, inconsistent, or
    incomplete documentation.

15
Tips For Collecting Documentation
  • Premap using GIS tools or a stereoscope before
    collecting data in the field. Firm up lines and
    understand where one polygon ends and another
    begins.
  • Limit a transect/traverse to one polygon. Dont
    run a transect/traverse across multiple polygons.
    If you cross into another polygon start a new
    transect/traverse.
  • Ensure transects/traverse provide a
    representative cross section of the polygon.
    Dont locate the transect/traverse parallel and
    near the edge of the polygon. Avoid transition
    zones or heavily disturbed areas.
  • Very large polygons may need more that one
    transect/traverse.
  • For each point/stop you may collect a full
    description, a partial description, or a note.
  • When hand digging a hole make sure the hole is
    dug out with a sharpshooter or shovel wide enough
    so you can auger to a deeper depth. Pedons need
    to be described to the series control section
    depth.

16
Tips For Collecting Documentation
  • Carry zip lock sandwich bags with you in your
    pack so that you can collect soil samples. Label
    the bags and put them in a box tray when you get
    back to the office. This allows you to avoid
    having to carry bulky boxes.
  • Cupcakes baking pans or ice cube trays are great
    for placing the different horizons in, making it
    a little easier to do texture, color,
    effervescence, etc.
  • Always carry a hand lens and make use of it when
    describing clay films, carbonates, and other
    small features.
  • As much data as possible for a 232 or full
    description should be completed in the field and
    not in the office. Some things like color,
    pores, pH, EC, CCE can be determined from the box
    sample in the office. All other properties should
    be recorded in the field.
  • Keep your descriptions as simple as possible.
    Each stop should not be turned into a
    micro-research project. When pits are opened up
    is the time to be a little more detailed.
  • Record key vegetation for each stop. Geology
    should also be recorded either for the whole
    transect/traverse or for each stop if it is that
    variable.
  • In the course of running a transect/traverse it
    is OK to make references to a previous stop. For
    example, if stop 2 is the same as stop 1, but is
    just a little deeper to sandstone bedrock, simply
    record for stop 2, same as stop 1 except
    sandstone bedrock occurs at 35 inches.

17
Tips For Collecting Documentation
  • In the course of running a transect/traverse if
    you find a pedon that you think would be make a
    good typifying or representative pedon for the
    map unit go ahead and complete a full description
    and collect box samples. You can complete a full
    description on the transect/traverse form or
    make a note on the transect/traverse form that
    you are collecting a 232 and use a 232 form to
    complete the description.
  • In areas where firm map unit and series have been
    approved and are well known, it is OK to simply
    record the series name. However, dont force a
    series name if you are unsure. Not recommended
    for initial soil survey, but has use in update
    work.
  • Make sure to record other things you observed
    while running the transect/traverse that did not
    fall on a point. For example, you may record
    that rock outcrop was observed, or slopes with
    lesser or greater percent were observed, or
    different ecosites were observed.
  • If you chose a pedon from a transect/traverse to
    use as a typifying pedon for a progress field
    review, and you open up a pit for the review,
    make sure to adjust the description to what is
    observed in the pit. You will always see things
    differently in a pit than in a hand dug hole.

18
Tips For Collecting Documentation
  • Most importantly, the documentation you collect
    must be useable by someone else in the future.
  • Legible
  • Correctly georeferenced, if you dont have a GPS
    location mark it on the map and at least record
    the PLS location.
  • Complete and Correct
  • Summarized
  • Should not be ambiguous. For example, if you
    cant auger below 100 cm, record whether you
    believe you were stopped by a large rock or that
    you believe it to be bedrock. Another example
    would be to identify Bk horizons as calcic or
    noncalcic horizons. Dont leave someone else
    guessing about what you observed.
  • Place documentation in map unit folders and taxon
    folders where they can be accessed by all.
  • Make security copies of your documentation on a
    regular basis. These can be hard copy or
    electronic copies stored at another location.
Write a Comment
User Comments (0)
About PowerShow.com