Geologic Map and Digital Database of the House Rock Spring Quadrangle, Coconino County, Northern Arizona

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

Frequently anticipated questions:


What does this data set describe?

Title:
Geologic Map and Digital Database of the House Rock Spring Quadrangle, Coconino County, Northern Arizona
Abstract:
This digital map database is compiled from unpublished data and new mapping by the authors, represents the general distribution of surficial and bedrock geology in the mapped area. Together with the accompanying pamphlet, it provides current information on the geologic structure and stratigraphy of the area. The database delineates map units that are identified by age and lithology following the stratigraphic nomenclature of the U.S. Geological Survey. The scale of the source maps limits the spatial resolution of the database to 1:24,000 or smaller.
Supplemental_Information:
This report consists of a set of geologic map database files (ARC/ INFO coverages) and supporting text and plot files. In addition, the report includes two sets of plot files(Post Script and PDF format) that will generate map sheets and pamphlets similar to a traditional USGS Miscellaneous Field Studies Report. These files are described in the explanatory pamphlets (hrsgeo.doc, hrsgeo. pdf, or hrsgeo.txt). The base layer used in the preparation of the geologic map plot files was derived from a Digital Raster Graphic version of a standard USGS 7.5' quadrangle. This raster image was converted to Grid format in ARC/INFO, trimmed and converted to a GeoTIFF image. The resultant TIFF image was combined with geologic data to produce the final map image in Illustrator 8.0.
  1. How might this data set be cited?
    Hampton, H.M., 2001, Geologic Map and Digital Database of the House Rock Spring Quadrangle, Coconino County, Northern Arizona: U.S. Geological Survey Miscellaneous Field Studies Map 2367, U.S. Geological Survey, Flagstaff, AZ.

    Online Links:

  2. What geographic area does the data set cover?
    West_Bounding_Coordinate: -112.12681823
    East_Bounding_Coordinate: -111.99838722
    North_Bounding_Coordinate: 36.87612474
    South_Bounding_Coordinate: 36.74888401
  3. What does it look like?
  4. Does the data set describe conditions during a particular time period?
    Calendar_Date: 2001
    Currentness_Reference:
    publication date
  5. What is the general form of this data set?
    Geospatial_Data_Presentation_Form: geologic 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 (742)
      • Complete chain (1516)
      • GT-Polygon composed of chains (544)
    2. What coordinate system is used to represent geographic features?
      Grid_Coordinate_System_Name: Universal Transverse Mercator
      Universal_Transverse_Mercator:
      UTM_Zone_Number: 12
      Transverse_Mercator:
      Scale_Factor_at_Central_Meridian: 0.9996
      Longitude_of_Central_Meridian: -105
      Latitude_of_Projection_Origin: 0.0
      False_Easting: 500000
      False_Northing: 0.0
      Planar coordinates are encoded using coordinate pair
      Abscissae (x-coordinates) are specified to the nearest 1
      Ordinates (y-coordinates) are specified to the nearest 1
      Planar coordinates are specified in meters
      The horizontal datum used is NAD27.
      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?
    HRSPOLY.PAT
    attribute table of HRSPOLY (Source: ARC/INFO)
    UNIT
    Geologic unit label (Source: author)
    ValueDefinition
    JnNavajo Sandstone
    JkKayenta Formation
    JmosMoenave Formation Springdale Sandstone member
    JmodMoenave Formation Dinosaur Canyon member
    PhHermit Formation
    PkfKaibab Formation Fossil Mountain member
    PkhKaibab Formation Harrisburg member
    PtbToroweap Formation Brady Canyon member
    PtsToroweap Formation Seligman member
    PtwToroweap Formation Woods Ranch member
    Qa1Young alluvial fan deposits
    Qa2Young intermediate age alluvial fan deposits
    Qa3Older intermediate age alluvial fan deposits
    Qa4Older alluvial fan deposits
    QafArtificial deposits
    QdSand-sheet and dune deposits
    Qg1Young terrace gravel deposits
    Qg2Intermediate terrace gravel deposits
    QlLandslide deposits
    QsStream-channel alluvium
    QtTalus deposits
    QvValley-fill deposits
    TrcoChinle Formation Owl Rock member
    TrcpChinle Formation Petrified Forest member
    TrcsChinle Formation Shinarump member
    TrmMoenkopi Formation
    PATTERN
    definition of graphical pattern fill for polygons (Source: ARC/INFO)
    ValueDefinition
    4breccia pattern fill used in conjunction with unit 'Ql'
    516red dot fill pattern used in conjunction with unit 'Qg2'
    518dense red dot fill pattern used in conjunction with unit 'Qa4'
    HRSPOLY.AAT
    Attribute table of HRSPOLY (Source: ARC/INFO)
    LINETYPE
    Type of geologic or geographic feature denoted by a line in the database. (Source: author)
    ValueDefinition
    CONTACTBoundary between two mapped units that retains the original depositional or intrusive relationship. The contact has been observed or is closely constrained, so it is well located as described in Positional_Accuracy.
    NORMAL HIGH ANGLE INFERRED FAULTStructural boundary between mapped units or structural discontinuity within a mapped unit that has experienced relative offset between the rock boundaries on either side of the fault. The contact has not been observed, so it is not well-located as described in Positional_Accuracy, but the location is constrained to be within 2 mm at map scale or within about 63 meters on the ground.
    NORMAL HIGH ANGLE FAULTStructural boundary between mapped units or structural discontinuity within a mapped unit that has experienced relative offset between the rock bodies on either side of the fault. The fault has been observed or is closely constrained, so it is well located as described in Positional_Accuracy.
    NORMAL HIGH ANGLE CONCEALED FAULTStructural boundary between mapped units or structural discontinuity within a mapped unit that has experienced relative offset between the rock bodies on either side of the fault. The fault is obscured by overlying mapped units, so it is not well-located as described in Positional_Accuracy, but the location is constrained to be within 3 mm at mapscale or within about 95 meters on the ground
    MAP BOUNDARYEdge of the mapped area. Used primarily to bound polygons at the edge of the map database. The location of the boundary is well located as described in positional_accuracy.
    NAME
    Feature name for annotation (Source: author)
    POINTTYPE
    arc marker point type (Source: author)
    ValueDefinition
    bar and ballArcmarker attached to an arc describing the nature of displacement along a fault. Side of arc with bar and ball is the side with downthrown displacement.
    noneno arcmarker attached to arc
    HRSFOLD.AAT
    Attribute table of HRSFOLD (Source: ARC/INFO)
    LINETYPE
    Type of geologic or geographic feature denoted by a line in the database. (Source: author)
    ValueDefinition
    ANTICLINEThe surface trace of the axis of an anticline. The axis cannot been observed, but the location is constrained to be within about 5 mm at map scale or within about 160 meters on the ground.
    CONCEALED ANTICLINEThe surface trace of the axis of an anticline. The axis cannot been observed, but the location is constrained to be within about 5 mm at map scale or within about 160 meters on the ground. The axis is concealed by younger units unaffected by earlier folding.
    MONOCLINEThe surface trace of the axis of a monocline. The axis cannot been observed, but the location is constrained to be within about 5 mm at map scale or within about 160 meters on the ground.
    CONCEALED MONOCLINEThe surface trace of the axis of a monocline. The axis cannot been observed, but the location is constrained to be within about 5 mm at map scale or within about 160 meters on the ground. The axis is concealed by younger units unaffected by earlier folding.
    SYNCLINEThe surface trace of the axis of a syncline. The axis cannot been observed, but the location is constrained to be within about 5 mm at map scale or within about 160 meters on the ground.
    PLUNGING ANTICLINEThe surface trace of the axis of a plunging anticline. The axis cannot been observed, but the location is constrained to be within about 5 mm at map scale or within about 160 meters on the ground.
    POINTTYPE
    Arc marker point type (Source: author)
    ValueDefinition
    anticlinePoint element placed on line indicating the anticlinal nature of the particular fold axis. Defined only in conjunction with an LINETYPE of ANTICLINE or CONCEALED ANTICLINE
    monoclinePoint element placed on line indicating the monoclinal nature of the particular fold axis. Defined only in conjunction with an LINETYPE of MONOCLINE or CONCEALED MONOCLINE
    synclinePoint element placed on line indicating the synclinal nature of the particular fold axis. Defined only in conjunction with an LINETYPE of SYNCLINE.
    HRSPOINT.PAT
    Attribute table of HRSPOINT (Source: ARC/INFO)
    POINTTYPE
    The type of planar feature which was observed and the orientation of which was measured at this point. (Source: author)
    ValueDefinition
    beddingOriginally horizontal sedimentary layers were observed and measured at this point.
    probable breccia pipe (C)Location where a circular collapse structure characterized by strata dipping inward toward central point was observed. May reflect collapse of a deep-seated breccia pipe.
    sinkholeObserved location of an enclosed depression or cave
    vertical jointThe orientation of vertical rock fractures without displacement was measured at this point.
    DIP
    The inclination of planar structures measured in degrees down from horizontal. (Source: author)
    Range of values
    Minimum:0
    Maximum:90
    Units:degrees
    Resolution:1
    STRIKE
    The orientation of a horizontal line in an inclined planar structure measured in degrees clockwise from north. (Source: author)
    Range of values
    Minimum:0
    Maximum:359
    Units:degrees
    Resolution:1
    NAME
    Name of geographic point feature, used only if necessary (Source: author)
    Entity_and_Attribute_Overview:
    The databases described in this report were compiled in ARC/INFO, a commercial Geographic Information System by Environmental Systems Research Institute. Almost all the attributes in the various attribute tables of the coverages included in the report are set or calculated by ARC/INFO. The exceptions being <COVER>-ID, LINETYPE, UNIT, POINTTYPE, STRIKE, and DIP. LINETYPE, UNIT and POINTTYPE are author added aspects of the coverages added to the PAT or AAT and are used to describe the type of line(LINETYPE), area (UNIT), point or arcmarker (POINTTYPE). LINETYPE and POINTTYPE are each defined with WIDTH 35, OUTPUT 35, and TYPE C (character). UNIT is defined with WIDTH 5, OUTPUT 5, and TYPE C. STRIKE and DIP are only present in HRSPOINT.PAT, because they describe bedding orientation of point objects. Each is defined with WIDTH and OUTPUT of 3,and TYPE I (integer).
    Entity_and_Attribute_Detail_Citation:
    This report combined with hrsmap.eps, hrsmap.pdf, hrsgeo.doc, hrsgeo.txt or hrsgeo.pdf

Who produced the data set?

  1. Who are the originators of the data set? (may include formal authors, digital compilers, and editors)
    • Hampton, H.M.
  2. Who also contributed to the data set?
    Thank you to Debra Block for her digital review.
  3. To whom should users address questions about the data?
    Hampton, Haydee M
    Northern Arizona University
    NAU Box 5694
    Flagstaff, Arizona
    USA


Why was the data set created?

The digital map database, compiled from previously published and unpublished data, and new mapping by the authors, represents the general distribution of bedrock and surficial deposits in the House Rock Spring area. Together with the accompanying text, it provides current information on the geologic structure and stratigraphy of the area covered. The database delineates map units that are identified by general age, lithology, and geomorphology following the spatial resolution (scale) of the database to 1:24,000. The content and character of the database, as well as three methods of obtaining the database, are described below.

How was the data set created?

  1. From what previous works were the data drawn?
  2. How were the data generated, processed, and modified?
    Date: 11-May-2001 (process 1 of 2)
    Stable-base maps of geologic features were scanned at the Flagstaff USGS Field site using the Optronics 5040 raster scanner at a resolution of 50 microns (508 dpi). The resulting raster file was in RLE format and converted to the RLC format using the "rle2rlc" program adapted by Marilyn Flynn. A tic file was created in lat/long and projected to UTM zone 12. Tics were defined in a 2.5 minute grid of latitude and longitude. The RLC file was converted to an ARC/INFO Grid in ARC/INFO and projected to UTM zone 12 using a first order polynomial transformation to the UTM tic marks. The base map image was prepared from a DRG obtained online from the ARIA image archive website. The raster image was registered using a world file and imported into ARC/INFO where it was then converted to a grid. Area colors where drained from the file, resulting in a three-color image in ARC/INFO. No elements of the base layer are attributed and the base map is provided solely for reference.
    Date: 11-May-2001 (process 2 of 2)
    Creation of original metadata record Person who carried out this activity:
    Hampton, Haydee M
    Northern Arizona University
    NAU Box 5694
    Flagstaff, AZ
    USA

    (520) 523-0872 (voice)
    haydee.hampton@nau.edu
  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?
  2. How accurate are the geographic locations?
    Well located data are intended to have a positional accuracy within .5 mm at a 1:24,000 map scale, or better than 12 meters on the ground
  3. How accurate are the heights or depths?
  4. Where are the gaps in the data? What is missing?
    This report is designed to describe completely the surficial and bedrock geology at a 1:24,000 scale. Geologic information only mappable at a larger scale has been omitted.
  5. How consistent are the relationships among the observations, including topology?
    Polygon and chain-node topology present

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:
Uses of this digital geologic map should not violate the spatial resolution of the map area (1:24,000) even though the digital data form removes the constraint of scale on a paper map. The accuracy inherent in map scale are also present in digital format. At a scale larger than 1:24,000, higher resolution data is not available and will not yield greater real detail.
  1. Who distributes the data set? (Distributor 1 of 1)
    U.S. Geological Survey Information Services
    Box 25248, Denver Federal Center
    Denver, CO
    USA

    1-888-ASK-USGS (voice)
    1-303-202-4693 (FAX)
  2. What's the catalog number I need to order this data set? USGS MF-2367
  3. What legal disclaimers am I supposed to read?
    Any use of trade, product of firm names is for descriptive purposes only and does not imply endorsement by the U.S. Government. Although this publication has been subjected to rigorous review and is substantially complete, the USGS reserves the right to revise the data pursuant to further analysis and review. Furthermore, it is released on condition that neither the USGS nor the United States Government may be held liable for any damages resulting from its authorized or unauthorized use.
  4. How can I download or order the data?

Who wrote the metadata?

Dates:
Last modified: 10-Jun-2016
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/map-mf/2367/metadata.faq.html>
Generated by mp version 2.9.48 on Tue Jul 03 20:05:08 2018