1 / 33

NHD Update Process Improvement Project

NHD Update Process Improvement Project. Kevin McNinch , Dave Hughes, Paul Kimsey. U.S. Department of the Interior U.S. Geological Survey. Current NHD Tools. NHD Geo Edit v3.3.2 Official release 04/18/2010 ArcGIS 9.3 sp1 & ArcGIS 9.3.1 NHD Model 1.06. Current NHD Tools.

step
Download Presentation

NHD Update Process Improvement Project

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. NHD Update Process Improvement Project Kevin McNinch, Dave Hughes, Paul Kimsey U.S. Department of the Interior U.S. Geological Survey

  2. Current NHD Tools • NHD Geo Edit v3.3.2 • Official release 04/18/2010 • ArcGIS 9.3 sp1 & ArcGIS 9.3.1 • NHD Model 1.06

  3. Current NHD Tools • NHD Geo Edit v3.3.3 • Official release planned 06/07/2010 • ArcGIS 9.3 sp1 & ArcGIS 9.3.1 • Compatible with NHD Model 1.07 • Permanent Identifiers & ComID (retired in 1 year) • External Crosswalk table • Backward compatibility to Model 1.06 • Compatible with NHD Model 2.0 • WBD replaces old 1:250k hydrologic units

  4. NHD Update ProcessImprovements Short Term 0-1 Years

  5. NHD Update ProcessImprovements • WHY do we need to do this in the short term?

  6. What do the Stewards Say: Maintenance is too difficult. Inconsistent results after editing. Need “direct” editing of the NHD data. Quick and simple edits need to be easy. Software installation and performance is an issue.

  7. Status of Stewardship Today (Sub basins) 0

  8. The Net Result After five years of stewardship, the program is not as advanced as it should be.

  9. NHD Update ProcessImprovements • WHAT do we need to do to streamline the current process?

  10. NHD Update Process Improvement Project • Charter • 02/01/2010 • Survey • Distributed to all partners • Compiled results from 23 respondents • Requirements Document • Draft April, 2010

  11. Process Enhancements, Requirements Specifications: • Ranked in order of High to Low: • Refactor code for NHD tools and utilities • Single Installation Package for all NHD Update Process Tools and Utilities • Merge all current NHD toolbars into one toolbar with logical progression of tasks

  12. Requirements Specifications: • Utilize ArcSDE Versioning to manage NHD Update Process data transactions • Allow editing with NHD GeoEdit Tool in geographic coordinate system • Create queue for QC checks • Create queued edit tool

  13. Requirements Specifications: • Make all NHD Update Process tools compatible with ESRI Personal Geodatabases (PGDB) and ESRI File Geodatabases (FGDB) • Refactor NHD Update Process tools so that they are not reliant on ESRI Task Assistant

  14. Requirements Specifications: • Incorporate NHD Plus build and refresh QC checks to support NHD Plus creation • Update process workflow to use ESRI ArcGIS Job Tracking Extension (JTX) • Improve Metadata Process

  15. Requirements Specifications: • Reach Code Allocation utility process updates • Bug Fixes and enhancements from NHD development group list • Update tools and installation package to work with ArcGIS 10.0 when released

  16. NHD Update Process • Current process (29 steps)

  17. Flow Diagram for Current NHD Maintenance Process NHD Stewardship Web site XML Extract Reproject XML2pgdb 1804_qc 1804_qc1.mdb Copy of NHD75464.mdb with transactions applied 1804_alb 1804_alb.mdb All edits performed on this mdb Extract from database NHD75464.zip Corrections ? Yes Reproject UnZip No Make copyof final 1804_geo.mdb and name it 1804_geo_load.mdb 1804_geo 1804_geo.mdb 1804_alb.mdb reprojected to geographic 1804_orig 1804_orig.mdb Save zip file in this folder 1804_geo_load 1804_geo_load.mdb Used for build flow, releveler and final XML extract

  18. Steps that can be eliminated from the current NHD Maintenance Process NHD Stewardship Web site XML Extract Reproject XML2pgdb 1804_qc 1804_qc1.mdb Copy of NHD75464.mdb with transactions applied 1804_alb 1804_alb.mdb All edits performed on this mdb Extract from database NHD75464.zip Corrections ? Yes Reproject UnZip No Make copyof final 1804_geo.mdb and name it 1804_geo_load.mdb 1804_geo 1804_geo.mdb 1804_alb.mdb reprojected to geographic 1804_orig 1804_orig.mdb Save zip file in this folder 1804_geo_load 1804_geo_load.mdb Used for build flow, releveler and final XML extract

  19. Flow Diagram for NHD Maintenance Process after Improvements National Map Replica Checkout Run QC suite against entire dataset Run QC suite against entire dataset Update using NHDGeoEdit tool Resolve QC errors (Queued Edit tool) Resolve QC errors (Queued Edit tool) Replica Checkin

  20. NHD Update ProcessImprovements • HOW are we going to accomplish this?

  21. NHD Update ProcessImprovements • Agile Project Management - SCRUM • Requirements are captured as items in a list of “product backlog” • Iterative development in a series of four-week “sprints” • Product is designed, coded, and tested during the sprint • Responsive to changing needs

  22. Product Noise Level Far from Agreement Anarchy Complex Requirements Complicated Source: Strategic Management and Organizational Dynamics by Ralph Stacey in Agile Software Development with Scrum by Ken Schwaber and Mike Beedle. Simple Close to Agreement Technology Close to Certainty Farfrom Certainty

  23. Putting it all together Image available at www.mountaingoatsoftware.com/scrum

  24. No changes during a sprint Change • Plan sprint durations around how long you can commit to keeping change out of the sprint

  25. Roles Ceremonies Artifacts • Product owner • ScrumMaster • Team • Sprint planning • Sprint review • Daily scrum meeting • Product backlog • Sprint backlog • Burndown charts Scrum framework

  26. NHD Update ProcessImprovements • Benefits • Agile development • Frequent delivery • Improved Communication • Pro-active project management

  27. NHD Update ProcessImprovements • BENEFITSto the stewardship community • - Level of complexity allows for a much broader audience from “expert” to “knowledgeable users” • - Reduces training time • - Reduces need for constant technical support • Eliminates re-training

  28. Where Does NHD Stewardship Go From Here? • Looking beyond lifecycle of current NHD GeoEdit Tools and NHD Stewardship Processes • Current development will be as reusable as possible • Begin planning and requirements gathering—create project charter to reflect this work • Completed NHD Architecture Planning Meeting May 13, 2010 • Analysis of current process (On-going) • Create NHD Update Process that: • Addresses a broader spectrum of NHD users • Simplifies

  29. NHD User Base Some Experts Many Knowledgeable Users Huge number of Casual Users

  30. NHD Stewardship Addressed Very Well with Edit Tool Complete Edit Capability Experts Poorly Addressed No Intermediate Tool Basic Editing Knowledgeable Users Not Yet Addressed Web Edit Tool Identify and Markup Edits In development Casual Users

  31. NHD Update Process • MID TERM2-3 Years • Web-Based Markup/Editing Tools • Alabama Web Edit Tool(WET) • Requirements gathering group ongoing for national web markup/editing tool • Detailed requirements gathering and analysis • Improve web services

  32. NHD Update Process • LONG TERM 4+ Years • Evaluating other technologies, trends, and tools for future of Vector Data Stewardship • Open source or COTS tools • Open data standards • Geosyncronization • Volunteered Geographic Information (VGI)

More Related