US Department of the Interior US Geological Survey Kevin McNinch Dave Hughes Paul Kimsey Current NHD Tools NHD Geo Edit v332 Official release 04182010 ID: 652985
Download Presentation The PPT/PDF document "NHD Update Process Improvement Project" is the property of its rightful owner. Permission is granted to download and print the materials on this web site for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.
![[ YOUR PROJECT TITLE ] [ YOUR NAME ]](https://thumbs.docslides.com/776481/your-project-title-your-name.jpg)
Slide1
NHD Update Process Improvement Project
U.S. Department of the Interior
U.S. Geological Survey
Kevin
McNinch
,
Dave Hughes,
Paul KimseySlide2
Current NHD Tools
NHD Geo Edit v3.3.2
Official release 04/18/2010ArcGIS 9.3 sp1 & ArcGIS 9.3.1NHD Model 1.06Slide3
Current NHD Tools
NHD Geo Edit v3.3.3
Official release planned 06/07/2010ArcGIS 9.3 sp1 & ArcGIS 9.3.1Compatible with NHD Model 1.07Permanent Identifiers & ComID
(retired in 1 year)External Crosswalk tableBackward compatibility to Model 1.06Compatible with NHD Model 2.0WBD replaces old 1:250k hydrologic unitsSlide4
NHD Update Process
Improvements
Short Term
0-1 YearsSlide5
WHY
do we need to do this in the short term?
NHD Update ProcessImprovementsSlide6
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.Slide7
0
Status of Stewardship Today
(Sub basins)Slide8
The Net Result
After five years of stewardship, the program is not as advanced as it should be.Slide9
WHAT
do we need to do to streamline the current process?
NHD Update ProcessImprovementsSlide10
NHD Update Process Improvement Project
Charter
02/01/2010SurveyDistributed to all partnersCompiled results from 23 respondentsRequirements DocumentDraft April, 2010Slide11
Process Enhancements, Requirements Specifications:
Ranked in order of High to Low:
Refactor code for NHD tools and utilitiesSingle Installation Package for all NHD Update Process Tools and Utilities
Merge all current NHD toolbars into one toolbar with logical progression of tasksSlide12
Requirements Specifications:
Utilize
ArcSDE Versioning to manage NHD Update Process data transactionsAllow editing with NHD GeoEdit Tool in geographic coordinate systemCreate queue for QC checks
Create queued edit toolSlide13
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 AssistantSlide14
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 ProcessSlide15
Requirements Specifications:
Reach Code Allocation utility process updates
Bug Fixes and enhancements from NHD development group listUpdate tools and installation package to work with ArcGIS 10.0 when releasedSlide16
NHD Update Process
Current process (29 steps) Slide17
NHD Stewardship Web site
Extract from database NHD75464.zip
UnZip
1804_orig1804_orig.mdbSave zip file in thisfolder1804_alb1804_alb.mdbAll edits performed on this mdb
1804_qc
1804_qc1.mdb
Copy of NHD75464.mdb with transactions applied
1804_geo
1804_geo.mdb
1804_alb.mdb reprojected to geographic
1804_geo_load
1804_geo_load.mdb
Used for build flow, releveler and final XML extract
Reproject
Reproject
XML Extract
XML2pgdb
Yes
No
Make copy
of final 1804_geo.mdb and name it
1804_geo_load.mdb
Flow Diagram for
Current
NHD
Maintenance Process
Corrections
?Slide18
NHD Stewardship Web site
Extract from database NHD75464.zip
UnZip
1804_orig1804_orig.mdbSave zip file in thisfolder1804_alb1804_alb.mdbAll edits performed on this mdb
1804_qc
1804_qc1.mdb
Copy of NHD75464.mdb with transactions applied
1804_geo
1804_geo.mdb
1804_alb.mdb reprojected to geographic
1804_geo_load
1804_geo_load.mdb
Used for build flow, releveler and final XML extract
Reproject
Reproject
XML Extract
XML2pgdb
Yes
No
Make copy
of final 1804_geo.mdb and name it
1804_geo_load.mdb
Steps that can be
eliminated
from the current NHD
Maintenance Process
Corrections
?Slide19
National Map
Replica Checkout
Flow Diagram for NHD Maintenance Process after Improvements
Replica
Checkin
Run QC suite against entire dataset
Resolve QC errors
(Queued Edit tool)
Update using
NHDGeoEdit
tool
Run QC suite
against entire
dataset
Resolve QC errors
(Queued Edit tool)Slide20
HOW
are we going to accomplish this?
NHD Update ProcessImprovementsSlide21
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 needsNHD Update ProcessImprovementsSlide22
Product Noise Level
Simple
Complex
Anarchy
Complicated
Technology
Requirements
Far from
Agreement
Close to
Agreement
Close to
Certainty
Far
from
Certainty
Source:
Strategic Management and Organizational Dynamics
by Ralph Stacey in
Agile Software Development with Scrum
by Ken Schwaber and Mike Beedle.Slide23
Putting it all together
Image available at www.mountaingoatsoftware.com/scrumSlide24
No changes during a sprint
Plan sprint durations around how long you can commit to keeping change out of the sprint
ChangeSlide25
Scrum framework
Product owner
ScrumMaster
Team
Roles
Sprint planning
Sprint review
Daily scrum meeting
Ceremonies
Product backlog
Sprint backlog
Burndown charts
ArtifactsSlide26
Benefits
Agile development
Frequent delivery
Improved CommunicationPro-active project managementNHD Update Process
ImprovementsSlide27
BENEFITS
to the stewardship communityNHD Update ProcessImprovements
- Level of complexity allows for a much broader audience from “expert” to “knowledgeable users”- Reduces training time - Reduces need for constant technical supportEliminates re-trainingSlide28
Where Does NHD Stewardship Go From Here?
Looking beyond lifecycle of current NHD
GeoEdit Tools and NHD Stewardship ProcessesCurrent development will be as reusable as possibleBegin planning and requirements gathering—create project charter to reflect this workCompleted NHD Architecture Planning Meeting May 13, 2010Analysis of current process (On-going)
Create NHD Update Process that:Addresses a broader spectrum of NHD usersSimplifiesSlide29
NHD
User Base
Huge number of
Casual Users
Many
Knowledgeable Users
Some
ExpertsSlide30
NHD
Stewardship
Addressed Very Well
with Edit Tool
Complete Edit Capability
Poorly Addressed
No Intermediate Tool
Basic Editing
Not Yet Addressed
Web Edit Tool
Identify and Markup Edits
In development
Experts
Casual Users
Knowledgeable UsersSlide31
MID TERM
2-3 YearsNHD Update Process
Web-Based Markup/Editing ToolsAlabama Web Edit Tool(WET)
Requirements gathering group ongoing for national web markup/editing tool
Detailed requirements gathering and analysis
Improve web servicesSlide32
LONG TERM
4+ Years
NHD Update Process
Evaluating other technologies, trends, and tools for future of Vector Data StewardshipOpen source or COTS toolsOpen data standards
Geosyncronization
Volunteered Geographic Information (VGI)Slide33