Agency-wide Implications for Alaska DGGS building a Statewide Geologic 1:100,000 Compilation from an NCGMP09 Multi-map Database (presentation): Digital Mapping Techniques Workshop, Tallahassee, Florida, May 22-25

Abstract

The Alaska Division of Geological & Geophysical Surveys (DGGS) has undertaken the challenge of developing a multi-map, multiuser database model based on the single-map NCGMP09 geologic map schema developed by the USGS and state geological surveys. The new multi-map model is intended for national use, as is a pilot data-sharing protocol to be developed with the model. Over the next three years, DGGS is seeking interested individuals to take part in discussions via teleconferences to provide input on the needs of geologic surveys and other organizations and help develop the specifications of the database model and data-sharing protocol. A multi-map geodatabase will help DGGS meet the future goal of a 1:100,000-scale Alaska compilation, and provide a vehicle for other geologic surveys and agencies to organize and share their own geologic data. Slide 1. DGGS has planned to incorporate a statewide "enterprise" geologic database into its business processes for almost two decades. At the end of 2000, we began fleshing out a schema based on the North American Data Model (NADM; Freeman, 2001). By 2005, DGGS had created a database model that encompassed most of the functions of the survey, including field, geologic, analytical, and archival data; publications; and some administrative tasks like invoicing. Population of most of the database at that time, however, was delayed, because the amount of overhead needed to run Oracle Spatial and Esri's SDE, a separate Esri product at the time, was beyond the resources of the survey. Ten years later we still recognize the importance of a comprehensive data management system, and we are re-engaged with a new plan, new staff, and the new geologic data model NCGMP09 from which to build. Currently in DGGS's enterprise database environment, publications and physical materials are successfully managed, field and analytical data are partially managed, and geologic data are largely unmanaged. With the goal of a seamless 1:100,000-scale map of Alaska in the future, DGGS is beginning a project to develop and implement a database that can contain multiple geologic maps, allow for multiple users at the same time, and provide standardized across the various data sets. Slide 2. DGGS would like to go about this project in a different way-by engaging the geologic community-for two reasons. First, the Environmental Protection Agency's (EPA) Environmental Information Exchange Network Grant Program (https://www.epa.gov/exchangenetwork) has tentatively funded the creation of a multi-map geologic database and data-sharing schema over three years. The Exchange Network's philosophy is to create communication and data-sharing networks among data users and producers in the EPA, states, and other agencies, with the goals of more robust

Alaska GeMS Geologic Mapping System Status Report: January 1, 2016–June 30, 2023

“…This searchable database of map images and files went live in 2005, and GIS data became available in 2007 (DGGS Staff and Papp, 2005). At this time, DGGS also saw a marked increase in online activity as customers accessed the website for digital versions of publications (Athey and DGGS Staff, 2014;Athey, 2017).…”

“…In 2016, with endorsement from the NGMDB, DGGS engaged in preliminary development of an enterprise, multi-map database schema and computing infrastructure with three years of funding from the Environmental Protection Agency (EPA), Environmental Information Exchange Network (Athey and Hendricks, 2016;Athey and others, 2017Athey and others, , 2018Athey and others, , 2019Athey and others, , 2020. For the EPA-funded project, DGGS delivered a preliminary schema of the multi-map database, as well as a data dictionary, documentation of the Arc-GIS Enterprise-PostgreSQL computing environment, and a pilot lightweight data-transfer schema (geologic feature service) for geologic polygons, contacts, and faults, with documentation.…”