Spatial Digital Database of the Geologic Map of Catalina Core Complex and San Pedro Trough, Pima, Pinal, Gila, Graham, and Cochise Counties, Arizona

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

Frequently anticipated questions:

What does this data set describe?

Spatial Digital Database of the Geologic Map of Catalina Core Complex and San Pedro Trough, Pima, Pinal, Gila, Graham, and Cochise Counties, Arizona
A paper copy of the Geologic Map of the Catalina Core Complex and San Pedro Trough (Dickinson, 1992) was scanned and digitized by U.S. Geological Survey staff and contractors at the Southwest Field Office (Tucson, AZ) in 2000-2001 for input into an ArcInfo geographic information system (GIS). The resulting geologic map database (in ArcInfo format) can be queried in many ways to produce a variety of geologic maps. Digital base map data files. (topography, roadways, towns, and hydrography) are not included: they may be obtained from a variety of commercial and government sources. Geologic map graphics and plot files that are provided in the Open-File Report are representations of the digital database and are not designed to be cartographic products.
This database consists of two major ArcInfo datasets. The CCC125K dataset contains arc features representing geologic contacts, faults, and folds; polygon features representing geologic rock (map) units; and regions representing allochthons. The CCCPNT dataset contains point features representing geologic point data of bedding, foliation, and fault attitude.
The datasets and related INFO look-up tables have been "exported" into ArcInfo interchange files with a .e00 file extension and will need to be imported for use. Lower case letters are consistently used in naming datasets and other files although they may be listed in uppercase letters for emphasis in this document and the Open-File Report it accompanies.
  1. How might this data set be cited?
    Dickinson, William R., Hirschberg, Douglas M., Pitts, G. Stephen, and Bolm, Karen S., 2001, Spatial Digital Database of the Geologic Map of Catalina Core Complex and San Pedro Trough, Pima, Pinal, Gila, Graham, and Cochise Counties, Arizona: U.S. Geological Survey Open-File Report 02-365, U.S. Geological Survey, Menlo Park, California.

    Online Links:

  2. What geographic area does the data set cover?
    West_Bounding_Coordinate: -111.2
    East_Bounding_Coordinate: -110.1
    North_Bounding_Coordinate: 33.1
    South_Bounding_Coordinate: 31.9
  3. What does it look like? (PDF)
    Printable version of the map, 6.5 megabytes
  4. Does the data set describe conditions during a particular time period?
    Calendar_Date: 2002
    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?
    2. What coordinate system is used to represent geographic features?
      Grid_Coordinate_System_Name: Universal Transverse Mercator
      UTM_Zone_Number: 12
      Scale_Factor_at_Central_Meridian: 0.9996
      Longitude_of_Central_Meridian: -111.0
      Latitude_of_Projection_Origin: 0.0
      False_Easting: 500000.0
      False_Northing: 0.0
      Planar coordinates are encoded using coordinate pair
      Abscissae (x-coordinates) are specified to the nearest 0.000256
      Ordinates (y-coordinates) are specified to the nearest 0.000256
      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.978698.
  7. How does the data set describe geographic features?
    The Catalina Core Complex and San Pedro Trough 125k GIS includes a geologic arc attribute table, CCC125K.AAT, that relates to the CCC125K.CON (contact look-up table), CCC125K.ST2 (structure look-up table), and CCC125K.REF (source reference look-up table) files; a rock-unit polygon attribute table (CCC125K.PAT) that relates to the CCC125K.RU (rock-unit look-up table) and CCC125K.REF (source reference lookup table) files; an allochthon region attribute table, (CCC125K.PATALLOCH) that relates to the CCC125K.REF (source reference lookup table) file; and a point attribute table, CCCPNT.PAT, that relates to the CCCPNT.REF (source reference look-up table) file.

Who produced the data set?

  1. Who are the originators of the data set? (may include formal authors, digital compilers, and editors)
    • William R. Dickinson
    • Douglas M. Hirschberg
    • G. Stephen Pitts
    • Karen S. Bolm
  2. Who also contributed to the data set?
    D.M. Hirschberg (contractor), G.S. Pitts (contractor), and K.S. Bolm (USGS), scanned Dickinson's (1992) geologic map; registered the resulting image; digitized the arcs and points; captured and positioned the annotation, attributed the arcs, polygons, and points; defined and populated the look-up tables; prepared the data model; wrote the metadata; and produced the Open-File Report text. See the Process_Step sections for more details on these steps.
  3. To whom should users address questions about the data?
    Mark Gettings
    U.S. Geological Survey
    USGS Geologic Division
    DeConcini Environmental and Natural Resources Bldg.
    520 North Park Ave., Room 357
    University of Arizona
    Tucson, AZ

    520-670-5507 (voice)
    520-670-5571 (FAX)

Why was the data set created?

This database was constructed to provide a geologic map GIS for use in spatial analysis by a variety of users. The digital geologic database can be queried in many ways to produce a variety of derivative geologic maps. The data are not meant to be used at any scale larger than 1:125,000 (for example, 1:100,000 or 1:24,000)

How was the data set created?

  1. From what previous works were the data drawn?
    Dickinson (1992) (source 1 of 1)
    Dickinson, W.R., 1992, Geologic map of Catalina Core Complex and San Pedro Trough: Contributed Map CM-92-C, Arizona Geological Survey, Tucson, AZ.

    Type_of_Source_Media: paper
    Source_Scale_Denominator: 125,000
    geologic features; contacts, faults, folds, point observations, and rock units.
  2. How were the data generated, processed, and modified?
    Date: 2000 (process 1 of 14)
    A paper copy of the geologic map (Dickinson, 1992) map was obtained and scanned at 300 dpi to create an 8-bit grayscale TIFF. The TIFF was registered to an ArcInfo coverage (dataset) of tics which had been mathematically generated in ArcInfo then projected to the Universal Transverse Mercator (UTM) projection.
    Date: 2000 (process 2 of 14)
    A dataset (CCC125K) with arc and polygon topology was created from the same mathematically generated and projected set of tics. Items (fields) were added to its arc attribute table (.aat) and polygon attribute table (.pat) as needed.
    Date: 2000 (process 3 of 14)
    Arcs were digitized and attributed on-screen in a 'heads-up' fashion with the image of the geologic map (Dickinson, 1992) as background. Each arc was attributed as soon as it was digitized. Attribute selections were entered via an on-screen menu for quality control purposes.
    Date: 2000 (process 4 of 14)
    Check plots on mylar were produced for each sector. First, generic line symbols were used to proof the locational fidelity of the linework to Dickinson (1992). Later, check plots with symbolized lines were produced to check for attributional fidelity to the source map. Updates to the CCC125K dataset were made as needed.
    Date: 2000 (process 5 of 14)
    Polygon topology was re-built. Polygons were attributed in the 'heads-up' fashion mentioned previously.
    Date: 2000 (process 6 of 14)
    Check plots were produced to proof for polygon attributional fidelity to Dickinson (1992). Polygons were edited as needed.
    Date: 2000 (process 7 of 14)
    An ArcInfo dataset (CCCPNT) with point topology was created. Items were added to the dataset's point attribute table (.pat) as needed.
    Date: 2000 (process 8 of 14)
    Points were digitized and attributed in the same 'heads-up' fashion. Check plots were produced to proof locational, rotational, and other attributional qualities of the points.
    Date: 2000 (process 9 of 14)
    Look-up tables for the CCC125K and CCCPNT datasets were defined and populated.
    Date: 2001 (process 10 of 14)
    Rock unit annotation was captured for the CCC125K dataset and annotation strings were repositioned as needed. Dip values were captured for the necessary points in the CCCPNT dataset and repositioned as needed.
    Date: 2001 (process 11 of 14)
    Arcs representing "plated" faults on the source map were re-coded as thrust faults (linecode = 171 or linecode = 173) in the arc attribute table (CCC125K.AAT). (Descriptions for the linecodes are given in the CCC125K.ST2 look-up table; however, for archival purposes, Dickinson's (1992) original line descriptions are given in the ORIG_DESC item in the CCC125K.AAT file.)
    Date: 21-Feb-2001 (process 12 of 14)
    First draft of metadata created by D.M. Hirschberg using FGDCMETA.AML ver. 1.2 05/14/98
    Date: 2002 (process 13 of 14)
    Polygons designated by Mark Gettings, U. S. Geological Survey were grouped into regions and each region was attributed with the allochthon name according to Dickinson (1992).
    Date: 26-Aug-2003 (process 14 of 14)
    Creation of original metadata record Person who carried out this activity:
    U.S. Geological Survey
    Attn: Douglas Hirschberg
    GIS Specialist
    520 N. Park Ave, Suite 355
    Tucson, AZ

    (520) 670-5514 (voice)
    (520) 670-5571 (FAX)
  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?
    Attribute accuracy was verified by manual comparison of Dickinson's (1992) map with hard copy printouts.
  2. How accurate are the geographic locations?
    The horizontal positional accuracy is probably no better than +/- 100 meters.
    The base for Dickinson's (1992) map is believed to be two U. S. Geological Survey 1:250,000 scale sheets spliced at the 32nd degree parallel and enlarged in scale to 1:125,000. Inaccuracies in the digital data would include inherent errors in Dickinson's (1992) map.
  3. How accurate are the heights or depths?
  4. Where are the gaps in the data? What is missing?
    None of the base map data (roads, washes, etc.) from Dickinson's (1992) map were digitized nor are represented in this database.
  5. How consistent are the relationships among the observations, including topology?
    All lines and points on the source map representing geologic features were digitized as arcs (line segments) or points. These features were digitized once. Lines intersect only where intended. Overshoots (dangling arcs) and undershoots are present as represented in Dickinson's (1992) map. 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.
    Polygon and chain-node topology present. All polygons have a label. All polygons close. 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. Point data are represented by two sets of coordinate pairs, each with the same coordinate values. All nodes are represented by a single coordinate pair which indicates the beginning or end of a line segment.

How can someone get a copy of the data set?

Are there legal restrictions on access or use of the data?
Access_Constraints: none
This digital database is not meant to be used or displayed at any scale larger than 1:125,000 (for example, 1:100,000 or 1:24,000). Any hardcopies utilizing these datasets shall clearly indicate their source. If users modify the data in any way they are obligated to describe on the hardcopy map the types of modifications they have performed. Users specifically agrees not to misrepresent these datasets, 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)
    USGS Information Services
    Box 25286 Denver Federal Center
    Denver, CO

    1-888-ASK-USGS (voice)
    303-202-4693 (FAX)
  2. What's the catalog number I need to order this data set? USGS Open-File Report 02-365
  3. What legal disclaimers am I supposed to read?
    The U.S. Geological Survey (USGS) provides these geograpic 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 spatial digital database for the geologic map of Catalina Core Complex and San Pedro Trough is not meant to be used or displayed at any scale larger than 1:125,000 (for example, 1:100,000 or 1:24,000).
  4. How can I download or order the data?

Who wrote the metadata?

Last modified: 10-Jun-2016
Metadata author:
Peter N Schweitzer
USGS Midwest Area
Collection manager, USGS Geoscience Data Clearinghouse,
Mail Stop 954
12201 Sunrise Valley Dr
Reston, VA

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

This page is <>
Generated by mp version 2.9.48 on Tue Jul 03 20:06:09 2018