Geologic Map of the Clifton Quadrangle, Mesa County, Colorado

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

Frequently anticipated questions:

What does this data set describe?

Title: Geologic Map of the Clifton Quadrangle, Mesa County, Colorado
Abstract:
1:24,000-scale geologic mapping in the Clifton 7.5' quadrangle, in support of the USGS Colorado River/I-70 Corridor Cooperative Geologic Mapping Project, provides interpretations of the Quaternary stratigraphy and geologic hazards in this area of the Grand Valley.
The Clifton 1:24,000 quadrangle is in Mesa County in western Colorado. Because the map area is dominated by various surficial deposits, the map depicts 16 different Quaternary units. Five prominent river terraces are present in the quadrangle containing gravels deposited by the Colorado River. The map area contains a large landslide deposit on the southern slopes of Mount Garfield. The landslide developed in the Mancos Shale and contains large blocks of the overlying Mesaverde Group. In addition, the landslide is a source of debris flows that have closed I-70 in the past. The major bedrock unit in the quadrangle is the Mancos Shale of Upper Cretaceous age.
The map is accompanied by text containing unit descriptions, and sections on geologic hazards (including landslides, piping, gullying, expansive soils, and flooding), and economic geology (including sand and gravel). A table indicates what map units are susceptible to a given hazard. Approximately 20 references are cited at the end of the report.
Supplemental_Information:
Map political location: Mesa County, Colorado
Compilation scale: 1:24,000
Geology mapped in 1996 to 1998.
Compilation completed March 1999.
DATASETS INCLUDED IN THIS GEOSPATIAL DATABASE: 
  clifpoly: geology polygons, contacts, and other linear features
  clifline: line of cross-section A-A'
  clifpnt: point features - bedding attitudes, drillholes
  1. How might this data set be cited?
    Carrara, Paul E., 2001, Geologic Map of the Clifton Quadrangle, Mesa County, Colorado: U.S. Geological Survey Miscellaneous Field Studies Map MF-2359, U.S. Geological Survey, Denver, Colorado.

    Online Links:

  2. What geographic area does the data set cover?
    West_Bounding_Coordinate: -108.50
    East_Bounding_Coordinate: -108.375
    North_Bounding_Coordinate: 39.125
    South_Bounding_Coordinate: 39.00
  3. What does it look like?
    http://pubs.usgs.gov/mf/2001/mf-2359/mf-2359.pdf (PDF)
    graphic representation of map layout
  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: 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.
    2. What coordinate system is used to represent geographic features?
      The map projection used is Polyconic.
      Projection parameters:
      Longitude_of_Central_Meridian: -108.4375
      Latitude_of_Projection_Origin: 39.0
      False_Easting: 0.0
      False_Northing: 0.0
      Planar coordinates are encoded using coordinate pair
      Abscissae (x-coordinates) are specified to the nearest 10
      Ordinates (y-coordinates) are specified to the nearest 10
      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: 
    COVERAGE NAME: clifpoly
USER-DEFINED ITEMS IN CLIFPOLY.PAT:
ATTRIBUTE NAME: CODE
DATABASE ITEM STRUCTURE: 3,3,I,0
DESCRIPTION: numeric entity identifier; used for printing
ITEM VALUES FOR 'CODE':
500
501
ATTRIBUTE NAME: P1
DATABASE ITEM STRUCTURE: 5,5,I,0
DESCRIPTION:  numeric entity identifier; used for printing
ITEM VALUES FOR 'P1':
Integer values in the range 100 - 586.
ATTRIBUTE NAME: P2
DATABASE ITEM STRUCTURE: 5,5,I,0
DESCRIPTION:  numeric entity identifier; used for printing
ITEM VALUES FOR 'P2':
20
80
ATTRIBUTE NAME: LABEL
DATABASE ITEM STRUCTURE: 6,6,C,0
DESCRIPTION: geologic unit text label
ITEM VALUES FOR 'LABEL':
(see table below)
ATTRIBUTE NAME: MODIFIER
DATABASE ITEM STRUCTURE: 10,10,C,0
DESCRIPTION: additional information for description, if any
ITEM VALUES FOR 'MODIFIER':
gravel pit
ATTRIBUTE NAME: SYMBOL
DATABASE ITEM STRUCTURE: 3,3,I,0
DESCRIPTION: shade symbol in color524.shd used to color polygons
ITEM VALUES FOR 'SYMBOL':
(see table below)
ATTRIBUTE NAME: DESC
DATABASE ITEM STRUCTURE: 80,80,C,0
DESCRIPTION: text description of geologic unit
ITEM VALUES FOR 'DESC':
(see table below)
RELATION OF ITEMS LABEL,MODIFIER, SYMBOL, and DESC:
LABEL   MODIFIER  SYMBOL   DESC
Kd                   454   Dakota Sandstone (Lower Cretaceous)
Km                   491   Mancos Shale (Upper Cretaceous)
Kmg                  432   Mount Garfield Formation and tongues of Mancos Shale (Upper Cretaceous)
Qa                     6   Alluvium of tributary channels (Holocene and late Pleistocene)
Qac                   25   Undivided alluvium and colluvium (Holocene and latest Pleistocene)
Qalc1                 11   Stream channel and floodplain deposits along the Colorado River (Holocene)
Qalc1   gravel pit    11   Stream channel and floodplain deposits along the Colorado River (Holocene)
Qalc2                 11   Alluvium deposited by the Colorado River (Holocene and latest Pleistocene)
Qalc2   gravel pit    11   Alluvium deposited by the Colorado River (Holocene and latest Pleistocene)
Qls                   39   Landslide deposits (Holocene and late Pleistocene)
Qp4                  451   Pediment deposit north of Sink Creek (early? Pleistocene)
Qpmv                 451   Pediment deposit east of Moulton Valley (late? Pleistocene)
Qpu                  451   Undifferentiated pediment deposits (early? Pleistocene)
Qt1                   22   Terrace alluvium (late Pleistocene)
Qt2                   46   Terrace alluvium (middle Pleistocene)
Qt2     gravel pit    46   Terrace alluvium (middle Pleistocene)
Qt3                  110   Terrace alluvium (early Pleistocene)
Qt3     gravel pit   110   Terrace alluvium (early Pleistocene)
Qt4                   62   Terrace alluvium (early Pleistocene)
Qt5                   29   Terrace alluvium (early Pleistocene)
Qtsc                  14   Terrace alluvium of Sink Creek (late to middle Pleistocene)
Qtu                   20   Undifferentiated terrace alluvium (middle to early Pleistocene)
af                     8   Artificial fill (latest Holocene)
(none)               327   water
USER-DEFINED ITEMS IN CLIFPOLY.AAT:
------------------------------------

ATTRIBUTE NAME: CODE
DATABASE ITEM STRUCTURE: 3,3,I,0
DESCRIPTION: numeric entity identifier; used for printing
ITEM VALUES FOR 'CODE':
1
4
92
99
ATTRIBUTE NAME: P1
DATABASE ITEM STRUCTURE: 3,3,I,0
DESCRIPTION: numeric entity identifier; used for printing
ITEM VALUES FOR 'P1':
1
ATTRIBUTE NAME: P2
DATABASE ITEM STRUCTURE: 3,3,I,0
DESCRIPTION: numeric entity identifier; used for printing
ITEM VALUES FOR 'P2':
0
2
ATTRIBUTE NAME: LINETYPE
DATABASE ITEM STRUCTURE: 80,80,C,0
DESCRIPTION: description of linear feature type
ITEM VALUES FOR 'LINETYPE':
(see table below)
ATTRIBUTE NAME: SYMBOL
DATABASE ITEM STRUCTURE: 3,3,I,0
DESCRIPTION: linesymbol in geol_sfo.lin used to draw line entities
ITEM VALUES FOR 'SYMBOL':
(see table below)
RELATIONSHIP OF ITEMS LINETYPE and SYMBOL:
LINETYPE                           SYMBOL
contact; certain                        1
gravel pit boundary                     1
contact; topographic escarpment       171
map boundary                          173
COVERAGE NAME: clifline
USER-DEFINED ITEMS IN CLIFLINE.AAT:
ATTRIBUTE NAME: CODE
DATABASE ITEM STRUCTURE: 3,3,I,0
DESCRIPTION: numeric entity identifier; used for printing
ITEM VALUES FOR 'CODE':
98
ATTRIBUTE NAME: P1
DATABASE ITEM STRUCTURE: 3,3,I,0
DESCRIPTION: numeric entity identifier; used for printing
ITEM VALUES FOR 'P1':
1
ATTRIBUTE NAME: P2
DATABASE ITEM STRUCTURE: 3,3,I,0
DESCRIPTION: numeric entity identifier; used for printing
ITEM VALUES FOR 'P2':
0
ATTRIBUTE NAME: LINETYPE
DATABASE ITEM STRUCTURE: 80,80,C,0
DESCRIPTION: description of linear feature type
ITEM VALUES FOR 'LINETYPE':
line of cross-section A-A prime
ATTRIBUTE NAME: SYMBOL
DATABASE ITEM STRUCTURE: 3,3,I,0
DESCRIPTION: linesymbol in geol_sfo.lin used to draw line entities
ITEM VALUES FOR 'SYMBOL':
227
COVERAGE NAME: clifpnt
USER-DEFINED ITEMS IN CLIFPNT.PAT:
ATTRIBUTE NAME: STRIKE
DATABASE ITEM STRUCTURE: 7,7,I,0
DESCRIPTION: compass orientation of feature, in degrees
ITEM VALUES FOR 'STRIKE':
integer values in the range 0 - 360
ATTRIBUTE NAME: DIP
DATABASE ITEM STRUCTURE: 3,3,I,0
DESCRIPTION: inclination from horizontal of feature, in degrees
ITEM VALUES FOR 'DIP':
integer values in the range 0 -90
ATTRIBUTE NAME: DESC
DATABASE ITEM STRUCTURE: 80,80,C,0
DESCRIPTION: text description of feature type
ITEM VALUES FOR 'DESC':
drillhole, dry
strike and dip of inclined beds
ATTRIBUTE NAME: SYMBOL
DATABASE ITEM STRUCTURE: 3,3,I,0
DESCRIPTION: markersymbol used to draw feature
ITEM VALUES FOR 'SYMBOL':
2
101
ATTRIBUTE NAME: SYMSET
DATABASE ITEM STRUCTURE: 20,20,C,0
DESCRIPTION: ArcInfo markerset associated with the SYMBOL item above
ITEM VALUES FOR 'SYMSET':
geoscamp1.mrk
oilgas.mrk
    Entity_and_Attribute_Detail_Citation: none

Who produced the data set?

  1. Who are the originators of the data set? (may include formal authors, digital compilers, and editors)
    • Paul E. Carrara
  2. Who also contributed to the data set?
  3. To whom should users address questions about the data?
    Paul E. Carrara
    U.S. Geological Survey
    MS 913, Box 25046 DFC
    Denver, CO

    303-236-1287 (voice)
    pcarrara@usgs.gov

Why was the data set created?

To update earlier small-scale geologic mapping, and to provide sufficient geologic information for land-use decisions.

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: 1999 (process 1 of 9)
    Polygons, lines, and points representing geologic features and data points were digitized from scale-stable compilation materials using the GSMCAD public domain program (USGS Open-File Report 96-007).
    Date: 1999 (process 2 of 9)
    The map data were exported to ARC/INFO using the GSMCAD export function to create ARC generate ASCII files. The ASCII files were then imported into ArcInfo using the GENERATE routine, and polygon topology built.
    Date: 1999 (process 3 of 9)
    The gsmdraw.aml program was used in ARC to produce a graphics file of the colored map. In addition an explanation sheet was produced that includes a correlation of map units diagram, a list of map unit names and corresponding symbols, and an explanation of graphical map symbols.
    Date: 1999 (process 4 of 9)
    Draft check plots of the geologic map and explanation were created and submitted for peer review. Geologists reviewed the plots for conformity with U.S. Geological Survey editorial standards and stratigraphic nomenclature. Revisions were made to the geospatial database as needed.
    Date: 2001 (process 5 of 9)
    Text map unit descriptors were added to the .AAT and .PAT database files for each coverage.
    Date: 2001 (process 6 of 9)
    The geospatial database files and metadata were quality checked for completeness and consistency.
    Date: 2001 (process 7 of 9)
    The database files, metadata, and check plots were edited by the USGS Central Publications Group, and revisions made to the geospatial database as needed.
    Date: 2001 (process 8 of 9)
    Final preparation of the geospatial database for distribution, and preparation of map-on-demand files and metadata.
    Date: 11-Jan-2001 (process 9 of 9)
    Creation of original metadata record Person who carried out this activity:
    Paul E. Carrara
    U.S. Geological Survey
    U.S. Geological Survey
    Lakewood, CO

    303-236-1287 (voice)
  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?
    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. To check attribute accuracy, a color check plot was visually compared to the geologist's original compilation. Discrepancies between the digital geospatial dataset and the original analog compilation were corrected as needed. Machine- created listings of unique attribute values were used to identify spelling errors or other inconsistencies, and corrections were made as needed. This map has been thoroughly reviewed for conformity with U.S. Geological Survey editorial standards and stratigraphic nomenclature.
  2. How accurate are the geographic locations?
    Lines were primarily positioned by photointerpretation of aerial photographs using a PG-2 photogrammetric plotter that rectified the position and transferred it to a basemap. Lines were digitized from the basemap using a digitizer tablet with resolution of 0.001 inch. Additional lines and point observations were added in the field using positions determined by a PLGR-95 GPS unit with accuracy of about 10 meters. Most positions on the map are estimated to be accurate closer than 30 m horizontally.
  3. How accurate are the heights or depths?
  4. Where are the gaps in the data? What is missing?
    Data are complete: no features that could be accurately represented at the compilation scale of 1:24,000 were eliminated or generalized. The smallest area represented is approximately 570 square meters. All geospatial database elements are attributed.
  5. How consistent are the relationships among the observations, including topology?
    Map elements were visually checked for overshoots, undershoots, duplicate features, polygon closure, and other errors by the author and by the GIS technician(s) that created the digital database. Automated (ArcInfo) routines were also used to check the databases for polygon label errors, line or point attribution errors, sliver polygons, dangling arcs, intersection errors, and projection information. Check plots of the map were reviewed by at least two other geologists for consistency with basic geologic principles and general conformity to USGS mapping standards.

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:
none. Acknowledgment of the U.S. Geological Survey would be appreciated in products derived from these data.
  1. Who distributes the data set? (Distributor 1 of 1)
    U.S.Geological Survey
    USGS Information Services
    Denver, CO
    United States

    1-888-ASK-USGS (voice)
  2. What's the catalog number I need to order this data set? MF-2359
  3. What legal disclaimers am I supposed to read?
    Although this digital spatial data has been subjected to rigorous review and is substantially complete, it is released on the 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: 05-Feb-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/map-mf/2359/metadata.faq.html>
Generated by mp version 2.9.48 on Tue Jul 03 20:05:06 2018