Digital geologic map of Arizona: a digital database derived from the 1983 printing of the Wilson, Moore, and Cooper 1:500,000-scale map

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

Frequently anticipated questions:


What does this data set describe?

Title:
Digital geologic map of Arizona: a digital database derived from the 1983 printing of the Wilson, Moore, and Cooper 1:500,000-scale map
Abstract:
The Geologic Map of Arizona was compiled at a scale of 1:500,000 by Eldred D. Wilson, Richard T. Moore and John R. Cooper, in 1969 and reprinted in 1977, 1981, and 1983.
Comparison of an acetate copy of the 1983 map with existing paper copies of earlier maps shows some updating of the original by 1983. This 1983 acetate was scanned and vectorized by Optronics Specialty Co., Inc. in 1998, and put into an Arc/Info geographic information system (GIS). The digital geologic map database can be queried in many ways to produce a variety of derivative geologic maps.
Supplemental_Information:
This GIS database consists of 4 Arc/Info datasets: one line and polygon file (azgeol) containing geologic contacts and structures (lines) and geologic map rock units (polygons), one line file (azfold) containing the folds and crater boundaries, one point file (azptfeat) containing geologic features, cinder cones and diatremes. one point file (azptdec) containing decorations, and
  1. How might this data set be cited?
    Hirschberg, Douglas M., and Pitts, G. Stephen, 2000, Digital geologic map of Arizona: a digital database derived from the 1983 printing of the Wilson, Moore, and Cooper 1:500,000-scale map: U.S. Geological Survey Open-File Report 00-409, U.S. Geological Survey, Menlo Park, California.

    Online Links:

  2. What geographic area does the data set cover?
    West_Bounding_Coordinate: -115.00
    East_Bounding_Coordinate: -108.75
    North_Bounding_Coordinate: 37.00
    South_Bounding_Coordinate: 31.25
  3. What does it look like?
  4. Does the data set describe conditions during a particular time period?
    Calendar_Date: 2000
    Currentness_Reference:
    Publication Date of Open-File Report 00-409
  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. It contains the following vector data types (SDTS terminology):
      • Point (10803)
      • String (25546)
      • GT-polygon composed of chains (10807)
    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: -112
      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 25.39368057251
      Ordinates (y-coordinates) are specified to the nearest 25.39368057251
      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?
    Entity_and_Attribute_Overview:
    The 'Digital Geologic Map of Arizona; a digital database from the 1983 printing of the Eldred D. Wilson and Richard T. Moore, and John R. Cooper 1:500,000-scale map' Open-File Report 00-409 contains a detailed description of each attribute code and a reference to the associated map symbols on the map source materials.
    This GIS database consists of four Arc/Info datasets: one line and polygon file, azgeol, containing geologic contacts and structures (lines) and geologic map rock units (polygons), one line file, azfold, containing the folds and crater boundaries, one point file, azptfeat, containing geologic features, cinder cones and diatremes, and one point file, azptdec, containing decorations.
    Azgeol contains an arc attribute table, azgeol.aat, which relates geologic linework arc attribution to the contact look-up table, azgeol.con, the structural attribute table, azgeol.str and the source reference look-up table, sources.ref.
    Azgeol also contains a polygon attribute table, azgeol.pat, which relates the polygons to the rock-unit look-up table, azgeol.ru, and the source reference look-up table, sources.ref.
    Azfold contains an arc attribute table, azfold.aat, which relates to the structural attribute table, azfold.str, and the source reference look-up table, sources.ref.
    Azptfeat contains the point attribute table, azptfeat.pat, which relates the feature points to their descriptions in azptfeat.lut, and the source reference look-up table, sources.ref.
    Azptdec contains the point attribute table, azptdec.pat, which relates the points to descriptions in the look-up table, azptdec.lut, and the source reference look-up table, sources.ref.
    Entity_and_Attribute_Detail_Citation: http://pubs.usgs.gov/of/2000/0409/00readme.txt

Who produced the data set?

  1. Who are the originators of the data set? (may include formal authors, digital compilers, and editors)
    • Douglas M. Hirschberg
    • G. Stephen Pitts
  2. Who also contributed to the data set?
    Eldred D. Wilson, Richard T. Moore, and John R. Cooper compiled the geologic map of which an acetate archive copy of the separates were located in Reston VA. Robert Miller (USGS) attached fiducial tics to assure registration accuracy. Optronics Specialty Co., Inc. scanned the geologic map and provided minimally attributed Arc/Info interchange-format files to the USGS.
    Douglas M. Hirschberg imported the files, transformed them to Lambert Conformal Conic, attached and attributed an interim geologic map data model, verified arc, point, and polygon attribution, added, re-positioned, or re-attributed features as needed, and assisted in creating the look-up tables.
    G. Stephen Pitts assisted with the design of the data model, entered the explanatory and source text, assisted in creating the look-up tables, and wrote the metadata.
  3. To whom should users address questions about the data?
    G. Stephen Pitts
    U.S. Geological Survey
    GIS Lab coordinator, contractor
    520 N. Park Ave, suite 355
    Tucson, Arizona
    USA

    1-520-670-5511 (voice)
    1-520-670-5571 (FAX)
    bear@usgs.gov

Why was the data set created?

This database was developed to provide a GIS of the geologic map of the State of Arizona for use at a scale of 1:500,000 or smaller. This GIS is intended for use in future spatial analysis by a variety of users. The geologic unit descriptions for this map may be updated to reflect more current description of structures and the geochronology of the map units.
This database is not meant to be used or displayed at any scale larger than 1:500,000 (e.g., 1:100,000 or 1:24,000)

How was the data set created?

  1. From what previous works were the data drawn?
    Wilson and others (1983) (source 1 of 1)
    Wilson, Eldred D., Moore, Richard T., and Cooper, John R., 1983, Geologic Map of Arizona: map series: G 81036, U.S. Geological Survey, Reston, VA.

    Type_of_Source_Media: acetate separate
    Source_Scale_Denominator: 500000
    Source_Contribution: geologic units, contact, and structure
  2. How were the data generated, processed, and modified?
    Date: 1998 (process 1 of 4)
    The original separates for this map were not locatable in Menlo Park, CA, and after extensive search, thought to no longer exist. By thorough investigation, two separates, the water layer and the geologic units, were found in a map tube in Reston, VA., and forwarded to Menlo Park, CA. where Robert Miller attached Lat-Lon tics to the acetate layer of the geologic units to assure registration accuracy
    Date: 1998 (process 2 of 4)
    The registered acetate separate of the geologic units, contacts, and structure was scanned, vectorized, minimally attributed, and exported to an Arc/Info interchange-format by Optronics Specialty Co., Inc and files were given to the USGS in Tucson
    Date: 1999 (process 3 of 4)
    The four coverages were transformed to Lambert Conformal Conic projection using 28 tics which produced an RMS error of 0.004. All linework, points, and attributions were verified by extensively comparison between printed versions of the map, the 1983 source acetate, and hard copy plots derived from the database. Some very small polygons were not identifiable on the original printed maps or the acetate, and were eliminated. Some small polygons were missing from the initial capture, and were re-captured by D.M. Hirschberg.
    All faults were attributed as Throw Unknown, Normal, Thrust, or Strike Slip, as determined from visual inspection of attributions on the paper map. Faults where attributed, were identified as U/D, T, or, in two cases on the 1983 map, with the right lateral strike slip decoration. Sense of up or down was determined by placement of the letters U and D on the paper map. Sense of upper plate, lower plate for thrust faults was inconsistent, (T on side of older rock in some cases and on side of younger rocks in other), so no upper plate / lower plate attribution was made on the Trust faults.
    Date: 24-Sep-1999 (process 4 of 4)
    Creation of original metadata record Person who carried out this activity:
    U.S. Geological Survey
    Attn: G. Stephen Pitts
    GIS lab manager, contractor
    520 N. Park Ave, suite 355
    Tucson, Arizona
    United States of America

    520.670.5511 (voice)
    520.670.5571 (FAX)
    bear@usgs.gov
  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?
    Accuracy of the Attribution was verified by manual comparison of the sources with hard copy printouts and plots.
  2. How accurate are the geographic locations?
    The horizontal positional accuracy for the digital data may be no better than +/- 500 meters (1 mm at mapscale). It was tested by visual comparison of the source acetate and available paper maps with hard copy plots.
  3. How accurate are the heights or depths?
  4. Where are the gaps in the data? What is missing?
    The digital dataset was produced from a previously published map (Wilson, Moore, & Cooper, 1969) which is considered to be a high quality cartographic product, generally speaking contacts exist where mapped, and the best available at 1:500,000. From subsequent mapping, errors are known to exist with the structure and geochronology.
  5. How consistent are the relationships among the observations, including topology?
    Polygon and chain-node topology present.
    Polygons intersecting the neatline are closed along the border. Segments making up the outer and inner boundaries of a polygon tie end-to-end to completely enclose the area. Line segments are a set of sequentially numbered coordinate pairs. No duplicate features exist nor duplicate points in a data string. Intersecting lines are separated into individual line segments at the point of intersection. All nodes are represented by a single coordinate pair which indicates the beginning or end of a line segment. The map boundary came from the scan, was projected to Lambert Conformal Conic.

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:
These data are not to be used at scales greater than 1:500,000. Any hardcopies utilizing these data sets shall clearly indicate their source. If the user has modified the data in any way they are obligated to describe the types of modifications they have performed on the hardcopy map. User 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
    Open-File Reports, Box 25286
    Denver, CO
    USA

    1-303-202-4200 (voice)
    1-303-202-4693 (FAX)
  2. What's the catalog number I need to order this data set? USGS Open-File Report 00-409
  3. What legal disclaimers am I supposed to read?
    The U.S. Geological Survey (USGS) provides these geographic data "as is." The USGS makes no guarantee or warranty concerning the accuracy of information contained in the geographic data. The USGS further makes no warranties, either expressed or implied as to any other matter whatsoever, including, without limitation, the condition of the product, or its fitness for any particular purpose. The burden for determining fitness for use lies entirely with the user. Although these data have been processed successfully on computers at the USGS, no warranty, expressed or implied, is made by the USGS regarding the use of these data on any other system, nor does the fact of distribution constitute or imply any such warranty. In no event shall the USGS have any liability whatsoever for payment of any consequential, incidental, indirect, special, or tort damages of any kind, including, but not limited to, any loss of profits arising out of use of or reliance on the geographic data or arising out of the delivery, installation, operation, or support by USGS.
    This digital geologic map GIS of the Geologic Map of Arizona at a scale of 1:500,000, is not meant to be used or displayed at any scale larger than 1:500,000 (e.g., 1:62,500 or 1:24,000).
  4. How can I download or order the data?

Who wrote the metadata?

Dates:
Last modified: 23-Feb-2015
Metadata author:
Peter N Schweitzer
USGS Midwest Area
Collection manager, USGS Geoscience Data Clearinghouse, http://geo-nsdi.er.usgs.gov/
Mail Stop 954
12201 Sunrise Valley Dr
Reston, VA
USA

703-648-6533 (voice)
703-648-6252 (FAX)
pschweitzer@usgs.gov
Metadata standard:
Content Standard for Digital Geospatial Metadata (FGDC-STD-001-1998)

This page is <https://geo-nsdi.er.usgs.gov/metadata/open-file/00-409/metadata.faq.html>
Generated by mp version 2.9.48 on Tue Jul 03 20:05:26 2018