### Geologic map of the Big Spring quadrangle, Carter County, Missouri

Metadata also available as

#### Frequently-anticipated questions:

- What does this data set describe?
  1. How should this data set be cited?
  2. What geographic area does the data set cover?
  3. What does it look like?
  4. Does the data set describe conditions during a particular time period?
  5. What is the general form of this data set?
  6. How does the data set represent geographic features?
  7. How does the data set describe geographic features?
- Who produced the data set?
  1. Who are the originators of the data set?
  2. Who also contributed to the data set?
  3. To whom should users address questions about the data?
- Why was the data set created?
- How was the data set created?
  1. From what previous works were the data drawn?
  2. How were the data generated, processed, and modified?
  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?
  2. How accurate are the geographic locations?
  3. How accurate are the heights or depths?
  4. Where are the gaps in the data? What is missing?
  5. How consistent are the relationships among the data, including topology?
- How can someone get a copy of the data set?
  1. Are there legal restrictions on access or use of the data?
  2. Who distributes the data?
  3. What's the catalog number I need to order this data set?
  4. What legal disclaimers am I supposed to read?
  5. How can I download or order the data?
- Who wrote the metadata?

### What does this data set describe?

Title:
  Geologic map of the Big Spring quadrangle, Carter County, Missouri
Abstract:
  The geology of the Big Spring 7 1/2-minute quadrangle, Carter County, Missouri was mapped from 1998 through 2001 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?

   > David J. Weary and Robert C. McDowell, 2006, Geologic map of the Big Spring quadrangle, Carter County, Missouri: U.S. Geological Survey Scientific Investigations Map 2804, U.S. Geological Survey, Reston, VA, USA.

   > Online Links:

   > - <http://pubs.usgs.gov/imap/i2804/>

2. What geographic area does the data set cover?

   West_Bounding_Coordinate: -90.970841
   East_Bounding_Coordinate: -90.890022
   North_Bounding_Coordinate: 36.961272
   South_Bounding_Coordinate: 36.876201

3. What does it look like?

   <http://pubs.usgs.gov/imap/i2804/data/BS_thumb.jpg> (GIF)
     GIF thumbnail image of geologic map

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

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

      - G-polygon (12)
      - Label point (75)
      - GT-polygon composed of chains (72)
      - Point (4)
      - Composite object (82)

   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.

      Vertical_Coordinate_System_Definition:
        Altitude_System_Definition:
          Altitude_Resolution: 0.000010
          Altitude_Encoding_Method:
            Explicit elevation coordinate included with horizontal coordinates

7. How does the data set describe geographic features?

   `large_sinkholes`

     `Shape`
       Feature geometry. (Source: ESRI)

       Coordinates defining the features.

     `OBJECTID`
       Internal feature number. (Source: ESRI)

       Sequential unique whole numbers that are automatically generated.

     `AREA`

     `PERIMETER`

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

       Positive real numbers that are automatically generated.

     `Shape_Area`
       Area of feature in internal units squared. (Source: ESRI)

       Positive real numbers that are automatically generated.

     `BS_SINKHOLES_`

     `BS_SINKHOLES_ID`

   `big_bed.pat`

     `FID`
       Internal feature number. (Source: ESRI)

       Sequential unique whole numbers that are automatically generated.

     `Shape`
       Feature geometry. (Source: ESRI)

       Coordinates defining the features.

     `AREA`
       Area of feature in internal units squared. (Source: ESRI)

       Positive real numbers that are automatically generated.

     `PERIMETER`
       Perimeter of feature in internal units. (Source: ESRI)

       Positive real numbers that are automatically generated.

     `BIG_BED#`
       Internal feature number. (Source: ESRI)

       Sequential unique whole numbers that are automatically generated.

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

     `MAP_UNIT`

     `SURF_BED`

     `SURFTYPE`

     `LITHPRI`

     `LITHSEC`

     `LITHTER`

     `FORM`

     `MEMBER`

     `GROUP`

     `SUPERGROUP`

     `ROCKCLASS`

     `AGE`

     `GEOCHR`

     `GEOCHRTECH`

     `GEOCHRREF`

     `FOSSIL`

     `FOSSILTYPE`

     `FOSSILREF`

     `CORRELEXTR`

     `ORIGIN`

     `RES`

     `RESREF`

     `COLOR`

     `MINPRI`

     `MINSEC`

     `MINOTH`

     `CLASTPRI`

     `CLASTSEC`

     `CEMENT`

     `THICKAPPRX`

     `THICKRANGE`

     `BEDTHIN`

     `BEDMEDIUM`

     `BEDTHICK`

     `CONTUP`

     `CONTLOW`

     `FOLPRI`

     `FOLSEC`

     `FOLTER`

     `CMPM`

     `RMPM`

     `RMRM`

     `DEFORMAGE`

     `DEFORMTECH`

     `DEFORMREF`

     `COMMENTS`

   `big_bed.ratarc`

     `FID`
       Internal feature number. (Source: ESRI)

       Sequential unique whole numbers that are automatically generated.

     `Shape`
       Feature geometry. (Source: ESRI)

       Coordinates defining the features.

     `ARC#`
       Internal feature number. (Source: ESRI)

       Sequential unique whole numbers that are automatically generated.

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

     `OCE_OG-ID`

     `ID`

### Who produced the data set?

1. Who are the originators of the data set? (may include formal authors, digital compilers, and editors)

   - David J. Weary and Robert C. McDowell

2. Who also contributed to the data set?

3. To whom should users address questions about the data?

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

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

   Hours_of_Service: 8:00 AM - 3:00 PM ET
   Contact_Instructions: Email preferred.

### Why was the data set created?

> The map data 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.

### How was the data set created?

1. From what previous works were the data drawn?

   (source 1 of 1)
     Type_of_Source_Media: U.S. Geological Survey topographic base map
     Source_Scale_Denominator: 24000
     Source_Contribution: Provided spatial base for registering the map data

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

   (process 1 of 4)
     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 Arc .e00 export files.

   (process 2 of 4)
     Dataset copied.

     Data sources used in this process:

     - c:\ozarks\new_bigspring\big_bed

   (process 3 of 4)
     Dataset copied.

     Data sources used in this process:

   (process 4 of 4)
     Metadata imported.

     Data sources used in this process:

     - C:\DOCUME~1\dweary\LOCALS~1\Temp\xml115.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 atrtributes 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. As with all things human, potential exists for error in location by the mapper in the field especially as most ground locations were plotted manually without aid of GPS, surveying or other precise locating equipment.

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 horizontal accuracy is assumed to be within National Map Accuracy Standards, with a horizontal 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 many ground locations were plotted manually without the aid of GPS, surveying, or other precision locating equipment. Most vertical positions derived from the plotted horizontal position on the topographic base

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

   The 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 J. Weary
   U.S. Geological Survey
   Geologist
   12201 Sunrise Valley Drive
   Reston, VA 20192
   USA

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

   Hours_of_Service: 8:00 AM - 3:00 PM ET
   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?

4. How can I download or order the data?

   - Availability in digital form:

     Data format: | Size: 0.342

   - Cost to order the data: no fees

   - Special instructions:

     > Download at: <http://pubs.usgs.gov/imap/i2804/>. CD with data may be requested from dweary@usgs.gov.

### Who wrote the metadata?

Dates:
  Last modified: 12-Feb-2007
Metadata author:
  REQUIRED: The organization responsible for the metadata information.
  c/o REQUIRED: The person responsible for the metadata information.
  REQUIRED: The city of the address., REQUIRED: The state or province of the address. REQUIRED: The ZIP or other postal code of the address.

  REQUIRED: The telephone number by which individuals can speak to the organization or individual. (voice)

Metadata standard:
  FGDC Content Standards for Digital Geospatial Metadata (FGDC-STD-001-1998)
Metadata extensions used:
  - <http://www.esri.com/metadata/esriprof80.html>
  - <http://www.esri.com/metadata/esriprof80.html>

Generated by `mp` version 2.8.6 on Mon Feb 12 08:12:52 2007