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

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, and Washington
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., Hopkins, Melanie J., and Haxel, Gordon A., 2005, Preliminary integrated databases for the United States - Western States: California, Nevada, Arizona, and Washington: U.S. Geological Survey Open-File Report 2005-1305, U.S. Geological Survey, Reston, Virginia, USA.

    Online Links:

    Other_Citation_Details: Original source of this data was the Arizona Geological Survey.
  2. What geographic area does the data set cover?
    West_Bounding_Coordinate: -115.692550
    East_Bounding_Coordinate: -108.394050
    North_Bounding_Coordinate: 37.506613
    South_Bounding_Coordinate: 30.723759
  3. What does it look like?
  4. Does the data set describe conditions during a particular time period?
    Calendar_Date: 2005
    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 (15980)
      • Label point (4851)
      • GT-polygon composed of chains (4851)
      • Point (2069)
      • Label point (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.001024
      Ordinates (y-coordinates) are specified to the nearest 0.001024
      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?
    azgeol_lcc.aat
    arc 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.
    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.
    AZGEOL_LCC#
    Internal feature number. (Source: ESRI) Sequential unique whole numbers that are automatically generated.
    AZGEOL_LCC-ID
    User-defined feature number. (Source: ESRI) Sequential unique whole numbers that are automatically generated.
    ARC-CODE
    unique identifier for line features
    ValueDefinition
    1Contact, location certain
    2Contact, location approximate
    4Normal fault, location certain
    5Normal fault, location approximate
    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
    32Fault, sense of displacement unknown or undefined, location inferred or queried
    52Normal fault, concealed
    53Thrust fault, concealed
    57Right lateral fault, concealed
    58Left lateral fault, concealed
    87Right lateral fault, location certain
    88Right lateral fault, location approximate
    89Right lateral fault, location inferred or queried
    90Left lateral fault, location certain
    91Left lateral fault, location approximate
    92Left lateral fault, location inferred or queried
    100Fault, sense of displacement unknown, concealed
    109Detachment fault, location certain
    113Strike-slip fault, motion unknown, location certain
    114Strike-slip fault, motion unknown, location approximate
    115Strike-slip fault, motion unknown, location inferred
    116Strike-slip fault, motion unknown, location concealed
    124State boundary
    125International boundary
    129Playa shoreline
    ARC-PARA1
    additional spatial information about structures; not used
    ARC-PARA2
    available scratch field; not used
    SOURCE
    a coded reference citation indicating source used (Source: Steve Ludington)
    ValueDefinition
    AZ001from original coverage
    AZ801arcs changed from contact to ARC-CODE = 30 (faults)
    AZ802arcs changed from contacts to ARC-CODE = 8
    AZ803arcs whose polarity was flipped to conform to right-hand rule
    AZ804arcs changed from generic high-angle fault to ARC-CODE = 4 (normal fault)
    AZ805arc changed from generic high-angle fault to ARC-CODE = 109 (detachment fault)
    AZ806arc changed from thrust fault to ARC-CODE = 4 (normal fault)
    AZ808arcs changed to ARC-CODE = 4 (normal fault) and that were flipped to conform to right-hand rule
    US001state and international boundaries
    azgeol_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.
    AZGEOL_LCC#
    Internal feature number. (Source: ESRI) Sequential unique whole numbers that are automatically generated.
    AZGEOL_LCC-ID
    User-defined feature number. (Source: ESRI)
    ORIG_LABEL
    unmodified map unit symbol from source coverage
    Formal codeset
    Codeset Name:AZunits
    Codeset Source:Accompanying attribute table in OFR 2005-1305. View by opening .csv file in Excel
    SGMC_LABEL
    orig_label + ;n, where n is a province number (0 if no provinces) (Source: Steve Ludington)
    Formal codeset
    Codeset Name:AZunits
    Codeset Source:Accompanying attribute table in OFR 2005-1305. View by opening .csv file in Excel
    UNIT_LINK
    sgmc_label, preceded by 2-letter state abbreviation); provides a unique identifier (Source: Steve Ludington)
    Formal codeset
    Codeset Name:AZunits
    Codeset Source:Accompanying attribute table in OFR 2005-1305. View by opening .csv file in Excel
    SOURCE
    a coded reference citation indicating source used (Source: Steve Ludington)
    ValueDefinition
    AZ001from original coverage
    AZ901label changed from Ppa to Pz to conform to printed map
    AZ902label changed from Jv to Jsv to conform to printed map
    AZ903label changed from Jsv to Jv to conform to printed map
    AZ904label changed from Jsv to Jv to conform to the printed map
    UNIT_AGE
    free-form field best representing geologic age of unit (Source: Steve Ludington)
    Formal codeset
    Codeset Name:AZage
    Codeset Source:Accompanying attribute table in OFR 2005-1305. View by opening .csv file in Excel
    ROCKTYPE1
    most abundant lithology in map unit (Source: Steve Ludington)
    Formal codeset
    Codeset Name:AZunits
    Codeset Source:Accompanying attribute table in OFR 2005-1305. View by opening .csv file in Excel
    ROCKTYPE2
    second most abundant lithology in map unit (Source: Steve Ludington)
    Formal codeset
    Codeset Name:AZunits
    Codeset Source:Accompanying attribute table in OFR 2005-1305. View by opening .csv file in Excel

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
    • Melanie J. Hopkins
    • Gordon A. Haxel
  2. Who also contributed to the data set?
    U.S. Geological Survey, Arizona 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?
    AGS DGM17 (source 1 of 2)
    Richards, S.J., 2001, Digital graphic files for the geologic map of Arizona: DGM 17, Arizona Geological Survey, Tucson, AZ.

    Other_Citation_Details: A representation of Arizona Geological Survey Map 35
    Type_of_Source_Media: CD-ROM
    US001 (source 2 of 2)
    Johnson, Bruce R., Unpublished Material, State boundaries.

    Type_of_Source_Media: online
    Source_Scale_Denominator: 100,000
    Source_Contribution: Provided linework for state boundaries
  2. How were the data generated, processed, and modified?
    Date: 2003 (process 1 of 15)
    Dataset copied.
    Date: 2004 (process 2 of 15)
    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. Replaced a section of the state boundary that follows the Colorado River with a line from 1:100,000 scale digital line graph hydrographic files. The state and international boundaries have a source of US001 in the AAT.
    Date: 2004 (process 3 of 15)
    A polygon was relabeled Pz (from Ppa) to conform to the printed map (source in PAT = AZ901); A polygon was relabeled Jsv (from Jv) to conform to the printed map (source in PAT = AZ902); A polygon was relabeled Jv (from Jsv) to conform to the printed map (source in PAT = AZ903); A polygon was relabeled Jv (from Jsv) to conform to the printed map (source in PAT = AZ904).
    Date: 2004 (process 4 of 15)
    Nine arcs were changed from contacts to ARC-CODE = 30 (fault, sense of displacement unknown, location certain; source in AAT = AZ801).
    Date: 2004 (process 5 of 15)
    Twenty-one arcs were changed from contacts to ARC-CODE = 8 (internal contact, no line; source in AAT = AZ802).
    Date: 2004 (process 6 of 15)
    Fourteen arcs were changed from generic high-angle fault to ARC-CODE = 4 (normal fault, location certain; source in AAT = AZ804).
    Date: 2004 (process 7 of 15)
    One arc was changed from generic high-angle fault to ARC-CODE = 109 (detachment fault, location certain; source in AAT = AZ805).
    Date: 2004 (process 8 of 15)
    One arc was changed from thrust fault to ARC-CODE = 4 (normal fault, location certain; source in AAT = AZ806).
    Date: 2004 (process 9 of 15)
    Nineteen arcs were changed to ARC-CODE = 4 (normal fault, location certain; source in AAT = AZ808). These arcs also had their polarity flipped to conform to right-hand rule.
    Date: 2004 (process 10 of 15)
    One hundred fifty-two arcs had their polarity flipped to conform to the right-hand rule (source in AAT = AZ803)
    Date: 2005 (process 11 of 15)
    The appropriate arcs were recoded as state and international boundaries.
    Date: 2005 (process 12 of 15)
    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 (OBJECTID, DATASETID, ACCURACY, TRACKINGID, TRACKINGDS, CONCEPTID, CONCEPTDS, CCONF, CARTOOBJID, CARTOOBJDS, LABEL, NAME).
    Date: 2005 (process 13 of 15)
    To prepare a uniform PAT file, the following items were added: ORIG_LABEL, SGMC_LABEL, UNIT_LINK, SOURCE, UNIT_AGE, ROCKTYPE1, and ROCKTYPE2. ORIG_LABEL was populated from the original item (PTYPE), SGMC_LABEL and UNIT_LINK were populated with information in the accompanying attribute table AZunits, UNIT_AGE was populated with information in the accompanying attribute table AZage, and ROCKTYPE1 and ROCKTYPE2 were populated with information in the accompanying attribute table AZlith. Then the original items in the PAT were deleted (OBJECTID, DATASETID, ACCURACY, TRACKINGID, TRACKINGDS, CONCEPTID, CONCEPTDS, CCONF, CARTOOBJID, CARTOOBJDS, MAPUNITID, MAPUNITDS, MCONF, LABEL).
    (process 14 of 15)
    Metadata imported. Data sources used in this process:
    • C:\DOCUME~1\Barry\LOCALS~1\Temp\xml18B.tmp
    (process 15 of 15)
    Metadata imported. Data sources used in this process:
    • C:\DOCUME~1\slud\LOCALS~1\Temp\xml12.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?
    Map unit designations follow original compilation faithfully. 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. Original source of this data was the Arizona Geological Survey.
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. Original source of this data was the Arizona Geological Survey.
  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 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?
    • Availability in digital form:
      Data format: geologic units and structural features in format ArcInfo Export (version 8.3) Size: 7.688
      Network links: http://pubs.usgs.gov/of/2005/1305/
    • Cost to order the data: none


Who wrote the metadata?

Dates:
Last modified: 16-Aug-2005
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/az.faq.html>
Generated by mp version 2.9.50 on Mon Jan 27 16:07:32 2020