USGS - science for a changing world

USGS Geoscience Data Catalog

Geologic map of the Rifle Falls quadrangle, Garfield County, Colorado

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

Frequently anticipated questions:


What does this data set describe?

Title:
Geologic map of the Rifle Falls quadrangle, Garfield County, Colorado
Abstract:
New 1:24,000-scale geologic map of the Rifle Falls 7.5' quadrangle, in support of the USGS Western Colorado I-70 Corridor Cooperative Geologic Mapping Project, provides new interpretations of the stratigraphy, structure, and geologic hazards in the area of the southwest flank of the White River uplift.
Bedrock strata include the Upper Cretaceous Iles Formation through Ordovician and Cambrian units. The Iles Formation includes the Cozzette Sandstone and Corcoran Sandstone Members, which are undivided. The Mancos Shale is divided into three members, an upper member, the Niobrara Member, and a lower member. The Lower Cretaceous Dakota Sandstone, the Upper Jurassic Morrison Formation, and the Entrada Sandstone are present. Below the Upper Jurassic Entrada Sandstone, the easternmost limit of the Lower Jurassic and Upper Triassic Glen Canyon Sandstone is recognized. Both the Upper Triassic Chinle Formation and the Lower Triassic(?) and Permian State Bridge Formation are present. The Pennsylvanian and Permian Maroon Formation is divided into two members, the Schoolhouse Member and a lower member. All the exposures of the Middle Pennsylvanian Eagle Evaporite intruded into the Middle Pennsylvanian Eagle Valley Formation, which includes locally mappable limestone beds. The Middle and Lower Pennsylvanian Belden Formation and the Lower Mississippian Leadville Limestone are present. The Upper Devonian Chaffee Group is divided into the Dyer Dolomite, which is broken into the Coffee Pot Member and the Broken Rib Member, and the Parting Formation. Ordovician through Cambrian units are undivided.
The southwest flank of the White River uplift is a late Laramide structure that is represented by the steeply southwest-dipping Grand Hogback, which is only present in the southwestern corner of the map area, and less steeply southwest-dipping older strata that flatten to nearly horizontal attitudes in the northern part of the map area. Between these two is a large-offset, mid-Tertiary(?) Rifle Falls normal fault, that dips southward placing Leadville Limestone adjacent to Eagle Valley and Maroon Formations. Diapiric Eagle Valley Evaporite intruded close to the fault on the down-thrown side and presumably was injected into older strata on the upthrown block creating a blister-like, steeply north-dipping sequence of Mississippian and older strata. Also, removal of evaporite by either flow or dissolution from under younger parts of the strata create structural benches, folds, and sink holes on either side of the normal fault. A prominent dipslope of the Morrison-Dakota-Mancos part of the section forms large slide blocks that form distinctly different styles of compressive deformation called the Elk Park fold and fault complex at different parts of the toe of the slide.
The major geologic hazard in the area consist of large landslides both associated with dip-slope slide blocks and the steep slopes of the Eagle Valley Formation and Belden Formation in the northern part of the map. Significant uranium and vanadium deposits were mined prior to 1980.
Supplemental_Information:
Map political location: Garfield County, Colorado
Compilation scale: 1:24,000
Geology mapped from 1992 to 1998
Compilation completed November 1998
  1. How might this data set be cited?
    Scott, Robert B., Shroba, Ralph R., and Egger, Anne E., 2001, Geologic map of the Rifle Falls quadrangle, Garfield County, Colorado: U.S. Geological Survey Miscellaneous Field Studies Map MF-2341, U.S. Geological Survey, Denver, Colorado.

    Online Links:

  2. What geographic area does the data set cover?
    West_Bounding_Coordinate: -107.75
    East_Bounding_Coordinate: -107.625
    North_Bounding_Coordinate: 39.75
    South_Bounding_Coordinate: 39.625
  3. What does it look like?
    http://pubs.usgs.gov/mf/2001/mf-2341/mf-2341.gif (GIF)
    Reduced-size image of the entire map sheet, 864x814 pixels, 252k bytes.
    http://pubs.usgs.gov/mf/2001/mf-2341/mf-2341.pdf (PDF)
    graphic representation of map layout
  4. Does the data set describe conditions during a particular time period?
    Calendar_Date: 2000Currentness_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 LAMBERT CONFORMAL CONIC.
      Projection parameters:
      Standard_Parallel: 39.75
      Standard_Parallel: 38.45
      Longitude_of_Central_Meridian: -105.5
      Latitude_of_Projection_Origin: 0.0
      False_Easting: 0.000
      False_Northing: 0.000
      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:
    The data are supplied in ARC/INFO export format.
    DATABASE FILES - ARC/INFO
    The database of the map consists of four coverages (root name = riflef), including corresponding INFO files:
    riflefpoly coverage: Contains all contact lines and labelpoints for each polygon. In the coverage's riflefpoly.aat INFO file the CODE item provides a numeric code that specifies the geologic identity and positional quality of each contact line (e.g., fault, approximately located), and the P1 and P2 items are relic cartographic parameters from the GSMCAD compilation program. The riflefpoly.aat CODE values are defined below. In the riflefpoly.pat INFO file the CODE and P2 items are relic cartographic parameters from the GSMCAD program, the P1 item provides a numeric code that specifies the polygon's map unit identity, the TEXT item indicates the map unit label for each polygon, and the SYMBOL item defines the polygon color as chosen from the color524.shd shadeset (included in bundled file archive). The P1 item defines the category of polygon as listed below and in the riflefunit.lut INFO file. The riflefpoly.pat P1 and TEXT items are listed below.
    riflefline coverage: Contains faults, fold axes, and other non-contact lines. Faults that are contacts also appear in the riflefpoly coverage. In the riflefline.aat INFO file the CODE item provides a numeric code that specifies the geologic identity and positional quality for each type of line, the P1 and P2 items are relic cartographic parameters from the GSMCAD program, and the TEXT item describes the geologic identity, positional quality, and, in some cases, additional aspects of each line. The riflefline.aat CODE and TEXT items are listed below.
    riflefpoint coverage: Contains points recording site-specific observations and measurements, such as strike and dip of bedding. In the riflefpoint.pat INFO file the CODE item provides a numeric code that specifies the type of point observation, the P1 and P2 items indicate the associated strike azimuth (or trend) and dip (or plunge), respectively, and the TEXT item describes the type of point observation. (In the case of bedding attiudes the P1 strike azimuths are always 90 deg. counterclockwise from the associated dip directions.) The riflefpoint.pat CODE and TEXT items are listed below.
    riflefdec coverage: Contains points used for cartographically decorating lines, such as "ball-and-bar" fault symbols, as well as a repeat of points in the riflefpoint coverage recording site-specific observations and measurements. Such point data provide additional qualitative information mainly for line features representing faults and folds, such as sense of fault displacement or fold type. In the INFO file riflefdec.pat the CODE item defines a numeric code for each type of point decoration and the P1 and P2 items indicate the orientation (or strike azimuth) and, where appropriate, dip (or plunge) value associated with each point symbol. The riflefdec.pat CODE items are listed below.
    Auxiliary files:
    color524.shd: This shadeset file defines the rgb values of colors assigned to polygons in the riflefpoly coverage (see SYMBOL item).
    riflef24k.pdf: A file for viewing and printing a graphics version of the map and accessory elements using Adobe Acrobat viewing software (version 4.0). Accessory map elements displayed in this graphics file are: (1) geologic cross section A-A', (2) geologic cross section B-B', (3) geologic cross section C-C', (4) correlation of map units diagram, (5) list of map unit symbols and names, and (6) explanation of map symbols.
    riflefexpl.pdf: A detailed text description of geologic map units and a brief discussion of deposits, structure, and geologic history of the map area.
    rifleftext coverage: Contains text points that define the position, rotation, and size of text to appear on the face of the map. Also includes arcs that draw leaders from the text to the appropriate polygons. This coverage is for cartographic purposes and does not include data critical to the database information. The P1 item defines rotation of the text, the P2 item the size of text, and the TEXT item the actual text.
    Gsmrelate INFO file: Contains the information that relates the riflefcode.lut and riflefunit.lut to the pat and aat INFO files of the coverages.
    riflefunit.lut INFO file: Contains the first two columns of the table below that lists the number (P1 item) assigned to each category of polygon and the corresponding text symbol used in the map explanation and on the face of the map.
    riflefcode.lut INFO file: Contains a text definition of the meaning of the number stored in the CODE item of every entity in all the coverages.
    riflefcolor.lu INFO file: Assigns a color from shadeset 524 for each category of polygon according to the P1 item.
    Gsmdraw.aml and gsmdraw.mnu files are included to constitute an ARC/INFO macro language program that will extract information from the riflef coverages to produce a graphics (.gra) file depicting the riflef geologic map. The graphics file can be viewed on screen or plotted with appropriate equipment.
    The aml program calls shadeset 524.shd, font font003, and lineset alcwrg.lin, so these are also included in the archive file. Other files can be substituted, but special geologic characters may not plot properly with a different font.
    Database root name: riflef
    P1  | GEOLOGIC MAP UNIT LABELS
    100 | af
    124 | Qac
    126 | Qfy
    127 | Qlo/Qfo
    131 | Qlo/Qp
    134 | QTg
    136 | Qc
    138 | Qsw
    141 | Qfp
    142 | Qls
    154 | Qd
    155 | Qg
    167 | Qlo/Qg
    169 | Qcm
    171 | shear zone
    180 | Qlo
    184 | Qtu
    413 | Kicc
    432 | Kmu
    437 | Kmn
    444 | Kml
    458 | Kd
    466 | Jm
    469 | Jeg
    472 | Je
    486 | @c
    498 | @Ps
    550 | &ee
    564 | Ml
    566 | Dc
    567 | Ddc
    569 | Ddb
    582 | P&ml
    584 | Pms
    612 | &b
    684 | Water
    685 | O\u
    686 | &ev
    687 | &evl
    689 | Dp
    Note: @ = Triassic; & = Pennsylvanian; \ = Cambrian
    
    DEFINITION OF CODES IN THE DATABASE COVERAGES (CODES AND TEXT LISTED IN THE .AAT AND .PAT FILES)
    CODE |   FEATURE
    001  | contact; certain
    003  | contact; inferred
    008  | landslide; scarp; contact
    009  | landslide on fault; contact certain
    010  | fault; contact; certain
    011  | fault; contact; concealed
    014  | fault; contact; inferred
    032  | fault; strike slip; concealed
    034  | fault contact; strike slip; inferred
    040  | thrust fault contact; certain
    041  | thrust fault; concealed
    044  | thrust fault contact; approximate location
    070  | fold axis; anticline; certain
    071  | fold axis; anticline; concealed
    074  | fold axis; syncline; certain
    075  | fold axis; syncline; concealed
    078  | line of section
    088  | intrusive dike; contact; certain
    089  |  'intrusive dike; contact; concealed
    093  | water boundary, certain
    097  | scratch boundary
    099  | map boundary
    201  | bedding attitude symbol
    203  | fault dip symbol
    204  | anticline symbol
    205  | syncline symbol
    206  | adit symbol
    207  | ball & bar symbol
    209  | left lateral symbol
    219  | over turned bed symbol
    242  | Question mark symbol to indicate uncertainty in a reach of a linear feature
    268  | diamond arrow symbol
    300  | Plots the symbol number read from P2
    362  | Flat bedding symbol
    500  | Unit labels text & tag
    501  | Hidden unit tags
    502  | Ordinary text
    503  | Ordinary text
    700  | Splined text
    

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?
    Cooperating agencies: Garfield County, U.S. Bureau of Land Management, U.S. Forest Service, Colorado Geological Survey
  3. To whom should users address questions about the data?
    Robert B. Scott
    U.S. Geological Survey
    MS 913, Box 25046 DFC
    Denver, CO

    303-236-1230 (voice)
    rbscott@usgs.gov

Why was the data set created?

This map was funded by the National Cooperative Geologic Mapping Program. The map is a product of the I-70 Urban Corridor Project. This corridor is experiencing rapid urban growth and geologic mapping is needed to aid in land development planning in order to address, avoid, or mitigate known and potential geologic hazards.

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: 2000 (process 4 of 9)
    Text map unit descriptors were added to the .AAT and .PAT database files for each coverage.
    Date: 2000 (process 5 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: 2000 (process 6 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: 2000 (process 7 of 9)
    The geospatial database files and metadata were quality checked for completeness and consistency.
    Date: 2000 (process 8 of 9)
    Final preparation of the geospatial database for distribution, and preparation of map-on-demand files and metadata.
    Date: 02-May-2013 (process 9 of 9)
    Creation of original metadata record Person who carried out this activity:
    Robert B. Scott
    U.S. Geological Survey
    U.S. Geological Survey
    Lakewood, CO

    303-236-1230 (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 1:24,000-scale color 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 and most digitized positions on the map are estimated to have about 20 m horizontal accuracy.
  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 400 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
    Central Publications Group
    Denver, CO

    1-888-ASK-USGS (voice)
  2. What's the catalog number I need to order this data set?
  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: 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/map-mf/2341/metadata.faq.html>

Accessibility FOIA Privacy Policies and Notices

USA.gov logo U.S. Department of the Interior | U.S. Geological Survey
URL: https://geo-nsdi.er.usgs.gov/metadata/map-mf/2341/metadata.faq.html
Page Contact Information: Peter Schweitzer
Page Last Modified: Monday, 14-Aug-2017 12:01:02 EDT

Generated by mp version 2.9.40 on Mon Aug 14 12:01:02 2017