A spatial database of bedding attitudes to accompany Geologic Map of the Boulder--Fort Collins--Greeley area, Colorado, by Roger B. Colton

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

Frequently anticipated questions:

What does this data set describe?

Title:
A spatial database of bedding attitudes to accompany Geologic Map of the Boulder--Fort Collins--Greeley area, Colorado, by Roger B. Colton
Abstract:
This digital map shows bedding attitude data displayed over the geographic extent of rock stratigraphic units (formations) as compiled by Colton in 1976 (U.S.Geological Survey Map I-855-G) under the Front Range Urban Corridor Geology Program. Colton used his own mapping and published geologic maps having varied map unit schemes to compile one map with a uniform classification of geologic units. The resulting published color paper map was intended for planning for use of land in the Front Range Urban Corridor. In 1997-1999, under the USGS Front Range Infrastructure Resources Project, Colton's map was digitized to provide data at 1:100,000 scale to address urban growth issues(see cross-reference). In general, the west part of the map shows a variety of Precambrian igneous and metamorphic rocks, major faults and brecciated zones along an eastern strip (5-20 km wide) of the Front Range. The eastern and central part of the map (Colorado Piedmont) depicts a mantle of Quaternary unconsolidated deposits and interspersed Cretaceous or Tertiary-Cretaceous sedimentary rock outcrops. The Quaternary mantle is comprised of eolian deposits (quartz sand and silt), alluvium (gravel, sand, and silt of variable composition), colluvium, and few landslides. At the mountain front, north-trending, dipping Paleozoic and Mesozoic sandstone and shale formations (and sparse limestone) form hogbacks, intervening valleys, and in range-front folds, anticlines, and fault blocks. Localized dikes and sills of Tertiary rhyodacite and basalt intrude rocks near the range front, mostly in the Boulder area.
Supplemental_Information:
Coverages included in this geospatial database: 
bouldip coverage:  bedding attitudes
boulcnty coverage: county boundaries
boulhwy coverage:  major highways and arterials
bouldhyp coverage: hypsography
boulplss coverage: township and range lines
geoscamp2.mrk:     This markerset file defines the geologic markers in the geologically themed coverages.
  1. How might this data set be cited?
    Brandt, Theodore R., Moore, David W., and Murray, Kyle E., 2003, A spatial database of bedding attitudes to accompany Geologic Map of the Boulder--Fort Collins--Greeley area, Colorado, by Roger B. Colton: U.S. Geological Survey Open-File Report 03-024, United States Geological Survey, Denver, Colorado, U.S.A..

    Online Links:

  2. What geographic area does the data set cover?
    West_Bounding_Coordinate: -105.375
    East_Bounding_Coordinate: -104.625
    North_Bounding_Coordinate: 40.625
    South_Bounding_Coordinate: 40.0
  3. What does it look like?
    http://pubs.usgs.gov/of/2003/ofr-03-024/OFR-03-024-thb.gif (GIF)
    Reduced-size image of the entire map sheet, 300x222 pixels, 20k bytes
    http://pubs.usgs.gov/of/2003/ofr-03-024/OFR-03-024map.pdf (PDF)
    Printable representation of map layout, 8.1 megabytes
  4. Does the data set describe conditions during a particular time period?
    Calendar_Date: 2003
    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?
      Grid_Coordinate_System_Name: Universal Transverse Mercator
      Universal_Transverse_Mercator:
      UTM_Zone_Number: 13
      Transverse_Mercator:
      Scale_Factor_at_Central_Meridian: 0.9996
      Longitude_of_Central_Meridian: -105
      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 2.5
      Ordinates (y-coordinates) are specified to the nearest 2.5
      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 is supplied in ARC/INFO export format.
    DATABASE STRUCTURE - ARC/INFO ====================================
    This GIS database includes related look-up tables, which store detailed attribute information. This database structure is more fully described in USGS OFR 99-438. The GIS database structure used in the database includes symbol items in coverage point (PAT) attribute tables for user convenience. Arc/Info relates for each coverage are saved in a file named <covername>.rel. Use the RELATE command with the restore argument at the arc prompt to make the relates active. Alternatively, in Arctools, use the Relate environment: open dialog in the Manage - Relates flyout menu under the Arctools menu to make the relates active.
    bouldip coverage: Contains points recording site-specific observations and measurements, such as strike and dip of bedding. In the bouldip.pat INFO file the PTTYPE item lists the type of point symbol, e.g., strike dip and of inclined bedding. The SYMBOL item lists the marker symbol used by ArcInfo to identify the type of structural map symbol(Symbol numbers refer to the geoscamp2.mrk markerset). The STRIKE item contains the strike of bedding. Strike is an azimuthal angle (measured in degrees from 0 to 360 in a clockwise direction from North). The DIP item contains the dip of bedding. This value is an angle measured (in degrees 0 to 90) down from the horizontal; thus a horizontal dip is 0 degrees and a vertical dip is 90 degrees. The SOURCE item lists the numeric code used to identify the data source. The DISPLAY item is coded 1 when a point is displayed on the map layout, 2 when it is not. In this database, all points are displayed.
    In the coverage's bouldip.ref INFO file the SOURCE item lists the numeric code used to identify the data source. The scale item lists the scale of the source map. (This value is the denominator of the proportional fraction that identifies the scale of the map that was digitized or scanned to produce the digital map.) The AUTHORS item lists the author(s) or compiler(s) of source map entered as last name, first name or initial, and middle initial. The YEAR item lists the source (map) publication date. The REFERENCE item lists the remainder of the reference in USGS reference format.
    boulcnty coverage: Contains lines representing county boundaries derived from Colorado Department of Local Affairs, Colorado Office of Emergency Management data.
    In the coverage's boulcnty.ref INFO file the SOURCE item lists the numeric code used to identify the data source. The scale item lists the scale of the source map. (This value is the denominator of the proportional fraction that identifies the scale of the map that was digitized or scanned to produce the digital map.) The AUTHORS item lists the author(s) or compiler(s) of source map entered as last name, first name or initial, and middle initial. The YEAR item lists the source (map) publication date. The REFERENCE item lists the remainder of the reference in USGS reference format.
    boulhwy coverage: Contains lines representing highways and major arterials. In the boulhwy.aat INFO file the FEATURID item contains a unique line identifier assigned by the Federal Highway Administration. The DESCRIPT item provides the name or identification for the link (i.e. BASELINE RD). The DSOURCE item provides the original source of the coordinate information (i.e. S=State Supplied Digital Data, U=USGS Digital Line Graphs, T=US Census TIGER/Line files, M=Digitized from State supplied maps, H=Military Supplied data, all other values indicate Unknown). The STFIPS item indicates the two character State FIPS Code (FIPS Pub 6-4). The CTFIPS item indicates the three digit County FIPS code (FIPS Pub 6-4). The SIGN1 item indicates the Primary Sign Route (i.e. I-25). The SIGN2 item indicates the Alternate Sign Route. The MILES item indicates an accurate measurement in miles for the link chain. The KM item indicates an accurate measurement in kilometers for the link chain. The FACTYPE item describes the permissible flow of traffic over the link (1=One-way flow, 2=Bi-directional flow). The LANES item indicates the number of lanes in both directions.
    In the coverage's boulhwy.ref INFO file the SOURCE item lists the numeric code used to identify the data source. The scale item lists the scale of the source map. (This value is the denominator of the proportional fraction that identifies the scale of the map that was digitized or scanned to produce the digital map.) The AUTHORS item lists the author(s) or compiler(s) of source map entered as last name, first name or initial, and middle initial. The YEAR item lists the source (map) publication date. The REFERENCE item lists the remainder of the reference in USGS reference format.
    bouldhyp coverage: Contains lines representing hypsographic contours derived from USGS Digital Line Graph data. In the bouldhyp.aat INFO file the ELEV item contains the contour elevation in meters.
    In the coverage's bouldhyp.ref INFO file the SOURCE item lists the numeric code used to identify the data source. The scale item lists the scale of the source map. (This value is the denominator of the proportional fraction that identifies the scale of the map that was digitized or scanned to produce the digital map.) The AUTHORS item lists the author(s) or compiler(s) of source map entered as last name, first name or initial, and middle initial. The YEAR item lists the source (map) publication date. The REFERENCE item lists the remainder of the reference in USGS reference format.
    boulplss coverage: Contains lines representing U.S. Public Land Survey System township and range lines derived from USGS Digital Line Graph data
    In the coverage's boulplss.ref INFO file the SOURCE item lists the numeric code used to identify the data source. The scale item lists the scale of the source map. (This value is the denominator of the proportional fraction that identifies the scale of the map that was digitized or scanned to produce the digital map.) The AUTHORS item lists the author(s) or compiler(s) of source map entered as last name, first name or initial, and middle initial. The YEAR item lists the source (map) publication date. The REFERENCE item lists the remainder of the reference in USGS reference format.
    The INFO structure of these files is listed below: 
    BOULDIP.PAT:
COLUMN   ITEM NAME        WIDTH OUTPUT  TYPE N.DEC  ALTERNATE NAME
    1  AREA                   8    18     F      5
    9  PERIMETER              8    18     F      5
   17  BOULDIP#               4     5     B      -
   21  BOULDIP-ID             4     5     B      -
   25  PTTYPE                80    80     C      -
  105  SYMBOL                 3     3     I      -
  108  STRIKE                 3     3     I      -
  111  DIP                    3     3     I      -
  114  SOURCE                 4     4     I      -
  118  DISPLAY                3     3     I      -

BOULDIP.REF:

COLUMN   ITEM NAME        WIDTH OUTPUT  TYPE N.DEC  ALTERNATE NAME
    1  SOURCE                 4     4     I      -
    5  SCALE                  8     8     I      -
   13  AUTHORS              200   200     C      -
  213  YEAR                   4     4     I      -
  217  REFERENCE            250   250     C      -

BOULCNTY.AAT:

COLUMN   ITEM NAME        WIDTH OUTPUT  TYPE N.DEC  ALTERNATE NAME
    1  FNODE#                 4     5     B      -
    5  TNODE#                 4     5     B      -
    9  LPOLY#                 4     5     B      -
   13  RPOLY#                 4     5     B      -
   17  LENGTH                 8    18     F      5
   25  BOULCNTY#              4     5     B      -
   29  BOULCNTY-ID            4     5     B      -
   33  SOURCE                 4     4     I      -

BOULCNTY.REF:

COLUMN   ITEM NAME        WIDTH OUTPUT  TYPE N.DEC  ALTERNATE NAME
    1  SOURCE                 4     4     I      -
    5  SCALE                  8     8     I      -
   13  AUTHORS              200   200     C      -
  213  YEAR                   4     4     I      -
  217  REFERENCE            250   250     C      -

BOULHWY.AAT:

COLUMN   ITEM NAME        WIDTH OUTPUT  TYPE N.DEC  ALTERNATE NAME
    1  FNODE#                 4     5     B      -
    5  TNODE#                 4     5     B      -
    9  LPOLY#                 4     5     B      -
   13  RPOLY#                 4     5     B      -
   17  LENGTH                 8    18     F      5
   25  BOULHWY#               4     5     B      -
   29  BOULHWY-ID             4     5     B      -
   33  FEATURID               8    20     F      0
   41  DESCRIPT              35    35     C      -
   76  DSOURCE                1     1     C      -
   77  STFIPS                 2     2     C      -
   79  CTFIPS                 3     3     C      -
   82  SIGN1                  6     6     C      -
   88  SIGN2                  6     6     C      -
   94  MILES                  4    13     F      2
   98  KM                     4    13     F      2
  102  FACTYPE                8    11     F      0
  110  LANES                  8    11     F      0
  118  SOURCE                 4     4     I      -

BOULHWY.REF:

COLUMN   ITEM NAME        WIDTH OUTPUT  TYPE N.DEC  ALTERNATE NAME
    1  SOURCE                 4     4     I      -
    5  SCALE                  8     8     I      -
   13  AUTHORS              200   200     C      -
  213  YEAR                   4     4     I      -
  217  REFERENCE            250   250     C      -

BOULDHYP.AAT:

COLUMN   ITEM NAME        WIDTH OUTPUT  TYPE N.DEC  ALTERNATE NAME
    1  FNODE#                 4     5     B      -
    5  TNODE#                 4     5     B      -
    9  LPOLY#                 4     5     B      -
   13  RPOLY#                 4     5     B      -
   17  LENGTH                 8    18     F      5
   25  BOULDHYP#               4     5     B      -
   29  BOULDHYP-ID             4     5     B      -
   33  ELEV                   6     6     I      -
   39  SOURCE                 4     4     I      -

BOULDHYP.REF:

COLUMN   ITEM NAME        WIDTH OUTPUT  TYPE N.DEC  ALTERNATE NAME
    1  SOURCE                 4     4     I      -
    5  SCALE                  8     8     I      -
   13  AUTHORS              200   200     C      -
  213  YEAR                   4     4     I      -
  217  REFERENCE            250   250     C      -

BOULPLSS.AAT:

COLUMN   ITEM NAME        WIDTH OUTPUT  TYPE N.DEC  ALTERNATE NAME
    1  FNODE#                 4     5     B      -
    5  TNODE#                 4     5     B      -
    9  LPOLY#                 4     5     B      -
   13  RPOLY#                 4     5     B      -
   17  LENGTH                 8    18     F      5
   25  BOULPLSS#              4     5     B      -
   29  BOULPLSS-ID            4     5     B      -
   33  SOURCE                 4     4     I      -

BOULPLSS.REF:

COLUMN   ITEM NAME        WIDTH OUTPUT  TYPE N.DEC  ALTERNATE NAME
    1  SOURCE                 4     4     I      -
    5  SCALE                  8     8     I      -
   13  AUTHORS              200   200     C      -
  213  YEAR                   4     4     I      -
  217  REFERENCE            250   250     C      -

Coding of PTTYPE in the bouldip coverage:

Inclined bedding - Showing strike and dip
Vertical bedding - Showing strike
Overturned bedding - Showing strike and dip
    Entity_and_Attribute_Detail_Citation: http://pubs.usgs.gov/of/2003/ofr-03-024/OFR-03-024text508.pdf

Who produced the data set?

  1. Who are the originators of the data set? (may include formal authors, digital compilers, and editors)
    • Theodore R. Brandt
    • David W. Moore
    • Kyle E. Murray
  2. Who also contributed to the data set?
  3. To whom should users address questions about the data?
    Theodore R. Brandt
    U.S. Geological Survey
    MS 980, Box 25046 DFC
    Denver, CO
    USA

    303-236-1901 (voice)
    303-236-0214 (FAX)
    tbrandt@usgs.gov

Why was the data set created?

This digital map can serve various purposes. It shows potential shallow aquifers and rock units that are suitable for waste disposal, and aggregate mining, for example. The map distinguishes rock units that are somewhat predictable in physical properties and mineral content, making the map useful in planning for urban growth and zoning. Ideally, qualified experts can use the map to make derivative maps that show the suitability of rock units for various uses by man.

How was the data set created?

  1. From what previous works were the data drawn?
    Braddock and others (1970) (source 1 of 7)
    Braddock, W. A., H., Calvert R., J., Gawarecki S., and Nutalaya, Prinya, 1970, Geologic map of the Masonville quadrangle, Larimer County, Colorado: U.S. Geological Survey Geologic Quadrangle Map GQ-832..

    Type_of_Source_Media: paper
    Source_Contribution: geologic data source
    Braddock and others (1973) (source 2 of 7)
    Braddock, W. A., Calvert, R. H., O'Connor, J. T., and Swann, G. A., 1973, Geologic map and sections of Horsetooth Reservoir quadrangle, Larimer County, Colorado: U.S. Geological Survey Open-File Report 73-29.

    Type_of_Source_Media: paper
    Source_Contribution: geologic data source
    Colton and Anderson (1977) (source 3 of 7)
    Colton, Roger B., and Anderson, Larry W., 1977, Preliminary geologic map of the Erie Quadrangle, Boulder, Weld, and Adams Counties, Colorado: U.S. Geological Survey Miscellaneous Field Studies Map MF-882.

    Type_of_Source_Media: paper
    Source_Contribution: geologic data source
    Hunter (1955) (source 4 of 7)
    Hunter, Z. M., 1955, Areal geology of the foothills of the Front Range in northern Colorado: GSA Bulletin v. 66, no. 12, Part 2, pp. 1677, Geological Society of America, Denver, Colorado.

    Type_of_Source_Media: paper
    Source_Contribution: geologic data source
    Scott and Cobban (1965) (source 5 of 7)
    Scott, G. R., and Cobban, W. A., 1965, Geologic and biostratigraphic map of the Pierre shale between Jarre Creek and Loveland, Colorado: U.S. Geological Survey Miscellaneous Geological Investigations Map I-439.

    Type_of_Source_Media: paper
    Source_Contribution: geologic data source
    Soister (1965b) (source 6 of 7)
    Soister, P. E., 1965, Geologic map of the Hudson quadrangle, Weld and Adams Counties, Colorado: U.S. Geological Survey Geological Quadrangle Map GQ-398.

    Type_of_Source_Media: paper
    Source_Contribution: geologic data source
    Wrucke and Wilson (1967) (source 7 of 7)
    Wrucke, Cester T., and Wilson, Richard F., 1967, Geologic map of the Boulder quadrangle, Boulder County, Colorado: U.S. Geological Survey Open-File Report 67-281.

    Type_of_Source_Media: paper
    Source_Contribution: geologic data source
  2. How were the data generated, processed, and modified?
    Date: 1999 (process 1 of 2)
    The geologic database was compiled using ARC/INFO. Subsequent to this original compilation, we edited and corrected the database by digitizing directly into ARC/INFO from original published maps. An average RMS error of .007 or better was achieved in digitizing these features.
    Date: 02-Sep-2009 (process 2 of 2)
    Creation of original metadata record Person who carried out this activity:
    Theodore Brandt
    U.S. Geological Survey
    U.S. Geological Survey
    Denver, CO

    303-236-1901 (voice)
  3. What similar or related data should the user be aware of?
    Colton, Roger B., 2003, Geologic Map of the Boulder-Fort Collins-Greeley area, Colorado: USGS Miscellaneous Investigations Series I-855-G, United States Geological Survey, Denver, Colorado, U.S.A..

    Online Links:

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

  1. How well have the observations been checked?
    Geologic bedding attitude points were captured by hand digitizing. The digital map was assembled and edited in ARC/INFO by manually comparing hard copy plots of the digital data with source map data.
  2. How accurate are the geographic locations?
    Digitized positions on the map that depict bedding attitude symbols are estimated to be within about 50 m of the actual measurement point on the land in most instances. Horizontal positional accuracy is tested by visual comparison of hard copy test plots to source maps or comparing locations of data on a computer monitor to other data layers in the same geographic area. The database contains elevation and U.S. Public Land Survey System data derived from U. S. Geological Survey Digital Line Graph data. Accuracy of these digital data indirectly depends on accuracy of the base maps on which the original source geologic maps were compiled. These base maps were made by the U.S. Geological Survey, which routinely checks them for compliance with the National Map Accuracy Standards. Highway location data derived from U.S. Department of Transportation National Transportation Atlas, 2001 National Highway Planning Network Version 3.0 was compiled from various sources at a scale of 1:100,000 and has a positional accuracy of within 80 m of actual transportation feature position. County boundary data derived from Colorado Department of Local Affairs, Colorado Office of Emergency Management data was compiled at a scale of 1:50,000 and has a positional accuracy of within 50 m of actual boundary feature position.
  3. How accurate are the heights or depths?
  4. Where are the gaps in the data? What is missing?
    This report has not been reviewed for conformity with U.S. Geological Survey editorial standards and stratigraphic nomenclature. Data are complete: no features of Trimble and Machette's map (USGS Map I-856-H) compiled map were eliminated or generalized. Properties and physical characteristics of geologic map units (rock-stratigraphic and surficial units) are described in the text explanation. Digital base map coverage are included with this report.
  5. How consistent are the relationships among the observations, including topology?
    Map elements were visually checked for overshoots, undershoots, duplicate features, and other errors. The original Trimble and Machette published paper map (USGS Map I-856-H) conformed with U.S. Geological Survey editorial standards and stratigraphic nomenclature. The digital version of Map I-856-H (version 1.1) strictly follows this nomenclature and was reviewed by another geologist and cartographer for consistency with basic geologic principles and general conformity to USGS mapping standards. ARC/INFO software was used to create topological relations among features.

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. Although software enables the user to display images at various scales, map data in this report should not be used at scales greater than 1:100,000.
  1. Who distributes the data set? (Distributor 1 of 1)
    U.S. Geological Survey Central Publications Group
    MS 902
    Box 25046 Denver Federal Center
    Denver, CO

    303-236-5486 (voice)
    webmaster@geology.cr.usgs.gov
  2. What's the catalog number I need to order this data set? USGS Open-File Report 03-24
  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 nor any agency thereof, nor any employees thereof, make any warranty, expressed or implied, or assumes any legal liability or responsibility for the accuracy, completeness, or usefulness of any information, apparatus, product, or process disclosed in this report, or represents that its use would not infringe privately owned rights. Reference therein to any specific commercial product, process, or service by trade name, trademark, manufacturer, or otherwise does not necessarily constitute or imply its endorsement, recommendation, or favoring by the United States Government or any agency thereof. Any views and opinions of authors expressed herein do not necessarily state or reflect those of the United States Government or any agency thereof.
  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/open-file/03-24/metadata.faq.html>
Generated by mp version 2.9.48 on Tue Jul 03 20:06:14 2018