USGS - science for a changing world

USGS Geoscience Data Catalog

Geologic map of the Cape Mendocino, Eureka, Garberville, and southwestern part of the Hayfork 30 X 60 Quadrangles and Adjacent Offshore Area, Northern California

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

Frequently anticipated questions:


What does this data set describe?

Title:
Geologic map of the Cape Mendocino, Eureka, Garberville, and southwestern part of the Hayfork 30 X 60 Quadrangles and Adjacent Offshore Area, Northern California
Abstract:
This 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 mapped area. Together with the accompanying text file (ceghmf.ps, ceghmf.pdf, ceghmf.txt), 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 and lithology following the stratigraphic nomenclature of the U.S. Geological Survey. The scale of the source maps limits the spatial resolution (scale) of the database to 1:100,000 or smaller.
Supplemental_Information:
This is the pre-release version of the report. The accompanying text file mf2336.rev contains version numbers for each part of the data set.
This report consists of a set of geologic map database files (Arc/ Info coverages) and supporting text and plotfiles. In addition, the report includes two sets of plotfiles (PostScript 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 (ceghdesc and ceghdb). The base map layer used in the preparation of the geologic map plotfiles was downloaded from the web (www.gisdatadepot.com) as Digital Raster Graphic files of scale-stable versions of the USGS 1:100,000 topographic maps and coverted to TIFF images which were then converted to GRIDs. These grids contain no database information other than position, and are included for reference only. The base maps used were the Cape Mendocino (1989 edition), Eureka (1987 edition), Garberville (1979 edition), Hayfork (1978 edition) 1:100,000 topographic maps, which all have a 50-meter contour interval. The bathymetry maps were converted from the Coast and Geodetic Survey hydrographic chart 1308 N-12, 1969.
  1. How might this data set be cited?
    McLaughlin, R.J., Ellen, S.D., Blake, M.C., Jayko, A.S., Irwin, W.P., Aalto, K.R., Carver, G.A., Clarke, S.H., Jr., Barnes, J.B., Cecil, J.D., and Cyr, K.A., 2000, Geologic map of the Cape Mendocino, Eureka, Garberville, and southwestern part of the Hayfork 30 X 60 Quadrangles and Adjacent Offshore Area, Northern California: U.S. Geological Survey Miscellaneous Field Studies Map 2336, U.S. Geological Survey, Menlo Park, CA.

    Online Links:

  2. What geographic area does the data set cover?
    West_Bounding_Coordinate: -125.02988586
    East_Bounding_Coordinate: -123
    North_Bounding_Coordinate: 41.01735316
    South_Bounding_Coordinate: 39.98265351
  3. What does it look like?
  4. Does the data set describe conditions during a particular time period?
    Calendar_Date: 2000Currentness_Reference:
    The date given is the publication date. The information in the report is the most up-to-date available at the time of publication.
  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
      • String
      • GT-polygon composed of chains
    2. What coordinate system is used to represent geographic features?
      Grid_Coordinate_System_Name: Universal Transverse Mercator
      Universal_Transverse_Mercator:
      UTM_Zone_Number: 10
      Transverse_Mercator:
      Scale_Factor_at_Central_Meridian: 0.9996
      Longitude_of_Central_Meridian: -123
      Latitude_of_Projection_Origin: 0.0
      False_Easting: 500000
      False_Northing: 0
      Planar coordinates are encoded using coordinate pair
      Abscissae (x-coordinates) are specified to the nearest 1.0
      Ordinates (y-coordinates) are specified to the nearest 1.0
      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?
    CEGH-GEO.PAT
    Attribute table of CEGH-GEO.PAT. (Source: ARC/INFO)
    PTYPE
    Geologic unit label (Source: author)
    ValueDefinition
    KrpIgneous and Sedimentary rocks of Point Delgada
    KsSedimentary rocks
    QTogOlder alluvium
    QTwMarine and non-Marine overlap deposits
    QalAlluvial deposits
    QlsLandslide deposits
    QmUndeformed marine shoreline and Aolian deposits
    QtUndifferentiated nonmarine terrace deposits
    TiVolcanic rocks of Fickle Hill
    YcglYager Terrane
    amAmphibolite
    bMelange block, lithology unknown
    blankunmapped area
    bsbasaltic rocks
    cMetachert
    cb1Subunit of unnamed Metasandstone and meta-argillite
    cb2Subunit of unnamed Metasandstone and meta-argillite
    ccChert
    cfsFort Steward Metasandstone
    chrHaman Ridge graywacke
    clsLimestone
    cm1Subunit of unnamed Metasandstone and meta-argillite
    cm2Subunit of unnamed Metasandstone and meta-argillite
    co1Subunit of Coastal Terrane
    co2Subunit of Coastal Terrane
    co3Subunit of Coastal Terrane
    co4Subunit of Coastal Terrane
    cobMinor mapped lithologies of the Coastal Terrane
    colsLimestone in the Coastal Terrane
    cwrWhite Rock metasandstone
    dpbBasaltic flows and keratophyric tuff
    dpdDiabase
    dpmsMudstone
    dpspSerpentinite melange
    dptTuffaceous chert
    ecgLayered gabbro
    ecmsElder Creek Terrane mudstone
    ecspSerpentintite melange
    ehEastern Hayfork subterrane melange and broken formation
    ehlsEastern Hayfork subterrane limestone
    ehspEastern Hayfork subterrane serpentinite
    fcFalse Cape Terrane
    gsGreenstone found in the central belt
    krbBasalt in the sandstone and argillite of King Peak
    krcChert in the sandstone and argillite of King Peak
    krk1Subunit of the sandstone and argillite of King Peak
    krk2Subunit of the sandstone and argillite of King Peak
    krk3Subunit of the sandstone and argillite of King Peak
    krlLimestone in the sandstone and argillite of King Peak
    mUndivided blueschist blocks
    mbChinquapin metabasalt member in the eastern belt
    mvMetabasalt and minor metachert-glaucophane bearing
    ppsmSouth Fork Mountain Schist
    ppvValentine Springs Formation
    rccRadiolarian chert in the Rattlesnake Creek Terrane
    rcicIntrusive complex in the Rattlesnake Creek Terrane
    rcisIntermediate to silicic volcanic rocks in the Rattlesnake Creek Terrane
    rclsLimestone in the Rattlesnake Creek Terrane
    rcmMelange in the Rattlesnake Creek Terrane
    rcpPlutonic rocks in the Rattlesnake Creek Terrane
    rcpdBlocky peridotite in the Rattlesnake Creek Terrane
    rcumUltramafic rocks in the Rattlesnake Creek Terrane
    spSerpentinite
    srgbGlen Creek Gabbro-ultramafic complex
    srpdSerpentinized peridotite
    srsGalice? Formation
    srvPyroclastic andesite
    waterwater
    whjiDiorite and gabbro plutons
    whuHayfork Bally meta-andesite, undivided
    whwgWildwood pluton
    whwpClinopyroxenite
    y1Subunit of the Yager Terrane
    y2Subunit of the Yager Terrane
    y3Subunit of the Yager Terrane
    ybMetasandstone of the Yolla Bolly Terrane
    ybcChicago Rock melange
    ybdDevils Hole Ridge Broken Formation
    ybhMetagreywacke of Hammerhorn Ridge
    ybiLittle Indian Valley argillite
    CEGH-GEO.AAT
    Attribute table of CEGH-GEO. (Source: ARC/INFO)
    LTYPE
    Type of geologic or geographic feature denoted by a line in the database. (Source: author)
    ValueDefinition
    1906San Andreas fault 1906 earthquake rupture. Structural boundary between mapped units or structural discontinuity within a mapped unit, that experienced relative right-lateral offset or surface rupturing in the San Francsico earthquake of 1906. Boundary mapped by F. Matthes.
    1906, inferred, queriedSan Andreas fault 1906 earthquake rupture. Structural boundary between mapped units or structural discontinuity within a mapped unit, that experienced relative right-lateral offset or surface rupturing in the San Francsico earthquake of 1906. Boundary mapped by F. Mattles. The fault rupture has not been observed, so it is not well-located as described in Positional_Accuracy, but the location is constrained to be within about 10 mm at map scale (1:100,000) or within about 1000 meters on the ground. The existence of the contact is inferred from structural and stratigraphic relationships observed elsewhere.
    contact, approx. locatedBoundary between two mapped units that retains the original depositional or intrusive relationship (i.e. not faulted). 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 about 2 mm at map scale (1:100,000) or within about 200 meters on the ground.
    contact, certainBoundary between two mapped units that retains the original depositional or intrusive relationship (i.e. not faulted). The contact has been observed or is closely constrained, so it is well-located as described in Positional_Accuracy.
    contact, concealedBoundary between two mapped units that retains the original depositional or intrusive relationship (i.e. not faulted). The contact 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 about 5 mm at map scale (1:100,000) or within about 500 meters on the ground.
    contact, inferredBoundary between two mapped units that retains the original depositional or intrusive relationship (i.e. not faulted). 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 about 5 mm at map scale (1:100,000) or within about 500 meters on the ground. The existence of the contact is inferred from structural and stratigraphic relationships observed elsewhere.
    contact, inferred, queriedBoundary between two mapped units that retains the original depositional or intrusive relationship (i.e. not faulted). 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 about 10 mm at map scale (1:100,000) or within about 1000 meters on the ground. The existence of the contact is inferred from structural and stratigraphic relationships observed elsewhere.
    fault, approx. locatedStructural 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 contact has not been observed, so it is not well-located as described in Positional_Accuracy, but the location is constrained to be within about 2 mm at map scale (1:100,000) or within about 200 meters on the ground.
    fault, 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.
    fault, 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 about 5 mm at map scale (1:100,000) or within about 500 meters on the ground.
    fault, concealed, queriedStructural 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 about 10 mm at map scale (1:100,000) or within about 1000 meters on the ground.
    fault, 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 has not been observed, so it is not well-located as described in Positional_Accuracy, but the location is constrained to be within about 5 mm at map scale (1:100,000) or within about 500 meters on the ground. The existence of the fault is inferred from structural and stratigraphic relationships observed elsewhere.
    fault, inferred, queriedStructural 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, but the location is constrained to be within about 10 mm at map scale (1:100,000) or within about 1000 meters on the ground. The existence of the fault is inferred from structural and stratigraphic relationships observed elsewhere.
    map boundary,Edge 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
    photo lineamentLinear physiographic feature, delineated by alignment of topographic features, ie offsets or alignments of drainages, gullys, ridges, valley fronts, scarps or steps in topography. They are generally delineated from aerial photographs. They are inferred to be related to faulting, although are seldom checked in the field.
    reverse fault, approx. locatedStructural boundary between mapped units or structural discontinuity within a mapped unit that has experienced reverse offset between the rock bodies 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 about 2 mm at map scale (1:100,000) or within about 200 meters on the ground.
    reverse fault, certainStructural boundary between mapped units or structural discontinuity within a mapped unit that has experienced reverse 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.
    reverse fault, concealedStructural boundary between mapped units or structural discontinuity within a mapped unit that has experienced reverse 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 about 5 mm at map scale (1:100,000) or within about 500 meters on the ground.
    normal fault, certainStructural boundary between mapped units or structural discontinuity within a mapped unit that has experienced normal 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 fault, inferred, queriedStructural boundary between mapped units or structural discontinuity within a mapped unit that has experienced normal 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, but the location is constrained to be within about 10 mm at map scale (1:100,000) or within about 1000 meters on the ground. The existence of the fault is inferred from structural and stratigraphic relationships observed elsewhere.
    scratch boundary, certainAn arbitrary line with no geologic or geographic significance. Used primarily to divide polygons that would otherwise have more vertices than allowed by Arc/Info.
    s.s. fault, r.l., certainStructural boundary between mapped units or structural discontinuity within a mapped unit that has experienced dextral 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.
    s.s. fault, r.l., approx. locatedStructural boundary between mapped units or structural discontinuity within a mapped unit that has experienced dextral 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, but the location is constrained to be within about 2 mm at map scale (1:100,000) or within about 200 meters on the ground.
    s.s. fault, r.l., concealedStructural boundary between mapped units or structural discontinuity within a mapped unit that has experienced dextral 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 about 5 mm at map scale (1:100,000) or within about 500 meters on the ground.
    s.s. fault, r.l., inferred, queriedStructural boundary between mapped units or structural discontinuity within a mapped unit that has experienced dextral 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, but the location is constrained to be within about 10 mm at map scale (1:100,000) or within about 1000 meters on the ground.
    thrust fault, approx. locatedStructural boundary between mapped units or structural discontinuity within a mapped unit that has experienced thrust offset between the rock bodies 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 about 2 mm at map scale (1:100,000) or within about 200 meters on the ground.
    thrust fault, certainStructural boundary between mapped units or structural discontinuity within a mapped unit that has experienced thrust 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.
    thrust fault, concealedStructural boundary between mapped units or structural discontinuity within a mapped unit that has experienced thrust 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 about 5 mm at map scale (1:100,000) or within about 500 meters on the ground.
    thrust fault, concealed, queriedStructural boundary between mapped units or structural discontinuity within a mapped unit that has experienced thrust 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 about 10 mm at map scale (1:100,000) or within about 1000 meters on the ground. The existence of this fault has been inferred from probable stratigraphic and structural relationships observed at a regional scale.
    thrust fault, inferredStructural boundary between mapped units or structural discontinuity within a mapped unit that has experienced thrust 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, but the location is constrained to be within about 5 mm at map scale (1:100,000) or within about 500 meters on the ground. The existence of the fault is inferred from structural and stratigraphic relationships observed elsewhere.
    thrust fault, inferred, queriedStructural boundary between mapped units or structural discontinuity within a mapped unit that has experienced thrust 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, but the location is constrained to be within about 10 mm at map scale (1:100,000) or within about 1000 meters on the ground. The existence of the fault is inferred from structural and stratigraphic relationships observed elsewhere.
    water boundaryThe edge of a mapped body of water. This line is derived from the base map, and therefore is well-located as described in Positional_Accuracy.
    water boundary,The edge of a mapped body of water. This line is derived from the base map, and therefore is well-located as described in Positional_Accuracy.
    water boundary, certainThe edge of a mapped body of water. This line is derived from the base map, and therefore is well-located as described in Positional_Accuracy.
    CEGH-STR.PAT
    Attribute table of CEGH-STR. (Source: ARC/INFO)
    PTTYPE
    The type of planar feature which was observed and the orientation of which was measured at this point. (Source: author)
    ValueDefinition
    approx. beddingOriginally horizontal sedimentary layers were observed at this point. Because of poor exposure, weathering, indistinct layering, or some other factor, only the approximate orientation of the layers was measured.
    beddingOriginally horizontal sedimentary layers were observed at this point.
    bedding w/topsOriginally horizontal sedimentary layers were observed at this point. In addition, a geopedal indicator was observed that showed the beds were upright.
    ot bedding w/topsOriginally horizontal sedimentary layers were observed at this point. In addition, a geopedal indicator was observed that showed the beds were overturned.
    flat beddingSedimentary layers that retain their original horizontal position were observed at this point.
    foliationMetamorphic foliation was observed at this point.
    ot beddingOriginally horizontal sedimentary layers were observed at this point. Evidence that the beds are overturned was observed, although that observation may not have been made at this point.
    vert beddingOriginally horizontal sedimentary layers were observed at this point. These layers are now vertical.
    vert foliationFoliation due to shearing or metamorhpism was observed at this point. This foliation is vertical.
    horz foliationFoliation due to shearing or metamorhpism was observed at this point. This foliation is horizontal.
    vert bedding w/topsOriginally horizontal sedimentary layers were observed at this point. In addition, a geopedal indicator was observed that showed the beds were upright. These layers are now vertical.
    inclined cleavageClosely-spaced, sub-parallel planar structures in metamorphic rock, non-horizontal and non-vertical, produced by deformation or metamorphism were observed here.
    jointSurface of fracture or parting, with no displacement, was observed here.
    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
    CEGH-STR.AAT
    Attribute table of CEGH-STR. (Source: ARC/INFO)
    LTYPE
    The type of fold axis or other structural linear feature that does not bound geologic units. Faults and contacts are described in a separate coverage. (Source: author)
    ValueDefinition
    f.a., anticline, approx. locatedThe surface trace of the axis of an anticline. The axis has not been observed, so it is not well-located as described in Positional_Accuracy, but the location is constrained to be within about 2 mm at map scale (1:100,000) or within about 200 meters on the ground.
    f.a., anticline, certainThe surface trace of the axis of an anticline. The axis has been observed or is closely constrained, so it is well-located as described in Positional_Accuracy.
    f.a., anticline, inferred, queriedThe surface trace of the axis of an anticline. The axis has not been observed, so it is not well-located as described in Positional_Accuracy, but the location is constrained to be within about 10 mm at map scale (1:100,000) or within about 1000 meters on the ground. The existence of the fold is inferred from structural and stratigraphic relationships observed elsewhere.
    f.a., syncline, approx. locatedThe surface trace of the axis of a syncline. The axis has not been observed, so it is not well-located as described in Positional_Accuracy, but the location is constrained to be within about 2 mm at map scale (1:100,000) or within about 200 meters on the ground.
    f.a., syncline, certainThe surface trace of the axis of a syncline. The axis has been observed or is closely constrained, so it is well-located as described in Positional_Accuracy.
    f.a., syncline, inferred, queriedThe surface trace of the axis of a syncline. The axis has not been observed, so it is not well-located as described in Positional_Accuracy, but the location is constrained to be within about 10 mm at map scale (1:100,000) or within about 1000 meters on the ground. The existence of the fold is inferred from structural and stratigraphic relationships observed elsewhere.
    f.a., ot syncline, certainThe surface trace of the axis of a syncline. The axis has been observed or is closely constrained, so it is well-located as described in Positional_Accuracy. Evidence that the syncline is overturned was observed, although that observation may not have been made at this point.
    f.a., ot syncline, approx. locatedThe surface trace of the axis of a syncline. The axis has not been observed, so it is not well-located as described in Positional_Accuracy, but the location is constrained to be within about 2 mm at map scale (1:100,000) or within about 200 meters on the ground. Evidence that the syncline is overturned was observed, although that observation may not have been made at this point.
    CM-GEO.PAT
    Attribute table of CM-GEO. (Source: ARC/INFO)
    PTYPE
    refer to PTYPE definitions listed under CEGH-GEO.PAT as this file was derived from that one. Therefore, this file might not have every PTYPE listed there, but all PTYPES it does possess will be defined there. (Source: author)
    LTYPE
    refer to LTYPE definitions listed under CEGH-GEO.AAT as this file was derived from that one. Therefore, this file might not have every LTYPE listed there, but all LTYPES it does possess will be defined there. (Source: author)
    CM-STR.PAT
    Attribute table of CM-STR. (Source: ARC/INFO)
    PTTYPE
    refer to PTTYPE definitions listed under CEGH-STR.PAT as this file was derived from that one. Therefore, this file might not have every PTYPE listed there, but all PTTYPES it does possess will be defined there. (Source: author)
    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
    CM-STR.AAT
    Attribute table of CM-STR. (Source: ARC/INFO)
    LTYPE
    refer to LTYPE definitions listed under CEGH-STR.AAT as this file was derived from that one. Therefore, this file might not have every LTYPE listed there, but all LTYPES it does possess will be defined there. (Source: author)
    EU-GEO.PAT
    Attribute table of EU-GEO. (Source: ARC/INFO)
    PTYPE
    refer to PTYPE definitions listed under CEGH-GEO.PAT as this file was derived from that one. Therefore, this file might not have every PTYPE listed there, but all PTYPES it does possess will be defined there. (Source: author)
    EU-GEO.AAT
    Attribute table of EU-GEO. (Source: ARC/INFO)
    LTYPE
    refer to LTYPE definitions listed under CEGH-GEO.AAT as this file was derived from that one. Therefore, this file might not have every LTYPE listed there, but all LTYPES it does possess will be defined there. (Source: author)
    EU-STR.PAT
    Attribute table of EU-STR. (Source: ARC/INFO)
    PTTYPE
    refer to PTTYPE definitions listed under CEGH-STR.PAT as this file was derived from that one. Therefore, this file might not have every PTTYPE listed there, but all PTTYPES it does possess will be defined there. (Source: author)
    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
    EU-STR.AAT
    Attribute table of EU-STR. (Source: ARC/INFO)
    LTYPE
    refer to LTYPE definitions listed under CEGH-STR.AAT as this file was derived from that one. Therefore, this file might not have every LTYPE listed there, but all LTYPES it does possess will be defined there. (Source: author)
    GA-GEO.PAT
    Attribute table of GA-GEO. (Source: ARC/INFO)
    PTYPE
    refer to PTYPE definitions listed under CEGH-GEO.PAT as this file was derived from that one. Therefore, this file might not have every PTYPE listed there, but all PTYPES it does possess will be defined there. (Source: author)
    GA-GEO.AAT
    Attribute table of GA-GEO. (Source: ARC/INFO)
    LTYPE
    refer to LTYPE definitions listed under CEGH-GEO.AAT as this file was derived from that one. Therefore, this file might not have every LTYPE listed there, but all LTYPES it does possess will be defined there. (Source: author)
    GA-STR.PAT
    Attribute table of GA-STR. (Source: ARC/INFO)
    PTTYPE
    refer to PTTYPE definitions listed under CEGH-STR.PAT as this file was derived from that one. Therefore, this file might not have every PTTYPE listed there, but all PTTYPES it does possess will be defined there. (Source: author)
    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
    GA-STR.AAT
    Attribute table of GA-STR. (Source: ARC/INFO)
    LTYPE
    refer to LTYPE definitions listed under CEGH-STR.AAT as this file was derived from that one. Therefore, this file might not have every LTYPE listed there, but all LTYPES it does possess will be defined there. (Source: author)
    HA-GEO.PAT
    Attribute table of HA-GEO. (Source: ARC/INFO)
    PTYPE
    refer to PTYPE definitions listed under CEGH-GEO.PAT as this file was derived from that one. Therefore, this file might not have every PTYPE listed there, but all PTYPES it does possess will be defined there. (Source: author)
    HA-GEO.AAT
    Attribute table of HA-GEO. (Source: ARC/INFO)
    LTYPE
    refer to LTYPE definitions listed under CEGH-GEO.AAT as this file was derived from that one. Therefore, this file might not have every LTYPE listed there, but all LTYPES it does possess will be defined there. (Source: author)
    CM-BLKS.PAT
    Attribute table of CM-BLKS. (Source: ARC/INFO)
    PTTYPE
    melange block (Source: author)
    ValueDefinition
    melange blockmelange block
    SAMPNO
    BKTYPE
    melange block
    ValueDefinition
    bsblueschist block
    CM-FOS.PAT
    Attribute table of CM-FOS. (Source: ARC/INFO)
    PTTYPE
    fossil locality (Source: author)
    SAMPNO
    sample number correlated to an index table which describes the fossil type, age, collector etc.. Table 1 on Sheet 5 (Source: author)
    Range of values
    Minimum:1
    Maximum:81
    Units:arbitrary sample number
    Resolution:1
    CM-KSP.PAT
    Attribute table of CM-KSP. (Source: ARC/INFO)
    PTTYPE
    K-feldspar sample locality (Source: author)
    ValueDefinition
    K-feldspar sample localityK-feldspar sample locality
    KSPAR
    percentage of K-feldspar measured from a sample taken at this locality. Note: a value of '0.01' represents a value of 'trace' amount K-feldspar. (Source: author)
    Range of values
    Minimum:0
    Maximum:99.99
    Units:percent
    Resolution:0.01
    SAMPNO
    (Source: ARC/INFO)
    EU-FOS.PAT
    Attribute table of EU-FOS. (Source: ARC/INFO)
    PTTYPE
    fossil locality (Source: author)
    ValueDefinition
    fossil localityfossil locality
    SAMPNO
    sample number correlated to an index table which describes the fossil type, age, collector etc.. Table 1 on Sheet 5 (Source: author)
    Range of values
    Minimum:1
    Maximum:81
    Units:arbitrary sample number
    Resolution:1
    GAR-FOS.PAT
    Attribute table of GAR-FOS. (Source: ARC/INFO)
    PTTYPE
    fossil locality (Source: author)
    ValueDefinition
    fossil localityfossil locality
    SAMPNO
    sample number correlated to an index table which describes the fossil type, age, collector etc.. Table 1 on Sheet 5 (Source: author)
    Range of values
    Minimum:1
    Maximum:81
    Units:arbitrary sample number
    Resolution:1
    GAR-KSP.PAT
    Attribute table of GAR-KSP. (Source: ARC/INFO)
    PTTYPE
    K-feldspar sample locality (Source: author)
    ValueDefinition
    K-feldspar sample localityK-feldspar sample locality
    KSPAR
    percentage of K-feldspar measured from a sample taken at this locality. Note: a value of '0.01' represents a value of 'trace' amount K-feldspar. (Source: author)
    Range of values
    Minimum:0
    Maximum:99.99
    Units:percent
    Resolution:0.01
    SAMPNO
    GAR-BLKS.PAT
    Attribute table of GAR-BLKS. (Source: ARC/INFO)
    PTTYPE
    melange block (Source: author)
    ValueDefinition
    melange blockmelange block
    BKTYPE
    melange block type (Source: author)
    ValueDefinition
    bsblueschist block
    chchert block
    gsgreenstone block
    spserpentinite block
    SAMPNO
    Entity_and_Attribute_Overview:
    The databases in this report were compiled in ARC/INFO, a commercial Geographic Information System (Environmental Systems Research Institute, Redlands, California). 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 are "coveragename"-ID, LTYPE, PTYPE, PTTYPE, BKTYPE, SAMPNO, STRIKE, and DIP. "coveragename"-ID is required by internal policy to be sequential. This ensures the highest compatibility of our databases with other GISs. Therefore "coveragename"-ID is calculated equal to "coveragename"#, which is a unique, sequential integer assigned by Arc/Info to each data record. LTYPE, PTYPE, BKTYPE, and PTTYPE are author added items to the coverage AAT or PAT that are used to describe the type of line (LTYPE), area ( PTYPE), block type (BKTYPE) or point (PTTYPE) being recorded. All coverages with AAT and PAT present include these items in the data structure, although in some cases these items are not used (see above). Each has WIDTH 35, OUTPUT 35, TYPE C, except BKTYPE which has WIDTH 6, OUTPUT 6, TYPE C. STRIKE and DIP are author added items to the coverage PAT that record information about the orientation of planar geologic structures. Both have WIDTH 3, OUTPUT 3, TYPE I. These items are recorded in the tables XX-STR.PAT of the structure coverages. KSPAR is an author added item that only the table GAR-BLKS.PAT has that records information about the percentage of K-feldspar collected at specific localities in the map area. It has WIDTH 35, OUTPUT 35, TYPE C. The base map layers are included for visual reference only and contain no data attributes or attribute tables.
    Entity_and_Attribute_Detail_Citation:
    This report combined with the explanatory pamphlet or pamphlets: ceghmf and ceghmfdb.

Who produced the data set?

  1. Who are the originators of the data set? (may include formal authors, digital compilers, and editors)
  2. Who also contributed to the data set?
    The authors are grateful to the following paleontologists of the U.S. Geological Survey, academia and the private sector, for their substantial contributions towards the understanding of the geology of the map area: S.A. Kling (Micro-Paleo Consultants), Cenozoic and Mesozoic radiolaria; J.A. Barron (USGS), Tertiary diatoms; K. McDougall (USGS), Tertiary benthic foraminifers; R.Z. Poove (USGS), Tertiary planktonic foraminifers; W.R. Evitt (Stanford University), Mesozoic and Tertiary dinoflagellates and pollen; W.V. Sliter (USGS), Mesozoic and early Tertiary foraminifers; G. Keller (Princeton University), Tertiary foraminifers; N.O. Frederikson (USGS), Mesozoic and Tertiary spores and pollen; B. Roth (consultant; formerly California Academy of Sciences), late Tertiary marine mollusks; C.L. Powell (USGS), marine mollusks; D. Bukry (USGS), Tertiary nannoplankton; D.L. Jones (USGS and UC Berkeley), Mesozoic Macrofossils; B. Murchey (USGS), Mesozoic radiolaria; C. Blome ( USGS), Mesozoic radiolaria; R. Feldman (Kent State University, Ohio), Cenozoic Crustacea; J. Clark (consultant), Mesozoic and Tertiary dinoflagellates; Y. Isozaki (Tokyo Institute of Technology, Japan), Mesozoic radiolaria; P. Baumgartner (Universite de Lausanne, Lausanne, Switzerland), Mesozoic radiolaria.
    The first author acknowledges R.G. Stanley, L. Magoon, T. Lorenson, and P. Lillis of the USGS, and M.B. Underwood (University of Missouri, Columbia, MO) for insights on structure and stratigraphy from petroleum source-rock investigations in the Mendocino triple junction region in 1997 and 1998.
    We are grateful to D. Harwood (USGS) and D. Howell (USGS) for their thorough scientific reviews of these maps as well as their willness to return them to us in a timely manner.
    We are very grateful to R. Graymer, Zenon Valin, and C. Wentworth for help and advice in the digital preparation and formatting of these maps for publication. We also thank R. Graymer for his careful digital review. We thank J. Zigler of the USGS Western Publications Group for her careful editing which substantially improved this report. Finally, we greatfully acknowledge the help of M. Reid (USGS and Chairman of the Mass wasting Scientific Review Panel), and L.J.P. Muffler (Regional Geologist for the Western Region of the USGS), for bringing attention to the existence of this database for addressing habitat, mass wasting and other issues in northwestern California.
    Note: Authorship of the geology of this publication resides in the first eight names in the author list in the order given. The last three names starting with J.B. Barnes, are the digital database authors in the order given.
  3. To whom should users address questions about the data?
    USGS Western Geologic Mapping Team
    Attn: Database coordinator
    345 Middlefield Road, MS 975
    Menlo Park, CA
    USA


Why was the data set created?

This database and accompanying plot files depict the distribution of geologic materials and structures at a regional (1:100,000) scale. The report is intended to provide geologic information for the regional study of materials properties, earthquake shaking, landslide potential, mineral hazards, seismic velocity, and earthquake faults. In addition, the report contains new information and interpretations about the regional geologic history and framework. However, the regional scale of this report does not provide sufficient detail for site development purposes. In addition, this map does not take the place of fault-rupture hazard zones designated by the California State Geologist (Hart and Bryant, 1997). Similarly, the database cannot be used to identify or delineate landslides in the region.

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 3)
    The databases in this report were compiled in ARC/INFO, a commercial Geographic Information System (Environmental Systems Research Institute, Redlands, California), with version 3.0 of the menu interface ALACARTE (Fitzgibbon and Wentworth, 1991, Fitzgibbon, 1991, Wentworth and Fitzgibbon, 1991). The files are in either GRID (ARC/INFO raster data) format or COVERAGE (ARC/INFO vector data) format. Coverages are stored in uncompressed ARC export format (ARC/INFO version 7.x). ARC/INFO export files (files with the .e00 extension) can be converted into ARC/INFO coverages in ARC/INFO (see below) and can be read by some other Geographic Information Systems, such as MapInfo via ArcLink and ESRI's ArcView (version 1.0 for Windows 3.1 to 3.11 is available for free from ESRI's web site: http://www.esri.com). The digital compilation was done in version 7.2.1 of ARC/INFO with version 3.0 of the menu interface ALACARTE (Fitzgibbon and Wentworth, 1991, Fitzgibbon, 1991, Wentworth and Fitzgibbon, 1991). The geologic map information was digitized from stable originals of the geologic maps at 1:100,000 scale. The author manuscripts (pen on mylar) were scanned using a Altek monochrome scanner with a resolution of 800 dots per inch. The scanned images were vectorized and transformed from scanner coordinates to projection coordinates with digital tics placed by hand at quadrangle corners. The scanned lines were edited interactively by hand using ALACARTE, color boundaries were tagged as appropriate, and some scanning artifacts visible at 1:24,000 were removed.
    (process 2 of 3)
    Geologic linework was scanned, converted to vector data, and edited on-screen to repair errors visible at map scale. Polygon topology was created and each polygon tagged on-screen. Structural information was digitized by hand using a digitizing table. Plotfiles were created in ArcPlot.
    Date: 02-Sep-2009 (process 3 of 3)
    Creation of original metadata record Person who carried out this activity:
    J.B. Barnes
    U.S. Geological Survey
    345 Middlefield Rd., M/S 975
    Menlo Park, CA
    USA

  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 items are intended to have a horizontal positional accuracy within .5 mm at 1:100,000 scale, or within 50 meters on the ground. The general positional accuracy of each line in the database is indicated within the LTYPE field in the Arc Attribute Table (see below). Points in the database are generally considered to be well located. The position of each data item is derived from the USGS topographic base map, and therefore additional inaccuracies arising from inaccuracies in the base map may also be encountered.
  3. How accurate are the heights or depths?
  4. Where are the gaps in the data? What is missing?
    The report is intended to describe completely the surficial deposits and bedrock geology at 1:100,000 scale. Geologic information only mappable at larger scale has been omitted. In addition, landslide deposits are for the most part not recorded.
  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 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 edited for a scale of 1:100,000 means that higher resolution information is not present in the dataset. Plotting at scales larger than 1:100,000 will not yield greater real detail, although it may reveal fine-scale irregularities below the intended resolution of the database. Similarly, 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.
  1. Who distributes the data set? (Distributor 1 of 1)
    Database Coordinator
    U.S. Geological Survey
    345 Middlefield Rd., M/S 975
    Menlo Park, CA
    USA

    Contact_Instructions:
    Please contact by mail. For digital packages on Exabyte tape, send a tape with your request. Please specify which data package you are requesting (PostScript plotfiles package m2336ps.tgz, PDF plotfiles package m2336pdf.tgz, or Arc/Info database package m2336db.tgz)
  2. What's the catalog number I need to order this data set? USGS Miscellaneous Field Studies Report MF-2336 consists of both traditional geologic map products and Arc/Info format geospatial databases. Furthermore, the traditional geologic map products (map sheets and pamphlets) can be obtained either as paper or as digital plot files.
  3. What legal disclaimers am I supposed to read?
    Any use of trade, product, or 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: 13-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/2336/metadata.faq.html>

Accessibility FOIA Privacy Policies and Notices

USA.gov logo U.S. Department of the Interior | U.S. Geological Survey
URL: https://geo-nsdi.er.usgs.gov/metadata/map-mf/2336/metadata.faq.html
Page Contact Information: Peter Schweitzer
Page Last Modified: Wednesday, 01-Feb-2017 10:42:17 EST

Generated by mp version 2.9.39 on Wed Feb 1 10:42:17 2017