<?xml version="1.0" encoding="UTF-8"?><ns1:descriptiveReport xmlns:ns1="http://svn.pydro.noaa.gov/2019/01/DescriptiveReport" xmlns:ns2="http://svn.pydro.noaa.gov/2019/01/AllGlobalTypes" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://svn.pydro.noaa.gov/2019/01/DescriptiveReport http://svn.pydro.noaa.gov/2019/01/DR.xsd"><ns1:metadata><ns1:surveyMetadata><ns2:verifier>Pacific Hydrographic Branch</ns2:verifier><ns2:titlesheetRemarks><ns2:branchRemarks>Any revisions to the Descriptive Report (DR) applied during office processing are shown in red italic text. The DR is maintained as a field unit product, therefore all information and recommendations within this report are considered preliminary unless otherwise noted. The final disposition of survey data is represented in the NOAA nautical chart products. All pertinent records for this survey are archived at the National Centers for Environmental Information (NCEI) and can be retrieved via https://www.ncei.noaa.gov/. 

Products created during office processing were generated in NAD83 UTM 5N, MLLW
. All references to other horizontal or vertical datums in this report are applicable to the processed hydrographic data provided by the field unit.</ns2:branchRemarks><ns2:fieldRemarks xsi:nil="true"></ns2:fieldRemarks></ns2:titlesheetRemarks><ns2:projectType>Navigable Area</ns2:projectType><ns2:acquisition><ns2:units>meters</ns2:units></ns2:acquisition><ns2:equipmentTypes><ns2:imageryEquipment>Multibeam Echo Sounder Backscatter</ns2:imageryEquipment><ns2:soundingEquipment>Multibeam Echo Sounder</ns2:soundingEquipment></ns2:equipmentTypes><ns2:datesOfSurvey><ns2:end>2019-06-21</ns2:end><ns2:start>2019-05-11</ns2:start></ns2:datesOfSurvey><ns2:timeZone>UTC</ns2:timeZone><ns2:year>2019</ns2:year><ns2:PIDate>2019-04-01</ns2:PIDate><ns2:chiefOfParty>Benjamin K. Evans, CAPT/NOAA</ns2:chiefOfParty></ns1:surveyMetadata><ns1:assignment>NOAA</ns1:assignment><ns1:registryMetadata><ns2:sublocality>Ugak Bay</ns2:sublocality><ns2:sheetID>7</ns2:sheetID><ns2:country>United States</ns2:country><ns2:stateOrTerritory>Alaska</ns2:stateOrTerritory><ns2:scale>40000</ns2:scale><ns2:registryInstructions xsi:nil="true"></ns2:registryInstructions><ns2:registryNumber>H13110</ns2:registryNumber></ns1:registryMetadata><ns1:projectMetadata><ns2:name>East Coast of Kodiak Island, Alaska</ns2:name><ns2:number>OPR-P136-RA-19</ns2:number><ns2:fieldUnit>NOAA Ship Rainier (S221)</ns2:fieldUnit><ns2:generalLocality>Kodiak Island, Alaska</ns2:generalLocality></ns1:projectMetadata></ns1:metadata><ns1:resultsAndRecommendations><ns1:chartComparison><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: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:charts><ns2:comments/><ns2:ENC><ns2:chart><ns2:name>US4AK5OM</ns2:name><ns2:updateApplicationDate>2019-08-17</ns2:updateApplicationDate><ns2:edition>8</ns2:edition><ns2:preliminary>false</ns2:preliminary><ns2:issueDate>2019-08-17</ns2:issueDate><ns2:scale>800000</ns2:scale></ns2:chart><ns2:discussion>A comparison was made between H13110 derived contours and ENC US4AK5OM with the following results. H13110 3-fathom and 10-fathom contours were generally inshore of the charted ENC depth curves. As noted below, many ledges extend farther out on the ENCs than their actual positions. </ns2:discussion><ns2:comments/><ns2:images><ns2:link>SupportFiles\Chart Comparison 1.png</ns2:link><ns2:caption>ENC US4AK5OM overlaid with H13110 contours. </ns2:caption></ns2:images><ns2:images><ns2:link>SupportFiles\Chart Comparison 2.png</ns2:link><ns2:caption>ENC US4AK5OM overlaid with H13110 contours showing discrepancies between charted depth curves and survey data. </ns2:caption></ns2:images><ns2:images><ns2:link>SupportFiles\Chart Comparison 3.png</ns2:link><ns2:caption>ENC US4AK5OM overlaid with H13110 contours showing discrepancies between charted depth curves and survey data. </ns2:caption></ns2:images></ns2:ENC></ns1:charts><ns1:chartedFeatures><ns2:results investigated="None Exist"><ns2:discussion>No charted features with 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> No new navigationally significant features were detected that were not included in the H13110 Final Feature File or elsewhere in this report.</ns2:discussion></ns2:results><ns2:comments/></ns1:unchartedFeatures><ns1:bottomSamples><ns2:results investigated="Investigated"><ns2:discussion>Four bottom samples were investigated for this survey; the results are included in the H13110 Final Feature File submitted with this report.</ns2:discussion></ns2:results><ns2:comments/></ns1:bottomSamples><ns1:shoalAndHazardousFeatures><ns2:results investigated="Investigated"><ns2:discussion> In many instances charted ledges extend past their positions identified during shoreline acquisition. </ns2:discussion><ns2:images><ns2:link>SupportFiles\Chart Comparison 4.png</ns2:link><ns2:caption>US4AK5OM overlaid with H13110 contours showing mischarted ledge. </ns2:caption></ns2:images><ns2:images><ns2:link>SupportFiles\Chart Comparison 5.png</ns2:link><ns2:caption>US4AK5OM overlaid with H13110 contours showing mischarted ledge. </ns2:caption></ns2:images></ns2:results><ns2:comments/></ns1:shoalAndHazardousFeatures><ns1:methods><ns2:discussion>A comparison was made between H13110 survey data and Electronic Navigational Chart (ENC) US4AK5OM using CUBE surfaces, selected soundings, and contours created in CARIS.</ns2:discussion><ns2:comments/></ns1:methods></ns1:chartComparison><ns1:additionalResults><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:otherResults><ns2:comments/></ns1:otherResults><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:insetRecommendation><ns2:results recommended="false"><ns2:discussion>No new insets are recommended for this area.</ns2:discussion></ns2:results><ns2:comments/></ns1:insetRecommendation><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:submarineFeatures><ns2:results investigated="None Exist"><ns2:discussion>No submarine features exist for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:submarineFeatures><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:platforms><ns2:results investigated="None Exist"><ns2:discussion>No platforms exist for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:platforms><ns1:shoreline><ns2:results investigated="Investigated"><ns2:discussion>Limited shoreline verification was conducted in accordance with applicable sections of NOAA HSSD and FPM using the Project Reference File (PRF) and Composite Source File (CSF) provided with the Project Instructions. In the field, all assigned features that were safe to approach, were addressed as required with S-57 attribution and recorded in the H13110_FFF to best represent the features at chart scale. This file also includes new features found in the field as well as recommendations to update, retain or delete assigned features. 

Three assigned rocks were investigated with single beam echo sounder. During acquisition no sign of the rocks were detected, however equipment misconfiguration of the SBES at the time of the survey rendered the data unusable for determining a least depth on the rocks with sufficient confidence. Visual observations and recommendations on the rocks are included in the final feature file.  

The height of one assigned feature was unable to be obtained via LiDAR. The rock was awash at the time of observation. The tidal adjustment of a feature approximately 59m to the SE observed at approximately the same time was used to obtain the raw height. Visual observations and recommendations on the rock are included in the final feature file. </ns2:discussion></ns2:results><ns2:comments/></ns1:shoreline><ns1:abnormalSeafloorEnviroCond><ns2:results investigated="None Exist"><ns2:discussion>No abnormal seafloor and/or environmental conditions exist for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:abnormalSeafloorEnviroCond><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:additionalResults></ns1:resultsAndRecommendations><ns1:verticalAndHorizontalControl><ns1:discussion>Additional information discussing the vertical or horizontal control for this survey can be found in the accompanying DAPR.</ns1:discussion><ns1:verticalControl><ns2:VDATUM_or_constantSep used="true"><ns2:discussion xsi:nil="true"></ns2:discussion><ns2:ellipsoidToChartDatumSepFile><ns2:fileName>P136RA2019_ERTDM_NAD83-MLLW.csar; </ns2:fileName><ns2:fileName> P136RA2019_ERTDM_NAD83-MHW.csar</ns2:fileName></ns2:ellipsoidToChartDatumSepFile><ns2:comments/><ns2:methodsUsed>ERS via ERTDM</ns2:methodsUsed></ns2:VDATUM_or_constantSep><ns2:standard_or_ERZT used="false" xsi:nil="true"/><ns2:tideStations/><ns2:comments/><ns2:verticalDatum>Mean Lower Low Water</ns2:verticalDatum></ns1:verticalControl><ns1:additionalIssues><ns2:issue><ns2:discussion>Precise Positioning-Real Time Extended (PP-RTX) processing methods were used in Applanix PosPac MMS 8.3 software to produce SBETs for post-processing horizontal correction.</ns2:discussion><ns2:title>SBET Processing Method</ns2:title><ns2:comments/></ns2:issue><ns2:comments/></ns1:additionalIssues><ns1:horizontalControl><ns2:projection>Projected UTM 5</ns2:projection><ns2:DGPS used="false" xsi:nil="true"/><ns2:comments/><ns2:WAAS used="true"><ns2:discussion>The Wide Area Augmentation System (WAAS) was used for real-time horizontal control during data acquisition.</ns2:discussion><ns2:comments/></ns2:WAAS><ns2:RTK used="false" xsi:nil="true"/><ns2:horizontalDatum>North American Datum 1983</ns2:horizontalDatum><ns2:PPP used="false" xsi:nil="true"/><ns2:PPK used="true"><ns2:baseStations/><ns2:comments/><ns2:methodsUsed>RTX</ns2:methodsUsed></ns2:PPK></ns1:horizontalControl></ns1:verticalAndHorizontalControl><ns1:approvalSheet><ns1:signingPersonnel><ns2:approverName>Samuel F. Greenaway CDR/NOAA</ns2:approverName><ns2:approvalDate>2020-03-03</ns2:approvalDate><ns2:approverTitle>Chief of Party</ns2:approverTitle></ns1:signingPersonnel><ns1:signingPersonnel><ns2:approverName>Hadley A. Owen, LT/NOAA</ns2:approverName><ns2:approvalDate>2020-03-03</ns2:approvalDate><ns2:approverTitle>Field Operations Officer</ns2:approverTitle></ns1:signingPersonnel><ns1:signingPersonnel><ns2:approverName>James B. Jacobson</ns2:approverName><ns2:approvalDate>2020-03-03</ns2:approvalDate><ns2:approverTitle>Chief Survey Technician</ns2:approverTitle></ns1:signingPersonnel><ns1:signingPersonnel><ns2:approverName>Amanda M. Finn</ns2:approverName><ns2:approvalDate>2020-03-03</ns2:approvalDate><ns2:approverTitle>Senior Survey Technician</ns2:approverTitle></ns1:signingPersonnel><ns1:statements><ns1:adequacyOfSurvey>The survey data meets or exceeds requirements as set forth in the NOS Hydrographic Surveys Specifications and Deliverables, 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: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: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:additionalInfo xsi:nil="true"></ns1:additionalInfo></ns1:statements></ns1:approvalSheet><ns1:dataAcquisitionAndProcessing><ns1:qualityControl><ns1:equipmentEffectiveness><ns2:results deviation="true"><ns2:issue><ns2:discussion>On day number 132 (May 12, 2019) the POSMV file for vessel S221 was incorrectly set up, resulting in no delayed heave being logged. Therefore real-time heave was applied. As the data in question was acquired via S221 (less subject to the effects of heave) on a relatively calm day, and delayed heave is a post processed element, it was determined that no additional error was induced. </ns2:discussion><ns2:title>S221 Logging of Delayed Heave</ns2:title><ns2:comments/></ns2:issue><ns2:issue><ns2:discussion>On day number 162 (June 11, 2019) launch 2801 experienced a poor GPS solution from inadequate satellite constellation due to terrain blockage (mountains) in a SW portion of the survey area. As a result the processed SBET was approximately 4 meters offset from adjacent lines. The Pydro AutoQC tool was used to interpolate over the affected area, and a new SBET was created and applied, resolving the issue. The affected line was 0004_20190611_171953_2801_300A_162.  </ns2:discussion><ns2:title>SBET - Lack of solution status near a steep elevation</ns2:title><ns2:comments/><ns2:images><ns2:link>SupportFiles\SBET Issue.png</ns2:link><ns2:caption>Approximate 4m offset in portion of data acquired by 2801 on DN 162. </ns2:caption></ns2:images><ns2:images><ns2:link>SupportFiles\SBET Resolution.png</ns2:link><ns2:caption>Affected SBET area after SBET interpolation. </ns2:caption></ns2:images></ns2:issue></ns2:results><ns2:comments/></ns1:equipmentEffectiveness><ns1:uncertainty><ns2:discussion>Total Propagated Uncertainty (TPU) values for survey H13110 were derived from a combination of fixed values for equipment and vessel characteristics, as well as from assigned values for sound speed uncertainties. The uncertainty for the Ellipsoidally Referenced Tidal Datum Model (ERTDM) used to reduce data to the ellipse was determined to be 0.15 meters based on a conservative modeling of uncertainty for the separation model. Please see Appendix A Supplemental Correspondence for more details. ERTDM is synonym to what was formerly know as poor man's VDatum (PMVD). 

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 this survey. Real-time uncertainties from Kongsberg MBES sonars were recorded and applied in 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 position and attitude were applied in Caris HIPS using SBET and RMS files generated using POSPac MMS software.

Uncertainty values of the submitted finalized grid were calculated in Caris using &quot;Greater of the Two&quot; of uncertainty and standard deviation (scaled to 95%). Grid QA within Pydro QC Tools was used to analyze H13110 Total Vertical Uncertainty (TVU) compliance, a histogram plot of the results is shown below.</ns2:discussion><ns2:values><ns2:soundSpeedUncertainty><ns2:measuredXBT xsi:nil="true"/><ns2:measuredCTD xsi:nil="true"/><ns2:measuredMVP units="meters/second">1.0</ns2:measuredMVP><ns2:surface units="meters/second">0.05</ns2:surface><ns2:hullID>S221</ns2:hullID></ns2:soundSpeedUncertainty><ns2:soundSpeedUncertainty><ns2:measuredXBT xsi:nil="true"/><ns2:measuredCTD units="meters/second">3.0</ns2:measuredCTD><ns2:measuredMVP xsi:nil="true"/><ns2:surface units="meters/second">0.05</ns2:surface><ns2:hullID>2801, 2802, 2803, 2804</ns2:hullID></ns2:soundSpeedUncertainty><ns2:tideUncertainty><ns2:tideMethod>ERS via ERTDM</ns2:tideMethod><ns2:zoning units="meters">0.15</ns2:zoning><ns2:measured units="meters">0</ns2:measured></ns2:tideUncertainty></ns2:values><ns2:comments><ns2:branchComment><ns2:comment>The hydrographer has correctly documented the separation model's uncertainty of 0.15m, but has not applied this uncertainty in the data. 

The hydrographer states, in Table 8 above, that the Sound Speed Uncertainty applied for vessel S221 Measured-MVP values was 1.0m/s, but the processing logs show the applied Measured sound speed uncertainty used for S221 was actually 3.0m/s. </ns2:comment></ns2:branchComment></ns2:comments><ns2:images><ns2:link>SupportFiles\H13110_MB_VR_MLLW_Final.QAv5.tvu_qc.png</ns2:link><ns2:caption>Pydro derived plot showing TVU compliance of H13110 finalized multi-resolution MBES data. </ns2:caption></ns2:images></ns1:uncertainty><ns1:coverageEquipmentAndMethods><ns2:results deviation="true"><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:discussion>Pydro QC Tools v. 3.1.1 Detect Fliers was used to find fliers in the finalized variable resolution surface. Detect Fliers parameters included Gaussian Curvature, Adjacent Cells, Edge Slivers, and Isolated Nodes. Flier height was not restricted.

Obvious noise was rejected by the hydrographer in Caris subset editor. After data cleaning, Detect Fliers identified 1 fliers. This was investigated and found to be a false positive.</ns2:discussion><ns2:title>Detect Fliers</ns2:title><ns2:comments/></ns2:issue><ns2:comments/></ns1:additionalQualityControl><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:factorsAffectingSoundings><ns2:results deviation="true"><ns2:issue><ns2:discussion>Due to poor environmental conditions during the time of the survey, areas in the NW part of the survey. Despite the hydrographer's best efforts to monitor data quality in real time, bubble masses at and below the surface proved to be problematic and caused spreading of the outer beams. To address this issue, the hydrographer rejected the most egregious outer beam soundings obviously in error in an attempt to produce a surface that best represented the sea floor. In some cases, where there was not sufficient overlap between adjacent survey lines, small holidays are now left from cleaning. All examined offsets between survey lines were observed to be within NOAA HSSD standards.</ns2:discussion><ns2:title>Environmental Influence - Outer beam noise</ns2:title><ns2:comments/><ns2:images><ns2:link>SupportFiles\H13110_NW_Overview.png</ns2:link><ns2:caption>Imagine showing the main holiday areas in the NW part of H13110.</ns2:caption></ns2:images><ns2:images><ns2:link>SupportFiles\12-5-2019 10-50-29 AM.png</ns2:link><ns2:caption>Image displaying environmental errors existing in NW portion of Survey.</ns2:caption></ns2:images><ns2:images><ns2:link>SupportFiles\H13110_Noise2.png</ns2:link><ns2:caption>Image showing areas where soundings were removed, leaving holidays.</ns2:caption></ns2:images></ns2:issue></ns2:results><ns2:comments/></ns1:factorsAffectingSoundings><ns1:crosslines><ns2:discussion>RAINIER launch 2801 acquired 13.97 nautical miles of multi beam crosslines across most depth ranges and multiple boat days. Due to operational time constraints, the percentage of crosslines acquired was slightly less than the requirement specified in the HSSD, however the hydrographer deems them adequate for verifying and evaluating the internal consistency of H13110 survey data. Analysis was performed using the Compare Grids function in Pydro Explorer on finalized VR surfaces of H13110 mainscheme only and crossline only data. 99.5% of nodes met allowable uncertainties. </ns2:discussion><ns2:comments/><ns2:images><ns2:link>SupportFiles\H13110 Xlines.png</ns2:link><ns2:caption>H13110 crossline surface overlaid on mainscheme tracklines. </ns2:caption></ns2:images><ns2:images><ns2:link>SupportFiles\H13110_MB_VR_MLLW_Final-H13110_XL_VR_MLLW_Final_fracAllowErr_Freq.png</ns2:link><ns2:caption>Pydro derived plot showing node percentage-pass value of H13110 mainscheme to crossline data. </ns2:caption></ns2:images><ns2:images><ns2:link>SupportFiles\H13110_MB_VR_MLLW_Final-H13110_XL_VR_MLLW_Final_depth_delta.png</ns2:link><ns2:caption>Pydro derived plot showing absolute difference statistics of H13110 mainscheme to crossline data.</ns2:caption></ns2:images></ns1:crosslines><ns1:junctions><ns2:discussion>There are no junctions associated with this survey. </ns2:discussion><ns2:comments/></ns1:junctions><ns1:soundSpeedMethods><ns1:images><ns2:link>SupportFiles\SVP Locations.png</ns2:link><ns2:caption>H13110 sound speed cast locations</ns2:caption></ns1:images><ns1:castFrequency>Once every four hours. </ns1:castFrequency><ns1:discussion>Fifty five sound speed profiles were acquired for this survey at discrete locations within the survey area at least once every four hours, when significant changes in surface sound speed were observed, or when operating in a new area. Sound speed profiles were acquired using Sea-Bird Scientific SBE 19plus Profiler and Odim Brooke Ocean MVP200. All casts were concatenated into a master file and applied using the &quot;Nearest distance within Time&quot; (4 hours) profile selection method.</ns1:discussion><ns1:comments/></ns1:soundSpeedMethods></ns1:qualityControl><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:equipment><ns1:majorSystem><ns2:model>POS MV 320 v5</ns2:model><ns2:manufacturer>Applanix</ns2:manufacturer><ns2:type>Positioning and Attitude System</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:model>EM 2040</ns2:model><ns2:manufacturer>Kongsberg Maritime</ns2:manufacturer><ns2:type>MBES</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:model>SBE 19plus</ns2:model><ns2:manufacturer>Sea-Bird Scientific</ns2:manufacturer><ns2:type>Conductivity, Temperature, and Depth Sensor</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:model>SVP 70</ns2:model><ns2:manufacturer>Teledyne RESON</ns2:manufacturer><ns2:type>Sound Speed System</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:model>EM 710</ns2:model><ns2:manufacturer>Kongsberg Maritime</ns2:manufacturer><ns2:type>MBES</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:model>MVP200</ns2:model><ns2:manufacturer>ODIM Brooke Ocean</ns2:manufacturer><ns2:type>Sound Speed System</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:model>VLP-16</ns2:model><ns2:manufacturer>Velodyne LiDAR</ns2:manufacturer><ns2:type>Lidar System</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:model>Echotrac CV200</ns2:model><ns2:manufacturer>ODIM Brooke Ocean</ns2:manufacturer><ns2:type>SBES</ns2:type></ns1:majorSystem><ns1:discussion xsi:nil="true"></ns1:discussion><ns1:comments/></ns1:equipment><ns1:comments/><ns1:vessels><ns1:images><ns2:link>SupportFiles\RA-6 Medley and Rainier.JPG</ns2:link><ns2:caption>RA-6 (2804) and RAINIER(S221) in Ugak Bay, AK</ns2:caption></ns1:images><ns1:images><ns2:link>SupportFiles\2701_RA2.jpg</ns2:link><ns2:caption>RA-2 (2701)</ns2:caption></ns1:images><ns1:vessel><ns2:draft units="meters">1.1</ns2:draft><ns2:LOA units="meters">8.8</ns2:LOA><ns2:hullID>2804</ns2:hullID></ns1:vessel><ns1:vessel><ns2:draft units="meters">1.1</ns2:draft><ns2:LOA units="meters">8.8</ns2:LOA><ns2:hullID>2803</ns2:hullID></ns1:vessel><ns1:vessel><ns2:draft units="meters">1.1</ns2:draft><ns2:LOA units="meters">8.8</ns2:LOA><ns2:hullID>2802</ns2:hullID></ns1:vessel><ns1:vessel><ns2:draft units="meters">1.1</ns2:draft><ns2:LOA units="meters">8.8</ns2:LOA><ns2:hullID>2801</ns2:hullID></ns1:vessel><ns1:vessel><ns2:draft units="meters">4.7</ns2:draft><ns2:LOA units="meters">70.4</ns2:LOA><ns2:hullID>S221</ns2:hullID></ns1:vessel><ns1:vessel><ns2:draft units="meters">0.47</ns2:draft><ns2:LOA units="meters">7.62</ns2:LOA><ns2:hullID>2701</ns2:hullID></ns1:vessel><ns1:discussion xsi:nil="true"></ns1:discussion><ns1:comments/></ns1:vessels></ns1:equipmentAndVessels><ns1:echoSoundingCorrections><ns1:corrections><ns2:results deviation="true"><ns2:discussion>All data reduction procedures conform to those detailed in the DAPR. </ns2:discussion></ns2:results><ns2:comments/></ns1:corrections><ns1:additionalIssues><ns2:comments/></ns1:additionalIssues><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:echoSoundingCorrections><ns1:backscatter><ns2:results acquired="true"><ns2:discussion>Raw backscatter data was acquired as .all files logged during MBES operations and subsequently processed by personnel aboard RAINIER. The .GSF files created during processing and one backscatter mosaic per vessel per frequency has been delivered with this report. Backscatter processing procedures are described in the DAPR.</ns2:discussion><ns2:images><ns2:link>SupportFiles\H13110_Backscatter_Chart_Overlay2.png</ns2:link><ns2:caption>Overview of H13110 backscatter mosaics (Chart 16593)</ns2:caption></ns2:images></ns2:results><ns2:comments/></ns1:backscatter><ns1:dataProcessing><ns1:surfaces><ns1:discussion>Submitted surfaces were generated using the NOAA recommended parameters for depth-based (Ranges) Caris variable-resolution bathymetric grids as specified in the 2019 HSSD. </ns1:discussion><ns1:comments/><ns1:surface><ns2:purpose>Complete MBES</ns2:purpose><ns2:depthRange><ns2:min units="meters">0.80</ns2:min><ns2:max units="meters">105.80</ns2:max></ns2:depthRange><ns2:surfaceName>H13110_MB_VR_MLLW_final</ns2:surfaceName><ns2:surfaceType>CARIS VR Surface (CUBE)</ns2:surfaceType><ns2:resolution units="meters">Variable Resolution</ns2:resolution><ns2:surfaceParameter>NOAA_VR</ns2:surfaceParameter></ns1:surface><ns1:surface><ns2:purpose>Complete MBES</ns2:purpose><ns2:depthRange><ns2:min units="meters">0.80</ns2:min><ns2:max units="meters">105.80</ns2:max></ns2:depthRange><ns2:surfaceName>H13110_MB_VR_MLLW</ns2:surfaceName><ns2:surfaceType>CARIS VR Surface (CUBE)</ns2:surfaceType><ns2:resolution units="meters">Variable Resolution</ns2:resolution><ns2:surfaceParameter>NOAA_VR</ns2:surfaceParameter></ns1:surface></ns1:surfaces><ns1:additionalDataProcessing><ns2:comments/></ns1:additionalDataProcessing><ns1:drSoftware><ns1:imagerySoftware deviation="true"><ns1:manufacturer>QPS</ns1:manufacturer><ns1:version>7.8.1</ns1:version><ns1:name>Fledermaus Geocoder Tool Box (FMGT)</ns1:name></ns1:imagerySoftware><ns1:discussion xsi:nil="true"></ns1:discussion><ns1:featureObjectCatalog>NOAA Extended Attribute Files Version 5_7</ns1:featureObjectCatalog><ns1:bathySoftware deviation="true"><ns1:manufacturer>CARIS</ns1:manufacturer><ns1:version>11.1</ns1:version><ns1:name>HIPS/SIPS</ns1:name></ns1:bathySoftware><ns1:comments/></ns1:drSoftware></ns1:dataProcessing></ns1:dataAcquisitionAndProcessing><ns1:areaSurveyed><ns1:surveyQuality><ns2:discussion>Pydro QC Tools Grid QA was used to analyze H13110 multibeam echo sounder (MBES) data density. The submitted H13110 variable-resolution (VR) surface met HSSD density requirements as shown in the histogram below.</ns2:discussion><ns2:adequacy>The entire survey is adequate to supersede previous data.</ns2:adequacy><ns2:comments/><ns2:images><ns2:link>SupportFiles\H13110_MB_VR_MLLW_Final.QAv5.density.png</ns2:link><ns2:caption>Pydro derived histogram plot showing HSSD density compliance of H13110 finalized variable-resolution MBES data. </ns2:caption></ns2:images></ns1:surveyQuality><ns1:coverageGraphic><ns2:coverageGraphicImage><ns2:images><ns2:link>SupportFiles\H13110_Holidays_Edits.png</ns2:link><ns2:caption>VR surface showing locations of holidays derived from Pydro. The two holidays in Mainscheme coverage identified in the most NW corner were created during the final day of acquisition; other holidays in the NW corner are the result of insufficient overlap during challenging weather conditions. All locations not directly explained in the image correspond to features.</ns2:caption></ns2:images><ns2:images><ns2:link>SupportFiles\Holiday between islets.png</ns2:link><ns2:caption>Holiday between two islets located in NE section of sheet. On the day of acquisition wave action and hazardous operating conditions made acquiring complete coverage unsafe. Due to time constraints it was not possible to acquire additional coverage. </ns2:caption></ns2:images><ns2:images><ns2:link>SupportFiles\NE section_NALL_Kelp Line_edited.png</ns2:link><ns2:caption>Examples of H13110 NALL determination; the green dashed line indicates assigned sheet limits. This area exhibited large quantities of bull kelp. </ns2:caption></ns2:images><ns2:images><ns2:link>SupportFiles\Extended coverage_edited.png</ns2:link><ns2:caption>H13110 MBES coverage and assigned survey limits. Note area where coverage was extended beyond sheet limits. </ns2:caption></ns2:images></ns2:coverageGraphicImage></ns1:coverageGraphic><ns1:surveyLimits><ns2:results deviation="true"><ns2:discussion>Data were acquired within the assigned survey limits as required in the Project Instructions and HSSD. As noted above, additional data were acquired opportunistically extending southeast from the sheet limits during ship survey operations. </ns2:discussion></ns2:results><ns2:comments/></ns1:surveyLimits><ns1:surveyPurpose><ns2:discussion>According to the Fisheries of the United States report, Kodiak, Alaska supports the third busiest and fourth richest fisheries port in the United States. In 2017 the port was responsible for 530 million pounds of fish and 152 million dollars of product. Ugak Bay is a well fished area and is adjacent to a coastal route frequently transited by commercial vessels to and from Kodiak. Much of the existing depth data of this area dates back to the 1930s, and is not surveyed to modern standards. This poses a serious risk to life, property and the delicate ecosystem around Kodiak Island. This survey will provide contemporary data to update National Ocean Service (NOS) nautical charting products and generate backscatter data, which will be used in habitat mapping and substrate analysis.</ns2:discussion><ns2:comments/></ns1:surveyPurpose><ns1:areaDescription><ns2:discussion>The survey area is referred to as H13110, &quot;Ugak Bay&quot; (Sheet 7) in the Project Instructions. The acquired survey area is approximately 22.22 square nautical miles, and encompasses the area assigned in the project instructions as well as a portion of H13109, &quot;Pasagshak Pt&quot; (Sheet 8). The project instructions provided an estimate of 32 square nautical miles. The hydrographer determined that the assigned sheet limits cover an area of 20.66 square nautical miles, and it was determined that the project instructions were incorrect. </ns2:discussion><ns2:images><ns2:link>SupportFiles\Survey outline and coverage1.png</ns2:link><ns2:caption>H13110 assigned survey area and coverage (Chart 16593)</ns2:caption></ns2:images><ns2:comments/><ns2:limits><ns2:northWest><ns2:longitude hemisphere="W">152.803385</ns2:longitude><ns2:latitude hemisphere="N">57.50152</ns2:latitude></ns2:northWest><ns2:southEast><ns2:longitude hemisphere="W">152.530158</ns2:longitude><ns2:latitude hemisphere="N">57.379335</ns2:latitude></ns2:southEast></ns2:limits></ns1:areaDescription><ns1:surveyCoverage><ns2:results deviation="true"><ns2:discussion>Complete multi beam echo sounder (MBES) coverage was acquired to the inshore limit of hydrography, the Navigable Area Limit Line (NALL). Areas where survey coverage did not reach the 3.5-meter depth contour, nor the assigned sheet limits, were due to the survey vessel reaching the extent of safe navigation as shown in the figures below. These areas are characterized as being near shore, subject to dangerous wave action or other hazards such as rocks or thick kelp.

A total of 10 holidays are present in survey coverage.  Four correspond to features that were investigated during shoreline. Two were created during the final day of acquisition. Due to operational time constraints it was not possible to acquire them once discovered. The remaining four are a cluster located between two investigated features that wave action and hazardous operating conditions made unsafe to acquire. </ns2:discussion></ns2:results><ns2:coverageRequirement><ns2:requiredCoverage>Complete Coverage (Refer to HSSD Section 5.2.2.3)</ns2:requiredCoverage><ns2:waterDepth>All waters in survey area </ns2:waterDepth></ns2:coverageRequirement><ns2:coverageRequirement><ns2:requiredCoverage>Acquire backscatter data during all multibeam data acquisition (Refer to HSSD Section 6.2)</ns2:requiredCoverage><ns2:waterDepth>All waters in survey area</ns2:waterDepth></ns2:coverageRequirement><ns2:comments/></ns1:surveyCoverage><ns1:surveyStatistics><ns2:LNM><ns2:totalLNM><ns2:MS_SBES>0</ns2:MS_SBES><ns2:MS_SBES_MBES>0</ns2:MS_SBES_MBES><ns2:MS_SBES_SSS>0</ns2:MS_SBES_SSS><ns2:MS_SSS>0</ns2:MS_SSS><ns2:XL_lidar>0</ns2:XL_lidar><ns2:MS_MBES_SSS>0</ns2:MS_MBES_SSS><ns2:XL_MBES_SBES>13.97</ns2:XL_MBES_SBES><ns2:MS_MBES>404.79</ns2:MS_MBES><ns2:MS_lidar>0</ns2:MS_lidar><ns2:percentXLLNM>3.45</ns2:percentXLLNM></ns2:totalLNM><ns2:vesselLNM><ns2:vessel><ns2:statistics><ns2:MS_SBES>0</ns2:MS_SBES><ns2:MS_SBES_MBES>0</ns2:MS_SBES_MBES><ns2:MS_SBES_SSS>0</ns2:MS_SBES_SSS><ns2:MS_SSS>0</ns2:MS_SSS><ns2:XL_lidar>0</ns2:XL_lidar><ns2:MS_MBES_SSS>0</ns2:MS_MBES_SSS><ns2:XL_MBES_SBES>0</ns2:XL_MBES_SBES><ns2:MS_MBES>55.43</ns2:MS_MBES><ns2:MS_lidar>0</ns2:MS_lidar></ns2:statistics><ns2:hullID>S221</ns2:hullID></ns2:vessel><ns2:vessel><ns2:statistics><ns2:MS_SBES>0</ns2:MS_SBES><ns2:MS_SBES_MBES>0</ns2:MS_SBES_MBES><ns2:MS_SBES_SSS>0</ns2:MS_SBES_SSS><ns2:MS_SSS>0</ns2:MS_SSS><ns2:XL_lidar>0</ns2:XL_lidar><ns2:MS_MBES_SSS>0</ns2:MS_MBES_SSS><ns2:XL_MBES_SBES>13.97</ns2:XL_MBES_SBES><ns2:MS_MBES>108.74</ns2:MS_MBES><ns2:MS_lidar>0</ns2:MS_lidar></ns2:statistics><ns2:hullID>2801</ns2:hullID></ns2:vessel><ns2:vessel><ns2:statistics><ns2:MS_SBES>0</ns2:MS_SBES><ns2:MS_SBES_MBES>0</ns2:MS_SBES_MBES><ns2:MS_SBES_SSS>0</ns2:MS_SBES_SSS><ns2:MS_SSS>0</ns2:MS_SSS><ns2:XL_lidar>0</ns2:XL_lidar><ns2:MS_MBES_SSS>0</ns2:MS_MBES_SSS><ns2:XL_MBES_SBES>0</ns2:XL_MBES_SBES><ns2:MS_MBES>18.82</ns2:MS_MBES><ns2:MS_lidar>0</ns2:MS_lidar></ns2:statistics><ns2:hullID>2802</ns2:hullID></ns2:vessel><ns2:vessel><ns2:statistics><ns2:MS_SBES>0</ns2:MS_SBES><ns2:MS_SBES_MBES>0</ns2:MS_SBES_MBES><ns2:MS_SBES_SSS>0</ns2:MS_SBES_SSS><ns2:MS_SSS>0</ns2:MS_SSS><ns2:XL_lidar>0</ns2:XL_lidar><ns2:MS_MBES_SSS>0</ns2:MS_MBES_SSS><ns2:XL_MBES_SBES>0</ns2:XL_MBES_SBES><ns2:MS_MBES>154.31</ns2:MS_MBES><ns2:MS_lidar>0</ns2:MS_lidar></ns2:statistics><ns2:hullID>2803</ns2:hullID></ns2:vessel><ns2:vessel><ns2:statistics><ns2:MS_SBES>0</ns2:MS_SBES><ns2:MS_SBES_MBES>0</ns2:MS_SBES_MBES><ns2:MS_SBES_SSS>0</ns2:MS_SBES_SSS><ns2:MS_SSS>0</ns2:MS_SSS><ns2:XL_lidar>0</ns2:XL_lidar><ns2:MS_MBES_SSS>0</ns2:MS_MBES_SSS><ns2:XL_MBES_SBES>0</ns2:XL_MBES_SBES><ns2:MS_MBES>67.48</ns2:MS_MBES><ns2:MS_lidar>0</ns2:MS_lidar></ns2:statistics><ns2:hullID>2804</ns2:hullID></ns2:vessel></ns2:vesselLNM></ns2:LNM><ns2:discussion xsi:nil="true"></ns2:discussion><ns2:comments/><ns2:totalSurveyStats><ns2:bottomSamples>4</ns2:bottomSamples><ns2:diveOps>0</ns2:diveOps><ns2:DP>99</ns2:DP><ns2:SNM>22.22</ns2:SNM><ns2:maritimeBoundaryPoints>0</ns2:maritimeBoundaryPoints></ns2:totalSurveyStats><ns2:surveyDates>2019-05-11</ns2:surveyDates><ns2:surveyDates>2019-05-12</ns2:surveyDates><ns2:surveyDates>2019-05-13</ns2:surveyDates><ns2:surveyDates>2019-05-14</ns2:surveyDates><ns2:surveyDates>2019-06-11</ns2:surveyDates><ns2:surveyDates>2019-06-12</ns2:surveyDates><ns2:surveyDates>2019-06-18</ns2:surveyDates><ns2:surveyDates>2019-06-19</ns2:surveyDates><ns2:surveyDates>2019-06-21</ns2:surveyDates></ns1:surveyStatistics></ns1:areaSurveyed></ns1:descriptiveReport>