Geologic Map and Digital Database of Hidden Hills and Vicinity, Mohave County, Northwestern 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 Hidden Hills and Vicinity, Mohave County, Northwestern Arizona
Abstract:
This digital map database is compiled from unpublished data and new mapping by the authors and 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:31,680 or smaller.
  1. How might this data set be cited?
    Billingsley, George H., Wellmeyer, Jessica L., Harr, Michelle L., and Priest, Susan S., 2002, Geologic Map and Digital Database of Hidden Hills and Vicinity, Mohave County, Northwestern Arizona: U.S. Geological Survey Miscellaneous Field Studies Map MF-2387, U.S. Geological Survey, Flagstaff, AZ.

    Online Links:

  2. What geographic area does the data set cover?
    West_Bounding_Coordinate: -113.75882397
    East_Bounding_Coordinate: -113.49201066
    North_Bounding_Coordinate: 36.50550062
    South_Bounding_Coordinate: 36.2445389
  3. What does it look like?
    http://pubs.usgs.gov/mf/2002/2387/images/hhmap.gif (GIF)
    Reduced-size image of the map sheet, 360x590 pixels, 85k bytes.
    http://pubs.usgs.gov/mf/2002/2387/hhmap.pdf (PDF)
    Printable version of the map sheet, 6.8 megabytes
  4. Does the data set describe conditions during a particular time period?
    Calendar_Date: 2002
    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 (3060)
      • Complete chain (8391)
      • GT-Polygon composed of chains (2591)
    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: -111
      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 Unknown.
      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?
    HH_POLY.PAT
    attribute table of HH_POLY
    PTYPE
    Geologic unit label
    ValueDefinition
    PeEsplanade Sandstone
    PhHermit Formation
    PkfKaibab Formation, Fossil Mountain member
    PkhKaibab Formation, Harrisburg member
    PklPakoon Limestone
    PsSupai Group, undivided
    PtbToroweap Formation, Brady Canyon member
    PtsToroweap Formation, Seligman member
    PtwToroweap Formation, Woods Ranch member
    Qa1Young alluvial fan deposits
    Qa2Young intermediate age alluvial fan deposits
    Qa3Old intermediate age alluvial fan deposits
    Qa4Old alluvial fan deposits
    Qa5Oldest alluvial fan deposits
    QafArtificial deposits
    QcColluvial deposits
    QfFloodplain or ponded deposits
    Qg1Young terrace gravel deposits
    Qg2Young intermediate terrace gravel deposits
    Qg3Old intermediate terrace gravel deposits
    Qg4Old terrace gravel deposits
    QlLandslide deposits
    QsStream-channel alluvium
    QtTalus deposits
    QvValley-fill deposits
    QTaTertiary and Quaternary alluvium
    TiPigeon Canyon, Intrusive dikes
    TpbShivwits Plateau, Basalt flows
    TpiShivwits Plateau, Intrusive rocks
    TppShivwits Plateau, Pyroclastic deposts
    TsbPoverty Mountain, Basalt flows
    TsiPoverty Mountain, Intrusive dike
    TspPoverty Mountain, Pyroclastic deposits
    TRmlMoenkopi Formation, Lower red member
    TRmmMoenkopi Formation, Middle red member
    TRmsMoenkopi Formation, Shnabkaib Member
    TRmtMoenkopi Formation, Timpoweap Member
    TRmvMoenkopi Formation, Virgin Limestone Member
    xxPlaceholder for non-geologic feature
    hh_poly.aat
    Arc attribute table of coverage
    LTYPE
    Type of geologic or geographic feature denoted by a line in the database.
    ValueDefinition
    contact_approxBoundary between two mapped units that retains the original depositional or intrusive relationship. The contact is approximate, so it is not as well located as described in Positional_Accuracy.
    contact_certainBoundary 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.
    high_angle_flt_approxStructural 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 not well located as described in Positional_Accuracy.
    high_angle_flt_certainStructural 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.
    high_angle_flt_concealedStructural 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.
    landslide_scarpLine demarcating the headwall of a landslide, also serving as a contact between a landslide unit (Ql) and the adjacent lithologic unit. This feature has been well-located as described in Positional_Accuracy.
    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.
    PTTYPE
    arc marker point type
    ValueDefinition
    fault_ball_fillArcmarker 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.
    xxNo arcmarker is to be attached to an arc containing the xx value in the PTTYPE field.
    hh_fold.aat
    Arc attribute table of coverage
    LTYPE
    Type of geologic or geographic feature denoted by a line in the database.
    ValueDefinition
    anticline_certain_redThe surface trace of the axis of an anticline. The axis has not been observed, but the location is constrained to be within about 3 mm at map scale or within about 72 meters on the ground.
    anticline_concealed_redThe surface trace of the axis of an anticline. The axis has not been observed, but the location is constrained to be within about 3 mm at map scale or within about 72 meters on the ground. The axis is concealed by younger units unaffected by earlier folding.
    basalt_flow_directionInterpreted direction of flow as seen in a basalt flow unit. Arrowhead points in direction of flow.
    monocline_certain_redThe surface trace of the axis of a monocline. The axis has not been observed, but the location is constrained to be within about 3 mm at map scale or within about 72 meters on the ground.
    plunging_anticline_redThe surface trace of the axis of a plunging anticline. The axis has not 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_syncline_redThe surface trace of the axis of a plunging syncline. The axis has not been observed, but the location is constrained to be within about 5 mm at map scale or within about 160 meters on the ground.
    syncline_certain_redThe surface trace of the axis of a syncline. The axis has not been observed, but the location is constrained to be within about 3 mm at map scale or within about 72 meters on the ground.
    syncline_concealed_redThe surface trace of the axis of a syncline. The axis has not been observed, but the location is constrained to be within about 3 mm at map scale or within about 72 meters on the ground. The axis is concealed by younger units unaffected by earlier folding.
    PTTYPE
    Arc marker point type
    ValueDefinition
    anticline_redPoint element placed on line indicating the anticlinal nature of the particular fold axis. Defined only in conjunction with an LTYPE of anticline_certain.
    monocline_redPoint element placed on line indicating the monoclinal nature of the particular fold axis. Defined only in conjunction with an LTYPE of monocline_concealed or monocline_certain.
    syncline_redPoint element placed on line indicating the synclinal nature of the particular fold axis. Defined only in conjunction with an LTYPE of syncline_certain or syncline_concealed.
    xxNo point element is to be placed on an arc with PTTYPE defined as xx.
    hh_dip.pat
    Attribute table of HH_DIP
    PTTYPE
    The type of planar feature which was observed and the orientation of which was measured at this point.
    ValueDefinition
    beddingOriginally horizontal sedimentary layers were observed and measured at this point.
    collapse_structureA probable breccia pipe collapse structure was observed at this location.
    sinkholeObserved location of an enclosed depression or cave.
    vertical_jointThe orientation of vertical rock fractures without displacement was measured at this point.
    volcanic_ventObserved location of a volcanic vent or cinder cone center.
    DIP
    The inclination of planar structures measured in degrees down from horizontal.
    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.
    Range of values
    Minimum:0
    Maximum:359
    Units:degrees
    Resolution:1
    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, LTYPE, PTYPE, PTTYPE, PATTERN, STRIKE, and DIP. LTYPE, PTYPE and PTTYPE are author added aspects of the coverages added to the PAT or AAT and are used to describe the type of line (LTYPE), area (PTYPE), point or arcmarker (PTTYPE). LTYPE and PTTYPE are each defined with WIDTH 35, OUTPUT 35, and TYPE C (character). PTYPE is defined with WIDTH 5, OUTPUT 5, and TYPE C. STRIKE and DIP are only present in HH_DIP.PAT, because they describe bedding orientation of point objects. Each is defined with WIDTH and OUTPUT of 3, and TYPE I (integer). PATTERN was another author- added attribute only in HR_POLY.PAT, and is defined by WIDTH 3, OUTPUT 3, and TYPE I. One coverage not described is HH_ANNO. This coverage contains only annotations, and leader placement. There are no defined attributes for this coverage.
    Entity_and_Attribute_Detail_Citation: http://pubs.usgs.gov/mf/2002/2387/hhgeo.pdf

Who produced the data set?

  1. Who are the originators of the data set? (may include formal authors, digital compilers, and editors)
    • Billingsley, George H.
    • Wellmeyer, Jessica L.
    • Harr, Michelle L.
    • Priest, Susan S.
  2. Who also contributed to the data set?
    This digital database was prepared by Jessica Wellmeyer, Michelle Harr, and Sue Priest at the U.S. Geological Survey.
  3. To whom should users address questions about the data?
    U.S. Geological Survey
    Attn: George H. Billingsley
    Geologist
    2255 N. Gemini Drive
    Flagstaff, AZ
    USA

    928-556-7198 (voice)
    928-556-7169 (FAX)
    gbillingsley@usgs.gov

Why was the data set created?

The geologic map of Hidden Hills and vicinity covers part of the Arizona Strip north of Grand Canyon and several large tributary canyons that make up the western part of Arizona's Grand Canyon. The map is part of a cooperative U.S. Geological Survey, National Park Service, and Bureau of Land Management project to provide geologic information for areas within the newly established Grand Canyon-Parashant National Monument. This map fills in one of the remaining areas where uniform quality geologic mapping was needed. The geologic information will be useful for future resource management studies for federal, state, and private agencies.

How was the data set created?

  1. From what previous works were the data drawn?
  2. How were the data generated, processed, and modified?
    (process 1 of 2)
    The databases in this report were compiled in ARC/INFO version 7.1.2, a commercial Geographic Information System (Environmental Systems Research Institute, Redlands, CA). The files are in either raster (GRID) or vector (coverage) format. Coverages are stored in uncompressed ARC export format. ARC/INFO export files with the .e00 extension can be converted into ARC/INFO coverages in ARC/INFO and can be read by other commercially available Geographic Information Systems. Stable- base maps were scanned at the Flagstaff USGS Field site using an 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 written by Marilyn Flynn. The RLC file was subsequently converted to an ARC/INFO Grid in ARC/INFO. The linework was vectorized using Gridline. A tic file was created in latitude and longitude and projected into the base map projection (Transverse Mercator) using a central meridian of -112.375. Tics are defined in the four extreme corners of the map are in the geologic coverages corresponding with quadrangle corners both in base maps and digital maps. The tic file was used to transform the grid into Universal Transverse Mercator projection. ARC/INFO generated an RMS (root mean square) report after transforming the original Grid (raster image) into UTM. Scanned lines were edited interactively by hand using the ARC module ARCEDIT and a series of macros and menus, polygon regions were attributed as necessary, and all artifacts and scanning errors visible at 1:24,000 were removed.
    Date: Apr-2002 (process 2 of 2)
    Creation of original metadata record Person who carried out this activity:
    U.S. Geological Survey
    Attn: Susan S. Priest
    Geologist
    2255 N. Gemini Dr.
    Flagstaff, AZ
    USA

    928-556-7148 (voice)
    928-556-7169 (FAX)
    spriest@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?
    This report has undergone two scientific peer reviews, one digital database review, one review for conformity with geologic names policy, and review of the plotfiles for conformity with USGS map standards.
  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 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:31,680 scale. Geologic information only mappable at a larger scale has been omitted. All geospatial database elements are attributed.
  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:31,680) even though the digital data form removes the constraint of scale on a paper map. The accuracy inherent in map scale is also present in digital format. At a scale larger than 1:31,680, higher resolution data is not available and will not yield greater real detail.
Any hardcopies utilizing these datasets shall clearly indicate their source. If users modify the data in any way they are obligated to describe the types of modifications they have performed. User 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
    USA

    1-888-ASK-USGS (voice)
    303-202-4693 (FAX)
    ask@usgs.gov
  2. What's the catalog number I need to order this data set?
  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 delivery, installation, operation, or support by USGS.
  4. How can I download or order the data?
    • Availability in digital form:
      Data format: Geologic units and structural features, with scanned topographic contour map image, symbols, shades, and markers used to produce the printed map in format ARCE (version 8.1) Size: 23
      Network links: http://pubs.usgs.gov/mf/2002/2387/hhdb.zip
    • Cost to order the data: none


Who wrote the metadata?

Dates:
Last modified: 13-Jun-2016
Last Reviewed: 09-Jul-2002
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/2387/metadata.faq.html>
Generated by mp version 2.9.48 on Tue Jul 03 20:05:13 2018