<?xml version="1.0" encoding="UTF-8"?>
<ns1:descriptiveReport xmlns:ns1="http://Pydro.com/2013/01/DescriptiveReport" xmlns:ns2="http://Pydro.com/2013/01/AllGlobalTypes" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><ns1:metadata><ns1:projectMetadata><ns2:number>OPR-O193-RA-13</ns2:number><ns2:name>Behm Canal, AK</ns2:name><ns2:generalLocality>Behm Canal</ns2:generalLocality><ns2:fieldUnit>NOAA Ship RAINIER</ns2:fieldUnit></ns1:projectMetadata><ns1:registryMetadata><ns2:registryNumber>H12518</ns2:registryNumber><ns2:sheetID>1</ns2:sheetID><ns2:registryInstructions xsi:nil="true"></ns2:registryInstructions><ns2:sublocality>Vicinity of Burroughs 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>2013</ns2:year><ns2:chiefOfParty>Richard T. Brennan, CDR/NOAA</ns2:chiefOfParty><ns2:projectType>Navigable Area</ns2:projectType><ns2:PIDate>2013-04-01</ns2:PIDate><ns2:datesOfSurvey><ns2:start>2013-05-09</ns2:start><ns2:end>2013-06-18</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="09N">Universal Transverse Mercator (UTM)</ns2:horizontalCoordinateSystem><ns2:timeZone>UTC</ns2:timeZone><ns2:verifier>Pacific Hydrographic Branch</ns2:verifier><ns2:titlesheetRemarks><ns2:fieldRemarks xsi:nil="true"></ns2:fieldRemarks><ns2:branchRemarks xsi:nil="true"></ns2:branchRemarks></ns2:titlesheetRemarks></ns1:surveyMetadata><ns1:assignment>NOAA</ns1:assignment></ns1:metadata><ns1:areaSurveyed><ns1:areaDescription><ns2:discussion>The area surveyed is referred to as Sheet 1:  &quot;Vicinity of Burroughs Bay&quot; within the Project Instructions. The area is in the northern portion of the eastern branch of Behm Canal near Ketchikan, Alaska (Figure 1).</ns2:discussion><ns2:limits><ns2:northWest><ns2:latitude hemisphere="N">56.05</ns2:latitude><ns2:longitude hemisphere="W">131.258333333</ns2:longitude></ns2:northWest><ns2:southEast><ns2:latitude hemisphere="N">55.775</ns2:latitude><ns2:longitude hemisphere="W">130.966666667</ns2:longitude></ns2:southEast></ns2:limits><ns2:images><ns2:figureNumber>1</ns2:figureNumber><ns2:caption>H12518 survey limits.</ns2:caption><ns2:link>SupportFiles\Figure_A_1_1_X1_Survey_Limits.png</ns2:link></ns2:images><ns2:comments/></ns1:areaDescription><ns1:surveyPurpose><ns2:discussion>The purpose of this project is to provide contemporary surveys to update National Ocean Service (NOS) nautical charting products.</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 H12518 met complete multibeam echosounder (MBES) coverage requirements, including the 5 soundings per node data density requirements outlined in Section 5.2.2.2 of the HSSDM (Figure 2). In order to extract some descriptive statistics of the data density achievements, the density layer of each finalized surface was queried within CARIS and then examined in Excel (Figure 3). Overall, the required data density was achieved in 98.7% of the nodes and 99.8% of the total area.</ns2:discussion><ns2:images><ns2:figureNumber>2</ns2:figureNumber><ns2:caption>H12518 data density.</ns2:caption><ns2:link>SupportFiles\Figure_A_3_X1_Density_plot.png</ns2:link></ns2:images><ns2:images><ns2:figureNumber>3</ns2:figureNumber><ns2:caption>Summary table showing the percentage of nodes satisfying the 5 sounding density requirements, sub-divided by the appropriate depth ranges. Note: The final row has a unit of square meters, and sums the number of different resolution nodes into a common unit of area.</ns2:caption><ns2:link>SupportFiles\Figure_A_3_X1_Density_table.png</ns2:link></ns2:images><ns2:comments/></ns1:surveyQuality><ns1:surveyLimits><ns2:results deviation="true"><ns2:discussion>Survey limits were acquired in accordance with the requirements in the Project Instructions and the Hydrographic Survey Specifications and Deliverables Manual (HSSDM).</ns2:discussion></ns2:results><ns2:comments/></ns1:surveyLimits><ns1:coverageGraphic><ns2:figureNumber>4</ns2:figureNumber><ns2:caption>Acquired survey coverage overlaid on Chart 17424.</ns2:caption><ns2:link>SupportFiles\Figure_A_4_X1_Survey_Coverage.png</ns2:link></ns1:coverageGraphic><ns1:surveyCoverage><ns2:results deviation="true"><ns2:discussion>Complete multibeam (MBES) coverage was achieved within the limits of hydrography as defined in the Project Instructions (Figure 4).  There are a few gaps in coverage where multibeam data did not meet the sheet limit nor the 4-meter curve.  In all cases, these gaps were nearshore and dangerous to approach, and were therefore deemed to be inshore of the NALL.  Further, HSD has acknowledged minor gaps along the sheet limits, which the field determines to be non-navigationally significant, need not be acquired (see Supplemental Correspondence - HSD_holidays_on_edge.pdf).</ns2:discussion></ns2:results><ns2:comments/></ns1:surveyCoverage><ns1:surveyStatistics><ns2:surveyDates>2013-05-08</ns2:surveyDates><ns2:surveyDates>2013-05-13</ns2:surveyDates><ns2:surveyDates>2013-05-14</ns2:surveyDates><ns2:surveyDates>2013-05-15</ns2:surveyDates><ns2:surveyDates>2013-06-16</ns2:surveyDates><ns2:surveyDates>2013-06-17</ns2:surveyDates><ns2:totalSurveyStats><ns2:bottomSamples>7</ns2:bottomSamples><ns2:AWOIS>0</ns2:AWOIS><ns2:maritimeBoundaryPoints>0</ns2:maritimeBoundaryPoints><ns2:DP>53</ns2:DP><ns2:diveOps>0</ns2:diveOps><ns2:SNM>29.0</ns2:SNM></ns2:totalSurveyStats><ns2:LNM><ns2:vesselLNM><ns2:vessel><ns2:hullID>S221</ns2:hullID><ns2:statistics><ns2:MS_SBES>0</ns2:MS_SBES><ns2:MS_MBES>74.7</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>2801 (RA-4)</ns2:hullID><ns2:statistics><ns2:MS_SBES>0</ns2:MS_SBES><ns2:MS_MBES>138.4</ns2:MS_MBES><ns2:MS_lidar>0</ns2:MS_lidar><ns2:MS_SSS>0</ns2:MS_SSS><ns2:MS_SBES_MBES>0</ns2:MS_SBES_MBES><ns2:MS_MBES_SSS>0</ns2:MS_MBES_SSS><ns2:MS_SBES_SSS>0</ns2:MS_SBES_SSS><ns2:XL_MBES_SBES>0</ns2:XL_MBES_SBES><ns2:XL_lidar>0</ns2:XL_lidar></ns2:statistics></ns2:vessel><ns2:vessel><ns2:hullID>2802 (RA-5)</ns2:hullID><ns2:statistics><ns2:MS_SBES>0</ns2:MS_SBES><ns2:MS_MBES>30.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>0</ns2:XL_MBES_SBES><ns2:XL_lidar>0</ns2:XL_lidar></ns2:statistics></ns2:vessel><ns2:vessel><ns2:hullID>2803 (RA-3)</ns2:hullID><ns2:statistics><ns2:MS_SBES>0</ns2:MS_SBES><ns2:MS_MBES>10.0</ns2:MS_MBES><ns2:MS_lidar>0</ns2:MS_lidar><ns2:MS_SSS>0</ns2:MS_SSS><ns2:MS_SBES_MBES>0</ns2:MS_SBES_MBES><ns2:MS_MBES_SSS>0</ns2:MS_MBES_SSS><ns2:MS_SBES_SSS>0</ns2:MS_SBES_SSS><ns2:XL_MBES_SBES>0</ns2:XL_MBES_SBES><ns2:XL_lidar>0</ns2:XL_lidar></ns2:statistics></ns2:vessel><ns2:vessel><ns2:hullID>2804 (RA-6)</ns2:hullID><ns2:statistics><ns2:MS_SBES>0</ns2:MS_SBES><ns2:MS_MBES>13.4</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>18.1</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>267.1</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>18.1</ns2:XL_MBES_SBES><ns2:XL_lidar>0</ns2:XL_lidar><ns2:percentXLLNM>6.8</ns2:percentXLLNM></ns2:totalLNM></ns2:LNM><ns2:discussion xsi:nil="true"></ns2:discussion><ns2:comments/></ns1:surveyStatistics></ns1:areaSurveyed><ns1:dataAcquisitionAndProcessing><ns1:equipmentAndVessels><ns1:discussion>Refer to the Data Acquisition and Processing Report (DAPR) for a complete description of data acquisition and processing systems, survey vessels, quality control procedures and data processing methods.  Additional information to supplement sounding and survey data, and any deviations from the DAPR are discussed in the following sections.</ns1:discussion><ns1:vessels><ns1:vessel><ns2:hullID>2801</ns2:hullID><ns2:LOA units="feet">28</ns2:LOA><ns2:draft units="feet">3.5</ns2:draft></ns1:vessel><ns1:vessel><ns2:hullID>2802</ns2:hullID><ns2:LOA units="feet">28</ns2:LOA><ns2:draft units="feet">3.5</ns2:draft></ns1:vessel><ns1:vessel><ns2:hullID>2803</ns2:hullID><ns2:LOA units="feet">28</ns2:LOA><ns2:draft units="feet">3.5</ns2:draft></ns1:vessel><ns1:vessel><ns2:hullID>2804</ns2:hullID><ns2:LOA units="feet">28</ns2:LOA><ns2:draft units="feet">3.5</ns2:draft></ns1:vessel><ns1:vessel><ns2:hullID>S221</ns2:hullID><ns2:LOA units="feet">231</ns2:LOA><ns2:draft units="feet">16.5</ns2:draft></ns1:vessel><ns1:discussion>Data was primarily acquired by RAINIER (S221) for the deep central portion of the survey, with limited nearshore mainscheme data acquired with survey launches (2801, 2802, 2803 and 2804) (Table 4). The vessels acquired multibeam echosounder (MBES) soundings, sound speed profiles, and bottom samples.</ns1:discussion><ns1:comments/></ns1:vessels><ns1:equipment><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>7125</ns2:model><ns2:type>MBES</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>Applanix</ns2:manufacturer><ns2:model>POS-MV V4</ns2:model><ns2:type>Attitude System</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>Seabird</ns2:manufacturer><ns2:model>SBE 19 Plus</ns2:model><ns2:type>Sound Speed System</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>ODIM Brooke Ocean (Rolls Royce Group)</ns2:manufacturer><ns2:model>MVP30</ns2:model><ns2:type>Sound Speed System</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>ODIM Brooke Ocean (Rollys Royce Group)</ns2:manufacturer><ns2:model>MVP200</ns2:model><ns2:type>Sound Speed System</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>Reson</ns2:manufacturer><ns2:model>SVP 70</ns2:model><ns2:type>Sound Speed System</ns2:type></ns1:majorSystem><ns1:discussion xsi:nil="true"></ns1:discussion><ns1:comments/></ns1:equipment><ns1:comments/></ns1:equipmentAndVessels><ns1:qualityControl><ns1:crosslines><ns2:discussion>Multibeam crosslines were acquired using the Reson 7125 on Launch 2804. Crosslines totaled 18.1 NM, which comprised 6.8% of mainscheme hydrography.  An 8-meter CUBE surface was created using strictly the mainscheme lines, while a second 8-meter CUBE surface was created using only crosslines, from which a difference surface was generated at an 8-meter resolution (Figure 5).  Statistics were then derived from the difference surface and are shown in Figure 6.  The average difference between the depths derived from mainscheme and crosslines was 0.56 meters (mainscheme being deeper) with a standard deviation of 2.41 meters.  There is a bimodal distribution in the depth differences (Figure 6), which has a distinct geographic trend (Figure 5).  Generally speaking, the crosslines were deeper in deep central portions of the survey area, and shoaler in the shoal waters closer to shore.  This deep-biasing in the deeper waters may be a function of the crosslines being acquired with the Reson 7125, which is seldom operationally deployed in waters deeper than 200 meters; in the areas of overlap, crossline depths exceeded 500 meters.

For the respective depths, the difference surface was compared to the allowable IHO accuracy standards (Figure 7).   In total, 95.6% of the depth differences between H12518 mainscheme and crossline data are within allowable IHO accuracies (Figure 8).  The majority of the inconsistencies are on the steep inclines and may simply be an artifact of the gridding algorithm.

In addition to performing a crossline comparison using surface differencing, the CARIS QC Report was used to compare the crossline soundings to the depth estimates of the 8-meter resolution surface.  The depth differences are calculated between each crossline ping and mainscheme surface; and that depth difference is then compared to allowable IHO uncertainties.  The output QC Report classifies the percentage of pings meeting IHO orders by beam angle.  This table was copied and examined in Excel (Figure 9).   Only 90% of the pings up to 40-degrees from nadir satisfy IHO Order 2.  The relatively low percentage of pings meeting IHO standards is largely due to the depth of water (averaging 263 meters in the area of overlap), which exceeds the operational limits of the Reson 7125 (which will seldom return a full swath in depths greater than 200 meters).</ns2:discussion><ns2:images><ns2:figureNumber>5</ns2:figureNumber><ns2:caption>H12518 crosslines.</ns2:caption><ns2:link>SupportFiles\Figure_B_2_1_Crossline_overview_PN.png</ns2:link></ns2:images><ns2:images><ns2:figureNumber>6</ns2:figureNumber><ns2:caption>Crossline comparison with mainscheme lines.</ns2:caption><ns2:link>SupportFiles\Figure_B_2_1_X2_Crossline_table.png</ns2:link></ns2:images><ns2:images><ns2:figureNumber>7</ns2:figureNumber><ns2:caption>Depth differences between H12518 mainscheme and crossline data as compared to allowable IHO accuracy standards for the associated depths.</ns2:caption><ns2:link>SupportFiles\Figure_B_2_1_X3_Crossline_IHO.png</ns2:link></ns2:images><ns2:images><ns2:figureNumber>8</ns2:figureNumber><ns2:caption>Summary table showing percentage of difference surface nodes between H12518 mainscheme and crossline data that meet allowable IHO accuracy standards for the associated depths.</ns2:caption><ns2:link>SupportFiles\Figure_B_2_1_X4_Crossline_IHO_table.png</ns2:link></ns2:images><ns2:images><ns2:figureNumber>9</ns2:figureNumber><ns2:caption>CARIS QC Report comparing crossline soundings to depth estimates.</ns2:caption><ns2:link>SupportFiles\Figure_B_2_1_X5_Crossline_QCreport.png</ns2:link></ns2:images><ns2:comments/></ns1:crosslines><ns1:uncertainty><ns2:values><ns2:tideUncertainty><ns2:measured units="meters">0</ns2:measured><ns2:zoning units="meters">0.07</ns2:zoning></ns2:tideUncertainty><ns2:soundSpeedUncertainty><ns2:hullID>2801</ns2:hullID><ns2:measuredCTD units="meters/second">3</ns2:measuredCTD><ns2:measuredMVP xsi:nil="true"/><ns2:surface units="meters/second">.15</ns2:surface></ns2:soundSpeedUncertainty><ns2:soundSpeedUncertainty><ns2:hullID>2802</ns2:hullID><ns2:measuredCTD units="meters/second">3</ns2:measuredCTD><ns2:measuredMVP xsi:nil="true"/><ns2:surface units="meters/second">.15</ns2:surface></ns2:soundSpeedUncertainty><ns2:soundSpeedUncertainty><ns2:hullID>2803</ns2:hullID><ns2:measuredCTD units="meters/second">3</ns2:measuredCTD><ns2:measuredMVP xsi:nil="true"/><ns2:surface units="meters/second">.15</ns2:surface></ns2:soundSpeedUncertainty><ns2:soundSpeedUncertainty><ns2:hullID>2804</ns2:hullID><ns2:measuredCTD units="meters/second">3</ns2:measuredCTD><ns2:measuredMVP units="meters/second">1</ns2:measuredMVP><ns2:surface units="meters/second">.15</ns2:surface></ns2:soundSpeedUncertainty><ns2:soundSpeedUncertainty><ns2:hullID>S221</ns2:hullID><ns2:measuredCTD xsi:nil="true"/><ns2:measuredMVP units="meters/second">1</ns2:measuredMVP><ns2:surface units="meters/second">.05</ns2:surface></ns2:soundSpeedUncertainty></ns2:values><ns2:discussion>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 survey H12518.  Real-time uncertainties from both the EM710 and Reson 7125 were recorded and applied in post-processing.  Applanix TrueHeave files are recorded on all survey vessels, which includes an estimate of the heave uncertainty, and are applied during post-processing.  Finally, the post-processed uncertainties associated with vessel roll, pitch, gyro and navigation are applied in CARIS HIPS via an SBET RMS file generated in POSPac.

Uncertainty values of submitted finalized grids were calculated in CARIS using the &quot;Greater of the Two&quot; of uncertainty and standard deviation (scaled to 95%). To visualize the locations in which accuracy requirements were met for each finalized surface, a custom predicted IHO-compliance layer was created, based on the difference between calculated uncertainty of the nodes and the allowable IHO uncertainty (Figure 10). To quantify the extent to which accuracy requirements were met, the preceding predicted IHO-compliance layers were queried within CARIS and then examined in Excel (Figure 11). Overall 100.0% by node and 100.0% by area of survey H12518 met the accuracy requirements stated in the HSSDM.</ns2:discussion><ns2:images><ns2:figureNumber>10</ns2:figureNumber><ns2:caption>H12518 met IHO accuracy standards for 99.8% of the survey area.</ns2:caption><ns2:link>SupportFiles\Figure_B_2_2_X1_IHO_overview.png</ns2:link></ns2:images><ns2:images><ns2:figureNumber>11</ns2:figureNumber><ns2:caption>Summary table showing the percentage of nodes satisfying the indicated IHO accuracy level, sub-divided by the appropriate depth ranges. Note: The final row has a unit of square meters, and sums the number of different resolution nodes into a common unit of area.</ns2:caption><ns2:link>SupportFiles\Figure_B_2_2_X2_IHO_table.png</ns2:link></ns2:images><ns2:comments/></ns1:uncertainty><ns1:junctions><ns2:discussion>One junction comparison was completed for H12518 (Figure 12).  The junctioning survey, H12519, was acquired concurrently with this survey.  Depth comparisons were performed using the CARIS Difference Surface and CARIS Subset Editor.</ns2:discussion><ns2:junction><ns2:survey><ns2:registryNumber>H12519</ns2:registryNumber><ns2:scale>40000</ns2:scale><ns2:year>2013</ns2:year><ns2:fieldUnit>NOAA Ship RAINIER</ns2:fieldUnit><ns2:relativeLocation>N</ns2:relativeLocation></ns2:survey><ns2:discussion>Overlap with survey H12519 was 400 meters wide along the 4,000 meter southern boundary of H12518 (Figure 13). Depths in the junction area range from 20 to 350 meters.  A 16-meter CARIS Difference Surface analysis between CUBE depth surfaces for each survey showed H12518 to be an average of 0.04 meters shoaler than H12519, with a standard deviation of 2.06 meters (Figure 14).  

For the respective depths, the difference surface was compared to the allowable IHO accuracy standards (Figure 15).  In total, 91.2% of the depth differences between H12518 and junctioning survey H12519 are within allowable IHO accuracies (Figure 16).  Inspection of the data in CARIS Subset Editor (Figure 17), shows great agreement between the two surveys, suggesting the majority of the inconsistencies seen in the difference surfaces are just artifacts of the gridding algorithm.</ns2:discussion><ns2:images><ns2:figureNumber>12</ns2:figureNumber><ns2:caption>Overview of junctions with survey H12518.</ns2:caption><ns2:link>SupportFiles\Figure_B_2_3_X0_Junction_overview.png</ns2:link></ns2:images><ns2:images><ns2:figureNumber>13</ns2:figureNumber><ns2:caption>Difference surface between H12518 (purple) and junctioning survey H12519 (orange).</ns2:caption><ns2:link>SupportFiles\Figure_B_2_3_X1_Junction_diff_surface.png</ns2:link></ns2:images><ns2:images><ns2:figureNumber>14</ns2:figureNumber><ns2:caption>Difference surface statistics between H12518 and H12519 CUBE depth layers (16-meter grid size). H12518 is an average of 0.04 meters shoaler.</ns2:caption><ns2:link>SupportFiles\H12519_H12518_JNX_graph.png</ns2:link></ns2:images><ns2:images><ns2:figureNumber>15</ns2:figureNumber><ns2:caption>Depth differences between H12518 and junctioning survey H12519 as compared to allowable IHO accuracy standards for the associated depths.</ns2:caption><ns2:link>SupportFiles\Figure_B_2_3_X3_H12518_Junction_IHO_compliance.png</ns2:link></ns2:images><ns2:images><ns2:figureNumber>16</ns2:figureNumber><ns2:caption>Summary table showing percentage of difference surface nodes between H12518 and junctioning survey H12519 that meet allowable IHO accuracy standards for the associated depths.</ns2:caption><ns2:link>SupportFiles\Figure_B_2_3_X3b_H12518_Junction_IHO_table.png</ns2:link></ns2:images><ns2:images><ns2:figureNumber>17</ns2:figureNumber><ns2:caption>Subset view of sonar data between H12518 (yellow) and junctioning survey H12519 (red).</ns2:caption><ns2:link>SupportFiles\Figure_B_2_3_Junction_subset2.png</ns2:link></ns2:images><ns2:comments/></ns2:junction><ns2:comments/></ns1:junctions><ns1:sonarQCChecks><ns2:results deviation="false"><ns2:discussion>Sonar system quality control checks were conducted as detailed in the quality control section of the DAPR.</ns2:discussion></ns2:results><ns2:comments/></ns1:sonarQCChecks><ns1:equipmentEffectiveness><ns2:results deviation="true"><ns2:issue><ns2:title>Loss of GAMS solution.</ns2:title><ns2:discussion>On DN167 (16 June), Launch 2802 experienced numerous drops in position throughout the day; this was likely due to a combination of high PDOP and satellite masking by the surrounding mountains.  The post-processing of position via POSPac was able to remedy some, but not all, of the errors in the trajectory file (Figure 18).  Every line from this day was closely scrutinized for potential errors in navigation or attitude records.  All cases in which the affected lines diverged from neighboring data, the affected soundings were flagged as rejected.  The lines requiring editing were DN167-1821, 1831, 1835, 1857 and 1928.</ns2:discussion><ns2:images><ns2:figureNumber>18</ns2:figureNumber><ns2:caption>Example of the effects of GPS drop outs and loss of GAMS solution on a single survey line:  upper inset shows artifact during loss of GAMS solution, while lower inset shows agreement between datasets while GAMS is in use.</ns2:caption><ns2:link>SupportFiles\Figure_B_2_5_X1_GPS_dropping.png</ns2:link></ns2:images><ns2:comments/></ns2:issue></ns2:results><ns2:comments/></ns1:equipmentEffectiveness><ns1:factorsAffectingSoundings><ns2:results deviation="true"><ns2:issue><ns2:title>Ellipsoid-to-Tidal surface comparison</ns2:title><ns2:discussion>Using the GPS height determined from the SBET file, data from H12518 was referenced to the ellipse and gridded.  By differencing this ellipsoidally-referenced surface (ERS) from the traditional tidally-referenced surface, one should only see the ellipsoidal slope across the length of the survey.  Any deviations from this slope would therefore be the result of an error intrinsic to either the ERS or tidal processing work flow.  For example, misprojected SBETs, current-induced dynamic draft, incorrect waterline measurements, corrupt True Heave files, or poorly-modeled water levels are all examples of artifacts that can be identified through the difference of the ERS and tidally-referenced surfaces.  

Figure 19 shows the gentle slope of the ellipse from north to south in the vicinity of survey H12518.  Given there were no major &quot;bright spots&quot; in the difference surface, none of the artifacts mentioned in the previous paragraph are likely present, in any substantial amount, in survey H12518.  Extending the ellipsoidal-to-tidal surface across the entire Behm Canal project (Figure 20), one can see the ellipsoid slope seen in survey H12518 continues through junctioning survey H12519.</ns2:discussion><ns2:images><ns2:figureNumber>19</ns2:figureNumber><ns2:caption>Difference surface between the ellipsoidally-referenced and tidally-referenced surfaces.</ns2:caption><ns2:link>SupportFiles\Figure_B_2_6_X1_ERS_diff_MLLW.png</ns2:link></ns2:images><ns2:images><ns2:figureNumber>20</ns2:figureNumber><ns2:caption>Difference surface between the ellipsoidally-referenced and tidally-referenced surfaces across the entire Behm Canal project.</ns2:caption><ns2:link>SupportFiles\Figure_B_2_6_X2_ERS_diff_MLLW.png</ns2:link></ns2:images><ns2:comments/></ns2:issue><ns2:issue><ns2:title>Surface Sound Speed</ns2:title><ns2:discussion>Surface sound speed values were observed to vary temporally and spatially throughout the survey area, with the largest variations being near the Unuk and Klahini Rivers at the head of Burroughs Bay (Figure 21).  A fresh water lens spread across the length of Burroughs Bay leading to sound speed changes of up to 30 meters/second.  To mitigate the potential refraction errors, extra sound speed profiles were acquired in the upper arm of Burroughs Bay (for further details, see Section B.2.7 - Sound Speed Methods).</ns2:discussion><ns2:images><ns2:figureNumber>21</ns2:figureNumber><ns2:caption>Plot of surface sound speed as recorded on a single day while acquiring crossline data.  Fresh water inflow from rivers at the head of Burroughs Bay, lead to a fresh water lens and corresponding drop in surface sound speed.</ns2:caption><ns2:link>SupportFiles\Figure_B_2_6_X3_Surface_SV.png</ns2:link></ns2:images><ns2:comments/></ns2:issue></ns2:results><ns2:comments/></ns1:factorsAffectingSoundings><ns1:soundSpeedMethods><ns1:castFrequency>For data collected by launches, sound speed profiles were acquired using the SBE 19plus CTDs at discrete locations within the survey area at least once every four hours, when large changes in surface sound speed were apparent, and when moving to a new area. For data collected on S221 (RAINIER), sound speed profiles were acquired using the Rolls Royce MVP200 approximately every 15 minutes or when recommended by &quot;CastTime&quot;, a cast frequency program developed at the University of New Hampshire. All casts were concatenated into a master file for the entire survey and (with the exception of one line) applied to lines using the &quot;Nearest in distance within time (4 hours)&quot; profile selection method (Figure 22).  

On DN135 (15 May) a line of opportunity was acquired by S221 without deploying the MVP (Line 0024).  The most appropriate cast was acquired by a survey launch which was working in the same area at a different time.  In order for this cast to be applied, the survey line was processed using the &quot;Nearest in distance within time (6 hours)&quot; profile selection method.  The affected line was examined in Subset Editor, which showed good agreement between neighboring lines.</ns1:castFrequency><ns1:discussion xsi:nil="true"></ns1:discussion><ns1:images><ns2:figureNumber>22</ns2:figureNumber><ns2:caption>Distribution of sound speed profiles acquired for survey H12518.</ns2:caption><ns2:link>SupportFiles\Figure_B_2_7_X1_Cast_Locations.png</ns2:link></ns1:images><ns1:comments/></ns1:soundSpeedMethods><ns1:coverageEquipmentAndMethods><ns2:results deviation="false"><ns2:discussion>All equipment and survey methods were used as detailed in the DAPR.</ns2:discussion></ns2:results><ns2:comments/></ns1:coverageEquipmentAndMethods><ns1:additionalQualityControl><ns2:comments/></ns1:additionalQualityControl></ns1:qualityControl><ns1:echoSoundingCorrections><ns1:corrections><ns2:results deviation="false"><ns2:discussion>All data reduction procedures conform to those detailed in the DAPR.</ns2:discussion></ns2:results><ns2:comments/></ns1:corrections><ns1:calibrations><ns2:results deviation="false"><ns2:discussion>All sounding systems were calibrated as detailed in the DAPR.</ns2:discussion><ns2:calibration xsi:nil="true"/></ns2:results><ns2:comments/></ns1:calibrations><ns1:additionalIssues><ns2:comments/></ns1:additionalIssues></ns1:echoSoundingCorrections><ns1:backscatter><ns2:results acquired="true"><ns2:discussion>Backscatter data was acquired, but not formally processed by RAINIER personnel.  However, periodic spot checks were performed to ensure backscatter quality.  A preliminary backscatter mosaic of data acquired by S221 is shown in Figure 23.  Backscatter was logged as 7k or .ALL files and submitted to NGDC, but is not included with the data submitted to the Branch.</ns2:discussion><ns2:images><ns2:figureNumber>23</ns2:figureNumber><ns2:caption>H12518 backscatter mosaic of S221 lines.</ns2:caption><ns2:link>SupportFiles\Figure_B_4_X1_Backscatter.png</ns2:link></ns2:images></ns2:results><ns2:comments/></ns1:backscatter><ns1:dataProcessing><ns1:softwareUpdates><ns1:featureObjectCatalog>NOAA Extended Attribute Files Version 5_3_2</ns1:featureObjectCatalog><ns1:discussion>All final data processing was performed using CARIS HIPS and SIPS 7.1.2.6.  It should be noted that all Kongsberg EM710 data was intentionally processed without the Simrad Sound Velocity Correction (SVC) module.  This was done in order to avoid a known error in the SVC module associated with reverse-mounted transducers.  To accomplish this, a custom CARIS license file was used, which excluded the licensing for the Simrad SVC.  For further details, refer to the DAPR.</ns1:discussion><ns1:comments/></ns1:softwareUpdates><ns1:surfaces><ns1:surface><ns2:surfaceName>H12518_1m</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">600</ns2:max></ns2:depthRange><ns2:surfaceParameter>NOAA_1m</ns2:surfaceParameter><ns2:purpose>Complete MBES</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceName>H12518_2m</ns2:surfaceName><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:resolution units="meters">2</ns2:resolution><ns2:depthRange><ns2:min units="meters">-2</ns2:min><ns2:max units="meters">600</ns2:max></ns2:depthRange><ns2:surfaceParameter>NOAA_2m</ns2:surfaceParameter><ns2:purpose>Complete MBES</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceName>H12518_4m</ns2:surfaceName><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:resolution units="meters">4</ns2:resolution><ns2:depthRange><ns2:min units="meters">-2</ns2:min><ns2:max units="meters">600</ns2:max></ns2:depthRange><ns2:surfaceParameter>NOAA_4m</ns2:surfaceParameter><ns2:purpose>Complete MBES</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceName>H12518_8m</ns2:surfaceName><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:resolution units="meters">8</ns2:resolution><ns2:depthRange><ns2:min units="meters">-2</ns2:min><ns2:max units="meters">600</ns2:max></ns2:depthRange><ns2:surfaceParameter>NOAA_8m</ns2:surfaceParameter><ns2:purpose>Complete MBES</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceName>H12518_16m</ns2:surfaceName><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:resolution units="meters">16</ns2:resolution><ns2:depthRange><ns2:min units="meters">-2</ns2:min><ns2:max units="meters">600</ns2:max></ns2:depthRange><ns2:surfaceParameter>NOAA_16m</ns2:surfaceParameter><ns2:purpose>Complete MBES</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceName>H12518_32m</ns2:surfaceName><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:resolution units="meters">32</ns2:resolution><ns2:depthRange><ns2:min units="meters">-2</ns2:min><ns2:max units="meters">600</ns2:max></ns2:depthRange><ns2:surfaceParameter>NOAA_32m</ns2:surfaceParameter><ns2:purpose>Complete MBES</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceName>H12518_1m_-10to40_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">40</ns2:max></ns2:depthRange><ns2:surfaceParameter>NOAA_1m</ns2:surfaceParameter><ns2:purpose>Complete MBES</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceName>H12518_2m_18to80_Final</ns2:surfaceName><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:resolution units="meters">2</ns2:resolution><ns2:depthRange><ns2:min units="meters">18</ns2:min><ns2:max units="meters">80</ns2:max></ns2:depthRange><ns2:surfaceParameter>NOAA_2m</ns2:surfaceParameter><ns2:purpose>Complete MBES</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceName>H12518_4m_36to160_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">160</ns2:max></ns2:depthRange><ns2:surfaceParameter>NOAA_4m</ns2:surfaceParameter><ns2:purpose>Complete MBES</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceName>H12518_8m_72to320_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">320</ns2:max></ns2:depthRange><ns2:surfaceParameter>NOAA_8m</ns2:surfaceParameter><ns2:purpose>Complete MBES</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceName>H12518_16m_144to500_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">500</ns2:max></ns2:depthRange><ns2:surfaceParameter>NOAA_16m</ns2:surfaceParameter><ns2:purpose>Complete MBES</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceName>H12518_32m_288to600_Final</ns2:surfaceName><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:resolution units="meters">32</ns2:resolution><ns2:depthRange><ns2:min units="meters">288</ns2:min><ns2:max units="meters">600</ns2:max></ns2:depthRange><ns2:surfaceParameter>NOAA_32m</ns2:surfaceParameter><ns2:purpose>Complete MBES</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceName>H12518_Combined_32m</ns2:surfaceName><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:resolution units="meters">32</ns2:resolution><ns2:depthRange><ns2:min units="meters">-2</ns2:min><ns2:max units="meters">600</ns2:max></ns2:depthRange><ns2:surfaceParameter>NOAA_32m</ns2:surfaceParameter><ns2:purpose>Complete MBES</ns2:purpose></ns1:surface><ns1:discussion>In order to prevent apparent coverage gaps resulting from the gridding algorithm in the &quot;steep and deep&quot; bathymetry found in H12518 (Figure 24), finalized surfaces were extended beyond the depth thresholds specified in the HSSDM.  For example, rather than gridding the data at a 2-meter resolution between 18 and 40 meter depths; the depth range was extended to between 18 and 80 meter depths.  All other finalization depth ranges are stated in Table 10.</ns1:discussion><ns1:images><ns2:figureNumber>24</ns2:figureNumber><ns2:caption>(Top) Finalized surfaces created using depth thresholds specified in the HSSDM; notice the gaps between depth resolutions.  (Bottom) The same region gridded at the finest resolution shows the data is free of coverage gaps.</ns2:caption><ns2:link>SupportFiles\Figure_B_5_2_X1_Surface_Resolutions.png</ns2:link></ns1:images><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>Ketchikan, AK</ns2:stationName><ns2:stationID>9450460</ns2:stationID></ns2:NWLONGauges><ns2:subordinateGauges><ns2:stationName>Burroughs Bay, AK</ns2:stationName><ns2:stationID>9450917</ns2:stationID></ns2:subordinateGauges></ns2:tideStations><ns2:correctorFiles><ns2:waterLevels><ns2:fileName>9450917.tid</ns2:fileName><ns2:status>Verified Observed</ns2:status></ns2:waterLevels><ns2:tideCorrectors><ns2:fileName>H12518CORP.zdf</ns2:fileName><ns2:status>Final</ns2:status></ns2:tideCorrectors></ns2:correctorFiles><ns2:finalTides><ns2:dateSubmitted>2013-06-21</ns2:dateSubmitted><ns2:dateReceived>2013-08-02</ns2:dateReceived></ns2:finalTides><ns2:discussion>The operating NWLON primary tide station in Ketchikan, AK (9450460), as well as a subordinate tide station installed by RAINIER personnel at Burroughs Bay, AK (9450917) served as the controls for datum determination and water level reducers for survey H12518.  A complete description of the vertical and horizontal control for this survey can be found in the accompanying OPR-O193-RA-13 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>UTM - 09 North</ns2:projection><ns2:PPK used="true"><ns2:methodsUsed>Single Base</ns2:methodsUsed><ns2:baseStations><ns2:userInstalledStations><ns2:HVCRSiteID>Channel Island, AK</ns2:HVCRSiteID><ns2:stationID>N/A</ns2:stationID></ns2:userInstalledStations></ns2:baseStations><ns2:discussion>In conjunction with this project, a GNSS base station was established by RAINIER personnel on Channel Island near the center of the survey area.  Vessel kinematic data was post-processed using Applanix POSPac processing software as described in the DAPR.  Single Base processing was used from DN133 to DN134 while the site was installed.</ns2:discussion><ns2:comments/></ns2:PPK><ns2:PPP used="true"><ns2:discussion>The PPK base station on Channel Island was removed on DN135 to relocate to the next project area.  Therefore, a PPK solution was not possible for DN135, DN167, and DN168. To provide enhanced positioning data, a PPP solution was used for those days.  Data processed by PPP correlated well with surrounding data processed with PPK.

Additionally, for testing purposes, DN129 was processed using PPP.  The lines showed high correlation with surrounding data and was never reprocessed using PPK.</ns2:discussion><ns2:comments/></ns2:PPP><ns2:RTK used="false" xsi:nil="true"/><ns2:DGPS used="true"><ns2:USCGStations><ns2:name>Biorka Island, AK (305 kHz)</ns2:name></ns2:USCGStations><ns2:USCGStations><ns2:name>Level Island, AK (295 kHz)</ns2:name></ns2:USCGStations><ns2:USCGStations><ns2:name>Annette Island, AK (323 kHz)</ns2:name></ns2:USCGStations><ns2:discussion>DGPS was used for primary positioning during acquisition.  Following PPK or PPP processing, DGPS position data was replaced with improved SBET navigation data.</ns2:discussion><ns2:comments/></ns2:DGPS><ns2:comments/></ns1:horizontalControl><ns1:additionalIssues><ns2:comments/></ns1:additionalIssues></ns1:verticalAndHorizontalControl><ns1:resultsAndRecommendations><ns1:chartComparison><ns1:methods><ns2:discussion>Two principle methods were used in comparing survey H12518 to the contemporary charts.  From the survey data, contours and soundings were generated and compared to the raster chart.  For the Electronic Navigation Chart (ENC), a TIN was generated from all soundings and contours within the ENC (Figure 25).  From this TIN, an interpolated surface was generated, which was then differenced from the survey data for the purposes of visualization and computing statistics.

For specific details on the chart comparisons for survey H12518, refer to Section D.1.1 - Raster Charts, and Section D.1.2 - Electronic Navigation Charts.</ns2:discussion><ns2:images><ns2:figureNumber>25</ns2:figureNumber><ns2:caption>TIN and interpolated surface generated from ENC US4AK43M and US4AK44M for the purposes of a chart comparison to survey H12518.</ns2:caption><ns2:link>SupportFiles\Figure_D_1_X1_ENC_TIN.png</ns2:link></ns2:images><ns2:comments/></ns1:methods><ns1:charts><ns2:rasterChart><ns2:chart><ns2:number>17424</ns2:number><ns2:kapp>2737</ns2:kapp><ns2:scale>80000</ns2:scale><ns2:edition>9</ns2:edition><ns2:editionDate>2009-10</ns2:editionDate><ns2:LNMDate>2013-08-14</ns2:LNMDate><ns2:NMDate>2013-08-14</ns2:NMDate></ns2:chart><ns2:discussion>A comparison was performed between survey H12518 and Chart 17424 (1:80000) using CARIS sounding and contour layers derived from the 32-meter combined surface.  The contours and soundings have been overlaid on the chart, and a representative area is shown in Figure 26.  Throughout the survey, the 100-fathom contour is closely followed by the survey data; however the charted 3-fathom contour has likely been pulled offshore for cartographic reasons and is seldom correctly modeled.  Given the extreme steep and deep nature of the bathymetry, the 3-fathom contour is inappropriate for this area and the Hydrographer recommends removing it from the chart.  For a further discussion of the surveyed depths to charted sounding comparison, refer to Section D.1.2 - Electronic Navigation Charts.

It is recommended that H12518 data supersede all charted depths on Chart 17424. </ns2:discussion><ns2:images><ns2:figureNumber>26</ns2:figureNumber><ns2:caption>Close-up of Burroughs Bay, showing comparison of contours derived from survey H12518 and those depicted on Chart 17424.</ns2:caption><ns2:link>SupportFiles\Figure_D_1_1_X1_Contours.png</ns2:link></ns2:images><ns2:comments/></ns2:rasterChart><ns2:rasterChart><ns2:chart><ns2:number>17422</ns2:number><ns2:kapp>2731</ns2:kapp><ns2:scale>80000</ns2:scale><ns2:edition>9</ns2:edition><ns2:editionDate>2006-02</ns2:editionDate><ns2:LNMDate>2013-08-14</ns2:LNMDate><ns2:NMDate>2013-08-14</ns2:NMDate></ns2:chart><ns2:discussion>In the vicinity of survey H12518, Chart 17422 is equivalent to Chart 17424.  Please refer back to the previous section for a comparison of survey H12518 and Chart 17424.</ns2:discussion><ns2:comments/></ns2:rasterChart><ns2:ENC><ns2:chart><ns2:name>US4AK44M</ns2:name><ns2:scale>80000</ns2:scale><ns2:edition>2</ns2:edition><ns2:updateApplicationDate>2011-12-12</ns2:updateApplicationDate><ns2:issueDate>2011-12-12</ns2:issueDate><ns2:preliminary>false</ns2:preliminary></ns2:chart><ns2:discussion>ENC US4AK44M coincides with raster Chart 17424 (with a small contribution from US4AK43M).  To compare soundings, a TIN surface was created from the ENC depth features (soundings and contours).  A 16-meter surface from H12518 was then differenced from the ENC TIN (Figure 27).  Positive (red) values show where survey H12518 is shoaler than the TIN and negative (blue) values show where survey H12518 is deeper than the TIN.  Overall, the surveyed depths and charted soundings agree well in the center of the channel; otherwise, there is a tendency for the chart to express a shoal biasing in the soundings (sometimes by over 10 fathoms).  Figure 28 shows a close-up of the depth comparisons in the vicinity of Fitzgibbon Cove and Saks Cove.  One can see how all the soundings near shore (shoaler than 100 fathoms) are typically much shoaler than H12518 depths (likely because the soundings were pulled offshore for cartographic reasons).  Figure 28 also shows that, generally, the survey and chart agree in the two coves.</ns2:discussion><ns2:images><ns2:figureNumber>27</ns2:figureNumber><ns2:caption>Difference surface between depth estimates from survey H12518 and an interpolated surface created from the soundings and contours of ENC US4AK44M (with a small contribution from US4AK43M).</ns2:caption><ns2:link>SupportFiles\Figure_D_1_2_X1_ENC_diff.png</ns2:link></ns2:images><ns2:images><ns2:figureNumber>28</ns2:figureNumber><ns2:caption>Close-up view of Fitzgibbon and Saks Coves and difference surface between depth estimates from survey H12518 and the TIN surface.  Charted nearshore soundings (except within the coves) appear to have been pulled offshore for cartographic reasons.</ns2:caption><ns2:link>SupportFiles\Figure_D_1_2_X2_ENC_diff_inset.png</ns2:link></ns2:images><ns2:comments/></ns2:ENC><ns2:ENC><ns2:chart><ns2:name>US4AK43M</ns2:name><ns2:scale>80000</ns2:scale><ns2:edition>2</ns2:edition><ns2:updateApplicationDate>2012-09-20</ns2:updateApplicationDate><ns2:issueDate>2012-09-20</ns2:issueDate><ns2:preliminary>false</ns2:preliminary></ns2:chart><ns2:discussion>ENC US4AK43M only intersects with a small portion of survey H12518 (Figure 23).  For the purposes of the chart comparison, both US4AK43M and US4AK44M were compiled into the TIN discussed previously that was used to create the difference surface.  Please refer back to the previous section for a comparison of survey H12518 and ENC US4AK44M.</ns2:discussion><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>Within the extents of survey H12518, Chart 17424 reports &quot;tide rips&quot; in two locations (Figure 29).  Though the RAINIER worked in the area through two spring tides, with daily tidal ranges exceeding five meters, no tidal rips were observed in the project area.</ns2:discussion><ns2:images><ns2:figureNumber>29</ns2:figureNumber><ns2:caption>Tide rips reported on Chart 17424.</ns2:caption><ns2:link>SupportFiles\Figure_D_1_5_X1_Charted_Feature.png</ns2:link></ns2:images></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="false"><ns2:numberSubmitted xsi:nil="true"></ns2:numberSubmitted><ns2:discussion>No Danger to Navigation Reports were submitted for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:DTONS><ns1:shoalAndHazardousFeatures><ns2:results investigated="None Exist"><ns2:discussion>No shoals or potentially hazardous features exist for this survey.</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>Eighteen bottom sample locations were identified in the Project Reference File. Eleven assigned bottom samples, where depths exceeded 100 meters, were not acquired due to equipment limitations.  Seven bottom sample locations were selected based on feasibility and distribution throughout the survey area (Figure 30).  Acquired bottom samples are addressed, as required, with S-57 attribution and recorded in the Final Features File accompanying this submission.</ns2:discussion><ns2:images><ns2:figureNumber>30</ns2:figureNumber><ns2:caption>Bottom samples in H12518.</ns2:caption><ns2:link>SupportFiles\Figure_D_1_10_Bottom_Samples.png</ns2:link></ns2:images></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 56 assigned features for this survey.  All features were addressed as required with S-57 attribution and recorded in the H12518 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="None Exist"><ns2:discussion>No Aids to navigation (ATONs) exist for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:ATONS><ns1:overheadFeatures><ns2:results investigated="None Exist"><ns2:discussion>No overhead features exist for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:overheadFeatures><ns1:submarineFeatures><ns2:results investigated="None Exist"><ns2:discussion>No submarine features exist for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:submarineFeatures><ns1:ferryRoutesAndTerminals><ns2:results investigated="None Exist"><ns2:discussion>No ferry routes or terminals exist for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:ferryRoutesAndTerminals><ns1:platforms><ns2:results investigated="None Exist"><ns2:discussion>No platforms exist for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:platforms><ns1:significantFeatures><ns2:results investigated="Investigated"><ns2:discussion>Originating at the head of Burroughs Bay, and wrapping around Pt Fitzgibbon is, what appears to be, an ancient submerged riverbed (Figure 31).  This meandering riverbed is pronounced in depths of up to 400 meters, and, in places, has scoured a trench in the seafloor of up to 50 meters.</ns2:discussion><ns2:images><ns2:figureNumber>31</ns2:figureNumber><ns2:caption>Ancient submerged riverbed located at the head of Burroughs Bay.</ns2:caption><ns2:link>SupportFiles\Figure_D_2_8_Significant_Feature.png</ns2:link></ns2:images></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, Standing and 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>Richard T. Brennan, CDR/NOAA</ns2:approverName><ns2:approverTitle>Commanding Officer, NOAA Ship RAINIER</ns2:approverTitle><ns2:approvalDate>2013-08-15</ns2:approvalDate></ns1:signingPersonnel><ns1:signingPersonnel><ns2:approverName>Michael O. Gonsalves, LT/NOAA</ns2:approverName><ns2:approverTitle>Field Operations Officer, NOAA Ship RAINIER</ns2:approverTitle><ns2:approvalDate>2013-08-15</ns2:approvalDate></ns1:signingPersonnel><ns1:signingPersonnel><ns2:approverName>James B. Jacobson</ns2:approverName><ns2:approverTitle>Chief Survey Technician, NOAA Ship RAINIER</ns2:approverTitle><ns2:approvalDate>2013-08-15</ns2:approvalDate></ns1:signingPersonnel><ns1:signingPersonnel><ns2:approverName>Damian Manda, LTJG/NOAA</ns2:approverName><ns2:approverTitle>Junior Officer, NOAA Ship RAINIER</ns2:approverTitle><ns2:approvalDate>2013-08-15</ns2:approvalDate></ns1:signingPersonnel></ns1:approvalSheet></ns1:descriptiveReport>