Geologic map of the Lakeview 7.5' quadrangle, Riverside County, California

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

Frequently anticipated questions:


What does this data set describe?

Title:
Geologic map of the Lakeview 7.5' quadrangle, Riverside County, California
Abstract:
This data set maps and describes the geology of the Lakeview 7.5' quadrangle, Riverside County, California. The quadrangle encompasses part of the northern Peninsular Ranges Province. Tonalitic granitic rocks of the Cretaceous Peninsular Range batholith dominate the bedrock areas, and include rocks ranging in composition from monzogranite to gabbro. The Lakeview Mountains are underlain chiefly by tonalite of the Lakeview pluton and related rocks. In the northeastern corner of the quadrangle, Tertiary sedimentary rocks of the San Timoteo beds of Frick (1921) and Mount Eden Formation of Fraser (1931) rest on Paleozoic schist, quartzite, gneiss, and marble having a well developed east dipping foliation. The Tertiary formations are much more extensively exposed in the San Timoteo Badlands to the northeast and southeast. These Tertiary and Paleozoic units are separated from the Lakeview Mountains by the San Jacinto Valley, which locally contains up to 3,000 m of Quaternary sediments. Two strands of the seismically active San Jacinto Fault zone bound the Valley, the Claremont Fault on the northeast side, and the Casa Loma Fault on the southwest side. Numerous cracks and fissures related to both groundwater withdrawal and tectonic movements are developed in the Quaternary sediments, especially in the northern part of the quadrangle.
Created using Environmental Systems Research Institute's ARC/INFO software, the database consists of the following items: (1) a map coverage containing faults, geologic contacts and units, (2) a coverage showing structural data, (3) a coverage containing geologic unit annotation and leaders, and (4) five additional INFO data tables (.rel) that contain detailed, coded, geologic information such as texture, fabric, color, and mineralogy and (5) line and point dictionaries, lines.rel and points.rel. These additional data are accessible to the user through the utilization of ARC/INFO relate environments and provide the user access to as much or as little of the encoded data as required. In addition, the data set includes the following graphic and text products: (1) A PostScript graphic plot-file containing the geologic map, topography, cultural data, a Correlation of Map Units (CMU) diagram, a Description of Map Units (DMU), and a key for point and line symbols, and (2) PDF files of this Readme (including the metadata file as an appendix), the poly_attrib_code.txt (the polygon attribute coding), and the graphic produced by the Postscript plot file.
The geologic map database contains original U.S. Geological Survey data generated by detailed field observation and by interpretation of aerial photographs. Within the database, geologic contacts are represented as lines (arcs), geologic units as polygons, and site-specific data as points. Polygon, arc, and point attribute tables (.pat, .aat, and .pat, respectively) uniquely identify each geologic datum.
Supplemental_Information:
Within the geologic map database, map units are identified by standard geologic map criteria such as formation-name, age, and lithology. The authors have attempted to adhere to the stratigraphic nomenclature of the U.S. Geological Survey and the North American Stratigraphic Code, but the database has not received a formal editorial review of geologic names.
Geologic map unit labels entered in database items LABL and PLABL contain substitute characters for conventional stratigraphic age symbols: Paleozoic appears as 'Pz' in LABL and as '|' in PLABL. The substitute characters in PLABL invoke their corresponding symbols from the GeoAge font group to generate map unit labels with conventional stratigraphic symbols.
  1. How might this data set be cited?
    Morton, D.M., and Matti, J.C., 2001, Geologic map of the Lakeview 7.5' quadrangle, Riverside County, California: U.S. Geological Survey Open-File Report 01-174, U.S. Geological Survey, Menlo Park, California.

    Online Links:

  2. What geographic area does the data set cover?
    West_Bounding_Coordinate: -117.12509085
    East_Bounding_Coordinate: -116.99990904
    North_Bounding_Coordinate: 33.87499933
    South_Bounding_Coordinate: 33.74998308
  3. What does it look like?
    http://pubs.usgs.gov/of/2001/0174/images/coverthb.gif (GIF)
    Simple image of the geologic map, topographic base, Correlation of Map Units, a description of Map Units and key to point and line symbols
    http://pubs.usgs.gov/of/2001/0174/pdf/lkvw_map.pdf (PDF)
    Navigable portable document file (.pdf) image of the geologic map, topographic base, Correlation of Map Units, Description of Map Units and key to point and line symbols.
  4. Does the data set describe conditions during a particular time period?
    Beginning_Date: 19620401
    Ending_Date: 01-Feb-2000
    Currentness_Reference:
    New data
  5. What is the general form of this data set?
    Geospatial_Data_Presentation_Form: vector digital data
  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 (378)
      • String (1083)
      • GT-polygon composed of chains (379)
    2. What coordinate system is used to represent geographic features?
      The map projection used is Polyconic.
      Projection parameters:
      Longitude_of_Central_Meridian: -117.0625
      Latitude_of_Projection_Origin: 33.7500
      False_Easting: 0.00000
      False_Northing: 0.00000
      Planar coordinates are encoded using coordinate pair
      Abscissae (x-coordinates) are specified to the nearest 0.000001
      Ordinates (y-coordinates) are specified to the nearest 0.000001
      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:
    Version 1.0 of the Lakeview 7.5' quadrangle comprises three ARC/INFO coverages, of which two contain geologic data and one contains cartographic features: lkvw_geo (geology), lkvw_pts (structural point data), and lkvw_anno (geologic unit annotation and leaders). 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.Two INFO tables, lines.rel and points.rel provide a full description of each of the geologic line and point features in the database. Full source citations are provided in the Entity_and Attribute_Detail_Citation section of this metadata document.
    1) The coverage lkvw_geo includes a polygon feature attribute table (lkvw_geo.pat) that describes the geospatial distribution of rock units represented in the Postscript (.ps) and Portable Document Format (.pdf) plotfiles of the geologic maps and an arc feature attribute table (lkvw_geo.aat) that describes the contacts and faults that bound rock-unit polygons. Line and point identity data are recorded in the .aat and .pat using a system of identity codes. Two INFO tables, lines.rel and points.rel, provide a full description of each of the geological line and point codes in the database. For display purposes in the .ps and .pdf geologic maps, the geology coverage includes one annotation subclass: anno.fault, which contains formal fault names. In addition, the item TAG allows the user to access (relate to) a series of INFO data tables that contain additional, detailed, coded geologic data. A complete description of the polygon, line, and point data coding schemes is available in U.S. Geological Survey Open-File Reports 97-859, OFR 97-860, and OFR 97-861 (full source citations follow).
    Five INFO data tables are included in the Lakeview database: lakeview_genesis.rel provides data summarizing the genesis of each of the major rock types that occur within a particular map rock unit, lakeview_summary.rel provides general information about a rock unit, lakeview_lithology.rel contains lithologic attributes for the main and secondary lithologic types in the geologic-map unit, lakeview_protolith.rel describes rock type protoliths, and lakeview_structure.rel contains geologic structural data. The tables have identical architecture. The item TAG serves as the relate item and there are five additional feature attribute items, LITH1...LITH5, that represent the major rock types within a rock unit. Lakeview_structure.rel contains an item STRHIST that contains attributes that describe the structural history of a particular unit.
    2) The coverage lkvw_pts includes a point attribute table (lkvw_pts.pat) that describes both the types and orientation of bedding, foliation, and lineation. An annotation subclass displays the dip or plunge values associated with the point data.
    3) The coverage lkvw_anno includes an arc attribute table (lkvw_ldr.pat) that describes annotation leaders and one annotation subclass, anno.geo, which contains unit labels derived from PLABL. Unit symbols that are placed outside the perimeter of a particular polygon identify that polygon with annotation leaders.
    Entity_and_Attribute_Detail_Citation:
    A complete description of the polygon, line, and point data coding schemes is available in the following U.S. Geological Survey Open-File Reports:
    Matti, J.C., Miller, F.K., Powell, R.E., Kennedy, S.A., Bunyapanasarn, T.P., Koukladas, Catherine, Hauser, R.M., and Cossette, P.M., 1997b, Geologic-point attributes for digital geologic-map databases produced by the Southern California Areal Mapping Project (SCAMP), Version 1.0: U.S.Geological Survey Open-File Report 97-859
    Matti, J.C., Miller, F.K., Powell, R.E., Kennedy, S.A., and Cossette, P.M., 1997c, Geologic-polygon attributes for digital geologic-map databases produced by the Southern California Areal Mapping Project (SCAMP), Version 1.0: U.S.Geological Survey Open-File Report 97-860
    Matti, J.C., Powell, R.E., Miller, F.K., Kennedy, S.A., Ruppert, K.R., Morton, G.L., and Cossette, P.M., 1997a, Geologic-line attributes for digital geologic-map databases produced by the Southern California Areal Mapping Project (SCAMP), Version 1.0: U.S.Geological Survey Open-File Report 97-861
    LKVW_GEO.PAT
    Geologic map units
    LABL
    Geologic map unit label. Plain text is substituted for conventional geologic age symbols (Pz for Paleozoic) and unit label subscripts as annotated on map
    ValueDefinition
    QwVery young wash deposits, arenaceous
    QywYoung wash deposits, arenaceous
    QfVery young alluvial-fan deposits, arenaceous
    QvVery young alluvial-valley deposits, siltey, clayey
    QcVery young colluvial deposits
    QlvVery young lacustrine and fluvial deposits, clayey, silty
    QyfYoung alluvial-fan deposits, arenaceous
    QyfYoung alluvial-fan deposits, gravel, arenaceous
    Qyf6Young alluvial-fan deposits, Unit 6, gravel, arenaceous
    Qyf5Young alluvial-fan deposits, Unit 5, gravel, arenaceous
    Qyf4Young alluvial-fan deposits, Unit 4, gravel, arenaceous
    Qyf3Young alluvial-fan deposits, Unit 3, gravel, arenaceous
    Qyf2Young alluvial-fan deposits, Unit 2, gravel, arenaceous
    Qyf1Young deposits of alluvial fans, Unit 1, gravel, arenaceous
    QyaYoung axial-valley floor deposits, arenaceous
    QyvYoung alluvial-valley deposits, arenaceous
    QyvYoung alluvial-valley deposits, clayey, arenaceous
    QyvYoung alluvial-valley deposits, clayey, silty
    QyvYoung alluvial-valley deposits, silty, arenaceous
    QyvYoung alluvial-valley deposits, silty, clayey
    Qyv1Young alluvial-valley deposits, Unit 1, arenaceous
    QylsYoung landslide deposits
    QofOld alluvial-fan deposits, arenaceous
    QofvOld alluvial-fan deposits and very young alluvial-valley deposits, arenaceous
    QovOld alluvial-valley deposits
    QocOld colluvial deposits
    QocOld colluvial deposits, gravel
    QvofVery old alluvial-fan deposits, arenaceous
    QvofVery old alluvial-fan deposits, gravel
    QvovVery old alluvial-valley deposits, arenaceous
    TstlSan Timoteo beds of Frick (1921)
    TmeusMount Eden Formation of Fraser (1931), upper sandstone member
    TmelsMount Eden Formation of Fraser (1931), lower sandstone member
    TmeaMount Eden Formation of Fraser (1931), arkosic sandstone member
    TmebMount Eden Formation of Fraser (1931), boulder breccia lenses
    TmecMount Eden Formation of Fraser (1931), conglomeratic sandstone member
    KmegGranite of Mount Eden
    KltTonalite of Laborde Canyon
    KtcgMonzogranite of Tres Cerritos
    KpLakeview Mountains pluton, pegmatite dikes
    KlmtLakeview Mountains pluton, tonalite
    KlmlLakeview Mountains pluton, leucocratic tonalite
    KlmmLakeview Mountains pluton, melanocratic tonalite
    KlmgLakeview Mountains pluton, hypersthene-hornblende gabbro
    KhgHeterogeneous granitic rocks
    KrctReinhardt Canyon pluton
    KgPzMixed metamorphic rocks and granitic rocks
    PzuMetamorphic rocks, undivided
    mMarble
    PLABL
    Coded geologic map unit label used to generate plot label. Subscripted characters indicate lithologies within the overall unit.
    SHDPS
    Coded integer that relates polygon to color in shadeset scamp2.shd
    SHDFIL
    Coded integer that relates polygon to fill pattern in shadeset geology2.shd
    NAME
    Geologic name of map unit (see list under LABL attribute)
    TAG
    A reference label for subgroups of polygons of the geologic-map unit identified by LABL. Each polygon subgroup has certain attributes in common with all other polygons of the map unit. However, each subgroup may have unique, distinguishing attributes which warrant recognition in the database although those distinguishing characteristics do not warrant recognition as new map units.
    TAG is defined as LABL followed by an upper-case letter, e.g., QwA, QwB, or QwC, etc. Map units in the Lakeview quadrangle are assigned an A tag designation except for Qyv (QyvA, QyvB and QyvC) and Qyf (QyfA, QyfB and QyfC).
    TAG serves one additional purpose: it functions as the relate item that associates each polygon with its attributes stored in the five polygon-attribute data tables identified in the overview description.
    LKVW_GEO.AAT
    Geologic contacts and faults that bound rock-unit polygons
    L-SYMB
    Coded integer symbol that relates arc to cartographic line symbol in lineset geoscamp2.lin
    L-TAG
    Coded alpha-numerical symbol that relates arc to definition of line type in dictionary look-up table (lines.rel). For description of attributes in line classification dictionary, refer to USGS Open-File Report 97-861 (see Entity_and_Attribute_Detail_Citation)
    ValueDefinition
    C17Contact, landslide, location meets map accuracy standard
    C29Contact, sedimentary, location meets map accuracy standard
    C30Contact, sedimentary, location may not meet map accuracy standard
    C31Contact, sedimentary, inferred, location may not meet map accuracy standard
    C37Contact, separates terraced alluvial units, location meets map accuracy standard
    C41Contact, sedimentary, gradational, location may not meet map accuracy standard
    C49Contact, igneous, location meets map accuracy standard
    C50Contact, igneous, location may not meet map accuracy standard
    C65Contact, metamorphic, location meets map accuracy standard
    CL1Cartographic line, map boundary
    DK9Dike, location may not meet map accuracy standard
    F6Fault, high-angle, oblique slip, location meets map accuracy standard
    F12Fault, high-angle, oblique slip, location may not meet map accuracy standard
    F18Fault, high-angle, oblique slip, inferred, location may not meet map accuracy standard
    F24Fault, high-angle, oblique slip, lnferred beneath mapped covering unit
    F36Fault, high-angle, oblique slip, existence questionable, location may not meet map accuracy standard
    F54Fault, high-angle, oblique slip, scarp, location meets map accuracy standard
    GF9Geomorphic feature.ground-failure scarp.certain.may not meet map accuracy standard
    ML8fissure.due to groundwater withdrawal and/or tectonics.certain.may not meet map accuracy standard
    L-NAME
    Formal name of linear geologic feature
    LKVW_PTS.PAT
    Structural point data
    P-DIP
    Dip of planar feature
    P-STRIKE
    Azimuthal strike of planar feature
    P-SYMB
    Coded integer symbol that relates point to cartographic point symbol in markerset (geoscamp2.mrk)
    P-TAG
    Coded alpha-numerical symbol that relates point to definition of point type in dictionary look-up table (points.rel). For description of attributes in point classification dictionary, refer to USGS Open-File Report 97-859 (see Entity_and_Attribute_Detail_Citation)
    ValueDefinition
    B1Bedding attitude, sedimentary, horizontal
    B2Bedding attitude, sedimentary, inclined
    B4Bedding attitude, sedimentary, vertical
    B14Bedding attitude, sedimentary, inclined, indicated, not measured
    FN4Foliation, inclined, indicated but not measured
    FN13Foliation, igneous, inclined
    FN14Foliation. igneous, vertical
    FN42Foliation, metamorphic, inclined
    FN43Foliation, metamorphic, vertical
    P-DIPDIR
    Azimuthal direction of dip of planar feature
    P-PLUNGE
    Plunge of linear feature
    P-BEARING
    Azimuthal direction of plunge of linear feature
    LKVW_ANNO.AAT
    Annotation leaders and unit labels
    L-SYMB
    Coded integer symbol, value 1, that relates arcs to cartographic line symbol in lineset geoscamp2.lin

Who produced the data set?

  1. Who are the originators of the data set? (may include formal authors, digital compilers, and editors)
    • D.M. Morton
    • J.C. Matti
  2. Who also contributed to the data set?
    Technical review by M. Dawson and F. Miller led to significant improvements that eventually were reflected in aspects of the database, the plot file, and in the description of the geologic units of the Lakeview 7.5' quadrangle. Digital review by R.W. Graymer has allowed us to prepare a much improved product.
    Geologic mapping and digital preparation of this report were sponsored jointly by (1) the National Cooperative Geologic Mapping Program of the U.S. Geological Survey, (2) the California Division of Mines and Geology, and (3) the Southern California Areal Mapping Project (SCAMP). The digital preparation of the data set was carried out by Rachel Alvarez and Gary Patt at the SCAMP Geographic Information System laboratory in Riverside, and by Pamela M. Cossette at the USGS Mineral Resources Program GIS lab in Spokane, Washington.
  3. To whom should users address questions about the data?
    D.M. Morton
    U.S. Geological Survey, Western Region, Earth Surface Processes Team
    Project chief
    U.S. Geological Survey
    Department of Geology
    University of California, Riverside
    Riverside, California
    United States of America

    (909) 276-6397 (voice)
    (909) 276-6295 (FAX)
    scamp@usgs.gov

Why was the data set created?

The data set for the Lakeview quadrangle has been prepared by the Southern California Areal Mapping Project (SCAMP), a cooperative project sponsored jointly by the U.S. Geological Survey and the California Division of Mines and Geology. The Lakeview data set represents part of an ongoing effort to create a regional GIS geologic database for southern California. This regional digital database, in turn, is being developed as a contribution to the National Geologic Map Database of the National Cooperative Geologic Mapping Program of the USGS.
The digital geologic map database for the Lakeview 7.5' quadrangle has been created as a general-purpose data set that is applicable to other land-related investigations in the earth and biological sciences. For example, it can be used for groundwater studies in the San Bernardino basin, and for mineral resource evaluation studies, animal and plant habitat studies, and soil studies in the San Bernardino National Forest. The database is not suitable for site-specific geologic evaluations.

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: 1962 (process 1 of 8)
    Field mapping and aerial photograph interpretation; iterative process (D.M. Morton and J.C. Matti).
    Date: 1964 (process 2 of 8)
    Transfer of geologic linework and point data from field maps and aerial photographs to a scale-stable cartographic base of quadrangle (scribeguide) (D.M. Morton and J.C. Matti).
    Date: 1964 (process 3 of 8)
    Description of Map Units and Correlation of Map Units (D.M. Morton and J.C. Matti)
    Date: 1994 (process 4 of 8)
    The geologic map information was hand digitized from author-prepared base-stable geologic map at 1:24,000 scale. (Rachel Alvarez and Gary Patt). Preliminary ARC/INFO database established.
    Date: 1999 (process 5 of 8)
    Detailed ARC/INFO database established; cleanup of ditizing artifacts; polygon, arc, and point attribute tables established using model developed for SCAMP coverages. Digitizing and editing artifacts significant enough to display at a scale of 1:24,000 were corrected (P.M. Cossette).
    Date: 1999 (process 6 of 8)
    Polygons coded with detailed geologic information using model developed for SCAMP coverages. (D.M. Morton and F.K. Miller).
    Date: 20-Mar-2001 (process 7 of 8)
    First draft of metadata created by cossette using FGDCMETA.AML ver. 1.2 05/14/98 on ARC/INFO data set /pool5/c/cossette2/lakeview/lkv-nonof/lkvw_geo
    Date: 11-Jul-2001 (process 8 of 8)
    Creation of original metadata record Person who carried out this activity:
    U.S. Geological Survey
    Attn: Pamela M. Cossette
    Cartographer
    904 West Riverside Avenue, Rm. 202
    Spokane, WA
    USA

    (509) 368-3123 (voice)
    (509) 368-3199 (FAX)
    pcossette@usgs.gov
  3. What similar or related data should the user be aware of?
    Morton, D.M., 1972, Geology of the Lakeview-Perris quadrangles, Riverside County, California: California Division of Mines and Geology Map Map Sheet 19, California Division of Mines and Geology, Sacramento, California.


How reliable are the data; what problems remain in the data set?

  1. How well have the observations been checked?
    Geologic-map units in the Lakeview quadrangle database were described using standard field methods. Consistent with these methods, the database author has assigned standard geologic attributes to geologic lines, points, and polygons identified in the database.
    Nation-wide geologic-map accuracy standards have not been developed and adopted by the U.S. Geological Survey and other earth-science entities. Until such standards are adopted, the SCAMP project has developed internal map-accuracy standards for 1:24,000-scale geologic maps produced by the project.
    Geologic lines and points on 1:24,000 scale geologic maps are judged to meet SCAMP's internal map-accuracy standards if they are located to within +/-15 meters, relative to topographic or cultural features on the base map.
    Lines and points that meet (or may not meet) this SCAMP internal map-accuracy standard are identified both in the digital database and on derivative geologic-map plots. Within the database, line and point data that are judged to meet the SCAMP internal map-accuracy standard are denoted by the attribute code .MEE. (meets) in the appropriate data table; line and point data that may not meet the SCAMP internal map-accuracy standard are denoted by the attribute code .MNM. (may not meet).
    On any derivative geologic-map plot, line data that are judged to meet the SCAMP internal map-accuracy standard are denoted by solid lines; line data that may not meet the SCAMP internal map-accuracy standard are denoted by dashed or dotted lines. There is no cartographic device for denoting the map-accuracy for geologic-point data (eg. symbols representing bedding, foliation, lineations, etc.).
  2. How accurate are the geographic locations?
    The maximum transformation RMS error acceptable for 7.5' quadrangle transformation and data input is 0.003 (7.6 meters). Horizontal positional accuracy was checked by visual comparison of hard-copy plots with base-stable source data.
  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 the Lakeview 7.5' quadrangle contain new data that have been subjected to rigorous review and are a substantially complete representation of the current state of knowledge concerning the geology of the quadrangle.
  5. How consistent are the relationships among the observations, including topology?
    Polygon and chain-node topology present.
    The areal extent of the map is represented digitally by an appropriately projected (Polyconic projection), mathematically generated box. Consequently, polygons intersecting the lines that comprise the map boundary are closed by that boundary. 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.

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:
The Lakeview 7.5' geologic-map database should be used to evaluate and understand the geologic character of the Lakeview 7.5' quadrangle as a whole. The data should not be used for purposes of site-specific land-use planning or site-specific geologic evaluations. The database is sufficiently detailed to identify and characterize geologic materials and structures. However, it is not sufficiently detailed for site-specific determinations.
Use of this digital geologic map database should not violate the spatial resolution of the data. Although the digital form of the data removes the constraint imposed by the scale of a paper map, the detail and accuracy inherent in map scale are also present in the digital data. The fact that this database was compiled and edited at a scale of 1:24,000 means that higher resolution information may not have been uniformly retained in the dataset. Plotting at scales larger than 1:24,000 will not yield greater real detail, although it may reveal fine-scale irregularities below the intended resolution of the database. Similarly, although higher resolution data is incorporated in parts of the map, the resolution of the combined output will be limited by the lower resolution data.
  1. Who distributes the data set? (Distributor 1 of 1)
    U.S. Geological Survey Information Services
    Box 25286, Denver Federal Center
    Denver, Colorado
    USA

    1-888-ASK-USGS (voice)
    303-202-4693 (FAX)
  2. What's the catalog number I need to order this data set? US Geological Survey Open-File Report 01-XXX
  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.
    This digital, geologic map database of the Lakeview 7.5'quadrangle, 1:24,000 map-scale, and any derivative maps thereof, is not meant to be used or displayed at any scale larger than 1:24,000 (e.g., 1:12,000).
  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:
FGDC Content Standards for Digital Geospatial Metadata (FGDC-STD-001-1998)

This page is <https://geo-nsdi.er.usgs.gov/metadata/open-file/01-174/metadata.faq.html>
Generated by mp version 2.9.48 on Tue Jul 03 20:05:37 2018