U.S. Department of the Interior U.S. Geological Survey GNIS/ Vector Integration: Jerry Ornelas (NGTOC –Denver) NHD Stewardship Conference April 13-17, 2009

Briefing Objectives  Project Scope  Development Scope  Impacts to the User Community

GNIS/Vector Problem Statement  Problem statement:  The Geographic Names Information System (GNIS) was developed pursuant to statutory and business requirements of the U.S. Board on Geographic Names with regard to national standardization of feature names and locations. Additional requirements have developed concerning federal and national standardization of geographic feature record identifiers and associated geolocation codes. The National Vector System is under development in response to requirements of The National Map. Additional requirements are being defined in order to support the Graphics production process.  For the most part, these requirements overlap or are mutually supporting. Current TNM operations feed feature data into the two separate systems. This situation results, in the accrual of operational and maintenance costs for two separate data ingestion and update processes, as well as the need for additional processes to reconcile and resolve differences between data in the two systems. This also creates a need to coordinate the planning and execution of data collection contracts and agreements for Names and Vectors.  Integration the current GNIS & Vector databases and acquisition applications

Project Scope (today)  GNIS  Acquisition  Names Management  Modifications and New Names  Metadata  Source Originator (form biblio)  Auditing Transactions  Delivery  GAZ Support Services  GNIS Shape Files  GeoNames Services  Database  Oracle Database  Web Forms  PL/SQL Procedures  Some Oracle Spatial

Project Scope (today)  Vector ( NHD, Structures, Boundaries, and Transportation )  Acquisition  Names Management  New Names Structures  Vector/NHD Stored Names  Metadata  Source Originator  Process Description  Auditing Transactions  Delivery  Vector Extracts  Personal/File GeoDatabases  Pre-defined Model Structure  Viewer Services  Database  Oracle Database  ArcObject.Net Tools  ArcObject.Net Applications  SDE  GeoDatabase

Project Scope (today)  Vector / GNIS Problem breakdown  Acquisition  Separate applications  GNIS Forms/ Geo Edit Tools  No consistent verification process to acquire spatial representations  GNIS Coordinates does not always represent the true spatial representations  Timing New Name acquisition  Metadata stored as a different format  Delivery  Inconsistent results on delivery to GNIS and Vector Community  Duplicates Representation  Same GNIS ID w/Two different Names (GNIS/Vector)  Spatial Representation (Shape / Lat Long Coordinates)  Spatial Representation (Spatial Accuracy)  Service Representation  GNIS and Gaz Services No Vector representation  Vector (NHD) Viewer min GNIS presents  TNM (Represent both as two entities)

Project Scope (today)  Vector / GNIS Problem breakdown (cont)  Delivery (cont)  Extracts  Different formats  GNIS is not part of the Vector Model  GNIS is not delivered with Vector Extracts  Vector is not delivered with GNIS  Database  Two separate databases  Inconsistent results Stored in Database  Duplicate representation  Same GNIS ID w/Two different Names (GNIS/Vector)  Spatial Representation (Geometry Shape / Lat Long Coordinates)  Spatial Representation (Spatial Accuracy)

Project Scope (today)  Target Solution  Acquisition  Consistent Acquisition set of Tools or Applications  One consistent validation process  Attrib and Spatials  True Spatial representations  Timing Issue is no longer  Metadata Format  Gaz points derived  Delivery  Consistent results on delivery to GAZ and Vector Community  Service Representation  GNIS/Gaz Services and Vector (NHD) Viewer, TNM Viewer  Fully represented  Extracts  Same delivery formats  GNIS part of the Vector Model  GNIS/Vector is delivered together

Project Scope (today)  Target Solution (cont)  Database  One databases  Consistent results Stored in Database  No Duplicate representation  Data Integrity  Spatial Representation (Shape Only)  Spatial Representation (Valid Spatial Accuracy)  Stored Metadata Format

Development Scope  Integrate Database Phase (Migration)  Migrate GNIS into a Integrated Database  Min adjust front-end and back-end process and applications  June 1st implementation  To Be Phase  Develop or Modify Acquisition tools or applications  Develop or Modify the Delivery methods  2009 EOFY implementation  Full conflation (when Unknown?)  Why Phase Approach  Lots of Resources to Conflate the Vector DB and GNIS  Approach Benefit  Database Integrated  Application and Tools Integrated (by EOFY)  New and Modified transactions will be conflated  Full conflation can take place (existing features)

Impacts on the User Community  No substantial interruption of current business processes, product and service delivery. Examples:  Coordination of data collection operations  Input and validation of vector data  Board on Geographic Names processes  Input and validation of gazetteer data  Operational products and services  Business as Usual ?  Exceptions  Once a feature is conflated with GNIS, Only Structure Point Spatials can be modified in GNIS forms  All others go thru Vector Applications  As of end of FY 2009  Tools and Application in place  Acquire and modify Vector and Names representations  Data Management of those edits in place to process and deliver

Current View

At Migration Cutover (June 1 st )

ToBe Target ( EOFY 2009 )

GNIS/ Vector Benefits  Single Integrated DB  Normalized Data  Single Point of Management  High Reliability & Quality Assurance  Integrated Schema (attribute)  Streamline the Names integration with Vector  Feature Name (one place, one name result)  Vector Features represented by GAZ Services

GNIS/ Vector Key Stakeholders  Product Service Leads  TNM Database Stewards  TNM Programs  Graphics Program  Vector Community

Migration Project Team  Project Oversight  James Flaherty  Lou Yost  Paul Wiese  George Costantino  James Barrett  David Hughes  Maria McCormick  Working Group  Lisa Kok (Denver Dev Team)  Dwight Hughes (HQ Dev Team)  Linda Liu (HQ Dev Team)  Lei Sun (HQ Dev Team)  Vickie Dougherty (Denver Dev Team)  Colleen Keeling (Denver Dev Team)  Jessica Janssen (Denver Dev Team)  Jerry Ornelas (Denver Dev Team)

Questions? 18