1.) GIS features were digitized from a .TIF image of the paper/mylar map that was scanned at 300dpi and georeferenced in NAD83 UTM.  See the Source Information Contribution section(s) for specific source map details.  These GIS features were first digitized into a digitizing geodatabase with limited attribution and topological rules.  Line quality was checked against the source scan to ensure that GIS features were represented accurately, both positionally and spatially. These features were then parsed using a GRI developed script (Genesis) into their appropriate GRI data model feature classes (data layers) within a new geodatabase, and further attributed.  Topology rules were imposed and validated on all GIS data, as per the GRI data model, to check for and correct topology errors.  Quality control (QC) consisting of a visual check of the data against its source, as well as running a GRI developed script (QC_Script) to check for GRI data model validation and feature-related consistency, was conducted.  2.) GIS table attribution was derived and checked using the source map(s).  Relationship classes were also used to ensure attribution consistency between feature class and table attribution.  For details on the GRI data model see the NPS GRI Geology-GIS Geodatabase Data Model v. 2.1 (available at: http://science.nature.nps.gov/im/inventory/geology/GeologyGISDataModel.cfm).  3.) GIS feature classes were then exported from the geodatabase to shapefile (.SHP) format, and GIS tables exported from the geodatabase to DBASEIV (.DBF) format.  4.) The map-related pdf document, see the Supplemental Information section for additional information, was produced from textual information and figures present on the source map(s) and/or in digital data files.  If applicable, source map images were produced at 150dpi or greater resolution and optical character recognition (OCR) software was used to produce text from source map text.  The text, source map images and other ancillary source map information were added to a Help & Manual (.HMX) template file.  The Help & Manual (.HMX) file was then compiled to produce the .PDF map document.  Any compilation errors were then checked and corrected and the document was reviewed for content, usability and grammatical errors.