Surficial Geology of Lower Comb Wash, San Juan County, Utah

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

Frequently anticipated questions:

What does this data set describe?

Title: Surficial Geology of Lower Comb Wash, San Juan County, Utah
Abstract:
This digital map database is compiled from new mapping by the author, represents the general distribution of surficial and bedrock geology in the mapped area. Together with the accompanying pamphlet, it provides current information on the surficial geology and stratigraphy of the area. The database delineate map units that are identified by age and lithology following the stratigraphic nomenclature of the U.S. Geological Survey. The scale of the source maps limits the spatial resolution of the database to 1:12,000 or smaller.
Supplemental_Information:
This report consists of a set of geologic map database files (ARC/INFO coverages) and supporting text and plot files. In addition, the report includes two sets of plot files (Post Script and PDF format) that will generate map sheets and pamphlets similar to a traditional USGS Open-File Report. These files are described in the explanatory pamphlets (cw_readme.txt, cw_readme.pdf, or cw_readme.doc).
  1. How might this data set be cited?
    Longpré, C. I., 2001, Surficial Geology of Lower Comb Wash, San Juan County, Utah: U.S. Geological Survey Open-File Report 01-424, U.S. Geological Survey, Tacoma, WA.

    Online Links:

  2. What geographic area does the data set cover?
    West_Bounding_Coordinate: -109.68329521
    East_Bounding_Coordinate: -109.63867555
    North_Bounding_Coordinate: 37.50108384
    South_Bounding_Coordinate: 37.26427193
  3. What does it look like?
    http://pubs.usgs.gov/of/2001/0424/pdf/cw_map.pdf (PDF)
    Printable map sheet, 724 kbytes.
  4. Does the data set describe conditions during a particular time period?
    Calendar_Date: 2001
    Currentness_Reference:
    publication date
  5. What is the general form of this data set?
    Geospatial_Data_Presentation_Form: geologic 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):
      • Entity point (285)
      • Complete chain (625)
      • GT-polygon composed of chains (267)
    2. What coordinate system is used to represent geographic features?
      Grid_Coordinate_System_Name: Universal Transverse Mercator
      Universal_Transverse_Mercator:
      UTM_Zone_Number: 12
      Planar coordinates are encoded using coordinate pair
      Abscissae (x-coordinates) are specified to the nearest 1
      Ordinates (y-coordinates) are specified to the nearest 1
      Planar coordinates are specified in meters
      The horizontal datum used is NAD27.
      The ellipsoid used is Clarke 1866 Semi_Major_Axis: 6378206.4.
      The flattening of the ellipsoid used is 1/294.98.
  7. How does the data set describe geographic features?
    CWN_POLY.PAT
    attribute table of cwn_poly (Source: ARC/INFO)
    PTYPE
    Geologic unit label
    ValueDefinition
    t1Terrace 1 deposits
    t2Terrace 2 deposits
    t3Terrace 3 deposits
    bctBig Cottonwood Terrace deposits
    mctMedium Cottonwood Terrace deposits
    taTamarisk terrace deposits
    CWS_POLY.PAT
    attribute table of cws_poly (Source: ARC/INFO)
    PTYPE
    Geologic unit label
    ValueDefinition
    t1Terrace 1 deposits
    t2Terrace 2 deposits
    t3Terrace 3 deposits
    bctBig Cottonwood Terrace deposits
    taTamarisk Terrace deposits
    afAlluvial fan deposits
    colColluvium
    mfpModern Floodplain
    stStock Tank
    PcmCutler Formation Cedar Mesa member
    TrcChinle Formation
    TrmMoenkopi Formation, undivided
    CWN_POLY.AAT
    attribute table of cwn_poly (Source: ARC/INFO)
    LTYPE
    Type of geologic or geographic feature denoted by a line in the database. (Source: author)
    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.
    terrace_scarpTerrace scarp with hatches pointing downslope. The scarp is observed or is closely constrained, so it is well located as described by Positional_Accuracy.
    prehistoric_roadLocation of a road of prehistoric origin. The location has been observed or is closely constrained, so it is well located as described in Positional_Accuracy.
    CWS_POLY.AAT
    attribute table of cws_poly (Source: ARC/INFO)
    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.
    CWN_ANNO.AAT
    attribute table of cwn_poly (Source: ARC/INFO)
    LTYPE
    Type of feature denoted by a line in the database.
    ValueDefinition
    leaderAnnotation leader.
    CWS_ANNO.AAT
    attribute table of cwn_poly (Source: ARC/INFO)
    LTYPE
    Type of feature denoted by a line in the database. (Source: author)
    ValueDefinition
    leaderAnnotation leader.
    CWN_DRAIN.AAT
    attribute table of cwn_poly (Source: ARC/INFO)
    LTYPE
    Type of geologic or geographic feature denoted by a line in the database. (Source: author)
    ValueDefinition
    ephemeral_streamThalweg of ephemeral stream. The thalweg has been observed or is closely constrained, so it is well located as described in Positional_Accuracy.
    perennial_streamThalweg of perennial stream. The thalweg has been observed or is closely constrained, so it is well located as described in Positional_Accuracy.
    CWS_DRAIN.AAT
    attribute table of cwn_poly (Source: ARC/INFO)
    LTYPE
    Type of geologic or geographic feature denoted by a line in the database.
    ValueDefinition
    ephemeral_streamThalweg of ephemeral stream. The thalweg has been observed or is closely constrained, so it is well located as described in Positional_Accuracy.
    perennial_streamThalweg of perennial stream. The thalweg has been observed or is closely constrained, so it is well located as described in Positional_Accuracy.
    CWN_XSECT.AAT
    attribute table of cwn_poly (Source: ARC/INFO)
    LTYPE
    Type of geologic or geographic feature denoted by a line in the database.
    ValueDefinition
    cross_sectionLocation and path of a geomorphic cross-section. The cross-section is well located as described in Positional_Accuracy.
    CWS_XSECT.AAT
    attribute table of cwn_poly (Source: ARC/INFO)
    LTYPE
    Type of geologic or geographic feature denoted by a line in the database.
    ValueDefinition
    cross_sectionLocation and path of a geomorphic cross-section. The cross-section is well located as described in Positional_Accuracy.
    Entity_and_Attribute_Overview:
    The databases described in this report were compiled in ARC/INFO, a commercial Geographic Information System by Environmental Systems Research Institute. Almost all the attributes in the various attribute tables of the coverages included in the report are set or calculated by ARC/INFO. The exceptions being <COVER>-ID, LTYPE and PTYPE. LTYPE and PTYPE are author added aspects of the coverages added to the PAT or AAT and are used to describe the type of line( LTYPE), area (PTYPE), or point. LTYPE is defined with WIDTH 35, OUTPUT 35, and TYPE C (character). PTYPE is defined with WIDTH 6, OUTPUT 6, and TYPE C. Coverage cwn_profile contains only points. There are no defined attributes for these coverages.
    Entity_and_Attribute_Detail_Citation: http://pubs.usgs.gov/of/2001/0424/pdf/cw_readme.pdf

Who produced the data set?

  1. Who are the originators of the data set? (may include formal authors, digital compilers, and editors)
    • Longpré, C. I.
  2. Who also contributed to the data set?
    Thank you to Jessica Wellmeyer for help compiling the digital database and Debra Block for her extensive review of the digital database.
    Thanks also to Carolyn Donlin for making this data available on the WWW.
  3. To whom should users address questions about the data?
    U.S. Geological Survey
    Attn: C.I. Longpré
    1201 Pacific Ave, Suite 600
    Tacoma, WA
    USA

    253-428-3600 x2624 (voice)
    clongpre@usgs.gov

Why was the data set created?

This geologic map is part of a cooperative project between the U.S. Geological Survey and Northern Arizona University. The map area includes lower Comb Wash in southeastern Utah on the Colorado Plateau. This part of the Colorado Plateau was not previously mapped in adequate geologic detail. The geologic information in this report may be useful to land management, range management, and flood control programs for all federal and state agencies, and private affairs.

How was the data set created?

  1. From what previous works were the data drawn?
  2. How were the data generated, processed, and modified?
    (process 1 of 2)
    The databases in this report were compiled in ARC/INFO version 7.1.2, a commercial Geographic Information System (Environmental Systems Research Institute, Redlands, CA). The files are in vector (coverage) format. Coverages are stored in uncompressed ARC export format. ARC/INFO export files with the .e00 extension can be converted into ARC/INFO coverages in ARC/INFO and can be read by other commercially available Geographic Information Systems. Stable-base maps were digitized at the USGS Flagstaff Field Center using an Altek Datatab Proline AC32 digitizer. A tic file was created in latitude and longitude and projected into the base map projection (Transverse Mercator) using a central meridian of -112.375. Tics are defined in the four extreme corners of the map are in the geologic coverages corresponding with quadrangle corners both in base maps and digital maps. The tic file was used to transform the digitized coverage into Universal Transverse Mercator projection. ARC/INFO generated an RMS (root mean square) report after transforming the original coverage from digitizer units into real world coordinates. Digitized lines were edited interactively by hand using the ARC module ARCEDIT and a series of macros and menus, polygon regions were attributed as necessary, and all artifacts visible at 1:12,000 were removed.
    Date: 11-May-2001 (process 2 of 2)
    Creation of original metadata record Person who carried out this activity:
    Longpré, Claire I.
    USGS-GEO-WRG-NGM
    1201 Pacific Ave, Suite 600
    Tacoma, WA
    USA

    (253) 428-3600 x2624 (voice)
    clongpre@usgs.gov
  3. What similar or related data should the user be aware of?

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

  1. How well have the observations been checked?
  2. How accurate are the geographic locations?
    Well-located data item are intended to have a positional accuracy within .24 mm at a 1:12,000 map scale, or 5 meters on the ground.
  3. How accurate are the heights or depths?
  4. Where are the gaps in the data? What is missing?
    This report is designed to describe completely the surficial and bedrock geology at a 1:12,000 scale. Geologic information only mappable at a larger scale has been omitted.
  5. How consistent are the relationships among the observations, including topology?
    Polygon and chain-node topology present

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:
Uses of this digital geologic map should not violate the spatial resolution of the map area (1:12,000) even though the digital data form removes the constraint of scale on a paper map. The accuracy inherent in map scale are also present in digital format. At a scale larger than 1:12,000, higher resolution data is not available and will not yield greater real detail.
  1. Who distributes the data set? (Distributor 1 of 1)
    Database Coordinator
    U.S. Geological Survey
    345 Middlefield Rd., M/S 975
    Menlo Park, CA
    USA

    Contact_Instructions:
    Please contact by mail or website. For digital packages on tape, sent a tape with your request. Please specify which data package you are requesting (Post Script plot files package CWEPS.ZIP, PDF plotfiles package CWPDF.ZIP, or ARC/INFO data base package CWDB.ZIP)
  2. What's the catalog number I need to order this data set? USGS Open-File report OF 01-424
  3. What legal disclaimers am I supposed to read?
    Any use of trade, product of firm names is for descriptive purposes only and does not imply endorsement by the U.S. Government. Although this publication has been subjected to rigorous review and is substantially complete, the USGS reserves the right to revise the data pursuant to further analysis and review. Furthermore, it is released on condition that neither the USGS nor the United States Government may be held liable for any damages resulting from its authorized or unauthorized use.
  4. How can I download or order the data?

Who wrote the metadata?

Dates:
Last modified: 13-Jun-2016
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/open-file/01-424/metadata.faq.html>
Generated by mp version 2.9.48 on Tue Jul 03 20:05:43 2018