soil data join recorrelation n.
Skip this Video
Loading SlideShow in 5 Seconds..
Soil Data Join Recorrelation PowerPoint Presentation
Download Presentation
Soil Data Join Recorrelation

Soil Data Join Recorrelation

182 Vues Download Presentation
Télécharger la présentation

Soil Data Join Recorrelation

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. Soil Data Join Recorrelation MO1 Approach to the Harmonization Process

  2. Agenda • Introduction • Brief review of NASIS structure • Overview of the Soil Data Join Recorrelation (SDJR) initiative • Acres goals and timelines • Roles and responsibilities • Overview of national instruction • Map unit NASIS group assignment • Review SDJR data package • MO1 SDJR demonstration

  3. NASIS review • These four objects (table and nested child tables) will be referenced: • Data Mapunit • Legend • Mapunit • Project

  4. NASIS review • Data Mapunit • Stores component data • Links to the Mapunit object through the Correlation child table • Mapunit • Linked to the Legend and Project objects • Uniquely identified by the national mapunit symbol • Links to the Legend object through the Legend Mapunit child table using the national map unit symbol

  5. NASIS review • Mapunit • Also is linked to the Project object through the Project Mapunit child table using the national map unit symbol • Same method as linking a mapunit to a legend

  6. NASIS review • Legend • Will not be edited by the MLRA SSO • Contains the Legend Mapunit child table • Only thing that can be edited in this table is the map unit acres and map unit symbol (aka, publication symbol) Can edit. Can’t edit . Comes from Mapunit table.

  7. NASIS review • Project • How update soil survey is managed • Created in NASIS 6 • Used to manage map units, mapping goals, and progress • MLRA SSO will be able to create and edit projects

  8. Overview of SDJR • A national initiative designed to emphasize and accelerate the ongoing MLRA approach to soil survey • Requires an evaluation of all map units owned by a MLRA SSO • Will result in: • Recorrelated and up-to-date map units, which will minimize the tabular data discrepancies that occur between similar or identical map units. • A comprehensive list of future projects

  9. Three SDJR Objectives • Evaluate map units in your MLRA SSA • Update NASIS for map units that can be harmonized • Document future projects identified during evaluation and harmonization

  10. Overview of SDJR • NASIS database initiative • Only working on tabular data (NASIS) • Soil lines will not be edited • Intention is to improve joins between soil survey areas by reducing the number of unique map units and data map units (DMU) in NASIS

  11. Overview of SDJR • Focuses on identically and similarly named map units, which are linked to more than one DMU • Intended result is for identically and similarly named map units to use the same up-to-date DMU • Legend map unit symbols will not be changed

  12. Overview of SDJR A new up-to-date DMU is created and both map units are linked to it. The original legend map unit symbols are retained.

  13. Overview of SDJR • NOT a spatial initiative • Soil lines will not be edited • At this time, the guidance for spatial editing is as follows: • “Any time a spatial edit is required to complete a SDJR project, it is no longer a SDJR project, but instead becomes a future project.”

  14. Overview of SDJR • New mapunits and DMUs created • Original map units retained and made additional in the Legend Mapunit table • Original DMUs retained and are linked as non-representative to the new map unit • No existing data will be modified • Only new data created

  15. What Triggered SDJR? • The USDA-NRCS Soil Survey program intends to: • Accelerate MLRA approach to soil survey • Develop a “road map” for conducting update soil survey • Create standards for updating tabular data • Develop systematic and consistent methods for populating the Project Object

  16. What Triggered SDJR? • The Soil Survey program needs to position itself as a viable program • Sell ourselves to the decision makers • Thematic maps of proposed future projects can be generated • The amount (acres of map units) of proposed work can be easily displayed

  17. SDJR Technical Team • Charged with developing SDJR national instructions • Hold monthly teleconferences to discuss the SDJR initiative • Comprised of 20 people • One SDQS from each MO • Paul Finnell, NSSC NASIS Database Manager • Cameron Loerch, National Leader, Soil Survey Standards

  18. Who is Working SDJR? • All MLRA SSOs that are not working on initial or extensive revision soil surveys will be focusing on SDJR • Those MLRA SSOs working on initial or extensive revision soil surveys will only harmonize matching map units and identify future projects

  19. How Much Time Is Spent on SDJR? • At a minimum, it will be enough time to satisfy your SDJR acre goals • Expect to focus 50%-75% of your time on SDJR • Your remaining time will be spent working on already initiated update projects, evaluations, 01, etc….

  20. What about field work? • SDJR is a database initiative • Projects that require field work are considered future MLRA projects • The short answer is there is no field work for SDJR

  21. SDJR Timeline • FY12 • MO staff assigns ownership of map units • MO staff provides SDJR training • MLRA SSOs evaluate map units • Organize map units into proposed projects • Begin identifying future projects • MLRA SSOs complete at least one SDJR project • Provide feedback to MO • FY13 • SDJR officially begins • Acre goals are set

  22. Acre Goals • Who, when, and how acre goals are set is still to be determined • Goals will most likely be based on the map units that you own in NASIS • Same named or similar named map units included in goals????

  23. Project Acre Goals • Each project will have an acre goal • Will be 20% of the total acres of map units included in your project • Populated in the Project Mapping Goal table

  24. Progress Reporting • Progress will be reported for each SDJR project after QA and correlation are completed by the MO office • Progress is recorded in the Project Mapping Progress table as 20% of the map unit acres that were harmonized

  25. Progress Reporting • The acres listed in the “Project Mapping Goal” table will not always equal the acres claimed in the “Project Mapping Progress” table • All map units included in a proposed SDJR project will not always be harmonized • In many instances, only some of the map units will be harmonizable • Non-harmonizable map units will become future MLRA projects

  26. Acre Goal and Progress Example Project Name: SDJR – MLRA 2 - Alderwood 0-15 percent slopes Total Acres for this project are 13,000 Project Acre Goal will be: 13,000 * 0.20 = 2,600 acres

  27. Acre Goal and Progress Example Project Name: SDJR – MLRA 2 - Alderwood 0-15 percent slopes Only able to harmonize the map units in red, which sum up to 6,400 acres Progress Reported (acres claimed) will be: 6,400 * 0.20 = 1,280 acres

  28. Roles and Responsibilities • National Headquarters • Provide direction • Set goals • Track progress and post results • Brief states on initiative

  29. Roles and Responsibilities • National Soil Survey Center • Establish and guide SDJR Technical Team • Provide national training • Ensure consistency • Provide national oversight on progress • Develop success metrics to monitor progress

  30. Roles and Responsibilities • State Soil Scientist • Inform State Conservationists, cooperators, and users about priorities and progress • Help establish priorities • Certify data • Serve as member of Management Team

  31. Roles and Responsibilities • MLRA Regional Office (MO1) • Train and support MLRA SSOs in the SDJR initiative • Provide SDJR data sets • Conduct QA on all SDJR projects • Ensure consistency across MLRA SSOs • Make changes to official legends in NASIS

  32. Roles and Responsibilities • MLRA Soil Survey Offices • Evaluate map units within the MRLA SSA • Propose SDJR projects and future MLRA projects • Follow SDJR national instructions for managing projects • Document evaluation findings • Complete approved SDJR projects • Generate up-to-date MLRA map units • Conduct QC on all completed SDJR projects

  33. Roles and Responsibilities • MLRA Management Team • Review, approve, and prioritize proposed SDJR projects

  34. Projects • Each map unit owned by your MLRA SSO will be evaluated in placed in one of these categories: • SDJR Projects • MLRA Projects • Non-projects

  35. Projects • SDJR Projects • Proposed projects • Require no field work or spatial edits • Similarly or identically named map units • Will contain SDJR at the beginning of the project name • SDJR – MLRA 2 – Alpha silt loam 0 to 8 % slopes

  36. Projects • MLRA projects • Future projects • Any project that requires field work or spatial line edits is a MLRA project • Will contain MLRA at the beginning of the project name • MLRA – MLRA 2 – Beta loams

  37. Projects • Non – Projects • Unique map units will not be included in SDJR or MLRA projects, unless you know these map units require some type of future project work

  38. Projects • As you evaluate and attempt to update map units in a SDJR project, you may identify the need for additional field work before any updating of some or all of the map units can occur • In these instances, those map units identified as needing field work are shifted to a future MLRA project and your evaluation findings (what work needs to be done) is included in the project descriptions

  39. Project Descriptions • Narrative statements that details history, location, acreage, reasoning for project, expected workload, theories, etc… • All projects must have a description • There are examples of project descriptions in the SDJR National Instructions, Exhibit D

  40. Project Descriptions • Proposed SDJR projects • Each SDJR project is a NASIS database update project • Descriptions are expected to be relatively shorter and concise since the workload will be somewhat straight forward and similar for each project • Future MLRA projects • Each MLRA project will be unique • Descriptions are expected to be relatively longer and thorough since you will need to carefully outline the unique issues and expected workload

  41. National Instructions • A harmonization road map • Supplemented with the following guides: • National Soil Survey Handbook • 608, 609, 610, & 627 • Soil Survey Manual • Chapter 2 • NASIS 6.0 Training Materials • Chapter 14 – Managing Update Projects • MO1 Technical Note 38 & 40

  42. National Instruction Workflow

  43. National Instruction WorkflowObtain Project Approval • Inventory and assess map units owned by your MLRA SSO • Use the Excel spreadsheet to group similar and identical named map units into proposed SDJR projects, future MLRA projects, or non-projects • Propose priorities based on acres or use and management concerns

  44. National Instruction WorkflowObtain Project Approval • Populate projects in NASIS • NASIS 6.0 Training Materials - Chapter 14 contains detailed instructions on how to populate the Project object • For both proposed SDJR and future MLRA projects, populate the following fields in the Project table: • Project Name • Project Description • Approval • All projects are initially “Not Approved” • MLRA SSO Area Symbol • MLRA SSO Area Name • State Responsible

  45. National Instruction WorkflowObtain Project Approval • Populate projects in NASIS • For all map units grouped into a project, populate the following fields in the Project Mapunit table: • National Mapunit Symbol • Mapunit Name • Mapunit Status

  46. National Instruction WorkflowObtain Project Approval • Proposed SDJR Projects reviewed • MO SDQS will review proposed projects and provide feedback to the MLRA SSO • After MO SDQS review, the MLRA SSO will notify the MLRA management team, which will then review, approve, and prioritize project plans • Future MLRA projects are not reviewed by the management team at this time

  47. National Instruction WorkflowObtain Project Approval • Approved Project is developed • MLRA SSOL will change project to “Approved” • In the Project Land Category Breakdown table, populate: • Land Category • Land Category Acres • The total of land category acres must equal the total of map unit acres • In the Project Mapping Goal • Update NRCS Acres Goal • Must equal 20% of the total acres in The Project Land Category Breakdown table • Fiscal Year

  48. National Instruction WorkflowObtain Project Approval • Approved Project is developed • In the Project Staff table, populate: • NASIS User Name • Project Leader? • Begin populating the Project Milestone table according to national instructions • Create new MLRA DMU(s) and map unit(s) and add new map unit(s) to the Project Mapunit table

  49. National Instruction WorkflowManage Approved Projects • Create spatial distribution maps • Thematic maps of project map units • Compile historical information • Manuscripts, laboratory data, university data, official soil survey records, pedons, and expert knowledge

  50. National Instruction WorkflowManage Approved Projects • Enter pedons into NASIS • Locate OSD and all TUDs in manuscripts • Make sure OSD classification is up to date • Review classifications of TUDs • Confirm that TUDs are within OSD concept • Map units using TUD’s outside the range of the OSD as the RV pedon need be turned into future projects • Enter all TUDs and OSD into NASIS • Enter additional pedons into NASIS