Unpublished Digital Geologic Map of Glen Canyon National Recreation Area and Vicinity, Utah, Arizona (NPS, GRD, GRI, GLCA, GLCA digital map) adapted from Utah Geological Survey digital data and map by Willis and Ehler (2011), and a Utah Geological Survey Open-File Report map by Doelling and Willis (1999)

Metadata also available as

Frequently-anticipated questions:

What does this data set describe?
    Title:
    Unpublished Digital Geologic Map of Glen Canyon National Recreation Area and Vicinity, Utah, Arizona (NPS, GRD, GRI, GLCA, GLCA digital map) adapted from Utah Geological Survey digital data and map by Willis and Ehler (2011), and a Utah Geological Survey Open-File Report map by Doelling and Willis (1999)
    Abstract:
    The Unpublished Digital Geologic Map of Glen Canyon National Recreation Area and Vicinity, Utah, Arizona is composed of GIS data layers complete with ArcMap 9.3 layer (.LYR) files, two ancillary GIS tables, a Map PDF document with ancillary map text, figures and tables, a FGDC metadata record and a 9.3 ArcMap (.MXD) Document that displays the digital map in 9.3 ArcGIS. These data formats also fully represent all of the features present on a GRI digital map, as well as containing related ancillary information GIS data tables. The data is also available as a 2.2 KMZ/KML file for use in Google Earth. Google Earth software is available for free at: <http://www.google.com/earth/index.html>. Users are encouraged to only use the Google Earth data for basic visualization, and to use the GIS data for any type of data analysis or investigation. The data were completed as a component of the Geologic Resources Inventory (GRI) program, a National Park Service (NPS) Inventory and Monitoring (I&M) Division funded program that is administered by the NPS Geologic Resources Division (GRD). Source geologic maps and data used to complete this GRI digital dataset were provided by the following: Utah Geological Survey. Detailed information concerning the sources used and their contribution the GRI product are listed in the Source Citation sections(s) of this metadata record (glca_metadata.xml; available at <http://nrdata.nps.gov/glca/nrdata/geology/gis/glca_metadata.xml>). Users of this data are cautioned about the locational accuracy of features within this dataset. Based on the source map scale of 1:100,000 and United States National Map Accuracy Standards features are within (horizontally) 50.8 meters or 166.7 feet of their actual location as presented by this dataset. Users of this data should thus not assume the location of features is exactly where they are portrayed in Google Earth, ArcGIS or other software used to display this dataset. All GIS and ancillary tables were produced as per the NPS GRI Geology-GIS Geodatabase Data Model v. 2.1. (available at: <http://science.nature.nps.gov/im/inventory/geology/GeologyGISDataModel.cfm>). The GIS data is available as a 9.3 personal geodatabase (glca_geology.mdb), and as shapefile (.SHP) and DBASEIV (.DBF) table files. The GIS data projection is NAD83, UTM Zone 12N, however, for the KML/KMZ format the data is projected upon export to WGS84 Geographic, the native coordinate system used by Google Earth. The data is within the area of interest of Glen Canyon National Recreation Area, as well as Rainbow Bridge National Monument (RABR), Canyonlands National Park (CANY), Capitol Reef National Park (CARE) and Grand Canyon National Park (GRCA).
    Supplemental_Information:
    The data layers (feature classes) that comprise the Unpublished Digital Geologic Map of Glen Canyon National Recreation Area and Vicinity, Utah, Arizona include: GLCAGLG (Geologic Units), GLCAGLGA (Geologic Contacts), GLCASUR (Major Water Body Extent), GLCACN1 (Structure Contours showing base of the Navajo Sandstone (Jn)), GLCAFLD (Folds), GLCAFLT (Faults), GLCAGLF (Geologic Line Features), GLCAJLN (Linear Joints), GLCAATD (Geologic Attitude and Observation Localities), GLCAGPF (Geologic Point Features), GLCASYM (Map Symbology), GLCACN2 (Structure Contours showing base of the Carmel Formation (Jc)), GLCACN3 (Structure Contours showing top of the Navajo Sandstone (Jn)), GLCACN4 (Structure Contours showing top of the Permian), GLCACN5 (Structure Contours showing top of the Morrison Formation (Jm)), GLCACN6 (Structure Contours showing top of the Wingate Sandstone (JTRw)), GLCACN7 (Structure Contours showing top of the Permian and Hoskinnini Member of the Moenkopi Formation), GLCACN8 (Structure Contours showing top of the White Rim Sandstone (Pwr)) and GLCAGML (Geologic Measurement Localities). There are three additional ancillary map components, the Geologic Unit Information (GLCAUNIT) Table, the Source Map Information (GLCAMAP) Table and the Map PDF Document (glca_geology.pdf). Refer to the NPS GRI Geology-GIS Geodatabase Data Model v. 2.1 (available at: <http://science.nature.nps.gov/im/inventory/geology/GeologyGISDataModel.cfm>) for detailed data layer (feature class) and table specifications including attribute field parameters, definitions and domains, and implemented topology rules and relationship classes. For the KML/KMZ format all or only some of the data layers are available. The KMZ file also possesses on-line links to the GRI program and its products, and to this readme document, FAQ metadata (in .html format), and the GRI ancillary map information (.pdf) document pertaining to this dataset.

  1. How should this data set be cited?

    National Park Service (NPS) Geologic Resources Inventory (GRI) program, 20110929, Unpublished Digital Geologic Map of Glen Canyon National Recreation Area and Vicinity, Utah, Arizona (NPS, GRD, GRI, GLCA, GLCA digital map) adapted from Utah Geological Survey digital data and map by Willis and Ehler (2011), and a Utah Geological Survey Open-File Report map by Doelling and Willis (1999).

    Online Links:

  2. What geographic area does the data set cover?

    West_Bounding_Coordinate: -111.750725763791
    East_Bounding_Coordinate: -109.875677924693
    North_Bounding_Coordinate: 38.5000485896149
    South_Bounding_Coordinate: 36.7916286680445

  3. What does it look like?

    Not applicable
    No browse graphic provided

  4. Does the data set describe conditions during a particular time period?

    Calendar_Date: 29-Sep-2011
    Currentness_Reference: ground condition

  5. What is the general form of this data set?

    Geospatial_Data_Presentation_Form: map

  6. How does the data set represent geographic features?

    1. How are geographic features stored in the data set?

    2. What coordinate system is used to represent geographic features?

      Grid_Coordinate_System_Name: Universal Transverse Mercator
      Universal_Transverse_Mercator:
      UTM_Zone_Number: 12
      Transverse_Mercator:
      Scale_Factor_at_Central_Meridian: 0.999600
      Longitude_of_Central_Meridian: -111.0
      Latitude_of_Projection_Origin: 0.000000
      False_Easting: 500000.000000
      False_Northing: 0.000000

      Planar coordinates are encoded using coordinate pair
      Abscissae (x-coordinates) are specified to the nearest 0.000007
      Ordinates (y-coordinates) are specified to the nearest 0.000007
      Planar coordinates are specified in meters

      The horizontal datum used is North American Datum of 1983.
      The ellipsoid used is Geodetic Reference System 80.
      The semi-major axis of the ellipsoid used is 6378137.000000.
      The flattening of the ellipsoid used is 1/298.257222.

  7. How does the data set describe geographic features?

    Entity_and_Attribute_Overview:
    Refer to the NPS GRI Geology-GIS Geodatabase Data Model v. 2.1 (available at: <http://science.nature.nps.gov/im/inventory/geology/GeologyGISDataModel.cfm>) for detailed feature class and table attribute field parameters, definitions and domains, and implemented relationship classes, as well as for implemented feature class topology rules.
    Entity_and_Attribute_Detail_Citation:
    NPS GRI Geology-GIS Geodatabase Data Model v. 2.1. (available at: <http://science.nature.nps.gov/im/inventory/geology/GeologyGISDataModel.cfm>)

Who produced the data set?

  1. Who are the originators of the data set? (may include formal authors, digital compilers, and editors)

  2. Who also contributed to the data set?

    James R. Chappell, Heather I. Stanton, Derek Witt, Ron Karpilo, and Stephanie O'Meara (Colorado State University)

  3. To whom should users address questions about the data?

    Stephanie O'Meara
    Colorado State University
    Research Associate, Geologist/GIS Specialist/Data Manager
    1201 Oak Ridge Drive, Suite 200
    Fort Collins, Colorado 80525
    USA

    (970) 491-6655 (voice)
    (970) 225-3597 (FAX)
    stephanie.omeara@colostate.edu

    Hours_of_Service: 9:00 a.m. to 5:00 p.m. (MST), Monday - Friday

Why was the data set created?
The data are intended to assist NPS personnel in the protection and management of Glen Canyon National Recreation Area.

How was the data set created?
  1. From what previous works were the data drawn?

    UGS unpublished (source 1 of 2)
    Willis, G.C. and Ehler, J.B., 2011, Interim geologic map of Glen Canyon National Recreation Area and vicinity, San Juan, Kane, Garfield, Wayne and Grand Counties, Utah and Coconino County, Arizona: NA unpublished, Utah Geological Survey (UGS), Salt Lake City, Utah.

    Type_of_Source_Media: digital data
    Source_Scale_Denominator: 100000
    Source_Contribution:
    Features and attribution were derived from source digital data. Ancillary map text, including unit descriptions, and graphics, if present on the source map, were captured, formatted and added to the ancillary map PDF document. See the Process Step section for additional information.

    UGS Open-File Report 368 (source 2 of 2)
    Doelling, H.H. and Willis, G.C., 1999, Interim geologic map of the Escalante and parts of the Loa and Hite Crossing 30'x60' quadrangles, Garfield and Kane Counties, Utah: NA Open-File Report 368, Utah Geological Survey (UGS), Salt Lake City, Utah.

    Type_of_Source_Media: paper
    Source_Scale_Denominator: 100000
    Source_Contribution:
    Geologic features (fault bar and ball symbols) present on the source map were digitized using a .TIF image of the paper/map that was scanned at 300dpi and georeferenced in NAD83 UTM. The source map scan was also used to attribute features, as well as to check (QC) line quality, both positionally and spatially, and feature attribution. Ancillary source map text, including unit descriptions, and graphics, if present, were captured, formatted and added to the ancillary map PDF document. See the Process Step section for additional information.

  2. How were the data generated, processed, and modified?

    Date: 29-Sep-2011 (process 1 of 1)
    1.) GIS features were produced from source digital data or digitized from a source paper map. See the Source Information Contribution section(s) for specific source map details. GIS features converted from source digital data were imported into a GRI data model compliant geodatabase. 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>). GIS features captured from a source paper map were digitized from a TIF image of the map scanned at 300dpi and georeferenced in NAD83 UTM. 2.) Line quality of digitized features was checked against the source scan to ensure that GIS features were represented accurately, both positionally and spatially. Line quality of digital data was checked and if warranted edited to ensure good quality linework. 3.) Feature attribution was derived for all features using the source data attribution and the source printed/plotted map if available. 4.) Data Model topology rules were validated on all features and any topology errors corrected. 5.) Quality control (QC) consisted of checking features and their attribution against the source digital data, as well as against the source printed/plotted map if available. A GRI developed script (QC_Script) was run to check for GRI data model validation and feature-related consistency. 6.) The UNIT and MAP tables were populated and checked against the source (s). Relationship classes were also added and used to ensure attribution consistency between feature class and table attribution. 7.) Feature symbology was produced for all feature classes. An attempt was made to best match symbology to its source map, however, in some cases features symbology maybe slightly modified, primarily based on the limitations of the ArcGIS geology style. In some cases, however, symbology may have been modified to reconcile differences from multiple sources. 8.) GIS feature classes were exported from the geodatabase to shapefile (SHP) format, and GIS tables exported to DBASEIV (DBF) format. Layer (LYR) files were also exported. 9.) The ancillary map information 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 (HMXZ) template file. The HMXZ file was then compiled to produce the ancillary map PDF document. Any compilation errors were then checked and corrected and the document was reviewed for content, usability and grammatical errors. 10.) KML/KMZ files were produced with certain UNIT and MAP table fields appended and calculated for each feature class prior to export.

    Person who carried out this activity:

    James R. Chappell
    Colorado State University
    Research Associate, Geologist/GIS Specialist
    1201 Oak Ridge Drive, Suite 200
    Fort Collins, Colorado 80525-5589
    USA

    (970) 491-5147 (voice)
    (970) 225-3597 (FAX)
    jrchapp@lamar.colostate.edu

    Hours_of_Service: 9:00 a.m. to 5:00 p.m. (MST), Monday - Friday
    Data sources used in this process:
    • UGS unpublished, UGS Open-File Report 368

  3. What similar or related data should the user be aware of?

    National Park Service Geologic Resources Inventory (GRI) program, 20110929, Metadata for the Unpublished Digital Geologic Map of Glen Canyon National Recreation Area and Vicinity, Utah, Arizona (NPS, GRD, GRI, GLCA, GLCA digital map).

    Online Links:

How reliable are the data; what problems remain in the data set?
  1. How well have the observations been checked?

    Feature and table attribution was derived and checked with the source map(s). Attribution was checked (QCd) for errors. Users of this data are advised to FULLY and CAREFULLY READ the "DISTRIBUTION LIABILITY" section of this metadata before using the data.

  2. How accurate are the geographic locations?

    Data was produced from digital source data and digitized from a georeferenced source map TIF image(s) (300dpi). Users of this data are cautioned about the locational accuracy of features within this dataset. Based on the source map scale and United States National Map Accuracy Standards features are within (horizontally) 50.8 meters or 166.7 feet of their actual location as presented by this dataset. Users of this data should thus not assume the location of features is exactly where they portrayed are in Google Earth, ArcGIS or other software used to display this dataset. The PRECISION of any Shapefile (SHP) files is DOUBLE. The maximum root mean square (RMS) horizontal accuracy of the georeferenced image as measured in ArcMap is 11.7 meters. Coordinate tics on the georeferenced (registered and rectified) source map image(s) were checked against control points that had the exact specified coordinates of the tic. The direct distance between the image tic and its control point were measured. All measured distances were less than 50% of the required distance to meet National Map Accuracy Standards (1/50th of an inch for maps at 1:20,000 scale and smaller). Features were checked (QCd) after digitizing for positional accuracy errors using the georeferenced source map image.

  3. How accurate are the heights or depths?

    No vertical coordinates are present in this GRI digital dataset.

  4. Where are the gaps in the data? What is missing?

    All data is considered complete to the extent of the source map(s).

  5. How consistent are the relationships among the observations, including topology?

    GIS data in 9.3 personal geodatabase (.MDB), shapefile (.SHP) and DBASEIV (.DBF) table, and 2.2 KML/KMZ file formats.

How can someone get a copy of the data set?
Are there legal restrictions on access or use of the data?

Access_Constraints: None
Use_Constraints:
Not for use at scale greater than 1:100,000 (source map scale). Users of this data are cautioned about the locational accuracy of features within this dataset. Based on the source map scale and United States National Map Accuracy Standards features are within (horizontally) 50.8 meters or 166.7 feet feet of their actual location as presented by this dataset. Users of this data should thus not assume the location of features is exactly where they are portrayed in Google Earth, ArcGIS or other software used to display this dataset.

  1. Who distributes the data set? (Distributor 1 of 1)

    Stephanie O'Meara
    Colorado State University
    Research Associate, Geologist/GIS Specialist/Data Manager
    1201 Oak Ridge Drive, Suite 200
    Fort Collins, Colorado 80525
    USA

    (970) 491-6655 (voice)
    (970) 225-3597 (FAX)
    stephanie.omeara@colostate.edu

    Hours_of_Service: 8:00 a.m. to 4:00 p.m. (MST), Monday - Friday
    Contact_Instructions:
    GRI data are available at: <http://irma.nps.gov/App/Reference/Search>
  2. What's the catalog number I need to order this data set?

    GIS map data available in 9.3 personal geodatabase (.MDB) file format (in glcagdb.zip), shapefile (.SHP) and DBASEIV (.DBF) table file format (in glcashp.zip), and in 2.2 KML/KMZ format (in glcakml.zip)

  3. What legal disclaimers am I supposed to read?

    The National Park Service shall not be held liable for improper or incorrect use of the data described and/or contained herein. These data and related graphics are not legal documents and are not intended to be used as such.

    The information contained in these data is dynamic and may change over time. The data are not better than the original sources from which they were derived. It is the responsibility of the data user to use the data appropriately and consistent within the limitations of geospatial data in general and these data in particular. The related graphics are intended to aid the data user in acquiring relevant data; it is not appropriate to use the related graphics as data.

    The National Park Service gives no warranty, expressed or implied, as to the accuracy, reliability, or completeness of these data. It is strongly recommended that these data are directly acquired from an NPS server and not indirectly through other sources which may have changed the data in some way. Although these data have been processed successfully on a computer system at the National Park Service, no warranty, expressed or implied is made regarding the utility of the data on another system or for general scientific purposes, nor shall the act of distribution constitute any such warranty. This disclaimer applies to both to individual use of the data and aggregate use with other data.

  4. How can I download or order the data?

Who wrote the metadata?
Dates:
Last modified: 29-Sep-2011

Metadata author:
Stephanie O'Meara
Colorado State University
Research Associate, Geologist/GIS Specialist/Data Manager
1201 Oak Ridge Drive, Suite 200
Fort Collins, Colorado 80525-5589
USA

(970) 491-6655 (voice)
(970) 225-3597 (FAX)
stephanie.omeara@colostate.edu

Hours_of_Service: 9:00 a.m. to 5:00 p.m. (MST), Monday - Friday
Metadata standard:
FGDC Content Standards for Digital Geospatial Metadata (FGDC-STD-001-1998)

Metadata extensions used:

Generated by mp version 2.7.19 on Wed Aug 17 11:22:24 2016