<?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-P136-RA-16</ns2:number><ns2:name>North Coast of Kodiak Island, AK</ns2:name><ns2:generalLocality>North Coast of Kodiak</ns2:generalLocality><ns2:fieldUnit>NOAA Ship RAINIER</ns2:fieldUnit></ns1:projectMetadata><ns1:registryMetadata><ns2:registryNumber>H12848</ns2:registryNumber><ns2:sheetID>6</ns2:sheetID><ns2:registryInstructions xsi:nil="true"></ns2:registryInstructions><ns2:sublocality>Uganik Passage</ns2:sublocality><ns2:stateOrTerritory>Alaska</ns2:stateOrTerritory><ns2:country>United States</ns2:country><ns2:scale>40000</ns2:scale></ns1:registryMetadata><ns1:surveyMetadata><ns2:year>2016</ns2:year><ns2:chiefOfParty>Edward J. Van Den Ameele, CAPT/NOAA</ns2:chiefOfParty><ns2:projectType>Navigable Area</ns2:projectType><ns2:PIDate>2016-05-16</ns2:PIDate><ns2:datesOfSurvey><ns2:start>2016-06-13</ns2:start><ns2:end>2016-06-29</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="5N">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 project area is referred to as Sheet 6: &quot;Uganik Passage&quot; within the Project Instructions.  The area is south of Uganik Island, AK.</ns2:discussion><ns2:limits><ns2:northWest><ns2:latitude hemisphere="N">57.8553556389</ns2:latitude><ns2:longitude hemisphere="W">153.389015972</ns2:longitude></ns2:northWest><ns2:southEast><ns2:latitude hemisphere="N">57.7918243889</ns2:latitude><ns2:longitude hemisphere="W">153.204131722</ns2:longitude></ns2:southEast></ns2:limits><ns2:images><ns2:caption>H12848 survey area as assigned in Project Instructions (Chart 16597_1).</ns2:caption><ns2:link>SupportFiles\A1 Survey Limits.png</ns2:link></ns2:images><ns2:comments/></ns1:areaDescription><ns1:surveyLimits><ns2:results deviation="true"><ns2:discussion>Data were acquired within survey limits in accordance with the requirements in the Project Instructions and the HSSD.</ns2:discussion></ns2:results><ns2:comments/></ns1:surveyLimits><ns1:surveyPurpose><ns2:discussion>The purpose of this project is to provide contemporary surveys to update National Ocean Service (NOS) nautical charting products, which will support Kodiak's large fishing fleet and increasing levels of passenger vessel traffic.</ns2:discussion><ns2:comments/></ns1:surveyPurpose><ns1:surveyQuality><ns2:adequacy>The entire survey is adequate to supersede previous data.</ns2:adequacy><ns2:discussion>The Finalized CSAR QA tool within Pydro Explorer was used to analyze multibeam echosounder (MBES) data density.  All finalized surfaces meet the HSSD data density requirement (Figures 2-5).</ns2:discussion><ns2:images><ns2:caption>Pydro derived histogram plot showing HSSD object detection compliance of H12848 MBES data within the 1-meter finalized CUBE surface.</ns2:caption><ns2:link>SupportFiles\H12848_MB_1m_MLLW_Final.density.png</ns2:link></ns2:images><ns2:images><ns2:caption>Pydro derived histogram plot showing HSSD object detection compliance of H12848 MBES data within the 2-meter finalized CUBE surface.</ns2:caption><ns2:link>SupportFiles\H12848_MB_2m_MLLW_Final.density.png</ns2:link></ns2:images><ns2:images><ns2:caption>Pydro derived histogram plot showing HSSD object detection compliance of H12848 MBES data within the 4-meter finalized CUBE surface.</ns2:caption><ns2:link>SupportFiles\H12848_MB_4m_MLLW_Final.density.png</ns2:link></ns2:images><ns2:images><ns2:caption>Pydro derived histogram plot showing HSSD object detection compliance of H12848 MBES data within the 8-meter finalized CUBE surface.</ns2:caption><ns2:link>SupportFiles\H12848_MB_8m_MLLW_Final.density.png</ns2:link></ns2:images><ns2:comments/></ns1:surveyQuality><ns1:surveyCoverage><ns2:coverageRequirement><ns2:waterDepth>Inshore limit to 8 meters water depth</ns2:waterDepth><ns2:requiredCoverage>Complete coverage MB with backscatter (Section 5.2.2.3) or Set Line Spacing MBES or SBES at 100m (HSSD Section 5.2.2.4).</ns2:requiredCoverage></ns2:coverageRequirement><ns2:coverageRequirement><ns2:waterDepth>Greater than 8 meters water depth</ns2:waterDepth><ns2:requiredCoverage>Complete Coverage MBES
(HSSD Section 5.2.2.3 Option A).</ns2:requiredCoverage></ns2:coverageRequirement><ns2:results deviation="true"><ns2:discussion>Complete multibeam coverage was achieved within the limits of hydrography as defined in the Project Instructions with some exceptions.  The following are examples of areas that do not meet the coverage requirement.

Coverage did not extend to the 4 meter contour on the northwestern side of the large peninsula in the passage.  Due to time constraints and the area being deemed not significant to navigation, survey coverage did not extend to the sheet limits in this area (Figure 6).

Coverage did not extend to the 4 meter contour in areas that were deemed unsafe by launch personnel, which includes some shoreline and some rocky features (Figure 7 and 8).  </ns2:discussion><ns2:images><ns2:caption>Northwestern shore of the peninsula was not completely covered due to time constraints.</ns2:caption><ns2:link>SupportFiles\Survey_Coverage_Gap.png</ns2:link></ns2:images><ns2:images><ns2:caption>Complete coverage was not achieved due to safety concerns.</ns2:caption><ns2:link>SupportFiles\Survey_Coverage_Gap_2.png</ns2:link></ns2:images><ns2:images><ns2:caption>Complete coverage was not achieved over rocky features due to safety concerns.</ns2:caption><ns2:link>SupportFiles\Survey_Coverage_Gap_3.png</ns2:link></ns2:images></ns2:results><ns2:comments/></ns1:surveyCoverage><ns1:coverageGraphic><ns2:caption>H12848 Survey Coverage (Chart 16597).</ns2:caption><ns2:link>SupportFiles\A4 Survey Coverage.png</ns2:link></ns1:coverageGraphic><ns1:coverageGraphic><ns2:caption>H12848 Geographic Context (Charts 16597 and 16594).</ns2:caption><ns2:link>SupportFiles\A4 Survey Coverage Small 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>26.71</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>110.64</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>2803</ns2:hullID><ns2:statistics><ns2:MS_SBES>0</ns2:MS_SBES><ns2:MS_MBES>40.28</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>58.04</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>17.47</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>235.67</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>17.47</ns2:XL_MBES_SBES><ns2:XL_lidar>0</ns2:XL_lidar><ns2:percentXLLNM>7.41</ns2:percentXLLNM></ns2:totalLNM></ns2:LNM><ns2:totalSurveyStats><ns2:bottomSamples>6</ns2:bottomSamples><ns2:maritimeBoundaryPoints>0</ns2:maritimeBoundaryPoints><ns2:DP>65</ns2:DP><ns2:diveOps>0</ns2:diveOps><ns2:SNM>8.53</ns2:SNM></ns2:totalSurveyStats><ns2:surveyDates>2016-06-13</ns2:surveyDates><ns2:surveyDates>2016-06-14</ns2:surveyDates><ns2:surveyDates>2016-06-15</ns2:surveyDates><ns2:surveyDates>2016-06-16</ns2:surveyDates><ns2:surveyDates>2016-06-22</ns2:surveyDates><ns2:surveyDates>2016-06-24</ns2:surveyDates><ns2:surveyDates>2016-06-25</ns2:surveyDates><ns2:surveyDates>2016-06-26</ns2:surveyDates><ns2:surveyDates>2016-06-27</ns2:surveyDates><ns2:surveyDates>2016-06-29</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.3</ns2:draft></ns1:vessel><ns1:vessel><ns2:hullID>1906</ns2:hullID><ns2:LOA units="meters">5.8</ns2:LOA><ns2:draft units="meters">0.3</ns2:draft></ns1:vessel><ns1:discussion>All data for H12848 were acquired by survey launches 2801, 2802, 2803, and 2804 and skiffs 1905 and 1906.  The survey launches acquired MBES depth soundings, backscatter data, and sound speed profiles.  The skiffs conducted shoreline verification.</ns1:discussion><ns1:comments/></ns1:vessels><ns1:equipment><ns1:majorSystem><ns2:manufacturer>Reson</ns2:manufacturer><ns2:model>SeaBat 7125 SV2</ns2:model><ns2:type>MBES</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>Reson</ns2:manufacturer><ns2:model>SeaBat 7125-B</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:majorSystem><ns2:manufacturer>Applanix</ns2:manufacturer><ns2:model>POS-MV V5</ns2:model><ns2:type>Positioning and Attitude System</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>Multibeam crosslines were acquired using Rainier launch 2804.  A 4-meter CUBE surface was created using only mainscheme lines, and a second 4-meter CUBE surface was created using only crosslines.  A difference surface was generated from these two surfaces in CARIS HIPS and SIPS at a 4-meter resolution.  This difference surface was compared to the IHO allowable total vertical uncertainty (TVU) standards.  In total, 98.7% of the depth differences between H12848 mainscheme and crossline data met HSSD TVU standards.  This analysis was performed on H12848 data reduced to Mean Lower-Low Water (MLLW) using Ellipsoidally Referenced Zoned Tides (ERZT) methods.</ns2:discussion><ns2:images><ns2:caption>Summary table indicating percentage of difference surface nodes between H12848 mainscheme and crossline data that met HSSD allowable TVU standards.</ns2:caption><ns2:link>SupportFiles\Crossline_Analysis_IHO_Satisfaction.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.014087</ns2:zoning><ns2:tideMethod>ERS via ERZT</ns2:tideMethod></ns2:tideUncertainty><ns2:soundSpeedUncertainty><ns2:hullID>2801, 2802, 2803, 2804</ns2:hullID><ns2:measuredCTD units="meters/second">3</ns2:measuredCTD><ns2:measuredMVP xsi:nil="true"/><ns2:surface units="meters/second">0.15</ns2:surface></ns2:soundSpeedUncertainty></ns2:values><ns2:discussion>Total Propagated Uncertainty (TPU) values for H12848 were derived from a combination of fixed values for equipment and vessel characteristics, as well as field assigned values for sound speed uncertainties.  Tidal uncertainties were accounted for by examining the field generated 1000-m separation model and statistically determining a measured uncertainty. The measured tide uncertainty value of 0.014087 meters was entered to account for ERZT processing methods.  See the OPR-P136-RA-16 ERS Capability memo included in Supplemental Correspondence for further information.

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

Uncertainty values of submitted finalized grids were calculated in CARIS HIPS and SIPS using the &quot;Greater of the Two&quot; of uncertainty and standard deviation (scaled to 95%). The Finalized CSAR Surface QA tool within Pydro Explorer was used to analyze H12848 MBES data (Figures 12-15). 

To visualize where uncertainty requirements were met, for each surface a custom &quot;HSSD Compliance&quot; layer was created, based on the difference between the calculated uncertainty of the nodes and the allowable uncertainty defined in the HSSD. Using this method, areas of concentrated IHO non-compliance were found in the final 2-meter and 4-meter CUBE surface.  Nodes that failed TVU compliance were generally in areas of high relief such as steep slopes and over rocky outcroppings.</ns2:discussion><ns2:images><ns2:caption>Pydro derived histogram plot showing HSSD uncertainty standards compliance of H12848 1-m finalized surface.</ns2:caption><ns2:link>SupportFiles\H12848_MB_1m_MLLW_Final.tvu_qc.png</ns2:link></ns2:images><ns2:images><ns2:caption>Pydro derived histogram plot showing HSSD uncertainty standards compliance of H12848 2-m finalized surface.</ns2:caption><ns2:link>SupportFiles\H12848_MB_2m_MLLW_Final.tvu_qc.png</ns2:link></ns2:images><ns2:images><ns2:caption>Pydro derived histogram plot showing HSSD uncertainty standards compliance of H12848 4-m finalized surface.</ns2:caption><ns2:link>SupportFiles\H12848_MB_4m_MLLW_Final.tvu_qc.png</ns2:link></ns2:images><ns2:images><ns2:caption>Pydro derived histogram plot showing HSSD uncertainty standards compliance of H12848 8-m finalized surface.</ns2:caption><ns2:link>SupportFiles\H12848_MB_8m_MLLW_Final.tvu_qc.png</ns2:link></ns2:images><ns2:images><ns2:caption>Area of HSSD non-compliance in 2m Final surface.</ns2:caption><ns2:link>SupportFiles\IHO_Compliance_2m_Final_West.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>Area of HSSD non-compliance in 2m Final surface.</ns2:caption><ns2:link>SupportFiles\IHO_Compliance_2m_Final_East.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>Area of HSSD non-compliance in 4m Final surface.</ns2:caption><ns2:link>SupportFiles\IHO_Compliance_4m_Final.jpg</ns2:link></ns2:images><ns2:comments/></ns1:uncertainty><ns1:junctions><ns2:discussion>H12848 junctions with two other surveys, H12919 and H12691, both Rainier surveys.  H12919 was acquired concurrently with H12848, while H12691 was acquired in 2015.</ns2:discussion><ns2:images><ns2:caption>H12848 Junction Surveys.</ns2:caption><ns2:link>SupportFiles\H12848_Junctions_2.png</ns2:link></ns2:images><ns2:junction><ns2:survey><ns2:registryNumber>H12691</ns2:registryNumber><ns2:scale>40000</ns2:scale><ns2:year>2015</ns2:year><ns2:fieldUnit>NOAA Ship RAINIER</ns2:fieldUnit><ns2:relativeLocation>SE</ns2:relativeLocation></ns2:survey><ns2:discussion>Overlap with survey H12691 was approximately 500 meters wide and 350 meters long (Figure 20).  Depths in the junction area range from 10 to 75 meters.  For the respective depths, the difference surface was compared to the allowable TVU standards specified in the HSSD.  Analysis of the absolute difference surface indicated a mean difference of 0.7 meters with a standard deviation of 0.36 meters.  In total, 70.2% (Figure 21) of the depth differences between H12848 and junction survey H12691 are within allowable uncertainties.  The biggest differences (greater than 1 meter) occurred over slopes.</ns2:discussion><ns2:images><ns2:caption>H12848 junction with H12691.</ns2:caption><ns2:link>SupportFiles\H12848_H12691_Overlap.png</ns2:link></ns2:images><ns2:images><ns2:caption>Summary table indicating the percentage of nodes from the junction overlap that met HSSD allowable TVU standards.</ns2:caption><ns2:link>SupportFiles\H12848_H12691_HSSD_Accuracy.png</ns2:link></ns2:images><ns2:comments/></ns2:junction><ns2:junction><ns2:survey><ns2:registryNumber>H12919</ns2:registryNumber><ns2:scale>40000</ns2:scale><ns2:year>2016</ns2:year><ns2:fieldUnit>NOAA Ship RAINIER</ns2:fieldUnit><ns2:relativeLocation>NW</ns2:relativeLocation></ns2:survey><ns2:discussion>Junction analysis specifics between H12848 and H12919 are located in the H12919 DR.</ns2:discussion><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>Inverter shutdown</ns2:title><ns2:discussion>On June 26th (Day Number 178) at roughly 2130 UTC, launch 2803 experienced an inverter shutdown, which resulted in the loss of power to the acquisition computer, sonar (Reson SeaBat 7125-B), and positioning and attitude sensor (POS MV V5).  While the launch was not logging MBES data at the time, processing the data revealed that due to the shutdown the time extents (including the 5 minutes beyond the last logged line) of the POS file did not fully cover the line logged prior to the shutdown, 2803_2016__1782124.  No delayed heave file could be applied to that line, however, a SBET could be applied.</ns2:discussion><ns2:comments/></ns2:issue></ns2:results><ns2:comments/></ns1:equipmentEffectiveness><ns1:factorsAffectingSoundings><ns2:results deviation="true"><ns2:issue><ns2:title>No Delayed Heave</ns2:title><ns2:discussion>No delayed heave was applied to line 2803_2016__1782124 (see section B.2.5 Equipment Effectiveness), but a SBET has been applied.  Reviewing the soundings in subset editor revealed consistency with other lines, and so it is included with the final submission surfaces.</ns2:discussion><ns2:comments/></ns2:issue></ns2:results><ns2:comments/></ns1:factorsAffectingSoundings><ns1:soundSpeedMethods><ns1:castFrequency>Sound speed profiles were acquired using the SBE 19plus CTD probes at discrete locations within the survey area at least once every four hours, when significant changes in surface speed were observed, or when surveying a new area.  Thirty-eight CTD casts were acquired and applied to H12848 MBES data using the nearest in distance within time (4 hours) method.</ns1:castFrequency><ns1:discussion xsi:nil="true"></ns1:discussion><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: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 was logged as a 7k file and will be sent to the Processing Branch. Backscatter was not formally processed by the field unit.</ns2:discussion></ns2:results><ns2:comments/></ns1:backscatter><ns1:dataProcessing><ns1:drSoftware><ns1:bathySoftware deviation="true"><ns1:manufacturer>Caris</ns1:manufacturer><ns1:name>HIPS/SIPS</ns1:name><ns1:version>9.1.5</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 Files V_5_4.</ns1:featureObjectCatalog><ns1:discussion>  All features were processed using CARIS HIPS and SIPS 9.1 and CARIS Notebook 3.1.</ns1:discussion><ns1:comments/></ns1:drSoftware><ns1:surfaces><ns1:surface><ns2:surfaceName>H12848_MB_1m_MLLW</ns2:surfaceName><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:resolution units="meters">1</ns2:resolution><ns2:depthRange><ns2:min units="meters">-1.36</ns2:min><ns2:max units="meters">144.96</ns2:max></ns2:depthRange><ns2:surfaceParameter>NOAA_1m</ns2:surfaceParameter><ns2:purpose>Complete MBES</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceName>H12848_MB_2m_MLLW</ns2:surfaceName><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:resolution units="meters">2</ns2:resolution><ns2:depthRange><ns2:min units="meters">-1.16</ns2:min><ns2:max units="meters">144.96</ns2:max></ns2:depthRange><ns2:surfaceParameter>NOAA_2m</ns2:surfaceParameter><ns2:purpose>Complete MBES</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceName>H12848_MB_4m_MLLW</ns2:surfaceName><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:resolution units="meters">4</ns2:resolution><ns2:depthRange><ns2:min units="meters">-0.76</ns2:min><ns2:max units="meters">144.85</ns2:max></ns2:depthRange><ns2:surfaceParameter>NOAA_4m</ns2:surfaceParameter><ns2:purpose>Complete MBES</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceName>H12848_MB_8m_MLLW</ns2:surfaceName><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:resolution units="meters">8</ns2:resolution><ns2:depthRange><ns2:min units="meters">-0.57</ns2:min><ns2:max units="meters">144.95</ns2:max></ns2:depthRange><ns2:surfaceParameter>NOAA_8m</ns2:surfaceParameter><ns2:purpose>Complete MBES</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceName>H12848_MB_1m_MLLW_Final</ns2:surfaceName><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:resolution units="meters">1</ns2:resolution><ns2:depthRange><ns2:min units="meters">-1.36</ns2:min><ns2:max units="meters">20</ns2:max></ns2:depthRange><ns2:surfaceParameter>NOAA_1m</ns2:surfaceParameter><ns2:purpose>Complete MBES</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceName>H12848_MB_2m_MLLW_Final</ns2:surfaceName><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:resolution units="meters">2</ns2:resolution><ns2:depthRange><ns2:min units="meters">18</ns2:min><ns2:max units="meters">40</ns2:max></ns2:depthRange><ns2:surfaceParameter>NOAA_2m</ns2:surfaceParameter><ns2:purpose>Complete MBES</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceName>H12848_MB_4m_MLLW_Final</ns2:surfaceName><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:resolution units="meters">4</ns2:resolution><ns2:depthRange><ns2:min units="meters">36</ns2:min><ns2:max units="meters">80</ns2:max></ns2:depthRange><ns2:surfaceParameter>NOAA_4m</ns2:surfaceParameter><ns2:purpose>Complete MBES</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceName>H12848_MB_8m_MLLW_Final</ns2:surfaceName><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:resolution units="meters">8</ns2:resolution><ns2:depthRange><ns2:min units="meters">72</ns2:min><ns2:max units="meters">144.95</ns2:max></ns2:depthRange><ns2:surfaceParameter>NOAA_8m</ns2:surfaceParameter><ns2:purpose>Complete MBES</ns2:purpose></ns1:surface><ns1:discussion>All CARIS CUBE surfaces were created with lines reduced to MLLW via ERZT methods.  Ten soundings were designated in accordance with HSSD requirements.

The 1-meter grid resolution range was expanded to include the full range of survey coverage.  See Supplemental Correspondence for Project Manager approval.</ns1:discussion><ns1:comments/></ns1:surfaces><ns1:additionalDataProcessing><ns2:comments/></ns1:additionalDataProcessing></ns1:dataProcessing></ns1:dataAcquisitionAndProcessing><ns1:verticalAndHorizontalControl><ns1:discussion>Additional information discussing the vertical or horizontal control for this survey can be found in the accompanying HVCR.</ns1:discussion><ns1:verticalControl><ns2:verticalDatum>Mean Lower Low Water</ns2:verticalDatum><ns2:tideStations><ns2:NWLONGauges><ns2:stationName>Seldovia</ns2:stationName><ns2:stationID>945-5500</ns2:stationID></ns2:NWLONGauges></ns2:tideStations><ns2:standard_or_ERZT used="false" xsi:nil="true"/><ns2:VDATUM_or_constantSep used="true"><ns2:methodsUsed>ERS via ERZT</ns2:methodsUsed><ns2:ellipsoidToChartDatumSepFile><ns2:fileName>H12848_WGS84_MLLW_SEP_1000m.csar</ns2:fileName></ns2:ellipsoidToChartDatumSepFile><ns2:discussion>Ellipsoidally Referenced Zoned Tides (ERZT) methods were used to transform between the ellipsoid and water level data. A 1000-meter resolution separation model between the ellipsoid and MLLW was computed using the real-time position measurements observed during the survey relative to the water line and the loaded TCARI tide file. &quot;GPS tides&quot; were then computed using the above separation model and the corrected GPS-height-to-water level data (SBET). The 1000-meter resolution separation model was generated in WGS84 due to the SBETs being exported in WGS84.  For additional information see the OPR-P136-RA-16 ERS Capability Memo included with the supplemental correspondence.</ns2:discussion><ns2:comments/></ns2:VDATUM_or_constantSep><ns2:comments/></ns1:verticalControl><ns1:horizontalControl><ns2:horizontalDatum>World Geodetic System of 1984 (WGS84(G1674))</ns2:horizontalDatum><ns2:projection>Universal Transverse Mercator (UTM) Zone 5 North</ns2:projection><ns2:PPK used="true"><ns2:methodsUsed>Smart Base</ns2:methodsUsed><ns2:methodsUsed>Single Base</ns2:methodsUsed><ns2:baseStations><ns2:CORSStations><ns2:HVCRSiteID>AC38</ns2:HVCRSiteID><ns2:stationID>QUARTZ_CRKAK2005</ns2:stationID></ns2:CORSStations><ns2:CORSStations><ns2:HVCRSiteID>AC67</ns2:HVCRSiteID><ns2:stationID>PILLARMTN_AK2006</ns2:stationID></ns2:CORSStations><ns2:CORSStations><ns2:HVCRSiteID>AC34</ns2:HVCRSiteID><ns2:stationID>OldHarbor_AK2006</ns2:stationID></ns2:CORSStations><ns2:CORSStations><ns2:HVCRSiteID>KOD6</ns2:HVCRSiteID><ns2:stationID>KODIAK 6</ns2:stationID></ns2:CORSStations><ns2:CORSStations><ns2:HVCRSiteID>AC39</ns2:HVCRSiteID><ns2:stationID>SHUYAKISSPAK2006</ns2:stationID></ns2:CORSStations><ns2:CORSStations><ns2:HVCRSiteID>AC24</ns2:HVCRSiteID><ns2:stationID>KINGSALMONAK2006</ns2:stationID></ns2:CORSStations><ns2:CORSStations><ns2:HVCRSiteID>KOD5</ns2:HVCRSiteID><ns2:stationID>KODIAK 5</ns2:stationID></ns2:CORSStations><ns2:CORSStations><ns2:HVCRSiteID>AC18</ns2:HVCRSiteID><ns2:stationID>Ushagat_IsAK2008</ns2:stationID></ns2:CORSStations><ns2:CORSStations><ns2:HVCRSiteID>AC02</ns2:HVCRSiteID><ns2:stationID>AkhiokCorpAK2005</ns2:stationID></ns2:CORSStations><ns2:userInstalledStations><ns2:HVCRSiteID>The Mids</ns2:HVCRSiteID><ns2:stationID>9715</ns2:stationID></ns2:userInstalledStations></ns2:baseStations><ns2:discussion xsi:nil="true"></ns2:discussion><ns2:comments/></ns2:PPK><ns2:PPP used="false" xsi:nil="true"/><ns2:RTK used="false" xsi:nil="true"/><ns2:DGPS used="true"><ns2:USCGStations><ns2:name>Kodiak 313kHz</ns2:name></ns2:USCGStations><ns2:discussion>For real time positioning during data acquisition either WAAS or DGPS was used.</ns2:discussion><ns2:comments/></ns2:DGPS><ns2:comments/></ns1:horizontalControl><ns1:additionalIssues><ns2:comments/></ns1:additionalIssues></ns1:verticalAndHorizontalControl><ns1:resultsAndRecommendations><ns1:chartComparison><ns1:methods><ns2:discussion>Chart comparisons were made using a CARIS sounding and contour layer derived from a 8-meter combined CUBE surface.  The contours and soundings were overlaid on the charts and compared for general agreement and to identify areas of significant change.</ns2:discussion><ns2:comments/></ns1:methods><ns1:charts><ns2:rasterChart><ns2:chart><ns2:number>16576</ns2:number><ns2:kapp>2871</ns2:kapp><ns2:scale>80000</ns2:scale><ns2:edition>5</ns2:edition><ns2:editionDate>2015-04</ns2:editionDate><ns2:LNMDate>2016-04-05</ns2:LNMDate><ns2:NMDate>2016-04-09</ns2:NMDate></ns2:chart><ns2:discussion>Chart 16597 covers a small area in the northwestern end of survey H12848.  Charted soundings were generally more shallow than H12848 data soundings, and charted contours had general agreement with H12848 contours with the greatest separation roughly 100 meters between the charted 10-fathom contour and H12848 10-fathom contour to the east.</ns2:discussion><ns2:images><ns2:caption>Variation between the H12848 and charted 10, 5, and 3-fathom contours.</ns2:caption><ns2:link>SupportFiles\Chart 16576_1.png</ns2:link></ns2:images><ns2:comments/></ns2:rasterChart><ns2:rasterChart><ns2:chart><ns2:number>16594</ns2:number><ns2:kapp>2553</ns2:kapp><ns2:scale>78900</ns2:scale><ns2:edition>14</ns2:edition><ns2:editionDate>2015-01</ns2:editionDate><ns2:LNMDate>2016-04-05</ns2:LNMDate><ns2:NMDate>2016-04-09</ns2:NMDate></ns2:chart><ns2:discussion>In the area of survey H12848, Chart 16594 has no data to compare to and refers the user to use Chart 16597.  Therefore no comparison was made with Chart 16594.</ns2:discussion><ns2:comments/></ns2:rasterChart><ns2:rasterChart><ns2:chart><ns2:number>16597</ns2:number><ns2:kapp>2559</ns2:kapp><ns2:scale>80000</ns2:scale><ns2:edition>10</ns2:edition><ns2:editionDate>2015-04</ns2:editionDate><ns2:LNMDate>2016-04-05</ns2:LNMDate><ns2:NMDate>2016-04-09</ns2:NMDate></ns2:chart><ns2:discussion>H12848 is dynamic with several large disagreements with Chart 16597.  As seen in Figures 23-28 contours and charted soundings can be off by hundreds of meters.  The large spacing in charted soundings hid many features, as seen highlighted in Figure 25.  The navigable passage between the Uganik Island peninsula and Kodiak Island is shoaler and thinner than charted (Figure 26).  In Figures 24, 25, and 28 large discrepancies between charted and H12848 soundings are highlighted in yellow circles.  Though these soundings were up to 30 fathoms different than what was charted, they were not chosen as DTONs because they do not pose a danger to surface navigation for the vessel traffic in the area.</ns2:discussion><ns2:images><ns2:caption>Charted contours and H12848 contours align poorly.</ns2:caption><ns2:link>SupportFiles\Chart 16597 Mid North Shallow.png</ns2:link></ns2:images><ns2:images><ns2:caption>Charted contours and H12848 contours align poorly.</ns2:caption><ns2:link>SupportFiles\Chart 16597 Mid North and 50 ftm.png</ns2:link></ns2:images><ns2:images><ns2:caption>H12848 10-fathom contour is different than charted, and highlighted area is 35 fathoms shoaler than nearby charted sounding.</ns2:caption><ns2:link>SupportFiles\Chart 16597 Middle North.png</ns2:link></ns2:images><ns2:images><ns2:caption>The passage by the peninsula is thinner than charted and with soundings shoaler than charted.</ns2:caption><ns2:link>SupportFiles\Chart 16597 Peninsula Channel.png</ns2:link></ns2:images><ns2:images><ns2:caption>Charted sounding is misplaced, and 10-fathom contour poorly aligns with chart along the southern coast.</ns2:caption><ns2:link>SupportFiles\Chart 16597 SE.png</ns2:link></ns2:images><ns2:images><ns2:caption>10-fathom contour aligns poorly with chart, and shoaler soundings exist than charted.</ns2:caption><ns2:link>SupportFiles\Chart 16597 SW.png</ns2:link></ns2:images><ns2:comments/></ns2:rasterChart><ns2:ENC><ns2:chart><ns2:name>US4AK5QM</ns2:name><ns2:scale>80000</ns2:scale><ns2:edition>6</ns2:edition><ns2:updateApplicationDate>2016-04-17</ns2:updateApplicationDate><ns2:issueDate>2016-04-17</ns2:issueDate><ns2:preliminary>false</ns2:preliminary></ns2:chart><ns2:discussion>In the area of survey H12848, Electronic Navigation Chart (ENC) US4AK5QM coincides with Chart 16597, therefore a comparison between H12848 and the ENC is equivalent to the preceding comparison with Chart 16597.</ns2:discussion><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>The Rep (1980) feature was found during shoreline operations and during MBES acquisition (Figure 29).  The shoalest acquired sounding is under 0.8 meters.</ns2:discussion><ns2:images><ns2:caption>Charted Feature with acquired multibeam coverage.</ns2:caption><ns2:link>SupportFiles\Charted_Feature.png</ns2:link></ns2:images></ns2:results><ns2:comments/></ns1:chartedFeatures><ns1:unchartedFeatures><ns2:results investigated="Investigated"><ns2:discussion> An uncharted wreck approximately 16 meters long, with a height of 3.7 meters above the sea floor was found in 9 to 10 meters of water.  This wreck was observed in the multibeam data and was assigned a critical sounding of 5.1 meters, or 2 fathoms 5 feet.  Next to the vessel is a feature that appears to be a fishing outrigger (Figures 30-32).</ns2:discussion><ns2:images><ns2:caption>An uncharted wreck located within the northwest corner of sheet H12848.</ns2:caption><ns2:link>SupportFiles\Overview_Shipwreck.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>A 2-dimensional subset view of an approximately 16 meter long wreck and a predicted fishing outrigger 12 meters away.</ns2:caption><ns2:link>SupportFiles\2D View Shipwreck.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>A backscatter image showing the wreck and predicted fishing outrigger.</ns2:caption><ns2:link>SupportFiles\Backscatter_Shipwreck.tiff</ns2:link></ns2:images></ns2:results><ns2:comments/></ns1:unchartedFeatures><ns1:DTONS><ns2:results reportSubmitted="true"><ns2:numberSubmitted>5</ns2:numberSubmitted><ns2:report><ns2:title>H12848_DTON</ns2:title><ns2:dateSubmitted>2016-08-19</ns2:dateSubmitted></ns2:report><ns2:report><ns2:title>H12848_DTONs_2</ns2:title><ns2:dateSubmitted>2016-08-25</ns2:dateSubmitted></ns2:report><ns2:discussion>Danger to Navigation Reports are included in Appendix II of this report.</ns2:discussion></ns2:results><ns2:comments/></ns1:DTONS><ns1:shoalAndHazardousFeatures><ns2:results investigated="Investigated"><ns2:discussion>All shoals and hazardous features were investigated in accordance with the Project Instructions and the HSSD, and are addressed in the 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="Investigated"><ns2:discussion>Two proposed bottom samples locations were identified in the Project Reference File and six were collected.  Samples were collected in the vicinity of the proposed sites and additional sites suggested by the Chief of Party.  Acquired bottom samples are addressed with S-57 attribution and recorded in the Final Feature File submitted with this report.</ns2:discussion></ns2:results><ns2:comments/></ns1:bottomSamples></ns1:chartComparison><ns1:additionalResults><ns1:shoreline><ns2:results investigated="Investigated"><ns2:discussion>Shoreline verification was conducted near predicted low water in accordance with the applicable sections of the NOAA HSSD and FPM.  There were 38 assigned features for this survey.  All of the assigned features were addressed as required with the S-57 attribution and recorded in the H12848 Final Features File to best represent the features at survey scale.

Features found by leveling are referenced to estimated depths that have been corrected using discrete zoning, whereas features found using multibeam coverage have depths referenced to the 1-meter final CUBE surface which was corrected using ERZT methods.

The Composite Source File (CSF) and Final Features File have missing SORIND/SORDAT information for 6 land areas (LNDARE) and 24 depth contours (DEPCNT) features.   Category of coastline (CATCOA) information is missing for 20 coastline (COALNE) features.  See the Separates folder for the QC Tools pdf output for &quot;scan features&quot;.</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>Edward J. Van Den Ameele, CAPT/NOAA</ns2:approverName><ns2:approverTitle>Commanding Officer, NOAA Ship Rainier</ns2:approverTitle><ns2:approvalDate>2016-10-05</ns2:approvalDate></ns1:signingPersonnel><ns1:signingPersonnel><ns2:approverName>Steven Loy, LT/NOAA</ns2:approverName><ns2:approverTitle>Field Operations Officer, NOAA Ship Rainier</ns2:approverTitle><ns2:approvalDate>2016-10-05</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>2016-10-05</ns2:approvalDate></ns1:signingPersonnel><ns1:signingPersonnel><ns2:approverName>Michael G. Bloom</ns2:approverName><ns2:approverTitle>Hydrographic Survey Technician, NOAA Ship Rainier</ns2:approverTitle><ns2:approvalDate>2016-10-05</ns2:approvalDate></ns1:signingPersonnel></ns1:approvalSheet></ns1:descriptiveReport>