<?xml version="1.0" encoding="UTF-8"?><ns1:descriptiveReport xmlns:ns1="http://svn.pydro.noaa.gov/2016/01/DescriptiveReport" xmlns:ns2="http://svn.pydro.noaa.gov/2016/01/AllGlobalTypes" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://svn.pydro.noaa.gov/2016/01/DescriptiveReport http://svn.pydro.noaa.gov/2016/01/DR.xsd"><ns1:metadata><ns1:projectMetadata><ns2:number>OPR-L397-RA-17</ns2:number><ns2:name>Channel Islands and Vicinity, CA</ns2:name><ns2:generalLocality>Channel Islands National Marine Sanctuary</ns2:generalLocality><ns2:fieldUnit>NOAA Ship Rainier</ns2:fieldUnit></ns1:projectMetadata><ns1:registryMetadata><ns2:registryNumber>H13082</ns2:registryNumber><ns2:sheetID>1</ns2:sheetID><ns2:registryInstructions xsi:nil="true"></ns2:registryInstructions><ns2:sublocality>Adams Cove to Westcott Shoal</ns2:sublocality><ns2:stateOrTerritory>California</ns2:stateOrTerritory><ns2:country>United States</ns2:country><ns2:scale>20000</ns2:scale></ns1:registryMetadata><ns1:surveyMetadata><ns2:year>2017</ns2:year><ns2:chiefOfParty>Benjamin K. Evans, CDR/NOAA</ns2:chiefOfParty><ns2:projectType>Navigable Area</ns2:projectType><ns2:PIDate>2017-08-25</ns2:PIDate><ns2:datesOfSurvey><ns2:start>2017-10-06</ns2:start><ns2:end>2017-11-05</ns2:end></ns2:datesOfSurvey><ns2:equipmentTypes><ns2:soundingEquipment>Multibeam Echo Sounder</ns2:soundingEquipment><ns2:imageryEquipment>Multibeam Echo Sounder Backscatter</ns2:imageryEquipment></ns2:equipmentTypes><ns2:acquisition><ns2:units>meters</ns2:units></ns2:acquisition><ns2:horizontalCoordinateSystem zone="10N">Universal Transverse Mercator (UTM)</ns2:horizontalCoordinateSystem><ns2:timeZone>UTC</ns2:timeZone><ns2:verifier>Pacific Hydrographic Branch</ns2:verifier><ns2:titlesheetRemarks><ns2:fieldRemarks xsi:nil="true"></ns2:fieldRemarks><ns2:branchRemarks xsi:nil="true"></ns2:branchRemarks></ns2:titlesheetRemarks></ns1:surveyMetadata><ns1:assignment>NOAA</ns1:assignment></ns1:metadata><ns1:areaSurveyed><ns1:areaDescription><ns2:discussion>The survey area is referred to as H13082, &quot;Adams Cove to Westcott Shoals&quot; (sheet 1) within the Project Instructions. The area encompasses approximately 15 square nautical miles of San Miguel Island's western coast, extending from Oil Point and around Point Bennett to Tyler Bight.</ns2:discussion><ns2:limits><ns2:northWest><ns2:latitude hemisphere="N">34.100911</ns2:latitude><ns2:longitude hemisphere="W">120.486206</ns2:longitude></ns2:northWest><ns2:southEast><ns2:latitude hemisphere="N">33.991197</ns2:latitude><ns2:longitude hemisphere="W">120.391121</ns2:longitude></ns2:southEast></ns2:limits><ns2:images><ns2:caption>H13082 assigned survey area (Chart 18727).</ns2:caption><ns2:link>SupportFiles\A.1 Sheets Limits Final.png</ns2:link></ns2:images><ns2:comments/></ns1:areaDescription><ns1:surveyLimits><ns2:results deviation="true"><ns2:discussion>Data were acquired within the assigned survey limits as required in the Project Instructions and HSSD.</ns2:discussion></ns2:results><ns2:comments/></ns1:surveyLimits><ns1:surveyPurpose><ns2:discussion>The harbors around the Channel Islands National Marine Sanctuary (CINMS) are home to a highly productive abundance of sea life and aquatic habitats that drive a thriving recreational and commercial fishing industry.  The sanctuary also regularly hosts kayakers, divers, surfers, sightseers, whale watchers, researchers, and Channel Islands National Park concessionaires, all of whom access the sanctuary via boats. Additionally, large cargo and tanker vessels transiting from Los Angeles and Long Beach, CA are routed close to CINMS boundaries. The area encompassing survey H13082 is a popular fishing and diving location but has numerous charted foul areas. In addition to providing data for crucial nautical chart updates, this survey will also generate backscatter data that will be used in habitat mapping and substrate analysis. The multibeam and backscatter data collected in this survey will enhance marine navigational safety and aid sanctuary managers, planners, and researchers in their conservation efforts.
</ns2:discussion><ns2:comments/></ns1:surveyPurpose><ns1:surveyQuality><ns2:adequacy>The entire survey is adequate to supersede previous data.</ns2:adequacy><ns2:discussion>Pydro QC Tools 2 Grid QA was used to analyze H13082 multibeam echosounder (MBES) data density. The submitted H13082 variable-resolution (VR) met HSSD density requirements as shown in the histogram below.</ns2:discussion><ns2:images><ns2:caption>Pydro derived plot showing HSSD density compliance of H13082 finalized variable-resolution MBES data.</ns2:caption><ns2:link>SupportFiles\H13082_MB_VR_MLLW_Final.QAv5.density.png</ns2:link></ns2:images><ns2:comments/></ns1:surveyQuality><ns1:surveyCoverage><ns2:coverageRequirement><ns2:waterDepth>All waters in survey areas</ns2:waterDepth><ns2:requiredCoverage>Complete Coverage (refer to HSSD Section 5.2.2.3)</ns2:requiredCoverage></ns2:coverageRequirement><ns2:results deviation="true"><ns2:discussion>Complete multibeam echosounder (MBES) coverage was acquired to the inshore limit of hydrography, the 4-meter Navigable Area Limit Line (NALL). Areas where survey coverage did not meet the NALL or the assigned sheet limits was due to the survey vessel reaching the inshore extent of safe navigation as shown in Figure 3. These areas are characterized as being very near shore and subject to hazards such as dangerous wave action or thick kelp. Survey coverage was extended beyond the assigned sheet limits in the south to junction with the BELL M. SHIMADA survey W00320, which is detailed later in this report.</ns2:discussion><ns2:images><ns2:caption>Example of Navigable Area Limit Line (NALL) determination southwest of Tyler Bight; the blue dashed line indicates assigned sheet limits and yellow indicates where the 4-meter contour was reached.</ns2:caption><ns2:link>SupportFiles\A.1 NALL Determination.png</ns2:link></ns2:images><ns2:images><ns2:caption>Holiday was caused by excessive kelp and unsafe conditions approaching the shoreline. The shoalest sounding recorded around the holiday is 7.9 meters.</ns2:caption><ns2:link>SupportFiles\Holiday 1.png</ns2:link></ns2:images><ns2:images><ns2:caption>Holiday was caused by unsafe conditions over the top of the rock. The shoalest sounding recorded around the holiday is 1.3 meters.</ns2:caption><ns2:link>SupportFiles\Holiday 2.png</ns2:link></ns2:images><ns2:images><ns2:caption>Holiday was caused by unsafe conditions over the top of the rocks. The shoalest sounding recorded around the holiday is 1.7 meters.</ns2:caption><ns2:link>SupportFiles\Holiday 3.png</ns2:link></ns2:images><ns2:images><ns2:caption>Holiday was caused by an acoustic shadow on the downslope side of a rock ledge in the sonar's outer beams. The shoalest sounding recorded on the top of the ledge is 14.9 meters.</ns2:caption><ns2:link>SupportFiles\Holiday 4.png</ns2:link></ns2:images></ns2:results><ns2:comments/></ns1:surveyCoverage><ns1:coverageGraphic><ns2:caption>H13082 MBES coverage and assigned survey limits (Chart 18272). Coverage extends approximately 0.4 nautical miles beyond the southern sheet limits to junction with the BELL M. SHIMADA survey W00320.</ns2:caption><ns2:link>SupportFiles\A.4 Coverage with Scale.png</ns2:link></ns1:coverageGraphic><ns1:surveyStatistics><ns2:LNM><ns2:vesselLNM><ns2:vessel><ns2:hullID>2801</ns2:hullID><ns2:statistics><ns2:MS_SBES>0</ns2:MS_SBES><ns2:MS_MBES>59.93</ns2:MS_MBES><ns2:MS_lidar>0</ns2:MS_lidar><ns2:MS_SSS>0</ns2:MS_SSS><ns2:MS_SBES_MBES>0</ns2:MS_SBES_MBES><ns2:MS_MBES_SSS>0</ns2:MS_MBES_SSS><ns2:MS_SBES_SSS>0</ns2:MS_SBES_SSS><ns2:XL_MBES_SBES>0</ns2:XL_MBES_SBES><ns2:XL_lidar>0</ns2:XL_lidar></ns2:statistics></ns2:vessel><ns2:vessel><ns2:hullID>2802</ns2:hullID><ns2:statistics><ns2:MS_SBES>0</ns2:MS_SBES><ns2:MS_MBES>36.31</ns2:MS_MBES><ns2:MS_lidar>0</ns2:MS_lidar><ns2:MS_SSS>0</ns2:MS_SSS><ns2:MS_SBES_MBES>0</ns2:MS_SBES_MBES><ns2:MS_MBES_SSS>0</ns2:MS_MBES_SSS><ns2:MS_SBES_SSS>0</ns2:MS_SBES_SSS><ns2:XL_MBES_SBES>28.20</ns2:XL_MBES_SBES><ns2:XL_lidar>0</ns2:XL_lidar></ns2:statistics></ns2:vessel><ns2:vessel><ns2:hullID>2803</ns2:hullID><ns2:statistics><ns2:MS_SBES>0</ns2:MS_SBES><ns2:MS_MBES>148.49</ns2:MS_MBES><ns2:MS_lidar>0</ns2:MS_lidar><ns2:MS_SSS>0</ns2:MS_SSS><ns2:MS_SBES_MBES>0</ns2:MS_SBES_MBES><ns2:MS_MBES_SSS>0</ns2:MS_MBES_SSS><ns2:MS_SBES_SSS>0</ns2:MS_SBES_SSS><ns2:XL_MBES_SBES>0</ns2:XL_MBES_SBES><ns2:XL_lidar>0</ns2:XL_lidar></ns2:statistics></ns2:vessel><ns2:vessel><ns2:hullID>2804</ns2:hullID><ns2:statistics><ns2:MS_SBES>0</ns2:MS_SBES><ns2:MS_MBES>142.33</ns2:MS_MBES><ns2:MS_lidar>0</ns2:MS_lidar><ns2:MS_SSS>0</ns2:MS_SSS><ns2:MS_SBES_MBES>0</ns2:MS_SBES_MBES><ns2:MS_MBES_SSS>0</ns2:MS_MBES_SSS><ns2:MS_SBES_SSS>0</ns2:MS_SBES_SSS><ns2:XL_MBES_SBES>7.03</ns2:XL_MBES_SBES><ns2:XL_lidar>0</ns2:XL_lidar></ns2:statistics></ns2:vessel></ns2:vesselLNM><ns2:totalLNM><ns2:MS_SBES>0</ns2:MS_SBES><ns2:MS_MBES>387.06</ns2:MS_MBES><ns2:MS_lidar>0</ns2:MS_lidar><ns2:MS_SSS>0</ns2:MS_SSS><ns2:MS_SBES_MBES>0</ns2:MS_SBES_MBES><ns2:MS_MBES_SSS>0</ns2:MS_MBES_SSS><ns2:MS_SBES_SSS>0</ns2:MS_SBES_SSS><ns2:XL_MBES_SBES>35.23</ns2:XL_MBES_SBES><ns2:XL_lidar>0</ns2:XL_lidar><ns2:percentXLLNM>0</ns2:percentXLLNM></ns2:totalLNM></ns2:LNM><ns2:totalSurveyStats><ns2:bottomSamples>0</ns2:bottomSamples><ns2:maritimeBoundaryPoints>0</ns2:maritimeBoundaryPoints><ns2:DP>14</ns2:DP><ns2:diveOps>0</ns2:diveOps><ns2:SNM>16.11</ns2:SNM></ns2:totalSurveyStats><ns2:surveyDates>2017-10-06</ns2:surveyDates><ns2:surveyDates>2017-10-07</ns2:surveyDates><ns2:surveyDates>2017-10-10</ns2:surveyDates><ns2:surveyDates>2017-10-25</ns2:surveyDates><ns2:surveyDates>2017-10-26</ns2:surveyDates><ns2:surveyDates>2017-11-01</ns2:surveyDates><ns2:surveyDates>2017-11-02</ns2:surveyDates><ns2:surveyDates>2017-11-03</ns2:surveyDates><ns2:surveyDates>2017-11-04</ns2:surveyDates><ns2:surveyDates>2017-11-05</ns2:surveyDates><ns2:discussion xsi:nil="true"></ns2:discussion><ns2:comments/></ns1:surveyStatistics></ns1:areaSurveyed><ns1:dataAcquisitionAndProcessing><ns1:equipmentAndVessels><ns1:discussion>Refer to the Data Acquisition and Processing Report (DAPR) for a complete description of data acquisition and processing systems, survey vessels, quality control procedures and data processing methods.  Additional information to supplement sounding and survey data, and any deviations from the DAPR are discussed in the following sections.</ns1:discussion><ns1:vessels><ns1:vessel><ns2:hullID>2801</ns2:hullID><ns2:LOA units="meters">8.8</ns2:LOA><ns2:draft units="meters">1.1</ns2:draft></ns1:vessel><ns1:vessel><ns2:hullID>2802</ns2:hullID><ns2:LOA units="meters">8.8</ns2:LOA><ns2:draft units="meters">1.1</ns2:draft></ns1:vessel><ns1:vessel><ns2:hullID>2803</ns2:hullID><ns2:LOA units="meters">8.8</ns2:LOA><ns2:draft units="meters">1.1</ns2:draft></ns1:vessel><ns1:vessel><ns2:hullID>2804</ns2:hullID><ns2:LOA units="meters">8.8</ns2:LOA><ns2:draft units="meters">1.1</ns2:draft></ns1:vessel><ns1:vessel><ns2:hullID>1905</ns2:hullID><ns2:LOA units="meters">5.7</ns2:LOA><ns2:draft units="meters">0.35</ns2:draft></ns1:vessel><ns1:vessel><ns2:hullID>1907</ns2:hullID><ns2:LOA units="meters">5.7</ns2:LOA><ns2:draft units="meters">0.35</ns2:draft></ns1:vessel><ns1:images><ns2:caption>NOAA Ship Rainier survey launch 2801 (RA-4).</ns2:caption><ns2:link>SupportFiles\B.1.1 Vessels.png</ns2:link></ns1:images><ns1:discussion>All data for H13082 were acquired by NOAA Ship RAINIER survey launches 2801, 2802, 2803, and 2804. The vessels acquired depth soundings, backscatter imagery, and sound speed profiles. Shoreline verification was conducted from RAINIER skiffs 1905 and 1907.</ns1:discussion><ns1:comments/></ns1:vessels><ns1:equipment><ns1:majorSystem><ns2:manufacturer>Applanix</ns2:manufacturer><ns2:model>POS M/V v5</ns2:model><ns2:type>Positioning and Attitude System</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>Kongsberg</ns2:manufacturer><ns2:model>2040</ns2:model><ns2:type>MBES</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>Reson</ns2:manufacturer><ns2:model>SVP71</ns2:model><ns2:type>Sound Speed System</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>Sea-Bird Electronics</ns2:manufacturer><ns2:model>SBE 19Plus SEACAT Profiler</ns2:model><ns2:type>Conductivity, Temperature, and Depth Sensor</ns2:type></ns1:majorSystem><ns1:discussion xsi:nil="true"></ns1:discussion><ns1:comments/></ns1:equipment><ns1:comments/></ns1:equipmentAndVessels><ns1:qualityControl><ns1:crosslines><ns2:discussion>RAINIER launches 2802 (RA-5) and 2804 (RA-6) acquired 35.23 nautical miles of multibeam crosslines. H13082 crossline data is adequate for verifying and evaluating the internal consistency of survey data. The Compare Grids function in Pydro Explorer analyzed 2-meter resolution surfaces of H13082 crossline only data and combined mainscheme/crossline data. In the difference surface, 99% of nodes met IHO allowable Total Vertical Uncertainty (TVU) standards. Figures 10-13 provide additional results.</ns2:discussion><ns2:images><ns2:caption>H13082 crossline surface overlaid on mainscheme tracklines.</ns2:caption><ns2:link>SupportFiles\B.2.1 Crosslines.PNG</ns2:link></ns2:images><ns2:images><ns2:caption>Pydro derived plot showing percentage-pass value of H13082 mainscheme to crossline data.</ns2:caption><ns2:link>SupportFiles\H13082_MS_2m_MLLW_Final-H13082_XL_2m_MLLW_Final_fracAllowErr_Freq.png</ns2:link></ns2:images><ns2:images><ns2:caption>Pydro derived plot showing absolute difference statistics of H13082 mainscheme to crossline data.</ns2:caption><ns2:link>SupportFiles\H13082_MS_2m_MLLW_Final-H13082_XL_2m_MLLW_Final_depth_delta.png</ns2:link></ns2:images><ns2:images><ns2:caption>Pydro derived plot showing node depth vs. allowable error fraction of H13082 mainscheme to crossline data.</ns2:caption><ns2:link>SupportFiles\H13082_MS_2m_MLLW_Final-H13082_XL_2m_MLLW_Final_fracAllowErr_vsDepth.png</ns2:link></ns2:images><ns2:comments/></ns1:crosslines><ns1:uncertainty><ns2:values><ns2:tideUncertainty><ns2:measured units="meters">0</ns2:measured><ns2:zoning units="meters">0.082867</ns2:zoning><ns2:tideMethod>ERS via VDATUM</ns2:tideMethod></ns2:tideUncertainty><ns2:soundSpeedUncertainty><ns2:hullID>2801, 2802, 2803, 2804</ns2:hullID><ns2:measuredCTD units="meters/second">3</ns2:measuredCTD><ns2:measuredMVP units="meters/second">N/A</ns2:measuredMVP><ns2:surface units="meters/second">0.15</ns2:surface></ns2:soundSpeedUncertainty></ns2:values><ns2:discussion>Total Propagated Uncertainty (TPU) values for survey H13082 were derived from a combination of fixed values for equipment and vessel characteristics, as well as from field assigned values for sound speed uncertainties. Tidal zoning uncertainty of 0.082867 meters was provided in the Project Instructions as part of VDatum. See the 2017 DAPR for further information.

In addition to the usual a priori estimates of uncertainty, some real-time and post-processing uncertainty sources were also incorporated into the depth estimates of this survey. Real-time uncertainties from Kongsberg MBES sonars were recorded and applied in post-processing. Applanix TrueHeave (POS) files, which record estimates of heave uncertainty, were applied during post-processing. Finally, the post-processed uncertainties associated with vessel roll, pitch, yaw, and position were applied in Caris HIPS using SBET and RMS files generated  using POSPac MMS software.

Uncertainty values of the submitted finalized grid was calculated in Caris using &quot;Greater of the Two&quot; of uncertainty and standard deviation (scaled to 95%). Grid QA v5 within Pydro QC Tools 2 was used to analyze H13082 TVU compliance (Fig. 14).</ns2:discussion><ns2:images><ns2:caption>Pydro derived plot showing TVU compliance of H13082 finalized variable-resolution MBES data.</ns2:caption><ns2:link>SupportFiles\H13082_MB_VR_MLLW_Final.QAv5.tvu_qc.png</ns2:link></ns2:images><ns2:comments/></ns1:uncertainty><ns1:junctions><ns2:discussion>Three junction comparisons were completed for survey H13082. Two of these surveys (H13083 and H13084) were acquired concurrently with this survey and one survey (W00320) was completed in 2016 by NOAA Ship BELL M. SHIMADA.</ns2:discussion><ns2:images><ns2:caption>H13082 junctions with surveys H13083, H13084, and W00320.</ns2:caption><ns2:link>SupportFiles\B.2.3 Junctions.png</ns2:link></ns2:images><ns2:junction><ns2:survey><ns2:registryNumber>H13083</ns2:registryNumber><ns2:scale>20000</ns2:scale><ns2:year>2017</ns2:year><ns2:fieldUnit>NOAA Ship RAINIER</ns2:fieldUnit><ns2:relativeLocation>NE</ns2:relativeLocation></ns2:survey><ns2:discussion>The junction with survey H13083 encompasses 0.40 square nautical miles along the northeastern boundary of survey H13082. The Compare Grids function of Pydro explorer derived a difference surface from the 2-meter CUBE surfaces of each survey for comparison. Analysis of the difference surface indicated that survey H13083 is an average of 0.03 meters deeper than survey H13082 with a standard deviation of 0.18 meters.</ns2:discussion><ns2:images><ns2:caption>H13082 and H13083 junction difference surface.</ns2:caption><ns2:link>SupportFiles\B.2.3 Junction_H13083.png</ns2:link></ns2:images><ns2:images><ns2:caption>Pydro derived plot showing percentage-pass value of the junction between surveys H13082 and H13083.</ns2:caption><ns2:link>SupportFiles\H13082_MB_2m_MLLW_Final-H13083_MB_2m_MLLW_Final_fracAllowErr_Freq.png</ns2:link></ns2:images><ns2:images><ns2:caption>Pydro derived plot showing absolute difference statistics of the junction between surveys H13082 and H13083.</ns2:caption><ns2:link>SupportFiles\H13082_MB_2m_MLLW_Final-H13083_MB_2m_MLLW_Final_depth_delta.png</ns2:link></ns2:images><ns2:images><ns2:caption>Pydro derived plot showing node depth vs. allowable error fraction of the junction between surveys H13082 and H13083.</ns2:caption><ns2:link>SupportFiles\H13082_MB_2m_MLLW_Final-H13083_MB_2m_MLLW_Final_fracAllowErr_vsDepth.png</ns2:link></ns2:images><ns2:comments/></ns2:junction><ns2:junction><ns2:survey><ns2:registryNumber>H13084</ns2:registryNumber><ns2:scale>20000</ns2:scale><ns2:year>2017</ns2:year><ns2:fieldUnit>NOAA Ship RAINIER</ns2:fieldUnit><ns2:relativeLocation>SE</ns2:relativeLocation></ns2:survey><ns2:discussion>The junction with survey H13084 encompasses 0.27 square nautical miles along the southeastern boundary of survey H13082. The Compare Grids function of Pydro explorer derived a difference surface from the 2-meter CUBE surfaces of each survey for comparison. Analysis of the difference surface indicated that survey H13084 is an average of 0.01 meters deeper than survey H13082 with a standard deviation of 0.23 meters.</ns2:discussion><ns2:images><ns2:caption>H13082 and H13084 junction difference surface.</ns2:caption><ns2:link>SupportFiles\B.2.3 Junction_H13084.png</ns2:link></ns2:images><ns2:images><ns2:caption>Pydro derived plot showing percentage-pass value of the junction between surveys H13082 and H13084.</ns2:caption><ns2:link>SupportFiles\H13082_MB_2m_MLLW_Final-H13084_MB_2m_MLLW_Final_fracAllowErr_Freq.png</ns2:link></ns2:images><ns2:images><ns2:caption>Pydro derived plot showing absolute difference statistics of the junction between surveys H13082 and H13084.</ns2:caption><ns2:link>SupportFiles\H13082_MB_2m_MLLW_Final-H13084_MB_2m_MLLW_Final_depth_delta.png</ns2:link></ns2:images><ns2:images><ns2:caption>Pydro derived plot showing node depth vs. allowable error fraction of the junction between surveys H13082 and H13084.</ns2:caption><ns2:link>SupportFiles\H13082_MB_2m_MLLW_Final-H13084_MB_2m_MLLW_Final_fracAllowErr_vsDepth.png</ns2:link></ns2:images><ns2:comments/></ns2:junction><ns2:junction><ns2:survey><ns2:registryNumber>W00320</ns2:registryNumber><ns2:scale>40000</ns2:scale><ns2:year>2016</ns2:year><ns2:fieldUnit>NOAA Ship BELL M. SHIMADA</ns2:fieldUnit><ns2:relativeLocation>NW</ns2:relativeLocation></ns2:survey><ns2:discussion>The junction with survey W00320 encompassed 4.57 square nautical miles along the entire northwestern and southwestern portions of the H13082 survey area. A comparison was made with the Compare Grids function of Pydro Explorer using a difference surface derived from 2-meter Caris .csar surfaces of each survey. Analysis of the difference surface indicated that W00320 is an average of 4.6 meters deeper than H13082 with a standard deviation of 0.96 meters. According to its Survey Acceptance Review (SAR), W00320 was a habitat mapping survey acquired with a Simrad ME70, a sonar normally used to collect water column data for fisheries applications. Data from the ME70 are not suitable for object detection, feature disapproval, or for areas of critical under-keel clearance. This information helps to explain the poor comparison between H13082 and W00320 data. The sign, large magnitude, and relatively low standard deviation of this offset suggest a systematic, rather than random error in the SHIMADA dataset. The hydrographer suspects that there may have been an error in static offset application during W00320 acquisition and/or processing. The hydrographer recommends that H13082 fully supersede W00320 in the common area.
</ns2:discussion><ns2:images><ns2:caption>H13082 and W00320 junction difference surface.</ns2:caption><ns2:link>SupportFiles\B.2.3 Junction_W00320.png</ns2:link></ns2:images><ns2:images><ns2:caption>Pydro derived plot showing percentage-pass value of the junction between surveys H13082 and W00320.</ns2:caption><ns2:link>SupportFiles\H13082_MB_2m_MLLW_Final-W00320_MB_2m_MLLW_Office_fracAllowErr_Freq.png</ns2:link></ns2:images><ns2:images><ns2:caption>Pydro derived plot showing absolute difference statistics of the junction between surveys H13082 and W00320.</ns2:caption><ns2:link>SupportFiles\H13082_MB_2m_MLLW_Final-W00320_MB_2m_MLLW_Office_depth_delta.png</ns2:link></ns2:images><ns2:images><ns2:caption>Pydro derived plot showing node depth vs. allowable error fraction of the junction between surveys H13082 and W00320.          </ns2:caption><ns2:link>SupportFiles\H13082_MB_2m_MLLW_Final-W00320_MB_2m_MLLW_Office_fracAllowErr_vsDepth.png</ns2:link></ns2:images><ns2:comments/></ns2:junction><ns2:comments/></ns1:junctions><ns1:sonarQCChecks><ns2:results deviation="false"><ns2:discussion>Sonar system quality control checks were conducted as detailed in the quality control section of the DAPR.</ns2:discussion></ns2:results><ns2:comments/></ns1:sonarQCChecks><ns1:equipmentEffectiveness><ns2:results deviation="true"><ns2:issue><ns2:title>Sonar Pulse Length</ns2:title><ns2:discussion>Survey H13082 was acquired to produce bathymetric data and high quality backscatter data. In order to acquire the high quality backscatter, minimal changes to the sonar’s operating mode were required. Instead of operating sonar pulse length automatically, it was manually switched between long pulse in depths greater than 20 meters and short pulse in depths less than 20 meters. The hydrographer monitored the effects of these manual changes out in the field and found no issues in the resulting data.</ns2:discussion><ns2:comments/></ns2:issue></ns2:results><ns2:comments/></ns1:equipmentEffectiveness><ns1:factorsAffectingSoundings><ns2:results deviation="false"><ns2:issue><ns2:title>None Exist</ns2:title><ns2:discussion>There were no other factors that affected corrections to soundings.</ns2:discussion><ns2:comments/></ns2:issue></ns2:results><ns2:comments/></ns1:factorsAffectingSoundings><ns1:soundSpeedMethods><ns1:castFrequency>Launches took casts at least once every four hours (before MBES acquisition, middle of the day, and near the end of the day).</ns1:castFrequency><ns1:discussion>Additional casts were taken when significant changes to surface sound speed were observed or when operating in a new area. Sound speed profiles were acquired using Sea-Bird 19plus SEACAT Profilers. All casts were concatenated into a master file and applied to MBES data in Caris HIPS using the &quot;Nearest in distance within time&quot; (4 hours) profile selection method.</ns1:discussion><ns1:images><ns2:caption>H13082 sound speed cast locations.</ns2:caption><ns2:link>SupportFiles\B.2.7 Sound Speed Locations.png</ns2:link></ns1:images><ns1:comments/></ns1:soundSpeedMethods><ns1:coverageEquipmentAndMethods><ns2:results deviation="false"><ns2:discussion>All equipment and survey methods were used as detailed in the DAPR.</ns2:discussion></ns2:results><ns2:comments/></ns1:coverageEquipmentAndMethods><ns1:additionalQualityControl><ns2:issue><ns2:title>Detect Fliers</ns2:title><ns2:discussion>Pydro QC Tools 2 Detect Fliers was used to find fliers in a finalized VR surface. Obvious noise was rejected by the hydrographer in Caris subset editor. After data cleaning, Detect Fliers was run again and found 20 certain fliers; these were investigated and found to be false positives. The results of the Detect Fliers tool are included as a .000 files in the Separates section of this report.</ns2:discussion><ns2:comments/></ns2:issue><ns2:comments/></ns1:additionalQualityControl></ns1:qualityControl><ns1:echoSoundingCorrections><ns1:corrections><ns2:results deviation="false"><ns2:discussion>All data reduction procedures conform to those detailed in the DAPR.</ns2:discussion></ns2:results><ns2:comments/></ns1:corrections><ns1:calibrations><ns2:results deviation="false"><ns2:discussion>All sounding systems were calibrated as detailed in the DAPR.</ns2:discussion><ns2:calibration xsi:nil="true"/></ns2:results><ns2:comments/></ns1:calibrations><ns1:additionalIssues><ns2:comments/></ns1:additionalIssues></ns1:echoSoundingCorrections><ns1:backscatter><ns2:results acquired="true"><ns2:discussion>Raw Backscatter data were logged as .all files for delivery to NOAA's Pacific Hydrographic Branch. The field unit processed the backscatter data and generated backscatter mosaics. One 2 meter mosaic per vessel per frequency was generated for H13082. To create the mosaic, processed HDCS lines were paired with the raw .all files in Fledermaus Geocoder Toolbox version 7.7.7.  Errors occurred while processing backscatter, including an “Auto Time-Sync Algorithm failure” message due to a discrepancy between GPS time and UTC time. Entering a -2.0 second merge offset option in the processing window cleared the error and made converting lines and producing backscatter mosaics possible.</ns2:discussion></ns2:results><ns2:comments/></ns1:backscatter><ns1:dataProcessing><ns1:drSoftware><ns1:bathySoftware deviation="false"><ns1:manufacturer xsi:nil="true"></ns1:manufacturer><ns1:name xsi:nil="true"></ns1:name><ns1:version xsi:nil="true"></ns1:version></ns1:bathySoftware><ns1:imagerySoftware deviation="false"><ns1:manufacturer xsi:nil="true"></ns1:manufacturer><ns1:name xsi:nil="true"></ns1:name><ns1:version xsi:nil="true"></ns1:version></ns1:imagerySoftware><ns1:featureObjectCatalog>NOAA Extended Attribute File V_5_5</ns1:featureObjectCatalog><ns1:discussion xsi:nil="true"></ns1:discussion><ns1:comments/></ns1:drSoftware><ns1:surfaces><ns1:surface><ns2:surfaceName>H13082_MB_VR_MLLW</ns2:surfaceName><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:resolution units="meters">999</ns2:resolution><ns2:depthRange><ns2:min units="meters">-0.4</ns2:min><ns2:max units="meters">102.3</ns2:max></ns2:depthRange><ns2:surfaceParameter>VR</ns2:surfaceParameter><ns2:purpose>Complete MBES</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceName>H13082_MB_VR_MLLW_Final</ns2:surfaceName><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:resolution units="meters">999</ns2:resolution><ns2:depthRange><ns2:min units="meters">-0.4</ns2:min><ns2:max units="meters">102.3</ns2:max></ns2:depthRange><ns2:surfaceParameter>VR</ns2:surfaceParameter><ns2:purpose>Complete MBES</ns2:purpose></ns1:surface><ns1:discussion>Submitted surfaces were generated using the recommended parameters for depth-based (Ranges) Caris variable-resolution bathymetric grids as specified in HTD 2017-2. The resolution values indicated in the above table are not accurate: the XML-DR schema used to generate this report did not accommodate variable-resolution grids; the &quot;999&quot; values were entered as a placeholder.</ns1:discussion><ns1:comments/></ns1:surfaces><ns1:additionalDataProcessing><ns2:comments/></ns1:additionalDataProcessing></ns1:dataProcessing></ns1:dataAcquisitionAndProcessing><ns1:verticalAndHorizontalControl><ns1:discussion>Shoreline features were reduced to Mean Lower Low Water using traditional tide methods via TCARI. All MBES bathymetry were acquired relative to the ellipsoid and reduced to MLLW via VDatum.</ns1:discussion><ns1:verticalControl><ns2:verticalDatum>Mean Lower Low Water</ns2:verticalDatum><ns2:tideStations><ns2:NWLONGauges><ns2:stationName>Los Angeles, CA</ns2:stationName><ns2:stationID>9410660</ns2:stationID></ns2:NWLONGauges><ns2:NWLONGauges><ns2:stationName>Santa Monica, CA</ns2:stationName><ns2:stationID>9410840</ns2:stationID></ns2:NWLONGauges><ns2:NWLONGauges><ns2:stationName>Santa Barbara, CA</ns2:stationName><ns2:stationID>9411340</ns2:stationID></ns2:NWLONGauges><ns2:NWLONGauges><ns2:stationName>Oil Platform Harvest, CA</ns2:stationName><ns2:stationID>9411406</ns2:stationID></ns2:NWLONGauges><ns2:NWLONGauges><ns2:stationName>Port San Luis, CA</ns2:stationName><ns2:stationID>9412110</ns2:stationID></ns2:NWLONGauges><ns2:NWLONGauges><ns2:stationName>Monterey, CA</ns2:stationName><ns2:stationID>9413450</ns2:stationID></ns2:NWLONGauges></ns2:tideStations><ns2:standard_or_ERZT used="true"><ns2:methodsUsed>TCARI</ns2:methodsUsed><ns2:correctorFiles><ns2:tideCorrectors><ns2:fileName>L397RA2017Rev.tc</ns2:fileName><ns2:status>Final</ns2:status></ns2:tideCorrectors></ns2:correctorFiles><ns2:finalTides><ns2:dateSubmitted>2018-11-08</ns2:dateSubmitted><ns2:dateReceived>2017-11-17</ns2:dateReceived></ns2:finalTides><ns2:discussion xsi:nil="true"></ns2:discussion><ns2:comments/></ns2:standard_or_ERZT><ns2:VDATUM_or_constantSep used="true"><ns2:methodsUsed>ERS via VDATUM</ns2:methodsUsed><ns2:ellipsoidToChartDatumSepFile><ns2:fileName>OPR-L397-RA-17_VDatumArea_xyNAD83-MLLW_geoid12b.csar</ns2:fileName></ns2:ellipsoidToChartDatumSepFile><ns2:discussion xsi:nil="true"></ns2:discussion><ns2:comments/></ns2:VDATUM_or_constantSep><ns2:comments/></ns1:verticalControl><ns1:horizontalControl><ns2:horizontalDatum>North American Datum of 1983 (NAD83)</ns2:horizontalDatum><ns2:projection>Universal Transverse Mercator (UTM) Zone 10 North</ns2:projection><ns2:PPK used="false" xsi:nil="true"/><ns2:PPP used="false" xsi:nil="true"/><ns2:RTK used="true"><ns2:discussion>The Wide Area Augmentation System (WAAS) was used for real-time horizontal control for this survey.

Precise Positioning-Real Time Extended (PP-RTX) processing methods were used in Applanix POSPac MMS 8.1 software to produce SBETs for post-processing horizontal correction.</ns2:discussion><ns2:comments/></ns2:RTK><ns2:DGPS used="false" xsi:nil="true"/><ns2:comments/></ns1:horizontalControl><ns1:additionalIssues><ns2:comments/></ns1:additionalIssues></ns1:verticalAndHorizontalControl><ns1:resultsAndRecommendations><ns1:chartComparison><ns1:methods><ns2:discussion>Electronic Navigation Chart (ENC) US5CA64M was compared to H13082 survey data using a variable resolution CUBE surface, selected soundings, and contours created in CARIS. </ns2:discussion><ns2:comments/></ns1:methods><ns1:charts><ns2:ENC><ns2:chart><ns2:name>US5CA64M</ns2:name><ns2:scale>40000</ns2:scale><ns2:edition>9</ns2:edition><ns2:updateApplicationDate>2017-08-24</ns2:updateApplicationDate><ns2:issueDate>2017-12-07</ns2:issueDate><ns2:preliminary>false</ns2:preliminary></ns2:chart><ns2:discussion>Most H13082 survey contours diverge less than 300 meters from the charted depth curve. Survey data detected several uncharted 10 fathom and 20 fathom shoals and established 3 fathom survey contours not previously charted. Unsafe conditions prevented complete data acquisition of the 3 fathom contour in the foul area surrounding Point Bennett.

ENC US5CA64M was compared to H13082 survey data and revealed the following:

- Area 1: Data located uncharted 3 fathom and 5 fathom survey contours in the charted foul area and surrounding Castle Rock; several 10 fathom shoals north of the foul area are not charted; the 10 fathom survey contour diverges from the charted 10 fathom depth curve south of the foul area (Fig. 30)

- Area 2: Data located uncharted 20 fathom shoals between the 20 fathom and 30 fathom depth curves; the 20 fathom survey contour diverges from the charted 20 fathom depth curve in two locations (Fig. 31)

- Area 3: Data located an uncharted 10 fathom shoal within the large charted 20 fathom shoal; the 30 fathom survey contour diverges from the charted 30 fathom depth curve in one location in the north (Fig. 32)

- Area 4: Several 40 and 50 fathom survey contours diverge from their respective charted depth curves (Fig. 33)

- Area 5: Data established uncharted 3 fathom and 5 fathom survey contours within the charted foul area (Fig. 34)</ns2:discussion><ns2:images><ns2:caption>Survey H13082 contours overlaid on ENC US5CA64M.</ns2:caption><ns2:link>SupportFiles\Full Sheet.png</ns2:link></ns2:images><ns2:images><ns2:caption>Area 1 contour offsets between H13082 and US5CA64M.</ns2:caption><ns2:link>SupportFiles\Area 1.png</ns2:link></ns2:images><ns2:images><ns2:caption>Area 2 contour offsets between H13082 and US5CA64M.</ns2:caption><ns2:link>SupportFiles\Area 2.png</ns2:link></ns2:images><ns2:images><ns2:caption>Area 3 contour offsets between H13082 and US5CA64M.</ns2:caption><ns2:link>SupportFiles\Area 3.png</ns2:link></ns2:images><ns2:images><ns2:caption>Area 4 contour offsets between H13082 and US5CA64M.</ns2:caption><ns2:link>SupportFiles\Area 4.png</ns2:link></ns2:images><ns2:images><ns2:caption>Area 5 contour offsets between H13082 and US5CA64M.</ns2:caption><ns2:link>SupportFiles\Area 5.png</ns2:link></ns2:images><ns2:comments/></ns2:ENC><ns2:comments/></ns1:charts><ns1:maritimeBoundary><ns2:results investigated="None Exist"><ns2:discussion>No Maritime Boundary Points were assigned for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:maritimeBoundary><ns1:chartedFeatures><ns2:results investigated="Investigated"><ns2:discussion> A reported position approximate &quot;Rks&quot; is charted 100-200 meters southwest of Castle Rock. The hydrographer recommends removing this feature; please refer to the Final Feature File for more information.</ns2:discussion></ns2:results><ns2:comments/></ns1:chartedFeatures><ns1:unchartedFeatures><ns2:results investigated="None Exist"><ns2:discussion>No uncharted features exist for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:unchartedFeatures><ns1:DTONS><ns2:results reportSubmitted="true"><ns2:numberSubmitted>1</ns2:numberSubmitted><ns2:discussion>One Danger to Navigation Report containing two DTONs is included in Appendix II of this report.

As of 3/5/2018, both DTONs were compared to the latest version of the largest scale ENC in the area and were found to be properly applied to the chart.</ns2:discussion></ns2:results><ns2:comments/></ns1:DTONS><ns1:shoalAndHazardousFeatures><ns2:results investigated="Investigated"><ns2:discussion> Features of navigational significance are discussed in the chart comparison sections above or are included in the H13082 Final Feature File submitted with this report.</ns2:discussion></ns2:results><ns2:comments/></ns1:shoalAndHazardousFeatures><ns1:channels><ns2:results investigated="None Exist"><ns2:discussion>No channels exist for this survey.  There are no designated anchorages, precautionary areas, safety fairways, traffic separation schemes, pilot boarding areas, or channel and range lines within the survey limits.</ns2:discussion></ns2:results><ns2:comments/></ns1:channels><ns1:bottomSamples><ns2:results investigated="None Exist"><ns2:discussion>A bottom sample requirement was not specified in the project instructions, however photos at ten individual sites were obtained using a Go Pro camera attached to a CTD probe. Video footage was recorded during the CTD cast and still photos where derived from the footage to obtain a &quot;virtual bottom sample'. A copy of the pertinent acquisition log is also include with photos to link each bottom sample site with a lat/long. These images and acquisition logs are included with the Separates section of this report for archival purposes.</ns2:discussion></ns2:results><ns2:comments/></ns1:bottomSamples></ns1:chartComparison><ns1:additionalResults><ns1:shoreline><ns2:results investigated="Investigated"><ns2:discussion>Limited shoreline verification was conducted in accordance with applicable sections of NOAA HSSD and FPM using the Project Reference File (PRF) and Composite Source File (CSF) provided with the Project Instructions. In the field, all assigned features that were safe to approach, were addressed as required with S-57 attribution and recorded in the H13093_Final_Feature_File (FFF) to best represent the features at chart scale. This file also includes new features found in the field as well as recommendations to update, retain or delete assigned features.</ns2:discussion></ns2:results><ns2:comments/></ns1:shoreline><ns1:priorSurveys><ns2:results investigated="None Exist"><ns2:discussion>No prior survey comparisons exist for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:priorSurveys><ns1:ATONS><ns2:results investigated="None Exist"><ns2:discussion>No Aids to navigation (ATONs) exist for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:ATONS><ns1:overheadFeatures><ns2:results investigated="None Exist"><ns2:discussion>No overhead features exist for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:overheadFeatures><ns1:submarineFeatures><ns2:results investigated="None Exist"><ns2:discussion>No submarine features exist for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:submarineFeatures><ns1:ferryRoutesAndTerminals><ns2:results investigated="None Exist"><ns2:discussion>No ferry routes or terminals exist for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:ferryRoutesAndTerminals><ns1:platforms><ns2:results investigated="None Exist"><ns2:discussion>No platforms exist for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:platforms><ns1:significantFeatures><ns2:results investigated="None Exist"><ns2:discussion>No Significant Features exist for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:significantFeatures><ns1:constructionOrDredging><ns2:results investigated="None Exist"><ns2:discussion>No present or planned construction or dredging exist within the survey limits.</ns2:discussion></ns2:results><ns2:comments/></ns1:constructionOrDredging><ns1:otherResults><ns2:comments/></ns1:otherResults><ns1:newSurveyRecommendation><ns2:results recommended="false"><ns2:discussion>No new surveys or further investigations are recommended for this area.</ns2:discussion></ns2:results><ns2:comments/></ns1:newSurveyRecommendation><ns1:insetRecommendation><ns2:results recommended="false"><ns2:discussion>No new insets are recommended for this area.</ns2:discussion></ns2:results><ns2:comments/></ns1:insetRecommendation></ns1:additionalResults></ns1:resultsAndRecommendations><ns1:approvalSheet><ns1:statements><ns1:supervision>As Chief of Party, field operations for this hydrographic survey were conducted under my direct supervision, with frequent personal checks of progress and adequacy. I have reviewed the attached survey data and reports.</ns1:supervision><ns1:approval>All field sheets, this Descriptive Report, and all accompanying records and data are approved. All records are forwarded for final review and processing to the Processing Branch.</ns1:approval><ns1:adequacyOfSurvey>The survey data meets or exceeds requirements as set forth in the NOS Hydrographic Surveys and Specifications Deliverables Manual, Field Procedures Manual, Letter Instructions, and all HSD Technical Directives. These data are adequate to supersede charted data in their common areas. This survey is complete and no additional work is required with the exception of deficiencies noted in the Descriptive Report.</ns1:adequacyOfSurvey><ns1:additionalInfo xsi:nil="true"></ns1:additionalInfo></ns1:statements><ns1:signingPersonnel><ns2:approverName>Benjamin K. Evans, CDR/NOAA</ns2:approverName><ns2:approverTitle>Commanding Officer NOAA Ship Rainier</ns2:approverTitle><ns2:approvalDate>2018-05-29</ns2:approvalDate></ns1:signingPersonnel><ns1:signingPersonnel><ns2:approverName>Scott E. Broo, LT/NOAA</ns2:approverName><ns2:approverTitle>Field Operations Officer NOAA Ship Rainier</ns2:approverTitle><ns2:approvalDate>2018-05-29</ns2:approvalDate></ns1:signingPersonnel><ns1:signingPersonnel><ns2:approverName>James B. Jacobson</ns2:approverName><ns2:approverTitle>Chief Survey Technician NOAA Ship Rainier</ns2:approverTitle><ns2:approvalDate>2018-05-29</ns2:approvalDate></ns1:signingPersonnel><ns1:signingPersonnel><ns2:approverName>Amanda M. Finn</ns2:approverName><ns2:approverTitle>Assistant Survey Tech. NOAA Ship Rainier</ns2:approverTitle><ns2:approvalDate>2018-05-29</ns2:approvalDate></ns1:signingPersonnel></ns1:approvalSheet></ns1:descriptiveReport>