Toolkit 7.0 / NPAD Training

1. Toolkit 7.0 / NPAD Training Northeast and Southeast NRCS Regions January 15, 2014 Central and West NRCS Regions January 16, 2014 • Please mute your telephones and your computer microphones. • Please do not put your telephone on hold during the teleconference. • Please hold your questions until we request them.

2. Trainers Arlen Ricke, Conservation Technical Assistance and Planning Team, Washington, DC Kristie McKinley, Enterprise Business Initiatives Team, Fort Worth, TX Jennifer Zwicke, Enterprise Business Initiatives Team, Fort Collins, CO Travis Rome, Enterprise Business Initiatives Team, Salina, KS Jennifer Chen, Enterprise Business Initiatives Team, Indianapolis, IN

3. Agenda • Easements Migration • Toolkit 7.0 Exercises • Create a new plan • Edit a new easement plan • Edit a plan linked to a ProTracts contract • Other • Preparing for Data Migration and the Toolkit Update • Why Change Toolkit? • Data Migration - NCP to NPAD • New Planning Procedures Using Toolkit 7.0 • What’s New in Toolkit 7.0 • Planning Land Units (PLUs) • Working with the Area of Interest (AOI) • Views • Practices

4. Why Change Toolkit?

5. Why Change Toolkit? After the original version of Conservation Desktop was not accepted by NRCS, options were considered for projects that would continue to move the agency forward toward CDSI objectives until the new Conservation Desktop and Mobile Planner were deployed in CY2015. One option approved by leadership was getting the National Planning and Agreements Database (NPAD) on line and updating Toolkit to utilize the new database. The interim projects, which included updating Toolkit, became the Foundation Maintenance Improvement (FMI) effort.

6. Why Change Toolkit? The FMI Products Will: • Begin to streamline agency business processes by implementing a corporate document management system • Implement core CDSI ideas like the Single Plan concept and eliminating “pancaked” plans • Improve conservation planning with new land uses and resource concerns • Improve Agency performance reporting by geospatially locating all land units and practices

7. Why Change Toolkit? The FMI Products Are: • An updated Customer Service Toolkit connected to a new planning database - NPAD • A Document Management System (DMS) to store and manage financial assistance documents • Geospatial Web Services for National, State, and local GIS data • A Toolkit Erosion Plugin for wind and water erosion calculations

8. Why Change Toolkit? • Phase 1 of the Toolkit update, February 3, 2014, will include migration of planning data and modify Toolkit to work within the new database. Incorporates new land use designations and land use modifiers. • Phase 2 Toolkit updates will begin in March 2014 and include: • Providing ability to select land from multiple plans and digitize any new land to create a Conservation Stewardship Program plan. • Integrating the Conservation Measurement Tool (CMT) with Toolkit to upload new practices and activities to create a practice schedule. • Implementing a Conservation Management Units (CMUs) tool to quickly select multiple land units to schedule practices by land use. • Providing ability to unlock PLUs contracted through ProTracts to modify land unit boundaries.

9. Why Change Toolkit? • Later Updates for 2014 include: • Automating symbolization when practice is planned and certified. • Incorporating NRCS’ new resource concerns. • Integrating ArcGIS 10.2. • Ability to complete land transfers. • Calculating soil loss for PLUs with the Integrated Erosion Tool Plug-In.

10. Why Change Toolkit? Impacts on Field Users • Toolkit will be shut down for up to 6 days during migration. • Toolkit users must learn new plan development processes. • The Performance Results System (PRS) will no longer be used for conservation planning data entry. • PRS Reporting from ProTracts will be eliminated. • PRS NCP Data Viewer and Data Checker Tools will be eliminated. • Access to IDEA, CARS and PRS Reports may be delayed during NPAD migration.

11. Data Migration PLAN DATA National Conservation Planning Database (NCP) National Planning and Agreements Database (NPAD)

12. Data Migration - NCP to NPAD A key component of FMI is to implement a new conservation planning database. All active plans that have a minimum of land unit and one practice in the National Conservation Planning (NCP) Database will be migrated to the new National Planning and Agreements Database (NPAD).

13. Data Migration - NCP to NPADWhat is Migrating • All active plans and land units that have practices will migrate to NPAD. • Any plan that was archived but linked to an active contract will migrate to NPAD as an active plan. • Easements that did not have a plan in Toolkit but have a valid SCIMS ID in NEST will migrate as a new plan that only contains the easement boundary as the only land unit.

14. Data Migration - NCP to NPADWhat is Not Migrating • Archived plans are not migrating to NPAD for check out in Toolkit. The information from these plans can still be found from other reporting tools such as IDEA, PRS and/or CARS. • Plans that do not have any land units or practices. • Land Units that do not have any practices. • Easements that do not have a valid SCIMS ID in NEST and do not have a plan that was renamed in Toolkit

15. Data Migration - NCP to NPAD Migration to NPAD will incorporate the business rules for migrating all active conservation plans based upon the below priority order of plans • Easements • ProTracts Contracts and Applications • CRP • CSP • General Plans During migration, land units are identified by a geometry status as to which land units need cleanup after migration.

16. Land Unit Migration All land units must be migrated as a polygon. • If a land unit polygon is mapped it will migrate to NPAD. • Any land units that are unmapped that have a practice will migrate as a polygon that is the shape of a triangle. The triangle will be located around the practice point (lat long) associated to the practice. • Any land units that are unmapped but the practice does not have a point (lat long) will migrate as a triangle to the county seat.

17. Practice Migration • All practices must migrate with a practice shape. • If there is an existing practice shape it will migrate. • If there is no practice shape a practice shape will be generated during migration in the correct point, line or polygon feature class.

18. Land Use Migration

19. Questions?

20. New Planning Procedures Using Toolkit 7.0

21. What’s New in Toolkit 7.0?

22. What’s New in Toolkit 7.0? • Connects to the new National Planning and Agreements Database (NPAD) • Eliminates pancaked Planned Land Units (PLUs) in the conservation plan • Implements new Land Use designations and Land Use modifiers • Integrates Easement Boundaries into the Active Land Unit Layer • Requires digitizing or copying boundary of practices into the Practice Layer

23. What’s New in Toolkit 7.0? • Integrates geospatial services by utilizing web map services (WMS) • Removes manual Performance Results System (PRS) reporting • Implements entering additional practice information to track Identified Priorities for Working Lands for Wildlife • ProTractsprogram codes are not selectable when scheduling conservation practices.

24. Planning Land Units (PLUs) Field 1 135.7 ac Range Grazed

25. PLUs • The Planning Land Unit is a unique geographic area, defined by a polygon, that has common land use and land use modifier, and is owned, operated, or managed by the same client(s). • Planners are required to digitize and attribute PLUs as the initial step when developing conservation plans. • A PLU can be associated with only one conservation plan. • The association between a PLU and a Conservation Plan cannot be deleted if the PLU is Locked or is an Easement. (Future release will allow PLU to be transferred to another plan) • A new PLU must be created and attributed in ArcMap and checked in before practices can be planned.

26. PLUs Planners will be required to create PLU polygons using an approved method. • a. Check in Legacy NCP land unit data and geometry into NPAD. • b. Digitize heads-up on an acceptable base image. • c. Import shapefile(s) collected by a NRCS planner using GPS. • d. Import geometry shapefile(s) provided by clients, TSPs, surveyors, etc. • e. Copy a polygon from one of these sources and paste it to the PLU layer: • FSA CLU layer • Resource Inventory Layer • Practice layer • NRCS National Easements layer (WRP, GRP, EWP-FPE, FRPP, GRP) • NRCS soils layer or interpretation theme

27. PLUs • Planners must create the polygon first and then attribute it. • a. Planners will not be permitted to enter attributes without first creating the PLU geometry. • b. Planners will not be permitted to add a PLU record to the national database unless the record has topologically correct geometry and the minimum required attributes.

28. PLUs • A PLU may be a single or multi-part polygon. • This example shows a multi-part PLU that is contained within a WRP easement.

29. PLUs • Horizontal overlap will be enforced for the Active PLU layer geometry status of Plan and Locked. • a. No overlapping of these polygons. • Associations between PLUs and other planning layers. • Practice layer • i. Each practice must be associated with at least one PLU.

30. PLUs • A PLU has only one planned land use. • a. Each part of a multi-part PLU polygon must have the same land use. • A PLU may have zero, one or many planned land use modifiers. • a. Each part of a multi-part PLU polygon must have the same planned land use modifier(s).

31. PLUs PLUs near or within a conservation easement boundary may not cross the easement boundary. The easement boundary must be fully contained by PLUS of the program subtype.

32. PLUs PLU Work Flow Check In Land Unit Add/Edit Land Unit in AOI Attribute Land Unit

33. PLUs Land Unit Geometry Status The Land Unit Geometry Status displays the current status of the land unit in Arc Map. The Land Unit Geometry Status can only be seen by using the Digitizing View in Arc Map. • The Toolkit PLU Status Designations are: • Plan • Locked • Easement • Legacy • Draft • Sketch • Each geometry status is defined in the following slides.

34. PLUs

35. PLUs

36. PLUs

37. PLUs

38. PLUs

39. PLUs

40. Working with the Area of Interest (AOI)

41. Working with the AOI Overlap Overlap is how point, lines and polygons share geometry. Overlap rules are topology rules used to ensure data quality and to allow your geodatabase to represent your features in a more realistic way. The following diagram demonstrates how the rule “Must Not Overlap” is applied to Land Unit polygons. The rule “Must Not Overlap” guarantees that no polygon (PLU) can overlap another polygon that is in the same feature class or subtype. However, they can share edges or vertices. If an error occurs (shown in red) it must be corrected before it can be checked into the database.

42. Working with the AOI Toolkit 7.0 enforces these overlap rules for PLUs using an Area of Interest (AOI). • By default, when an existing plan is checked out in Toolkit, the system automatically generates an AOI layer by selecting all PLUs bound to the PLAN and buffering .25 mile. If PLUs are not adjacent, multiple AOI polygons will be created that are all buffered .25 mile around PLUs

43. Working with the AOI • Toolkit 7.0 requires all PLUs to be created and edited within an AOI. • When the AOI is created, the system will return all land units from within and outside the selected plan. • PLU geometry within the AOI that are outside the plan are read only and cannot be edited. • PLU geometry within the AOI are used for enforcing overlap and displaying PLUs from other plans by selecting and reviewing PLU attribute information. • In new plans there will be an AOI layer that is empty until the planner adds an AOI boundary using the AOI Tool in Arc Map that allows the planner to Add New AOI.

44. Working with the AOI • The AOI is editable by the planner from Arc Map by using the AOI Tool and selecting either Extend AOI or Add AOI. Selecting the Add AOI button allows the planner to draw an AOI using a freeform polygon shape. • If the AOI is expanded in ArcMap, but no land units are added the AOI is returned to the original buffer when the plan is checked out again.

45. Working with the AOI • When the planner submits a AOI Request, the AOI shape will be sent to NPAD and intersected with the active PLU layer. • The NPAD system will return the entirety of the set of PLUs requested that intersect the AOI bounding box requested by the planner. • If the planner tries to draw or copy a PLU outside the AOI the system will return a message to the planner to draw or expand the AOI. • In the AOI tool the planner is required to check a box to indicate if the PLUs requested should contain the PLU Legacy layer in addition to the default of the Active PLU Layer.

46. Questions?

47. Views

48. Toolkit Views • Views • There are two views that are used to display the Conservation Plan. • Plan View (current functionality) is the default set in Arc Map that displays the PLUs in a yellow outline. This view is primarily used for viewing, printing and displaying the plan boundaries. • Digitize View (new functionality) is the view that displays the PLUs by the geometry status codes. This view is primarily used when using the Land Unit Editor tool and the Check In tool.

49. Toolkit Views • There are two ways to change views. • • On the Toolkit toolbar click the Toolkit Digitizer tool button to go to from the Plan View to the Digitizing View. • • To toggle back and forth from the Digitizing View to the Plan View click the Change Views button on the Toolkit toolbar.

50. Toolkit Views Plan View Digitize View