<?xml version="1.0" encoding="UTF-8"?><ns1:descriptiveReport xmlns:ns1="http://Pydro.com/2014/02/DescriptiveReport" xmlns:ns2="http://Pydro.com/2014/02/AllGlobalTypes" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><ns1:metadata><ns1:projectMetadata><ns2:number>OPR-P136-RA-14</ns2:number><ns2:name>North Coast of Kodiak Island, AK</ns2:name><ns2:generalLocality>North Coast of Kodiak Island, AK</ns2:generalLocality><ns2:fieldUnit>NOAA Ship Rainier</ns2:fieldUnit></ns1:projectMetadata><ns1:registryMetadata><ns2:registryNumber>H12689</ns2:registryNumber><ns2:sheetID>2</ns2:sheetID><ns2:registryInstructions xsi:nil="true"></ns2:registryInstructions><ns2:sublocality>Afognak Strait and Whale Passage</ns2:sublocality><ns2:stateOrTerritory>Alaska</ns2:stateOrTerritory><ns2:country>United States</ns2:country><ns2:scale>15000</ns2:scale></ns1:registryMetadata><ns1:surveyMetadata><ns2:year>2014</ns2:year><ns2:chiefOfParty>Edward J. Van Den Ameele, CDR/NOAA</ns2:chiefOfParty><ns2:projectType>Navigable Area</ns2:projectType><ns2:PIDate>2014-04-01</ns2:PIDate><ns2:datesOfSurvey><ns2:start>2014-05-06</ns2:start><ns2:end>2014-07-08</ns2:end></ns2:datesOfSurvey><ns2:equipmentTypes><ns2:soundingEquipment>Multibeam Echosounder</ns2:soundingEquipment><ns2:imageryEquipment>Multibeam Echosounder Backscatter</ns2:imageryEquipment></ns2:equipmentTypes><ns2:acquisition><ns2:units>meters</ns2:units></ns2:acquisition><ns2:horizontalCoordinateSystem zone="5">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>Dates of survey above are incorrect.  Actual dates of survey are between 5/7/2014 to 7/9/2014.</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 Sheet 2: &quot;Afognak Strait and Whale Passage&quot; within the Project Instructions. The area encompasses approximately 21.0 square nautical miles of Afognak Strait and Whale Passage, and the eastern portions of Dry Spruce Bay and Kupreanof Strait (Figures 1-2).</ns2:discussion><ns2:limits><ns2:northWest><ns2:latitude hemisphere="N">58.0157702778</ns2:latitude><ns2:longitude hemisphere="W">152.737725556</ns2:longitude></ns2:northWest><ns2:southEast><ns2:latitude hemisphere="N">57.8904852778</ns2:latitude><ns2:longitude hemisphere="W">153.0732675</ns2:longitude></ns2:southEast></ns2:limits><ns2:images><ns2:caption>Overlay of H12689 sheet limits (blue) and the acquired survey coverage (red) on Chart 16594.</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>This project is being conducted in support of NOAA's Office of Coast Survey to provide contemporary hydrographic data in order to update the nautical charting products and reduce survey backlog in the area. The nautical chart updates 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>Data acquired on survey H12689 met complete multibeam echosounder (MBES) coverage requirements outlined in Section 5.2.2.2 of the HSSD, including data density requirements. Overall, the required data density was achieved in 99.928% of nodes.</ns2:discussion><ns2:comments><ns2:branchComment concurrence="Concur with clarification"><ns2:comment>During review at the Branch, a density analysis was conducted on each of the finalized surfaces. The requirement of five soundings per node was achieved in: 99.94% of nodes in the 1m surface, 99.99% of nodes in the 2m surface, 99.96% of nodes in the 4m surface, and 99.72% of nodes in the 8m surface.  There was an overall compliance rate of 99.95%.</ns2:comment></ns2:branchComment></ns2:comments></ns1:surveyQuality><ns1:surveyCoverage><ns2:results deviation="true"><ns2:discussion>Complete multibeam echosounder (MBES) coverage was achieved within the limits of hydrography as specified in the Project Instructions with the following exceptions:

Survey coverage did not meet the sheet limits along many portions near the shoreline and islets; conditions in these areas were deemed unsafe due to currents and proximity to shore (Figure 3).

Survey coverage also did not meet the sheet limits in The Slough and The Narrows surrounding Little Raspberry Island since they were considered largely unnavigable. Pushing survey operations further inshore in this area would have brought upon unnecessary safety risks (Figure 4).

A roll-stabilization issue with the Reson 7125 SV2 sonar on Launch 2804 resulted in degradation of some H12689 bathymetric data (see Section B.2.5). The affected line (2804_2014RA1902300) ,which was run just north of Ostrovka Point, was removed resulting in an approximately 9 square meter holiday. The surrounding data was examined; no navigationally significant features were present (Figure 5).

Four small holidays measuring 4 to 7 meters long appear in Fox Bay. Data over this area was acquired by both Launch 2801 and 2802 on days 156 and 158 respectively. The acquisition log for Launch 2801 on day 156 indicates issues with Hypack software crashes and associated gaps occurring in the matrix. The acquisition log for Launch 2802 on day 158 indicates several Reson time synchronization errors and the associated &quot;roll blowouts,&quot; the same problem seen with the Reson 7125 SV2 on Launch 2804 described previously. As noted in the Final Feature File, the rocks assigned for investigation in this area were not found. The surrounding data was examined; no navigationally significant features were present (Figure 6).</ns2:discussion><ns2:images><ns2:caption>Multibeam coverage did not reach the shoreline due to currents and proximity to shore (Chart 16594).</ns2:caption><ns2:link>SupportFiles\Survey Coverage_Currents and Shore.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>Multibeam coverage did not reach the sheet limits in the unnavigable areas surrounding Little Raspberry Island.</ns2:caption><ns2:link>SupportFiles\Survey Coverage_Slough and Narrows.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>Holiday resulting from removing line affected by Reson 7125 SV2 roll timing issue.</ns2:caption><ns2:link>SupportFiles\Holiday from deleted line.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>Holidays located in Fox Bay.</ns2:caption><ns2:link>SupportFiles\Fox Bay Holidays.jpg</ns2:link></ns2:images></ns2:results><ns2:comments><ns2:branchComment concurrence="Comment Only"><ns2:comment>In addition to the areas outlined above, coverage did not meet the NALL in a majority of the area between Shoal Pt. and Head Pt. </ns2:comment></ns2:branchComment></ns2:comments></ns1:surveyCoverage><ns1:coverageGraphic><ns2:caption>H12689 depth-colored MBES coverage overlay on Chart 16594.</ns2:caption><ns2:link>SupportFiles\Coverage Area.jpg</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>190.8</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.92</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>152.2</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>97.2</ns2:MS_MBES><ns2:MS_lidar>0</ns2:MS_lidar><ns2:MS_SSS>0</ns2:MS_SSS><ns2:MS_SBES_MBES>0</ns2:MS_SBES_MBES><ns2:MS_MBES_SSS>0</ns2:MS_MBES_SSS><ns2:MS_SBES_SSS>0</ns2:MS_SBES_SSS><ns2:XL_MBES_SBES>28.6</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>231.6</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>33.4</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>685.3</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>108.3</ns2:XL_MBES_SBES><ns2:XL_lidar>0</ns2:XL_lidar><ns2:percentXLLNM>15.8</ns2:percentXLLNM></ns2:totalLNM></ns2:LNM><ns2:totalSurveyStats><ns2:bottomSamples>7</ns2:bottomSamples><ns2:AWOIS>0</ns2:AWOIS><ns2:maritimeBoundaryPoints>0</ns2:maritimeBoundaryPoints><ns2:DP>0</ns2:DP><ns2:diveOps>0</ns2:diveOps><ns2:SNM>21.0</ns2:SNM></ns2:totalSurveyStats><ns2:surveyDates>2014-05-06</ns2:surveyDates><ns2:surveyDates>2014-05-07</ns2:surveyDates><ns2:surveyDates>2014-05-08</ns2:surveyDates><ns2:surveyDates>2014-05-09</ns2:surveyDates><ns2:surveyDates>2014-05-10</ns2:surveyDates><ns2:surveyDates>2014-05-12</ns2:surveyDates><ns2:surveyDates>2014-05-13</ns2:surveyDates><ns2:surveyDates>2014-05-14</ns2:surveyDates><ns2:surveyDates>2014-05-18</ns2:surveyDates><ns2:surveyDates>2014-05-19</ns2:surveyDates><ns2:surveyDates>2014-05-20</ns2:surveyDates><ns2:surveyDates>2014-05-21</ns2:surveyDates><ns2:surveyDates>2014-06-02</ns2:surveyDates><ns2:surveyDates>2014-06-03</ns2:surveyDates><ns2:surveyDates>2014-06-04</ns2:surveyDates><ns2:surveyDates>2014-06-05</ns2:surveyDates><ns2:surveyDates>2014-06-06</ns2:surveyDates><ns2:surveyDates>2014-06-07</ns2:surveyDates><ns2:surveyDates>2014-06-09</ns2:surveyDates><ns2:surveyDates>2014-06-14</ns2:surveyDates><ns2:surveyDates>2014-06-16</ns2:surveyDates><ns2:surveyDates>2014-06-28</ns2:surveyDates><ns2:surveyDates>2014-06-29</ns2:surveyDates><ns2:surveyDates>2014-07-08</ns2:surveyDates><ns2:discussion xsi:nil="true"></ns2:discussion><ns2:comments><ns2:branchComment concurrence="Do not concur"><ns2:comment>Table 2: The &quot;Number of DPs&quot; is incorrectly reported as 0 and should be approximately 85.    
Table 3: Dates of survey acquisition were compared to the HDCS data and should include all of the following:  DN 127, 128, 129, 130, 131, 133, 134, 135, 139, 140, 142, 154, 155, 156, 157, 158, 159, 161, 166, 168, 180, 181, and 190.</ns2:comment></ns2:branchComment></ns2:comments></ns1:surveyStatistics></ns1:areaSurveyed><ns1:dataAcquisitionAndProcessing><ns1:equipmentAndVessels><ns1:discussion>Refer to the 2014 Data Acquisition and Processing Report (DAPR) for a complete description of 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 H12689 was acquired by NOAA Ship Rainier's four survey launches (2801, 2802, 2803, and 2804) and two skiffs (1905, 1906). The survey launches acquired MBES depth soundings, sound speed profiles, and bottom samples. The skiffs acquired bottom samples and conducted shoreline verification.</ns1:discussion><ns1:comments/></ns1:vessels><ns1:equipment><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>SeaBat 7125 SV2</ns2:model><ns2:type>MBES</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>Reson</ns2:manufacturer><ns2:model>SVP 71</ns2:model><ns2:type>Sound Speed System</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>Applanix</ns2:manufacturer><ns2:model>POS-MV V4</ns2:model><ns2:type>Vessel Attitude and Positioning System</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>Sea-Bird Electronics, Inc.</ns2:manufacturer><ns2:model>SBE 19 and 19plus SEACAT Profiler</ns2:model><ns2:type>Conductivity, Temperature, and Depth Sensor</ns2:type></ns1:majorSystem><ns1:discussion xsi:nil="true"></ns1:discussion><ns1:comments/></ns1:equipment><ns1:comments/></ns1:equipmentAndVessels><ns1:qualityControl><ns1:crosslines><ns2:discussion>Multibeam crosslines were acquired using the Reson 7125-B on launches 2801 (RA-4), 2803 (RA-3), and the Reson 7125 SV2 on Launch 2804 (RA-6) (Figure 7). A 2-meter CUBE surface was created using only mainscheme lines, a second 2-meter CUBE surface was created using only crosslines, and a difference surface was generated from these two surfaces in Caris at a 2-meter resolution. This difference surface was compared to the allowable uncertainty values within the HSSD for the observed depths and statistics were calculated in Excel. In total, 99.702% of the depth differences between H12689 mainscheme and crossline data are within the requirements of the HSSD (Figure 8). In a portion of two crosslines east of Chernof Point, the outer swath did not meet the HSSD requirements (Figure 9). SBETs were not applied to these lines, and may be the cause of this issue (see Section C.3).</ns2:discussion><ns2:images><ns2:caption>Depth-colored MBES overlay of acquired H12689 crossline data.</ns2:caption><ns2:link>SupportFiles\Crosslines Overview.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>Summary table indicating percentage of difference surface nodes between H12689 mainscheme and crossline data that met HSSD requirements for associated depths.</ns2:caption><ns2:link>SupportFiles\Crossline IHO table.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>Area east of Chernof Point in which depth differences between H12689 mainscheme and crossline data do not meet the HSSD requirements for the associated depths.</ns2:caption><ns2:link>SupportFiles\HSSD compliance failure.jpg</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.122</ns2:zoning></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:values><ns2:discussion>Uncertainty values were measured and applied in accordance with Section B.4 of the DAPR.

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%). To visualize where uncertainty accuracy 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. To quantify the extent to which accuracy requirements were met, the HSSD Compliance layers were queried within Caris and examined in Excel. Overall, 99.928% of the nodes of survey H12689 met the uncertainty requirements specified in the HSSD (Figure 10). These HSSD Compliance layers were retained in the submitted surfaces.</ns2:discussion><ns2:images><ns2:caption>H12689 met HSSD uncertainty standards in 99.928% of all nodes.</ns2:caption><ns2:link>SupportFiles\HSSD Compliance.jpg</ns2:link></ns2:images><ns2:comments/></ns1:uncertainty><ns1:junctions><ns2:discussion>Four junction comparisons were completed for H12689 (Figure 11). One survey (H12690) was acquired concurrently with this survey, and three surveys (H12512, H12495 and H12496) were completed in 2012 by NOAA Ship Rainier. Depth comparisons were performed using Caris difference surfaces.</ns2:discussion><ns2:images><ns2:caption>Overview of junctions with survey H12689.</ns2:caption><ns2:link>SupportFiles\H12689 Junctions.jpg</ns2:link></ns2:images><ns2:junction><ns2:survey><ns2:registryNumber>H12690</ns2:registryNumber><ns2:scale>78900</ns2:scale><ns2:year>2014</ns2:year><ns2:fieldUnit>NOAA Ship Rainier</ns2:fieldUnit><ns2:relativeLocation>W</ns2:relativeLocation></ns2:survey><ns2:discussion>Overlap with survey H12690 was approximately 300 to 600 meters wide, covering an area of 0.59 square nautical miles along the western boundary of H12689 (Figure 11). Depths in the junction area range from approximately 4 to 110 meters. For the respective depths, the difference surface was compared to the allowable TVU (Total Vertical Uncertainty) standards specified in the HSSD. In total, 99.031% of the depth differences between H12689 and junction survey H12690 are within allowable uncertainties.</ns2:discussion><ns2:comments/></ns2:junction><ns2:junction><ns2:survey><ns2:registryNumber>H12512</ns2:registryNumber><ns2:scale>78900</ns2:scale><ns2:year>2012</ns2:year><ns2:fieldUnit>NOAA Ship Rainier</ns2:fieldUnit><ns2:relativeLocation>S</ns2:relativeLocation></ns2:survey><ns2:discussion>Overlap with survey H12512 was approximately 130 to 440 meters wide, covering an area of 0.03 square nautical miles along the southern boundary of H12689 (Figure 11). Depths in the junction area range from 4 to 37 meters. For the respective depths, the difference surface was compared to the allowable TVU standards specified in the HSSD. In total, 96.230% of the depth differences between H12689 and junction survey H12512 are within allowable uncertainties.</ns2:discussion><ns2:comments/></ns2:junction><ns2:junction><ns2:survey><ns2:registryNumber>H12495</ns2:registryNumber><ns2:scale>78900</ns2:scale><ns2:year>2012</ns2:year><ns2:fieldUnit>NOAA Ship Rainier</ns2:fieldUnit><ns2:relativeLocation>NE</ns2:relativeLocation></ns2:survey><ns2:discussion>Overlap with survey H12495 was approximately 220 to 300 meters wide, covering an area of 0.14 square nautical miles along the northeastern boundary of H12689 (Figure 11). Depths in the junction area range from 5 to 15 meters. For the respective depths, the difference surface was compared to the allowable TVU standards specified in the HSSD. In total, 99.653% of the depth differences between H12689 and junction survey H12495 are within allowable uncertainties.</ns2:discussion><ns2:comments/></ns2:junction><ns2:junction><ns2:survey><ns2:registryNumber>H12496</ns2:registryNumber><ns2:scale>78900</ns2:scale><ns2:year>2012</ns2:year><ns2:fieldUnit>NOAA Ship Rainier</ns2:fieldUnit><ns2:relativeLocation>SE</ns2:relativeLocation></ns2:survey><ns2:discussion>Overlap with survey H12496 was approximately 300 to 900 meters wide, covering an area of 0.62 square nautical miles along the southeastern boundary of H12689 (Figure 11). Depths in the junction area range from 4 to 128 meters. For the respective depths, the difference surface was compared to the allowable TVU standards specified in the HSSD. In total, 97.464% of the depth differences between H12689 and junction survey H12496 are within allowable uncertainties.</ns2:discussion><ns2:comments/></ns2:junction><ns2:comments><ns2:branchComment concurrence="Do not concur"><ns2:comment>The scale of all four junctioning surveys listed in Table 8 should be 1:40000, not 1:78900.</ns2:comment></ns2:branchComment><ns2:branchComment concurrence="Concur with clarification"><ns2:comment>During review at the Branch, a difference surface was created for each junction by differencing the 8-meter Combined surface of H12689 with the 8-meter Combined surface of the junctioning survey. Areas where differences exceeded allowable uncertainty limits were investigated and could be attributed to the steep and/or rocky nature of the seafloor. Statistics were generated from each difference surface which indicate: for junctioning survey H12690, 95% of nodes were within +/-0.51 meters; for junctioning survey H12512, 95% of nodes were within +/-0.63 meters; for junctioning survey H12495, 95% of nodes were within +/-0.27 meters; and for H12496, 95% of nodes were within +/-0.55 meters.</ns2:comment></ns2:branchComment></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>Reson 7125 SV2 Roll-Stabilization Issue</ns2:title><ns2:discussion>An equipment issue with the Reson 7125 SV2 sonar resulted in degradation of some H12689 bathymetric data (Figure 12). High frequency lines from DN190 on Launch 2804 (RA-6) were affected resulting in brief periodic loss of accurate bottom detection (refer to the 2014 DAPR for more information regarding this issue).  All affected lines were examined in Caris subset mode and the affected lines were deleted as per Hydrographer-in-Charge recommendation. Although the affected lines were deleted, vertical offsets still remain in this area near Ostrovka Point which are most likely due to a less than accurate tidal zoning (see Section B.2.6 for  further details). The vertical offsets that remain where lines have been deleted meet HSSD requirements.</ns2:discussion><ns2:images><ns2:caption>Subset view of Reson 7125 SV2 roll-stabilization issue.</ns2:caption><ns2:link>SupportFiles\Reson SV2 Roll Artifact.jpg</ns2:link></ns2:images><ns2:comments/></ns2:issue></ns2:results><ns2:comments/></ns1:equipmentEffectiveness><ns1:factorsAffectingSoundings><ns2:results deviation="true"><ns2:issue><ns2:title>Vertical Offset</ns2:title><ns2:discussion>Vertical offsets ranging from approximately 0.20 to 0.60 meters were observed in various areas of the survey area.  In order to determine whether this offset was due to a less than accurate tidal zoning model, the affected multibeam data was referenced to the WGS84 ellipsoid by applying GPS tides in Caris. Once referenced to the ellipsoid, the vertical offset between overlapping lines was greatly reduced (Figures 13-15). Areas affected include those around Deranof and Nachalni Islands, Dry Spruce Bay, Ostrovka Point, Chernof Point, and Fox Bay (Figures 16-19). Some data in these areas exceed HSSD TVU standards. Strong currents were encountered in these areas creating tidal complexities, which could have caused these offsets. In the most extreme cases east of Chernof Point and to the north and northwest of Ostrovka Point, where the vertical uncertainty breaches accepted limits, the data does not meet the requirements set forth in the HSSD. Soundings from the outer beams of lines in these areas were filtered to limit the occurences of HSSD non-compliance. Moreover, these extreme cases of veritcal offsests have been deemed not to be navigationally significant.  In areas not adversely affected by these vertical offsets, which encompasses the majority of the survey area, the data meets or exceeds the requirements set forth in the HSSD.</ns2:discussion><ns2:images><ns2:caption>Section of H12689 1-meter surface showing artifacts
caused by vertical offset. Vessel track lines shown in green. Note: surface exaggeration value of 15.</ns2:caption><ns2:link>SupportFiles\Tidal Offset_Overview.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>Example of vertical offset in subset view with final zoned tides applied. Data colored by day.</ns2:caption><ns2:link>SupportFiles\Tidal Offset_Final Tides.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>Subset view of data with GPS tides applied, which reduces the vertical offset.</ns2:caption><ns2:link>SupportFiles\Tidal_Offset_GPS Tides.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>Example area of vertical offset near Nachalni and Deranof Islands.  </ns2:caption><ns2:link>SupportFiles\Vertical_Offset_Nachalni_Deranof.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>Example areas of vertical offsets near Chernof Point of Kupreanof Peninsula.</ns2:caption><ns2:link>SupportFiles\Vertical Offset_Chernof Point.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>Example areas of vertical offsets in the south end of Dry Spruce Bay.</ns2:caption><ns2:link>SupportFiles\Vertical Offset_Dry Spruce.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>Example area of vertical offset in Fox Bay.</ns2:caption><ns2:link>SupportFiles\Vertical_Offset_Fox_Bay.jpg</ns2:link></ns2:images><ns2:comments><ns2:branchComment concurrence="Concur with clarification"><ns2:comment>Data exceeding HSSD specifications is limited to small areas and does not exceed specifications by more than 0.2 meters.  The surveyed data is sufficient to supersede charted data.  </ns2:comment></ns2:branchComment></ns2:comments></ns2:issue><ns2:issue><ns2:title>Sound Speed Artifact</ns2:title><ns2:discussion>In the nearshore area surrounding Nachalni and Deranof Islands, the CTD cast frequency was unable to sufficiently characterize changes in sound speed within the water column. As a result, refraction error artifacts occur in the BASE surface where the outer beams &quot;smile&quot; or frown.&quot; (Figure 20). The survey data meets or exceeds the requirements set forth in the HSSD.
</ns2:discussion><ns2:images><ns2:caption>Sound speed artifact found south of Nachalni Island. Data colored by line number.</ns2:caption><ns2:link>SupportFiles\Sound Velocity Artifact.jpg</ns2:link></ns2:images><ns2:comments/></ns2:issue><ns2:issue><ns2:title>Kelp</ns2:title><ns2:discussion>Kelp was encountered in some shoal areas of the survey. Some of the thickest kelp patches were in the shoals at the east end of Afognak Strait (Figure 21). MBES data in these areas was examined 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>Subset view showing seafloor obscured by kelp and the affected reference surface. Subset taken at 57-59-54.97N, 152-46-02.75W.</ns2:caption><ns2:link>SupportFiles\Thick Kelp.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 the SBE19 and SBE 19Plus SEACAT CTD probes at discrete locations within the survey area at least once every four hours, when significant changes in surface sound speed were observed, or when surveying a new area. 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, with the following exceptions: 5 hours was used for &quot;Nearest in distance within time&quot; for Launch 2804 (RA-6) high frequency lines 2040 through 2116.</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="true"><ns2:discussion>Delayed Heave could not be applied to Launch 2804 DN181 low-frequency crosslines 2123 through 0000 (line 0000 acquired on DN182 according to UTC). The survey data still meets or exceeds the requirements set forth in the HSSD.</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>Backscatter data was acquired, but not formally processed by Rainier personnel. Two backscatter lines per boat, per day were reviewed to ensure quality. Backscatter was logged as .7k files and submitted to NGDC, but is not included with the data submitted to the Branch. </ns2:discussion></ns2:results><ns2:comments/></ns1:backscatter><ns1:dataProcessing><ns1:softwareUpdates><ns1:featureObjectCatalog>NOAA Extended Attribute Files V_5_3_2</ns1:featureObjectCatalog><ns1:discussion>All data was processed using Caris HIPS and SIPS 8.1.</ns1:discussion><ns1:comments/></ns1:softwareUpdates><ns1:surfaces><ns1:surface><ns2:surfaceName>H12689_MB_1m_MLLW</ns2:surfaceName><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:resolution units="meters">1</ns2:resolution><ns2:depthRange><ns2:min units="meters">-0.57</ns2:min><ns2:max units="meters">128</ns2:max></ns2:depthRange><ns2:surfaceParameter>NOAA_1m</ns2:surfaceParameter><ns2:purpose>Complete MBES</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceName>H12689_MB_2m_MLLW</ns2:surfaceName><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:resolution units="meters">2</ns2:resolution><ns2:depthRange><ns2:min units="meters">-0.50</ns2:min><ns2:max units="meters">128</ns2:max></ns2:depthRange><ns2:surfaceParameter>NOAA_2m</ns2:surfaceParameter><ns2:purpose>Complete MBES</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceName>H12689_MB_4m_MLLW</ns2:surfaceName><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:resolution units="meters">4</ns2:resolution><ns2:depthRange><ns2:min units="meters">0</ns2:min><ns2:max units="meters">128</ns2:max></ns2:depthRange><ns2:surfaceParameter>NOAA_4m</ns2:surfaceParameter><ns2:purpose>Complete MBES</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceName>H12689_MB_8m_MLLW</ns2:surfaceName><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:resolution units="meters">8</ns2:resolution><ns2:depthRange><ns2:min units="meters">0</ns2:min><ns2:max units="meters">128</ns2:max></ns2:depthRange><ns2:surfaceParameter>NOAA_8m</ns2:surfaceParameter><ns2:purpose>Complete MBES</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceName>H12689_MB_1m_MLLW_Final</ns2:surfaceName><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:resolution units="meters">1</ns2:resolution><ns2:depthRange><ns2:min units="meters">-0.70</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>H12689_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>H12689_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>H12689_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:discussion>In accordance with section 5.2.2.2 of the HSSD, the depth range of the 2-meter finalized surface was increased from 18-40 meters to 12-40 meters and the 1-meter finalized surface was increased from 0-20 meters to -1-20 meters in order to prevent apparent holidays resulting from the gridding algorithm in the bathymetry found in H12689.</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>Discrete Zoning</ns2:methodsUsed><ns2:tideStations><ns2:NWLONGauges><ns2:stationName>Kodiak Island</ns2:stationName><ns2:stationID>9457292</ns2:stationID></ns2:NWLONGauges><ns2:NWLONGauges><ns2:stationName>Seldovia</ns2:stationName><ns2:stationID>9455500</ns2:stationID></ns2:NWLONGauges><ns2:subordinateGauges><ns2:stationName>Uzkosti Point, AK</ns2:stationName><ns2:stationID>9457376</ns2:stationID></ns2:subordinateGauges><ns2:subordinateGauges><ns2:stationName>Nachalni Island, AK</ns2:stationName><ns2:stationID>9457407</ns2:stationID></ns2:subordinateGauges></ns2:tideStations><ns2:correctorFiles><ns2:waterLevels><ns2:fileName>9457292.tid</ns2:fileName><ns2:status>Final Approved</ns2:status></ns2:waterLevels><ns2:waterLevels><ns2:fileName>9457376.tid</ns2:fileName><ns2:status>Final Approved</ns2:status></ns2:waterLevels><ns2:waterLevels><ns2:fileName>9457407.tid</ns2:fileName><ns2:status>Final Approved</ns2:status></ns2:waterLevels><ns2:tideCorrectors><ns2:fileName>H12689CORF.zdf</ns2:fileName><ns2:status>Final</ns2:status></ns2:tideCorrectors></ns2:correctorFiles><ns2:finalTides><ns2:dateSubmitted>2014-07-10</ns2:dateSubmitted><ns2:dateReceived>2014-10-19</ns2:dateReceived></ns2:finalTides><ns2:discussion>The NWLON primary tide stations on Kodiak Island, AK (9457292) and in Seldovia, AK (9455500), as well as the subordinate tide stations installed by Rainier personnel at Uzkosti Point, AK (9457376) and Nachalni Island, AK (9457407) served as the controls for datum determination and water level reducers for survey H12689. A complete description of the vertical and horizontal control for this survey can be found in the accompanying OPR-P136-RA-14 Horizontal and Vertical Control Report (HVCR), submitted under a separate cover.</ns2:discussion><ns2:comments/></ns2:standard_or_ERZT><ns2:VDATUM_or_constantSep used="false"><ns2:discussion xsi:nil="true"></ns2:discussion><ns2:comments/></ns2:VDATUM_or_constantSep><ns2:comments/></ns1:verticalControl><ns1:horizontalControl><ns2:horizontalDatum>North American Datum of 1983 (NAD83)</ns2:horizontalDatum><ns2:projection>Universal Transverse Mercator (UTM)</ns2:projection><ns2:PPK used="true"><ns2:methodsUsed>Smart Base</ns2:methodsUsed><ns2:baseStations><ns2:CORSStations><ns2:HVCRSiteID>KOD5</ns2:HVCRSiteID><ns2:stationID>KODIAK 5</ns2:stationID></ns2:CORSStations><ns2:CORSStations><ns2:HVCRSiteID>KOD6</ns2:HVCRSiteID><ns2:stationID>KODIAK 6</ns2:stationID></ns2:CORSStations><ns2:CORSStations><ns2:HVCRSiteID>SELD</ns2:HVCRSiteID><ns2:stationID>SELD_AKDA_AK2000</ns2:stationID></ns2:CORSStations><ns2:CORSStations><ns2:HVCRSiteID>AC08</ns2:HVCRSiteID><ns2:stationID>CAPDOUGLASAK2007</ns2:stationID></ns2:CORSStations><ns2:CORSStations><ns2:HVCRSiteID>AC18</ns2:HVCRSiteID><ns2:stationID>Ushagat_IsAK2008</ns2:stationID></ns2:CORSStations><ns2:CORSStations><ns2:HVCRSiteID>AC24</ns2:HVCRSiteID><ns2:stationID>KINGSALMONAK2006</ns2:stationID></ns2:CORSStations><ns2:CORSStations><ns2:HVCRSiteID>AC26</ns2:HVCRSiteID><ns2:stationID>CAPE_GULL_AK2008</ns2:stationID></ns2:CORSStations><ns2:CORSStations><ns2:HVCRSiteID>AC27</ns2:HVCRSiteID><ns2:stationID>AC27MNeil_AK2004</ns2:stationID></ns2:CORSStations><ns2:CORSStations><ns2:HVCRSiteID>AC34</ns2:HVCRSiteID><ns2:stationID>OldHarbor_AK2006</ns2:stationID></ns2:CORSStations><ns2:CORSStations><ns2:HVCRSiteID>AC38</ns2:HVCRSiteID><ns2:stationID>QUARTZ_CRKAK2005</ns2:stationID></ns2:CORSStations><ns2:CORSStations><ns2:HVCRSiteID>AC39</ns2:HVCRSiteID><ns2:stationID>SHUYAKISSPAK2006</ns2:stationID></ns2:CORSStations><ns2:CORSStations><ns2:HVCRSiteID>AC67</ns2:HVCRSiteID><ns2:stationID>PILLARMTN_AK2006</ns2:stationID></ns2:CORSStations></ns2:baseStations><ns2:discussion>Vessel kinematic data (POS files) were post-processed with Applanix POSPac and POSGNSS software using Smart Base processing methods described in the DAPR. SBET and RMS data was applied to all survey lines with the exception of those described in Section C.3.3.1.</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 313 kHz</ns2:name></ns2:USCGStations><ns2:USCGStations><ns2:name>Kenai 310 kHz</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>SBETs could not be applied to line 2358 acquired by Launch 2803 on DN158, line 2359 acquired by Launch 2801 on DN158, and lines 2123 through 0000 and 1633 acquired by Launch 2804 on DN181 and DN141 respectively due to time extents not overlapping with the lines (Figure 22). On DN181 the POS file for Launch 2804 stopped logging some time before 2123 due to the hard drive being full. No error message was given to indicate any issue. As a result, all lines acquired from that launch after that time could not have SBETS applied. The survey data meets or exceeds the requirements set forth in the HSSD.</ns2:discussion><ns2:images><ns2:caption>Lines that could not be applied with SBETs.</ns2:caption><ns2:link>SupportFiles\Lines without SBETs.jpg</ns2:link></ns2:images><ns2:comments/></ns2:issue><ns2:comments/></ns1:additionalIssues></ns1:verticalAndHorizontalControl><ns1:resultsAndRecommendations><ns1:chartComparison><ns1:methods><ns2:discussion>Chart comparisons were performed using a Caris sounding and contour layer based on the 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>16594</ns2:number><ns2:kapp>2553</ns2:kapp><ns2:scale>78900</ns2:scale><ns2:edition>13</ns2:edition><ns2:editionDate>1998-04</ns2:editionDate><ns2:LNMDate>2014-12-15</ns2:LNMDate><ns2:NMDate>2014-11-28</ns2:NMDate></ns2:chart><ns2:discussion>H12689 derived soundings in Kupreanof Strait agreed with charted depths within 2 fathoms except as noted below. (Figures 23-24). The derived 50-fathom contour at the west end of the survey area is disjointed in comparison with the one charted. Along the southern shoreline of Kupreanof Strait, the derived 10-fathom contour tends to lie inshore from where it has been charted. Along this same shoreline, the derived 3-fathom contour generally agrees with the chart, however, the derived 5-fathom contour is not thoroughly charted in this area and the Hydrographer recommends updating the 5-fathom contour based upon the derived contours and soundings from the survey data. At the east end of Kupreanof Strait and to the west of Occident and Chiachi Points, the derived 10-fathom contour differs significantly from the charted contour (Figure 25).

The derived soundings through the main waterway of Dry Spruce Bay agreed with charted depths within 2 fathoms, however, along the shoreline of the bay the derived soundings are deeper and tend to disagree with the charted contours (Figure 26). In some cases there are derived soundings ranging from 10 to 19 fathoms lying in-between the charted 3 and 10-fathom contours. These discrepancies continue inshore of the charted 3-fathom contour with derived soundings ranging from 4 to 14 fathoms. The derived 5-fathom contour was overlain on Chart 16594 rather than the 3-fathom contour due to this deepening trend towards the shoreline. During the chart comparison analysis the derived 3-fathom contour, when overlain on the chart, follows tightly along the derived 5-fathom contour, so it has also been omitted for visual clarity purposes.

Derived soundings in Afognak Strait agreed with charted depths within 2 fathoms except as noted below (Figures 27-30). The charted 10-fathom contour has not been thoroughly distinguished in this area, yet shoaling occurs to where the chart should be updated with the derived 10 fathom contour. The derived 5-fathom contour generally tends to lie inshore of the charted 5-fathom contour. The derived 3-fathom contour tends to agree with the corresponding charted contour, however, a thorough comparison is hindered by the discontinuities of the derived contour. </ns2:discussion><ns2:images><ns2:caption>Overview of Kupreanof Strait with an overlay of derived soundings and contours. Note: The chart has been darkened slightly to enhance derived contour and sounding visuals.</ns2:caption><ns2:link>SupportFiles\Kupreanof Soundings_Contours.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>Areas in Kupreanof Strait where derived soundings are shoaler than charted depths</ns2:caption><ns2:link>SupportFiles\Kupreanof Soundings Diff.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>Differences in the derived 10-fathom contour west of Occident and Chiachi Points.</ns2:caption><ns2:link>SupportFiles\Occident Contour Diff.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>Overview of Dry Spruce Bay with an overlay of derived soundings and contours.</ns2:caption><ns2:link>SupportFiles\Dry Spruce Soundings_Contours.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>Overview of Afognak Strait with an overlay of derived contours. </ns2:caption><ns2:link>SupportFiles\Afognak Contours.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>Area at the west end of Afognak Strait where derived soundings are shoaler than charted depths.</ns2:caption><ns2:link>SupportFiles\West Afognak Sounding Diff.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>A central area of Afognak Strait where derived soundings are shoaler than charted depths.
</ns2:caption><ns2:link>SupportFiles\Central Afognak Sounding Diff.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>Area at the east end of Afognak Strait where derived soundings are shoaler than charted depths.
</ns2:caption><ns2:link>SupportFiles\East Afognak Sounding Diff.jpg</ns2:link></ns2:images><ns2:comments/></ns2:rasterChart><ns2:rasterChart><ns2:chart><ns2:number>16594</ns2:number><ns2:kapp>2554</ns2:kapp><ns2:scale>30000</ns2:scale><ns2:edition>13</ns2:edition><ns2:editionDate>1998-04</ns2:editionDate><ns2:LNMDate>2014-12-01</ns2:LNMDate><ns2:NMDate>2014-11-28</ns2:NMDate></ns2:chart><ns2:discussion>The Whale Passage inset from Chart 16594 was used for comparisons made in Whale Passage.

Derived soundings in Whale Passage  agreed within 2 fathoms except as noted below (Figures 31-32). The derived 10-fathom contour generally agrees with and follows the trend of the charted 10-fathom contour. However, an exception to this can be seen around Shag Rocks where the derived 10-fathom contour lies inshore of the charted contour.</ns2:discussion><ns2:images><ns2:caption>Overview of Whale Passage with an overlay of derived soundings and contours.</ns2:caption><ns2:link>SupportFiles\Whale Pass Soundings_Contours.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>Two spots in Whale Passage where derived soundings are shoaler than the chart depicts.</ns2:caption><ns2:link>SupportFiles\Whale Pass Soundings Diff.jpg</ns2:link></ns2:images><ns2:comments/></ns2:rasterChart><ns2:ENC><ns2:chart><ns2:name>US4AK5PM</ns2:name><ns2:scale>78900</ns2:scale><ns2:edition>4</ns2:edition><ns2:updateApplicationDate>2011-07-12</ns2:updateApplicationDate><ns2:issueDate>2014-08-12</ns2:issueDate><ns2:preliminary>false</ns2:preliminary></ns2:chart><ns2:discussion>Electronic Navigation Chart (ENC) US4AK5PM coincides with raster Chart 16594. The soundings on the ENC match the raster, however, the contours on raster Chart 16594 tend to be shifted to the northwest by about 40 to 50 meters (Figure 33). Although there is a visible shift in the contours between the raster and the ENC, the contours on the raster and the ENC both follow the same trend and therefore a comparison between H12689 and the ENC is equivalent to the preceding comparison with Chart 16594.
</ns2:discussion><ns2:images><ns2:caption>Transparent overlay of raster Chart 16594 on ENC US4AK5PM showing the misalignment of contours.</ns2:caption><ns2:link>SupportFiles\ENC - RNC offset.jpg</ns2:link></ns2:images><ns2:comments/></ns2:ENC><ns2:comments/></ns1:charts><ns1:AWOISItems><ns2:results investigated="None Exist"><ns2:discussion>No AWOIS items were assigned for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:AWOISItems><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>Complete MBES coverage was obtained over charted rock labeled as PA west of Chernof Point. No feature was discovered.</ns2:discussion></ns2:results><ns2:comments/></ns1:chartedFeatures><ns1:unchartedFeatures><ns2:results investigated="Investigated"><ns2:discussion>One uncharted, non-dangerous wreck was found near the mouth of Whale Passage (Figure 34). The position and other information for the wreck is attributed in the H12689 Final Feature File submitted with this report.</ns2:discussion><ns2:images><ns2:caption>Wreck discovered in Whale Passage.</ns2:caption><ns2:link>SupportFiles\Whale Pass Wreck.jpg</ns2:link></ns2:images></ns2:results><ns2:comments/></ns1:unchartedFeatures><ns1:DTONS><ns2:results reportSubmitted="true"><ns2:numberSubmitted>3</ns2:numberSubmitted><ns2:report><ns2:title>H12689 Danger to Navigation Report</ns2:title><ns2:dateSubmitted>2014-05-17</ns2:dateSubmitted></ns2:report><ns2:report><ns2:title>H12689 Danger to Navigation Report</ns2:title><ns2:dateSubmitted>2015-03-12</ns2:dateSubmitted></ns2:report><ns2:discussion>Three dangers to navigation were identified during this survey (Figure 35-36). The Danger to Navigation Reports are included in Appendix II of this report. The DTON west of Occident Point and in Whale Passage are reflected in the latest chart update as of 12/16/2014. The DTON located in Afognak Strait has been registered by the Nautical Data Branch and has been directed to Products Branch A for processing as of 3/16/2014.</ns2:discussion><ns2:images><ns2:caption>Chart 16594 before (left) and after (right) H12689 DTON were applied.</ns2:caption><ns2:link>SupportFiles\DTONs.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>DTON located in Afognak Strait.</ns2:caption><ns2:link>SupportFiles\DTON 3.jpg</ns2:link></ns2:images></ns2:results><ns2:comments><ns2:branchComment concurrence="Comment Only"><ns2:comment>All DTONs have been charted and were included in the chart update product. The DTON report is attached.</ns2:comment></ns2:branchComment></ns2:comments></ns1:DTONS><ns1:shoalAndHazardousFeatures><ns2:results investigated="Investigated"><ns2:discussion>All shoal and hazardous features were investigated in accordance with the Project Instruction 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>Eight proposed bottom sample locations were identified in the Project Reference File. All samples were collected at the proposed sites. Only one of the samples was not collected after three failed attempts. 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 HSSDM and FPM. There were 370 assigned features for this survey. All features were addressed as required with S-57 attribution and recorded in the H12689 Final Features File to best represent the features at chart scale.</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="Exist - Not Investigated"><ns2:discussion>Aids to navigation (ATON) were present in the survey area, but were not assigned for investigation.  All fifteen ATON observed in the field appeared correctly charted and serve their intended purpose.</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, CDR/NOAA</ns2:approverName><ns2:approverTitle>Commanding Officer, NOAA Ship Rainier</ns2:approverTitle><ns2:approvalDate>2015-04-03</ns2:approvalDate></ns1:signingPersonnel><ns1:signingPersonnel><ns2:approverName>Adam Pfundt, LTJG/NOAA</ns2:approverName><ns2:approverTitle>Field Operations Officer, NOAA Ship Rainier</ns2:approverTitle><ns2:approvalDate>2015-04-03</ns2:approvalDate></ns1:signingPersonnel><ns1:signingPersonnel><ns2:approverName>James B. Jacobson</ns2:approverName><ns2:approverTitle>Chief Survey Technician</ns2:approverTitle><ns2:approvalDate>2015-04-03</ns2:approvalDate></ns1:signingPersonnel><ns1:signingPersonnel><ns2:approverName>Eli R. Smith</ns2:approverName><ns2:approverTitle>Hydrographic Assistant Survey Technician, NOAA Ship Rainier</ns2:approverTitle><ns2:approvalDate>2015-04-03</ns2:approvalDate></ns1:signingPersonnel></ns1:approvalSheet></ns1:descriptiveReport>