<?xml version="1.0" encoding="UTF-8"?><ns1:descriptiveReport xmlns:ns1="http://svn.pydro.noaa.gov/2015/02/DescriptiveReport" xmlns:ns2="http://svn.pydro.noaa.gov/2015/02/AllGlobalTypes" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://svn.pydro.noaa.gov/2015/02/DescriptiveReport http://svn.pydro.noaa.gov/2015/02/DR.xsd"><ns1:metadata><ns1:projectMetadata><ns2:number>OPR-S327-RA-15</ns2:number><ns2:name>Kotzebue Sound, AK</ns2:name><ns2:generalLocality>Kotzebue Sound, AK</ns2:generalLocality><ns2:fieldUnit>NOAA Ship Rainier</ns2:fieldUnit></ns1:projectMetadata><ns1:registryMetadata><ns2:registryNumber>H12829</ns2:registryNumber><ns2:sheetID>18</ns2:sheetID><ns2:registryInstructions>Commence survey when gauge 94BBBBB is operational.  Coordinate with HSD-OPS.</ns2:registryInstructions><ns2:sublocality>2 Miles NW of Espenberg</ns2:sublocality><ns2:stateOrTerritory>Alaska</ns2:stateOrTerritory><ns2:country>United States</ns2:country><ns2:scale>40000</ns2:scale></ns1:registryMetadata><ns1:surveyMetadata><ns2:year>2015</ns2:year><ns2:chiefOfParty>Edward J. Van Den Ameele, CDR/NOAA</ns2:chiefOfParty><ns2:projectType>Navigable Area</ns2:projectType><ns2:PIDate>2015-05-28</ns2:PIDate><ns2:datesOfSurvey><ns2:start>2015-08-06</ns2:start><ns2:end>2015-08-12</ns2:end></ns2:datesOfSurvey><ns2:equipmentTypes><ns2:soundingEquipment>Multibeam Echo Sounder</ns2:soundingEquipment><ns2:imageryEquipment>Multibeam Echo Sounder Backscatter</ns2:imageryEquipment><ns2:imageryEquipment>Side Scan Sonar</ns2:imageryEquipment></ns2:equipmentTypes><ns2:acquisition><ns2:units>meters</ns2:units></ns2:acquisition><ns2:horizontalCoordinateSystem zone="3N">Universal Transverse Mercator (UTM)</ns2:horizontalCoordinateSystem><ns2:timeZone>UTC</ns2:timeZone><ns2:verifier>Pacific Hydrographic Branch</ns2:verifier><ns2:titlesheetRemarks><ns2:fieldRemarks xsi:nil="true"></ns2:fieldRemarks><ns2:branchRemarks>The purpose of this survey is to provide contemporary surveys to update National Ocean Service (NOS) nautical charts. All separates are filed with the hydrographic data. Any revisions to the Descriptive Report (DR) generated during office processing are shown in bold, red italic text.  The processing branch maintains the DR as a field unit product, therefore, all information and recommendations within the body of the DR are considered preliminary unless otherwise noted. The final disposition of surveyed features is represented in the OCS nautical chart update products.  All pertinent records for this survey, including the DR, are archived at the National Centers for Environmental Information (NCEI) and can be retrieved via http://www.ncei.noaa.gov/.</ns2:branchRemarks></ns2:titlesheetRemarks></ns1:surveyMetadata><ns1:assignment>NOAA</ns1:assignment></ns1:metadata><ns1:areaSurveyed><ns1:areaDescription><ns2:discussion>The project area is referred to as H12828 &quot;2 Miles NE of Espenberg&quot; (Priority 17) and H12829 &quot;2 Miles NW of Espenberg&quot; (Priority 18) within the Project Instructions.  The area is directly north of Espenberg, AK (Figure 1).  </ns2:discussion><ns2:limits><ns2:northWest><ns2:latitude hemisphere="N">66.6875706944</ns2:latitude><ns2:longitude hemisphere="W">164.286898</ns2:longitude></ns2:northWest><ns2:southEast><ns2:latitude hemisphere="N">66.5901216111</ns2:latitude><ns2:longitude hemisphere="W">163.717958111</ns2:longitude></ns2:southEast></ns2:limits><ns2:images><ns2:caption>H12829 and H12828 combined survey area as assigned in Project Instructions dated May 28, 2015 (Chart 16005).</ns2:caption><ns2:link>SupportFiles\Original survey area.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>Outline of area surveyed as part of H12829.</ns2:caption><ns2:link>SupportFiles\Survey_Outline.png</ns2:link></ns2:images><ns2:comments/></ns1:areaDescription><ns1:surveyLimits><ns2:results deviation="true"><ns2:discussion>On August 7, 2015 H12829 and H12828 were combined and given the registry number H12829.  Details are included in &quot;RA Combine Sheets H12828 and H12829.pdf&quot; located in the supplemental  correspondence folder.

Additional fixed-line spacing mainscheme lines were run with Rainier launch 2801 south of the survey limits to provide preliminary information regarding the contouring of Kotzebue Sound near the town of Espenberg, AK.</ns2:discussion></ns2:results><ns2:comments><ns2:branchComment concurrence="Comment Only"><ns2:comment>See attached correspondence regarding revisions to sheet limits and coverage requirements.</ns2:comment></ns2:branchComment></ns2:comments></ns1:surveyLimits><ns1:surveyPurpose><ns2:discussion>The purpose of this survey is to provide contemporary data to update National Ocean Service (NOS) nautical charting products.  Information for survey priorities was collected from a number of users/customers in the region including: Alaska Marine Pilots, USCG D17 &amp; buoy tender Hickory, Crowley Tug &amp; Barge, as well as field reports from USCG and NOAA personnel.</ns2:discussion><ns2:comments/></ns1:surveyPurpose><ns1:surveyQuality><ns2:adequacy>The survey is partially adequate to supersede previous data.</ns2:adequacy><ns2:discussion>H12829 data collected with 100% side scan sonar and concurrent multibeam met NOS Hydrographic Surveys Specifications and Deliverables (HSSD) May 2015 quality requirements and Project Instruction coverage standards with exceptions as noted in this report.  The finalized CSAR surface IHO compliance tool within Pydro was used to analyze H12829 MBES data.  The results showed that 99.3% of MBES nodes on the 1 meter surface and 99.4% of MBES nodes on the 2 meter surface of H12829 met HSSD object detection coverage requirements.   Data collected with only multibeam is adequate to supersede previous data only when shoaler than previously charted. (Figures 3, 4, 5).  SSS data were qualitatively examined by the hydrographer utilizing a SSS mosaic in accordance with the DAPR.
</ns2:discussion><ns2:images><ns2:caption>Summary table showing the percentage of nodes satisfying the HSSD 5 soundings density requirements, sub-divided by the appropriate depth ranges.</ns2:caption><ns2:link>SupportFiles\Density_Report.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>Pydro derived histogram plot showing HSSD object detection compliance of 1-meter surface of H12829 MBES data.</ns2:caption><ns2:link>SupportFiles\H12829_MB_1m_MLLW_FINAL_Density.png</ns2:link></ns2:images><ns2:images><ns2:caption>Pydro derived histogram plot showing HSSD object detection compliance of 2-meter surface of H12829 MBES data.</ns2:caption><ns2:link>SupportFiles\H12829_MB_2m_MLLW_FINAL_Density.png</ns2:link></ns2:images><ns2:comments/></ns1:surveyQuality><ns1:surveyCoverage><ns2:coverageRequirement><ns2:waterDepth>Inshore limit to 8 meters water depth</ns2:waterDepth><ns2:requiredCoverage>300 meter spaced Set Line Spacing SBES or MBES with backscatter.  Please ensure the following: 1) Indications of shoaling falling between set line spacing main scheme lines must be investigated 2) Set Line Spacing Line orientation should be approximately perpendicular to iosbaths whenever possible.</ns2:requiredCoverage></ns2:coverageRequirement><ns2:coverageRequirement><ns2:waterDepth>8 meters to 20 meters water depth</ns2:waterDepth><ns2:requiredCoverage>Either 1) 100% SSS with concurrent set line spacing SBES or MBES with backscatter, or 2) complete MBES with backscatter.  Note: Complete MBES is sufficient for both determination of least depth identified with SSS and for disproving a feature - 100% SSS is insufficient to disprove a feature.  Refer to Section 6.1.2 of the HSSD to confirm proper SSS acquisition paramters.  Gaps in SSS coverage should be treated as gaps in MBES coverage and addressed accordingly.</ns2:requiredCoverage></ns2:coverageRequirement><ns2:coverageRequirement><ns2:waterDepth>Greater than 20 meters water depth</ns2:waterDepth><ns2:requiredCoverage>Complete MBES coverage with backscatter</ns2:requiredCoverage></ns2:coverageRequirement><ns2:results deviation="true"><ns2:discussion>On July 10, 2015 NOAA Hydrographic Survey Division (HSD) Operations Branch altered the coverage requirements for Kotzebue Sound surveys.  For specific changes, refer to &quot;OPR-S327-RAFA-15 Updated Coverage Requirements.pdf&quot; located in the supplemental correspondence folder included in the report.

On July 14, 2015 NOAA HSD further altered coverage requirements for Kotzebue Sound surveys.  Specific details are included in &quot;Second Change OPR-S327-RAFA-15 Updated Coverage Requirements2.pdf&quot; located in the supplemental correspondence folder.

An earlier than expected departure on August 12, 2015 prevented further investigation, at fixed line-spacing, of the area from the assigned corridor north to the original sheet limits.  

H12829 data was acquired by S221 with set 160m line spacing which provided 100% SSS coverage with concurrent multibeam within the corridor and with some expansion out to the original survey limits.  Multibeam crosslines were acquired within the limits of the corridor by launch 2803.  Additional fixed line-spacing multibeam lines were acquired outside of the sheet and corridor limits by launches 2803 and 2801 (Figure 6).

Complete side scan and multibeam coverage was not achieved as specified in the project instructions due to the unplanned early departure of the ship before the project could be completed.  Holidays in the side scan data (Figure 7) due to refraction, software setting errors, and ship's heading (Figure 8) could not be resolved before leaving the project area and are detailed in the H12829_Holidays_SSS.hob file.  They were identified by examining the imagery in the SSS editor, identifying areas of potential holidays, and comparing with adjacent lines.  Areas determined to be holidays were digitized in a .hob file.  Potential contacts detected by side scan were not investigated (Figure 9 and Figure 10) and are included in the H12829_Contacts.hob file.  Potential contacts were identified by examining the length of shadow and, if the shadow indicated over 1 meter in height, digitized into a .hob file. Limited multibeam holidays were observed due to sonar data blowouts (Figure 11) or acoustic shadowing.  Instances of acoustic shadowing occurred in the 18-20m range and only impacted the 1m surface.  The 2m surface did not experience shadowing.

Where multibeam holidays occurred the side scan data was examined to identify potential dangers or features.  No coincidental features were noted.

Lines 0034_20150807_105548_Rainier and 0000_20150808_000831_Rainier were determined to be ERS holidays due to unresolvable SBET issues and were excluded from submitted surfaces.  The data remains available and is reduced to MLLW via ERZT methods.  The multibeam data and associated side scan were examined for hazards and contacts but was not included in the bathymetry.  More detail is available in the Vertical and Horizontal Control section of this report.
</ns2:discussion><ns2:images><ns2:caption>H12829 Mixed Coverage Survey Outline with revised transit corridor outlined in black overlaid on Chart 16005.</ns2:caption><ns2:link>SupportFiles\Mixed coverage map.png</ns2:link></ns2:images><ns2:images><ns2:caption>SSS holidays overlaid on the mosaic.</ns2:caption><ns2:link>SupportFiles\SSS holidays overlaid on mosaic.png</ns2:link></ns2:images><ns2:images><ns2:caption>SSS and MBES Holidays caused by transition to JSF file format and ship's heading errors.</ns2:caption><ns2:link>SupportFiles\Sidescan and MBES whole due to JSF.png</ns2:link></ns2:images><ns2:images><ns2:caption>Overview of contacts detected with SSS.</ns2:caption><ns2:link>SupportFiles\Side scan contacts.png</ns2:link></ns2:images><ns2:images><ns2:caption>An inspection of a single contact along with the &gt;1m shadow measurement.</ns2:caption><ns2:link>SupportFiles\SSS contact.png</ns2:link></ns2:images><ns2:images><ns2:caption>MBES blowout leading to holiday production.</ns2:caption><ns2:link>SupportFiles\MBES blowout.png</ns2:link></ns2:images></ns2:results><ns2:comments><ns2:branchComment concurrence="Comment Only"><ns2:comment>See attached correspondence regarding revisions to sheet limits and coverage requirements.  The H12829_Holidays_SSS.hob file is not appended to this report.</ns2:comment></ns2:branchComment></ns2:comments></ns1:surveyCoverage><ns1:coverageGraphic><ns2:caption>OPR-S327-RA-15 altered coverage requirements, July 14, 2015.</ns2:caption><ns2:link>SupportFiles\Full corridor survey requirements.png</ns2:link></ns1:coverageGraphic><ns1:surveyStatistics><ns2:LNM><ns2:vesselLNM><ns2:vessel><ns2:hullID>2801</ns2:hullID><ns2:statistics><ns2:MS_SBES>0</ns2:MS_SBES><ns2:MS_MBES>23.8</ns2:MS_MBES><ns2:MS_lidar>0</ns2:MS_lidar><ns2:MS_SSS>0</ns2:MS_SSS><ns2:MS_SBES_MBES>0</ns2:MS_SBES_MBES><ns2:MS_MBES_SSS>0</ns2:MS_MBES_SSS><ns2:MS_SBES_SSS>0</ns2:MS_SBES_SSS><ns2:XL_MBES_SBES>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>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>70.3</ns2:XL_MBES_SBES><ns2:XL_lidar>0</ns2:XL_lidar></ns2:statistics></ns2:vessel><ns2:vessel><ns2:hullID>S221</ns2:hullID><ns2:statistics><ns2:MS_SBES>0</ns2:MS_SBES><ns2:MS_MBES>7.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>492.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:vesselLNM><ns2:totalLNM><ns2:MS_SBES>0</ns2:MS_SBES><ns2:MS_MBES>30.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>492.0</ns2:MS_MBES_SSS><ns2:MS_SBES_SSS>0</ns2:MS_SBES_SSS><ns2:XL_MBES_SBES>70.3</ns2:XL_MBES_SBES><ns2:XL_lidar>0</ns2:XL_lidar><ns2:percentXLLNM>13.4</ns2:percentXLLNM></ns2:totalLNM></ns2:LNM><ns2:totalSurveyStats><ns2:bottomSamples>1</ns2:bottomSamples><ns2:maritimeBoundaryPoints>0</ns2:maritimeBoundaryPoints><ns2:DP>0</ns2:DP><ns2:diveOps>0</ns2:diveOps><ns2:SNM>44.2</ns2:SNM></ns2:totalSurveyStats><ns2:surveyDates>2015-08-06</ns2:surveyDates><ns2:surveyDates>2015-08-07</ns2:surveyDates><ns2:surveyDates>2015-08-08</ns2:surveyDates><ns2:surveyDates>2015-08-12</ns2:surveyDates><ns2:discussion xsi:nil="true"></ns2:discussion><ns2:comments/></ns1:surveyStatistics></ns1:areaSurveyed><ns1:dataAcquisitionAndProcessing><ns1:equipmentAndVessels><ns1:discussion>Refer to the 2015 Data Acquisition and Processing Report (DAPR) for a complete description of data acquisition and processing systems, survey vessels, quality control procedures and data processing methods.  Additional information to supplement sounding and survey data, and any deviations from the DAPR are discussed in the following sections.</ns1:discussion><ns1:vessels><ns1:vessel><ns2:hullID>2801</ns2:hullID><ns2:LOA units="meters">8.8</ns2:LOA><ns2:draft units="meters">1.1</ns2:draft></ns1:vessel><ns1:vessel><ns2:hullID>2803</ns2:hullID><ns2:LOA units="meters">8.8</ns2:LOA><ns2:draft units="meters">1.1</ns2:draft></ns1:vessel><ns1:vessel><ns2:hullID>S221</ns2:hullID><ns2:LOA units="meters">70.4</ns2:LOA><ns2:draft units="meters">4.7</ns2:draft></ns1:vessel><ns1:images><ns2:caption>NOAA Ship Rainier S221 steams away after deploying a launch.</ns2:caption><ns2:link>SupportFiles\S221 during acquisition and launch deployment.jpg</ns2:link></ns1:images><ns1:images><ns2:caption>Launch 2802 returns to S221 (all launches are identical).</ns2:caption><ns2:link>SupportFiles\Launch 2802 returns to the ship.jpg</ns2:link></ns1:images><ns1:discussion>All data for survey H12829 was acquired by NOAA Ship Rainier and its survey launches 2801 and 2803.  The vessels acquired MBES depth soundings, backscatter data, side scan sonar imagery, and sound speed profiles.</ns1:discussion><ns1:comments/></ns1:vessels><ns1:equipment><ns1:majorSystem><ns2:manufacturer>Applanix</ns2:manufacturer><ns2:model>POS M/V v4</ns2:model><ns2:type>Positioning and Attitude System</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>Applied Microsystems</ns2:manufacturer><ns2:model>MicroCTD</ns2:model><ns2:type>Conductivity, Temperature, and Depth Sensor</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>Odim Brooke Ocean</ns2:manufacturer><ns2:model>Moving Vessel Profiler 200</ns2:model><ns2:type>Sound Speed System</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>Seabird</ns2:manufacturer><ns2:model>SBE 19 and 19Plus V2 SeaCAT Profiler</ns2:model><ns2:type>Conductivity, Temperature, and Depth Sensor</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>Reson</ns2:manufacturer><ns2:model>SVP71</ns2:model><ns2:type>Surface Sound Speed Probe</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>Reson</ns2:manufacturer><ns2:model>SVP70</ns2:model><ns2:type>Surface Sound Speed Probe</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>Edgetech</ns2:manufacturer><ns2:model>4200</ns2:model><ns2:type>SSS</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>Reson</ns2:manufacturer><ns2:model>Seabat 7125-B</ns2:model><ns2:type>MBES</ns2:type></ns1:majorSystem><ns1:discussion xsi:nil="true"></ns1:discussion><ns1:comments/></ns1:equipment><ns1:comments/></ns1:equipmentAndVessels><ns1:qualityControl><ns1:crosslines><ns2:discussion>Multibeam crosslines were acquired using Rainier launch 2803.  A 1-meter CUBE surface was created using only H12829 mainscheme lines and a second 1-meter surface was created using only crosslines.  A 1-meter difference surface was then generated in CARIS from which statistics were derived.  The difference surface was compared to the IHO allowable total vertical uncertainty (TVU) standards.  In total 99.999% of the depth differences between H12829 ERZT mainscheme and crossline data met HSSD TVU standards (Figure 15).  This analysis was performed with final tides applied and reduced to MLLW using ERZT methods.

A mainscheme to crossline comparison between H12829 data reduced to MLLW using traditional TCARI methods and ERZT methods was conducted (Figure 16).  TCARI mainscheme to crossline data differed by an average of -0.026 meters with a standard deviation of 0.156 meters.  ERZT mainscheme to crossline data differed by an average of -0.02 meters with a standard deviation of 0.082 meters.</ns2:discussion><ns2:images><ns2:caption>Summary table indicating percentage of difference surface nodes between H12829 mainscheme and crossline data that met HSSD allowable TVU standards.</ns2:caption><ns2:link>SupportFiles\Crossline statistics_ERZT.png</ns2:link></ns2:images><ns2:images><ns2:caption>H12829 mainscheme to crossline comparison statistics using TCARI (left) and ERZT (right) methods.</ns2:caption><ns2:link>SupportFiles\TCARI vs ERZT stats.jpg</ns2:link></ns2:images><ns2:comments/></ns1:crosslines><ns1:uncertainty><ns2:values><ns2:tideUncertainty><ns2:measured units="meters">0.030398</ns2:measured><ns2:zoning units="meters">0</ns2:zoning><ns2:tideMethod>ERZT</ns2:tideMethod></ns2:tideUncertainty><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">0.05</ns2:surface></ns2:soundSpeedUncertainty><ns2:soundSpeedUncertainty><ns2:hullID>2801, 2803</ns2:hullID><ns2:measuredCTD units="meters/second">3</ns2:measuredCTD><ns2:measuredMVP xsi:nil="true"/><ns2:surface units="meters/second">0.15</ns2:surface></ns2:soundSpeedUncertainty></ns2:values><ns2:discussion>Total Propagated Uncertainty (TPU) values for H12829 were derived from a combination of fixed values for equipment and vessel characteristics, as well as field assigned values for sound speed uncertainties.  Tidal uncertainties were accounted for by examining the created 1000 meters separation model and statistically determining a measured uncertainty. The measured tide uncertainty value of 0.030398 meters was entered to account for ERZT processing methods.  See the OPR-S327-RA-15 ERZT memo included in Supplemental Correspondence for further information.

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

Uncertainty values of submitted finalized grids were calculated in Caris using the &quot;Greater of the Two&quot; of uncertainty and standard deviation (scaled to 95%).  The surfaces were analyzed using the Pydro Finalized CSAR Surface IHO Compliance showing &gt;99.9% of the nodes met HSSD uncertainty requirements (Figure 17).

</ns2:discussion><ns2:images><ns2:caption>Pydro derived histogram plot showing HSSD uncertainty standards compliance of H12829 MBES data.</ns2:caption><ns2:link>SupportFiles\uncertainty standards.png</ns2:link></ns2:images><ns2:comments><ns2:branchComment concurrence="Comment Only"><ns2:comment>See attached ERZT Capability Memo.</ns2:comment></ns2:branchComment></ns2:comments></ns1:uncertainty><ns1:junctions><ns2:discussion>H12829 junctions with two other surveys which were part of the same project.  H12830 lies to the west of this survey and was conducted by NOAA Ship Fairweather.  Sheet 12827 lies to the east and was conducted by NOAA Ship Rainier.  </ns2:discussion><ns2:junction><ns2:survey><ns2:registryNumber>H12830</ns2:registryNumber><ns2:scale>40000</ns2:scale><ns2:year>2015</ns2:year><ns2:fieldUnit>NOAA Ship FAIRWEATHER</ns2:fieldUnit><ns2:relativeLocation>W</ns2:relativeLocation></ns2:survey><ns2:discussion>Junction analysis will be completed at the Pacific Hydrographic Branch.</ns2:discussion><ns2:comments><ns2:branchComment concurrence="Comment Only"><ns2:comment>The junction analysis between H12830 and H12829 has been completed during office review. The two surveys junction very well, with a mean surface difference of 0.02m and a 2-sigma std dev of 0.2m. This junction covers a depth range of 12.4m to 19.5m.</ns2:comment></ns2:branchComment></ns2:comments></ns2:junction><ns2:junction><ns2:survey><ns2:registryNumber>H12827</ns2:registryNumber><ns2:scale>40000</ns2:scale><ns2:year>2015</ns2:year><ns2:fieldUnit>NOAA Ship RAINIER</ns2:fieldUnit><ns2:relativeLocation>E</ns2:relativeLocation></ns2:survey><ns2:discussion>Details related to the junction comparison made with this sheet are contained in the descriptive report for H12827.  </ns2:discussion><ns2:comments><ns2:branchComment concurrence="Concur"><ns2:comment>From the H12827 DR: Overlap with survey H12829 was approximately 660 meters wide along the western boundary of H12827. Depths in the junction area range from 8.0 to 23.6 meters. For the respective depths, the 2-meter difference surface was compared to the allowable TVU standards specified in the HSSD. Analysis of the 2-meter difference surface indicated a mean difference of -0.005 meters with a standard deviation of 0.166 meters. In total, 99.5% of the depth differences between H12827 and junction survey H12829 are within allowable uncertainties.

These results were confirmed during the survey review for H12829.</ns2:comment></ns2:branchComment></ns2:comments></ns2:junction><ns2:comments/></ns1:junctions><ns1:sonarQCChecks><ns2:results deviation="true"><ns2:discussion>Ice scours present in the survey area were utilized to periodically assess effectiveness of SSS imagery during acquisition in an effort to comply with HSSD confidence check requirements.  Effective swath coverage was noted in acquisition logs.</ns2:discussion></ns2:results><ns2:comments/></ns1:sonarQCChecks><ns1:equipmentEffectiveness><ns2:results deviation="true"><ns2:issue><ns2:title>Side Scan Navigation Data</ns2:title><ns2:discussion>Errors in SSS heading, velocity, speed, and navigation data were prolific throughout the survey in ship (S221) towed data and created &quot;smeared&quot; regions in the SSS mosaic.  The source of these errors is unknown.  Due to the large number of these errors, they have not been edited from the data (see Appendix II, Supplemental Survey Records &amp; Correspondence document &quot;Proceeding on RA Kotzebue Surveys.pdf&quot;).  These errors only affect the appearance and quality of the mosaic; all SSS data were examined in SIPS to ensure that all significant contacts were detected.  Very few contacts were detected throughout this survey, and where contacts were found, navigation data were examined to ensure that an accurate position was calculated for each contact.  Refraction affecting the quality of the outer edges of the SSS range scale was also frequent throughout the SSS data and is detailed further in B.2.6 Factors Affecting Soundings.</ns2:discussion><ns2:comments/></ns2:issue></ns2:results><ns2:comments><ns2:branchComment concurrence="Do not concur"><ns2:comment>Despite this report, the final mosaic submitted to the branch contained no such navigational errors and met the survey requirements where collected.</ns2:comment></ns2:branchComment></ns2:comments></ns1:equipmentEffectiveness><ns1:factorsAffectingSoundings><ns2:results deviation="true"><ns2:issue><ns2:title>Side Scan Sonar Refraction</ns2:title><ns2:discussion>The presence of a strong pycnocline (a marked difference in water density) sometimes caused refraction of side scan sonar imagery, reducing the effective range of SSS data for object detection.  The SSS was adjusted in height as needed to minimize the refraction and adjacent lines were examined to determine appropriate quality overlap. </ns2:discussion><ns2:comments/></ns2:issue></ns2:results><ns2:comments/></ns1:factorsAffectingSoundings><ns1:soundSpeedMethods><ns1:castFrequency>Sound speed profiles were acquired on Rainier's launches using SBE 19plus CTD probes at discrete locations within the survey area at least once every four hours, when significant changes in surface sound speed were observed, or when surveying in a new area.  For operations conducted on S221 (Rainier), sound speed profiles were acquired using the Rolls Royce MVP200 approximately every fifteen minutes, when SIS indicated the surface sound speed varied from the previous cast by &gt; 5.0m/s or when recommended by &quot;Cast Time,&quot; a cast frequency program developed at the University of New Hampshire.  Ninety six MVP and CTD casts were concatenated into a master file and applied to H12829 MBES data using the &quot;Nearest in distance within time (4 hours)&quot; profile selection method.  </ns1:castFrequency><ns1:discussion xsi:nil="true"></ns1:discussion><ns1:comments/></ns1:soundSpeedMethods><ns1:coverageEquipmentAndMethods><ns2:results deviation="false"><ns2:discussion>All equipment and survey methods were used as detailed in the DAPR.</ns2:discussion></ns2:results><ns2:comments/></ns1:coverageEquipmentAndMethods><ns1:additionalQualityControl><ns2:comments/></ns1:additionalQualityControl></ns1:qualityControl><ns1:echoSoundingCorrections><ns1:corrections><ns2:results deviation="false"><ns2:discussion>All data reduction procedures conform to those detailed in the DAPR.</ns2:discussion></ns2:results><ns2:comments/></ns1:corrections><ns1:calibrations><ns2:results deviation="false"><ns2:discussion>All sounding systems were calibrated as detailed in the DAPR.</ns2:discussion><ns2:calibration xsi:nil="true"/></ns2:results><ns2:comments/></ns1:calibrations><ns1:additionalIssues><ns2:comments/></ns1:additionalIssues></ns1:echoSoundingCorrections><ns1:backscatter><ns2:results acquired="true"><ns2:discussion>MBES backscatter data, logged as .7k files for launch acquired data and .ALL for ship acquired data, was acquired but not formally processed by Rainier personnel.  Sample backscatter lines were reviewed on Rainier for quality control purposes.  The data was submitted directly to the National Centers for Environmental Information (NCEI).</ns2:discussion></ns2:results><ns2:comments/></ns1:backscatter><ns1:dataProcessing><ns1:drSoftware><ns1:bathySoftware deviation="true"><ns1:manufacturer>Caris</ns1:manufacturer><ns1:name>HIPS/SIPS</ns1:name><ns1:version>9.0.19</ns1:version></ns1:bathySoftware><ns1:imagerySoftware deviation="true"><ns1:manufacturer>Caris</ns1:manufacturer><ns1:name>HIPS/SIPS</ns1:name><ns1:version>9.0.19</ns1:version></ns1:imagerySoftware><ns1:featureObjectCatalog>NOAA Profile V_5_3_3</ns1:featureObjectCatalog><ns1:discussion xsi:nil="true"></ns1:discussion><ns1:comments/></ns1:drSoftware><ns1:surfaces><ns1:surface><ns2:surfaceName>H12829_MB_1m_MLLW</ns2:surfaceName><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:resolution units="meters">1</ns2:resolution><ns2:depthRange><ns2:min units="meters">3.57</ns2:min><ns2:max units="meters">24.32</ns2:max></ns2:depthRange><ns2:surfaceParameter>NOAA_1m</ns2:surfaceParameter><ns2:purpose>SSS with Concurrent MBES</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceName>H12829_MB_1m_MLLW_FINAL</ns2:surfaceName><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:resolution units="meters">1</ns2:resolution><ns2:depthRange><ns2:min units="meters">3.57</ns2:min><ns2:max units="meters">20.0</ns2:max></ns2:depthRange><ns2:surfaceParameter>NOAA_1m</ns2:surfaceParameter><ns2:purpose>SSS with Concurrent MBES</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceName>H12829_MB_2m_MLLW</ns2:surfaceName><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:resolution units="meters">2</ns2:resolution><ns2:depthRange><ns2:min units="meters">3.38</ns2:min><ns2:max units="meters">24.31</ns2:max></ns2:depthRange><ns2:surfaceParameter>NOAA_2m</ns2:surfaceParameter><ns2:purpose>SSS with Concurrent MBES</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceName>H12829_MB_2m_MLLW_FINAL</ns2:surfaceName><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:resolution units="meters">2</ns2:resolution><ns2:depthRange><ns2:min units="meters">18.0</ns2:min><ns2:max units="meters">24.31</ns2:max></ns2:depthRange><ns2:surfaceParameter>NOAA_2m</ns2:surfaceParameter><ns2:purpose>SSS with Concurrent MBES</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceName>H12829_SSS_Mosaic</ns2:surfaceName><ns2:surfaceType>SSS Mosaic</ns2:surfaceType><ns2:resolution units="meters">1</ns2:resolution><ns2:depthRange><ns2:min units="meters">0.0</ns2:min><ns2:max units="meters">25.0</ns2:max></ns2:depthRange><ns2:surfaceParameter>N/A</ns2:surfaceParameter><ns2:purpose>100% SSS</ns2:purpose></ns1:surface><ns1:discussion>All Caris CUBE surfaces  were created with lines reduced to MLLW via ERZT methods except as noted below.  Lines 0034_20150807_105548_Rainier and 0000_20150808_000831_Rainier were excluded from all surfaces due to their designation as ERS holidays.  Additional details are included in the &quot;H12829 H12821 H12820 ERS ERZT Report.pdf&quot; in the supplemental correspondence folder and in the Vertical and Horizontal Control section of this report.  No soundings were designated for this survey.</ns1:discussion><ns1:comments><ns2:branchComment concurrence="Comment Only"><ns2:comment>See attached ERZT Capability Memo.</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>ERZT</ns2:methodsUsed><ns2:tideStations><ns2:NWLONGauges><ns2:stationName>Red Dog Dock</ns2:stationName><ns2:stationID>9491094</ns2:stationID></ns2:NWLONGauges><ns2:subordinateGauges><ns2:stationName>Kotzebue</ns2:stationName><ns2:stationID>9490424</ns2:stationID></ns2:subordinateGauges><ns2:subordinateGauges><ns2:stationName>Good Hope Bay</ns2:stationName><ns2:stationID>9469833</ns2:stationID></ns2:subordinateGauges></ns2:tideStations><ns2:correctorFiles><ns2:waterLevels><ns2:fileName>9469833</ns2:fileName><ns2:status>Final Approved</ns2:status></ns2:waterLevels><ns2:waterLevels><ns2:fileName>9490424</ns2:fileName><ns2:status>Final Approved</ns2:status></ns2:waterLevels><ns2:waterLevels><ns2:fileName>9491094</ns2:fileName><ns2:status>Final Approved</ns2:status></ns2:waterLevels><ns2:tideCorrectors><ns2:fileName>S327FARA2015_Final.tc</ns2:fileName><ns2:status>Final</ns2:status></ns2:tideCorrectors></ns2:correctorFiles><ns2:finalTides><ns2:dateSubmitted>2015-09-03</ns2:dateSubmitted><ns2:dateReceived>2016-01-28</ns2:dateReceived></ns2:finalTides><ns2:discussion xsi:nil="true"></ns2:discussion><ns2:comments><ns2:branchComment concurrence="Comment Only"><ns2:comment>See attached Tide Note dated January 28, 2016.</ns2:comment></ns2:branchComment></ns2:comments></ns2:standard_or_ERZT><ns2:VDATUM_or_constantSep used="true"><ns2:ellipsoidToChartDatumSepFile><ns2:fileName>H12829_Ellipse-to-MLLW_Separation_Model_1000m_PostInterp2.csar</ns2:fileName></ns2:ellipsoidToChartDatumSepFile><ns2:discussion>Ellipsoidally Referenced Zoned Tides (ERZT) methods were used to transform between the ellipsoid and water level data.  A 1000-meter resolution separation model between the ellipsoid and MLLW was computed using real-time position measurements observed during the survey relative to the water line and the load TCARI tide file.  &quot;GPS tides&quot; were then computed using the above separation model and the corrected GPS-height-to-water level data (SBET).  For additional information see &quot;H12829 H12821 H12820 ERS ERZT Report.pdf&quot; in the supplemental correspondence folder .  

The 1000 meter resolution separation model excluded line 0034_20150807_105548_Rainier due to issues with the SBET offsets and difficulties in interpolation.  </ns2:discussion><ns2:comments><ns2:branchComment concurrence="Comment Only"><ns2:comment>See attached ERZT Capability Memo.</ns2:comment></ns2:branchComment></ns2:comments></ns2:VDATUM_or_constantSep><ns2:comments/></ns1:verticalControl><ns1:horizontalControl><ns2:horizontalDatum>North American Datum of 1983 (NAD83)</ns2:horizontalDatum><ns2:projection>Universal Transverse Mercator (UTM) Zone 3 North.</ns2:projection><ns2:PPK used="true"><ns2:methodsUsed>Single Base</ns2:methodsUsed><ns2:baseStations><ns2:userInstalledStations><ns2:HVCRSiteID>9715</ns2:HVCRSiteID><ns2:stationID>Tern Tower</ns2:stationID></ns2:userInstalledStations><ns2:userInstalledStations><ns2:HVCRSiteID>1066</ns2:HVCRSiteID><ns2:stationID>Bear Nestity</ns2:stationID></ns2:userInstalledStations><ns2:userInstalledStations><ns2:HVCRSiteID>9677</ns2:HVCRSiteID><ns2:stationID>Ernie</ns2:stationID></ns2:userInstalledStations></ns2:baseStations><ns2:discussion>Vessel kinematic data (POS files) were post-processed with Applanix POSPac and POSGNSS software using Single Base processing methods described in the DAPR. SBET and RMS data was applied to all survey lines.  Line 0025_20150807_034959 had a gap in the Delayed Heave file which prevented application of the file in accordance with the DAPR.  The Maximum Allowable Gap was changed to seven seconds during application which permitted Delayed Heave to be applied to the line.   This error propagated into the SBET and RMS files necessitating creation of two SBET and RMS files to cover the timespan.  A thirty second Maximum Allowable Gap was necessary to apply the SBET and RMS files to the line.  A change to the Output Rate for the RMS file was also necessary to 1.0173.

All SBETs were exported in WGS84 and applied to lines.  Surfaces were created in NAD83.  Further details are included in &quot;H12829 H12821 H12820 ERS ERZT Report.pdf&quot; in the supplemental correspondence folder.
</ns2:discussion><ns2:comments><ns2:branchComment concurrence="Comment Only"><ns2:comment>See attached ERZT Capability Memo.</ns2:comment></ns2:branchComment></ns2:comments></ns2:PPK><ns2:PPP used="false" xsi:nil="true"/><ns2:RTK used="false" xsi:nil="true"/><ns2:DGPS used="false" xsi:nil="true"/><ns2:comments/></ns1:horizontalControl><ns1:additionalIssues><ns2:issue><ns2:title>SBET Interpolation</ns2:title><ns2:discussion>SBETs were examined through comparison of a 100 meter resolution separation model, ERS-to-MLLW difference surface, and visual inspection of surfaces.  Lines with vertical offsets were further examined in the Pydro POSPac Automated QC tool.  Large time spans of up to an hour on SBETs for DN 218 and DN 219 had vertical offsets of up to 1 meter.  These areas were examined, interpolated, and exported in the AutoQC tool.  Lines 0013_20150806_141721_Rainier, 0012_2015_0806_131721_Rainier, 0038_20150807_141649_Rainier, 0039_20150807_151649_Rainier, 0009_20150806_112336_Rainier, and 0010_20150806121044_Rainier were impacted by the interpolation.  

Line 0034_20150807_105548_Rainier was also identified as a candidate for interpolation however, upon examination in Pydro's POSPac AutoQC tool, it was determined that interpolation would not be possible for this line (Figure 18).  Application of the SBET for Line 0000_20150808_000831_Rainier resulted in a significant horizontal offset.  Attempts to resolve the issue were unsucessful.  The SBET was removed and the horizontal offset was eliminated.</ns2:discussion><ns2:images><ns2:caption>Line 0034_20150807_105548_Rainier SBET both pre and post interpolation shows similar results.</ns2:caption><ns2:link>SupportFiles\Bad sbet interp.png</ns2:link></ns2:images><ns2:comments><ns2:branchComment concurrence="Comment Only"><ns2:comment>The data is adequate for charting despite the use of interpolated SBETs.</ns2:comment></ns2:branchComment></ns2:comments></ns2:issue><ns2:comments/></ns1:additionalIssues></ns1:verticalAndHorizontalControl><ns1:resultsAndRecommendations><ns1:chartComparison><ns1:methods><ns2:discussion>A comparison was made between H12829 survey data, ENC US2AK92M, ENC US1AK90M, and Chart 16005 using a Caris CUBE surface and selected soundings.</ns2:discussion><ns2:comments/></ns1:methods><ns1:charts><ns2:rasterChart><ns2:chart><ns2:number>16005</ns2:number><ns2:kapp>1</ns2:kapp><ns2:scale>700000</ns2:scale><ns2:edition>11</ns2:edition><ns2:editionDate>2015-05</ns2:editionDate><ns2:LNMDate>2015-11-25</ns2:LNMDate><ns2:NMDate>2015-11-25</ns2:NMDate></ns2:chart><ns2:discussion>H12829 sounding data coincides with two charted depths as shown in Figure 19.  H12829 soundings agree to within two fathoms over the 9 fathom depth and to within three fathoms over the charted 13 fathom depth.

The 10 fathom depth contour identified by H12829 data was located between 800m and 2450m north (offshore) of the currently charted position (Figure 20).</ns2:discussion><ns2:images><ns2:caption>H12829 Soundings overlaid with Chart 16005.  (ENC US2AK92M depths circled in blue)</ns2:caption><ns2:link>SupportFiles\Sounding to Charted Depth.png</ns2:link></ns2:images><ns2:images><ns2:caption>Location of H12829 10 fathom depth contour to the north of charted (16005) position</ns2:caption><ns2:link>SupportFiles\Contour line offsets.png</ns2:link></ns2:images><ns2:comments/></ns2:rasterChart><ns2:ENC><ns2:chart><ns2:name>US2AK92M</ns2:name><ns2:scale>700000</ns2:scale><ns2:edition>7</ns2:edition><ns2:updateApplicationDate>2011-05-02</ns2:updateApplicationDate><ns2:issueDate>2014-11-13</ns2:issueDate><ns2:preliminary>false</ns2:preliminary></ns2:chart><ns2:discussion>In the area of survey H12829, Electronic Navigation Chart (ENC) US2AK92M coincides with Chart 16005, therefore a comparison between H12829 and US2AK92M is equivalent to the preceding comparison with Chart 16005.</ns2:discussion><ns2:comments/></ns2:ENC><ns2:ENC><ns2:chart><ns2:name>US1AK90M</ns2:name><ns2:scale>1587870</ns2:scale><ns2:edition>10</ns2:edition><ns2:updateApplicationDate>2015-03-08</ns2:updateApplicationDate><ns2:issueDate>2015-03-08</ns2:issueDate><ns2:preliminary>false</ns2:preliminary></ns2:chart><ns2:discussion>An offset between ENS US1AK90M and both Chart 16005 and ENC US2AK92M of approximately 750 meters was observed (Figure 21).  Only one sounding on ENC US1AK90M existed in the survey.  H12829 soundings agreed to within  1 1/2  fathoms on the 9 fathom depth on ENC US1AK90M.

The 10 fathom depth contour identified by H12829 data had some overlap with the 10 fathom contour on US1AK90M (Figure 22).  Separation between the two contours differed by a range of 0 m to 1200 m with the data from H12829 residing further to the north (offshore) than US1AK90M.</ns2:discussion><ns2:images><ns2:caption>Separation between soundings on Chart 16005, ENC US2AK92M, and ENC US1AK90M.</ns2:caption><ns2:link>SupportFiles\ENC sounding offset.png</ns2:link></ns2:images><ns2:images><ns2:caption>Comparison of ENC US1AK90M 10 fathom depth contour to H12829 10 fathom contour.</ns2:caption><ns2:link>SupportFiles\US1AK90M contour.png</ns2:link></ns2:images><ns2:comments/></ns2:ENC><ns2:comments/></ns1:charts><ns1:maritimeBoundary><ns2:results investigated="None Exist"><ns2:discussion>No Maritime Boundary Points were assigned for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:maritimeBoundary><ns1:chartedFeatures><ns2:results investigated="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>One bottom sample was acquired for this survey and is detailed in the Final Features File accompanying this report.  A second assigned bottom sample was not acquired due to an earlier than anticipated departure from the project area.</ns2:discussion></ns2:results><ns2:comments><ns2:branchComment concurrence="Comment Only"><ns2:comment>The final feature file is not appended to this report.</ns2:comment></ns2:branchComment></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="Exist - Not Investigated"><ns2:discussion>Several side scan sonar contacts were identified but not investigated due to an ordered earlier than scheduled departure from the project area.  Ice scours were common throughout the survey area.</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="true"><ns2:discussion>Further investigation of the SSS contacts detailed in the H12829_Contacts.hob file is recommended.</ns2:discussion></ns2:results><ns2:comments><ns2:branchComment concurrence="Comment Only"><ns2:comment>The  H12829_Contacts.hob file is not appended to this report.</ns2:comment></ns2:branchComment></ns2:comments></ns1:newSurveyRecommendation><ns1:insetRecommendation><ns2:results recommended="false"><ns2:discussion>No new insets are recommended for this area.</ns2:discussion></ns2:results><ns2:comments/></ns1:insetRecommendation></ns1:additionalResults></ns1:resultsAndRecommendations><ns1:approvalSheet><ns1:statements><ns1:supervision>As Chief of Party, field operations for this hydrographic survey were conducted under my direct supervision, with frequent personal checks of progress and adequacy. I have reviewed the attached survey data and reports.</ns1:supervision><ns1:approval>All field sheets, this Descriptive Report, and all accompanying records and data are approved. All records are forwarded for final review and processing to the Processing Branch.</ns1:approval><ns1:adequacyOfSurvey>The survey data meets or exceeds requirements as set forth in the NOS Hydrographic Surveys and Specifications Deliverables Manual, Field Procedures Manual, Letter Instructions, and all HSD Technical Directives. These data are adequate to supersede charted data in their common areas. This survey is complete and no additional work is required with the exception of deficiencies noted in the Descriptive Report.</ns1:adequacyOfSurvey><ns1:additionalInfo xsi:nil="true"></ns1:additionalInfo></ns1:statements><ns1:signingPersonnel><ns2:approverName>Edward J. Van Den Ameele, CDR/NOAA</ns2:approverName><ns2:approverTitle>Commanding Officer, NOAA Ship Rainier</ns2:approverTitle><ns2:approvalDate>2016-07-14</ns2:approvalDate></ns1:signingPersonnel><ns1:signingPersonnel><ns2:approverName>Steven Loy, LT/NOAA</ns2:approverName><ns2:approverTitle>Field Operations Officer, NOAA Ship Rainier</ns2:approverTitle><ns2:approvalDate>2016-07-14</ns2:approvalDate></ns1:signingPersonnel><ns1:signingPersonnel><ns2:approverName>James B. Jacobson</ns2:approverName><ns2:approverTitle>Chief Survey Technician, NOAA Ship Rainier</ns2:approverTitle><ns2:approvalDate>2016-07-14</ns2:approvalDate></ns1:signingPersonnel><ns1:signingPersonnel><ns2:approverName>Christopher M. Wood</ns2:approverName><ns2:approverTitle>Junior Officer, NOAA Ship Rainier</ns2:approverTitle><ns2:approvalDate>2016-07-14</ns2:approvalDate></ns1:signingPersonnel></ns1:approvalSheet></ns1:descriptiveReport>