USGS - science for a changing world

Mineral Resources On-Line Spatial Data

Mineral Resources > Online Spatial Data > Geology > by state

Preliminary integrated geologic map databases for the United States - Western States - California, Nevada, Arizona, Washington, Oregon, Idaho, and Utah: Idaho

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

Frequently anticipated questions:


What does this data set describe?

Title:
Preliminary integrated geologic map databases for the United States - Western States - California, Nevada, Arizona, Washington, Oregon, Idaho, and Utah: Idaho
Abstract:
These digital maps are a reformulation of previously published maps, primarily maps of states. The reformulation gives all the maps the same structure and format, allowing them to be combined into regional maps. The associated data tables have information about age and lithology of the map units, also in a standard format.
Supplemental_Information:
The data is provided in decimal degrees and in Lambert Conformal Conic projection. The data is provided in both coverage and shapefile format, and includes supplemental attribute tables. No attempt was made to reconcile differences in mapping across state boundaries.
  1. How might this data set be cited?
    Ludington, Steve, Moring, Barry C., Miller, Robert J., Flynn, Kathryn S., and Bookstrom, Arthur A., 2006, Preliminary integrated geologic map databases for the United States - Western States - California, Nevada, Arizona, Washington, Oregon, Idaho, and Utah: Idaho: Open-File Report 2005-1305, U.S. Geological Survey, Reston, Virginia, USA.

    Online Links:

    This is part of the following larger work.

    Ludington, Steve, Moring, Barry C., Miller, Robert J., Evans, James G., Stone, Paul A., Bookstrom, Arthur A., Nutt, Constance J., Bedford, David R., Haxel, Gordon A., Hopkins, Melanie J., and Flynn, Kathryn S., 2005, Preliminary integrated geologic map databases for the United States - Western States - California, Nevada, Arizona, Washington, Oregon, Idaho, and Utah.

    Online Links:

  2. What geographic area does the data set cover?
    West_Bounding_Coordinate: -118.946324
    East_Bounding_Coordinate: -110.651702
    North_Bounding_Coordinate: 49.530559
    South_Bounding_Coordinate: 41.327632
  3. What does it look like?
  4. Does the data set describe conditions during a particular time period?
    Calendar_Date: 2006Currentness_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 (31751)
      • Label point (10817)
      • GT-polygon composed of chains (10817)
      • Point (4)
      • String (0)
      • String (0)
    2. What coordinate system is used to represent geographic features?
      The map projection used is Lambert Conformal Conic.
      Projection parameters:
      Standard_Parallel: 33.000000
      Standard_Parallel: 45.000000
      Longitude_of_Central_Meridian: -100.000000
      Latitude_of_Projection_Origin: 0.000000
      False_Easting: 0.000000
      False_Northing: 0.000000
      Planar coordinates are encoded using coordinate pair
      Abscissae (x-coordinates) are specified to the nearest 0.002048
      Ordinates (y-coordinates) are specified to the nearest 0.002048
      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.400000.
      The flattening of the ellipsoid used is 1/294.978698.
  7. How does the data set describe geographic features?
    idgeol_lcc.aat
    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.
    IDGEOL_LCC#
    Internal feature number. (Source: ESRI) Sequential unique whole numbers that are automatically generated.
    IDGEOL_LCC-ID
    User-defined feature number. (Source: ESRI)
    ARC-CODE
    Code that provides geologic information about the line (Source: AAT data dictionary - see Appendix 7 of DOCUMENTATION)
    ARC-PARA1
    not used
    ARC-PARA2
    not used
    SOURCE
    A code used to identify the source of the feature
    ValueDefinition
    ID001from original coverage
    US001State and National boundary arcs
    ID801Changed designation of arcs
    ID802Changed designation of arcs
    LINE_TYPE
    MODIFIER
    ACCURACY
    L-SGMC_LABEL
    R-SGMC_LABEL
    L-MAP_UNIT
    R-MAP_UNIT
    ERR-TYPE
    idgeol_lcc.pat
    polygon attribute table (Source: ESRI)
    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.
    IDGEOL_LCC#
    Internal feature number. (Source: ESRI) Sequential unique whole numbers that are automatically generated.
    IDGEOL_LCC-ID
    User-defined feature number. (Source: ESRI)
    ORIG_LABEL
    unmodified map unit symbol from source coverage (Source: IDunits)
    Formal codeset
    Codeset Name:IDunits
    Codeset Source:Accompanying attribute table in OFR 2005-1305.
    SGMC_LABEL
    orig_label + ;n, where n is a province number (0 if no provinces) (Source: IDunits)
    Formal codeset
    Codeset Name:IDunits
    Codeset Source:Accompanying attribute table in OFR 2005-1305.
    UNIT_LINK
    sgmc_label, preceded by 2-letter state abbreviation; provides a unique identifier (Source: IDunits)
    Formal codeset
    Codeset Name:IDunits
    Codeset Source:Accompanying attribute table in OFR 2005-1305.
    SOURCE
    a coded reference citation indicating source used (Source: Steve Ludington)
    Formal codeset
    Codeset Name:idgeol_lcc.source
    Codeset Source:Accompanying attribute table in OFR 2005-1305.
    UNIT_AGE
    free-form field best representing geologic age of unit (Source: IDunits)
    Formal codeset
    Codeset Name:IDunits
    Codeset Source:Accompanying attribute table in OFR 2005-1305.
    ROCKTYPE1
    most abundant lithology in map unit (Source: IDunits)
    Formal codeset
    Codeset Name:IDunits
    Codeset Source:Accompanying attribute table in OFR 2005-1305.
    ROCKTYPE2
    second most abundant lithology in map unit (Source: IDunits)
    Formal codeset
    Codeset Name:IDunits
    Codeset Source:Accompanying attribute table in OFR 2005-1305.
    SOURCE_ID
    AB_OLD_FM
    AB_FORMATI
    AB_CHANGE
    AB_FEATURE
    JNK
    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.
    Entity_and_Attribute_Overview:
    Coding for polygon attributes- NAME FEATURE orig_label unmodified map unit symbol from original coverage sgmc_label orig_label modified for standard age symbology with an integer for region unit_link sgmc_label preceded by state code identifier source reference to source of the data unit_age geologic age of map unit rocktype1 most abundant lithology rocktype2 second most abundant lithology

    Coding for arc attributes- NAME FEATURE arc-code descriptor of type of line arc-para1 not used arc-para2 not used source reference to source of the data

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?
    U.S. Geological Survey
  3. To whom should users address questions about the data?
    Steve Ludington
    U.S. Geological Survey
    geologist
    U.S. Geological Survey, MS 901
    Menlo Park, CA
    USA

    650.329.5371 (voice)
    slud@usgs.gov

Why was the data set created?

Provide digital maps and databases that, because of their common structure and format, allow creation of regional maps that depict age and lithology of map units.

How was the data set created?

  1. From what previous works were the data drawn?
    USGS OFR 95-690 (source 1 of 2)
    Johnson, B.R., and Raines, G.L., 1996, Digital representation of the Idaho state geologic map: a contribution to the Interior Columbia River basin ecosystem management project: U.S. Geological Survey Open-File Report 95-690, U.S. Geological Survey, Reston, VA.

    Online Links:

    Type_of_Source_Media: online
    Source_Scale_Denominator: 500000
    Source_Contribution: original coverage
    US001 (source 2 of 2)
    Johnson, Bruce R., Unpublished Material, State boundaries.

    Type_of_Source_Media: online
    Source_Scale_Denominator: 100000
    Source_Contribution: Provided linework for state boundaries
  2. How were the data generated, processed, and modified?
    Date: 2005 (process 1 of 5)
    Dataset copied from USGS website.
    Date: 2005 (process 2 of 5)
    Adjusted the perimeter of the coverage to match a reference dataset of state boundaries derived from 1:100,000 scale digital line graphs. This allows the map to be used together with adjoining state maps referenced to the same boundary data. The state boundaries have a source of US001 in the AAT.
    Date: 2006 (process 3 of 5)
    Following standard items were added to AAT: ARC-CODE, ARC-PARA1, ARC-PARA2 (last two not used). ARC-CODE was populated using the line codes in the original coverage and inspection of the printed map. Original items in AAT were deleted.
    Date: 2006 (process 4 of 5)
    The original map had no unit names or descriptions. Art Bookstrom compiled this information into the accompanying database tables, in effect, creating a new legend. About 4,000 of nearly 11,000 polygons had their designations changed to conform to this new legend, and many new units were created. This information is stored in the SGMC_LABEL field of the PAT. The individual changes are documented in the SOURCE field of the PAT. The key to what those changes were is in an accompanying table, IDGEOL_LCC.SOURCE, which can be joined to the PAT using SOURCE as the key field.
    Date: 2006 (process 5 of 5)
    Following standard items were added to PAT: ORIG_LABEL, SGMC_LABEL, UNIT_LINK, SOURCE, UNIT_AGE, ROCKTYPE1, AND ROCKTYPE2. ORIG_LABEL was populated from the original coverage item, and the other information was obtained from the accompanying database tables (ORunits, ORage, ORlith). Unneeded items were then deleted from the PAT.
  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?
    Map unit designations were completely renovated and modernized by Art Bookstrom, using the paper map legend and geologic literature.
  2. How accurate are the geographic locations?
    The geologic map was digitized from a map compiled at 1:500,000, and is an accurate representation of the source map. It is intended to be used at scales equal to or smaller than 1:500,000. Display at significantly larger scales may produce error in location of contacts or faults relative to features contained in other data sets. The state boundary arcs are based on the 1:100,000 scale USGS topographic map series digital line graphs.
  3. How accurate are the heights or depths?
  4. Where are the gaps in the data? What is missing?
    The dataset contains all the map unit polygons portrayed on the original map, although many of their designations have changed. The dataset contains all the faults that were portrayed on the original printed map. Bodies of water are classified as water and geologic units underlying them are not portrayed.
  5. How consistent are the relationships among the observations, including topology?
    All internal polygons were checked for closure. 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:
No warranty, expressed or implied, is made regarding the accuracy or utility of this data for general or scientific purposes, nor shall the act of distribution constitute any such warranty. The U.S. Geological Survey shall not be held liable for improper or incorrect use of this data.
Use_Constraints:
This database is not meant to be used at scales appreciably larger or smaller than the original scale. Any printed material utilizing these databases shall clearly indicate their source. If modifications to the data are made, this should be clearly indicated and described in print. Users specifically agree not to misrepresent these data, nor to imply that any changes they have made were approved by the U.S. Geological Survey. This database has been approved for release and publication by the Director of the U.S. Geological Survey. Although the database has been subjected to review and is substantially complete, the U.S. Geological Survey reserves the right to revise the data pursuant to further analysis and review. The database is released on the condition that neither the U.S. Geological Survey or the United States Government may be held liable for any damages resulting from its authorized or unauthorized use.
  1. Who distributes the data set? (Distributor 1 of 1)
    U.S. Geological Survey Information Services
    U.S. Geological Survey, 507 National Center
    Reston, VA
    USA

    1.800.ASK.USGS (voice)
    http://www.usgs.gov/contact/
  2. What's the catalog number I need to order this data set? U.S. Geological Survey Open-File Report OFR 2005-1305
  3. What legal disclaimers am I supposed to read?
    This report is preliminary and has not been reviewed for conformity with U.S. Geological Survey editorial standards, nor with the North American Stratigraphic Code. Any use of trade, product, or firm names is for descriptive purposes only and does not imply endorsement by the U.S. Geological Survey. Although these data have been used by the U.S. Geological Survey, and imported into appropriate software, no warranty, express or implied, is made by the U.S. Geological Survey as to how successfully or accurately the data can be imported into specific application software running on specific hardware platforms. The fact of distribution shall not constitute any such warranty, and no responsibility is assumed by the U.S. Geological Survey in connection therewith. This data is not meant to be used or displayed at scales substantially larger than 1:500,000.
  4. How can I download or order the data?

Who wrote the metadata?

Dates:
Last modified: 03-Oct-2006
Last Reviewed: 2006
Metadata author:
U.S. Geological Survey
Attn: Steve Ludington
geologist
USGS, MS 901
Menlo Park, CA
USA

650.329.5371 (voice)
slud@usgs.gov
Metadata standard:
Content Standard for Digital Geospatial Metadata (FGDC-STD-001-1998)
Metadata extensions used:

This page is <https://mrdata.usgs.gov/geology/state/metadata/id.faq.html>

Accessibility FOIA Privacy Policies and Notices

USA.gov logo U.S. Department of the Interior | U.S. Geological Survey
Page Contact Information: Peter Schweitzer
Page Last Modified: Monday, 03-Jul-2017 15:29:12 MDT

Generated by mp version 2.9.40 on Mon Jul 3 15:29:12 2017