Integrated Geologic Map Databases for the United States: Alabama, Florida, Georgia, Mississippi, North Carolina, and South Carolina

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

Frequently anticipated questions:


What does this data set describe?

Title:
Integrated Geologic Map Databases for the United States: Alabama, Florida, Georgia, Mississippi, North Carolina, and South Carolina
Abstract:
This report presents the results of the USGS Mineral Resources Program activity to compile a national-scale geologic map database to support national and regional level projects, including mineral resource and geoenvironmental assessments. The only comprehensive sources of regional- and national-scale geologic maps are state geologic maps with scales ranging from 1:100,000 to 1:1,000,000. Digital versions of these state maps form the core of what is presented here. Because no adequate geologic map exists for the state of Alaska, it is being compiled in regional blocks that also form part of this national database. It is expected that this series will completed by approximately the end of 2007. These maps and databases are being released in blocks of states or, in the case of Alaska, as compiled blocks of 1:250,000-scale quadrangles as chapters in this series. For Alaska, formal maps as well as databases are being published here, whereas for the conterminous U.S. only state databases and preview graphics are presented, because published maps for most states already exist. For Alaska these regional compilations will form the base for compiling a new geologic map of the state. As documented in Chapter A, standards for the conterminous U.S. are somewhat different than those for Alaska and Hawaii.
Supplemental_Information:
This database consists of five major Arc/Info GIS datasets for each state; - one: geologic map with formations, - two: faults (where present), - three: dikes (where present), - four: miscellaneous line features (where present), - five: miscellaneous point features (where present).
  1. How might this data set be cited?
    Dicken, Connie L., Nicholson, Suzanne W., Horton, John D., Foose, Michael P., and Mueller, Julia A.L., 2005, Integrated Geologic Map Databases for the United States: Alabama, Florida, Georgia, Mississippi, North Carolina, and South Carolina: U.S. Geological Survey Open-File Report 2005-1323, U.S. Geological Survey, Reston, VA.

    Online Links:

  2. What geographic area does the data set cover?
    West_Bounding_Coordinate: -87.6349620516053
    East_Bounding_Coordinate: -79.8367213636331
    North_Bounding_Coordinate: 31.0006339380621
    South_Bounding_Coordinate: 24.2764737404176
  3. What does it look like?
  4. Does the data set describe conditions during a particular time period?
    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?
      The map projection used is Lambert Conformal Conic.
      Projection parameters:
      Standard_Parallel: 33
      Standard_Parallel: 45
      Longitude_of_Central_Meridian: -100.0
      Latitude_of_Projection_Origin: 0
      False_Easting: 0.00000
      False_Northing: 0.00000
      Planar coordinates are encoded using coordinate pair
      Abscissae (x-coordinates) are specified to the nearest 0.01
      Ordinates (y-coordinates) are specified to the nearest 0.01
      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?
    fl_geol.pat
    Polygon attribute table for the florida geologic coverage. (Source: ESRI)
    orig_label
    unmodified map unit symbol from source cover.

    type: character width: 12 output width: 12 (Source: Doug Stoeser)
    ValueDefinition
    QaAnastasia Formation
    QalAlluvium
    QbdBeach ridge and dune
    QhHolocene sediments
    QkKey Largo Limestone
    QmMiami Limestone
    QtrTrail Ridge sands
    QuUndifferentiated sediments
    TabAlum Bluff Group
    TapAvon Park Formation
    TcCypresshead Formation
    TchChattahoochee Formation
    TciCitronelle Formation
    ThHawthorn Group
    ThaHawthorn Group, Arcadia Formation
    ThatHawthorn Group, Arcadia Formation, Tampa Member
    ThcHawthorn Group, Coosawhatchie Formation
    ThccHawthorn Group, Coosawhatchie Formation, Charlton Member
    ThpHawthorn Group, Peace River Formation
    ThpbHawthorn Group, Peace River Formation, Bone Valley Member
    ThsHawthorn Group, Statenville Formation
    ThtHawthorn Group, Torreya Formation
    TicIntracoastal Formation
    TjbJackson Bluff Formation
    TmcMiccosukee Formation
    ToOcala Limestone
    TQdDunes
    TQsuShelly sediments of Plio-Pleistocene age
    TQuUndifferentiated sediments
    TQucReworked Cypresshead sediments
    TreResiduum on Eocene sediments
    TrmResiduum on Miocene sediments
    TroResiduum on Oligocene sediments
    TsSuwannee Limestone
    TsmSuwannee Limestone- Marianna Limestone undifferentiated
    TsmkSt. Marks Formation
    TtTamiami Formation
    waterwater
    sgmc_label
    orig_label + ;n where n= province number (n=0 if no province number)

    type: character width: 16 output width: 16 (Source: Doug Stoeser)
    ValueDefinition
    PSa;0Anastasia Formation
    PSHal;0Alluvium
    PSHbd;0Beach ridge and dune
    Hh;0Holocene sediments
    PSk;0Key Largo Limestone
    PSm;0Miami Limestone
    PStr;0Trail Ridge sands
    PSHu;0Undifferentiated sediments
    MIab;0Alum Bluff Group
    EOap;0Avon Park Formation
    POc;0Cypresshead Formation
    MIch;0Chattahoochee Formation
    POci;0Citronelle Formation
    MIh;0Hawthorn Group
    OGMIha;0Hawthorn Group, Arcadia Formation
    OGMIhat;0Hawthorn Group, Arcadia Formation, Tampa Member
    MIhc;0Hawthorn Group, Coosawhatchie Formation
    MIPOhcc;0Hawthorn Group, Coosawhatchie Formation, Charlton Member
    MIPOhp;0Hawthorn Group, Peace River Formation
    MIPOhpb;0Hawthorn Group, Peace River Formation, Bone Valley Member
    MIhs;0Hawthorn Group, Statenville Formation
    MIht;0Hawthorn Group, Torreya Formation
    POic;0Intracoastal Formation
    POjb;0Jackson Bluff Formation
    POmc;0Miccosukee Formation
    EOo;0Ocala Limestone
    POPSd;0Dunes
    POPSsu;0Shelly sediments of Plio-Pleistocene age
    POPSu;0Undifferentiated sediments
    POPSuc;0Reworked Cypresshead sediments
    EOre;0Residuum on Eocene sediments
    MIrm;0Residuum on Miocene sediments
    OGro;0Residuum on Oligocene sediments
    OGs;0Suwannee Limestone
    OGsm;0Suwannee Limestone- Marianna Limestone undifferentiated
    MIsmk;0St. Marks Formation
    POt;0Tamiami Formation
    water;0water
    unit_link
    composite map label = ST + sgmc_label This creates a unique identifier for every unit in the CONUS (continental United States) covers.

    type: character width: 18 output width: 18 (Source: Doug Stoeser)
    ValueDefinition
    FLPSa;0Anastasia Formation
    FLPSHal;0Alluvium
    FLPSHbd;0Beach ridge and dune
    FLHh;0Holocene sediments
    FLPSk;0Key Largo Limestone
    FLPSm;0Miami Limestone
    FLPStr;0Trail Ridge sands
    FLPSHu;0Undifferentiated sediments
    FLMIab;0Alum Bluff Group
    FLEOap;0Avon Park Formation
    FLPOc;0Cypresshead Formation
    FLMIch;0Chattahoochee Formation
    FLPOci;0Citronelle Formation
    FLMIh;0Hawthorn Group
    FLOGMIha;0Hawthorn Group, Arcadia Formation
    FLOGMIhat;0Hawthorn Group, Arcadia Formation, Tampa Member
    FLMIhc;0Hawthorn Group, Coosawhatchie Formation
    FLMIPOhcc;0Hawthorn Group, Coosawhatchie Formation, Charlton Member
    FLMIPOhp;0Hawthorn Group, Peace River Formation
    FLMIPOhpb;0Hawthorn Group, Peace River Formation, Bone Valley Member
    FLMIhs;0Hawthorn Group, Statenville Formation
    FLMIht;0Hawthorn Group, Torreya Formation
    FLPOic;0Intracoastal Formation
    FLPOjb;0Jackson Bluff Formation
    FLPOmc;0Miccosukee Formation
    FLEOo;0Ocala Limestone
    FLPOPSd;0Dunes
    FLPOPSsu;0Shelly sediments of Plio-Pleistocene age
    FLPOPSu;0Undifferentiated sediments
    FLPOPSuc;0Reworked Cypresshead sediments
    FLEOre;0Residuum on Eocene sediments
    FLMIrm;0Residuum on Miocene sediments
    FLOGro;0Residuum on Oligocene sediments
    FLOGs;0Suwannee Limestone
    FLOGsm;0Suwannee Limestone- Marianna Limestone undifferentiated
    FLMIsmk;0St. Marks Formation
    FLPOt;0Tamiami Formation
    FLwater;0water
    source
    An alphanumeric code (e.g. US001) that designates the source material used.

    type: character width: 6 output width: 8 (Source: Doug Stoeser)
    ValueDefinition
    FL001Scott, T. M., Campbell, K. M., Rupert, F. R., Arthur, J. D., Missimer, T. M., Lloyd, J. M., Yon, J. W., and Duncan, J. G., 2001, Geologic Map of the State of Florida, Florida Geological Survey & Florida Department of Environmental Protection, Map Series 146.
    FL201C.L. Dicken polygon edits. Additionally, when using US001 state boundary file, water polygons have been generated.
    unit_age
    The geologic age from the source map used.

    type: character width: 60 output width: 60 (Source: Doug Stoeser)
    ValueDefinition
    Eocene 
    Holocene 
    Miocene 
    Miocene/Pliocene 
    Oligocene 
    Oligocene/Miocene 
    Pleistocene 
    Pleistocene/Holocene 
    Pliocene 
    Pliocene/Pleistocene 
    rocktype1
    The predominant lithology found in the formation.

    type: character width: 40 output width: 40 (Source: Johnson Lith Class 6.1a)
    ValueDefinition
    alluvium 
    beach sand 
    calcarenite 
    clay or mud 
    claystone 
    delta 
    dolostone (dolomite) 
    dune sand 
    limestone 
    mixed clastic/carbonate 
    sand 
    sandstone 
    water 
    rocktype2
    The second most predominant lithology in the formation.

    type: character width: 40 output width: 40 (Source: Johnson Lith Class 6.1)
    ValueDefinition
    beach sand 
    clay or mud 
    claystone 
    dolostone 
    gravel 
    limestone 
    mudstone 
    sand 
    sandstone 
    fl_geol.aat
    Arc attribute table for florida geologic coverage. (Source: ESRI)
    arc-code
    Unique identifier for the line feature

    type: integer width: 3 output width: 3 (Source: AAT data dictionary)
    ValueDefinition
    1contact, location certain
    7shoreline or riverbank
    124state boundary
    arc-para1
    Used for "decorated" lines where additional information is needed.

    type: integer width: 3 output width: 3 (Source: AAT data dictionary)
    ValueDefinition
    0no additional information
    arc-para2
    "Scratch" field used mostly in Alaska.

    type: integer width: 3 output width: 3 (Source: AAT data dictionary)
    ValueDefinition
    0no additional information
    source
    An alphanumeric code (e.g. US001) that designates the source material used.

    type: character width: 6 output width: 8 (Source: Doug Stoeser)
    ValueDefinition
    FL001Scott, T. M., Campbell, K. M., Rupert, F. R., Arthur, J. D., Missimer, T. M., Lloyd, J. M., Yon, J. W., and Duncan, J. G., 2001, Geologic Map of the State of Florida, Florida Geological Survey & Florida Department of Environmental Protection, Map Series 146.
    US001Johnson, Bruce R. and Leveritch, Beth, 1998, 1:100,000 Scale State Boundaries of the Conterminous United States: U.S. Geological Survey, unpublished (see metadata file: st100kmeta.txt, Chapter A)
    Entity_and_Attribute_Overview:
    Coding for polygon attributes:

    NAME: FEATURE: orig_label unmodified map unit symbols from source cover sgmc_label orig_label modified for standard geologic age symbols and an integer code added for province unit_link sgmc_label and a state code identifier source reference to source of data unit_age geologic age rocktype1 predominant lithology rocktype2 second most predominant lithology

    Coding for arc attributes:

    NAME: FEATURE: arc-code unique integer identifier arc-para1 used where additional information is needed arc-para2 scratch field source reference to source of data

    Coding for point attributes:

    NAME: FEATURE: point_feature name of feature on map source reference to source of data

    Coding for dikes (special arcs) attributes:

    NAME: FEATURE: orig_label unmodified map unit symbols from source cover sgmc_label orig_label modified for standard geologic age symbols and an integer code added for province arc-code unique integer identifier dike_lith general lithology dike_age geologic age source reference to source of data

    Entity_and_Attribute_Detail_Citation: ESRI

Who produced the data set?

  1. Who are the originators of the data set? (may include formal authors, digital compilers, and editors)
    • Connie L. Dicken
    • Suzanne W. Nicholson
    • John D. Horton
    • Michael P. Foose
    • Julia A.L. Mueller
  2. Who also contributed to the data set?
    State Geologic Map Compilation (SGMC) activity of the National Surveys and Analysis projects of the US Geological Survey Mineral Resources Program.

  3. To whom should users address questions about the data?
    Suzanne W. Nicholson
    U.S. Geological Survey
    12201 Sunrise Valley Dr. MS954
    Reston, VA
    USA

    703-648-6344 (voice)
    swnich@usgs.gov

Why was the data set created?

A primary goal of this work is to develop geologic map datasets with standardized structure and attribution. The database design and standards are documented in Chapter A of this series. The intent is that contiguous databases can be merged seamlessly and without any additional effort. In addition to a common database structure, the conterminous U.S. state databases (the contiguous 48 states) have been fitted to a set of standard state boundaries so that, when states are merged, they match without slivers or overlap. No attempt has been made to reconcile differences in mapping across state boundaries.

How was the data set created?

  1. From what previous works were the data drawn?
    florida - digital (source 1 of 3)
    Survey, Florida Geological, 2001, Geologic Map of the State of Florida: Open file Report No. 80, Florida Geological Survey, Tallahassee, Florida.

    Online Links:

    Type_of_Source_Media: vector
    Source_Scale_Denominator: 750,000
    Source_Contribution: provided linework and geology for state map
    state boundaries (source 2 of 3)
    Johnson, Bruce R., unpublished, 1:100,000 Scale State Boundaries of the Conterminous United States.

    Other_Citation_Details:
    Arc/INFO coverage developed by Bruce Johnson. Derived from USGS 100,000-scale DLG boundary layer quadrangles.
    Type_of_Source_Media: online
    Source_Scale_Denominator: 100,000
    Source_Contribution: provided linework of the conterminous state boundaries
    lithclass (source 3 of 3)
    Johnson, Bruce R., unpublished, Geologic Map Unit Classification, ver. 6.1.

    Other_Citation_Details:
    Document has been modified and is included in Appedices of the publication.
    Type_of_Source_Media: online; http:/geology.usgs.gov/dm
    Source_Scale_Denominator: none
    Source_Contribution:
    Source of lithologic codes and specific rock names found in ROCKTYPE1 and ROCKTYPE2.
  2. How were the data generated, processed, and modified?
    Date: 2003 (process 1 of 10)
    The purpose of this standardization is to allow all SGMC covers to be seamlessly joined without any additional effort to form regional or national level digital maps. Note that for Alaska, the state is being compiled as blocks of 1:250k quadrangles that will ultimately be used to compile a new state map. Douglas Stoeser and Ric Wilson are co-coordinators for the overall SGMC effort, with Stoeser coordinating work on the mainland states and Wilson coordinating work for Alaska and Hawaii.
    Date: 02-Nov-2004 (process 2 of 10)
    C.L. Dicken obtained the digital geologic map of Florida from the following website: http://www.dep.state.fl.us/geology/gisdatamaps/state_geo_map.htm

    Dicken re-projected the coverage into the following:

    projection: Lambert Conformal Conic units: meters datum: NAD27 standard parallel 1: 33 0 0.000 standard parallel 2: 45 0 0.000 central meridian: -100 0 0.000 reference latitude: 0 0 0.000 false easting: 0.00000 false northing: 0.00000

    All attributes were deleted except FORMATION_.

    (Note: Attributes associated with the generation of the coverages were not deleted. PAT - shape, area, perimeter, coverage#, and coverage-id AAT - shape, fnode#, tnode#, lnode#, rnode#, length, coverage#, and coverage-id)

    The values from FORMATION_ where then calculated into a new field called orig_label.
    Date: 03-Nov-2004 (process 3 of 10)
    The relevant state outline (arcs) was removed from the coverage and replaced with the arcs from the 1:100,000 Scale State Boundaries of the Conterminous United States.

    This allows for a seamless fit of each state to a standard state boundary base.
    Date: 10-Nov-2004 (process 4 of 10)
    The following attributes were exported from Filemaker as a .dbf: orig_label, map_symbol2, unit_link, reference_id, unit_age, rocktype1, and rocktype2.

    orig_label reflects the original map symbol used on the source map

    map_symbol2 reflects map-symbol1 with the addition of a province number

    unit_link is an auto generated field based on map-symbol2 and the state abbreviation (e.g. IN001) that produces a unique identifier for each map unit

    reference_id was populated with an alphanumeric code (e.g. US001) that designates the source used for the linework and other references used to describe the age or lithologies of the unit.

    unit_age was populated with general age assignment

    rocktype1 records dominant lithology (must be >50% of unit), using standardized data dictionary

    rocktype2 records second most dominant lithology, using standardized data dictionary

    The attributes were then converted using the following structure:

    item name: orig_label width: 12 output: 12 type: c

    item name: sgmc_label width: 16 output: 16 type: c

    item name: unit_link width: 18 output: 18 type: c

    item name: source width: 6 output: 8 type: c

    item name: unit_age width: 60 output: 60 type: c

    item name: rocktype1 width: 40 output: 40 type: c

    item name: rocktype2 width: 40 output: 40 type: c
    Date: 10-Nov-2004 (process 5 of 10)
    Once the .dbf was in the correct format with standardized column widths and data structure, it was converted into a lookup table (.lut) in Arc/Info. Then a joinitem was performed to join the look-up table to the polygon attribute table. orig_label was used as the merge item.
    Date: 10-Nov-2004 (process 6 of 10)
    Next, in preparing the uniform .aat file, the following items were added to the table:

    item name: arc-code width: 3 output: 3 type: i

    item name: arc-para1 width: 3 output: 3 type: i

    item name: arc-para2 width: 3 output: 3 type: i

    item name: source width: 6 output: 8 type: c

    Date: 10-Nov-2004 (process 7 of 10)
    Arc-code was populated using the paper map source to tag the lines using the AAT line type data dictionary (see Chapter A in this series).

    Arc-para1 was populated when additional information was available such as identifying the upthrown side of a fault or direction of thrusting on a fault. (see Chapter A)

    Arc-para2 is a scratch field that is used mostly in Alaska.

    Source was populated with an alphanumeric code (e.g. US001) that designates the source used for the linework.

    Date: 18-Jan-2005 (process 8 of 10)
    Once the .aat and the .pat were populated with the correct attributes, the coverage was exported as an .e00 file (flgeol_lcc.e00).

    Then it was unprojected into geographic coordinates and exported again (flgeol_dd.e00).
    Date: 18-Jan-2005 (process 9 of 10)
    Florida does not have any faults in their coverage so no fault extraction was performed.
    Date: 18-Jan-2005 (process 10 of 10)
    Finally, the geology lines and geology polygons were converted into shapefiles; in both geographic coordinates and in Lambert Conformal Conic projection.
  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?
    The values of the attributes ROCKTYPE1 and ROCKTYPE2 were assigned based on the information in the legends of the source maps (most of which are paper). The definitions of these values are described in the draft document Geologic Map Classification version 6.1 (Johnson and others); available at the following website: http://geology.usgs.gov/dm
  2. How accurate are the geographic locations?
    Accuracy of Florida state boundary and those arcs intersecting it: The accuracy of the state boundary arcs is based on the 1:100,000 scale original data used to produce this boundary. (Johnson, Bruce R. and Leveritch, Beth, 1998, 1:100,000 Scale State Boundaries of the Conterminous United States: U.S. Geological Survey, unpublished (see metadata file: st100kmeta.txt, Chapter A))

    Those internal arcs intersecting the state boundary were extended or shortened as needed to complete polygons, possibly creating a small amount of error.
  3. How accurate are the heights or depths?
  4. Where are the gaps in the data? What is missing?
    Bodies of water are classified as water, and the geologic units underlying them are not included in this coverage.
  5. How consistent are the relationships among the observations, including topology?
    All internal polygons were checked for closure with vendor software and on hard copy plots. Overshoots and undershoots have been deleted or corrected as appropriate.

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:
This database is not meant to be used or displayed at any scale other than 1:500,000.

Any hardcopies utilizing these data sets shall clearly indicate their source. If the licensee has modified the data in any way they are obligated to describe the types of modifications they have performed on the hardcopy map. Licensee specifically agrees not to misrepresent these data sets, nor to imply that changes they made were approved by the U.S. Geological Survey.

  1. Who distributes the data set? (Distributor 1 of 1)
    U.S. Geological Survey Information Services Reston-ESIC
    U.S. Geological Survey
    507 National Center
    Reston, Virginia
    USA

    1-888-ASK-USGS or 1-703-648-5953 (voice)
  2. What's the catalog number I need to order this data set?
  3. What legal disclaimers am I supposed to read?
    Any use of trade, product, or firm names is for descriptive purposes only and does not imply endorsement by the USGS. Although these data have been used by the USGS and have been successfully imported into data base programs, no warranty, expressed or implied, is made by the USGS as to how successfully or accurately the data can be imported into any specific application software running on any specific hardware platform. The fact of distribution shall not constitute any such warranty, and no responsibility is assumed by the USGS in connection therewith. This data base GIS is not meant to be used or displayed at any scale other than 1:500,000.
  4. How can I download or order the data?
    • Availability in digital form:
      Data format: Geologic units and structural features in format ARC/INFO export (version 8.3)
      Network links: http://pubs.usgs.gov/of/2005/1323
    • Cost to order the data: none


Who wrote the metadata?

Dates:
Last modified: 19-Jan-2005
Metadata author:
U.S. Geological Survey
Attn: Connie L. Dicken
12201 Sunrise Valley Dr. MS954
Reston, VA
USA

703-648-6482 (voice)
cdicken@usgs.gov
Metadata standard:
Content Standard for Digital Geospatial Metadata (FGDC-STD-001-1998)

This page is <https://mrdata.usgs.gov/geology/state/metadata/fl.faq.html>
Generated by mp version 2.9.50 on Mon Jan 27 16:07:32 2020