Geologic Map and Digital Database of Part of the Uinkaret Volcanic Field, 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 Part of the Uinkaret Volcanic Field, Mohave County, Northwestern 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:31,680 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 (uink.eps, uink.pdf, or uink.txt). The base layer used in the preparation of the geologic map plot files was derived from four Digital Raster Graphic versions of standard USGS 7.5' quadrangles. These raster images where converted to Grid format in ARC/INFO, trimmed and seamed together, then converted to a GeoTIFF image. The resultant TIFF image was combined with geologic data to produce the final map image in Illustrator 9.0.
  1. How might this data set be cited?
    Wellmeyer, J.L., and Dudash, S.L., 2001, Geologic Map and Digital Database of Part of the Uinkaret Volcanic Field, Mohave County, Northwestern Arizona: U.S. Geological Survey Miscellaneous Field Studies Map 2368, U.S. Geological Survey, Flagstaff, AZ.

    Online Links:

  2. What geographic area does the data set cover?
    West_Bounding_Coordinate: -113.257211
    East_Bounding_Coordinate: -112.99361063
    North_Bounding_Coordinate: 36.50445323
    South_Bounding_Coordinate: 36.24555938
  3. What does it look like?
  4. Does the data set describe conditions during a particular time period?
    Calendar_Date: 2001
    Currentness_Reference:
    The date given is the anticipated 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 (2491)
      • Complete chain (8642)
      • GT-Polygon composed of chains (2185)
    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?
    UINK_POLY.PAT
    attribute table of uink_poly (Source: ARC/INFO)
    UNIT
    Geologic unit label (Source: author)
    ValueDefinition
    CmMuav Limestone
    DtbTemple Butte Formation
    MrRedwall Limestone
    MPsSupai Group undivided
    PeEsplanade Sandstone
    PhHermit Formation
    PcCoconino Sandstone
    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
    QafArtificial deposits
    QbQuaternary basalt flows
    Qb1Quaternary basalt flows
    Qb6375Basalt flows of hill 6375
    Qb6467Basalt flows of hill 6467
    Qb6588Basalt flows of hill 6588
    Qb6646Basalt flows of hill 6646
    QcColluvial deposits
    QltbLarimore Tank basalt
    QcbbCraigs Knoll and Berry Knoll basalt flows
    QcbiCraigs Knoll and Berry Knoll intrusives
    QcbpCraigs Knoll and Berry Knoll pyroclastics
    QfFloodplain deposits
    Qg1Young terrace gravel deposits
    Qg2Intermediate terrace gravel deposits
    QiBasalt Dikes
    QkrbKenworthy Ranch basalt flows
    QkrpKenworthy Ranch pyroclastic deposits
    QlLandslide deposits
    QlsbLittle Springs basalt flow
    QlspLittle Springs pyroclastic deposits
    QmrbMarshall Ranch basalt flow
    QmrpMarshall Ranch pyroclastic deposits
    QpQuaternary pyroclastic deposits
    Qp1Quaternary pyroclastic deposits
    Qp6375Pyroclastics of Hill 6375
    Qp6467Pyroclastics of Hill 6467
    Qp6588Pyroclastics of Hill 6588
    Qp6646Pyroclastics of Hill 6646
    QpvbPotato Vally basalt flows
    QpvpPotato Vally pyroclastic deposits
    QsStream-channel alluvium
    QgrbGraham Ranch basalt
    QgrpGraham Ranch pyroclastics
    QtTalus deposits
    QTiIntrusive dikes
    QvValley-fill deposits
    TbBasalt flows north of Mt. Emma
    TbbBundyville basalt flows
    TbiBundyville intrusives
    TiIntrusive dikes
    TmlbMount Logan basalt flows
    TmbMount Trumbull basalt flows
    TmiMount Trumbull intrusives
    TpPyroclastics north of Mt. Emma
    TrcpChinle Formation Petrified Forest member
    TrmlMoenkopi Formation Lower red member
    TrmmMoenkopi Formation Middle red member
    TrmsMoenkopi Formation Shnabkaib member
    TrmtMoenkopi Formation Timpoweap member
    TrmuMoenkopi Formation Upper red member
    TrmvMoenkopi Formation Virgin Limestone member
    PATTERN
    Graphic fill pattern (Source: Author)
    ValueDefinition
    0No fill pattern in poly/region
    4Breccia fill pattern
    UINK_POLY.AAT
    attribute table of uink_poly (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 withina mapped unit that has experienced relative offset between the rok 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 isconstrained 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 betweena 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.
    BASALT FLOW DIRECTIONInterpreted direction of flow as seen in a basalt flow unit. Arrowhead points in direction of flow
    BASALT FLOW DIRECTION TAINInterpreted direction of flow as seen in a basalt flow unit. No arrowhead is present
    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.
    noneIndicates that no arcmarker is to be placed on specified arc
    UINK_FOLD.AAT
    Attribute table of uink_fold (Source: ARC/INFO)
    LINETYPE
    Type of geologic or geographic feature denoted by a line in the database. (Source: author)
    ValueDefinition
    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.
    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.
    POINTTYPE
    arc marker point type (Source: author)
    ValueDefinition
    monoclineArcmarker attached to an arc describing the monoclinal nature of fold axis
    synclineArcmarker attached to an arc describing the synclinal nature of fold axis
    noneIndicates that no arcmarker is to be placed on specified arc
    UINK_POINT.PAT
    Attribute table of uink_point (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.
    pyroclastic coneObserved location of a volcanic vent or cinder cone center.
    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
    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, PATTERN, 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 50, OUTPUT 50, and TYPE C (character). UNIT is defined with WIDTH 8, OUTPUT 8, and TYPE C. STRIKE and DIP are only present in UINK_ POINT.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 UINK_POINT.PAT, and is defined by WIDTH 3, OUTPUT 3, and TYPE I. The data in PATTERN correlates directly with specific values in the UNIT field.
    Entity_and_Attribute_Detail_Citation:
    The report combined with uinkmap.eps, uinkmap.pdf, uinkgeo.doc, uinkgeo.txt, or uinkgeo.pdf

Who produced the data set?

  1. Who are the originators of the data set? (may include formal authors, digital compilers, and editors)
    • Wellmeyer, J.L.
    • Dudash, S.L.
  2. Who also contributed to the data set?
    We would like to thank Debra Block at the Flagstaff USGS for all her GIS and ARC support and answers to all those questions. Thanks also to Scott Graham for the digital review of the dataset, Haydee Hampton for initial preparation of the digital files, Theresa Iki for her map editing, and Rich Koch and Carolyn Donlin for final publications work.
  3. To whom should users address questions about the data?
    Wellmeyer, Jessica L.
    USGS-GEO-WRG-NGM
    2255 North Gemini Drive
    Flagstaff, AZ
    USA

    520-556-7267 (voice)
    jwellmey@usgs.gov

Why was the data set created?

The geologic map of the Uinkaret volcanic field area covers part of the Colorado Plateau 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 and National Park Service project to provide geologic information for areas within the newly established Grand Canyon/Parashant Canyon National Monument. Most of the Grand Canyon and parts of the adjacent plateaus have been geologically mapped; this map fills in one of the remaining areas where uniform quality geologic mapping was needed. The geologic information presented may be useful in future related studies as to land use management, range management, and flood control programs for federal and state agencies, and private concerns.

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: 08-Jun-2001 (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 Flyn. 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 latitute and longitude and projected into the base map projection (Geographic). 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:31,680 were removed.
    Wendell Duffield, Susan Priest and Charles Powell II all contibuted to the review process
    Date: 08-Jun-2001 (process 2 of 2)
    Creation of original metadata record Person who carried out this activity:
    Wellmeyer, Jessica L
    USGS-GEO-WRG-NGM
    2255 N. Gemini Drive
    Flagstaff, AZ
    US

    (520) 556-7267 (voice)
    jwellmey@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?
  2. How accurate are the geographic locations?
    Well located data item 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?
    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.
  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 are 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.
  1. Who distributes the data set? (Distributor 1 of 1)
    USGS Information Services
    Box 25286, Denver Federal Center
    Denver, CO
    USA

    (303) 202-4200 (voice)
    (303) 202-4695 (FAX)
    infoservices@usgs.gov
  2. What's the catalog number I need to order this data set? USGS Map MF-2368
  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: 05-Feb-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 Standards for Digital Geospatial Metadata (FGDC-STD-001-1998)

This page is <https://geo-nsdi.er.usgs.gov/metadata/map-mf/2368/metadata.faq.html>
Generated by mp version 2.9.48 on Tue Jul 03 20:05:08 2018