Surficial Geologic Map of The Loop and Druid Arch Quadrangles, Canyonlands National Park, Utah

Metadata also available as - [Outline] - [Parseable text] - [XML]

Frequently anticipated questions:


What does this data set describe?

Title:
Surficial Geologic Map of The Loop and Druid Arch Quadrangles, Canyonlands National Park, Utah
Abstract:
This geologic map is a product of a cooperative project between the U.S. Geological Survey and the U.S. National Park Service to provide geologic information about this part of Canyonlands National Park, Utah. This digital map database contains bedrock data from previously published data that has been modified by the author. New mapping of the surficial deposits represents the general distribution of surficial deposits of the Druid Arch and The Loop 7.5-minute quadrangles.
Supplemental_Information:
Use of multiple deposit labels for a polygon. Surficial geologic units may exist as thin (< 2m) veneers over older units. In areas where this relationship is common the unit designators are shown on the map as being separated by a slash (/). The younger, or overlying, unit is indicated first. Thus, Qed/Qes indicates an area where a veneer of sand dune deposits overlies sand sheet deposits. Not all composite units are shown on the map or in the database.
  1. How might this data set be cited?
    Billingsley, George H., Block, Debra L., and Felger, Tracey J., 2002, Surficial Geologic Map of The Loop and Druid Arch Quadrangles, Canyonlands National Park, Utah: U.S. Geological Survey Miscellaneous Field Studies Map MF-2411, U.S. Geological Survey, Flagstaff, AZ.

    Online Links:

  2. What geographic area does the data set cover?
    West_Bounding_Coordinate: -109.87882988
    East_Bounding_Coordinate: -109.74573
    North_Bounding_Coordinate: 38.25126408
    South_Bounding_Coordinate: 37.99873863
  3. What does it look like?
    http://pubs.usgs.gov/mf/2002/2411/images/mf2411.jpg (JPEG)
    Reduced-size image of the entire map sheet, 366x580 pixels, 75k bytes.
    http://pubs.usgs.gov/mf/2002/2411/mf2411.pdf (PDF)
    Printable representation of the map, 10.4 megabytes
  4. Does the data set describe conditions during a particular time period?
    Calendar_Date: 2002
    Currentness_Reference:
    Publication date
  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?
      This is a Vector data set. It contains the following vector data types (SDTS terminology):
      • Point (6001)
      • String (12859)
      • GT-polygon composed of chains (6002)
    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.9996
      Longitude_of_Central_Meridian: -111
      Latitude_of_Projection_Origin: 0.0
      False_Easting: 500000
      False_Northing: 0.0
      Planar coordinates are encoded using coordinate pair
      Abscissae (x-coordinates) are specified to the nearest 0.8448421359062
      Ordinates (y-coordinates) are specified to the nearest 0.8448421359062
      Planar coordinates are specified in Meters
      The horizontal datum used is North American Datum of 1927.
      The ellipsoid used is Clarke 1866.
      The semi-major axis of the ellipsoid used is 6378206.4.
      The flattening of the ellipsoid used is 1/294.98.
  7. How does the data set describe geographic features?
    Entity_and_Attribute_Overview:
    The digital database for the Surficial geologic map of The Loop and Druid Arch quadrangles, Canyonlands National Park, Utah includes three geospatial datasets as ARC/INFO coverages: cany_poly (geology), cany_point (sinkholes), and cany_anno (annotation). Geospatial entities in ARC/INFO coverages have the following software-defined attributes: <cover>.pat contains AREA, PERIMETER, COVER#, and COVER-ID; <cover>.aat contains FNODE#, TNODE#, LPOLY#, RPOLY#, LENGTH, COVER#, and COVER-ID. User-defined attributes are described in detail below.
    (1) The coverage cany_poly includes the following feature attribute tables: (a) a polygon feature attribute table (cany_poly.pat) that describes the geospatial distribution of geologic units represented in the Postscript(.eps) and Portable Document Format (.pdf) plotfiles of the map; (b) an arc feature attribute table (cany_poly.aat) that describes the contacts and linear features that bound rock-unit polygons.
    (2) The coverage cany_point includes a point feature attribute table (control.pat) that describes the geospatial distribution of sinkholes.
    (3) The coverage cany_anno includes two annotation feature attribute tables: (a)(cany_anno.tatunit) containing unit labels derived from the coded item PTYPE in cany_poly and (b)(cany_anno.tatstructure) containing fault separation values. An arc feature attribute table (cany_anno.aat) contains leaders from the unit annotation to the related polygon.
    Entity_and_Attribute_Detail_Citation:
    CANY_POLY.PAT
    Polygon attribute table of coverage
    PTYPE
    Geologic map unit label. Plain text is substituted for conventional geologic age symbols (PP for Pennsylvanian) shown on map
    ValueDefinition
    PPeElephant Canyon Formation (Upper Pennsylvanian)
    PPhHonaker Trail Formation (Middle and Upper Pennsylvanian)
    PcCedar Mesa Sandstone (Permian)
    PcuCutler Formation/Cedar Mesa Sandstone, undifferentiated (Permian)
    PoOrgan Rock Shale
    QaeAlluvium and sand sheet deposits (Holocene and Pleistocene?)
    QafArtificial fill and quarries (Holocene)
    QalAlluvial deposits (Holocene and Pleistocene?)
    QedSand dune deposits (Holocene)
    QesSand sheet deposits (Holocene)
    Qf1Young alluvial fan deposits (Holocene)
    Qf2Young intermediate alluvial fan deposits (Holocene)
    QfpFloodplain deposits (Holocene)
    QpPonded deposits (Holocene)
    QrColorado River terrace deposits (Holocene)
    QrfRock fall debris (Holocene)
    QsStream-channel alluvium (Holocene)
    Qt1Young alluvial terrace deposits (Holocene)
    Qt2Intermediate alluvial terrace deposits (Holocene and Pleistocene?)
    Qt3Old alluvial terrace deposits (Pleistocene)
    waterwater
    PTYPE2
    Geologic map unit label. Underlying unit, with thin veneer of PTYPE on top.
    PTYPE3
    Geologic map unit label. Underlying unit, with thin veneer of PTYPE and PTYPE2 on top.
    PTYPE4
    Geologic map unit label. Composite unit, indicated with slashes
    CANY_POLY.AAT
    Arc attribute table of coverage
    LTYPE
    Type of geologic or geographic feature denoted by a line in the database.
    ValueDefinition
    contact_certainBoundary between two mapped units that retains the original depositional or intrusive relationship. The contact has been observed or is closely constrained, so it is well located as described in Positional_Accuracy.
    fault_certainStructural boundary between mapped units or structural discontinuity within a mapped unit that has experienced relative offset between the rock bodies on either side of the fault. The fault has been observed or is closely constrained, so it is well located as described in Positional_Accuracy.
    fault_concealedStructural boundary between mapped units or structural discontinuity within a mapped unit that has experienced relative offset between the rock bodies on either side of the fault. The fault is obscured by overlying mapped units, so it is not well located as described in Positional_Accuracy, but the location is constrained to be within about 95 meters on the ground.
    facies_changeThe lateral and vertical transition zone in the lithologic characteristics of contemporaneous deposits.
    map_boundaryEdge of the mapped area. Used primarily to bound polygons at the edge of the map database.
    PTTYPE
    Arcmarker point type
    ValueDefinition
    fault_ball_fillArcmarker attached to an arc describing the nature of displacement along a fault. Side of arc with bar and ball is the side with downthrown displacement.
    xxPlaceholder - no arcmarker is drawn on arc.
    CANY_POINT.PAT
    Point attribute table of coverage
    PTTYPE
    Point type.
    ValueDefinition
    sinkholeObserved location of an enclosed depression or cave.

Who produced the data set?

  1. Who are the originators of the data set? (may include formal authors, digital compilers, and editors)
    • George H. Billingsley
    • Debra L. Block
    • Tracey J. Felger
  2. Who also contributed to the data set?
    This database was prepared by George Billingsley, Debra Block, and Tracey Felger. Technical review was provided by Harland Goldstein and Fred Peterson. Digital review was provided by Scott Graham.
  3. To whom should users address questions about the data?
    George H. Billingsley
    U.S. Geological Survey
    Geologist
    2255 N. Gemini Dr.
    Flagstaff, AZ
    USA

    1-928-556-7198 (voice)
    1-928-556-7169 (FAX)
    gbillingsley@usgs.gov

Why was the data set created?

The geologic data presented is intended to provide additional information to park resource managers of Canyonlands National Park to help better understand and implement range management practices, biological studies, archaeological programs, and visitor interpretive information systems.

How was the data set created?

  1. From what previous works were the data drawn?
  2. How were the data generated, processed, and modified?
    Date: 2001 (process 1 of 3)
    A tic file was created in latitude/longitude coordinates and projected into the base map projection (UTM). The geology was digitized on screen at a consistent scale of 1:4,000 over DOQs in ArcView 3.2. The shapefile was converted to a coverage and final editing and attributing was done in ARC/INFO 8.0 using custom pull-down and form menus.
    Date: 21-Feb-2002 (process 2 of 3)
    First draft of metadata created by dblock using FGDCMETA.AML ver. 1.2 05/14/98 on ARC/INFO data set c:\arcwork\canyonlands\cany\cany_poly
    Date: 24-Jul-2007 (process 3 of 3)
    Creation of original metadata record Person who carried out this activity:
    U.S. Geological Survey
    Attn: Debra Block
    Geologist
    2255 N. Gemini Dr.
    Flagstaff, AZ
    USA

    1-928-556-7138 (voice)
    1-928-556-7169 (FAX)
    dblock@usgs.gov
  3. What similar or related data should the user be aware of?
    Huntoon, P.W., Billingsley, G.H., and Breed, W.J., 1982, Geologic map of Canyonlands National Park and vicinity: Canyonlands Natural History Association, Moab, Utah.


How reliable are the data; what problems remain in the data set?

  1. How well have the observations been checked?
    Data were entered and checked by the geologist that made the field observations. The attributes of this geospatial data set consist of text identifiers and numeric codes that indicate the identity of the geologic unit or type of geologic feature, and determine how each feature is colored or symbolized. Software generated lists of unique attribute values were used to identify spelling errors or other inconsistencies, and corrections were made as needed.
  2. How accurate are the geographic locations?
    Well-located data are intended to have a positional accuracy within 12 meters on the ground at a 1:24,000 map scale.
  3. How accurate are the heights or depths?
  4. Where are the gaps in the data? What is missing?
    The geologic map and digital database of The Loop and Druid Arch 7.5-minute qudrangles contain new data that have been subjected to rigorous review and are a substantially complete representation of the current state of knowledge concerning the surficial and bedrock geology of the area. All geospatial database elements are attributed.
  5. How consistent are the relationships among the observations, including topology?
    Polygon and chain-node topology present. Polygons internal to the map boundary are completely enclosed by line segments which are themselves a set of sequentially numbered coordinate pairs. Point data are represented by coordinate pairs. The neatline was mathematically generated from latitude and longitude values.

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:
Spatial Resolution. Use of this digital geologic map should not violate the spatial resolution of the data. This geologic map and database was developed using digital orthophotograph quadrangles (DOQs)as a base. DOQs have a pixel resolution of 1 or 2 m and are accurate to a scale of 1:24,000 (1 in = 2,000 ft). Any enlargement beyond 1:24,000 exceeds the spatial resolution of the geologic data and should not be used in lieu of a more detailed site-specific geologic evaluation. Similarly, the digital topographic base map is derived from the U.S. Geological Survey, 1:24,000- scale Druid Arch and The Loop 7.5 minute quadrangles; any enlargement beyond 1:24,000 exceeds the spatial resolution of the topographic data. Plotting or viewing of the data at scales larger than 1:24,000 will not yield greater real detail, although it may reveal fine-scale irregularities below the intended resolution of the database.
  1. Who distributes the data set? (Distributor 1 of 1)
    U.S. Geological Survey Information Services
    Box 25286 Denver Federal Center
    Denver, CO
    USA

    1-888-ASK-USGS (voice)
    ask@usgs.gov
  2. What's the catalog number I need to order this data set?
  3. What legal disclaimers am I supposed to read?
    The U.S. Geological Survey (USGS) provides these geographic data "as is." The USGS makes no guarantee or warranty concerning the accuracy of information contained in the Geographic: data. The USGS further makes no warranties, either expressed or implied as to any other matter whatsoever, including, without limitation, the condition of the product, or its fitness for any particular purpose. The burden for determining fitness for use lies entirely with the user. Although these data have been processed successfully on computers at the USGS, no warranty, expressed or implied, is made by the USGS regarding the use of these data on any other system, nor does the fact of distribution constitute or imply any such warranty.
    In no event shall the USGS have any liability whatsoever for payment of any consequential, incidental, indirect, special, or tort damages of any kind, including, but not limited to, any loss of profits arising out of use of or reliance on the Geographic: data or arising out of delivery, installation, operation, or support by USGS.
  4. How can I download or order the data?

Who wrote the metadata?

Dates:
Last modified: 13-Jun-2016
Last Reviewed: 07-May-2002
Metadata author:
Peter N Schweitzer
USGS Midwest Area
Collection manager, USGS Geoscience Data Clearinghouse, http://geo-nsdi.er.usgs.gov/
Mail Stop 954
12201 Sunrise Valley Dr
Reston, VA
USA

703-648-6533 (voice)
703-648-6252 (FAX)
pschweitzer@usgs.gov
Metadata standard:
Content Standard for Digital Geospatial Metadata (FGDC-STD-001-1998)

This page is <https://geo-nsdi.er.usgs.gov/metadata/map-mf/2411/metadata.faq.html>
Generated by mp version 2.9.48 on Tue Jul 03 20:05:19 2018