Database – Point Data Aggregation

1. Database – Point Data Aggregation

2. Rationale The evaluation is complete and the project plans have been created. The purpose of this module is to identify the existing point data pertinent to the project plan and make decisions on the amount of additional data. This module will look at methods to analyze the geographic distribution, amount of characterization data, and transect summaries. Point data is then aggregated to build a specific component within a specific map unit.

3. Objectives • Determine the point data needs for project plans • Learn techniques in populating point data into PedonPC • Learn techniques in analyzing point data using AnalysisPC • Determine the composition of the map unit concepts across the various surveys • Identify how the point data is used to the describe variations in map unit composition from a single traditional survey area to a MLRA soil survey area

4. Chat: • Who has access to the original mapping field documents (pedon descriptions, map sheets, correlation notes, etc)?

5. Item 4.2 Availability of detailed primary soil property data. One user requirement for NASISis to have access to the most detailed information available. Although detailed information is collected in the form of pedon descriptions, transects and field notes, most of the detail is not available to users in the soil survey report. Historically, the soil survey report has been a primary mechanism for providing soils information to users.In the future NASIS will be a dynamic soils information system that will enable many different output formats and levels of detail. The National Soils Information System Draft Requirements Statement published in January 1991 identified twelve “Fundamental NASIS Concepts”.

6. Item 4.2 Availability of detailed primary soil property data. … A conventional soil survey report would be only one of these output formats.It is an objective of NASIS to be able to provide as much detailed information as has been collected or recorded.The level of information provided (either detailed or generalized) should be determined by the users need, based on the availability of data and the detail appropriate for the intended use.The National Soils Information System Draft Requirements Statement published in January 1991 identified twelve “Fundamental NASIS Concepts”.

7. Point Data Analysis Assumptions: • The historical data has been assembled and ready for review • The evaluations are completed • The Project Plan has been created • Historical and recent point data is compiled • Additional point data will be collected • Data is to be analyzed • Decisions are to be made

8. Chat: • Why do we collect data? (and don’t say because the correlator says so)

9. Documentation (627.08) Soil scientists take field notes as they progressively map the soils. They: • record them on location at the time of the observation; • emphasize documenting the ordinary, the prevalent, and the commonplace; • if not a direct observation, clearly identify location, date, author, soil component, and source; • use standard terminology and standard database programs;

10. Documentation (627.08) (b) Purpose of Documentation Documentation is collected for specific outcomes within each survey area. The main outcomes are: • 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.

11. Documentation (627.08) (b) Purpose of Documentation Documentation is collected for specific outcomes within each survey area. The main outcomes are: • 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

12. Documentation (627.08) (e) Field Description Standards (1) Proposed series require descriptions of at least 5 pedons … (2) Each map unit soil component has a unique description ... (3) Map units require a minimum of 30 recorded points for each map unit to document the composition … (4) Exceptions to the minimum standards for documentation of map units and map unit components apply …

13. Chat: • What soil properties do you collect on a pedon description that are used to populate a component and its horizons?

14. Pedon Description Lab Data Properties Interpretations What soil properties do you extract from a pedon description that is used to populate Component and Horizon tables??

15. Minimum Data Set • The 7 physical properties that must be populated by the soil scientist (no calculation) • Sand (and fractions) • Silt • Clay • Organic Matter • Coarse Fragments • Bulk Density • Water states (Ksat, WT, AWC, 15bar, etc) DO NOT USE THE PARTICLE SIZE ESTIMATOR CALCULATION UNLESS YOU VERIFY THE RESULTS

16. Why are these 7 special? • Many other soil properties can be calculated from these 7 e.g. • Texture/sieves=sand+silt+clay+CF • CEC=clay+OM • Water Content=BD+OM+CF+Clay • Kfact=vfs+silt+OM+Ksat+structure

17. DISCLAIMER • The following information is meant as an example of using available software tools to populate and analyze data. The soil series in this example was selected based on the amount of available pedon descriptions, only. This module is designed to explain how the population of pedon data is used in developing aggregated data for the component and horizon.

18. Series Distribution Let’s assume the project plan was created for the Olton map units Using the OSD Series Distribution Tool the geographical distribution can be identified

19. Manuscript Pedon Review The manuscript pedon data is reviewed

20. Manuscript Pedon Review More manuscript pedon data is reviewed

21. OSD Review

22. SSURGO and OSD Review The OSD typical pedon is plotted in relation to the map units The TPs for the associated soils are included for reference An issue readily identified is the OSD TP inside the “outlying” map units

23. OSD Review Randall County and OSD Typical Pedon location Correlation dates are labeled for each county

24. OSD Location

25. OSD Location “Potter Soils” re-correlated to “Potter-Mobeetie association, 8 to 45 percent slopes”

26. OSD vs. TUD

27. OSD/TUD/NASIS Data Review Component does not exist in the map unit located by the OSD New DMU Old DMU

28. One method of Analysis

29. Chat: • Who is using PedonPC?

30. PedonPC Capturing Point Data

31. PedonPC

32. PedonPC • Designed for quick data entry • Field use • Office use • Data imported into NASIS • Tailored choice lists

33. Features • Can be used in the field with the tablet • Adding GPS allows for auto population of location data • Geo-referenced data can then be shared

34. Mobility • The portability of the tablet provides for the capture of point data using PedonPC

35. Tablet Data Entry - Site • Designed to use Portrait view • Includes tab managed screens • 3 tabs for Site

36. Tablet Data Entry - Pedon • Enter site data first • 3 tabs for Pedon • Screens can be tailored

37. Tablet Data Entry – Horizon1 • Horizon data on two tabs • Columns can be moved to fit needs • Tailored choice lists and forms

38. Tablet Data Entry – Horizon2 • Horizon 2 tab contains redox, concentrations and features • Notice the Pedon Horizon Field Measured Properties

39. So, what if you don’t use a tablet in the field?

40. PC Data Entry • From the PedonPC main menu, select PC Data Entry

41. PC Entry • Shows Site and Pedon on one screen with tabs managing data entry

42. Entering Data in PedonPC

43. Entering Data – Auto Population using ArcGIS The auto- population tool in Arc allows the user to click the map to locate the pedon point and a PedonPC dialog box appears

44. Entering Data – Auto Population using ArcGIS • Populate the new User Pedon ID and PedonPC opens with the new site and overlaps created if they appear as spatial layers in the Arc session

45. Importing into NASIS6

46. Purpose??? • All soil scientists use soil descriptions to communicate • All soil descriptions are useful in TSS and in Soil Survey • All descriptions should include enough information that can be used for more than one purpose. • Using PedonPC assures information is available for all to use

47. NASIS Pedon Incorporating Point Data

48. NASIS6 Pedon No matter the software, point data needs to be in NASIS

49. NASIS Pedon Review Pedons, Sites and Transects are loaded into NASIS and available for analysis

50. Pedon reports • Run National “PEDON…” reports