<?xml version="1.0" encoding="UTF-8"?><ns1:descriptiveReport xmlns:ns1="http://svn.pydro.noaa.gov/2015/02/DescriptiveReport" xmlns:ns2="http://svn.pydro.noaa.gov/2015/02/AllGlobalTypes" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://svn.pydro.noaa.gov/2015/02/DescriptiveReport http://svn.pydro.noaa.gov/2015/02/DR.xsd"><ns1:metadata><ns1:projectMetadata><ns2:number>OPR-P136-RA-15</ns2:number><ns2:name>North Coast Kodiak Island, Alaska</ns2:name><ns2:generalLocality>Kodiak Island, Alaska</ns2:generalLocality><ns2:fieldUnit>NOAA Ship Rainier</ns2:fieldUnit></ns1:projectMetadata><ns1:registryMetadata><ns2:registryNumber>H12691</ns2:registryNumber><ns2:sheetID>2</ns2:sheetID><ns2:registryInstructions xsi:nil="true"></ns2:registryInstructions><ns2:sublocality>Viekoda Bay</ns2:sublocality><ns2:stateOrTerritory>Alaska</ns2:stateOrTerritory><ns2:country>United States</ns2:country><ns2:scale>40000</ns2:scale></ns1:registryMetadata><ns1:surveyMetadata><ns2:year>2015</ns2:year><ns2:chiefOfParty>Edward J. Van Den Ameele, CDR/NOAA</ns2:chiefOfParty><ns2:projectType>Navigable Area</ns2:projectType><ns2:PIDate>2015-09-09</ns2:PIDate><ns2:datesOfSurvey><ns2:start>2015-09-20</ns2:start><ns2:end>2015-10-21</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>The purpose of this survey is to provide contemporary surveys to update National Ocean Service (NOS) nautical charts. All separates are filed
with the hydrographic data. Any revisions to the Descriptive Report (DR) generated during office processing are shown in bold red italic text. The
processing branch maintains the DR as a field unit product, therefore, all information and recommendations within the body of the DR are considered
preliminary unless otherwise noted. The final disposition of surveyed features is represented in the OCS nautical chart update products. All pertinent
records for this survey, including the DR, are archived at the National Centers for Environmental Information (NCEI) and can be retrieved via http://
www.ncei.noaa.gov/.</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 &quot;Viekoda Bay&quot; within the Project Instructions. The area encompasses approximately 34 square nautical miles, which includes Viekoda Bay, Uganik East Passage, and Terror Bay (Figure 1).</ns2:discussion><ns2:limits><ns2:northWest><ns2:latitude hemisphere="N">57.9843308611</ns2:latitude><ns2:longitude hemisphere="W">153.311034611</ns2:longitude></ns2:northWest><ns2:southEast><ns2:latitude hemisphere="N">57.7307758056</ns2:latitude><ns2:longitude hemisphere="W">153.212083083</ns2:longitude></ns2:southEast></ns2:limits><ns2:images><ns2:caption>H12691 survey area as assigned in Project Instructions (Charts 16594_1 and 16597_1).</ns2:caption><ns2:link>SupportFiles\Survey Limits.jpg</ns2:link></ns2:images><ns2:comments/></ns1:areaDescription><ns1:surveyLimits><ns2:results deviation="false"><ns2:discussion>Survey limits were acquired 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) 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 IHO compliance tool within Pydro was used to analyze multibeam echosounder (MBES) data density. All finalized surfaces meet the HSSD data density requirement (Figures 2-6).</ns2:discussion><ns2:images><ns2:caption>Pydro derived histogram plot  showing HSSD compliance of H12691 MBES data within the 1-meter finalized CUBE surface.</ns2:caption><ns2:link>SupportFiles\H12691_MB_1m_MLLW_Final_Density.png</ns2:link></ns2:images><ns2:images><ns2:caption>2-meter finalized CUBE surface data density compliance.</ns2:caption><ns2:link>SupportFiles\H12691_MB_2m_MLLW_Final_Density.png</ns2:link></ns2:images><ns2:images><ns2:caption>4-meter finalized CUBE surface data density compliance.</ns2:caption><ns2:link>SupportFiles\H12691_MB_4m_MLLW_Final_Density.png</ns2:link></ns2:images><ns2:images><ns2:caption>8-meter finalized CUBE surface data density compliance.</ns2:caption><ns2:link>SupportFiles\H12691_MB_8m_MLLW_Final_Density.png</ns2:link></ns2:images><ns2:images><ns2:caption>16-meter finalized CUBE surface data density compliance.</ns2:caption><ns2:link>SupportFiles\H12691_MB_16m_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>100m spaced Set Line Spacing with Single Beam Echosounder (SBES) or MBES with concurrent backscatter.</ns2:requiredCoverage></ns2:coverageRequirement><ns2:coverageRequirement><ns2:waterDepth>Greater than 8 meters water depth</ns2:waterDepth><ns2:requiredCoverage>MBES with concurrent backscatter.</ns2:requiredCoverage></ns2:coverageRequirement><ns2:results deviation="true"><ns2:discussion>Complete MBES coverage was achieved within the limits of hydrography as specified in the Project Instructions with following exceptions:

Line 0013 acquired by S221 on DN263 and line 2207 acquired by launch 2802 on DN275 would not accept Applanix POSPac Smoothed Best Estimate of Trajectory (SBET) corrections.  Therefore, these lines could not be analyzed using the Ellipsoidally Referenced Zoned Tides (ERZT) method. Holidays were only created by the removal of line 0013. These holidays are in relatively deep water where no threats to safe navigation exist (Figure 7). 

Due to time constraints, nearshore acquisition along some stretches of Viekoda Bay did not meet coverage requirements. On the final day of acquisition (DN294), priority was assigned to areas where reaching the 4-meter contour provided more coverage over dynamic seafloor where hazards could potentially exist (Figures 8-10).

The coverage requirement was not met in areas that could not be navigated safely due to dangerous shoals, which were widespread throughout the survey area (Figure 11).

At the head of Viekoda Bay the seafloor was very shoal. During shoreline verification, skiffs were not even able to navigate these waters safely. Due to these factors and time constraints, survey coverage did not reach the entire southeast extent of the sheet limits (Figure 12).

A holiday measuring approximately 510 meters long and 4 to 20 meters wide along the western side of Viekoda bay resulted from HYPACK/HYSWEEP software errors on launch 2802 DN294. The HYPACK created matrix crashed multiple times within the HYSWEEP module which resulted in data loss. This system malfunction occurred during the final hours of data acquisition and no time was available to reacquire over the holiday (Figure 13).

On launch 2803 DN264, the Applanix POSMV primary antenna lost satellite connectivity. This resulted in heave artifacts where the data could not be sufficiently corrected. It was necessary to delete lines affected by this artifact which resulted in holidays. Where one line was deleted, the shoalest point in proximity (37 meters) has full survey coverage (Figure 14). Where another was deleted, the survey coverage reaches the 4-meter contour (Figure 15).

A holiday measuring approximately 26 meters long by 8 meters wide is present at the end of line 2803_2015_2950008. Due to time constraints on the final day of acquisition, the holiday was unable to be covered (Figure 16).</ns2:discussion><ns2:images><ns2:caption>Line 0013 acquired by S221 on DN263 and line 2207 acquired by launch 2802 on DN275. Holidays exist where line 0013 has been removed from the grid. No holidays exist where line 2207 has been deleted.</ns2:caption><ns2:link>SupportFiles\No SBET Holidays.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>Rocky area off western shore of Veikoda Bay was not completely covered due to time constraints.</ns2:caption><ns2:link>SupportFiles\Rky Area Holiday.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>Northwest of Rolling Point, survey coverage only reached 6 to 7 fathoms.</ns2:caption><ns2:link>SupportFiles\Rolling Point coverage requirements fail.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>Northwest of Seiba Point, survey coverage only reached 4 to 6 fathoms.</ns2:caption><ns2:link>SupportFiles\Seiba Point coverage requirements fail.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>The many shoals surrounding Naugolka Point made it especially difficult to survey. Coverage was not met where navigation was unsafe.</ns2:caption><ns2:link>SupportFiles\Naugolka coverage requirements fail.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>Towards the head of Viekoda Bay, survey coverage does not meet the southeast extents of the sheet limits. Depths along this coverage range from approximately 6.5 to 8 fathoms. </ns2:caption><ns2:link>SupportFiles\Head of Viekoda Bay coverage fail.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>Holiday resulting from a HYPACK/HYSWEEP system crash on launch 2802 DN294.</ns2:caption><ns2:link>SupportFiles\HYSWEEP crash holiday.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>Holiday resulting from loss of Applanix POSMV satellite connectivity on launch 2803 DN264.</ns2:caption><ns2:link>SupportFiles\2803 DN264 line 2036 delete holiday.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>Holiday resulting from loss of Applanix POSMV satellite connectivity on launch 2803 DN264.</ns2:caption><ns2:link>SupportFiles\2803 DN264 line 1825 delete holiday.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>Holiday at the end of line 2950008 acquired by launch 2803 on DN294.</ns2:caption><ns2:link>SupportFiles\Gap Holiday Viekoda Bay.jpg</ns2:link></ns2:images></ns2:results><ns2:comments/></ns1:surveyCoverage><ns1:coverageGraphic><ns2:caption>H12691 MBES coverage overlay on Chart 16594_1.</ns2:caption><ns2:link>SupportFiles\16594 Coverage.jpg</ns2:link></ns1:coverageGraphic><ns1:coverageGraphic><ns2:caption>H12691 MBES coverage overlay on Chart 16597_1.</ns2:caption><ns2:link>SupportFiles\16597 Coverage.jpg</ns2:link></ns1:coverageGraphic><ns1:surveyStatistics><ns2:LNM><ns2:vesselLNM><ns2:vessel><ns2:hullID>S221</ns2:hullID><ns2:statistics><ns2:MS_SBES>0</ns2:MS_SBES><ns2:MS_MBES>37.01</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>9.28</ns2:XL_MBES_SBES><ns2:XL_lidar>0</ns2:XL_lidar></ns2:statistics></ns2:vessel><ns2:vessel><ns2:hullID>2801</ns2:hullID><ns2:statistics><ns2:MS_SBES>0</ns2:MS_SBES><ns2:MS_MBES>74.14</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>11.05</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>196.25</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>113.96</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>9.29</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>255.43</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.56</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>676.79</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>37.18</ns2:XL_MBES_SBES><ns2:XL_lidar>0</ns2:XL_lidar><ns2:percentXLLNM>5.49</ns2:percentXLLNM></ns2:totalLNM></ns2:LNM><ns2:totalSurveyStats><ns2:bottomSamples>11</ns2:bottomSamples><ns2:maritimeBoundaryPoints>0</ns2:maritimeBoundaryPoints><ns2:DP>74</ns2:DP><ns2:diveOps>0</ns2:diveOps><ns2:SNM>31.38</ns2:SNM></ns2:totalSurveyStats><ns2:surveyDates>2015-09-20</ns2:surveyDates><ns2:surveyDates>2015-09-21</ns2:surveyDates><ns2:surveyDates>2015-09-22</ns2:surveyDates><ns2:surveyDates>2015-10-01</ns2:surveyDates><ns2:surveyDates>2015-10-02</ns2:surveyDates><ns2:surveyDates>2015-10-08</ns2:surveyDates><ns2:surveyDates>2015-10-15</ns2:surveyDates><ns2:surveyDates>2015-10-19</ns2:surveyDates><ns2:surveyDates>2015-10-21</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>S221</ns2:hullID><ns2:LOA units="meters">70.4</ns2:LOA><ns2:draft units="meters">4.7</ns2:draft></ns1:vessel><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 H12691 was acquired by the NOAA Ship Rainier (S221), launches (2801, 2802, 2803, and 2804) and skiffs (1905, 1906). The ship and launches acquired MBES depth soundings, sound speed profiles, and bottom samples. The skiffs (1905 and 1906) conducted shoreline verification.</ns1:discussion><ns1:comments/></ns1:vessels><ns1:equipment><ns1:majorSystem><ns2:manufacturer>Applanix</ns2:manufacturer><ns2:model>POS MV v4</ns2:model><ns2:type>Positioning and Attitude System</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>Kongsberg</ns2:manufacturer><ns2:model>EM710</ns2:model><ns2:type>MBES</ns2:type></ns1:majorSystem><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>SVP70</ns2:model><ns2:type>Sound Speed System</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 and SBE 19 SEACAT Profiler</ns2:model><ns2:type>Conductivity, Temperature, and Depth Sensor</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>ODIM Brooke Ocean</ns2:manufacturer><ns2:model>MVP 200</ns2:model><ns2:type>Sound Speed System</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>Applied Microsystems</ns2:manufacturer><ns2:model>MicroCTD</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>Multibeam crosslines were acquired using the Reson 7125-B on launches 2801 (RA-4), 2803 (RA-3), and the Reson 7125 SV2 on launch (RA-6). 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 at a 4-meter resolution. This difference surface was compared to the IHO allowable total vertical uncertainty (TVU) standards. In total, 98.94% of the depth differences between H12691 mainscheme and crossline data met HSSD TVU standards (Figure 19). This analysis was performed on H12691 data reduced to Mean Lower-Low Water (MLLW) using Ellipsoidally Referenced Zoned Tides (ERZT) methods. 

A mainscheme to crossline comparison of H12691 data reduced to MLLW using Discrete Zoned Tides was also conducted. Discrete Zoned Tides mainscheme to crossline data differed by an average of 0.028 meters with a standard deviation of 0.416 meters. ERZT mainscheme to crossline data differed by an average of 0.044 meters with a standard deviation of 0.401 meters (Figure 20).</ns2:discussion><ns2:images><ns2:caption>Summary table indicating the percentage of difference surface nodes between H12691 mainscheme and crossline ERZT data that met HSSD allowable TVU standards.</ns2:caption><ns2:link>SupportFiles\ERZT XL IHO.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>H12691 MBES mainscheme to crossline comparison statistics using ERZT (left) and Discrete Zoned Tides (right).</ns2:caption><ns2:link>SupportFiles\ERZT_ZDF XL Diff.jpg</ns2:link></ns2:images><ns2:comments/></ns1:crosslines><ns1:uncertainty><ns2:values><ns2:tideUncertainty><ns2:measured units="meters">0.035003</ns2:measured><ns2:zoning units="meters">0</ns2:zoning><ns2:tideMethod>ERZT</ns2:tideMethod></ns2:tideUncertainty><ns2:soundSpeedUncertainty><ns2:hullID>2801, 2802, 2803, 2804</ns2:hullID><ns2:measuredCTD units="meters/second">3.0</ns2:measuredCTD><ns2:measuredMVP xsi:nil="true"/><ns2:surface units="meters/second">0.15</ns2:surface></ns2:soundSpeedUncertainty><ns2:soundSpeedUncertainty><ns2:hullID>S221</ns2:hullID><ns2:measuredCTD xsi:nil="true"/><ns2:measuredMVP units="meters/second">1.0</ns2:measuredMVP><ns2:surface units="meters/second">0.05</ns2:surface></ns2:soundSpeedUncertainty></ns2:values><ns2:discussion>Uncertainty values were measured and applied in accordance with Section B.4 of the DAPR.

Total Propagated Uncertainty (TPU) values for H12691 were derived from a combination of fixed values for equipment and vessel characteristics, as well as field assigned values for sound speed uncertainties. ERZT uncertainty was calculated using a standard error estimator, wherein the mean of the ERZT standard deviation layer was divided by the square root of an estimated number of survey lines in a given node. This measured tide error uncertainty of 0.035003 meters was entered to account for ERZT processing methods.

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 final grids were calculated in Caris using the &quot;Greater of the Two&quot; of uncertainty and standard deviation (scaled to 95%). The finalized CSAR IHO compliance tool within Pydro was used to analyze H12691 MBES uncertainty (Figures 21-25).

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 uncertrainty defined in the HSSD. Using this method, areas of concentrated IHO non-compliance were found in the final 2-meter CUBE surface on the east and west sides of Terror Bay (Figure 26). On the steep eastern slope, the CUBE surface undulates above and below soundings. Therefore, the CUBE surface exceeds accepted IHO TVU (Figure 26). On the western slope, there is a vertical offset between lines 2802_2015_2812043 and 2802_2015_2652329 which causes the CUBE surface to exceed the accepted IHO TVU (Figure 28). </ns2:discussion><ns2:images><ns2:caption>1-meter finalized surface meets HSSD uncertainty standards.</ns2:caption><ns2:link>SupportFiles\H12691_MB_1m_MLLW_Final_TVU_QC.png</ns2:link></ns2:images><ns2:images><ns2:caption>2-meter finalized surface meets HSSD uncertainty standards.</ns2:caption><ns2:link>SupportFiles\H12691_MB_2m_MLLW_Final_TVU_QC.png</ns2:link></ns2:images><ns2:images><ns2:caption>4-meter finalized surface meets HSSD uncertainty standards.</ns2:caption><ns2:link>SupportFiles\H12691_MB_4m_MLLW_Final_TVU_QC.png</ns2:link></ns2:images><ns2:images><ns2:caption>8-meter finalized surface meets HSSD uncertainty standards.</ns2:caption><ns2:link>SupportFiles\H12691_MB_8m_MLLW_Final_TVU_QC.png</ns2:link></ns2:images><ns2:images><ns2:caption>16-meter finalized surface meets HSSD uncertainty standards.</ns2:caption><ns2:link>SupportFiles\H12691_MB_16m_MLLW_Final_TVU_QC.png</ns2:link></ns2:images><ns2:images><ns2:caption>Areas of HSSD non-compliance in 2-meter finalized surface.</ns2:caption><ns2:link>SupportFiles\Terror Bay HSSD Non-compliance.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>Surface undulation on steep slope causing IHO non-compliance.</ns2:caption><ns2:link>SupportFiles\Non-compliance A.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>Line offset causing IHO non-compliance.</ns2:caption><ns2:link>SupportFiles\Non-compliance B.jpg</ns2:link></ns2:images><ns2:comments/></ns1:uncertainty><ns1:junctions><ns2:discussion>One junction comparison was completed for H12691 with survey H12692, which was acquired concurrently by Rainier.</ns2:discussion><ns2:junction><ns2:survey><ns2:registryNumber>H12692</ns2:registryNumber><ns2:scale>40000</ns2:scale><ns2:year>2015</ns2:year><ns2:fieldUnit>NOAA Ship RAINIER</ns2:fieldUnit><ns2:relativeLocation>NW</ns2:relativeLocation></ns2:survey><ns2:discussion>Overlap with survey H12692 ranges from approximately 200 to 750 meters wide along the northwestern boundary of H12691 (Figure 29). Depths in the junction area range from approximately 4 to 220 meters.  For the respective depths, the difference surface was compared to the allowable TVU standards specified in the HSSD.  Analysis of the difference surface indicated a mean difference of 0.012 meters with a standard deviation of 0.436 meters. In total, 98.64% of the depth differences between H12691 and junction survey H12692 are within allowable uncertainties (Figure 30). </ns2:discussion><ns2:images><ns2:caption>H12691 junction with H12692.</ns2:caption><ns2:link>SupportFiles\Junction.jpg</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\Junction excel.jpg</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="false"><ns2:issue><ns2:title>None Exist</ns2:title><ns2:discussion>There were no conditions or deficiencies that affected equipment operational effectiveness.</ns2:discussion><ns2:comments/></ns2:issue></ns2:results><ns2:comments/></ns1:equipmentEffectiveness><ns1:factorsAffectingSoundings><ns2:results deviation="true"><ns2:issue><ns2:title>Kelp</ns2:title><ns2:discussion>Thick patches of kelp were seen mostly along the eastern and western shore of Viekoda Bay (Figure 31-33). MBES data in these areas were investigated using CARIS Subset Editor. Soundings that obviously represented kelp and not the seafloor were rejected. When unable to clearly distinguish between kelp and the seafloor, the soundings were retained.</ns2:discussion><ns2:images><ns2:caption>Kelp beds along the eastern shore of Viekoda Bay.</ns2:caption><ns2:link>SupportFiles\Kelp - Viekoda Bay.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>Kelp beds along the eastern shore of Seiba Point, Viekoda Bay.</ns2:caption><ns2:link>SupportFiles\Kelp - Viekoda Bay Seiba Pt.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>Kelp beds along the western shore near Rolling Point, Viekoda Bay.</ns2:caption><ns2:link>SupportFiles\Kelp - Viekoda Bay Rolling Pt.jpg</ns2:link></ns2:images><ns2:comments/></ns2:issue></ns2:results><ns2:comments/></ns1:factorsAffectingSoundings><ns1:soundSpeedMethods><ns1:castFrequency>All launch sound speed profiles were acquired using either the SBE 19plus or SBE19 SEACAT 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. For MBES operations conducted on S221 (Rainier), sound speed profiles were acquired using the ODIM Brooke Ocean MVP200 in the same manner and frequency as with the launch CTD casts. A sheet-wide concatenated sound speed file was created and applied to survey lines using the &quot;Nearest in distance within time (4 hours)&quot; profile selection 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><ns2:branchComment concurrence="Concur with clarification"><ns2:comment>It was determined in office review that systematic roll bias errors exist in the data for 2801's RESON
7125, 200kHz transceiver. The HVF contains a roll bias correction of -0.67 degrees, but the data is at
optimal intra-line alignment with a roll bias corrector value of -0.42 degrees.</ns2:comment></ns2:branchComment></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 has been sent to the Processing Branch. Backscatter was not processed by the field unit.</ns2:discussion></ns2:results><ns2:comments><ns2:branchComment concurrence="Concur with clarification"><ns2:comment>Raw backscatter data was submitted to NCEI and data was processed into mosaic GeoTIFF images during office processing.</ns2:comment></ns2:branchComment></ns2:comments></ns1:backscatter><ns1:dataProcessing><ns1:drSoftware><ns1:bathySoftware deviation="true"><ns1:manufacturer>Caris</ns1:manufacturer><ns1:name>HIPS and SIPS</ns1:name><ns1:version>9.0.21</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_3_3.</ns1:featureObjectCatalog><ns1:discussion>  All features were processed using Caris HIPS and SIPS 9.0 and Caris Notebook 3.1.</ns1:discussion><ns1:comments/></ns1:drSoftware><ns1:surfaces><ns1:surface><ns2:surfaceName>H12691_MB_1m_MLLW</ns2:surfaceName><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:resolution units="meters">1</ns2:resolution><ns2:depthRange><ns2:min units="meters">-1.52</ns2:min><ns2:max units="meters">232.21</ns2:max></ns2:depthRange><ns2:surfaceParameter>NOAA_1m</ns2:surfaceParameter><ns2:purpose>Complete MBES</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceName>H12691_MB_2m_MLLW</ns2:surfaceName><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:resolution units="meters">2</ns2:resolution><ns2:depthRange><ns2:min units="meters">-1.46</ns2:min><ns2:max units="meters">224.24</ns2:max></ns2:depthRange><ns2:surfaceParameter>NOAA_2m</ns2:surfaceParameter><ns2:purpose>Complete MBES</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceName>H12691_MB_4m_MLLW</ns2:surfaceName><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:resolution units="meters">4</ns2:resolution><ns2:depthRange><ns2:min units="meters">-1.14</ns2:min><ns2:max units="meters">222.99</ns2:max></ns2:depthRange><ns2:surfaceParameter>NOAA_4m</ns2:surfaceParameter><ns2:purpose>Complete MBES</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceName>H12691_MB_8m_MLLW</ns2:surfaceName><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:resolution units="meters">8</ns2:resolution><ns2:depthRange><ns2:min units="meters">-1.13</ns2:min><ns2:max units="meters">222.67</ns2:max></ns2:depthRange><ns2:surfaceParameter>NOAA_8m</ns2:surfaceParameter><ns2:purpose>Complete MBES</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceName>H12691_MB_16m_MLLW</ns2:surfaceName><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:resolution units="meters">16</ns2:resolution><ns2:depthRange><ns2:min units="meters">-0.42</ns2:min><ns2:max units="meters">222.05</ns2:max></ns2:depthRange><ns2:surfaceParameter>NOAA_16m</ns2:surfaceParameter><ns2:purpose>Complete MBES</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceName>H12691_MB_1m_MLLW_Final</ns2:surfaceName><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:resolution units="meters">1</ns2:resolution><ns2:depthRange><ns2:min units="meters">-2</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>H12691_MB_2m_MLLW_Final</ns2:surfaceName><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:resolution units="meters">2</ns2:resolution><ns2:depthRange><ns2:min units="meters">12</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>H12691_MB_4m_MLLW_Final</ns2:surfaceName><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:resolution units="meters">4</ns2:resolution><ns2:depthRange><ns2:min units="meters">33</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>H12691_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">160</ns2:max></ns2:depthRange><ns2:surfaceParameter>NOAA_8m</ns2:surfaceParameter><ns2:purpose>Complete MBES</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceName>H12691_MB_16m_MLLW_Final</ns2:surfaceName><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:resolution units="meters">16</ns2:resolution><ns2:depthRange><ns2:min units="meters">144</ns2:min><ns2:max units="meters">320</ns2:max></ns2:depthRange><ns2:surfaceParameter>NOAA_16m</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. Twenty-seven soundings were designated in accordance with HSSD requirements.

The 1-meter, 2-meter, and 4-meter grid resolution ranges were expanded to minimize holidays due to acoustic shadows around shoals and on steep slopes, and to include the full range of survey coverage. See Appendix V for required documentation.</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:standard_or_ERZT used="true"><ns2:methodsUsed>ERZT</ns2:methodsUsed><ns2:tideStations><ns2:NWLONGauges><ns2:stationName>Seldovia</ns2:stationName><ns2:stationID>9455500</ns2:stationID></ns2:NWLONGauges><ns2:subordinateGauges><ns2:stationName>South Arm, Uganik Bay, AK</ns2:stationName><ns2:stationID>9457588</ns2:stationID></ns2:subordinateGauges></ns2:tideStations><ns2:correctorFiles><ns2:waterLevels><ns2:fileName>9455500</ns2:fileName><ns2:status>Final Approved</ns2:status></ns2:waterLevels><ns2:tideCorrectors><ns2:fileName>P136RA2015_Rev2_CORP</ns2:fileName><ns2:status>Final</ns2:status></ns2:tideCorrectors></ns2:correctorFiles><ns2:finalTides><ns2:dateSubmitted>2015-10-23</ns2:dateSubmitted><ns2:dateReceived>2016-03-07</ns2:dateReceived></ns2:finalTides><ns2:discussion>The NWLON tide station in Seldovia, AK (9455500) and the subordinate tide station installed by Rainier personnel in South Arm, Uganik Bay, AK (9457588) served as the controls for datum determination and water level reducers for survey H12691. A complete description of the vertical and horizontal control for this survey can be found in the accompanying OPR-P136-RA-15 Horizontal and Vertical Control Report (HVCR), submitted under a separate cover.</ns2:discussion><ns2:comments/></ns2:standard_or_ERZT><ns2:VDATUM_or_constantSep used="true"><ns2:ellipsoidToChartDatumSepFile><ns2:fileName>H12691_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 ZDF tide file. GPS tides 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-15 ERS/ERZT Capability Memo included with the supplemental correspondence.</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 5 North</ns2:projection><ns2:PPK used="true"><ns2:methodsUsed>Smart Base</ns2:methodsUsed><ns2:baseStations><ns2:CORSStations><ns2:HVCRSiteID>AC27</ns2:HVCRSiteID><ns2:stationID>AC27MNEIL_AK2004</ns2:stationID></ns2:CORSStations><ns2:CORSStations><ns2:HVCRSiteID>AC08</ns2:HVCRSiteID><ns2:stationID>CAPDOUGLASAK2007</ns2:stationID></ns2:CORSStations><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>KOD6</ns2:HVCRSiteID><ns2:stationID>KODIAK 6</ns2:stationID></ns2:CORSStations><ns2:CORSStations><ns2:HVCRSiteID>KOD5</ns2:HVCRSiteID><ns2:stationID>KODIAK 5</ns2:stationID></ns2:CORSStations><ns2:CORSStations><ns2:HVCRSiteID>AC34</ns2:HVCRSiteID><ns2:stationID>OldHarbor_AK2006</ns2:stationID></ns2:CORSStations><ns2:CORSStations><ns2:HVCRSiteID>AC39</ns2:HVCRSiteID><ns2:stationID>SHUYAKISSPAK2006</ns2:stationID></ns2:CORSStations><ns2:CORSStations><ns2:HVCRSiteID>AC45</ns2:HVCRSiteID><ns2:stationID>SITKINAKISAK2006</ns2:stationID></ns2:CORSStations><ns2:CORSStations><ns2:HVCRSiteID>AC24</ns2:HVCRSiteID><ns2:stationID>KINGSALMONAK2006</ns2:stationID></ns2:CORSStations><ns2:CORSStations><ns2:HVCRSiteID>SELD</ns2:HVCRSiteID><ns2:stationID>SELD_AKDA_AK2000</ns2:stationID></ns2:CORSStations><ns2:CORSStations><ns2:HVCRSiteID>AC26</ns2:HVCRSiteID><ns2:stationID>CAPE_GULL_AK2008</ns2:stationID></ns2:CORSStations><ns2:CORSStations><ns2:HVCRSiteID>AC02</ns2:HVCRSiteID><ns2:stationID>AkhiokCorpAK2005</ns2:stationID></ns2:CORSStations></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 xsi:nil="true"></ns2:discussion><ns2:comments/></ns2:DGPS><ns2:comments/></ns1:horizontalControl><ns1:additionalIssues><ns2:issue><ns2:title>Lines without SBETs</ns2:title><ns2:discussion>Applanix POSPac Smooth Best Estimate and Trajectory (SBET) corrections could not be applied to line 0013 acquired by S221 on DN263 because the Delayed Heave time extents do not entirely cover the line. SBET corrections were also not applied to line 2207 acquired by launch 2802 on DN275 because Delayed Heave failed to apply to the line. Therefore, these lines could not be analyzed using ERZT methods. The HDCS data for these lines has been retained for submission, but has been omitted from the final CUBE surfaces.</ns2:discussion><ns2:comments/></ns2:issue><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 16-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. Charts 16594, 16597, and 16576 show good agreement where they overlap. Chart 16594 was used to make comparisons in Viekoda Bay and Chart 16597 was used to make comparisons in Uganik East Passage and Terror Bay</ns2:discussion><ns2:comments><ns2:branchComment concurrence="Concur with clarification"><ns2:comment>As noted but not tabulated, this survey also falls on chart 16576 which includes depth curves at 10 fathom intervals. Shoaling and contour trends are similar for 16576 and chart 16594.

 </ns2:comment></ns2:branchComment><ns2:branchComment concurrence="Concur with clarification"><ns2:comment>It should also be noted that chart 16594 corresponds to ENC US4AK5PM and chart 16597 corresponds to ENC US4AK5QM.</ns2:comment></ns2:branchComment></ns2:comments></ns1:methods><ns1:charts><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 Viekoda Bay, the 10-fathom and 3-fathom contours are mostly seen to be inshore from what is charted (Figures 34-36). There are also many shoals offshore of the charted 10-fathom contour (Figures 37). The 50-fathom contour tends to fall further offshore than what is charted (Figures 38-39). Derived soundings often disagree with what is charted. Many shoaling trends are seen offshore and deepening trends are seen nearshore.</ns2:discussion><ns2:images><ns2:caption>Variation of the 10 and 3-fathom contour showing deeper depths inshore of what is charted.</ns2:caption><ns2:link>SupportFiles\Viekoda Bay 10fm_3fm local variation.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>Variation of the 10 and 3-fathom contour showing deeper depths inshore of what is charted.</ns2:caption><ns2:link>SupportFiles\Viekoda Bay 10fm_3fm local variation 2.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>Variation of the 10 and 3-fathom contour showing deeper depths inshore of what is charted. Some shoals are offshore of the charted 10-fathom contour.</ns2:caption><ns2:link>SupportFiles\Viekoda Bay 10fm_3fm local variation 3.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>Shoals offshore of the 10-fathom contour.</ns2:caption><ns2:link>SupportFiles\Viekoda scatterred shoals.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>Variation of the 50-fathom contour which shows shoaler depths extending offshore. A sounding shoaler by 23-fathoms is highlighted.</ns2:caption><ns2:link>SupportFiles\Viekoda Bay 50fm variation 2.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>Variation of the 50-fathom contour, which shows shoaler depths extending further offshore.</ns2:caption><ns2:link>SupportFiles\Viekoda Bay 50fm variation.jpg</ns2:link></ns2:images><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>The overall trends in Uganik East Passage and Terror Bay are similar to what is seen in Viekoda Bay. Many shoaling trends are also seen offshore (Figures 40-41). Derived soundings show deepening trends along the western nearshore (42), while derived soundings along the eastern nearshore generally stay consistent with what is charted. There are also shoals offshore of the charted 10-fathom contour (Figure 43-44).</ns2:discussion><ns2:images><ns2:caption>Soundings are generally shoaler than what is charted through Uganik East Passage and Terror Bay.</ns2:caption><ns2:link>SupportFiles\Uganik East_Terror shoal trend.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>Variation of the 10-fathom contour which shows shoaler depths further offshore than what is charted.</ns2:caption><ns2:link>SupportFiles\Terror 10fm variation.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>Deepening trend along western nearshore.</ns2:caption><ns2:link>SupportFiles\deep soundings nearshore.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>A selection of soundings much shoaler than what is charted.</ns2:caption><ns2:link>SupportFiles\Terror shoals.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>Shoals offshore of the charted 10-fathom contour.</ns2:caption><ns2:link>SupportFiles\Terror shoals 2.jpg</ns2:link></ns2:images><ns2:comments/></ns2:rasterChart><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="None Exist"><ns2:discussion>No charted features exist for this survey.</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>17</ns2:numberSubmitted><ns2:report><ns2:title>H12691 DTON Report</ns2:title><ns2:dateSubmitted>2015-09-28</ns2:dateSubmitted></ns2:report><ns2:report><ns2:title>H12691 DTON Report</ns2:title><ns2:dateSubmitted>2015-12-02</ns2:dateSubmitted></ns2:report><ns2:report><ns2:title>H12691 DTON Report</ns2:title><ns2:dateSubmitted>2016-05-06</ns2:dateSubmitted></ns2:report><ns2:discussion>Danger to Navigation Reports are included in Appendix I of this report.</ns2:discussion></ns2:results><ns2:comments><ns2:branchComment concurrence="Concur with clarification"><ns2:comment>DTON reports are appended. Note that final processing of data has resulted in minor changes to depths for some of the features and soundings reported. It should also be noted that some of the DTONs initially reported as soundings were later classified and compiled as rocks. In addition, within the context of the complete update to the chart and chart scale , some of the submitted DTONs were not selected during compilation, mostly due to shoaler and more prominent features in vicinity.</ns2:comment></ns2:branchComment></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>Ten proposed bottom sample locations were identified in the Project Reference File and eleven were collected. Samples were collected in the vicinity of the proposed sites. 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 147 assigned features for this survey. All but one of the assigned features were addressed as required with the S-57 attribution and recorded in the H12691 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.</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><ns2:branchComment concurrence="Do not concur"><ns2:comment>The surveyed extents include two Fish Farm area features which represent navigationally significant
underwater obstructions. The location and intended purpose of charted Fish Farm features in the
surveyed area were verified and addressed.</ns2:comment></ns2:branchComment></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, CD/NOAA</ns2:approverName><ns2:approverTitle>Commanding Officer</ns2:approverTitle><ns2:approvalDate>2016-05-10</ns2:approvalDate></ns1:signingPersonnel><ns1:signingPersonnel><ns2:approverName>Steven Loy, LT/NOAA</ns2:approverName><ns2:approverTitle>Field Operations Officer</ns2:approverTitle><ns2:approvalDate>2016-05-10</ns2:approvalDate></ns1:signingPersonnel><ns1:signingPersonnel><ns2:approverName>James B. Jacobson</ns2:approverName><ns2:approverTitle>Chief Survey Technician</ns2:approverTitle><ns2:approvalDate>2016-05-10</ns2:approvalDate></ns1:signingPersonnel><ns1:signingPersonnel><ns2:approverName>Eli R. Smith</ns2:approverName><ns2:approverTitle>Sheet Manager</ns2:approverTitle><ns2:approvalDate>2016-05-10</ns2:approvalDate></ns1:signingPersonnel></ns1:approvalSheet></ns1:descriptiveReport>