Link to USGS home page

Polygon coverage MBGEOLSE for Seafloor rocks and sediments of the continental shelf from Monterey Bay to Point Sur, California

Metadata also available as - [Parseable text]

Frequently-anticipated questions:


What does this data set describe?

    Title:
    Polygon coverage MBGEOLSE for Seafloor rocks and sediments of the continental shelf from Monterey Bay to Point Sur, California
    Abstract:
    This data set, MBGEOLSE, consists of polygons of seafloor geologic units and line traces of the San Gregorio Fault interpreted from acoustic imagery data collected by the USGS and cooperators on the continental shelf from 1995 to 1998. MBGEOLSE is the data layer of the print map USGS MF-2345, which also includes a shaded relief base layer. The pertinent USGS/CMG field activity IDs (<http://walrus.wr.usgs.gov/infobank>) are

     P-1-95-MB
     P-2-95-MB
     M-1-95-MB
     J-2-95-MB
     J-6-95-MB
     M-2-95-MB
     M-1-96-MB
     J-6-96-MB
     J-7-96-MB
     J-1-97-MB
     J-3-97-MB
     M-4-97-MB
     J-3-98-MB
     M-1-98-MB
     A-4-98-MB
    
    Supplemental_Information:
    Information for the pertinent USGS/CMG field activities are online at

    <http://walrus.wr.usgs.gov/infobank/p/p195mb/html/p-1-95-mb.meta.html>
    <http://walrus.wr.usgs.gov/infobank/p/p295mb/html/p-2-95-mb.meta.html>
    <http://walrus.wr.usgs.gov/infobank/m/m195mb/html/m-1-95-mb.meta.html>
    <http://walrus.wr.usgs.gov/infobank/j/j295mb/html/j-2-95-mb.meta.html>
    <http://walrus.wr.usgs.gov/infobank/j/j695mb/html/j-6-95-mb.meta.html>
    <http://walrus.wr.usgs.gov/infobank/m/m295mb/html/m-2-95-mb.meta.html>
    <http://walrus.wr.usgs.gov/infobank/m/m196mb/html/m-1-96-mb.meta.html>
    <http://walrus.wr.usgs.gov/infobank/j/j696mb/html/j-6-96-mb.meta.html>
    <http://walrus.wr.usgs.gov/infobank/j/j796mb/html/j-7-96-mb.meta.html>
    <http://walrus.wr.usgs.gov/infobank/j/j197mb/html/j-1-97-mb.meta.html>
    <http://walrus.wr.usgs.gov/infobank/j/j397mb/html/j-3-97-mb.meta.html>
    <http://walrus.wr.usgs.gov/infobank/m/m497mb/html/m-4-97-mb.meta.html>
    <http://walrus.wr.usgs.gov/infobank/j/j398mb/html/j-3-98-mb.meta.html>
    <http://walrus.wr.usgs.gov/infobank/m/m198sc/html/m-1-98-sc.meta.html>
    <http://walrus.wr.usgs.gov/infobank/a/a498mb/html/a-4-98-mb.meta.html>

    Related USGS work in the Monterey Bay National Marine Sanctuary are online at

    <http://walrus.wr.usgs.gov/mbms>.

    Although this Federal Geographic Data Committee-compliant metadata file is intended to document the data set in nonproprietary form, as well as in ARC/INFO format, this metadata file may include some ARC/INFO-specific terminology.

  1. How should this data set be cited?

    Eittreim, Stephen L. , Anima, Roberto J. , Stevenson, Andrew J. , and Wong, Florence L. , 20000915, Polygon coverage MBGEOLSE for Seafloor rocks and sediments of the continental shelf from Monterey Bay to Point Sur, California: USGS Miscellaneous Field Studies Map MF-2345, U.S. Geological Survey, Menlo Park, CA.

    Online Links:

  2. What geographic area does the data set cover?

    West_Bounding_Coordinate: -122.38432
    East_Bounding_Coordinate: -121.79294309
    North_Bounding_Coordinate: 37.11288919
    South_Bounding_Coordinate: 36.22982869

  3. What does it look like?

    <http://geopubs.wr.usgs.gov/open-file/of01-179/images/geombgeolse.gif> (GIF)
    location map of eqreloc

  4. Does the data set describe conditions during a particular time period?

    Calendar_Date: 01-Sep-2000
    Currentness_Reference: Ground Condition

  5. What is the general form of this data set?

    Geospatial_Data_Presentation_Form: 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):

      • GT-polygon composed of chains (2126)

    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: 0.000
      False_Northing: -500000

      Planar coordinates are encoded using coordinate pair
      Abscissae (x-coordinates) are specified to the nearest 3.224549805355
      Ordinates (y-coordinates) are specified to the nearest 3.224549805355
      Planar coordinates are specified in meters

      The horizontal datum used is North American Datum of 1983.
      The ellipsoid used is Geodetic Reference System 80.
      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:

    >MBGEOLSE.PAT:     polygon attribute table
    COLUMN   ITEM NAME        WIDTH OUTPUT  TYPE N.DEC  ALTERNATE NAME
        1  AREA                   8    18     F      5
        9  PERIMETER              8    18     F      5
       17  MBGEOLSE#              4     5     B      -
       21  MBGEOLSE-ID            4     5     B      -
       25  GRID-CODE              4     8     B      -
       29  TAG                    2     4     B      -
    
    AREA, PERIMETER:  of polygons in square meters, meters, respectively
    MBGEOLSE#:        unique internal control number
    MBGEOLSE-ID:      user-assigned sequence number
    GRID-CODE:        value keyed to lookup table MBGEOLSE.PLUT below
    TAG:              flag to label polygon during plotting
    
    >MBGEOLSE.AAT:       arc attribute table
    COLUMN   ITEM NAME        WIDTH OUTPUT  TYPE N.DEC  ALTERNATE NAME
        1  FNODE#                 4     5     B      -
        5  TNODE#                 4     5     B      -
        9  LPOLY#                 4     5     B      -
       13  RPOLY#                 4     5     B      -
       17  LENGTH                 8    18     F      5
       25  MBGEOLSE#              4     5     B      -
       29  MBGEOLSE-ID            4     5     B      -
       33  LTYPE                 15    15     C      -
    
    FNODE#, TNODE#  starting, ending node of arc, respectively
    LPOLY#, RPOLY#  polygon to left, right, respectively, of arc
    LENGTH          length of arc in meters
    MBGEOLSE#:        unique internal control number
    MBGEOLSE-ID:      user-assigned sequence number
    LTYPE:            line type: contact, scratch, fault
    
    >MBGEOLSE.PLUT:       polygon symbol lookup table
    COLUMN   ITEM NAME        WIDTH OUTPUT  TYPE N.DEC  ALTERNATE NAME
        1  GRID-CODE              4     8     B      -
        5  DESCRIPTION           35    25     C      -
       40  AGE                   26    26     C      -
       66  PTYPE                  5     5     C      -
         **  REDEFINED ITEMS  **
       66  LABEL                  5     5     C      -
    
    Record  GRID-CODE DESCRIPTION               AGE
    
    PTYPE
         1        -9  nodata
         2         1  Monterey Formation        Miocene                    Tm
         3         2  mud and fine sand         Quaternary
    
    Qmud
         4         3  coarse sands              Quaternary
    
    Qsd
         5         4  granitic rock             Late Cretaceous
    
    Kgr
         6         5  pipeline
         7         8  relict gravels and sands  Quaternary
    
    Qgv
         8         9  Santa Cruz Mudstone       late Miocene
    
    Tsc
         9        10  Purisima Formation        Pliocene and Miocene       Tp
        10        13  Aromas Sand               Quaternary                 Qa
        11        15  Rocks of Sur platform     Tertiary and Cretaceous
    
    TKu
        12        28  Vaqueros(?) Formation     Miocene and late Oligocene
    
    Tv(?)
    
    
    Entity_and_Attribute_Detail_Citation:
    none


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?

    Bathymetric data from National Oceanic and Atmospheric Administration (NOAA) / National Ocean Service (NOS) multibeam swath soundings for depths greater than 100 m and from the NOS Hydrographic Data Base (NOAA, 1998) for shallower depths were gridded at 2-second intervals with GMT's (Wessel and Smith, 1998) surface algorithm and smoothed with Arcinfo (ESRI, 1998) filter methods. Contour lines were generated from the resulting 50-m grid. The grid of bathymetric data was merged with USGS 30-m DEMs to calculate the shaded relief image, which has a 2X vertical exaggeration.

    NOAA, 1998, NOS Hydrographic Survey Data, US Coastal Waters: Boulder, CO, World Data Center for Marine Geology & Geophysics, Data Announcement 98-MGG-03, CD-ROM Set, Version 4.0 <http://www.ngdc.noaa.gov/mgg/bathymetry/hydro.html>.

    Wessel, P., and Smith, W. H. F., 1998, New, improved version of Generic Mapping Tools released: EOS Transactions of the American Geophysical Union, v. 79 (47), p. 579 <http://www.soest.hawaii.edu/gmt/>.

  3. To whom should users address questions about the data?

    United States Geological Survey (USGS),
    c/o Florence L. Wong
    Geologist, GIS Coordinator
    USGS, MailStop 999, 345 Middlefield Road
    Menlo Park, CA 94025-3561
    USA

    (650) 329-5327 (voice)
    (650) 329-5190 (FAX)
    fwong@usgs.gov


Why was the data set created?

These data are intended for science researchers, students, policy makers, and the general public.


How was the data set created?

  1. From what previous works were the data drawn?

    none (source 1 of 1)
    United States Geological Survey, Coastal and Marine Geology (CMG), Flore, 20000915, Polygon coverage MBGEOLSE for Seafloor rocks and sediments of the continental shelf from Monterey Bay to Point Sur, California: USGS Miscellaneous Field Studies USGS MF-2345, U.S. Geological Survey, Menlo Park, CA.

    Online Links:

    Type_of_Source_Media:
    Sidescan sonar images with pixel resolutions ranging from 0.4 to 2.5 meters
    Source_Contribution: bottom types interpreted in Adobe Photoshop

  2. How were the data generated, processed, and modified?

    Date: 30-Jan-1998 (process 1 of 20)
    FLW = Florence L. Wong; SLE = Stephen L. Eittreim SLE interpreted units of sonar block 1 over sidescan image in Adobe Photoshop as a TIFF image. FLW converted Adobe Photoshop TIFF to polygon coverage blk1p.

    Date: 09-Feb-1998 (process 2 of 20)
    SLE interpreted units of sonar block 2 over sidescan image in Adobe Photoshop as a TIFF image. FLW converted Adobe Photoshop TIFF to polygon coverage blk2p.

    Date: 11-Feb-1998 (process 3 of 20)
    SLE re-interpreted units of sonar blocks 1 and 2 over sidescan image in Adobe Photoshop. FLW converted Adobe Photoshop TIFF to polygon coverages blk1p and blk2p.

    Date: 27-Feb-1998 (process 4 of 20)
    SLE interpreted units of sonar block 3 over sidescan image in Adobe Photoshop. FLW converted Adobe Photoshop TIFF to polygon coverage blk3p; combined blocks 1, 2, 3 as scshelf.

    Date: 11-Mar-1998 (process 5 of 20)
    SLE interpreted units of sonar block 4 over sidescan image in Adobe Photoshop. FLW converted Adobe Photoshop TIFF to polygon coverage blk4p and joined to scshelf.

    Date: 25-Mar-1998 (process 6 of 20)
    SLE interpreted units of sonar blocks off Seaside over sidescan image in Adobe Photoshop. FLW converted Adobe Photoshop TIFF to polygon coverage montp.

    Date: 01-Jul-1998 (process 7 of 20)
    SLE interpreted units of sonar blocks 1 and 5 over sidescan image in Adobe Photoshop. FLW converted Adobe Photoshop TIFF to polygon coverage blk15p.

    Date: 16-Jul-1998 (process 8 of 20)
    SLE interpreted units of sonar blocks 2 and 6 over sidescan image in Adobe Photoshop. FLW converted Adobe Photoshop TIFF to polygon coverage blk26gp.

    Date: 23-Jul-1998 (process 9 of 20)
    SLE interpreted units of sonar blocks 7 and 8 over sidescan image in Adobe Photoshop. FLW converted Adobe Photoshop TIFF to polygon coverage and merged with scshelf as blk3478p.

    Date: 20-Aug-1998 (process 10 of 20)
    SLE revised units of sonar blocks 1 and 5 over sidescan image in Adobe Photoshop. FLW converted Adobe Photoshop TIFF to polygon coverage blk15p.

    Date: 26-Aug-1998 (process 11 of 20)
    SLE interpreted units of sonar blocks 10 and 11 over sidescan image in Adobe Photoshop. FLW converted Adobe Photoshop TIFF to polygon coverage blk1011gp

    Date: 10-Sep-1998 (process 12 of 20)
    SLE interpreted units of sonar block 9 and gap between blocks 3 and 7 over sidescan image in Adobe Photoshop. FLW converted Adobe Photoshop TIFF to polygon coverages blk9gp and blk37gapp; combined blk15gp and blk9gp as blk159p.

    Date: 14-Dec-1998 (process 13 of 20)
    SLE interpreted units of sonar block 15 over sidescan image in Adobe Photoshop. FLW converted Adobe Photoshop TIFF to polygon coverage blk15ip.

    Date: 05-Mar-1999 (process 14 of 20)
    SLE interpreted units of sonar blocks 12, 13, and surshelf over sidescan backscatter and shaded relief images in Adobe Photoshop. Wilson Lee (WL) converted Adobe Photoshop TIFF to polygon coverages and combined all polygon blocks into coverage ALLBLK.

    Date: 23-Apr-1999 (process 15 of 20)
    FLW exported interim version named MBGEOLSE to Norman Maher, Gary Greene, MBARI

    Date: 16-Jul-1999 (process 16 of 20)
    WL made further revisions as ALLBLKFINAL

    Date: 11-Jan-2000 (process 17 of 20)
    WL made further revisions as MB_POLY

    Date: 11-Jan-2000 (process 18 of 20)
    FLW made further revisions as MBGEOLSE; submitted to peer review.

    Date: 02-Oct-2006 (process 19 of 20)
    FLW made further revisions per reviews.

    Date: 30-Aug-2000 (process 20 of 20)
    First draft of metadata created by Florence Wong using FGDCMETA.AML ver. 1.33 07/15/99 on ARC/INFO data set /we/florence/mont.eitt2/dirsonar/mbgeolse

  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?

    Identified as best available version.

  2. How accurate are the geographic locations?

    The side-scan sonar mosaics on the shelf north of Monterey Canyon have a pixel resolution of 0.4 m for the inner shelf and 0.8 m for the outer shelf. Although this pixel resolution allows us to resolve relatively small features on the seafloor, the accuracy of pixel location is considerably poorer than this due to inaccuracies in navigating the fish towed behind the ship for the northern surveys. The southern-shelf data, which were collected with hull-mounted systems, were processed at pixel resolutions of 2.5 m for backscatter and 5 m for bathymetry. The estimated navigational accuracy in pixel location is 50 m for the northern shelf data and 10 m for the southern shelf data. See Eittreim and others (in press) for a fuller discussion of the navigational accuracy and acoustic systems.

    Interpretation was done at the scale of 2.4 m per pixel. At an image resolution of 72 dpi, common to most video screens, this represents a scale of 1:6,800.

  3. How accurate are the heights or depths?

  4. Where are the gaps in the data? What is missing?

    Regional data coverage is limited by location of the survey lines. On the northern shelf from the sheltered area around Santa Cruz northwest to Point Ano Nuevo, the innermost survey lines were run into water depths as shallow as 5 meters. However in most other areas, shallowest lines were at about the 10 meter isobath, leaving a significant data gap to the shoreline. Interior gaps in the interpreted coverage are due to missing sidescan data, whether from non-overlapping tracklines, instrument failure, or corrupted data files.

  5. How consistent are the relationships among the observations, including topology?

    Polygon and chain-node topology present. Every polygon has a label and all polygons are closed. Every line has a label.


How can someone get a copy of the data set?

Are there legal restrictions on access or use of the data?

Access_Constraints:
Physical source materials are under controlled, on-site access.

If available, access to physical samples is described in the "WR CMG Sample Distribution Policy" at <http://walrus.wr.usgs.gov/infobank/bear/programs/html/main/sample>- dist-policy.html>.

Use_Constraints:
Please recognize the U.S. Geological Survey (USGS) as the source of this information.

Although these data have been used by the U.S. Geological Survey, U.S. Department of the Interior, no warranty expressed or implied is made by the U.S. Geological Survey as to the accuracy of the data.

The act of distribution shall not constitute any such warranty, and no responsibility is assumed by the U.S. Geological Survey in the use of this data, software, or related materials.

This information is not intended for navigational purposes.

Any use of trade, firm, or product names is for descriptive purposes only and does not imply endorsement by the U.S. Government.

  1. Who distributes the data set? (Distributor 1 of 1)

    United States Geological Survey (USGS),
    c/o Florence L. Wong
    Geologist, GIS Coordinator
    USGS, MailStop 999, 345 Middlefield Road
    Menlo Park, CA 94025-3561
    USA

    (650) 329-5327 (voice)
    (650) 329-5190 (FAX)
    fwong@usgs.gov

  2. What's the catalog number I need to order this data set?

  3. What legal disclaimers am I supposed to read?

    Please recognize the U.S. Geological Survey (USGS) as the source of this information.

    Although these data have been used by the U.S. Geological Survey, U.S. Department of the Interior, no warranty expressed or implied is made by the U.S. Geological Survey as to the accuracy of the data.

    The act of distribution shall not constitute any such warranty, and no responsibility is assumed by the U.S. Geological Survey in the use of this data, software, or related materials.

  4. How can I download or order the data?


Who wrote the metadata?

Dates:
Last modified: 30-Aug-2000
Last Reviewed: May-2001

Metadata author:
United States Geological Survey (USGS),
c/o Florence L. Wong
Geologist, GIS Coordinator
USGS, MailStop 999, 345 Middlefield Road
Menlo Park, CA 94025-3561
USA

(650) 329-5327 (voice)
(650) 329-5190 (FAX)
fwong@usgs.gov

Metadata standard:
FGDC Content Standards for Digital Geospatial Metadata (FGDC-STD-001-1998)


http://geopubs.wr.usgs.gov/open-file/of01-179/data/geology/mbgeolse_faq.html
Maintained by: Florence L. Wong
Last modified: Jul 2, 2001 (flw)
USGS Privacy Statement   |   Disclaimer
Department of the Interior   U.S. Geological Survey   Geologic Division   Western Region Coastal & Marine Geology
Generated by mp version 2.7.9 on Mon Jul 2 14:08:48 2001