Geologic Map of Upper Clayhole Valley 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 of Upper Clayhole Valley 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., and Priest, Susan S., 2003, Geologic Map of Upper Clayhole Valley and Vicinity, Mohave County, Northwestern Arizona: U.S. Geological Survey Miscellaneous Field Studies Map MF-2418, U.S. Geological Survey, Flagstaff, Arizona.

    Online Links:

  2. What geographic area does the data set cover?
    West_Bounding_Coordinate: -113.25727737
    East_Bounding_Coordinate: -112.993552
    North_Bounding_Coordinate: 36.75446479
    South_Bounding_Coordinate: 36.49554749
  3. What does it look like?
    http://pubs.usgs.gov/mf/2003/2418/cvmap.gif (GIF)
    Reduced-size image of the entire map sheet, 450x490 pixels, 127k bytes
    http://pubs.usgs.gov/mf/2003/2418/cvmap.pdf (PDF)
    Printable representation of the map sheet, 12.3 megabytes
  4. Does the data set describe conditions during a particular time period?
    Calendar_Date: 2003
    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 (2204)
      • String (5933)
      • GT-polygon composed of chains (2204)
    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 3.1804656156
      Ordinates (y-coordinates) are specified to the nearest 3.1804656156
      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 Geologic Map of Upper Clayhole Valley and Vicinity, Mohave County, Northwestern Arizona includes four geospatial datasets as ARC/INFO coverages: cv_poly (geology), cv_fold (folds, basalt flow lines), cv_dip (point data including strike and dip, collapse features, sinkholes, and volcanic vents), and cv_anno (annotation and geologic unit labels). Geospatial entities in ARC/INFO coverages have the following software-defined attributes: <cover>.pat contains AREA, PERIMETER, COVER#, and COVER-ID; <cover>.aat contains FNODE#, TNODE#, LPOLY#, RPOLY#, LENGTH, COVER#, and COVER-ID. User-defined attributes are described in detail below.
    (1) The coverage cv_poly includes the following feature attribute tables: (a) a polygon feature attribute table (cv_poly.pat) that describes the geospatial distribution of surficial units represented in the Postscript (.eps) and Portable Document Format (.pdf) plotfiles of the map. (b) an arc feature attribute table (cv_poly.aat) that describes the contacts and linear features that bound rock-unit polygons. For display purposes, the cv_poly coverage includes an annotation class which contains line types and arcmarker symbols derived from the coded items LTYPE and PTTYPE respectively.
    (2) The coverage cv_fold includes an arc feature attribute table (cv_fold.aat) that describes linear features (folds and basalt flow lines). For display purposes, the cv_fold coverage includes an annotation class which contains line types and arcmarker symbols derived from the coded items LTYPE and PTTYPE respectively. Arrowheads indicating plunging folds are drawn based on values in the coded item PLUNGE.
    (3) The coverage cv_dip includes the following: (a) a point feature attribute table (cv_dip.pat) that describes the position of point data including strike and dips, collapse features, sinkholes, and volcanic vents. Symbols are derived from the item PTTYPE, dip angle in degrees is derived from item DIP, and strike angle in degrees is in item STRIKE. (b) cv_dip also contains annotation for dip values.
    (4) The coverage cv_anno, containing subclass anno.unit, is used to annotate geologic unit labels and fault offsets. The unit labels are derived from the coded item PTYPE in the coverage cv_poly.
    Entity_and_Attribute_Detail_Citation: http://pubs.usgs.gov/mf/2003/2418/cvgeo.pdf
    CV_POLY.PAT
    Polygon attribute table of coverage
    PTYPE
    Geologic map unit label. Plain text is substituted for conventional geologic age symbols (TR for Triassic) shown on map.
    ValueDefinition
    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
    Qa2Older alluvial fan deposits
    QabAntelope Knoll Basalt, basalt flows
    QafArtificial fill and quarries
    QapAntelope Knoll Basalt, pyroclastic deposits
    Qb1Quaternary basalts, undivided, basalt flows
    QcColluvial deposits
    QcbbBasalt of Craigs Knoll and Berry Knoll, basalt flows
    QcbiBasalt of Craigs Knoll and Berry Knoll, intrusive dike or neck
    QcbpBasalt of Craigs Knoll and Berry Knoll, pyroclastic deposits
    QfFloodplain deposits
    Qg1Young terrace-gravel deposits
    Qg2Intermediate-age terrace-gravel deposits
    Qg3Older terrace-gravel deposits
    QgrbBasalt of Graham Ranch, basalt flows
    QgriBasalt of Graham Ranch, intrusive plug or dike
    QgrpBasalt of Graham Ranch, pyroclastic deposits
    QhbBasalt of Hat knoll, basalt flows
    QhiBasalt of Hat knoll, intrusive dike or neck
    QhpBasalt of Hat knoll, pyroclastic deposits
    QiQuaternary basalts, undivided, basalt dike
    QlLandslide deposits
    QltbBasalt of Larimore Tank, basalt flows
    QltiBasalt of Larimore Tank, intrusive dike or neck
    QltpBasalt of Larimore Tank, pyroclastic deposits
    QmbBasalt of Moriah Knoll, basalt flows
    QmkbBasalt of Maryland Knoll, basalt flows
    QmkpBasalt of Maryland Knoll, pyroclastic deposits
    QmpBasalt of Moriah Knoll, pyroclastic deposits
    Qp1Quaternary basalts, undivided, pyroclastic deposits
    QsStream-channel alluvium
    QsbBasalt of Seven Knolls, basalt flows
    QsiBasalt of Seven Knolls, intrusive dike or neck
    QskbBasalt of Spencer Knoll, basalt flows
    QskpBasalt of Spencer Knoll, pyroclastic deposits
    QspBasalt of Seven Knolls, pyroclastic deposits
    QtTalus deposits
    QvValley-fill deposits
    TRmlMoenkopi Formation, lower red member
    TRmltMoenkopi Formation, lower red member and Timpoweap Member, undivided
    TRmmMoenkopi Formation, middle red member
    TRmsMoenkopi Formation, Shnabkaib Member
    TRmtMoenkopi Formation, Timpoweap Member
    TRmvMoenkopi Formation, Virgin Limestone Member
    CV_POLY.AAT
    Arc attribute table of coverage
    LTYPE
    Type of geologic or geographic feature denoted by a line in the database.
    ValueDefinition
    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.
    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_boundaryExtent of mapped area.
    normal_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.
    normal_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 not been observed, so it is not well located as described in Positional_Accuracy.
    normal_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 and it's trace is fairly apparent, so it is not well located as described in Positional_Accuracy.
    normal_flt_inferredStructural 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 and it's trace is uncertain, so it is not 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.
    CV_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 cannot be observed, but the location is constrained to be within about 5 mm at map scale or about 16 meters on the ground.
    anticline_concealed_redThe surface trace of the axis of an anticline. The axis cannot be observed, but the location is constrained to be within about 5 mm at map scale or about 16 meters on the ground. The axis is concealed by younger units but fairly apparent.
    basalt_flow_directionInterpreted direction of lava 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 cannot be observed, but the location is constrained to be within about 5 mm at map scale or about 16 meters on the ground.
    monocline_concealed_redThe surface trace of the axis of a monocline. The axis cannot be observed, but the location is constrained to be within about 5 mm at map scale or about 16 meters on the ground. The axis is concealed by younger units but fairly apparent.
    plunging_anticline_concealed_redThe surface trace of the axis of a plunging anticline. The axis cannot be observed, but the location is constrained to be within about 5 mm at map scale or about 16 meters on the ground. The axis is concealed by younger units but fairly apparent.
    plunging_anticline_redThe surface trace of the axis of a plunging anticline. The axis cannot be observed, but the location is constrained to be within about 5 mm at map scale or about 16 meters on the ground.
    plunging_syncline_concealed_redThe surface trace of the axis of a plunging syncline. The axis cannot be observed, but the location is constrained to be within about 5 mm at map scale or about 16 meters on the ground. The axis is concealed by younger units but fairly apparent.
    plunging_syncline_redThe surface trace of the axis of a plunging syncline. The axis cannot be observed, but the location is constrained to be within about 5 mm at map scale or about 16 meters on the ground.
    syncline_certain_redThe surface trace of the axis of a syncline. The axis cannot be observed, but the location is constrained to be within about 5 mm at map scale or about 16 meters on the ground.
    syncline_concealed_redThe surface trace of the axis of a syncline. The axis cannot be observed, but the location is constrained to be within about 5 mm at map scale or about 16 meters on the ground. The axis is concealed by younger units but fairly apparent.
    syncline_inferred_redThe surface trace of the axis of a syncline. The axis is obscured by overlying mapped units and it's trace is uncertain, but the location is constrained to be about 5 mm at map scale or within about 16 meters on the ground.
    PTTYPE
    Arc marker point type
    ValueDefinition
    anticline_redPoint element placed on line indicating the anticlinal nature of the particular fold axis.
    monocline_redPoint element placed on line indicating the monoclinal nature of the particular fold axis.
    syncline_redPoint element placed on line indicating the synclinal nature of the particular fold axis.
    xxNo arcmarker is to be attached to an arc containing the xx value in the PTTYPE field.
    CV_DIP.PAT
    Point attribute table of coverage
    PTTYPE
    The type of planar feature which was observed and the orientation of which was measured at this location.
    ValueDefinition
    beddingOriginally horizontal sedimentary layers were observed and measured at this location.
    approx_beddingOriginally horizontal sedimentary layers were observed and estimated at this location.
    collapse_structureLocation of a circular collapse structure characterized by strata dipping inward toward a central point was observed. May reflect collapse of a deep-seated breccia pipe.
    sinkholeObserved location of an enclosed depression or cave.
    vertical_jointOrientation of vertical rock fracture without displacement was measured at this location.
    volcanic_ventObserved location of volcanic vent.
    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

Who produced the data set?

  1. Who are the originators of the data set? (may include formal authors, digital compilers, and editors)
    • George H. Billingsley
    • Susan S. Priest
  2. Who also contributed to the data set?
    This digital database was prepared by Sue Priest. Technical review was provided by Wendell Duffield and Paul Stone of the U.S. Geological Survey. Digital review was provided by Debra Block of the U.S. Geological Survey.
    Prepared in cooperation with the National Park Service and the Bureau of Land Management.
  3. To whom should users address questions about the data?
    George H. Billingsley
    U.S. Geological Survey
    Geologist
    2255 N. Gemini Dr.
    Flagstaff, AZ
    USA

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

Why was the data set created?

The geologic map of Upper Clayhole Valley and vicinity covers part of the Arizona Strip north of 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 5)
    This map was produced using 1:24,000-scale 1976 infrared aerial photographs followed by extensive field checking. Volcanic rocks were mapped as separate units when identified on aerial photographs as mappable and distinctly separate units associated with one or more pyroclastic cones and flows. Many of the Quaternary alluvial deposits that have similar lithology but different geomorphic characteristics were mapped almost entirely by photogeologic methods. Stratigraphic position and amount of erosional degradation were used to determine relative ages of alluvial deposits having similar lithologies. Each map unit and structure was investigated in detail in the field to ensure accuracy of description.
    (process 2 of 5)
    Punch-registered mylar sheets were scanned at the Flagstaff Field Center on an Optronics 5040 raster scanner at a resolution of 50 microns (508 dpi). The scans were output in TIFF format and converted to ARC/INFO grids. The grids were registered and rectified to four latitude/longitude registration points.
    Date: 2001 (process 3 of 5)
    The linework was vectorized using gridline. The lines were edited and attributed in ARC/INFO. Polygons were built and attributed in ARC/INFO. Point data were digitized onscreen in ARC/INFO.
    Date: 2002 (process 4 of 5)
    First draft of metadata created by spriest on ARC/INFO data set c:\arcwork\clayhole
    Date: 17-Apr-2002 (process 5 of 5)
    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?
    Billingsley, George H., 2003, Geologic Map of Upper Clayhole Valley and Vicinity, Mohave County, Northwestern, Arizona: U.S. Geological Survey Miscellaneous Field Studies Series USGS MF-2418, U.S. Geological Survey, Flagstaff, Arizona.

    Online Links:


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:31,680 map scale, or 16 meters on the ground.
  3. How accurate are the heights or depths?
  4. Where are the gaps in the data? What is missing?
    The geologic map and digital database of Clayhole Valley 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. Polygons internal to the map boundary are completely enclosed by line segments which are themselves a set of sequentially numbered coordinate pairs. Point data are represented by coordinate pairs. The neatline was mathematically generated from latitude and longitude values.

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. Where this database is used in combination with other data of higher resolution, the resolution of the combined output will be limited by the lower resolution of these data.
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)
    U.S. Geological Survey Information Services
    Box 25286 Denver Federal Center
    Denver, CO
    USA

    1-888-ASK-USGS (voice)
    ask@usgs.gov
  2. What's the catalog number I need to order this data set? USGS Miscellaneous Field Studies Map MF-2418
  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 (cv_poly); folds, basalt flow lines (cv_ fold); point data including strike and dip, collapse features, sinkholes, and volcanic vents (cv_dip); and ancillary GIS files in format ARCE (version 8.1) Size: 12
      Network links: http://pubs.usgs.gov/mf/2003/2418/cvdb.zip
    • Cost to order the data: none


Who wrote the metadata?

Dates:
Last modified: 05-Feb-2016
Last Reviewed: 01-May-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/2418/metadata.faq.html>
Generated by mp version 2.9.48 on Tue Jul 03 20:05:19 2018