USGS - science for a changing world

USGS Geoscience Data Catalog

Additional USGS Geoscience data can be found by geographic location or by publication series.

Geologic Map of the Eminence Quadrangle, Shannon County, Missouri

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

Frequently anticipated questions:

What does this data set describe?

Geologic Map of the Eminence Quadrangle, Shannon County, Missouri
The geology of the Eminence 7 1/2-minute quadrangle , Shannon County, Missouri was mapped from 1996 through 1997 as part of the Midcontinent Karst Systems and Geologic Mapping Project, Eastern Earth Surface Processes Team. The map supports the production of a geologic framework that will be used in hydrogeologic investigations related to potential lead and zinc mining in the Mark Twain National Forest adjacent to the Ozark National Scenic Riverways (National Park Service). Digital geologic coverages will be used by other federal and state agencies in hydrogeologic analyses of the Ozark karst system and in ecological models.
Bedrock, Quaternary , residual units, faults, and structural data are each stored in separate coverages. See readme.txt file for explanation of organization.
  1. How might this data set be cited?
    Orndorff, Randall C., Harrison, Richard W., and Weary, David J., 1999, Geologic Map of the Eminence Quadrangle, Shannon County, Missouri: U.S. Geological Survey Miscellaneous Investigations Series Map I-2653, U.S. Geological Survey, Reston, Virginia.

    Online Links:

    The printed version of I-2653 is in press, and includes supplimental figures, data, interpretive text, and a cross-section.
  2. What geographic area does the data set cover?
    West_Bounding_Coordinate: -91.3778
    East_Bounding_Coordinate: -91.2472
    North_Bounding_Coordinate: 37.2518
    South_Bounding_Coordinate: 37.1233
  3. What does it look like?
  4. Does the data set describe conditions during a particular time period?
    Beginning_Date: 1996
    Ending_Date: 1999
    Currentness_Reference: data processing period
  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. It contains the following vector data types (SDTS terminology):
      • Complete Chain (730)
    2. What coordinate system is used to represent geographic features?
      Grid_Coordinate_System_Name: Universal Transverse Mercator
      UTM_Zone_Number: 15
      Scale_Factor_at_Central_Meridian: 0.9996
      Longitude_of_Central_Meridian: -93.0
      Latitude_of_Projection_Origin: 0.0
      False_Easting: 500000.0
      False_Northing: 0.0
      Planar coordinates are encoded using Coordinate pair
      Planar coordinates are specified in Meters
      The horizontal datum used is North American Datum of 1983.
      The ellipsoid used is GRS 80.
      The semi-major axis of the ellipsoid used is 6378137.0000000.
      The flattening of the ellipsoid used is 1/298.26.
      Altitude_Datum_Name: National Geodetic Vertical Datum of 1929
      Altitude_Encoding_Method: Implicit coordinate
      Altitude_Resolution: 20
      Altitude_Distance_Units: feet
  7. How does the data set describe geographic features?
    User defined items in data tables for polygon coverages for bedrock geology, quaternary surficial units and residuual deposits (see readme.txt for description of coverages):
    MapUnit = 1 to 4 character abbreviation of geologic unit
    name = unit is surficial or bedrock
    SurfType = type of surficial unit
    LithPri = primary lithology of unit
    LithSec = secondary lithology of unit
    LithTer = tertiary lithology of unit
    Form = formal Formation name
    Member = formal Member within a Formation
    Group = formal Group name
    Super Group = formal Supergroup name
    RockClass = major rock-type classification
    Age = era, age, epoch, etc.
    Geochr = geochron
    GeochrTech = technique for detemining geochron
    GeochrRef = geochron reference
    Fossil = yes/no fossils collected
    FossilType = type of fossil, phylum etc.
    FossilRef = fossil reference, e.g. a report
    CorrelExtr = correlation of unit is extrapolated or
    interpolated from other data
    Origin = author interpretation of environment of origin of
    unit = potential mineral resource
    Color =weathered color of rock as exposed in the map area
    MinPri = primary mineral in unit
    MinSec = secondary mineral in unit
    MinOth = other minerals found in unit
    ClastPri = primary clast(s) in unit
    ClastSec = secondary clast(s) in unit
    Cement = compositon of cement or matrix
    ThickApprx = approximate thickness of unit
    ThickRange = range of thickness of unit
    BedThin = there are thin beds within unit
    BedMedium = there are medium beds within unit
    BedThick = there are thick beds within unit
    ContUp = nature of upper contact
    ContLow = nature of lower contact
    FolPri = primary foliation
    FolSec = secondary foliation
    FolTer = tertiary foliation
    CMPM = contact metamorphic minerals
    RMPM = prograde regional metamorphic minerals
    RMRM = retrograde regional metamorphic minerals
    DeformAge = interpreted geoogic age and/or orogeny of
    deformation = isotopic technique used to date deformation
    DeformRef = reference to absolute or relative age of deformation
    Comments = additional information about unit
    User defined items in data tables for line coverages of contacts
    nature of geologic unit contact, may be frame, approximate, exposed, or concealed. Frame is arc along the quadrangle boundary.
    User defined items in data tables for line coverages of faults
    f_type = confidence-level of fault location: approx, inferred, mapped, projected fault_type = type of fault: dipslip, strikeslip, unkown movement = sense of movement on fault
    User defined items in data tables point coverges of structural data
    dip = angular measure of dip of planer feature azimuth = 360 degree compass direction of planar or linear feature = 360 degree direction of linear symbol type = type of feature: bd = bedding, bdh = bedding horizontal, if = inclined igneous foliation, vf = vertical igneous foliation, nic = nonthroughgoing inclined close-spaced joints, nim = nonthroughgoing inclined medium-spaced joints, niw = nonthroughgoing inclined medium-spaced joint; nvc = nonthroughgoing vertical close-spaced joints, nvm = nonthroughgoing vertical medium-spaced joints, nvw = nonthroughgoing vertical widely-spaced joints, tim = throughgoing inclined medium-spaced joints, tiw = throughgoing inclined widely spaced joints, tvc = throughgoing vetical close-spaced joints, tvm = throughgoing vertical medium-spaced joints, tvw = throughgoing vertical wide-spaced joints, jmv = joint with movement, mnf = minor fault. symbol_ang = symbol angle calculated for proper plotting in Arc/Info dip direction, will be 90 or 270 degrees off of azimuth = sense of rotation, depending on direction of dip
    Entity_and_Attribute_Detail_Citation: File readme.txt included with the data set.

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?
  3. To whom should users address questions about the data?
    USGS Eastern Earth Surface Processes Team
    Attn: David Weary
    USGS MS 926A, National Center
    Reston, Virginia

    703-648-6897 (voice)
    Hours_of_Service: Monday - Friday 7:30 - 4:00 EST

Why was the data set created?

The purpose of this geologic map and database is to support and be part of a three-dimensional geologic framework study of south-central Missouri. The framework will be used to assess environmental impacts of lead and zinc mining in the Mark Twain National Forest on the hydrologic system of the Ozark National Scenic Riverways.

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 2)
    The original map data was manually transferred to separate stable media overlays registered to a stable-base USGS 7.5 minute topographic map. The overlays were scanned using Anatech Scansmith sofware driving an Eagle 4080 ET scanner to produce .tiff files. The .tiff files were then processed via GTX Corporation's GTX OSR V4.0 software to produce .dxf vector files. The .dxf files were imported to ESRI Arc/Info and transformed to match the geographic coordinates of the quadrangle. The coverages were then edited to eliminate dangles, gaps, and other errors, and built to the appropriate topology. Items were created for features in each coverage and attributed as appropriate. Test plots were generated with data sets plotted over other data and base topography and hydrology for review by USGS map editors and authors. Errors were corrected by on-screen digitizing, and corrections were checked again by map editors and authors. A separate database file for polygon attributes was generated and populated in Microsoft Access 2000, exported as a .bdf file, converted in Arc/Info to an Info file, then joined to each polygon coverage using map_unit as the join item. Each coverage was then projected to either (UTM, Zone 15, NAD83, GRS80) or (Geographic, DD, NAD27, Clarke1866) and exported to an Arc .e00 export file. Base coverages included with the data (hypsography, hydrography, and roads) were downloaded over the WWW from the USGS GLIS site, converted from SDTS to Arc/Info coverages, built, then projected to match the data, and then exported to .e00 format also.
    Date: 14-Feb-2000 (process 2 of 2)
    Creation of original metadata record Person who carried out this activity:
    USGS Eastern Earth Surface Processes Team
    Attn: David Weary
    USGS MS 926A National Center
    Reston, Virginia

    703-648-6897 (voice)
    Hours_of_Service: Monday - Friday, 7:30 AM - 4:00 PM EST
  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?
    Attribute accuracy was tested by manually comparing hard copy plots of the digital data with the source materials. Authors as well as USGS map editors performed separate reviews.
  2. How accurate are the geographic locations?
    The data were created by delineating the boundaries from stable overlays on a USGS 7.5 minute Topographic Map at 1:24000 scale. Therefore, the mapped horizontal accuracy is assumed to be within National Map Accuracy Standards, with a horizontal accuracy of 45.6 feet at the 95% confidence level. As with all things human, potential exists for error in location by the mapper in the field especially as all ground locations were plotted manually without aid of GPS, surveying, or other precision locating equipment.
  3. How accurate are the heights or depths?
    The data were delineated off a USGS 7.5 minute topographic map at 1:24000 scale. Therefore, the vertical accuracy is assumed to be within National Map Accuracy Standards, with a vertical accuracy of 11.9 feet at the 95% confidence level. As with all things human, potential exists for error in location by the mapper in the field especially as all ground locations were plotted manually without aid of GPS, surveying, or other precision locating equipment. Measurement of some vertical positions (altitude) was aided by barometric altimeter readings, but with accuracy of only about plus or minus 20 feet. Most vertical positions are derived from the plotted horizontal position on the topographic base.
  4. Where are the gaps in the data? What is missing?
    Geologic map units were collected and digitized at a resolution appropriate for portraying on a base of 1:24,000 scale.
  5. How consistent are the relationships among the observations, including topology?
    No rigorous formal tests were performed. Polygon coverages were queried to screen for empty or inconsistent values. Line geometry is topologically clean.

How can someone get a copy of the data set?

Are there legal restrictions on access or use of the data?
Access_Constraints: none
Although all data and software released on this CD-ROM have been used by the USGS, no warranty, expressed or implied, is made by the USGS as to the accuracy of the data and related materials and (or) the functioning of the software. Any use of trade, product, or firm names is for descriptive purposes only and does not imply endorsement by the U.S. Govenment.
  1. Who distributes the data set? (Distributor 1 of 1)
    USGS Information Services
    Box 25286
    Denver Federal Center
    Denver, CO

    1-888-ASK-USGS (voice)
    303-202-4693 (FAX)
  2. What's the catalog number I need to order this data set? USGS Miscellaneous Investigations Map I-2653
  3. What legal disclaimers am I supposed to read?
    Users must assume responsibility to determine the appropriate use of these data. Please contact the USGS Eastern Earth Surface Processes Team for more detailed information.
  4. How can I download or order the data?

Who wrote the metadata?

Last modified: 23-Feb-2015
Metadata author:
Peter N Schweitzer
USGS Midwest Area
Collection manager, USGS Geoscience Data Clearinghouse,
Mail Stop 954
12201 Sunrise Valley Dr
Reston, VA

703-648-6533 (voice)
703-648-6252 (FAX)
Metadata standard:
Content Standard for Digital Geospatial Metadata (FGDC-STD-001-1998)

This page is <>

Accessibility FOIA Privacy Policies and Notices

Take Pride in America logo logo U.S. Department of the Interior | U.S. Geological Survey
Page Contact Information: Peter Schweitzer
Page Last Modified: Monday, 16-Mar-2015 16:22:43 EDT

Generated by mp version 2.9.30 on Mon Mar 16 16:22:43 2015