The geology of the Stegall Mountain 7 1/2-minute quadrangle, Shannon and Carter Counties, South-Central Missouri

Metadata also available as

Frequently-anticipated questions:


What does this data set describe?

    Title:
    The geology of the Stegall Mountain 7 1/2-minute quadrangle, Shannon and Carter Counties, South-Central Missouri
    Abstract:
    The geology of the Stegall Mountain 7 1/2-minute quadrangle, Shannon and Carter Counties, Missouri was mapped from 1997 through 1999 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.

  1. How should this data set be cited?

    Harrison, R.W., Orndorff, R.C., and Weary, D.J., 2002, The geology of the Stegall Mountain 7 1/2-minute quadrangle, Shannon and Carter Counties, South-Central Missouri: U.S. Geological Survey Geologic Investigations Series Map I-2767, U.S. Geological Survey, Reston, VA.

    Online Links:

  2. What geographic area does the data set cover?

    West_Bounding_Coordinate: -91.252866
    East_Bounding_Coordinate: -91.121930
    North_Bounding_Coordinate: 37.126921
    South_Bounding_Coordinate: 36.998101

  3. What does it look like?

  4. Does the data set describe conditions during a particular time period?

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

      • Complete chain (426)
      • Point (4)
      • GT-polygon composed of chains (112)
      • Point (4)

    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?

    stm_faults.aat
    ArcInfo polygon attribute table

    FID
    Internal feature number. (Source: ESRI)

    Sequential unique whole numbers that are automatically generated.

    Shape
    Feature geometry. (Source: ESRI)

    Coordinates defining the features.

    FNODE#
    Internal node number for the beginning of an arc (from-node). (Source: ESRI)

    Whole numbers that are automatically generated.

    TNODE#
    Internal node number for the end of an arc (to-node). (Source: ESRI)

    Whole numbers that are automatically generated.

    LPOLY#
    Internal node number for the left polygon. (Source: ESRI)

    Whole numbers that are automatically generated.

    RPOLY#
    Internal node number for the right polygon. (Source: ESRI)

    Whole numbers that are automatically generated.

    LENGTH
    Length of feature in internal units. (Source: ESRI)

    Positive real numbers that are automatically generated.

    STM_FAULTS#
    Internal feature number. (Source: ESRI)

    Sequential unique whole numbers that are automatically generated.

    STM_FAULTS-ID
    User-defined feature number. (Source: ESRI)

    FAULTS-ID

    TYPE_
    Type of fault for symbology purposes

    TYPE_ID

    NEW_FAULTS

    FNODE_

    TNODE_

    LPOLY_

    RPOLY_

    FAULTS_NEW

    LINE_TYPE
    Type of fault symbology

    FAULTS_NEWA

    FNODE_A

    TNODE_A

    LPOLY_A

    RPOLY_A

    FAULT_

    FAULT_ID

    FNODE_AA

    TNODE_AA

    LPOLY_AA

    RPOLY_AA

    FAULT1_CLP

    FAULT1_CLPA

    LTYPE

    LL_

    RL_

    L_ID

    R_ID


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 J. Weary
    U.S. Geologcial Survey
    Geologist

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

    Hours_of_Service: 8:00 AM - 3:00 PM ET


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)
    Type_of_Source_Media: Stable-base U.S. Geological Survey topographic map
    Source_Scale_Denominator: 24000
    Source_Contribution: Base topography

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

    (process 1 of 3)
    A digital geographic base layer was created by georegistering then rectifying a .tiff image of the USGS 7.5 minute quadrangle. RMS error was required to be less than 3 meters (10 ft) in ground units. Geologic data was added as layers in ArcView 3.2 from field maps and notes by the authors. The shape files were converted to coverages and edited to eliminate dangles, gaps, and other errors, then were 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\xml79E.tmp

    (process 3 of 3)
    Metadata imported.

    Data sources used in this process:

    • C:\DOCUME~1\DAVEWE~1\LOCALS~1\Temp\xml7AD.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

  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 Weary
    U.S. Geological Survey
    Geologist

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

    Hours_of_Service: 8:00 AM - 3:00 PM ET
  2. What's the catalog number I need to order this data set?

    Downloadable Data available at: <http://pubs.usgs.gov/imap/i-2767/>

  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

  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 coverages, personal geodatabases; or importing .e00 Arc export files propduced by ESRI ArcMap V. 8.3.


Who wrote the metadata?

Dates:
Last modified: 30-Dec-2004

Metadata author:
U.S. Geological Survey
c/o David Weary
Geologist
MS 926A National Center
Reston, VA 20192
USA

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

Hours_of_Service: 8:00 AM - 3:00 PM ET
Metadata standard:
FGDC Content Standards for Digital Geospatial Metadata (FGDC-STD-001-1998)

Metadata extensions used:


Generated by mp version 2.7.33 on Thu Dec 30 11:52:03 2004