<?xml version="1.0"?>
<!--<!DOCTYPE metadata SYSTEM "http://www.esri.com/metadata/esriprof80.dtd">-->
<metadata xml:lang="en"><Esri><CreaDate>20060818</CreaDate><CreaTime>16565500</CreaTime><SyncOnce>FALSE</SyncOnce><SyncDate>20040914</SyncDate><SyncTime>19360800</SyncTime><ModDate>20060818</ModDate><ModTime>16354000</ModTime><MetaID>{ABDF2D54-8846-4B85-B5E6-99E0BFA2CFCD}</MetaID><PublishedDocID>{78F58497-20C0-4774-88C7-BE530492D244}</PublishedDocID><PublishStatus>Published</PublishStatus></Esri><idinfo><native Sync="TRUE">Microsoft Windows 2000 Version 5.0 (Build 2195) Service Pack 4; ESRI ArcCatalog 8.3.0.800</native><descript><langdata Sync="TRUE">en</langdata><abstract>California coastwide bathymetric Digital Elevation Model (DEM) at 200 meter resolution with depth values in decimeters.  This DEM is a resampled mosaic of smaller, tiled DEMs produced from source data of varying densities.  Offshore coverage is approximately out to the Exclusive Economic Zone (EEZ) boundary.  An small inland buffer of coastal terrestrial values coded to zero is included for cartographic overlap.

Nearshore depths were produced from NOS Hydrographic Survey data with a tidal datum of mean lower low water (MLLW).  Far offshore areas were produced from U.S. Geological Survey depth contours with no documented tidal datum.

Please see the provided Bathymetry Project documentation for further information.</abstract><purpose>Assess depths for the California coast.</purpose><supplinf>-- BEGIN EXCERPTS FROM BATHYMETRY PROJECT DOCUMENTATION -- 

        California Department of Fish and Game
                   BATHYMETRY PROJECT      
                     Second Edition
                                        
This document provides an overall description of the 
California Department of Fish and Game (DFG) bathymetry 
development project, including source datasets, processes 
used, and resulting products.  

The bathymetry data are not suitable for navigation.
DFG makes no warranty as to the suitability of the
bathymetry data, and any project-related datasets, for
any purpose.

In addition to this readme file, other documentation files
(text, XML, etc.) may accompany datasets related to this 
project.


ACKNOWLEDGEMENTS

The bathymetry processing methods and documentation
were originally developed by the State of California
Stephen P. Teale Data Center, GIS Solutions Group (Teale)
under DFG direction.  Key Teale staff involved in the
project included Andy Richardson and Virginia Wong-Coppin. 


REVISIONS

A second edition of the bathymetry data was completed by
DFG in August 2002. The second edition data were processed
using ARC/INFO GIS software in a Windows 2000 operating
system environment and included the following enhancements:
- Correction or exclusion of over 1700 miscoded and
suspicious Hydrographic Surveys used in the bathymetry 
development process.
- Replacement of older U.S. Geological Survey 7.5-minute 
terrestrial elevation data with the newer/higher-quality 
National Elevation Dataset (NED) for use in nearshore 
bathymetry interpolation.
- Minor adjustments to some of the ARC/INFO software
ARC Macro Language (AML) scripts and resolution zone
boundaries used to process the bathymetry data.


GEOGRAPHIC AREA 

Bathymetry was developed to cover most of the 200 nautical
mile Exclusive Economic Zone (EEZ) off the coast of
California.  The actual extent of data is slightly beyond 
this zone in some areas to account for the 100 kilometer
tiles used to process source data (some tiles extend beyond
the EEZ boundary by as much as almost a tile width, or less
than 100 KM).  To the east, the coverage includes many major
inlets along the coast.  The tiles also extend north and
south of California by less than 1 tile height.


RESULTING PRODUCTS

Initially a single coastwide Digital Elevation Model (DEM)
was evisioned to be the product resulting from this project.
Upon commencing the project it became evident that due to
the nature of the source data multiple datasets were
appropriate. These include:

1.  Coastwide 25, 50, 100, and 200 meter zonal DEMs
2.  5 meter zonal DEMs for localities supported by 
    high-density source data
3.  Tiled 5, 25, 50, 100, and 200 meter zonal DEMs
4.  Tiled 25 meter base DEMs

The coastwide 25-200 meter zonal DEMs are based on the fact
that there is a wide variation in the density of the source
data.  Where data were dense, a 25 meter zonal DEM was
generated.  Where data were sparse, a 200 meter zonal DEM
was generated.  The 50 and 100 meter zonal DEMs represent
intermediate densities.  Though "coastwide", data in these
DEMs do not overlap, however together they cover the entire
study area.  These 25, 50, 100, and 200 meter "zones" were
defined by plotting the source data on paper, visually
identifying and hand drafting zone boundaries based on data
density, then capturing the boundaries in digital format.

The 5 meter zonal DEMs correspond to areas where source data 
are particularly dense.  These areas were identified by
visually scanning the source data on-screen, and "heads up"
digitizing the boundaries.  These DEMs differ from the 25-200
meter zonal DEMs in that they were processed using different
tolerances and that they were not merged into a single
coastwide zonal DEM (due to resolution / storage constraints).
These DEMs are available named by geographic localities or as
tiled data.

The tiled 5-200 meter zonal DEMs are simply the coastwide
zonal DEMs (or individual 5 meter zonal DEMs) clipped to a 
7500 meter buffered tile extent and stored in the tile
directory.  This makes it easy for a user to find DEMs of
all available resolutions for a single tile.  Tile directories
store only those resolutions that cover the tile.

The tiled 25 meter base DEMs are intermediate products used
to generate the 25-200 meter zonal DEMs.  These have proven
useful as a source for generating contours and depth range
polygons.  They are also useful for visualizing and analyzing
small geographic areas, though the user must understand that
the source data do not necessarily support 25 meter resolution.
These DEMs are tile-wide in extent, and are available clipped
to the tile boundary (dembase) and buffered 7500 meters beyond
the tile (dembaseb).

An available georeferenced map image (bathy_map.jpg with 
bathy_map.jgw world file) shows spatial distribution, tile
numbers, and resolution zones of the DEM data.


SOURCE DATA

Four sources of depth/elevation data were used to create the
bathymetric DEMs:

1. Hydrographic Survey Data version 4.0, National Ocean
   Service (NOS), National Oceanic and Atmospheric
   Administration, U.S. Department of Commerce.
   Dataset name = hydsura (ESRI coverage format).
2. U.S. Geological Survey bathymetric contours for the 
   California EEZ - 100m contours from 200m to maximum depth.
   Dataset name = eezbata (ESRI coverage format).
3. 30 meter terrestrial DEM based on the National Elevation
   Dataset (NED), U.S. Geological Survey, U.S. Department of
   the Interior.  Dataset name = dema (ESRI grid format).
4. 1:24,000-scale State of California Coastline, State
   Lands Commission, State of California.  Dataset name =
   rawclipa (ESRI coverage format).

The NOS Hydrographic Surveys were the primary nearshore
depth data used to create the bathymetric DEMs.  These
data represent multiple historical ship transects and were
imported to ARC/INFO as a set of over 6 million points.
Sampling density is quite variable, as close as a few
meters in inland bays and as far apart as hundreds or
thousands of meters away from the coast.  The Hydrographic
Surveys were processed as-is and not filtered to model a
particular range of dates.

The U.S. Geological Survey bathymetric contours were
provided by the U. S. Geological Survey Coastal and Marine
Geology Team.  The original dataset known as "eezbatcall"
was reprojected by DFG to the California (Teale) Albers
projection.  The coverage provided contours from 200 meters
to maximum depth for the California EEZ area.  The contours
were digitized from various small-scale (approximately
1:1,000,000) U.S. Geological Survey maps.

The 30 meter terrestrial DEM was used to allow continuous
gridding along the coast.  Though there is no land area
included in the resulting products, the bathymetry gridding
process requires sampling data beyond the edge of the
resulting grid to smoothly interpolate depth/elevation
along the edge.  The NED terrestrial DEM data were
distributed by the U.S. Geological Survey then processed
and re-distributed by Teale.

The 1:24,000 coastline was used to define land and water
areas and as source depth points of "0".  This results in
a well-defined coastline in the bathymetric DEMs.  The
original State Lands Commission coastline coverage was
modified by Teale for project purposes.


PROCESSING DATA

In addition to the source depth/elevation data, a number of
datasets were used to control processing.  These include:

1.  TILE100KM
2.  RES_ZONES
3.  RAWCLIPA
4.  M5_ZONES

TILE100KM is a set of 100 kilometer square (10,000 square
kilometers) tiles used to split the entire EEZ into 75
managable processing areas.  Many of the resulting datasets
are also stored by these tiles.

RES_ZONES are zones corresponding to the density of source
data that were used to determine the resolution of the
resulting zonal DEMs (5, 25, 50, 100, and 200 meters).

RAWCLIPA contains a set of polygons that define which areas
are water and which areas are land.  This dataset serves two
functions in the gridding process.  Coastlines are
extracted, converted to a set of points with a depth value
of "0", merged with the Hydrographic Surveys, U.S. Geological
Survey bathymetric contours, terrestrial DEMs, and gridded. 
When gridding is complete, land polygons are pulled from this 
dataset and used to blank out the resulting DEM.

M5_ZONES are areas where the Hydrographic Surveys support 5
meter gridding.  The final products include a single 5 meter
zonal DEM for each polygon in this dataset.


PROCESSING METHODOLOGY

The primary engine behind the gridding process is the
ARC/INFO TOPOGRID tool.  TOPOGRID uses an iterative finite
difference interpolation technique that is essentially a
discretized thin plate spline technology.  It is based upon
the ANUDEM program developed my Michael Hutchinson.  The
online help for TOPOGRID contains the following references:

  Hutchinson, M.F. 1988.  Calculation of hydrologically
  sound digital elevation models.  Third International
  Symposium on Spatial Data Handling, Sydney.  Columbus,
  Ohio: International Geographic Union.

  Hutchinson, M.F. 1989.  A new procedure for gridding
  elevation and stream line data with automatic removal of
  spurious pits.  Journal of Hydrology: 106, 211-232.

  Hutchinson, M.F. and Dowling, T.I. 1991.  A continental
  hydrological assessment of a new grid-based digital
  elevation model of Australia.  Hydrological Processes 5:
  45-58.

  Hutchinson, M.F. 1993.  Development of a continent-wide
  DEM with applications to terrain and climate analysis.
  In: M.F. Goodchild et al (eds), Environmental Modeling
  with GIS.  New York, Oxford University Press: 392-399.

  Wahba, G.  1990.  Spline models for Observational data.
  CBMS-NSF Regional Conference Series in Applied
  Mathematics, Philadelphia: Soc. Ind. Appl. Maths.

The following TOPOGRID parameters were used to create the
25-200 meter DEMs:
DATATYPE SPOT
ENFORCE OFF
ITERATIONS 30
TOLERANCES 2.5 1.5 10
XYZLIMITS %LIMITS% (%LIMITS% = bounding box of buffered 
                   tile)

The following TOPOGRID parameters were used to create the
5 meter DEMs:
BOUNDARY XXZONE  (XXZONE is the 5 meter zone polygon)
DATATYPE SPOT
ENFORCE OFF
ITERATIONS 30
TOLERANCES 2.5 1.5 2.5
XYZLIMITS %LIMITS%  (%LIMITS% is 50 meters beyond the 5
                     meter zone polygon bounding box)

The processing logic applied to each of the 75 tiles to
create the 25-200 meter DEMs was:
- Receive the tile number to process
- Create a results directory corresponding to the tile 
  number
- Extract the tile from TILE100KM
- Buffer the tile 10 KM
- Using the buffered tile, clip out:
  - RES_ZONES
  - RAWCLIPA (land water polygons)
  - Hydrographic Surveys
  - Coastlines (from RAWCLIPA)
    - Convert to points
  - Terrestrial DEM (if tile covers land area)
    - Convert to points
  - U. S. Geological Survey bathymetric contours (if tile 
    covers 200 meter zone)
- Merge all point coverages
- Run TOPOGRID to create 25 meter DEM covering buffered tile 
  area
- Blank out land areas
- Clip to 7500 meters beyond tile boundary; store in tile 
  directory
- Clip to tile boundary; store in tile directory
- For each resolution zone covered by the tile:
  - Clip out area from buffered DEM
  - Resample to appropriate resolution for zone (using bilinear
    interpolation)
  - Blank out land areas
  - Store in tile directory

The process used to create the 5 meter DEMs is:
- For each polygon in M5_ZONES:
  - Create a coverage containing a single rectangle polygon
    50 meters (10 5 meter cells) larger than the zone 
    polygon
  - Using the rectangle, clip out:
    - RAWCLIPA (land water polygons)
    - Hydrographic Surveys
    - Coastlines (from RAWCLIPA)
      - Convert to points
    - Terrestrial DEM (if tile covers land area)
      - Convert to points
  - Merge the resulting point coverages
  - Run TOPOGRID to create 5 meter DEM covering the 
    rectangle
  - Blank out land areas
  - Clip to extent of the zone polygon

After the original tiled 25 meter base DEMs were created
by Teale, shaded reliefs were generated and visually 
inspected.  Miscoded points that resulted in spurious pits
or spikes were identified and coded as such.  After all 
errors were corrected for a tile, the DEMs for the tile 
were re-created and re-inspected.

DATA QUALITY ASSESSMENT

The following are subjective comments regarding the data.

Because the bathymetry data were generated from a variety 
of sources at varying scales, overall accuracy is difficult
to assess.  The data have not been thoroughly reviewed.
Depth values should be corroborated with other sources.

Some "artifacts" are present in the data, and may be 
especially noticeable along resolution zone and tile
boundaries where differing data sources may not have
provided a smooth interpolation transition.  Additional
errors may be present.

Source Hydrographic Survey data originated from many
historical surveys and thus do not necessarily represent
current hydrologic conditions.  For accuracy assessments
of Hydrographic Survey data, please reference the
documentation for that product.

DEM depth values are of particular questionable quality
in the following areas.  Other problem areas may exist.

- Nearshore areas north of Mack Pt. (southern Oregon).
Source terrestrial elevation data was missing for 
this area but depth values were still interpolated
to the shoreline.

- Nearshore, Gulf of the Farallones area, south of Stormy
Stack and north of Muir Beach out to about -25 meters 
depth.  Source depth data was missing for this area but 
depth values were still interpolated to the shoreline.

- Nearshore areas south of the California border
out to -200 meters depth.  Source depth and terrestrial
elevation data were missing for this area but depth 
values were still interpolated to the shoreline.

- Any depth values outside of the gridding resolution
zones.  Cross-reference the "tile100km" and "res_zones"
coverages used in data processing to determine areas
within tiled DEMs that are outside the resolution zones.
The georeferenced map image (bathy_map.jpg with 
bathy_map.jgw world file) can also be used for this
purpose.

- San Diego Bay.  Source data were missing for portions
of the bay but depth values were still interpolated.

Readme Version 2002.08.23

-- END EXCERPTS FROM BATHYMETRY PROJECT DOCUMENTATION --</supplinf></descript><citation><citeinfo><origin>National Ocean Service - National Oceanic and Atmospheric Administration</origin><title>Bathymetric DEM, 200 Meter Resolution (Depth Values in Decimeters)</title><ftname Sync="TRUE">bdem200m_m</ftname><geoform Sync="TRUE">raster digital data</geoform><origin>U.S. Geological Survey</origin><origin>California Department of Fish and Game</origin><onlink Sync="TRUE">\\Molib01\GIS_Library\Elevation\Water\DEMs\DFG_Bathymetry_Project\bdem200m_d</onlink><pubdate>200208</pubdate></citeinfo></citation><timeperd><timeinfo><sngdate/></timeinfo></timeperd><status><progress>Complete</progress><update>None planned</update></status><spdom><bounding><westbc Sync="TRUE">-129.267938</westbc><eastbc Sync="TRUE">-116.582361</eastbc><northbc Sync="TRUE">42.406405</northbc><southbc Sync="TRUE">31.958108</southbc></bounding><lboundng><leftbc Sync="TRUE">-767395.463585</leftbc><rightbc Sync="TRUE">282204.536415</rightbc><bottombc Sync="TRUE">-639530.466823</bottombc><topbc Sync="TRUE">487469.533177</topbc></lboundng></spdom><keywords><theme><themekt>ISO 19115 Topic Category</themekt><themekey>elevation</themekey><themekey>geoscientificInformation</themekey><themekey>oceans</themekey></theme><theme><themekt>none</themekt><themekey>bathymetry</themekey></theme><place><placekt>none</placekt><placekey>California</placekey></place></keywords><accconst>none</accconst><useconst>The bathymetry data are not suitable for navigation.  DFG makes no warranty as to the suitability of the data for any purpose.</useconst><natvform Sync="TRUE">Raster Dataset</natvform><ptcontac><cntinfo><cntperp><cntper>Will Patterson</cntper><cntorg>California Department of Fish and Game</cntorg></cntperp><cntemail>wpatters@dfg.ca.gov</cntemail></cntinfo></ptcontac></idinfo><dataIdInfo><envirDesc Sync="TRUE">Microsoft Windows 2000 Version 5.0 (Build 2195) Service Pack 4; ESRI ArcCatalog 8.3.0.800</envirDesc><dataLang><languageCode Sync="TRUE" value="en"></languageCode></dataLang><idCitation><resTitle Sync="TRUE">bdem200m_m</resTitle><presForm><PresFormCd Sync="TRUE" value="005"></PresFormCd></presForm></idCitation><spatRpType><SpatRepTypCd Sync="TRUE" value="002"></SpatRepTypCd></spatRpType><dataExt><geoEle><GeoBndBox esriExtentType="native"><westBL Sync="TRUE">-767395.463585</westBL><eastBL Sync="TRUE">282204.536415</eastBL><northBL Sync="TRUE">487469.533177</northBL><southBL Sync="TRUE">-639530.466823</southBL><exTypeCode Sync="TRUE">1</exTypeCode></GeoBndBox></geoEle></dataExt><geoBox esriExtentType="decdegrees"><westBL Sync="TRUE">-129.267938</westBL><eastBL Sync="TRUE">-116.582361</eastBL><northBL Sync="TRUE">42.406405</northBL><southBL Sync="TRUE">31.958108</southBL><exTypeCode Sync="TRUE">1</exTypeCode></geoBox></dataIdInfo><metainfo><langmeta Sync="TRUE">en</langmeta><metstdn Sync="TRUE">FGDC Content Standards for Digital Geospatial Metadata</metstdn><metstdv Sync="TRUE">FGDC-STD-001-1998</metstdv><mettc Sync="TRUE">local time</mettc><metc><cntinfo><cntorgp><cntper>GIS Service Center</cntper><cntorg>California Department of Fish and Game</cntorg></cntorgp><cntaddr/><cntemail>geodata@dfg.ca.gov</cntemail></cntinfo></metc><metd Sync="TRUE">20060818</metd><metextns><onlink Sync="TRUE">http://www.esri.com/metadata/esriprof80.html</onlink><metprof Sync="TRUE">ESRI Metadata Profile</metprof></metextns></metainfo><mdLang><languageCode Sync="TRUE" value="en"></languageCode></mdLang><mdStanName Sync="TRUE">ISO 19115 Geographic Information - Metadata</mdStanName><mdStanVer Sync="TRUE">DIS_ESRI1.0</mdStanVer><mdChar><CharSetCd Sync="TRUE" value="004"></CharSetCd></mdChar><mdHrLv><ScopeCd Sync="TRUE" value="005"></ScopeCd></mdHrLv><mdHrLvName Sync="TRUE">dataset</mdHrLvName><distinfo><resdesc Sync="TRUE">Downloadable Data</resdesc><stdorder><digform><digtinfo><transize Sync="TRUE">20.093</transize><dssize Sync="TRUE">20.093</dssize></digtinfo></digform></stdorder><distrib><cntinfo><cntperp><cntper>GIS Service Center</cntper><cntorg>California Department of Fish and Game</cntorg></cntperp><cntemail>geodata@dfg.ca.gov</cntemail></cntinfo></distrib></distinfo><distInfo><distributor><distorTran><onLineSrc><orDesc Sync="TRUE">002</orDesc><linkage Sync="TRUE">file://\\Molib01\GIS_Library\Elevation\Water\DEMs\DFG_Bathymetry_Project\bdem200m_d</linkage><protocol Sync="TRUE">Local Area Network</protocol></onLineSrc><transSize Sync="TRUE">20.093</transSize></distorTran><distorFormat><formatName Sync="TRUE">Raster Dataset</formatName></distorFormat></distributor></distInfo><spdoinfo><direct Sync="TRUE">Raster</direct><rastinfo><rasttype Sync="TRUE">Grid Cell</rasttype><rowcount Sync="TRUE">5635</rowcount><colcount Sync="TRUE">5248</colcount><rastxsz Sync="TRUE">200.000000</rastxsz><rastysz Sync="TRUE">200.000000</rastysz><rastbpp Sync="TRUE">16</rastbpp><vrtcount Sync="TRUE">1</vrtcount><rastorig Sync="TRUE">Upper Left</rastorig><rastcmap Sync="TRUE">FALSE</rastcmap><rastcomp Sync="TRUE">Default</rastcomp><rastband Sync="TRUE">1</rastband><rastdtyp Sync="TRUE">matrix values</rastdtyp><rastplyr Sync="TRUE">FALSE</rastplyr><rastifor Sync="TRUE">ESRI GRID</rastifor></rastinfo></spdoinfo><spref><horizsys><cordsysn><geogcsn Sync="TRUE">GCS_North_American_1983</geogcsn><projcsn Sync="TRUE">NAD_1983_Albers</projcsn></cordsysn><planar><planci><plance Sync="TRUE">row and column</plance><plandu Sync="TRUE">meters</plandu><coordrep><absres Sync="TRUE">200.000000</absres><ordres Sync="TRUE">200.000000</ordres></coordrep></planci><mapproj><mapprojn Sync="TRUE">Albers Conical Equal Area</mapprojn><albers><stdparll Sync="TRUE">34.000000</stdparll><stdparll Sync="TRUE">40.500000</stdparll><longcm Sync="TRUE">-120.000000</longcm><latprjo Sync="TRUE">0.000000</latprjo><feast Sync="TRUE">0.000000</feast><fnorth Sync="TRUE">-4000000.000000</fnorth></albers></mapproj></planar><geodetic><horizdn Sync="TRUE">North American Datum of 1983</horizdn><ellips Sync="TRUE">Geodetic Reference System 80</ellips><semiaxis Sync="TRUE">6378137.000000</semiaxis><denflat Sync="TRUE">298.257222</denflat></geodetic></horizsys></spref><refSysInfo><RefSystem><refSysID><identCode Sync="TRUE">NAD_1983_Albers</identCode></refSysID></RefSystem></refSysInfo><spatRepInfo><GridSpatRep><numDims Sync="TRUE">2</numDims><axDimProps><Dimen><dimName><DimNameTypCd Sync="TRUE" value="002"></DimNameTypCd></dimName><dimSize Sync="TRUE">5248</dimSize><dimResol Sync="TRUE">200</dimResol></Dimen><Dimen><dimName><DimNameTypCd Sync="TRUE" value="001"></DimNameTypCd></dimName><dimSize Sync="TRUE">5635</dimSize><dimResol Sync="TRUE">200</dimResol></Dimen></axDimProps><cellGeo><CellGeoCd Sync="TRUE" value="002"></CellGeoCd></cellGeo><tranParaAv Sync="TRUE">1</tranParaAv></GridSpatRep></spatRepInfo><eainfo><detailed Name="bdem200m_m"><enttyp><enttypl Sync="TRUE">bdem200m_m</enttypl><enttypt Sync="TRUE">Table</enttypt><enttypc Sync="TRUE">4811</enttypc></enttyp><attr><attrlabl Sync="TRUE">ObjectID</attrlabl><attalias Sync="TRUE">ObjectID</attalias><attrtype Sync="TRUE">OID</attrtype><attwidth Sync="TRUE">4</attwidth><atprecis Sync="TRUE">0</atprecis><attscale Sync="TRUE">0</attscale><attrdef Sync="TRUE">Internal feature number.</attrdef><attrdefs Sync="TRUE">ESRI</attrdefs><attrdomv><udom Sync="TRUE">Sequential unique whole numbers that are automatically generated.</udom></attrdomv></attr><attr><attrlabl Sync="TRUE">Value</attrlabl><attalias Sync="TRUE">Value</attalias><attrtype Sync="TRUE">Integer</attrtype><attwidth Sync="TRUE">0</attwidth><atprecis Sync="TRUE">0</atprecis><attscale Sync="TRUE">0</attscale></attr><attr><attrlabl Sync="TRUE">Count</attrlabl><attalias Sync="TRUE">Count</attalias><attrtype Sync="TRUE">Double</attrtype><attwidth Sync="TRUE">0</attwidth><atprecis Sync="TRUE">0</atprecis><attscale Sync="TRUE">0</attscale></attr></detailed></eainfo><mdDateSt Sync="TRUE">20060818</mdDateSt><dataqual><complete>Please see the provided Bathymetry Project documentation.</complete><lineage><procstep><proccont><cntinfo><cntperp><cntper>Will Patterson</cntper><cntorg>California Department of Fish and Game</cntorg></cntperp><cntemail>geodata@dfg.ca.gov</cntemail></cntinfo></proccont><procdesc>Converted to NAD83 (ArcInfo Workstation 9.1 PROJECTGRID command using bilinear interpolation), metadata edited.</procdesc><procdate>200608</procdate></procstep></lineage></dataqual><distinfo><distrib><cntinfo><cntperp><cntper>Marine Region GIS</cntper><cntorg>California Department of Fish and Game</cntorg></cntperp><cntemail>MR_GIS@dfg.ca.gov</cntemail></cntinfo></distrib></distinfo><Binary><Thumbnail><Data EsriPropertyType="Picture">Qk3uNwEAAAAAADYAAAAoAAAAyAAAAIUAAAABABgAAAAAALg3AQAAAAAAAAAAAAAAAAAAAAAA////
[encoded data, 106324 characters]
////////////////////////////////////////////////////////////////////////</Data></Thumbnail></Binary></metadata>
