1 / 74

Mapunit Management and Data Population Issues

Mapunit Management and Data Population Issues. In reference to completing the project plan. Rationale.

blair-eaton
Télécharger la présentation

Mapunit Management and Data Population Issues

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Mapunit Management and Data Population Issues In reference to completing the project plan

  2. Rationale This module will identify the issues of consolidating the traditional map unit concepts into a map unit with a MLRA concept. NASIS6 will provide map unit management concepts and techniques to decrease database management overhead. The NASIS6 data structure will be reviewed and issues in populating the database will be discussed. 

  3. Objectives • Understand the variation in historical “map unit concepts” to build the MLRA map unit concept • Explain the database process of managing map units across political boundaries • Explain the new NASIS6 database structure and how it is used in the MLRA process • Identify database population and calculation issues

  4. What is a “Map Unit”? (NSSH 627.03 and SSM Chapter 2) Definition A map unit is a collection of areas defined and named the same in terms of their soil components or miscellaneous areas or both.Each map unit differs in some respect from all others in a survey area and each map unit has a symbol that uniquely identifies the map unit on a soil map.…

  5. What is a “Map Unit”? Map Units of Soil Surveys (NSSH 627.03) Definition …Each individual area, point, or line so identified on the map is a delineation. The project office specifically designs map unitsto meet the needs of the major usersin each major land resource area. Map units in adjoining survey areas are comparable especially within the same major land resource area.

  6. Historical map unit design • Surveys were mapped as islands, largely independent of each other • Surveys were mapped a various scales • Series concepts and taxonomy may have changed based on the age of the survey • Map unit concept fits the need of the specific survey at the time of mapping

  7. Map Unit Design The correlation process in the design of a map unit has not changed over time; what is now changing is the extent of what is deemed the “survey area”

  8. Review • Understand the historical scale of the surveys since this scale influenced the map unit design • SSURGO was compiled to 1:12000 or 1:24000 • Although the lines were recompiled to a different scale, the map unit design was not affected.

  9. Review

  10. Map Unit Design Spatially: Fayette silt loam, 9 to 14 percent slopes, moderately eroded Individually, each survey has a similarly named map unit The question: Is it the same map unit concept wherever mapped? Why does it stop at the state line?

  11. Map Unit Design Political Boundaries: Fayette silt loam, eroded, 7 to 11 percent slopes Versus Fayette silt loam, 9 to 14 percent slopes, moderately eroded Versus Fayette silt loam, 9 to 14 percent slopes

  12. Is it the same mapunit?

  13. Is it the same mapunit?

  14. Map Unit Design Just because the name says “Fayette silt loam, 9 to 14 percent slopes” within the individual surveys does not mean they all maintain the same map unit concepts due to the mapping scale and the map unit design for that given survey. The purpose of the Project Plan is to identify the map unit concepts that can be combined for the MLRA.

  15. Is it the same mapunit? • Map unit concepts must be reviewed in the manuscripts. • Typically the NASIS data has not been populated to reflect the manuscript. • NASIS contains only series/phase concept data based on the SOI-5 unless it has been edited since 1995

  16. Is it the same mapunit? • The MLRA update process should review the map unit concept for individual surveys and gather documentation to support the development of a MLRA map unit concept. • This may require multiple map units.

  17. NASIS6 How NASIS6 will assist in the management of data

  18. NASIS 6.0 Changes

  19. NASIS 6.0 Changes

  20. NASIS 6.0 Changes New object for ownership of map units

  21. NASIS 6.0 Changes Map units are viewed in context of the Legend in which they belong Map units are independent and linked to the Legend

  22. NASIS 6.0 Changes New table for linking legends and map units

  23. NASIS 6.0 Changes • Legend Mapunit table is the linkage between a legend and its map units

  24. NASIS 6.0 Changes Correlation table still exists for linking mapunits to their datamapunits

  25. NASIS 6.0 Changes • Correlation table links Map unit to its Datamapunit

  26. NASIS6 Changes

  27. NASIS 6.0 Changes

  28. NASIS 6.0 Changes • Correlation table links Map unit to its Datamapunit

  29. NASIS 6.x Mapunit Design

  30. NASIS 6.x Mapunit Design • Creation of the Mapunit Object will facilitate MLRA update process • A map unit is still linked to its’ datamapunit • However, a map unit can be shared among Legends • MLRASSO Leaders CAN NOT begin linking a map unit to multiple legends without the correlation process and understanding mapunit concept

  31. NASIS6 Management Managing Project Plans in NASIS6

  32. Load the “Local Database”

  33. Load the “Selected Set”

  34. Managing Project Plans in NASIS6 The correlated map units for the Project Plan are brought into the Mapunit table and copied

  35. Managing Project Plans in NASIS6 Then create a new Project and paste the map units in the Project Mapunit table

  36. Managing Projects in NASIS6 • Projects for the MLRA will be managed in the NASIS6 Project object • The Project table includes the name and the description • The Project name will include the MLRA • The Project Mapunit table will include the map units within the Project Plan

  37. Managing Project Plans in NASIS6 • Project staff is identified in the Project Staff table • Include all personnel – MO, NSSL

  38. Managing Project Plans in NASIS6 • Mapping Goals are identified by personnel in Project Mapping Goal

  39. Managing Project Plans in NASIS6 • Milestones are identified in the Project Milestone table

  40. Milestones – current list

  41. Managing Projects in NASIS6 • Other Project Plan tables • Correlation • Data Needs • Field Reviews • Products

  42. MLRA Mapunit Management Is it the same map unit?

  43. MLRA Mapunit Management • Step 1: create a new Project DMU – on all update projects it is SOP to create a new MU/DMU in order to preserve original published data

  44. MLRA Mapunit Management • Step 2: Populatebased on field observations for the MLRA map unit concept

  45. MLRA Mapunit Management • Step 3: Create a new Project map unit in the Mapunit table (SOP for update Projects)

  46. MLRA Mapunit Management • Step 4: Link the new MLRA map unit to the new MLRA DMU • Step 4a: Include all correlation records that the new map unit will replace – see next slide.

  47. MLRA Mapunit Management

  48. MLRA Mapunit Management • Step 4c: Document the new Project map unit in Mapunit History

  49. MLRA Mapunit Management • Step 5: Add the new Project map unit (MLRA) to the Project Plan

  50. Project Mapunit Management • Map units are managed using a Project Plan • A new Project DMU is created for the new MLRA map unit concept • A new Project map unit is added to the Mapunit table and linked to the MLRA DMU • The Project map unit will include all correlation records of the map units replaced by the MLRA map unit • The new Project map unit is then added to the Project Mapunit table • All work is managed in the Project Plan until QC/QA is completed

More Related