1. Mineral Resources
  2. Online Spatial Data

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

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

Frequently anticipated questions:

What does this data set describe?

Title:
Preliminary integrated databases for the United States - Western States: California, Nevada, Arizona, Washington, Oregon, Idaho, and Utah
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., Stone, Paul A., Bookstrom, Arthur A., Bedford, David R., Evans, James G., Haxel, Gordon A., Nutt, Constance J., and Hopkins, Melanie J., 2005, Preliminary integrated databases for the United States - Western States: California, Nevada, Arizona, Washington, Oregon, Idaho, and Utah: U.S. Geological Survey Open-File Report OFR 2005-1305, U.S. Geological Survey, Reston, Virginia, USA.

    Online Links:

  2. What geographic area does the data set cover?
    West_Bounding_Coordinate: -126.494824
    East_Bounding_Coordinate: -113.794483
    North_Bounding_Coordinate: 43.802247
    South_Bounding_Coordinate: 31.088099
  3. What does it look like?
  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):
      • Complete chain (66831)
      • Label point (22651)
      • GT-polygon composed of chains (22651)
      • Point (4)
    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
      Latitude_of_Projection_Origin: 0
      False_Easting: 0
      False_Northing: 0
      Planar coordinates are encoded using coordinate pair
      Abscissae (x-coordinates) are specified to the nearest 500
      Ordinates (y-coordinates) are specified to the nearest 500
      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?
    utgeol_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.
    UTGEOL_LCC#
    Internal feature number. (Source: ESRI) Sequential unique whole numbers that are automatically generated.
    UTGEOL_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)
    ValueDefinition
    1Contact, location certain
    7Shoreline or riverbank
    8Internal contact
    10Thrust fault, location certain
    11Thrust fault, location approximate
    30Fault, sense of displacement unknown or undefined, location certain
    31Fault, sense of displacement unknown or undefined, location approximate
    53Thrust fault, concealed
    100Fault, sense of displacement unknown, concealed
    124State boundary
    129Playa shoreline
    ARC-PARA1
    not used
    ARC-PARA2
    not used
    SOURCE
    code used to identify the source of the feature (Source: Steve Ludington)
    Formal codeset
    Codeset Name:SOURCE
    Codeset Source:see process steps of this metadata document
    utgeol_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.
    UTGEOL_LCC#
    Internal feature number. (Source: ESRI) Sequential unique whole numbers that are automatically generated.
    UTGEOL_LCC-ID
    User-defined feature number. (Source: ESRI)
    ORIG_LABEL
    unmodified map unit symbol from source coverage (Source: Utah digital map)
    Formal codeset
    Codeset Name:UTunits
    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: UTunits)
    Formal codeset
    Codeset Name:UTunits
    Codeset Source:Accompanying attribute table in OFR 2005-1305.
    UNIT_LINK
    sgmc_label, preceded by 2-letter state abbreviation); provides a unique identifier (Source: UTunits)
    Formal codeset
    Codeset Name:UTunits
    Codeset Source:Accompanying attribute table in OFR 2005-1305.
    SOURCE
    a coded reference citation indicating source used (Source: Steve Ludington)
    Formal codeset
    Codeset Name:SOURCE
    Codeset Source:see process steps of this metadata document
    UNIT_AGE
    free-form field best representing geologic age of unit (Source: UTunits)
    Formal codeset
    Codeset Name:UTunits
    Codeset Source:Accompanying attribute table in OFR 2005-1305.
    ROCKTYPE1
    most abundant lithology in map unit (Source: UTunits)
    Formal codeset
    Codeset Name:UTunits
    Codeset Source:Accompanying attribute table in OFR 2005-1305.
    ROCKTYPE2
    second most abundant lithology in map unit (Source: UTunits)
    Formal codeset
    Codeset Name:UTunits
    Codeset Source:Accompanying attribute table in OFR 2005-1305.
    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)
    • Steve Ludington
    • Barry C. Moring
    • Robert J. Miller
    • Kathryn S. Flynn
    • Paul A. Stone
    • Arthur A. Bookstrom
    • David R. Bedford
    • James G. Evans
    • Gordon A. Haxel
    • Constance J. Nutt
    • Melanie J. Hopkins
  2. Who also contributed to the data set?
    U.S. Geological Survey, Utah 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?
    UT001 (source 1 of 2)
    Hintze, L.F., Willis, G.C., Laes, D.Y.M., Sprinkel, D.A., and Brown, K.D., Digital Geologic Map of Utah: DM Map 179DM, Utah Geological Survey, Salt Lake City, Utah.

    Other_Citation_Details: Digitized from the 1980 Geologic Map of Utah
    Type_of_Source_Media: CD-ROM
    Source_Scale_Denominator: 500000
    Source_Contribution: Basic digital geology
    US001 (source 2 of 2)
    Johnson, Bruce R., 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: 2002 (process 1 of 23)
    Dataset copied from the CD-ROM.
    Date: 2004 (process 2 of 23)
    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 23)
    Created 13 new polygons to conform to the paper map. These polygons have a SOURCE of UT901 in the PAT.
    Date: 2006 (process 4 of 23)
    One polygon was untagged in original digital coverage; it was tagged to conform to the Box Elder 1:250,000 map. This polygon has a SOURCE of UT902 in the PAT.
    Date: 2006 (process 5 of 23)
    Labels for 35 polygons were changed to conform to the paper map. These polygons have a SOURCE of UT903 in the PAT
    Date: 2006 (process 6 of 23)
    One polygon label was changed to conform to the adjacent Nevada state map. This polygon has a SOURCE of UT904 in the PAT.
    Date: 2006 (process 7 of 23)
    One polygon label was changed to conform to the Escalante1:250,000 map. This polygon has a SOURCE of UT905 in the PAT.
    Date: 2006 (process 8 of 23)
    The appropriate arcs were recoded as state and international boundaries.These have a SOURCE of US001 in the AAT.
    Date: 2006 (process 9 of 23)
    To prepare a uniform AAT file, the following items were added: arc-code, arc-para1, and arc-para2. The last two are not used. Arc-code was populated, using the information in the original item, and inspection of the printed map. Then the original items in the AAT were deleted.
    Date: 2002 (process 10 of 23)
    To prepare a uniform PAT file, the following items were added: ORIG_LABEL, SGMC_LABEL, UNIT_LINK, SOURCE, UNIT_AGE, ROCKTYPE1, and ROCKTYPE2. New unit designations for SGMC_LABEL were developed by Steve Ludington based on the key to Utah regions on the explanation sheet of the paper map. UNIT_LINK was populated with information in the accompanying attribute table UTunits, UNIT_AGE was populated with information in the accompanying attribute table CAage, and ROCKTYPE1 and ROCKTYPE2 were populated by Constance J. Nutt.
    Date: 2006 (process 11 of 23)
    Because there is no list of map units for the Utah map, Steve Ludington created original map units based on the explanation sheet of the paper map. At the same time, he assigned polygons to regions where information was available to distinguish between age and lithologic information in different regions.
    Date: 2006 (process 12 of 23)
    The labels of two polygons were changed to conform to the Cortez 1:250,000 map.These polygons have a SOURCE of UT906 in the PAT.
    Date: 2006 (process 13 of 23)
    The labels of two polygons were changed to conform to the Tooele 1:250,000 map.These polygons have a SOURCE of UT907 in the PAT.
    Date: 2006 (process 14 of 23)
    The labels of two polygons were changed to conform to the Logan 1:250,000 map.These polygons have a SOURCE of UT908 in the PAT.
    Date: 2006 (process 15 of 23)
    The labels of two polygons were changed to conform to the Salt Lake City 1:250,000 map.These polygons have a SOURCE of UT909 in the PAT.
    Date: 2006 (process 16 of 23)
    The label of one polygon was changed to conform to the Vernal 1:250,000 map.This polygon has a SOURCE of UT910 in the PAT.
    Date: 2006 (process 17 of 23)
    The label of one polygon was changed to conform to the Richfield 1:250,000 map.This polygon has a SOURCE of UT911 in the PAT.
    Date: 2006 (process 18 of 23)
    The labels of 28 polygons were changed to conform to the Box Elder 1:250,000 map.These polygons have a SOURCE of UT912 in the PAT.
    Date: 2006 (process 19 of 23)
    The labels of 73 polygons were changed to conform with stratigraphic sequence and appearance on the paper map. These polygons have a SOURCE of UT913 in the PAT.
    Date: 2006 (process 20 of 23)
    Twenty-four arcs were added to split polygons and create new ones to conform to the paper map. These arcs have a SOURCE of UT801 in the AAT.
    Date: 2006 (process 21 of 23)
    470 arcs were changed to ARC-CODE = 8 because the identity of the polygons on both sides of the arc were the same. These arcs have a SOURCE of UT802 in the AAT.
    Date: 2006 (process 22 of 23)
    295 arcs were given ARC-CODE = 8 because they were tagged as "Gilsonite veins" on the original coverage, and there is no corresponding arc code. These arcs have a SOURCE of UT803 in the AAT.
    Date: 2006 (process 23 of 23)
    ARC-CODE was changed on 102 arcs to conform to the paper map. This included labelilng water boundaries. These arcs have a SOURCE of UT804 in the AAT.
  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 follow original compilation faithfully. Regional designations were added to map units. Additional information about age and lithology was obtained from the paper map legend and geologic literature.
  2. How accurate are the geographic locations?
    The geologic map was digitized from compilations ranging in scale from 1:100,000 to 1:1,000,000, and is an accurate representation of the source maps. 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 units and 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. Used with permission, Utah Geological Survey. Modified from, Utah Geological Survey, CD-ROM Map 179DM, Digital Geologic Map of Utah.
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)
  2. What's the catalog number I need to order this data set? U.S. Geological Survey
  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?
    • Availability in digital form:
      Data format: geologic units and structural features in format ArcInfo Export (version 8.3) Size: 21.792
      Network links: http://pubs.usgs.gov/of/2005/1305/
    • Cost to order the data: none

    • Special instructions:
      Download online

Who wrote the metadata?

Dates:
Last modified: 13-Oct-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)
This page is <https://mrdata.usgs.gov/geology/state/metadata/ut.faq.html>
Generated by mp version 2.9.50 on Mon Jan 27 16:07:34 2020