Surficial geologic maps along the riparian zone of the Animas River and its headwater tributaries, Silverton to Durango, Colorado, with upper Animas River watershed gradient profiles

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

Frequently anticipated questions:

What does this data set describe?

Title:
Surficial geologic maps along the riparian zone of the Animas River and its headwater tributaries, Silverton to Durango, Colorado, with upper Animas River watershed gradient profiles
Abstract:
This product consists of Adobe Acrobat .PDF format documents for 10 surficial geologic strip maps along the Animas River watershed from its major headwater tributaries, south to Durango, Colo. The Animas River originates in the San Juan Mountains north of the historic mining town of Silverton, Colo. The surficial geologic maps identify surficial deposits, such as floodplain, and terrace gravels, alluvial fans, glacial till, talus, colluvium, landslides, and bogs. Sixteen primary units were mapped that included human-related deposits and structures, eight alluvial deposits, four colluvial deposits, one glacial deposit, one travertine deposit, and undifferentiated bedrock. Each of the surficial geologic strip maps has .PDF links to surficial geology photographs, which enables the user to take a virtual tour of these deposits. Geochemical data collected from mapped surficial deposits that pre-date and post-date mining activity have aided in determining the geochemical baseline in the watershed. Several photographs with their corresponding geochemical baseline profiles are accessible through .PDF links from several of the maps. A single coverage for all surficial deposits mapped is included as an ArcInfo shape file and as an Arc Export format .e00 file.
Supplemental_Information:
This product consists of one vector coverage. This coverage is that of the surficial deposits mapped along the riparian zone of the Animas River from its headwater tributaries above Silverton to Durango, Colo.
  1. How might this data set be cited?
    Robert W. Blair, Jr., Yager, Douglas B., and Church, Stanley E., 2002, Surficial geologic maps along the riparian zone of the Animas River and its headwater tributaries, Silverton to Durango, Colorado, with upper Animas River watershed gradient profiles: U.S. Geological Survey Digital Data Series DDS-71, U.S. Geological Survey, Denver, Colorado.

    Online Links:

  2. What geographic area does the data set cover?
    West_Bounding_Coordinate: -107.78353
    East_Bounding_Coordinate: -107.55006
    North_Bounding_Coordinate: 37.93581
    South_Bounding_Coordinate: 37.29523
  3. What does it look like?
    http://pubs.usgs.gov/dds/dds-071/dds71_508/dds71_text_508.pdf (PDF)
    pamphlet with links to graphic representation of 10 map layouts
  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?
    surf_dep.dbf
    Surficial geologic units (polygons)
    deposit_type
    Abbreviation for the type of deposit. Character string of width 8.
    (This field is named DEPOSIT_TY in the shapefile to fit within the 10-character limit for fields in the dBase file format)
    ValueDefinition
    Bbedrock
    B/cmixed bedrock and colluvial deposits
    B/fpmixed bedrock and floodplain deposits
    B/lsmixed bedrock and landslide deposits
    B/mmixed bedrock and glacial till deposits
    Fpfloodplain deposits
    HHuman-related deposits and structures
    Llake
    Rfpreworked floodplain deposits
    Tterrace deposits undifferentiated based on comparative relative ages
    bbog deposits
    ccolluvial deposits
    c/mmixed colluvial and glacial till deposits
    c/ovdmixed colluvial and old valley deposits
    dcdebris cone deposits
    ffan deposits undifferentiated based on comparative relative ages
    f/mmixed fan and glacial till deposits
    f/tmixed fan and terrace deposits
    f1fan deposits, with higher number corresponding to older fans
    f2fan deposits, with higher number corresponding to older fans
    f3fan deposits, with higher number corresponding to older fans
    ibiron bog deposits
    lslandslide deposits
    ls/mmixed landslide and glacial till deposits
    ls1landslide deposits, with higher number corresponding to older landslides
    ls2landslide deposits, with higher number corresponding to older landslides
    mglacial till
    m/cmixed glacial till and colluvial deposits
    m?possible glacial till
    maAnimas City (ma) and Spring Creek (ms) glacial till deposits
    msAnimas City (ma) and Spring Creek (ms) glacial till deposits
    ovdold valley deposits
    oxoxbow deposits, abandoned channels
    rBreworked bedrock
    rcreworked colluvium
    rfreworked fan
    rmreworked glacial till
    rm?possible reworked glacial till
    rtreworked terrace
    rt1reworked terrace (relative order of formation 1)
    rt2reworked terrace (relative order of formation 2)
    rvdreworked valley deposits
    t/bmixed terrace and bog deposits
    t/mmixed terrace and glacial till deposits
    t1terrace deposits, with higher number corresponding to older terraces
    t2terrace deposits, with higher number corresponding to older terraces
    t3terrace deposits, with higher number corresponding to older terraces
    t4terrace deposits, with higher number corresponding to older terraces
    tatalus deposits
    tdtravertine deposits
    vdvalley deposits
    wwater
    VALUE
    Numeric code matching symbols for a generalized portrayal of the polygon data. Integer values.
    ValueDefinition
    3(fp) floodplain deposits
    4(H) Human-related deposits and structures
    6
    (t) terrace deposits undifferentiated based on comparative relative ages
(t/b) mixed terrace and bog deposits
(t/m) mixed terrace and glacial till deposits
    8(b) bog deposits
    10
    (rvd) reworked valley deposits
(vd) valley deposits
    12(ovd) old valley deposits
    13
    (f) fan deposits undifferentiated based on comparative relative ages
(f/m) mixed fan and glacial till deposits
(f/m) mixed fan and glacial till deposits
(f/t) mixed fan and terrace deposits
(f1) fan deposits, with higher number corresponding to older fans
(f2) fan deposits, with higher number corresponding to older fans
(f3) fan deposits, with higher number corresponding to older fans
(rf) reworked fan
    14(ib) iron bog deposits
    17
    (ls) landslide deposits
(ls/m) mixed landslide and glacial till deposits
(ls1) landslide deposits, with higher number corresponding to older landslides
(ls2) landslide deposits, with higher number corresponding to older landslides
    18(dc) debris cone deposits
    21
    (L) lake
(w) water
    25
    (B) bedrock
(B/c) mixed bedrock and colluvial deposits
(B/fp) mixed bedrock and floodplain deposits
(B/ls) mixed bedrock and landslide deposits
(B/m) mixed bedrock and glacial till deposits
(rB) reworked bedrock
    80(ta) talus deposits
    81
    (m) glacial till
(m/c) mixed glacial till and colluvial deposits
(m?) possible glacial till
(ma) Animas City (ma) and Spring Creek (ms) glacial till deposits
(ms) Animas City (ma) and Spring Creek (ms) glacial till deposits
(rm) reworked glacial till
(rm?) possible reworked glacial till
    82
    (c) colluvial deposits
(c/m) mixed colluvial and glacial till deposits
(c/ovd) mixed colluvial and old valley deposits
(rc) reworked colluvium
    86(ox) oxbow deposits, abandoned channels
    109(td) travertine deposits
    Entity_and_Attribute_Overview:
    DATABASE STRUCTURE--The database structure of the map consists of one coverage, SURF_DEP, with the following INFO attribute items. 
    AREA
PERIMETER
SURF_DEP #
SURF_DEP-ID
DEPOSIT_TYPE
VALUE
    The coverage SURF_DEP contains all contact lines and label points for each polygon. The SURF_DEP.PAT INFO file has attribute fields for INFO ITEMS DEPOSIT_TYPE and VALUE. DEPOSIT_TYPE corresponds to a unique symbol that identifies specific surficial deposit types. Some units have a mixed deposit type such as b/t where both bog and terrace deposits represent a polygon. VALUE is a unique numeric identifier that represents each general class of surficial deposits. Note that where a mapped unit has multiple generations of terraces that are represented by t1, t2, and t3 in the DEPOSIT_TYPE field, these have the same numeric VALUE. The VALUE attribute also corresponds to the ArcInfo colornames.shd symbolset number used for color shading. The following detailed overview discusses all of the non-common attributes included in the SURF_DEP coverage:
    The ITEM DEPOSIT_TYPE is described as follows: 
    H = Human-related deposits and structures
Fp = floodplain deposits
Rfp = reworked floodplain deposits
T = terrace deposits undifferentiated based on comparative relative ages
t1,t2,t3,t4 = terrace deposits, with higher number corresponding to older terraces
rt = reworked terrace
rt1 = reworked terrace (relative order of formation 1)
rt2 = reworked terrace (relative order of formation 2)
vd = valley deposits
rvd = reworked valley deposits
ovd = old valley deposits
ox = oxbow deposits, abandoned channels
f = fan deposits undifferentiated based on comparative relative ages
f1,f2,f3 = fan deposits, with higher number corresponding to older fans
rf = reworked fan
b = bog deposits
ib = iron bog deposits
c = colluvial deposits
rc = reworked colluvium
dc = debris cone deposits
ta = talus deposits
ls = landslide deposits
ls1,ls2 = landslide deposits, with higher number corresponding to older landslides
m = glacial till
ma,ms = Animas City (ma) and Spring Creek (ms) glacial till deposits
m? = possible glacial till
rm = reworked glacial till
rm? = possible reworked glacial till
c/ovd = mixed colluvial and old valley deposits
c/m = mixed colluvial and glacial till deposits
m/c = mixed glacial till and colluvial deposits
f/m = mixed fan and glacial till deposits
ls/m = mixed landslide and glacial till deposits
t/m = mixed terrace and glacial till deposits
f/t = mixed fan and terrace deposits
t/b = mixed terrace and bog deposits
B/c = mixed bedrock and colluvial deposits
B/fp = mixed bedrock and floodplain deposits
B/ls = mixed bedrock and landslide deposits
B/m = mixed bedrock and glacial till deposits
td = travertine deposits
B = bedrock
rB = reworked bedrock
w = water
L =lake
    The INFO file item VALUE is populated with a numeric value that corresponds to the ArcInfo colornames.shd shadeset file and is also a unique value that represents each general class of surficial deposit types. Note that a deposit type with multiple generations of deposits such as t1, t2, and t3 have the same numeric value. Also, when there are mixed units, the value recorded in the VALUE field represents the first deposit type reported in the mixed deposit, that is, the value for t in the case of the unit t/b. The DEPOSIT_TYPES and corresponding numeric VALUE attributes are as follows: 
    H = 4
fp = 3
t = 6
vd = 10
rvd = 10
ovd = 12
ox = 86
f = 13
rf = 13
f1 = 13
f2 = 13
f3 = 13
f/m = 13
b = 8
ib = 14
c = 82
rc = 82
dc = 18
ta = 80
ls = 17
ls1 = 17
ls2 = 17
m = 81
ma = 81
ms = 81
m? = 81
rm = 81
rm? = 81
c/ovd = 82
c/m = 82
m/c = 81
f/m = 13
ls/m = 17
t/m = 6
f/t = 13
t/b = 6
B/c = 25
B/fp = 25
B/ls = 25
B/m = 25
td = 109
B = 25
rB = 25
w = 21
L = 21
    Entity_and_Attribute_Detail_Citation: http://pubs.usgs.gov/dds/dds-071/dds71_text_ver.pdf

Who produced the data set?

  1. Who are the originators of the data set? (may include formal authors, digital compilers, and editors)
    • Robert W. Blair, Jr.
    • Douglas B. Yager
    • Stanley E. Church
  2. Who also contributed to the data set?
    Robert W. Blair, Jr., mapped the surficial deposits. Douglas B. Yager created the ArcInfo coverages.
  3. To whom should users address questions about the data?
    Robert W. Blair, Jr.
    Fort Lewis College
    Department of Geosciences, Fort Lewis College
    Durango, Colorado
    USA

    (970)247-7263 (voice)
    blair_r@fortlewis.edu

Why was the data set created?

This map data was completed for the purpose of identifying the surficial deposits along the riparian zone of the Animas River and its major headwater tributaries. Mapped surficial units that were deposited before and after the onset of mining were analyzed to determine the geochemical baseline of sediments in the watershed.

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: 1998 (process 1 of 3)
    U.S. Department of Agricultural stereo color aerial photographs were used to construct the surficial geologic maps along the Animas River watershed. Photo sets were flown 9/3/73 and include project numbers F16-08067 and F16-08111. Photo scale is approximately 1:20,500. These are the largest scale photos available for the Animas River watershed and they provide the best spatial and tonal detail. Some crosschecking was done with NASA high altitude color IR photos flown 8/26/89 (NAPP 1127) with a scale of 1:46,000. Surficial deposits were mapped by R. Blair while viewing color aerial photos in stereo by interpreting morphologic, color, and textural boundary differences. Mapping was done on clear plastic overlays directly over photos using India ink drafting pens. Standard pocket stereo glasses with a magnification of 2.5 times were used to view photos. Photo maps (plastic overlays) were scaled to as much as 1:24,000 using variable scale copy machines. The map boundaries were then transferred by hand to USGS topographic green-line base mylar maps while simultaneously checking the stereo aerial photos to maintain accuracy. Mapping included surficial deposits on the valley floor and deposits within approximately one hundred to two hundred meters up the valley sides. The mapped areas were spot field checked in 1998 and 1999.
    Date: 1999 (process 2 of 3)
    Drafted line work was scanned with a scan resolution of 400 dpi. ArcInfo 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 ArcInfo's project command. ARCEDIT's EDGEMATCH command was used to join adjacent quadrangle map data. Label errors were determined and corrected and the coverage topology was established with the CLEAN command.
    Date: 09-Jul-2009 (process 3 of 3)
    Creation of original metadata record Person who carried out this activity:
    Douglas B. Yager
    U.S. Geological Survey
    Box 25046
    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 surficial deposit unit attributes were compared to paper maps for accuracy when compiled and digitized. 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 against unpublished field maps, and preliminary drafted versions of the maps.
  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 the scale of source maps used when compiling data from aerial photographs to 1:24,000-scale topographic base materials, and the task of mapping only major tributaries in the headwater region of the upper Animas River watershed and along the main stem of the Animas River.
  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.

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:24,000. 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/digital-data/71/metadata.faq.html>
Generated by mp version 2.9.48 on Tue Jul 03 20:04:43 2018