Geologic map of the Low Wassie 7 1/2-minute quadrangle, Oregon and Shannon Counties, Missouri

Metadata also available as

Frequently-anticipated questions:


What does this data set describe?

Title:
Geologic map of the Low Wassie 7 1/2-minute quadrangle, Oregon and Shannon Counties, Missouri
Abstract:
The geology of the Low Wassie 7 1/2-minute quadrangle, Oregon and Shannon Counties, Missouri was mapped from 1995 through 1996 as part of the Midcontinent Karst Systems and Geologic Mapping Project, Eastern Earth Surface Processes Team. The map supports the production of a geological 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. Purpose: The purpose of this geological 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.
  1. How should this data set be cited?

    Weems, Robert E. , 2002, Geologic map of the Low Wassie 7 1/2-minute quadrangle, Oregon and Shannon Counties, Missouri: Geologic Investigations Series Map I-2719, U.S. Geological Survey, Reston, VA, USA.

    Online Links:

  2. What geographic area does the data set cover?

    West_Bounding_Coordinate: -91.376528
    East_Bounding_Coordinate: -91.248018
    North_Bounding_Coordinate: 37.000352
    South_Bounding_Coordinate: 36.873731

  3. What does it look like?

  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: vector digital data

  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):

      • Entity point (539)
      • Label point (35)
      • GT-polygon composed of chains (35)
      • Point (8)

    2. What coordinate system is used to represent geographic features?

      Grid_Coordinate_System_Name: Universal Transverse Mercator
      Universal_Transverse_Mercator:
      UTM_Zone_Number: 15
      Transverse_Mercator:
      Scale_Factor_at_Central_Meridian: 0.999600
      Longitude_of_Central_Meridian: -93.000000
      Latitude_of_Projection_Origin: 0.000000
      False_Easting: 500000.000000
      False_Northing: 0.000000

      Planar coordinates are encoded using coordinate pair
      Abscissae (x-coordinates) are specified to the nearest 0.000032
      Ordinates (y-coordinates) are specified to the nearest 0.000032
      Planar coordinates are specified in meters

      The horizontal datum used is North American Datum of 1983.
      The ellipsoid used is Geodetic Reference System 80.
      The semi-major axis of the ellipsoid used is 6378137.000000.
      The flattening of the ellipsoid used is 1/298.257222.

  7. How does the data set describe geographic features?

    lw_strxpts

    FID
    Internal feature number. (Source: ESRI)

    Sequential unique whole numbers that are automatically generated.

    Shape
    Feature geometry. (Source: ESRI)

    Coordinates defining the features.

    AREA

    PERIMETER

    LW_STRXPTS

    LW_STRXP_1

    DIGPT

    DIP
    dip of planar feature (0-90 degrees)

    AZIMUTH
    Azimuth of strike of planar feature

    AZ
    Azimuth of strike of planar feature adjusted to right-hand-rule

    TYPE_
    Abbreviation of type of planar feature

    ValueDefinition
    BDInclined bedding
    BDHHorizontal bedding
    NICNon-throughgoing inclined closely-spaced joint
    NIMNon-throughgoing inclined medium-spaced joint
    NIWNon-throughgoing inclined widely-spaced joint
    NVCNon-throughgoing vertical closely-spaced joint
    NVMNon-throughgoing vertical medium-spaced joint
    NVWNon-throughgoing vertical widely-spaced joint
    TIMThroughgoing inclined medium-spaced joint
    TVMThroughgoing vertical medium-spaced joint
    TVWThroughgoing vertical widely-spaced joint

    SUB_TYPE

    SYMBOL_ANG
    Angle for drawing symbol in ArcPlot

    DIPDIR
    Direction of dip; vertical dips default to 90, horizonatl to 0

    ROTATION
    Rotation direction for symbol plotting, clockwise or counterclockwise


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?

    David Weary
    U.S. Geological Survey
    Geologist
    USGS MS 926A
    Reston, VA 20192
    USA

    703-648-6897 (voice)
    dweary@usgs.gov

    Hours_of_Service: 8:00 AM - 3:00 PM EST
    Contact_Instructions: email preferred


Why was the data set created?

The purpose of this geological 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?

    (source 1 of 1)
    U.S. Geological Survey, Low Wassie, MO.

    Type_of_Source_Media: Stable-base U.S. Geological Survey topographic map
    Source_Scale_Denominator: 24000
    Source_Contribution: Base map for plotting data

  2. How were the data generated, processed, and modified?

    (process 1 of 3)
    The map data was inked onto a stable-base USGS 7.5 minute topographic map. The map was scanned using Anatech Scansmith software driving an Eagle 4080 ET scanner to produce .tiff files. The .tiff files were then processed via GTX Coporation'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 and provided to the author for comparison to the original data and corrections made to all errors identified. A separate database file for map_unit polygon attributes was generated and populated in Microsoft Access 2000, exported as a .dbf 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 (NAD27, Clarke 1866) and exported to an Arc .e00 export files.

    (process 2 of 3)
    Metadata imported.

    Data sources used in this process:

    • C:\DOCUME~1\DAVEWE~1\LOCALS~1\Temp\xml3434.tmp

    (process 3 of 3)
    Metadata imported.

    Data sources used in this process:

    • C:\DOCUME~1\DAVEWE~1\LOCALS~1\Temp\xml343E.tmp

  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?

    All polygon atributes were checked for correct values against original field data by the geologists.

  2. How accurate are the geographic locations?

    These data were created by delineating the boundaries from inked lines on a stable-base USGS 7.5 minute topographic map at 1:24,000 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.

  3. How accurate are the heights or depths?

    These data were created by delineating the boundaries from inked lines on a stable-base USGS 7.5 minute topographic map at 1:24,000 scale. Therefore, the mapped vertical accuracy is assumed to be within National Map Accuracy Standards, with a horizontal accuracy of 11.9 feet at the 95% confidence level.

  4. Where are the gaps in the data? What is missing?

    These data are complete at a resolution of 1:24,000 Positional_Accuracy:

  5. How consistent are the relationships among the observations, including topology?

    These data are believed to be logically consistent, though no rigorous formal test 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 with proper citation
Use_Constraints:
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. Government.

  1. Who distributes the data set? (Distributor 1 of 1)

    David J. Weary
    U.S. Geological Survey
    Geologist

    703-648-6897 (voice)
    dweary@usgs.gov

    Hours_of_Service: 8:00 - 3:00 EST
    Contact_Instructions: email preferred.
  2. What's the catalog number I need to order this data set?

    Downloadable Data

  3. What legal disclaimers am I supposed to read?

    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.

  4. How can I download or order the data?

  5. Is there some other way to get the data?

    Cooperators or researchers with a need for the data may request a CD-ROM if downloading from the internet is not feasable. Contact David Weary, 703-648-6897 or dweary@usgs.gov with request.

  6. What hardware or software do I need in order to use the data set?

    The graphic file for the full map plate requires Adobe Acrobat Reader 5.0 or above. Use of the GIS data files requires a GIS software capable of viewing shapefiles produced by ESRI ArcMap V. 8.3.


Who wrote the metadata?

Dates:
Last modified: 13-May-2005
Metadata author:
David J. Weary
U.S. Geological Survey
Geologist
MS 926A National Center
Reston, Virginia 20192
USA

703-648-6897 (voice)
dweary@usgs.gov

Hours_of_Service: 8:00 AM - 3:00 PM EST
Contact_Instructions: email preferred
Metadata standard:
FGDC Content Standards for Digital Geospatial Metadata (FGDC-STD-001-1998)
Metadata extensions used:


Generated by mp version 2.8.6 on Fri May 13 12:18:19 2005