Generalized Geologic Map of the Upper Animas River Watershed and Vicinity, Silverton, Colorado

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

Frequently anticipated questions:


What does this data set describe?

Title:
Generalized Geologic Map of the Upper Animas River Watershed and Vicinity, Silverton, Colorado
Abstract:
This dataset represents geology compiled for the upper Animas River Watershed near Silverton, Colorado. The source data used are derived from 1:24,000, 1:20,000, 1:48,000 and 1:250,000-scale geologic maps by geologists who have worked in this area since the early 1960's.
Supplemental_Information:
This product consists of seven vector coverages. These separate coverages include the geology, faults, veins, andesite dikes, dacite dikes, rhyolite dikes, and San Juan Caldera topographic margin.
  1. How might this data set be cited?
    Yager, Douglas B., and Bove, Dana J., 2002, Generalized Geologic Map of the Upper Animas River Watershed and Vicinity, Silverton, Colorado: U.S. Geological Survey Miscellaneous Field Studies Map MF-2377, U.S. Geological Survey, Denver, Colorado.

    Online Links:

  2. What geographic area does the data set cover?
    West_Bounding_Coordinate: -107.87511
    East_Bounding_Coordinate: -107.50006
    North_Bounding_Coordinate: 38.00012
    South_Bounding_Coordinate: 37.749787
  3. What does it look like?
    http://pubs.usgs.gov/mf/2002/mf-2377/mf-2377.gif (GIF)
    Reduced-size image of the map sheet, 250x152 pixels, 32-bit RGB true color, 25k bytes.
    http://pubs.usgs.gov/mf/2002/mf-2377/mf-2377.pdf (PDF)
    printable graphic representation of map sheet
  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.
    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: .9996
      Longitude_of_Central_Meridian: -105.0
      Latitude_of_Projection_Origin: 0.0
      False_Easting: 500000.0
      False_Northing: 0.0
      Planar coordinates are encoded using coordinate pair
      Abscissae (x-coordinates) are specified to the nearest 65
      Ordinates (y-coordinates) are specified to the nearest 65
      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 and in ArcView shapefile format. DATABASE STRUCTURE--The database structure of the map consists of seven coverages.
    GEO coverage--Contains all contact lines and label points for each polygon. The GEO.PAT INFO file has attribute fields for INFO ITEMS POLY-ID, NAME, COLOR, LITH, and AGE. POLY-ID corresponds to a unique numeric polygon identifier that relates to each formation type; NAME corresponds to the formation name; COLOR corresponds to the ARC INFO colornames.shd symbolset number used for color shading; LITH corresponds to the unit litology, or rock type; AGE corresponds to the geologic age.
    The GEO.AAT attributes are described below.
    FAULTS coverage--Contains all lines, which represent faults and or combined fault and vein structures. Some faults correspond with geologic contacts in the GEO coverage. The FAULTS coverage has the attribute items LINE_ID and TYPE. The attribute item in the ARC INFO file FAULTS.AAT contains the LINE_ID attribute, which has a number that corresponds with fault type, that is, concealed, inferred, and so forth; the TYPE field contains the fault type description.
    VEINS coverage--Contains arcs for mineralized, altered veins and fissures. The attribute item in the INFO file VEINS.AAT contains an ARC INFO ITEM fields LINE_ID and TYPE. The LINE_ID contains a number that corresponds with vein type, that is, concealed vein, mineral fissure, and so forth; the TYPE field contains a description of the vein type.
    A_DIKE coverage--Contains lines for dikes of andesitic(?) (52-68 percent SiO2) composition.
    D_DIKE coverage--Contains lines for dikes of dacitic (63-68 percent SiO2) composition.
    R_DIKE coverage--Contains lines for dikes of rhyolitic (>68 percent SiO2) composition.
    SJCALD coverage--Contains lines that define the topographic margin of the San Juan caldera; the SJCALD.AAT attributes are described below.
    The following detailed overview discusses all of the non common attributes included in each of the seven coverages that constitute the geologic map.
    The GEO coverage includes the INFO files GEO.PAT and GEO.AAT.
    The INFO file GEO.PAT has populated attribute fields for items POLY-ID, NAME, COLOR, LITH, and AGE. POLY-ID is the unique numeric polygon code that corresponds to each formation type. NAME is the formation name. COLOR is the ARC INFO colornames.shd symbolset number used for color shading. LITH is the unit lithology. (Note--abbreviations are used for some unit LITH descriptions and they are as follows-siltst = siltstone, dol. = dolomite, sandst. = sandstone, calc. = calcareous, limest. = limestone, congl. = conglomerate, and mudst. = mudstone.) AGE is the geologic age.
    Attribute codes for all geologic units are defined in order of (POLY-ID,NAME,COLOR,LITH,AGE) as follows-
    (1,Tsp,60,rhyolite ash flow tuff,Miocene)
    (3,Qb,1,N.A.,Quaternary)
    (4,lake,21,N.A.,Quaternary)
    (7,Tcl,74,rhyolite ash flow tuff,Oligocene)
    (8,Ti,96,intrusions of unknown composition,Tertiary),
    (9,Qu,16,undifferentiated surficial deposits,Quaternary)
    (10,Qtg,17,talus,glacial till and rock glacier deposits,Quaternary)
    (11,Qal,6,unconsolidated fluvial deposits including alluvial fans, Quaternary)
    (12,Qcl,95,landslide and colluvium deposits,Quaternary)
    (19,Tir,118,rhyolite dikes and plugs,Miocene)
    (20,Tid,109,dacite intrusions,Oligocene to Miocene)
    (22,Tse,71,rhyolitic to dacitic ash flow tuff,Oligocene)
    (24,Ts,71,rhyolitic ash flow tuff,Oligocene)
    (25,Td,69,rhyolitic ash flow tuff,Oligocene)
    (27,Tb,68,rhyolitic ash flow tuff,Oligocene)
    (28,Tur,70,dacitic ash flow tuff,Oligocene)
    (29,Tig,25,monzonite to granodiorite stock,Oligocene)
    (30,Tsv,12,mostly intermediate comp. lava flows,volcaniclastics, Oligocene)
    (32,Tip,84,andesite to dacite ash flow tuff and breccia,Oligocene)
    (34,Tsj,24,mostly intermediate comp. volcaniclastics,lavas,Oligocene)
    (35,Tt,127,conglomerate and sandstone,Eocene)
    (36,Kg,113,granodiorite,Cretaceous)
    (37,Jm,65,sandstone and calcareous mudstone,Jurassic)
    (38,Je,58,sandstone,Jurassic)
    (39,Trd,49,siltst.,sandst., with limest.&congl. interbeds,Triassic)
    (40,Pc,36,shale,sandst.,&congl., locally calcareous,Permian)
    (41,Ph,23,sandst., with shale,sandst.,&congl.interbeds,Pennsylvanian)
    (42,Phm,30,shale, sandstone, and conglomerate,Pennsylvanian)
    (43,Pm,48,calcareous shale, sandstone, and conglomerate,Pennsylvanian)
    (44,Ml,36,limestone w. chert/shale interbeds (top),Mississippian)
    (45,Mdu,128,altered limestone,Mississippian)
    (45,Mdu?,128,altered limestone,Mississippian)
    (46,De,129,dol. limest., w. calc. shale & sandst. interbeds,Devonian)
    (48,Ci,52,quartzite,Cambrian)
    (49,pCu,121,schist,quartzite,and gneiss,Precambrian)
    (50,Do,93,dolomite and limestone,Devonian)
    (51,Jw,63,calc. mudst.&siltst., w. limest. sandst. interbeds,Jurassic)
    (52,Km,19,shale,Cretaceous)
    (53,Kd,20,sandst. w. siltst. & calc. shale interbeds,Cretaceous)
    (59,Tf,59,dacite ash flow tuff,Oligocene)
    (60,UM,2,Not mapped)
    
    The INFO file GEO.AAT contains the attribute field LINE_ID, which in all cases is equal to "1" and which represents a solid contact.
    The FAULTS coverage is comprised of the INFO file FAULTS.AAT. FAULTS.AAT contains the attribute items LINE_ID and TYPE. LINE_ID contains a number, which corresponds to a fault type; TYPE contains the description of the fault type. The LINE_ID = TYPE are described as follows--LINE_ID = 2, TYPE "Fault", LINE_ID = 8, TYPE "concealed or inferred fault".
    The VEINS coverage is comprised of the INFO file VEINS.AAT. VEINS.AAT contains the attribute items LINE_ID and TYPE. LINE_ID contains a number,which corresponds to the vein type; TYPE contains the description of the vein type. The LINE_ID = TYPE are described as follows--LINE_ID = 22, TYPE "Vein", LINE_ID = 23, TYPE "Mineral fissure", LINE_ID = 24, TYPE = "Concealed vein or fault".
    The coverage A_DIKE (andesite dikes) includes the INFO FILE A_DIKE.AAT that has an attribute field LINE_ID; the LINE_ID = 5 in all instances.
    The coverage D_DIKE (dacite dike) includes the INFO FILE D_DIKE.AAT that has an attribute field LINE_ID; the LINE_ID = 6 in all instances.
    The coverage R_DIKE (rhyolite dike) includes the INFO FILE R_DIKE.AAT that has an attribute field LINE_ID; the LINE_ID = 4 in all instances.
    The coverage SJCALD (San Juan caldera topographic margin) includes the INFO FILE SJCALD.AAT that has attribute fields LINE_ID and Type. LINE_ID contains a number that corresponds to the topographic margin type. The LINE_ID = TYPE are described as follows--LINE_ID = 14 indicates the topographic margin and LINE_ID = 15 is the concealed or approximately located topographic margin.
    Entity_and_Attribute_Detail_Citation: http://pubs.usgs.gov/mf/2002/mf-2377/mf-2377_508.pdf

Who produced the data set?

  1. Who are the originators of the data set? (may include formal authors, digital compilers, and editors)
    • Douglas B. Yager
    • Dana J. Bove
  2. Who also contributed to the data set?
    D.B. Yager compiled and digitized geology for the Ironton, Ophir, Howardsville, and Silverton quadrangles with contribution of a digital coverage provided by R.G. Luedke for the Silverton quadrangle. D.J. Bove compiled geology for the Handies Peak quadrangle.
  3. To whom should users address questions about the data?
    Douglas B. Yager
    U.S. Geological Survey
    Denver Federal Center, MS-973
    Box 25046
    Denver, Colorado
    USA

    303-236-2487 (voice)
    dyager@usgs.gov

Why was the data set created?

This map data was compiled for the purpose of comparing multiple Animas River Watershed Abandoned Mine Lands Project datasets such as geophysical, biologic, remote sensing, and geochemical datasets in a geologic context.

How was the data set created?

  1. From what previous works were the data drawn?
    Burbank and Luedke, 1964 (source 1 of 6)
    Burbank, W.S., and Luedke, R.G., 1964, Geology of the Ironton quadrangle, Colorado: scale 1:24,000: U.S. Geological Survey Geologic Quadrangle Map GQ-291, U.S. Geologial Survey, Denver, Colorado.

    Type_of_Source_Media: paper
    Source_Contribution: Geology compiled for the Ironton quadrangle
    Steven and others, 1974 (source 2 of 6)
    Steven, T.A., Lipman, P.W., Hail, W.J., Jr., Barker, Fred, and Luedke, R.G., 1974, Geologic map of the Durango quadrangle, southwestern Colorado: scale 1:250,000: U.S. Geological Survey Miscellaneous Investigations Series Map I-764, U.S. Geological Survey, Denver, Colorado.

    Type_of_Source_Media: map
    Source_Contribution:
    granitic intrusion compiled from near the mouth of Cunningham Creek
    Luedke and Burbank, 1975a (source 3 of 6)
    Luedke, R.G., and Burbank, W.S., 1975, Preliminary geologic map of the Silverton quadrangle, Colorado: scale 1:20,000: U.S. Geological Survey Open-File Report Open-File Report 75-0433, U.S. Geological Survey, Denver, Colorado.

    Type_of_Source_Media: paper
    Source_Contribution: Geology compiled for the Silverton quadrangle
    Luedke and Burbank, 1975b (source 4 of 6)
    Luedke, R.G., and Burbank, W.S., 1975, Preliminary geologic map of the Howardsville quadrangle, Colorado: scale 1:20,000: U.S. Geological Survey Open-File Report Open-File Report 75-0432, U.S. Geological Survey, Denver, Colorado.

    Type_of_Source_Media: paper
    Source_Contribution: Geology compiled for the Howardsville quadrangle
    Lipman, 1976 (source 5 of 6)
    Lipman, P.W., 1976, Geologic map of the Lake City caldera area, western San Juan Mountains, southwestern Colorado: scale 1:48,000: U.S. Geological Survey Miscellaneous Investigations Series Map I-0962, U.S. Geological Survey, Denver, Colorado.

    Type_of_Source_Media: paper
    Source_Contribution:
    Geology compiled for part of the Howardsville and Handies Peak quadrangle
    Luedke and Burbank, 1987 (source 6 of 6)
    Luedke, R.G, and Burbank, W.S., 1987, Geologic map of the Handies Peak quadrangle, San Juan, Hinsdale, and Ouray Counties, Colorado: scale 1:24,000: U.S. Geological Survey Geologic Quadrangle Map GQ-1595, U.S. Geological Survey, Denver, Colorado.

    Type_of_Source_Media: map
    Source_Contribution: Geology compiled for part of the Handies Peak quadrangle
  2. How were the data generated, processed, and modified?
    Date: 1996 (process 1 of 2)
    Data from source maps were compiled onto stable mylar base material with use of stable, U.S. Geological Survey green line topographic base materials as a guide for transfer of geologic contacts. Drafted line work was scanned with a scan resolution of 400 dpi. ARC INFO commands, IMAGEGRID and GRIDLINE,were used for raster to vector conversion. The vector cover produced was projected first with use of the ARC INFO TRANSFORM command. The vector coverage was TRANSFORMED into an empty TICCOV derived from the vector coverage with defined corner coordinate tics with geographic data. Once transformed, the coverage was projected using ARC INFO's project command. ARCEDIT's EDGEMATCH command was utilized to join adjacent quadrangle map data. Label errors were determined and corrected and the coverage topology was established with the CLEAN command.
    Date: 18-May-2009 (process 2 of 2)
    Creation of original metadata record Person who carried out this activity:
    Douglas B. Yager
    U.S. Geological Survey
    Box 25046
    Denver Federal Center, MS-973
    Denver, Colorado
    USA

    (303) 236-2487 (voice)
    dyager@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?
    100 percent of formation attributes were compared to paper maps for accuracy when compiled and digitized. The authors included a revised interpretation of the geology of some of the volcanic units located in the western part of the map area, based on newly acquired isotopic dates (Bove and others, 1999). Thus, the percentage of San Juan Formation on our map is greater and differs from the percentage of this unit from other sources used for the compilation such as (Luedke, 1996). Field checks of every unit, fault, vein, or dike were not attempted due to the time constraints and focus and scope of the project. The user should note that the authors compiled data for the Howardsville quadrangle from one preliminary data source (Luedke, 1975b), thus the lack of detail in the western part of this quadrangle. A quantitative assessment of attribute accuracy was not attempted. Frequency tests were run on the arc and polygon labels to ensure that no features are unlabeled. The attributes have been checked by both the authors and the reviewers for agreement with published maps, unpublished field mapping, and preliminary drafted versions of the map.
  2. How accurate are the geographic locations?
    The estimated horizontal positional accuracy of the data is 10 meters. All data used from published and unpublished digital sources are limited by the accuracy of that data. Attempts were made to verify the accuracy of these data by comparison to published topographic data and overlap with other digital data.
  3. How accurate are the heights or depths?
  4. Where are the gaps in the data? What is missing?
    Completeness of the data is a function of source maps used, generalization of units, faults, and veins strategy developed by the authors during compilation, and field checking accomplished in the course of mapping altered bedrock regions. Some source data was not complete and "preliminary" such as in the western part of the Howardsville quadrangle.
  5. How consistent are the relationships among the observations, including topology?
    Polygon and chain-node topology present. Each polygon is closed and has one label point. Polygon and chain-node topology present. Each polygon is closed and has one label point.

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:
The intended scale of use for this data is 1:48,000. Over 90 percent of the data were compiled at 1:24,000 scale. Data for granitic intrusions in the southwest part of the project area were compiled from 1:250,000-scale data sources. 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, Colorado
    USA

    (303)236-5486 (voice)
    webmaster@geology.cr.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.
  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/2377/metadata.faq.html>
Generated by mp version 2.9.48 on Tue Jul 03 20:05:11 2018