<?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-P377-RA-14</ns2:number><ns2:name>Southern Alaska Peninsula, AK</ns2:name><ns2:generalLocality>Southern Alaska Peninsula, AK</ns2:generalLocality><ns2:fieldUnit>NOAA Ship Rainier</ns2:fieldUnit></ns1:projectMetadata><ns1:registryMetadata><ns2:registryNumber>H12662</ns2:registryNumber><ns2:sheetID>1</ns2:sheetID><ns2:registryInstructions xsi:nil="true"></ns2:registryInstructions><ns2:sublocality>Delta Pt Lagoon to Lenard Harbor</ns2:sublocality><ns2:stateOrTerritory>Alaska</ns2:stateOrTerritory><ns2:country>United States</ns2:country><ns2:scale>40000</ns2:scale></ns1:registryMetadata><ns1:surveyMetadata><ns2:year>2014</ns2:year><ns2:chiefOfParty>Edward J. Van Den Ameele, CDR/NOAA</ns2:chiefOfParty><ns2:projectType>Navigable Area</ns2:projectType><ns2:PIDate>2014-04-18</ns2:PIDate><ns2:datesOfSurvey><ns2:start>2013-08-24</ns2:start><ns2:end>2014-07-21</ns2:end></ns2:datesOfSurvey><ns2:equipmentTypes><ns2:soundingEquipment>Multibeam Echo Sounder</ns2:soundingEquipment><ns2:imageryEquipment>Multibeam Echo Sounder Backscatter</ns2:imageryEquipment></ns2:equipmentTypes><ns2:acquisition><ns2:units>meters</ns2:units></ns2:acquisition><ns2:horizontalCoordinateSystem zone="3">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>This survey is located in Cold Bay on the southwest Alaskan Peninsula.  The area surveyed extends from Delta Point Lagoon to Lenard Harbor; it encompasses an area of approximately 25 square nautical miles (Figures 1-2).</ns2:discussion><ns2:limits><ns2:northWest><ns2:latitude hemisphere="N">55.219</ns2:latitude><ns2:longitude hemisphere="W">162.6665</ns2:longitude></ns2:northWest><ns2:southEast><ns2:latitude hemisphere="N">55.0960277778</ns2:latitude><ns2:longitude hemisphere="W">162.362888889</ns2:longitude></ns2:southEast></ns2:limits><ns2:images><ns2:caption>Overview of H12662 survey area (Chart 16011).</ns2:caption><ns2:link>SupportFiles\Overview.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>H12662 survey outline and assigned sheet limits overlaid on Chart 16549.</ns2:caption><ns2:link>SupportFiles\H12662_Survey_Outline.jpg</ns2:link></ns2:images><ns2:comments/></ns1:areaDescription><ns1:surveyLimits><ns2:results deviation="true"><ns2:discussion>NOAA Hydrographic Survey Division (HSD) approved a Rainier request to waive the 4 meter inshore limit requirement for this survey.  For specifics, refer to supplemental correspondence &quot;Cold Bay Inshore Coverage - H12662.pdf&quot; submitted with this report.
</ns2:discussion></ns2:results><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.  </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 H12662 met complete multibeam echosounder (MBES) coverage requirements, including the 5 soundings per node data density requirement.  In order to extract statistics of the data density achieved, the density layer of each finalized surface was queried within CARIS then examined in Excel.  Overall, the required data density was achieved in 99.976% of nodes (Figures 3-4).</ns2:discussion><ns2:images><ns2:caption>H12662 data density.</ns2:caption><ns2:link>SupportFiles\H12662_Density_with_legend.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>Summary table showing the percentage of nodes satisfying the 5 soundings density requirement, sub-divided by appropriate ranges.  </ns2:caption><ns2:link>SupportFiles\H12662_Density_Stats_MoreDecimalPts_crop.jpg</ns2:link></ns2:images><ns2:comments/></ns1:surveyQuality><ns1:surveyCoverage><ns2:results deviation="true"><ns2:discussion>Complete multibeam echosounder coverage was achieved within the assigned survey area except as noted below.

Holidays: A scattering of small holidays, in most cases the result of inadequate line spacing, exist in H12662 survey coverage.  A representative area approximately one kilometer northwest of Kelp Point is shown in Figure 6.  The largest holiday in this area of low seafloor relief, measures approximately 2 x 33 meters.  All H12662 holidays were examined to ensure that no navigationally significant features were evident in the surrounding data. </ns2:discussion><ns2:images><ns2:caption>Area with holidays in survey coverage.  Largest holiday measures approximately 2 x 33 meters.</ns2:caption><ns2:link>SupportFiles\HolidayExample.jpg</ns2:link></ns2:images></ns2:results><ns2:comments><ns2:branchComment concurrence="Concur with clarification"><ns2:comment>Data is adequate for charting.</ns2:comment></ns2:branchComment></ns2:comments></ns1:surveyCoverage><ns1:coverageGraphic><ns2:caption>H12662 multibeam echo sounder coverage (Chart 16549).</ns2:caption><ns2:link>SupportFiles\H12662_Coverage.jpg</ns2:link></ns1:coverageGraphic><ns1:surveyStatistics><ns2:LNM><ns2:vesselLNM><ns2:vessel><ns2:hullID>S221</ns2:hullID><ns2:statistics><ns2:MS_SBES>0</ns2:MS_SBES><ns2:MS_MBES>48.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>2801</ns2:hullID><ns2:statistics><ns2:MS_SBES>0</ns2:MS_SBES><ns2:MS_MBES>169.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>208.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>2804</ns2:hullID><ns2:statistics><ns2:MS_SBES>0</ns2:MS_SBES><ns2:MS_MBES>225.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>26.9</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>651.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>26.9</ns2:XL_MBES_SBES><ns2:XL_lidar>0</ns2:XL_lidar><ns2:percentXLLNM>4.1</ns2:percentXLLNM></ns2:totalLNM></ns2:LNM><ns2:totalSurveyStats><ns2:bottomSamples>6</ns2:bottomSamples><ns2:AWOIS>0</ns2:AWOIS><ns2:maritimeBoundaryPoints>0</ns2:maritimeBoundaryPoints><ns2:DP>0</ns2:DP><ns2:diveOps>1</ns2:diveOps><ns2:SNM>24.75</ns2:SNM></ns2:totalSurveyStats><ns2:surveyDates>2013-08-24</ns2:surveyDates><ns2:surveyDates>2014-07-14</ns2:surveyDates><ns2:surveyDates>2014-07-15</ns2:surveyDates><ns2:surveyDates>2014-07-16</ns2:surveyDates><ns2:surveyDates>2014-07-17</ns2:surveyDates><ns2:surveyDates>2014-07-18</ns2:surveyDates><ns2:surveyDates>2014-07-19</ns2:surveyDates><ns2:surveyDates>2014-07-20</ns2:surveyDates><ns2:surveyDates>2014-07-21</ns2:surveyDates><ns2:surveyDates>2014-07-22</ns2:surveyDates><ns2:discussion>Shoreline data collection for H12662 was conducted by NOAA Ship Rainier personnel during the 2013 field season; at that time the survey designation was H12582.  Due to time constraints, no MBES data was acquired for H12582 in 2013.  In 2014, after modifying the southern sheet limits, NOAA HSD re-designated and reassigned survey H12582 as H12662. </ns2:discussion><ns2:comments/></ns1:surveyStatistics></ns1:areaSurveyed><ns1:dataAcquisitionAndProcessing><ns1:equipmentAndVessels><ns1:discussion>Refer to the Data Acquisition and Processing Report (DAPR) for a complete description of data acquisition and processing systems, survey vessels, quality control procedures and data processing methods.  Additional information to supplement sounding and survey data, and any deviations from the DAPR are discussed in the following sections.</ns1:discussion><ns1:vessels><ns1:vessel><ns2:hullID>S221</ns2:hullID><ns2:LOA units="meters">70.4</ns2:LOA><ns2:draft units="meters">4.7</ns2:draft></ns1:vessel><ns1:vessel><ns2:hullID>2801</ns2:hullID><ns2:LOA units="meters">8.8</ns2:LOA><ns2:draft units="meters">1.1</ns2:draft></ns1:vessel><ns1:vessel><ns2:hullID>2803</ns2:hullID><ns2:LOA units="meters">8.8</ns2:LOA><ns2:draft units="meters">1.1</ns2:draft></ns1:vessel><ns1:vessel><ns2:hullID>2804</ns2:hullID><ns2:LOA units="meters">8.8</ns2:LOA><ns2:draft units="meters">1.1</ns2:draft></ns1:vessel><ns1:vessel><ns2:hullID>1905</ns2:hullID><ns2:LOA units="meters">5.7</ns2:LOA><ns2:draft units="meters">0.3</ns2:draft></ns1:vessel><ns1:images><ns2:caption>NOAA Ship Rainier with survey launches on board.</ns2:caption><ns2:link>SupportFiles\NOAA_Ship_Rainier.jpg</ns2:link></ns1:images><ns1:discussion>All data for survey H12662 was acquired by NOAA Ship Rainier and survey launches 2801, 2803, 2804 and skiff 1905.  The vessels acquired MBES depth soundings, sound speed profiles, bottom samples and conducted shoreline verification.</ns1:discussion><ns1:comments/></ns1:vessels><ns1:equipment><ns1:majorSystem><ns2:manufacturer>Applanix</ns2:manufacturer><ns2:model>POS MV v4</ns2:model><ns2:type>Positioning and Attitude System</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>Kongsberg</ns2:manufacturer><ns2:model>EM710</ns2:model><ns2:type>MBES</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>Reson</ns2:manufacturer><ns2:model>SeaBat 7125-B</ns2:model><ns2:type>MBES</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>Reson</ns2:manufacturer><ns2:model>SV2</ns2:model><ns2:type>MBES</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>Odim Brooke Ocean (Rolls Royce Group)</ns2:manufacturer><ns2:model>Moving Vessel Profiler 200</ns2:model><ns2:type>Conductivity, Temperature, and Depth Sensor</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>Reson</ns2:manufacturer><ns2:model>SVP71</ns2:model><ns2:type>Surface Sound Speed Probe</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>Sea-Bird Electronics</ns2:manufacturer><ns2:model>SBE 19plus SEACAT Profiler</ns2:model><ns2:type>Conductivity, Temperature, and Depth Sensor</ns2:type></ns1:majorSystem><ns1:discussion xsi:nil="true"></ns1:discussion><ns1:comments/></ns1:equipment><ns1:comments/></ns1:equipmentAndVessels><ns1:qualityControl><ns1:crosslines><ns2:discussion>Multibeam crosslines were acquired using Rainier Launch 2804 (RA-6).  A 2 meter CUBE surface was created using only H12662 mainscheme lines, and a second 2 meter surface was created using only crosslines.  A 2 meter difference surface was then generated in Caris from which statistics were derived.  For its respective depths, the difference surface was compared to the IHO allowable total vertical uncertainty (TVU) standards.   In total, 100.0% of the depth differences between H12662 mainscheme and crossline data were within HSSD TVU standards (Figures 8-9).</ns2:discussion><ns2:images><ns2:caption>Depth differences between H12662 mainscheme and crossline data as compared to allowable TVU accuracy standards for associated depths.  Mainscheme tracklines shown in gray.</ns2:caption><ns2:link>SupportFiles\XL_IHO_Compliance_2_with_revised_legend2.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>Summary table indicating percentage of difference surface nodes between H12662 mainscheme and crossline data that met HSSD TVU standards for associated depths.</ns2:caption><ns2:link>SupportFiles\Crossline_HSSD_TVU.jpg</ns2:link></ns2:images><ns2:comments/></ns1:crosslines><ns1:uncertainty><ns2:values><ns2:tideUncertainty><ns2:measured units="meters">0</ns2:measured><ns2:zoning units="meters">0.1</ns2:zoning></ns2:tideUncertainty><ns2:soundSpeedUncertainty><ns2:hullID>S221 (Rainier)</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, 2804</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>Uncertainty values were measured and applied in accordance with Section B.4 of the DAPR.

Uncertainty values of submitted finalized grids were calculated in Caris using the &quot;Greater of the Two&quot; of uncertainty and standard deviation (scaled to 95%).  To visualize where uncertainty requirements were met, for each surface a custom HSSD compliance layer was created, based on the difference between the calculated uncertainty of the nodes and the allowable uncertainty defined in the HSSD.  To quantify the extent to which requirements were met, the HSSD Compliance layers were queried within Caris and examined in Excel.  Overall, 99.898% of survey H12662 nodes met uncertainty requirements specified in NOAA HSSD.

</ns2:discussion><ns2:comments/></ns1:uncertainty><ns1:junctions><ns2:discussion>A junction comparison was conducted between H12662 and 2013 Rainier survey H12581 (Figure 10).</ns2:discussion><ns2:images><ns2:caption>H12662 / H12581 junction.</ns2:caption><ns2:link>SupportFiles\Junction.jpg</ns2:link></ns2:images><ns2:junction><ns2:survey><ns2:registryNumber>H12581</ns2:registryNumber><ns2:scale>40000</ns2:scale><ns2:year>2013</ns2:year><ns2:fieldUnit>NOAA Ship Rainier</ns2:fieldUnit><ns2:relativeLocation>N</ns2:relativeLocation></ns2:survey><ns2:discussion>The overlap with survey H12581 encompassed approximately 0.9 Square Int. Nautical Miles along the northern boundary of H12662.  A comparison was made using a difference surface derived from the 4 meter CUBE surfaces of each survey.  Analysis of the difference surface indicated that H12662 is an average of 0.09 meters deeper than H12581 with a standard deviation of 0.2 meters (Figure 11). For the respective depths, the difference surface was compared to the allowable TVU standards specified in the HSSD.  100.00% of the depth differences between H12662 and junction survey H12581 were within allowable uncertainties.</ns2:discussion><ns2:images><ns2:caption>Junction H12662 / H12581 difference surface.</ns2:caption><ns2:link>SupportFiles\H12662_Diff_H12581_Junction.jpg</ns2:link></ns2:images><ns2:comments><ns2:branchComment concurrence="Comment Only"><ns2:comment>Junctioning survey H12663 assigned in the same year was not completed as outlined in the Project Instructions due to issues encountered during the survey season which prevented data acquisition.  A junction comparison will be completed once the data has been acquired.</ns2:comment></ns2:branchComment></ns2:comments></ns2:junction><ns2:comments/></ns1:junctions><ns1:sonarQCChecks><ns2:results deviation="false"><ns2:discussion>Sonar system quality control checks were conducted as detailed in the quality control section of the DAPR.</ns2:discussion></ns2:results><ns2:comments/></ns1:sonarQCChecks><ns1:equipmentEffectiveness><ns2:results deviation="true"><ns2:issue><ns2:title>Reson SV2 Roll Issue</ns2:title><ns2:discussion>An equipment issue with the Reson SV2 sonar resulted in degradation of some H12662 bathymetric data (Figure 12).  High frequency lines 2321, 2338 and 2347 from DN201 on Launch 2804 (RA-6) were affected resulting in sounding deflection of approximately 0.15 meters and surface artifacts.  Affected data fell within NOAA HSSD standards.  Refer to the 2014 DAPR for more information regarding the issue.  </ns2:discussion><ns2:images><ns2:caption>Subset view of Reson SV2 acquired lines showing example of affected data (exaggerated 125x).</ns2:caption><ns2:link>SupportFiles\Roll_Timing_Issue_Location_with_inset_and_title.jpg</ns2:link></ns2:images><ns2:comments/></ns2:issue><ns2:issue><ns2:title>Application of SBET Data</ns2:title><ns2:discussion>Smoothed Best Estimate Trajectory (SBET) and Root Mean Square (RMS) data was applied to all H12662 survey lines with the following exception: Launch 2801 (RA-4), DN195 high frequency line 1803, did not load SBET data.  The acquisition log noted that an IMU failure occurred while logging this line.  The line shows no other anomalous characteristics and agrees well with adjoining data.
</ns2:discussion><ns2:comments/></ns2:issue></ns2:results><ns2:comments/></ns1:equipmentEffectiveness><ns1:factorsAffectingSoundings><ns2:results deviation="true"><ns2:issue><ns2:title>Vertical Offset</ns2:title><ns2:discussion>A vertical offset of approximately 0.25 meters was observed in the vicinity of Kelp Point (Figure 13).  In order to determine whether this offset was due to a less than accurate tidal zoning model, the affected multibeam data was referenced to the WGS-84 ellipsoid by applying GPS tides in Caris.  Once referenced to the ellipse, the vertical offset between overlapping lines was greatly reduced (Figures 14-15).  Strong currents were encountered in this area, therefore suboptimal dynamic draft modeling may have contributed to the observed offsets.  With zoned tides applied, H12662 multibeam data is within allowable vertical quality standards as outlined in NOAA 2014 HSSD.

Additional vertical offsets were observed in some areas where data was acquired by different vessels on different days and by the same vessel on different days (Figures 16-17).  The observed offsets range from approximately 0.15 to 0.30 meters.  Strong currents were not noticed in the vicinity of these offsets; application of GPS tide data did not eliminate the issue.  The source of the offsets are unknown but all affected MBES data falls within NOAA HSSD standards.

</ns2:discussion><ns2:images><ns2:caption>Section of H12662 1 meter surface showing artifacts caused by vertical offset. Note: surface exaggeration value of 10.
</ns2:caption><ns2:link>SupportFiles\VerticalOffsetArea_with_Inset_and_text.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>Example of vertical offset in subset view with final zoned tides applied. Data colored by line.</ns2:caption><ns2:link>SupportFiles\Final_Tides_Applied_text.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>Subset view of data with GPS tides applied, greatly reducing vertical offset.</ns2:caption><ns2:link>SupportFiles\GPS_Tides_Applied_text.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>Example areas of vertical offsets not eliminated with application of GPS tide data.  Vessel tracklines shown in green.</ns2:caption><ns2:link>SupportFiles\Vertical Offset Different Days_area_withtext.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>Subset view of 0.30 meter vertical offset and resulting CUBE surface artifact.</ns2:caption><ns2:link>SupportFiles\Vertical Offset Different Days.jpg</ns2:link></ns2:images><ns2:comments><ns2:branchComment concurrence="Comment Only"><ns2:comment>An additional vertical offset ranging between 0.45m-0.60m was found during office review (image below) which in some areas exceeds IHO vertical uncertainty limits by up to 6cm.  Despite not meeting IHO specifications, data is adequate to supersede charted data.</ns2:comment><ns2:images><ns2:caption>Vertical offset which exceeds IHO specifications by ~4cm at this particular depth</ns2:caption><ns2:link>file:///M:/OPRP377RA14/Surveys/H12662/Compilation/Report/Final/SupportFiles/VerticalOffset_ExceedIHO.jpg</ns2:link></ns2:images></ns2:branchComment></ns2:comments></ns2:issue><ns2:issue><ns2:title>Kelp</ns2:title><ns2:discussion>Kelp was encountered in shoal areas of the survey (Figure 18).  MBES data in these areas was examined using Caris subset editor; soundings that obviously represented kelp and not the seafloor, were rejected.  When unable to clearly distinguish between kelp and the seafloor, the soundings were retained.</ns2:discussion><ns2:images><ns2:caption>Subset view showing seafloor obscured by kelp and reference surface.</ns2:caption><ns2:link>SupportFiles\Kelp_Subset_with_text.jpg</ns2:link></ns2:images><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 a new area. 

For MBES operations conducted on S221 (Rainier), sound speed profiles were acquired using the Rolls Royce MVP200 approximately every 15 minutes or when recommended by &quot;Cast Time&quot;, a cast frequency program developed at the University of New Hampshire.  All casts were concatenated into a master file for either the launches or the ship, and applied to appropriate lines using the &quot;Nearest in distance within time (4 hours)&quot; profile selection method (Figure 19).
</ns1:castFrequency><ns1:discussion xsi:nil="true"></ns1:discussion><ns1:images><ns2:caption>H12662 sound speed cast locations.</ns2:caption><ns2:link>SupportFiles\H12662_CTD_Cast_Locations.jpg</ns2:link></ns1:images><ns1:comments/></ns1:soundSpeedMethods><ns1:coverageEquipmentAndMethods><ns2:results deviation="false"><ns2:discussion>All equipment and survey methods were used as detailed in the DAPR.</ns2:discussion></ns2:results><ns2:comments/></ns1:coverageEquipmentAndMethods><ns1:additionalQualityControl><ns2:issue><ns2:title>Outer Beam Deflection</ns2:title><ns2:discussion>An unusual downward deflection of outer beam soundings was observed in some H12662 MBES data (Figure 20).  The condition was present in data acquired with Reson 7125-B and SV2 model sonars.  The issue  resulted in artifacts visible in the delivered Caris CUBE surfaces.  To address this issue, outer beam soundings obviously in error were flagged as rejected in an attempt to produce surfaces that better represented the seafloor.  All examined offsets were found to be approximately 0.1 to 0.2 meters and within NOAA HSSD standards.  </ns2:discussion><ns2:images><ns2:caption>Example of H12662 outer beam deflection.
</ns2:caption><ns2:link>SupportFiles\H12662_SoundSpeed_Issue.jpg</ns2:link></ns2:images><ns2:comments/></ns2:issue><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, logged as .7k or .ALL files, was acquired but not formally processed by Rainier personnel.  Two backscatter lines per boat, per day were reviewed to ensure quality.  The data was submitted directly to the National Geophysical Data Center (NGDC).
</ns2:discussion></ns2:results><ns2:comments/></ns1:backscatter><ns1:dataProcessing><ns1:softwareUpdates><ns1:featureObjectCatalog>NOAA Profile V_5_3_2.</ns1:featureObjectCatalog><ns1:discussion xsi:nil="true"></ns1:discussion><ns1:comments/></ns1:softwareUpdates><ns1:surfaces><ns1:surface><ns2:surfaceName>H12662_MB_1m_MLLW</ns2:surfaceName><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:resolution units="meters">1</ns2:resolution><ns2:depthRange><ns2:min units="meters">2</ns2:min><ns2:max units="meters">133</ns2:max></ns2:depthRange><ns2:surfaceParameter>NOAA_1m</ns2:surfaceParameter><ns2:purpose>Complete MBES</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceName>H12662_MB_2m_MLLW</ns2:surfaceName><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:resolution units="meters">2</ns2:resolution><ns2:depthRange><ns2:min units="meters">2</ns2:min><ns2:max units="meters">133</ns2:max></ns2:depthRange><ns2:surfaceParameter>NOAA_2m</ns2:surfaceParameter><ns2:purpose>Complete MBES</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceName>H12662_MB_4m_MLLW</ns2:surfaceName><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:resolution units="meters">4</ns2:resolution><ns2:depthRange><ns2:min units="meters">2</ns2:min><ns2:max units="meters">133</ns2:max></ns2:depthRange><ns2:surfaceParameter>NOAA_4m</ns2:surfaceParameter><ns2:purpose>Complete MBES</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceName>H12662_MB_8m_MLLW</ns2:surfaceName><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:resolution units="meters">8</ns2:resolution><ns2:depthRange><ns2:min units="meters">2</ns2:min><ns2:max units="meters">133</ns2:max></ns2:depthRange><ns2:surfaceParameter>NOAA_8m</ns2:surfaceParameter><ns2:purpose>Complete MBES</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceName>H12662_MB_1m_MLLW_Final</ns2:surfaceName><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:resolution units="meters">1</ns2:resolution><ns2:depthRange><ns2:min units="meters">0</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>H12662_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</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>H12662_MB_4m_MLLW_Final</ns2:surfaceName><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:resolution units="meters">4</ns2:resolution><ns2:depthRange><ns2:min units="meters">36</ns2:min><ns2:max units="meters">80</ns2:max></ns2:depthRange><ns2:surfaceParameter>NOAA_4m</ns2:surfaceParameter><ns2:purpose>Complete MBES</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceName>H12662_MB_8m_MLLW_Final</ns2:surfaceName><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:resolution units="meters">8</ns2:resolution><ns2:depthRange><ns2:min units="meters">72</ns2:min><ns2:max units="meters">133</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/></ns1:surfaces><ns1:additionalDataProcessing><ns2:comments><ns2:branchComment concurrence="Concur"><ns2:comment>H12662_MB_8m_MLLW_Combined, created during office processing, was used for compilation.</ns2:comment></ns2:branchComment></ns2:comments></ns1:additionalDataProcessing></ns1:dataProcessing></ns1:dataAcquisitionAndProcessing><ns1:verticalAndHorizontalControl><ns1:discussion>Additional information regarding the vertical or horizontal control for this survey can be found in the accompanying OPR-P377-RA-14 Horizontal and Vertical Control Report (HVCR), submitted under a separate cover.</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>King Cove, AK (For 2013 features and 2014 MBES)</ns2:stationName><ns2:stationID>945-9881</ns2:stationID></ns2:NWLONGauges><ns2:NWLONGauges><ns2:stationName>Cold Bay, AK (For 2013 features only)</ns2:stationName><ns2:stationID>945-9949</ns2:stationID></ns2:NWLONGauges></ns2:tideStations><ns2:correctorFiles><ns2:waterLevels><ns2:fileName>9459881.tid </ns2:fileName><ns2:status>Final Approved</ns2:status></ns2:waterLevels><ns2:waterLevels><ns2:fileName>9459949.tid</ns2:fileName><ns2:status>Final Approved</ns2:status></ns2:waterLevels><ns2:tideCorrectors><ns2:fileName>P377RA2014CORP.zdf (for 2014 MBES) and H12581RevCORF.zdf (for 2013 shoreline features)</ns2:fileName><ns2:status>Final</ns2:status></ns2:tideCorrectors></ns2:correctorFiles><ns2:finalTides><ns2:dateSubmitted>2014-07-24</ns2:dateSubmitted><ns2:dateReceived>2014-08-05</ns2:dateReceived></ns2:finalTides><ns2:discussion>The NWLON gauge at King Cove, AK experienced gaps in data recording during the time of survey H12662.  Examination of H12662 MBES data acquired during the outage revealed no offsets greater than 0.12 meters.  For additional information regarding the King Cove outages, refer to the Horizontal and Vertical Control Report (HVCR) and Appendix 2, Supplemental Correspondence submitted with this report.  

H12662 MBES data was corrected using water level and zoning files listed above.  Shoreline feature data submitted with the H12662 Final Feature File were corrected using 2013 final approved water levels and zoning from 2013 survey H12581.  </ns2:discussion><ns2:comments/></ns2:standard_or_ERZT><ns2:VDATUM_or_constantSep used="false"><ns2:discussion xsi:nil="true"></ns2:discussion><ns2:comments/></ns2:VDATUM_or_constantSep><ns2:comments/></ns1:verticalControl><ns1:horizontalControl><ns2:horizontalDatum>North American Datum of 1983 (NAD83)</ns2:horizontalDatum><ns2:projection>Universal Transverse Mercator (UTM) Zone 03 North</ns2:projection><ns2:PPK used="true"><ns2:methodsUsed>Single Base</ns2:methodsUsed><ns2:baseStations><ns2:CORSStations><ns2:HVCRSiteID>BAY6</ns2:HVCRSiteID><ns2:stationID>COLD BAY 6 (Cold Bay, AK)</ns2:stationID></ns2:CORSStations></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 with one exception described in the Equipment Effectiveness section of this report.</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>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:comments/></ns1:additionalIssues></ns1:verticalAndHorizontalControl><ns1:resultsAndRecommendations><ns1:chartComparison><ns1:methods><ns2:discussion>A comparison was made between H12662 survey data and Chart 16549 using Caris CUBE surfaces, selected soundings and contours.   </ns2:discussion><ns2:comments/></ns1:methods><ns1:charts><ns2:rasterChart><ns2:chart><ns2:number>16549</ns2:number><ns2:kapp>2534</ns2:kapp><ns2:scale>80000</ns2:scale><ns2:edition>17</ns2:edition><ns2:editionDate>2014-06</ns2:editionDate><ns2:LNMDate>2014-08-05</ns2:LNMDate><ns2:NMDate>2014-07-26</ns2:NMDate></ns2:chart><ns2:discussion>H12662 soundings agreed with charted depths to within approximately one fathom except as follows: In Lenard Harbor, 16 fathom soundings were acquired over a 19 fathom charted depth in an area of sloping sea floor (Figure 21).  At the mouth of Lenard Harbor, near the southern shore, 4 fathom soundings were acquired over a 1-1/4 fathom charted depth (Figure 22).  

Contours generated in Caris and overlaid on Chart 16549, reveal no navigationally significant shoaling or deepening trends (Figures 23-24).</ns2:discussion><ns2:images><ns2:caption>Section of Chart 16549 with H12662 selected soundings overlaid in red.  Note the 16 fathom soundings over the 19 fathom charted depth.
</ns2:caption><ns2:link>SupportFiles\16over19.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>Section of Chart 16549 with H12662 selected soundings overlaid in red. Note the 4 fathom soundings over the 1-1/4 fathom charted depth.
</ns2:caption><ns2:link>SupportFiles\OneAndAQuarter.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>Chart 16549 overlaid with H12662 contours, west section.</ns2:caption><ns2:link>SupportFiles\Contours_2_with_Legend.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>Chart 16549 overlaid with H12662 contours, east section.</ns2:caption><ns2:link>SupportFiles\Contours_1_with_Legend.jpg</ns2:link></ns2:images><ns2:comments/></ns2:rasterChart><ns2:ENC><ns2:chart><ns2:name>US4AK55M</ns2:name><ns2:scale>80000</ns2:scale><ns2:edition>15</ns2:edition><ns2:updateApplicationDate>2011-03-25</ns2:updateApplicationDate><ns2:issueDate>2014-05-10</ns2:issueDate><ns2:preliminary>false</ns2:preliminary></ns2:chart><ns2:discussion>Electronic Navigation Chart (ENC) US4AK55M coincides with raster Chart 16549.  Navigation information contained on the ENC matches the raster, therefore a comparison between H12662 and the ENC is equivalent to the preceding comparison with Chart 16549.</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 that contain the label PA, ED, PD, or Rep exist for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:chartedFeatures><ns1:unchartedFeatures><ns2:results investigated="Investigated"><ns2:discussion>Two uncharted, non-dangerous wrecks were found within the survey area (Figures 25-26).  Rainier working divers investigated wreck 1 (Figure 25) to confirm that the least depth acquired with MBES was the shoalest point and that no masts or other features were missed.  The position and other information for both wrecks is attributed in the H12662 Final Feature File submitted with this report. </ns2:discussion><ns2:images><ns2:caption>H12662 wreck 1.</ns2:caption><ns2:link>SupportFiles\Wreck_1_B.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>H12662 Wreck 2.</ns2:caption><ns2:link>SupportFiles\Wreck_2_A.jpg</ns2:link></ns2:images></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 uncharted shoals or potentially hazardous features were located for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:shoalAndHazardousFeatures><ns1:channels><ns2:results investigated="Investigated"><ns2:discussion>Within the marked 10 fathom natural channel near Kelp Point, H12662 soundings agree with charted depths (Figure 27).</ns2:discussion><ns2:images><ns2:caption>Chart 16549 showing marked channel entrance to Cold Bay with H12662 soundings (in fathoms) overlaid in red.</ns2:caption><ns2:link>SupportFiles\H12662_Channel.jpg</ns2:link></ns2:images></ns2:results><ns2:comments/></ns1:channels><ns1:bottomSamples><ns2:results investigated="Investigated"><ns2:discussion>Six bottom samples were acquired for this survey; the findings are recored in the H12662 Final Feature File submitted with this report.</ns2:discussion></ns2:results><ns2:comments/></ns1:bottomSamples></ns1:chartComparison><ns1:additionalResults><ns1:shoreline><ns2:results investigated="Investigated"><ns2:discussion>Shoreline investigation results are contained within the H12662 Final Feature File submitted with this report.  Shoreline data was acquired during the 2013 field season for survey H12582.  Due to time constraints, no MBES data was acquired on H12582 in 2013.  In 2014, after modifying the southern sheet limits, NOAA HSD re-designated and reassigned survey H12582 as H12662.  Shoreline feature data submitted with this report was corrected with approved water levels and final zoning from 2013 survey H12581 which junctioned to the north of H12582.   Rather than submit H12582 feature data with survey H12581 as tentatively planned, the data was retained aboard Rainier and not submitted until H12662 was completed.</ns2:discussion></ns2:results><ns2:comments/></ns1:shoreline><ns1:priorSurveys><ns2:results investigated="None Exist"><ns2:discussion>No prior survey comparisons were performed for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:priorSurveys><ns1:ATONS><ns2:results investigated="Exist - Not Investigated"><ns2:discussion>One aid to navigation (ATON) is present in the survey area, but was not assigned for investigation.  It was observed in the field and appeared correctly charted and to be serving its intended purpose (Figure 28).</ns2:discussion><ns2:images><ns2:caption>H12662 aid to navigation.</ns2:caption><ns2:link>SupportFiles\H12662_ATON.JPG</ns2:link></ns2:images></ns2:results><ns2:comments/></ns1:ATONS><ns1:overheadFeatures><ns2:results investigated="None Exist"><ns2:discussion>No overhead features exist within the H12662 survey area.</ns2:discussion></ns2:results><ns2:comments/></ns1:overheadFeatures><ns1:submarineFeatures><ns2:results investigated="Investigated"><ns2:discussion>A charted cable area extends north to south through the survey area (Figure 29).  H12662 MBES data was examined for evidence of cables but none was found.</ns2:discussion><ns2:images><ns2:caption>Chart 16549 with H12662 MBES data overlaid showing route of cable area.</ns2:caption><ns2:link>SupportFiles\CableArea_with_Arrow.jpg</ns2:link></ns2:images></ns2:results><ns2:comments/></ns1:submarineFeatures><ns1:ferryRoutesAndTerminals><ns2:results investigated="Investigated"><ns2:discussion>The state of Alaska operates seasonally scheduled ferry service to the community of Cold Bay, its route passes through the H12662 survey area.</ns2:discussion></ns2:results><ns2:comments/></ns1:ferryRoutesAndTerminals><ns1:platforms><ns2:results investigated="None Exist"><ns2:discussion>No platforms exist within the H12662 survey area.</ns2:discussion></ns2:results><ns2:comments/></ns1:platforms><ns1:significantFeatures><ns2:results investigated="Investigated"><ns2:discussion>A feature resembling a submerged terminal moraine was located at the mouth of Lenard Harbor (Figure 30).</ns2:discussion><ns2:images><ns2:caption>Lenard Harbor terminal moraine.</ns2:caption><ns2:link>SupportFiles\Terminal_Moraine.jpg</ns2:link></ns2:images></ns2:results><ns2:comments/></ns1:significantFeatures><ns1:constructionOrDredging><ns2:results investigated="None Exist"><ns2:discussion>No present or planned construction or dredging exist within the H12662 survey area.  </ns2:discussion></ns2:results><ns2:comments/></ns1:constructionOrDredging><ns1:otherResults><ns2:comments/></ns1:otherResults><ns1:newSurveyRecommendation><ns2:results recommended="false"><ns2:discussion>No new surveys or further investigations are recommended for this area.</ns2:discussion></ns2:results><ns2:comments/></ns1:newSurveyRecommendation><ns1:insetRecommendation><ns2:results recommended="false"><ns2:discussion>No new insets are recommended for this area.</ns2:discussion></ns2:results><ns2:comments/></ns1:insetRecommendation></ns1:additionalResults></ns1:resultsAndRecommendations><ns1:approvalSheet><ns1:statements><ns1:supervision>As Chief of Party, Field operations for this hydrographic survey were conducted under my direct supervision, with frequent personal checks of progress and adequacy. I have reviewed the attached survey data and reports.</ns1:supervision><ns1:approval>All field sheets, this Descriptive Report, and all accompanying records and data are approved. All records are forwarded for final review and processing to the Processing Branch.</ns1:approval><ns1:adequacyOfSurvey>The survey data meets or exceeds requirements as set forth in the NOS Hydrographic Surveys and Specifications Deliverables Manual, Field Procedures Manual, Letter Instructions, and all HSD Technical Directives. These data are adequate to supersede charted data in their common areas. This survey is complete and no additional work is required with the exception of deficiencies noted in the Descriptive Report.</ns1:adequacyOfSurvey><ns1:additionalInfo xsi:nil="true"></ns1:additionalInfo></ns1:statements><ns1:signingPersonnel><ns2:approverName>Edward J. Van Den Ameele, CDR/NOAA</ns2:approverName><ns2:approverTitle>Commanding Officer, NOAA Ship Rainier</ns2:approverTitle><ns2:approvalDate>2015-01-23</ns2:approvalDate></ns1:signingPersonnel><ns1:signingPersonnel><ns2:approverName>Adam Pfundt, LTJG/NOAA</ns2:approverName><ns2:approverTitle>Field Operations Officer, NOAA Ship Rainier</ns2:approverTitle><ns2:approvalDate>2015-01-23</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>2015-01-23</ns2:approvalDate></ns1:signingPersonnel><ns1:signingPersonnel><ns2:approverName>B.D. Jackson</ns2:approverName><ns2:approverTitle>Senior Survey Technician, NOAA Ship Rainier</ns2:approverTitle><ns2:approvalDate>2015-01-23</ns2:approvalDate></ns1:signingPersonnel></ns1:approvalSheet></ns1:descriptiveReport>