<?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-P183-RA-13</ns2:number><ns2:name>Shumagin Islands, AK</ns2:name><ns2:generalLocality>Shumagin Islands, AK</ns2:generalLocality><ns2:fieldUnit>NOAA Ship RAINIER</ns2:fieldUnit></ns1:projectMetadata><ns1:registryMetadata><ns2:registryNumber>H12595</ns2:registryNumber><ns2:sheetID>8</ns2:sheetID><ns2:registryInstructions xsi:nil="true"></ns2:registryInstructions><ns2:sublocality>5 NM South of Simeonof Island</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-05-31</ns2:PIDate><ns2:datesOfSurvey><ns2:start>2013-07-17</ns2:start><ns2:end>2013-09-03</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="4">Universal Transverse Mercator (UTM)</ns2:horizontalCoordinateSystem><ns2:timeZone>UTC</ns2:timeZone><ns2:verifier>Pacific Hydrographic Branch</ns2:verifier><ns2:titlesheetRemarks><ns2:fieldRemarks xsi:nil="true"></ns2:fieldRemarks><ns2:branchRemarks>The purpose of this survey is to provide contemporary surveys to update National Ocean Service (NOS) nautical charts. All separates are filed
with the hydrographic data. Any revisions to the Descriptive Report (DR) generated during office processing are shown in bold red italic text.
The processing branch maintains the DR as a field unit product, therefore, all information and recommendations within the body of the DR are
considered preliminary unless otherwise noted. The final disposition of surveyed features is represented in the OCS nautical chart update products.
All pertinent records for this survey, including the DR, are archived at the National Geophysical Data Center (NGDC) and can be retrieved via http://
www.ngdc.noaa.gov/.</ns2:branchRemarks></ns2:titlesheetRemarks></ns1:surveyMetadata><ns1:assignment>NOAA</ns1:assignment></ns1:metadata><ns1:areaSurveyed><ns1:areaDescription><ns2:discussion>The survey area is referred to as Sheet 8: &quot;5 NM South of Simeonof Island&quot; within the Project Instructions (Figure 1).  The area is 2.2 NM south of Simeonof Island and 3.7 NM east of Chernabura Island.</ns2:discussion><ns2:limits><ns2:northWest><ns2:latitude hemisphere="N">54.8268555556</ns2:latitude><ns2:longitude hemisphere="W">159.406727778</ns2:longitude></ns2:northWest><ns2:southEast><ns2:latitude hemisphere="N">54.7335972222</ns2:latitude><ns2:longitude hemisphere="W">159.102497222</ns2:longitude></ns2:southEast></ns2:limits><ns2:images><ns2:caption>H12595 survey limits.</ns2:caption><ns2:link>SupportFiles\Image 1.png</ns2:link></ns2:images><ns2:comments/></ns1:areaDescription><ns1:surveyLimits><ns2:results deviation="true"><ns2:discussion>Parts of the northeast corner of this survey did not reach the sheet limits; however, prior survey H12475 completely covers this area and there is significant overlap between the two surveys (Figure 2).</ns2:discussion><ns2:images><ns2:caption>H12475 overlap with H12595 sheet limits.</ns2:caption><ns2:link>SupportFiles\Figure 2 Overlap.png</ns2:link></ns2:images></ns2:results><ns2:comments><ns2:branchComment concurrence="Concur with clarification"><ns2:comment>SAR: Figure 2 contains a typo and the northern area pictured should read H12475, not H12473.</ns2:comment></ns2:branchComment></ns2:comments></ns1:surveyLimits><ns1:surveyPurpose><ns2:discussion>The purpose of this survey 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 H12595 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 HSSD (Figure 3) with one exception:  

The 1-meter surface fell slightly short of density requirements due to foul weather at the time of acquisition. 

Statistics were extracted from the density layer of each finalized surface in CARIS and examined in Excel.  Overall, the required data density was achieved in 100.0% of the nodes by area (Figure 4).</ns2:discussion><ns2:images><ns2:caption>H12595 data density.</ns2:caption><ns2:link>SupportFiles\Image 2 Density.png</ns2:link></ns2:images><ns2:images><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\Image 3 Density Table.png</ns2:link></ns2:images><ns2:comments><ns2:branchComment concurrence="Comment Only"><ns2:comment>SAR: In review, the Density analysis was verified using a macro - FinalizedCSARSurfaceQA.py - distributed with NOAA's in-house software suite Pydro, which analyses values directly from the .csar surfaces and do not use intermediate applications or files. The results disagree with the values found in Figure 4. The 1m surface contains 12172/12909 nodes ( 94.29%) which pass the density requirement. The 2m surface contains 149459/150054 nodes (99.6%) which pass the density requirement, and the 4m surface contains 12625970/12629583 nodes (99.97%) which pass the density requirement.</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 defined in the Project Instructions with the following exceptions:

Acoustic Shadowing:  Almost all holidays were a result of acoustic shadowing (Figure 6).  This effect was seen where data density on the 'dark' side of a feature or between features was too sparse to produce a surface at the appropriate resolution.  All cases were investigated to assure that least depths were found.

Coverage Gaps:  Data acquisition during poor weather conditions resulted in coverage gaps, the largest of which is 116 meters by 8 meters (Figure 7).  All of the coverage gaps are at a depth of 30 meters or greater, and are not navigationally significant.</ns2:discussion><ns2:images><ns2:caption>Subset exemplifying the acoustic shadows seen in the survey. </ns2:caption><ns2:link>SupportFiles\use_this_acoustic_shadow.png</ns2:link></ns2:images><ns2:images><ns2:caption>Location of largest coverage gap.</ns2:caption><ns2:link>SupportFiles\Figure 7 Coverage Gap.png</ns2:link></ns2:images></ns2:results><ns2:comments><ns2:branchComment concurrence="Concur with clarification"><ns2:comment>In review, the reviewer used a 4m resolution to grid the surfaces for compilation because the 8m surface was unnecessary given the depths. When gridded according to the HSSD, gaps appeared - caused by bubble sweep raking the sonar face in inclement weather and disrupting very short, swath-wide segments of bathymetry. The gaps were investigated and found to contain no navigationally significant features. All remaining data is adequate to supersede charted data. </ns2:comment></ns2:branchComment></ns2:comments></ns1:surveyCoverage><ns1:coverageGraphic><ns2:caption>Acquired survey coverage overlaid on Chart 16540. Scale shows depth in meters.</ns2:caption><ns2:link>SupportFiles\Figure 5 Overview.png</ns2:link></ns1:coverageGraphic><ns1:surveyStatistics><ns2:LNM><ns2:vesselLNM><ns2:vessel><ns2:hullID>S221</ns2:hullID><ns2:statistics><ns2:MS_SBES>0</ns2:MS_SBES><ns2:MS_MBES>510.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>0</ns2:XL_MBES_SBES><ns2:XL_lidar>0</ns2:XL_lidar></ns2:statistics></ns2:vessel><ns2:vessel><ns2:hullID>2801</ns2:hullID><ns2:statistics><ns2:MS_SBES>0</ns2:MS_SBES><ns2:MS_MBES>17.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>2802</ns2:hullID><ns2:statistics><ns2:MS_SBES>0</ns2:MS_SBES><ns2:MS_MBES>50.9</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>25.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</ns2:hullID><ns2:statistics><ns2:MS_SBES>0</ns2:MS_SBES><ns2:MS_MBES>44.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>29.0</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>647.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>29</ns2:XL_MBES_SBES><ns2:XL_lidar>0</ns2:XL_lidar><ns2:percentXLLNM>4.5</ns2:percentXLLNM></ns2:totalLNM></ns2:LNM><ns2:totalSurveyStats><ns2:bottomSamples>12</ns2:bottomSamples><ns2:AWOIS>0</ns2:AWOIS><ns2:maritimeBoundaryPoints>0</ns2:maritimeBoundaryPoints><ns2:DP>0</ns2:DP><ns2:diveOps>0</ns2:diveOps><ns2:SNM>59.11</ns2:SNM></ns2:totalSurveyStats><ns2:surveyDates>2013-07-17</ns2:surveyDates><ns2:surveyDates>2013-07-18</ns2:surveyDates><ns2:surveyDates>2013-07-24</ns2:surveyDates><ns2:surveyDates>2013-08-02</ns2:surveyDates><ns2:surveyDates>2013-08-06</ns2:surveyDates><ns2:surveyDates>2013-08-08</ns2:surveyDates><ns2:surveyDates>2013-08-09</ns2:surveyDates><ns2:surveyDates>2013-08-10</ns2:surveyDates><ns2:surveyDates>2013-08-11</ns2:surveyDates><ns2:surveyDates>2013-09-02</ns2:surveyDates><ns2:surveyDates>2013-09-03</ns2:surveyDates><ns2:discussion>All data for survey H12595 was acquired by NOAA Ship RAINIER and her four survey launches (2801, 2802, 2803, and 2804). The survey launches and ship acquired MBES depth soundings, sound speed profiles, and bottom samples.</ns2:discussion><ns2:comments/></ns1:surveyStatistics></ns1:areaSurveyed><ns1:dataAcquisitionAndProcessing><ns1:equipmentAndVessels><ns1:discussion>Refer to the Data Acquisition and Processing Report (DAPR) for a complete description of data acquisition and processing systems, survey vessels, quality control procedures and data processing methods.  Additional information to supplement sounding and survey data, and any deviations from the DAPR are discussed in the following sections.</ns1:discussion><ns1:vessels><ns1:vessel><ns2:hullID>S221 (Rainier)</ns2:hullID><ns2:LOA units="feet">231</ns2:LOA><ns2:draft units="feet">16.5</ns2:draft></ns1:vessel><ns1:vessel><ns2:hullID>2801 (RA-4)</ns2:hullID><ns2:LOA units="feet">28</ns2:LOA><ns2:draft units="feet">3.5</ns2:draft></ns1:vessel><ns1:vessel><ns2:hullID>2802 (RA-5)</ns2:hullID><ns2:LOA units="feet">28</ns2:LOA><ns2:draft units="feet">3.5</ns2:draft></ns1:vessel><ns1:vessel><ns2:hullID>2803 (RA-3)</ns2:hullID><ns2:LOA units="feet">28</ns2:LOA><ns2:draft units="feet">3.5</ns2:draft></ns1:vessel><ns1:vessel><ns2:hullID>2804 (RA-6)</ns2:hullID><ns2:LOA units="feet">28</ns2:LOA><ns2:draft units="feet">3.5</ns2:draft></ns1:vessel><ns1:discussion xsi:nil="true"></ns1:discussion><ns1:comments/></ns1:vessels><ns1:equipment><ns1:majorSystem><ns2:manufacturer>Reson</ns2:manufacturer><ns2:model>7125</ns2:model><ns2:type>MBES</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>Kongsberg</ns2:manufacturer><ns2:model>EM710</ns2:model><ns2:type>MBES</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>ODIM Brooke Ocean (Rolls-Royce Group)</ns2:manufacturer><ns2:model>MVP30</ns2:model><ns2:type>Conductivity, Temperature, and Depth Sensor</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>ODIM Brooke Ocean (Rolls-Royce Group)</ns2:manufacturer><ns2:model>MVP200</ns2:model><ns2:type>Conductivity, Temperature, and Depth Sensor</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>Seabird</ns2:manufacturer><ns2:model>SBE 19 Plus</ns2:model><ns2:type>Conductivity, Temperature, and Depth Sensor</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>Seabird</ns2:manufacturer><ns2:model>SBE 19</ns2:model><ns2:type>Conductivity, Temperature, and Depth Sensor</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 vessel 2801 (RA-4). A 4-meter CUBE surface was created using the mainscheme lines, while a second 4-meter CUBE surface was created using only crosslines, from which a difference surface was generated in CARIS at a 4-meter resolution (Figure 8). Statistics were then derived from the difference surface and are shown in Figure 9. The average difference between the depths derived from the mainscheme and crosslines was 0.04 meters (crosslines being shoaler) with a standard deviation of 0.17 meters.  

For the respective depths, the difference surface was compared to the allowable IHO accuracy standards (Figure 10). In total, 100.0% of the depth differences between H12595 mainscheme and crossline data are within allowable IHO accuracies (Figure 11).</ns2:discussion><ns2:images><ns2:caption>H12595 difference surface between the mainscheme and crosslines.</ns2:caption><ns2:link>SupportFiles\XL Difference.png</ns2:link></ns2:images><ns2:images><ns2:caption>Crossline comparison with mainscheme lines.</ns2:caption><ns2:link>SupportFiles\Image 9 crossline.png</ns2:link></ns2:images><ns2:images><ns2:caption>Depth differences between H12595 mainscheme and crossline data as compared to allowable IHO accuracy standards for the associated depths.</ns2:caption><ns2:link>SupportFiles\IHO difference.png</ns2:link></ns2:images><ns2:images><ns2:caption>Summary table showing percentage of difference surface nodes between H12595 mainscheme and crossline data that meet allowable IHO accuracy standards for the respective depths.</ns2:caption><ns2:link>SupportFiles\Crossline IHOness Table.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.045</ns2:zoning></ns2:tideUncertainty><ns2:soundSpeedUncertainty><ns2:hullID>S221</ns2:hullID><ns2:measuredCTD xsi:nil="true"/><ns2:measuredMVP units="meters/second">1.0</ns2:measuredMVP><ns2:surface units="meters/second">0.05</ns2:surface></ns2:soundSpeedUncertainty><ns2:soundSpeedUncertainty><ns2:hullID>2801</ns2:hullID><ns2:measuredCTD units="meters/second">3.0</ns2:measuredCTD><ns2:measuredMVP xsi:nil="true"/><ns2:surface units="meters/second">0.15</ns2:surface></ns2:soundSpeedUncertainty><ns2:soundSpeedUncertainty><ns2:hullID>2802</ns2:hullID><ns2:measuredCTD units="meters/second">3.0</ns2:measuredCTD><ns2:measuredMVP xsi:nil="true"/><ns2:surface units="meters/second">0.15</ns2:surface></ns2:soundSpeedUncertainty><ns2:soundSpeedUncertainty><ns2:hullID>2803</ns2:hullID><ns2:measuredCTD units="meters/second">3.0</ns2:measuredCTD><ns2:measuredMVP xsi:nil="true"/><ns2:surface units="meters/second">0.15</ns2:surface></ns2:soundSpeedUncertainty><ns2:soundSpeedUncertainty><ns2:hullID>2804</ns2:hullID><ns2:measuredCTD xsi:nil="true"/><ns2:measuredMVP units="meters/second">3.0</ns2:measuredMVP><ns2:surface units="meters/second">0.15</ns2:surface></ns2:soundSpeedUncertainty></ns2:values><ns2:discussion>Total propagated uncertainty values for survey H12595 were derived from a combination of fixed values for equipment and vessel characteristics, as well as field assigned values for sound speed uncertainties. Tidal uncertainties were provided by NOAA's Center for Operational Oceanographic Products and Services 
(CO-OPS), and were applied to depth soundings.

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 the locations in which accuracy requirements were met, for each finalized surface a custom &quot;predicted IHO compliance&quot; layer was created based on the difference between calculated uncertainty of the nodes and the allowable IHO uncertainty (Figure 12). To quantify the extent to which accuracy requirements were met, the preceding &quot;predicted IHO compliance&quot; layers were queried within CARIS and then examined in Excel (Figure 13). Overall, 100.0% by node and 100.0% by area of survey H12595 met the accuracy requirements stated in the HSSD.

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 H12595. 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 include 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.</ns2:discussion><ns2:images><ns2:caption>H12595 met IHO accuracy standards for 100.0% of the survey area.</ns2:caption><ns2:link>SupportFiles\IHO Uncertainty SFC.png</ns2:link></ns2:images><ns2:images><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 different resolution nodes into a common unit of area.</ns2:caption><ns2:link>SupportFiles\IHO Uncertainty Table.png</ns2:link></ns2:images><ns2:comments><ns2:branchComment concurrence="Comment Only"><ns2:comment>SAR: In review, the TPU analysis was verified using a macro - FinalizedCSARSurfaceQA.py - distributed with NOAA's in-house software suite Pydro, which analyses values directly from the .csar surfaces and do not use intermediate applications or files. The results disagree with some values found in DR Figure 13. The 1m surface contains 12909/12909 nodes (100%) which pass the density requirement. The 2m surface contains 149885/150054 nodes (99.89%) which pass the density requirement, and the 4m surface contains 12629395/12629583 nodes (99.99%) which pass the density requirement.

It should be noted that node counts for surfaces in the DR's Figure 4 and Figure 13 do not agree, which is indicative of an incomplete analysis. Despite these errors, the review shows that surveyed data is of the highest order quality and adequate to supersede charted soundings.</ns2:comment></ns2:branchComment></ns2:comments></ns1:uncertainty><ns1:junctions><ns2:discussion>Three junction comparisons were completed for H12595. One survey (H12594) was acquired concurrently with this survey, and two surveys (H12473 and H12475) were completed in 2012 by NOAA Ship RAINIER (Figure 14). Depth comparisons were performed using CARIS difference surfaces and Subset Editor.</ns2:discussion><ns2:images><ns2:caption>H12595 junction overview.</ns2:caption><ns2:link>SupportFiles\H12595 Junctions.png</ns2:link></ns2:images><ns2:junction><ns2:survey><ns2:registryNumber>H12473</ns2:registryNumber><ns2:scale>40000</ns2:scale><ns2:year>2012</ns2:year><ns2:fieldUnit>NOAA Ship RAINIER</ns2:fieldUnit><ns2:relativeLocation>NW</ns2:relativeLocation></ns2:survey><ns2:discussion>Overlap with survey H12473 ranges from 90 to 450 meters wide along the northwestern boundary of H12595 (Figure 15). Depths in the junction area range from approximately 10 to 60 meters. A difference surface analysis between CUBE depth layers for each survey showed H12595 to be an average of 0.04 meters deeper than H12473, with a standard deviation of 0.23 meters (Figure 16). This is well within IHO Order 1 accuracy at these depths.</ns2:discussion><ns2:images><ns2:caption>Junction between H12595 (blue) and H12473 (red).</ns2:caption><ns2:link>SupportFiles\H12473 Junction.png</ns2:link></ns2:images><ns2:images><ns2:caption>Difference surface statistics between H12595 and H12473 CUBE depth layers (4m grid size). H12595 is an average of 0.04 meters deeper.</ns2:caption><ns2:link>SupportFiles\H12473 Junction Histogram.png</ns2:link></ns2:images><ns2:comments/></ns2:junction><ns2:junction><ns2:survey><ns2:registryNumber>H12475</ns2:registryNumber><ns2:scale>40000</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 H12475 ranges from 60 to 490 meters wide along the northeastern boundary of H12595 (Figure 17). Depths in the junction area range from approximately 36 to 66  meters. A difference surface analysis between CUBE depth layers for each survey showed H12595 to be an average of 0.09 meters deeper than H12475, with a standard deviation of 0.17 meters (Figure 18). This is well within IHO Order 1 accuracy at these depths.</ns2:discussion><ns2:images><ns2:caption>Junction between H12595 (blue) and H12475 (green).</ns2:caption><ns2:link>SupportFiles\H12475 Junction.png</ns2:link></ns2:images><ns2:images><ns2:caption>Difference surface statistics between H12595 and H12475 CUBE depth layers (4m grid size). H12595 is an average of 0.09 meters deeper.</ns2:caption><ns2:link>SupportFiles\H12475 Junction Histogram.png</ns2:link></ns2:images><ns2:comments/></ns2:junction><ns2:junction><ns2:survey><ns2:registryNumber>H12594</ns2:registryNumber><ns2:scale>40000</ns2:scale><ns2:year>2013</ns2:year><ns2:fieldUnit>NOAA Ship RAINIER</ns2:fieldUnit><ns2:relativeLocation>W</ns2:relativeLocation></ns2:survey><ns2:discussion>Overlap with survey H12594 ranges from 160 to 460 meters wide along the western boundary of H12595 (Figure 19). Depths in the junction area range from approximately 35 to 60 meters. A difference surface analysis between CUBE depth layers for each survey showed H12595 to be an average of 0.09 meters shoaler than H12594, with a standard deviation of 0.12 meters (Figure 20). This is well within IHO Order 1 accuracy at these depths.</ns2:discussion><ns2:images><ns2:caption>Junction between H12595 (blue) and H12594 (brown).</ns2:caption><ns2:link>SupportFiles\H12594 Junction.png</ns2:link></ns2:images><ns2:images><ns2:caption>Difference surface statistics between H12595 and H12594 CUBE depth layers (4m grid size). H12595 is an average of 0.09 meters shoaler.</ns2:caption><ns2:link>SupportFiles\H12594 Junction Histogram.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="false"><ns2:issue><ns2:title>None Exist</ns2:title><ns2:discussion>There were no conditions or deficiencies that affected equipment operational effectiveness.</ns2:discussion><ns2:comments/></ns2:issue></ns2:results><ns2:comments/></ns1:equipmentEffectiveness><ns1:factorsAffectingSoundings><ns2:results deviation="true"><ns2:issue><ns2:title>Ellipsoid-to-Tidal Surface Comparison</ns2:title><ns2:discussion>Using the GPS height determined from the SBET file, data from H12595 was referenced to the ellipse and gridded. As a QC tool an ERS to MLLW difference surface was created to identify artifacts. 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. Misprojected SBETs, current induced dynamic draft, incorrect waterline measurements, corrupt TrueHeave 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.

The depth gradient between the MLLW and the ERS surfaces is expected to be similar in magnitude and position as the EGM2008-WGS84 geoid-ellipsoid separation model published by the National Geospatial-Intelligence Agency (NGA). In review, it was found that the two models compare well - exhibiting a signature northwest to southeast gradient of depth differences across the survey area - particularly considering the 2.5' resolution of the NGA surface and the expected differences between the geoid and MLLW (Figure 21).

There are three notable artifacts apparent in the data; two lines indicated on the eastern side of the survey show a heave artifact, and a dark red line shows vertical offsets from surrounding data. Upon review, it was found that the two lines on the eastern side of the survey had missing TrueHeave records for small segments of each line. This created heave artifacts of ± 0.5 meters that were present at MLLW but not on the ellipse. TrueHeave was retained for these lines in order to improve the quality of the majority of the data (see B.3.1 Corrections to Echo Soundings). The dark red line indicates vertical offsets of up to 0.4 meters from surrounding data. These offsets are only present on the ellipse. 

Four lines were excluded from this difference surface due to problems with the application of SBETs (see C.3.3.1 Lines without SBETs).  </ns2:discussion><ns2:images><ns2:caption>Difference surface between the ellipsoidally-referenced and tidally-referenced surfaces. Difference surface is overlaid on the EGM2008-WGS84 geoid-ellipsoid separation model with artifacts.</ns2:caption><ns2:link>SupportFiles\ERS Surface with Errors.png</ns2:link></ns2:images><ns2:comments/></ns2:issue><ns2:issue><ns2:title>Sound Speed Artifacts</ns2:title><ns2:discussion>Despite casts being taken as frequently as every 15 minutes, with consideration to spatial distribution, sound speed artifacts were seen within the data. These artifacts occurred as &quot;smiles&quot; or &quot;frowns&quot; due to inadequately modeled refraction. In these areas, the outer beams were flagged as rejected to assist the gridding algorithm in bringing the surface back to better represent the true seafloor. Although this artifact exists within the data, it is within uncertainty standards specifications as stated within Section 5.1.3 of the HSSD. The Hydrographer finds that the data is adequate to supersede charted data (Figure 22).</ns2:discussion><ns2:images><ns2:caption>Example of sound speed artifact seen within H12595.</ns2:caption><ns2:link>SupportFiles\B.2.7 Sound Speed Artifacts.png</ns2:link></ns2:images><ns2:comments/></ns2:issue></ns2:results><ns2:comments/></ns1:factorsAffectingSoundings><ns1:soundSpeedMethods><ns1:castFrequency>For casts collected on S221, 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 other launch sound speed profiles were acquired using the SBE-19 and SBE-19 plus CTDs at discrete locations at least once every four hours. A concatenated sound speed casts file was created for each vessel and applied to all H12595 survey lines using the &quot;Nearest in Distance within (4 hours) Time&quot; profile selection method. A total of 282 CTD casts were used (Figure 23).</ns1:castFrequency><ns1:discussion xsi:nil="true"></ns1:discussion><ns1:images><ns2:caption>Distribution of sound speed profiles acquired for survey H12595.</ns2:caption><ns2:link>SupportFiles\Sound Speed Locations 3.png</ns2:link></ns1:images><ns1:comments/></ns1:soundSpeedMethods><ns1:coverageEquipmentAndMethods><ns2:results deviation="true"><ns2:discussion>Modified EM710 Waterline Value:

A routine part of acquisition with the EM710 is a measurement of the ship's waterline immediately before commencing operations, or immediately after any evolution that is suspected to impact said waterline (e.g. the deployment/recovery of launches); see DAPR. On DN218, however, a waterline measurement was taken that was suspected to be in error (-4.556 meters), likely due to large seas at the time of observation. This measurement was not in keeping with historic values and led to a vertical shift in the data acquired by the ship on this day. To address this, the waterline measurement taken two days later and under similar loading conditions (-4.707 meters) was used for DN218. This change was observed to improve vertical agreement with surrounding data and is documented in the HVF.</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. 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:results><ns2:comments/></ns1:backscatter><ns1:dataProcessing><ns1:softwareUpdates><ns1:featureObjectCatalog>NOAA Profile V_5_3_2</ns1:featureObjectCatalog><ns1:discussion>All data was processed using CARIS HIPS and SIPS 8.1.1. 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>H12595_1m</ns2:surfaceName><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:resolution units="meters">1</ns2:resolution><ns2:depthRange><ns2:min units="meters">9</ns2:min><ns2:max units="meters">90</ns2:max></ns2:depthRange><ns2:surfaceParameter>NOAA_1m</ns2:surfaceParameter><ns2:purpose>Complete MBES</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceName>H12595_2m</ns2:surfaceName><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:resolution units="meters">2</ns2:resolution><ns2:depthRange><ns2:min units="meters">9</ns2:min><ns2:max units="meters">90</ns2:max></ns2:depthRange><ns2:surfaceParameter>NOAA_2m</ns2:surfaceParameter><ns2:purpose>Complete MBES</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceName>H12595_4m</ns2:surfaceName><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:resolution units="meters">4</ns2:resolution><ns2:depthRange><ns2:min units="meters">9</ns2:min><ns2:max units="meters">90</ns2:max></ns2:depthRange><ns2:surfaceParameter>NOAA_4m</ns2:surfaceParameter><ns2:purpose>Complete MBES</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceName>H12595_8m</ns2:surfaceName><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:resolution units="meters">8</ns2:resolution><ns2:depthRange><ns2:min units="meters">9</ns2:min><ns2:max units="meters">90</ns2:max></ns2:depthRange><ns2:surfaceParameter>NOAA_8m</ns2:surfaceParameter><ns2:purpose>Complete MBES</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceName>H12595_1m_0to20m_Final</ns2:surfaceName><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:resolution units="meters">1</ns2:resolution><ns2:depthRange><ns2:min units="meters">0</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>H12595_2m_18to40m__Final</ns2:surfaceName><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:resolution units="meters">2</ns2:resolution><ns2:depthRange><ns2:min units="meters">18</ns2:min><ns2:max units="meters">40</ns2:max></ns2:depthRange><ns2:surfaceParameter>NOAA_2m</ns2:surfaceParameter><ns2:purpose>Complete MBES</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceName>H12595_4m_36to80m_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>H12595_8m_72to100m_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">100</ns2:max></ns2:depthRange><ns2:surfaceParameter>NOAA_8m</ns2:surfaceParameter><ns2:purpose>Complete MBES</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceName>H12595_Combined_8m</ns2:surfaceName><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:resolution units="meters">8</ns2:resolution><ns2:depthRange><ns2:min units="meters">9</ns2:min><ns2:max units="meters">90</ns2:max></ns2:depthRange><ns2:surfaceParameter>NOAA_8m</ns2:surfaceParameter><ns2:purpose>Complete MBES</ns2:purpose></ns1:surface><ns1:discussion xsi:nil="true"></ns1:discussion><ns1:comments><ns2:branchComment concurrence="Concur with clarification"><ns2:comment>Depth ranges for BASE surfaces, 4m Finalized, and 4m Combined surface (created in review for compilation) do not exceed 78m, and do not extend to 90m as stated in Table 9.
A 4 meter base surface was created during SAR review. The H12595_MB_4m_MLLW_Combined file was used for final compilation.</ns2:comment></ns2:branchComment></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>Sand Point, AK </ns2:stationName><ns2:stationID>945-9450 </ns2:stationID></ns2:NWLONGauges><ns2:subordinateGauges><ns2:stationName>Bird Island, AK</ns2:stationName><ns2:stationID>945-9251</ns2:stationID></ns2:subordinateGauges></ns2:tideStations><ns2:correctorFiles><ns2:waterLevels><ns2:fileName>9459450.tid</ns2:fileName><ns2:status>Verified Observed</ns2:status></ns2:waterLevels><ns2:waterLevels><ns2:fileName>9459251.tid</ns2:fileName><ns2:status>Verified Observed</ns2:status></ns2:waterLevels><ns2:tideCorrectors><ns2:fileName>H12595CORF.zdf</ns2:fileName><ns2:status>Final</ns2:status></ns2:tideCorrectors></ns2:correctorFiles><ns2:finalTides><ns2:dateSubmitted>2013-09-20</ns2:dateSubmitted><ns2:dateReceived>2013-11-20</ns2:dateReceived></ns2:finalTides><ns2:discussion>The tide station installed by RAINIER personnel on Bird Island, AK (945-9251) was used as the primary control for datum determination and as a source for water level reducers from 2348 UTC on 13 July (DN194) through 0436 UTC on 18 August (DN230). The National Water Level Observation Network (NWLON) tide station in Sand Point, AK (945-9450) served as a subordinate gauge during this time. During the time of acquisition when the Bird Island gauge was not operational, the NWLON tide station in Sand Point served as the primary gauge. A complete description of the vertical and horizontal control for this survey can be found in the accompanying Horizontal and Vertical Control Report (HVCR), submitted under separate cover.</ns2:discussion><ns2:comments><ns2:branchComment concurrence="Concur"><ns2:comment>Tide note is appended to this report.</ns2:comment></ns2:branchComment></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 - Zone 04N</ns2:projection><ns2:PPK used="true"><ns2:methodsUsed>Single Base</ns2:methodsUsed><ns2:baseStations><ns2:userInstalledStations><ns2:HVCRSiteID>Bird Island</ns2:HVCRSiteID><ns2:stationID>N/A</ns2:stationID></ns2:userInstalledStations></ns2:baseStations><ns2:discussion>In conjunction with this project, a GPS base station was established by RAINIER personnel on Bird Island, AK; the station was operational from DN192 through DN207 and from DN222 through DN245. During the times when the Bird Island base station was not operational (DN208 through DN221 and DN246 through DN254), a Plate Boundary Observatory station on Chernabura Island (ChernaburaAK2008, AC12) was used for post-processing. There were two exceptions: On DN198 and DN199, there were several processing problems with the Bird Island base station; some of the data for these days was corrected using the Chernabura Island base station.

Vessel kinematic data was post-processed with Applanix POSPac and POSGNSS software using Single Base processing methods described in the DAPR. 

Differential Global Positioning System (DGPS) correctors were used for horizontal control when the post-processing methods stated above were not possible (see C.3 Additional Horizontal or Vertical Control Issues).

</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, AK (313 kHz)</ns2:name></ns2:USCGStations><ns2:USCGStations><ns2:name>Cold Bay, AK (289 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 Lines 0048_20130724_060218_Rainier and 0047_20130724_053305_Rainier acquired from vessel S221 DN205, and lines 2803_2013RA2221742 and 2803_2013RA2221802 acquired from vessel 2803 DN222 due to time extents not overlapping with the lines. DGPS correctors were retained for these lines. Inspection of the data in Subset Editor shows agreement with surrounding data.</ns2:discussion><ns2:comments/></ns2:issue><ns2:comments/></ns1:additionalIssues></ns1:verticalAndHorizontalControl><ns1:resultsAndRecommendations><ns1:chartComparison><ns1:methods><ns2:discussion>A comparison was made between survey H12595 and Chart 16540 using CARIS CUBE surfaces and a sounding layer. All data from H12595 should supersede charted data.</ns2:discussion><ns2:comments/></ns1:methods><ns1:charts><ns2:rasterChart><ns2:chart><ns2:number>16540</ns2:number><ns2:kapp>2528</ns2:kapp><ns2:scale>300000</ns2:scale><ns2:edition>13</ns2:edition><ns2:editionDate>2010-10</ns2:editionDate><ns2:LNMDate>2010-10-12</ns2:LNMDate><ns2:NMDate>2010-10-30</ns2:NMDate></ns2:chart><ns2:discussion>Comparison was performed with Chart 16540 (1:300000) using a CARIS sounding layer based on the combined 4-meter CUBE surface from H12595. During the comparison, it was observed that the charted rocks were not present.

The northern portion of the survey has a least depth of 5 fathoms just south of the charted 7 fathom sounding.  In addition, there are several areas shoaler than charted, the shoalest being 15 fathoms.  These shoals do not pose a danger to navigation (Figure 24). </ns2:discussion><ns2:images><ns2:caption>Chart 16540 depth comparison in fathoms.</ns2:caption><ns2:link>SupportFiles\D.1.1 Chart Soundings.png</ns2:link></ns2:images><ns2:comments><ns2:branchComment concurrence="Comment Only"><ns2:comment>Table 16 indicates that Notice to Mariners and Local Notice to Mariners were not applied to chart 16540 prior to comparison with field work by the hydrographer.  The chart used for comparison during office review and compilation was corrected through LNTM 09/13/2014 and NTM 9/23/2014.</ns2:comment></ns2:branchComment></ns2:comments></ns2:rasterChart><ns2:ENC><ns2:chart><ns2:name>US3AK50M</ns2:name><ns2:scale>300000</ns2:scale><ns2:edition>17</ns2:edition><ns2:updateApplicationDate>2011-06-29</ns2:updateApplicationDate><ns2:issueDate>2011-06-29</ns2:issueDate><ns2:preliminary>false</ns2:preliminary></ns2:chart><ns2:discussion>ENC US3AK50M was digitized from Chart 16540 and coincides with the raster. The depths on the ENC match the raster, and the comparison between survey H12595 and the ENC is equivalent to the preceding comparison with Chart 16540. The Hydrographer recommends that a sounding set derived from survey H12595 supersede charted depths.</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="None Exist"><ns2:discussion>No charted features exist for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:chartedFeatures><ns1:unchartedFeatures><ns2:results investigated="None Exist"><ns2:discussion>No uncharted features exist for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:unchartedFeatures><ns1:DTONS><ns2:results reportSubmitted="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>Bottom samples were acquired in accordance with the Project Instructions and the HSSD. Twelve proposed bottom sample locations were included in the Project Reference File; all twelve samples were collected. All samples were labeled in accordance with the HSSD with S-57 attribution, and can be found in the Final Feature File (Figure 25). </ns2:discussion><ns2:images><ns2:caption>Bottom sample locations.</ns2:caption><ns2:link>SupportFiles\Bottom Samples.png</ns2:link></ns2:images></ns2:results><ns2:comments/></ns1:bottomSamples></ns1:chartComparison><ns1:additionalResults><ns1:shoreline><ns2:results investigated="None Exist"><ns2:discussion>Shoreline was not assigned in the Hydrographic Survey Project Instructions or Statement of Work.</ns2:discussion></ns2:results><ns2:comments/></ns1:shoreline><ns1:priorSurveys><ns2:results investigated="None Exist"><ns2:discussion>No prior survey comparisons exist for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:priorSurveys><ns1:ATONS><ns2:results investigated="None Exist"><ns2:discussion>No Aids to navigation (ATONs) exist for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:ATONS><ns1:overheadFeatures><ns2:results investigated="None Exist"><ns2:discussion>No overhead features exist for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:overheadFeatures><ns1:submarineFeatures><ns2:results investigated="None Exist"><ns2:discussion>No submarine features exist for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:submarineFeatures><ns1:ferryRoutesAndTerminals><ns2:results investigated="None Exist"><ns2:discussion>No ferry routes or terminals exist for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:ferryRoutesAndTerminals><ns1:platforms><ns2:results investigated="None Exist"><ns2:discussion>No platforms exist for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:platforms><ns1:significantFeatures><ns2:results investigated="None Exist"><ns2:discussion>No significant features exist for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:significantFeatures><ns1:constructionOrDredging><ns2:results investigated="None Exist"><ns2:discussion>No present or planned construction or dredging exist within the survey limits.</ns2:discussion></ns2:results><ns2:comments/></ns1:constructionOrDredging><ns1:otherResults><ns2:comments/></ns1:otherResults><ns1:newSurveyRecommendation><ns2:results recommended="false"><ns2:discussion>No new surveys or further investigations are recommended for this area.</ns2:discussion></ns2:results><ns2:comments/></ns1:newSurveyRecommendation><ns1:insetRecommendation><ns2:results recommended="false"><ns2:discussion>No new insets are recommended for this area.</ns2:discussion></ns2:results><ns2:comments/></ns1:insetRecommendation></ns1:additionalResults></ns1:resultsAndRecommendations><ns1:approvalSheet><ns1:statements><ns1:supervision>As Chief of Party, Field operations for this hydrographic survey were conducted under my direct supervision, with frequent personal checks of progress and adequacy. I have reviewed the attached survey data and reports.</ns1:supervision><ns1:approval>All field sheets, this Descriptive Report, and all accompanying records and data are approved. All records are forwarded for final review and processing to the Processing Branch.</ns1:approval><ns1:adequacyOfSurvey>The survey data meets or exceeds requirements as set forth in the NOS Hydrographic Surveys and Specifications Deliverables Manual, Field Procedures Manual, Letter Instructions, and all HSD Technical Directives. These data are adequate to supersede charted data in their common areas. This survey is complete and no additional work is required with the exception of deficiencies noted in the Descriptive Report.</ns1:adequacyOfSurvey><ns1:additionalInfo xsi:nil="true"></ns1:additionalInfo></ns1:statements><ns1:signingPersonnel><ns2:approverName>Richard T. Brennan, CDR/NOAA</ns2:approverName><ns2:approverTitle>Commanding Officer, NOAA Ship RAINIER</ns2:approverTitle><ns2:approvalDate>2013-12-11</ns2:approvalDate></ns1:signingPersonnel><ns1:signingPersonnel><ns2:approverName>Meghan McGovern, LT/NOAA</ns2:approverName><ns2:approverTitle>Field Operations Officer, NOAA Ship RAINIER</ns2:approverTitle><ns2:approvalDate>2013-12-11</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-12-11</ns2:approvalDate></ns1:signingPersonnel><ns1:signingPersonnel><ns2:approverName>J.C. Clark, ENS/NOAA</ns2:approverName><ns2:approverTitle>Junior Officer, NOAA Ship RAINIER</ns2:approverTitle><ns2:approvalDate>2013-12-11</ns2:approvalDate></ns1:signingPersonnel></ns1:approvalSheet></ns1:descriptiveReport>