<?xml version="1.0" encoding="UTF-8"?><ns1:descriptiveReport xmlns:ns1="http://svn.pydro.noaa.gov/2016/01/DescriptiveReport" xmlns:ns2="http://svn.pydro.noaa.gov/2016/01/AllGlobalTypes" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://svn.pydro.noaa.gov/2016/01/DescriptiveReport http://svn.pydro.noaa.gov/2016/01/DR.xsd"><ns1:resultsAndRecommendations><ns1:chartComparison><ns1:chartedFeatures><ns2:results investigated="Investigated"><ns2:discussion>H12999 MBES data identified a least depth of 16-fathoms over a shoal reported in 2006. </ns2:discussion><ns2:images><ns2:link>SupportFiles\Shoal_rep_2006.jpg</ns2:link><ns2:caption>H12999 MBES data overlaid on Chart 16593 showing least depth on shoal reported in 2006.</ns2:caption></ns2:images></ns2:results><ns2:comments/></ns1:chartedFeatures><ns1:bottomSamples><ns2:results investigated="Investigated"><ns2:discussion>Six bottom samples were investigated for this survey; the results are included in the H12999 Final Feature File submitted with this report.</ns2:discussion></ns2:results><ns2:comments/></ns1:bottomSamples><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:charts><ns2:ENC><ns2:discussion>H12999 survey data coincide with sections of ENC US4AK5OM and US4AK5PM.  A positional offset between the two ENCs of approximately 20-70 meters was identified at the junction of these charts at the north end of the H12999 survey area (Figure 16).

A comparison was made between H12999 derived contours and ENC US4AK5OM with the following results: Except as noted below, H12999 3-fathom and 10-fathom contours were generally inshore of the ENC positions; the H12999 50-fathom contour showed good general agreement with the ENC (Figure 17).

In the Svitlak Island area, H12999 data identified many inconsistencies with the chart including a 3-meter shoal, located on the charted 5-fathom ENC contour, approximately 1600 meters west of Utesistoi Island.  The area southwest of Svitlak Island is a complex mix of shoals, foul ground and ledges; the ENC requires significant revision in that region (Figure 18).

Eleven Dangers to Navigation (DTON) were identified in the H12999 survey area and submitted to Marine Chart Division's (MCD) Nautical Data Branch.  Refer to the H12999_DTON_Report for location and description of these dangers.  </ns2:discussion><ns2:images><ns2:link>SupportFiles\ENC_Discontinuity_with_Inset.jpg</ns2:link><ns2:caption>ENC Discontinuity.  Red circles identify areas with positional offsets between ENCs of approximately 20 to 70 meters within the H12999 survey area.</ns2:caption></ns2:images><ns2:images><ns2:link>SupportFiles\H12999_Contour_ENC_Comparison_Lables.jpg</ns2:link><ns2:caption>ENC US4AK5OM overlaid with H12999 derived contours.</ns2:caption></ns2:images><ns2:images><ns2:link>SupportFiles\Svitlak_Area_3_fathom_Contours_Labled.jpg</ns2:link><ns2:caption>H12999 3-fathom contours (in red) overlaid on ENC US4AK5OM showing numerous discrepancies between survey data and the chart.</ns2:caption></ns2:images><ns2:chart><ns2:issueDate>2015-10-05</ns2:issueDate><ns2:edition>4</ns2:edition><ns2:name>US4AK5OM</ns2:name><ns2:scale>80000</ns2:scale><ns2:updateApplicationDate>2015-10-05</ns2:updateApplicationDate><ns2:preliminary>false</ns2:preliminary></ns2:chart><ns2:comments/></ns2:ENC><ns2:ENC><ns2:discussion>ENC US4AK5PM covers the northern-most nautical mile of H12999 data.  The survey derived 3-fathom and 10-fathom contours were found to be inshore of the ENC charted positions; the H12999 50-fathom contour showed good general agreement with the ENC.  Overall, H12999 soundings were deeper than charted depths.</ns2:discussion><ns2:chart><ns2:issueDate>2017-07-30</ns2:issueDate><ns2:edition>11</ns2:edition><ns2:name>US4AK5PM</ns2:name><ns2:scale>80000</ns2:scale><ns2:updateApplicationDate>2017-04-28</ns2:updateApplicationDate><ns2:preliminary>false</ns2:preliminary></ns2:chart><ns2:comments/></ns2:ENC><ns2:comments/></ns1:charts><ns1:DTONS><ns2:results reportSubmitted="true"><ns2:discussion>Eleven dangers to navigation were identified in the survey area and submitted in one report.  The H12999 Danger to Navigation Report is included in Appendix II of this Descriptive Report.</ns2:discussion><ns2:numberSubmitted>1</ns2:numberSubmitted><ns2:report><ns2:title>H12999_DTON_Report</ns2:title><ns2:dateSubmitted>2017-08-05</ns2:dateSubmitted></ns2:report></ns2:results><ns2:comments><ns2:branchComment concurrence="Concur with clarification"><ns2:comment>One additional DTON was identified and submitted for charting during office review.</ns2:comment></ns2:branchComment></ns2:comments></ns1:DTONS><ns1:shoalAndHazardousFeatures><ns2:results investigated="Investigated"><ns2:discussion> Features of navigational significance are discussed in the chart comparison sections above or are included in the H12999 Final Feature File submitted with this report.</ns2:discussion></ns2:results><ns2:comments/></ns1:shoalAndHazardousFeatures><ns1:unchartedFeatures><ns2:results investigated="Investigated"><ns2:discussion> No new navigationally significant features were detected that were not included in the H12999 Final Feature File or elsewhere in this report.</ns2:discussion></ns2:results><ns2:comments/></ns1:unchartedFeatures><ns1:methods><ns2:discussion>A comparison was made between H12999 survey data and Electronic Navigation Charts (ENC) US4AK5OM and US4AK5PM using CUBE surfaces, selected soundings and contours created in Caris.</ns2:discussion><ns2:comments/></ns1:methods><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:chartComparison><ns1:additionalResults><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 H12999_Final_Feature_File (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.  </ns2:discussion></ns2:results><ns2:comments/></ns1:shoreline><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:overheadFeatures><ns2:results investigated="None Exist"><ns2:discussion>No overhead features were observed within the H12999 survey area.</ns2:discussion></ns2:results><ns2:comments/></ns1:overheadFeatures><ns1:submarineFeatures><ns2:results investigated="Investigated"><ns2:discussion>A charted (16593) cable area extends through the H12999 survey area from Broad Point to Isthmus Point; no evidence of cables were identified in H12999 MBES data.</ns2:discussion></ns2:results><ns2:comments/></ns1:submarineFeatures><ns1:constructionOrDredging><ns2:results investigated="None Exist"><ns2:discussion>No present or planned construction or dredging are known to exist within the survey limits.</ns2:discussion></ns2:results><ns2:comments/></ns1:constructionOrDredging><ns1:platforms><ns2:results investigated="None Exist"><ns2:discussion>There are no platforms within the H12999 survey area.</ns2:discussion></ns2:results><ns2:comments/></ns1:platforms><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:priorSurveys><ns2:results investigated="None Exist"><ns2:discussion>No prior survey comparisons were provided for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:priorSurveys><ns1:otherResults><ns2:comments/></ns1:otherResults><ns1:ATONS><ns2:results investigated="Exist - Not Investigated"><ns2:discussion>No ATONs were specifically assigned for this survey and none exist within the assigned sheet limits.  The &quot;NOAA-UAF&quot; FL Y 4s Private buoy charted at the northeast corner of the H12999 survey area was not observed in the field.  The charted Marker at the head of Kalsin Bay was not seen.</ns2:discussion></ns2:results><ns2:comments/></ns1:ATONS><ns1:significantFeatures><ns2:results investigated="Investigated"><ns2:discussion>There are no significant features in the H12999 survey area that were not discussed elsewhere in this report.</ns2:discussion></ns2:results><ns2:comments/></ns1:significantFeatures><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:areaSurveyed><ns1:coverageGraphic><ns2:link>SupportFiles\H12999_Coverage.jpg</ns2:link><ns2:caption>H12999 MBES coverage and assigned survey limits (Chart 16593).</ns2:caption></ns1:coverageGraphic><ns1:surveyStatistics><ns2:surveyDates>2017-05-12</ns2:surveyDates><ns2:surveyDates>2017-05-13</ns2:surveyDates><ns2:surveyDates>2017-05-14</ns2:surveyDates><ns2:surveyDates>2017-05-15</ns2:surveyDates><ns2:surveyDates>2017-05-16</ns2:surveyDates><ns2:surveyDates>2017-05-25</ns2:surveyDates><ns2:surveyDates>2017-05-26</ns2:surveyDates><ns2:surveyDates>2017-05-28</ns2:surveyDates><ns2:surveyDates>2017-05-29</ns2:surveyDates><ns2:surveyDates>2017-05-30</ns2:surveyDates><ns2:surveyDates>2017-05-31</ns2:surveyDates><ns2:surveyDates>2017-06-01</ns2:surveyDates><ns2:surveyDates>2017-06-10</ns2:surveyDates><ns2:surveyDates>2017-06-11</ns2:surveyDates><ns2:surveyDates>2017-06-13</ns2:surveyDates><ns2:surveyDates>2017-06-20</ns2:surveyDates><ns2:surveyDates>2017-06-22</ns2:surveyDates><ns2:surveyDates>2017-06-23</ns2:surveyDates><ns2:surveyDates>2017-06-26</ns2:surveyDates><ns2:surveyDates>2017-06-27</ns2:surveyDates><ns2:surveyDates>2017-06-30</ns2:surveyDates><ns2:comments/><ns2:discussion xsi:nil="true"></ns2:discussion><ns2:LNM><ns2:totalLNM><ns2:XL_MBES_SBES>24.3</ns2:XL_MBES_SBES><ns2:percentXLLNM>4.0</ns2:percentXLLNM><ns2:MS_SBES_SSS>0</ns2:MS_SBES_SSS><ns2:MS_SSS>0</ns2:MS_SSS><ns2:MS_SBES>0</ns2:MS_SBES><ns2:MS_SBES_MBES>0</ns2:MS_SBES_MBES><ns2:XL_lidar>0</ns2:XL_lidar><ns2:MS_lidar>0</ns2:MS_lidar><ns2:MS_MBES>605</ns2:MS_MBES><ns2:MS_MBES_SSS>0</ns2:MS_MBES_SSS></ns2:totalLNM><ns2:vesselLNM><ns2:vessel><ns2:statistics><ns2:XL_MBES_SBES>0</ns2:XL_MBES_SBES><ns2:MS_SBES_SSS>0</ns2:MS_SBES_SSS><ns2:MS_SSS>0</ns2:MS_SSS><ns2:MS_SBES>0</ns2:MS_SBES><ns2:MS_SBES_MBES>0</ns2:MS_SBES_MBES><ns2:XL_lidar>0</ns2:XL_lidar><ns2:MS_lidar>0</ns2:MS_lidar><ns2:MS_MBES>143.5</ns2:MS_MBES><ns2:MS_MBES_SSS>0</ns2:MS_MBES_SSS></ns2:statistics><ns2:hullID>2801</ns2:hullID></ns2:vessel><ns2:vessel><ns2:statistics><ns2:XL_MBES_SBES>0</ns2:XL_MBES_SBES><ns2:MS_SBES_SSS>0</ns2:MS_SBES_SSS><ns2:MS_SSS>0</ns2:MS_SSS><ns2:MS_SBES>0</ns2:MS_SBES><ns2:MS_SBES_MBES>0</ns2:MS_SBES_MBES><ns2:XL_lidar>0</ns2:XL_lidar><ns2:MS_lidar>0</ns2:MS_lidar><ns2:MS_MBES>152.0</ns2:MS_MBES><ns2:MS_MBES_SSS>0</ns2:MS_MBES_SSS></ns2:statistics><ns2:hullID>2802</ns2:hullID></ns2:vessel><ns2:vessel><ns2:statistics><ns2:XL_MBES_SBES>20.3</ns2:XL_MBES_SBES><ns2:MS_SBES_SSS>0</ns2:MS_SBES_SSS><ns2:MS_SSS>0</ns2:MS_SSS><ns2:MS_SBES>0</ns2:MS_SBES><ns2:MS_SBES_MBES>0</ns2:MS_SBES_MBES><ns2:XL_lidar>0</ns2:XL_lidar><ns2:MS_lidar>0</ns2:MS_lidar><ns2:MS_MBES>52.5</ns2:MS_MBES><ns2:MS_MBES_SSS>0</ns2:MS_MBES_SSS></ns2:statistics><ns2:hullID>2803</ns2:hullID></ns2:vessel><ns2:vessel><ns2:statistics><ns2:XL_MBES_SBES>3.9</ns2:XL_MBES_SBES><ns2:MS_SBES_SSS>0</ns2:MS_SBES_SSS><ns2:MS_SSS>0</ns2:MS_SSS><ns2:MS_SBES>0</ns2:MS_SBES><ns2:MS_SBES_MBES>0</ns2:MS_SBES_MBES><ns2:XL_lidar>0</ns2:XL_lidar><ns2:MS_lidar>0</ns2:MS_lidar><ns2:MS_MBES>256.8</ns2:MS_MBES><ns2:MS_MBES_SSS>0</ns2:MS_MBES_SSS></ns2:statistics><ns2:hullID>2804</ns2:hullID></ns2:vessel></ns2:vesselLNM></ns2:LNM><ns2:totalSurveyStats><ns2:maritimeBoundaryPoints>0</ns2:maritimeBoundaryPoints><ns2:SNM>16.5</ns2:SNM><ns2:diveOps>0</ns2:diveOps><ns2:bottomSamples>6</ns2:bottomSamples><ns2:DP>155</ns2:DP></ns2:totalSurveyStats></ns1:surveyStatistics><ns1:surveyQuality><ns2:discussion>Data were acquired within assigned survey limits as required in the Project Instructions and HSSD unless otherwise noted in this report.

Pydro QC Tools 2 Grid QA was used to analyze H12999 multibeam echosounder (MBES) data density.  The submitted H12999 variable-resolution (VR) surface met HSSD density requirements.</ns2:discussion><ns2:adequacy>The entire survey is adequate to supersede previous data.</ns2:adequacy><ns2:images><ns2:link>SupportFiles\H12999_MB_VR_MLLW_Final.QAv5.density.png</ns2:link><ns2:caption>Pydro derived histogram plot showing HSSD density compliance of H12999 finalized variable-resolution MBES data.</ns2:caption></ns2:images><ns2:comments/></ns1:surveyQuality><ns1:surveyCoverage><ns2:coverageRequirement><ns2:waterDepth>All waters in survey area except for H12997 and designated S-57 cvrage areas</ns2:waterDepth><ns2:requiredCoverage>Complete Coverage (refer to HSSD Section 5.2.2.3). Note All MBES acquisition requires backscatter acquistion (refer to HSSD Section 6.2)</ns2:requiredCoverage></ns2:coverageRequirement><ns2:results deviation="true"><ns2:discussion>Complete multibeam echosounder (MBES) coverage was acquired to the inshore limit of hydrography, the Navigable Area Limit Line (NALL).  In areas where survey coverage did not reach the 4-meter depth contour nor the assigned sheet limits, it was due to the survey vessle reaching the inshore extent of safe navigation as shown in the figure below.  These areas were generally located very near shore, were subject to dangerous wave action and other hazards.</ns2:discussion><ns2:images><ns2:link>SupportFiles\H12999_NALL.jpg</ns2:link><ns2:caption>Examples of H12999 NALL determination.</ns2:caption></ns2:images></ns2:results><ns2:comments/></ns1:surveyCoverage><ns1:areaDescription><ns2:discussion>The survey area is referred to as &quot;Kalsin Bay&quot; (sheet 4) within the Project Instructions.  The area encompasses approximately 17 square nautical miles extending from Broad Point to Isthmus Point and southwest to the head of Kalsin Bay.</ns2:discussion><ns2:images><ns2:link>SupportFiles\H12999_Survey_Area_Overview_and_Inset.jpg</ns2:link><ns2:caption>H12999 assigned survey area.</ns2:caption></ns2:images><ns2:comments/><ns2:limits><ns2:southEast><ns2:latitude hemisphere="N">57.588126</ns2:latitude><ns2:longitude hemisphere="W">152.296797</ns2:longitude></ns2:southEast><ns2:northWest><ns2:latitude hemisphere="N">57.707464</ns2:latitude><ns2:longitude hemisphere="W">152.474055</ns2:longitude></ns2:northWest></ns2:limits></ns1:areaDescription><ns1:surveyPurpose><ns2:discussion>The area of Chiniak Bay supports the second busiest and third richest fisheries port in Alaska.  In 2015, the Port of Kodiak was responsible for 515 million pounds of fish and $138 million dollars of product.  Chiniak Bay is the gateway to Kodiak and has a survey vintage of 1933.  This area has seen many groundings and near misses due to the number of dangers to navigation and submerged pinnacles that exist in this area.  The navigation of this area is further complicated by the number of vessels trying to enter and exit the Port of Kodiak via a choke point located at the channel entrance buoy.  In recent years a number of groundings in and around the area have occurred, the most famous being a 174 foot long Army landing craft that was outbound to deliver goods to a remote village in western AK in 2012.  This survey will serve to update the nautical charts with modern data to support safe navigation.</ns2:discussion><ns2:comments/></ns1:surveyPurpose><ns1:surveyLimits><ns2:results deviation="true"><ns2:discussion>Data were acquired within survey limits as required in the Project Instructions and HSSD unless otherwise noted in this report.</ns2:discussion></ns2:results><ns2:comments/></ns1:surveyLimits></ns1:areaSurveyed><ns1:metadata><ns1:projectMetadata><ns2:number>OPR-P136-RA-17</ns2:number><ns2:fieldUnit>NOAA Ship RAINIER</ns2:fieldUnit><ns2:generalLocality>Kodiak Island, AK</ns2:generalLocality><ns2:name>North Coast of Kodiak Island</ns2:name></ns1:projectMetadata><ns1:assignment>NOAA</ns1:assignment><ns1:surveyMetadata><ns2:horizontalCoordinateSystem zone="5 North">Universal Transverse Mercator (UTM)</ns2:horizontalCoordinateSystem><ns2:equipmentTypes><ns2:imageryEquipment>Multibeam Echo Sounder Backscatter</ns2:imageryEquipment><ns2:soundingEquipment>Multibeam Echo Sounder</ns2:soundingEquipment></ns2:equipmentTypes><ns2:titlesheetRemarks><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:fieldRemarks xsi:nil="true"></ns2:fieldRemarks></ns2:titlesheetRemarks><ns2:acquisition><ns2:units>meters</ns2:units></ns2:acquisition><ns2:PIDate>2017-03-09</ns2:PIDate><ns2:projectType>Navigable Area</ns2:projectType><ns2:datesOfSurvey><ns2:end>2017-06-30</ns2:end><ns2:start>2017-05-12</ns2:start></ns2:datesOfSurvey><ns2:chiefOfParty>John J. Lomnicky, CDR/NOAA</ns2:chiefOfParty><ns2:year>2017</ns2:year><ns2:timeZone>UTC</ns2:timeZone><ns2:verifier>Atlantic Hydrographic Branch</ns2:verifier></ns1:surveyMetadata><ns1:registryMetadata><ns2:registryNumber>H12999</ns2:registryNumber><ns2:scale>40000</ns2:scale><ns2:country>United States</ns2:country><ns2:registryInstructions>Possible reserve sheet for remote launch party</ns2:registryInstructions><ns2:sheetID>4</ns2:sheetID><ns2:stateOrTerritory>Alaska</ns2:stateOrTerritory><ns2:sublocality>Kalsin Bay</ns2:sublocality></ns1:registryMetadata></ns1:metadata><ns1:dataAcquisitionAndProcessing><ns1:equipmentAndVessels><ns1:comments/><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:discussion xsi:nil="true"></ns1:discussion><ns1:majorSystem><ns2:type>Positioning and Attitude System</ns2:type><ns2:model>POS M/V v5</ns2:model><ns2:manufacturer>Applanix</ns2:manufacturer></ns1:majorSystem><ns1:majorSystem><ns2:type>MBES</ns2:type><ns2:model>SeaBat 7125 SV2</ns2:model><ns2:manufacturer>Reson</ns2:manufacturer></ns1:majorSystem><ns1:majorSystem><ns2:type>MBES</ns2:type><ns2:model>SeaBat 7125-B</ns2:model><ns2:manufacturer>Reson</ns2:manufacturer></ns1:majorSystem><ns1:majorSystem><ns2:type>Sound Speed System</ns2:type><ns2:model>SVP71</ns2:model><ns2:manufacturer>Reson</ns2:manufacturer></ns1:majorSystem><ns1:majorSystem><ns2:type>Conductivity, Temperature, and Depth Sensor</ns2:type><ns2:model>SBE 19plus SEACAT Profiler</ns2:model><ns2:manufacturer>Sea-Bird Electronics</ns2:manufacturer></ns1:majorSystem><ns1:comments/></ns1:equipment><ns1:vessels><ns1:discussion xsi:nil="true"></ns1:discussion><ns1:vessel><ns2:LOA units="meters">8.8</ns2:LOA><ns2:draft units="meters">1.1</ns2:draft><ns2:hullID>2801</ns2:hullID></ns1:vessel><ns1:vessel><ns2:LOA units="meters">8.8</ns2:LOA><ns2:draft units="meters">1.1</ns2:draft><ns2:hullID>2802</ns2:hullID></ns1:vessel><ns1:vessel><ns2:LOA units="meters">8.8</ns2:LOA><ns2:draft units="meters">1.1</ns2:draft><ns2:hullID>2803</ns2:hullID></ns1:vessel><ns1:vessel><ns2:LOA units="meters">8.8</ns2:LOA><ns2:draft units="meters">1.1</ns2:draft><ns2:hullID>2804</ns2:hullID></ns1:vessel><ns1:vessel><ns2:LOA units="meters">5.7</ns2:LOA><ns2:draft units="meters">0.35</ns2:draft><ns2:hullID>1905</ns2:hullID></ns1:vessel><ns1:vessel><ns2:LOA units="meters">5.7</ns2:LOA><ns2:draft units="meters">0.35</ns2:draft><ns2:hullID>1907</ns2:hullID></ns1:vessel><ns1:images><ns2:link>SupportFiles\S221_Rainier.jpg</ns2:link><ns2:caption>NOAA Ship Rainier near Kalsin Bay with survey launches 2803 and 2802 in view.</ns2:caption></ns1:images><ns1:comments/></ns1:vessels></ns1:equipmentAndVessels><ns1:echoSoundingCorrections><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: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:echoSoundingCorrections><ns1:dataProcessing><ns1:drSoftware><ns1:bathySoftware deviation="false"><ns1:version xsi:nil="true"></ns1:version><ns1:manufacturer xsi:nil="true"></ns1:manufacturer><ns1:name xsi:nil="true"></ns1:name></ns1:bathySoftware><ns1:imagerySoftware deviation="false"><ns1:version xsi:nil="true"></ns1:version><ns1:manufacturer xsi:nil="true"></ns1:manufacturer><ns1:name xsi:nil="true"></ns1:name></ns1:imagerySoftware><ns1:comments/><ns1:discussion xsi:nil="true"></ns1:discussion><ns1:featureObjectCatalog>NOAA Extended Attribute Files V_5_5.</ns1:featureObjectCatalog></ns1:drSoftware><ns1:additionalDataProcessing><ns2:comments/></ns1:additionalDataProcessing><ns1:surfaces><ns1:discussion>Submitted surfaces were generated using the recommended parameters for depth-based Caris variable resolution bathymetric grids as specified in HSTD 2017-2.  The resolution values indicated in Table 9 above are not accurate: the XML-DR schema used to generate this report does not accommodate variable resolution grids; the 999 value is obviously spurious and was entered merely as a &quot;place holder.&quot;  The XML-DR team is aware of this issue and are working to update the schema.

A total of thirteen H12999 soundings were designated: eleven as DTONs, and two non-DTON features for inclusion in the H12999_Final_Feature_File.</ns1:discussion><ns1:surface><ns2:surfaceName>H12999_MB_VR_MLLW</ns2:surfaceName><ns2:depthRange><ns2:max units="meters">144.48</ns2:max><ns2:min units="meters">0.12</ns2:min></ns2:depthRange><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:purpose>Complete MBES</ns2:purpose><ns2:resolution units="meters">999</ns2:resolution><ns2:surfaceParameter>VR</ns2:surfaceParameter></ns1:surface><ns1:surface><ns2:surfaceName>H12999_MB_VR_MLLW_Final</ns2:surfaceName><ns2:depthRange><ns2:max units="meters">147.48</ns2:max><ns2:min units="meters">0.12</ns2:min></ns2:depthRange><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:purpose>Complete MBES</ns2:purpose><ns2:resolution units="meters">999</ns2:resolution><ns2:surfaceParameter>VR</ns2:surfaceParameter></ns1:surface><ns1:comments/></ns1:surfaces></ns1:dataProcessing><ns1:qualityControl><ns1:factorsAffectingSoundings><ns2:results deviation="true"><ns2:issue><ns2:discussion>In some nearshore areas, marine vegetation inhibited accurate bottom detection.  In cases where it was possible to discern the true bottom from marine vegetation, the obscuring soundings were rejected.  However, when unable to clearly distinguish between the apparent seafloor and vegetation, no soundings were rejected.</ns2:discussion><ns2:title>Mid-Water Column Acoustic Scatter</ns2:title><ns2:images><ns2:link>SupportFiles\H12999_Marine_Vegetation_Area.jpg</ns2:link><ns2:caption>Example of area where marine vegetation may impede accurate seafloor detection.</ns2:caption></ns2:images><ns2:comments/></ns2:issue></ns2:results><ns2:comments/></ns1:factorsAffectingSoundings><ns1:additionalQualityControl><ns2:comments/></ns1:additionalQualityControl><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:equipmentEffectiveness><ns2:results deviation="false"><ns2:issue><ns2:discussion>There were no conditions or deficiencies that affected equipment operational effectiveness.</ns2:discussion><ns2:title>None Exist</ns2:title><ns2:comments/></ns2:issue></ns2:results><ns2:comments/></ns1:equipmentEffectiveness><ns1:crosslines><ns2:discussion>Multibeam crosslines were acquired using Rainier launches 2803 and 2804 across all depth ranges, water masses and boat days that were practical; they are adequate for verifying and evaluating the internal consistency of survey data.  A 4-meter CUBE surface was created using only H12999 mainscheme lines, and a second 4-meter surface was created using only crosslines.  A difference surface was then generated in Caris from which statistics were derived.  For its respective depths, the difference surface was compared to IHO allowable Total Vertical Uncertainty (TVU) standards.  In total, 99.98% of the depth differences between H12999 mainscheme and crossline data met HSSD TVU standards.  The analysis was performed on H12999 MBES data reduced to Mean Lower-Low Water (MLLW) using Ellipsoidally Referenced Zoned Tides (ERZT) methods.</ns2:discussion><ns2:images><ns2:link>SupportFiles\H12999_Crossline_IHO_Compliance_Stats.jpg</ns2:link><ns2:caption>Summary table indicating percentage of difference surface nodes between H12999 mainscheme and crossline data that met HSSD allowable TVU standards.</ns2:caption></ns2:images><ns2:images><ns2:link>SupportFiles\H12999_XLs.jpg</ns2:link><ns2:caption>H12999 crossline surface overlaid on mainscheme tracklines showing good temporal and geographic distribution.</ns2:caption></ns2:images><ns2:comments/></ns1:crosslines><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:uncertainty><ns2:values><ns2:tideUncertainty><ns2:measured units="meters">0</ns2:measured><ns2:zoning units="meters">0.0224</ns2:zoning><ns2:tideMethod>ERS via ERZT</ns2:tideMethod></ns2:tideUncertainty><ns2:soundSpeedUncertainty><ns2:measuredCTD units="meters/second">3</ns2:measuredCTD><ns2:measuredMVP units="meters/second">N/A</ns2:measuredMVP><ns2:hullID>2801, 2802, 2803, 2804</ns2:hullID><ns2:surface units="meters/second">0.15</ns2:surface></ns2:soundSpeedUncertainty></ns2:values><ns2:discussion>Total Propagated Uncertainty (TPU) values for survey H12999 were derived from a combination of fixed values for equipment and vessel characteristics, as well as from field assigned values for sound speed uncertainties.  Tidal uncertainty was accounted for by examining the field generated one thousand-meter resolution separation model and statistically determining a measured value.  A measured uncertainty of 0.0224 meters was entered to account for ERZT processing methods.  See the 2017 DAPR 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 this survey.  Real-time uncertainties from Reson MBES sonars were recorded 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 position were applied in CARIS HIPS using SBET / RMS files generated using POSPac software.

Uncertainty values of submitted finalized grids were calculated in CARIS using &quot;Greater of the Two&quot; of uncertainty and standard deviation (scaled to 95%).  Pydro QC tools 2 were used to analyze H12999 TVU compliance; a histogram plot of the results is shown below.</ns2:discussion><ns2:images><ns2:link>SupportFiles\H12999_MB_VR_MLLW_Final.QAv5.tvu_qc.png</ns2:link><ns2:caption>Pydro derived histogram plot showing TVU compliance of H12999 finalized multi-resolution MBES data.</ns2:caption></ns2:images><ns2:comments/></ns1:uncertainty><ns1:soundSpeedMethods><ns1:images><ns2:link>SupportFiles\H12999_SVP.jpg</ns2:link><ns2:caption>H12999 sound speed cast locations.</ns2:caption></ns1:images><ns1:discussion xsi:nil="true"></ns1:discussion><ns1:castFrequency>Seventy four 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 19plus SEACAT Profilers.  All casts were concatenated into a master file and applied to MBES data using the &quot;Nearest distance within time&quot; (4 hours) profile selection method.</ns1:castFrequency><ns1:comments/></ns1:soundSpeedMethods><ns1:junctions><ns2:junction><ns2:survey><ns2:scale>40000</ns2:scale><ns2:fieldUnit>NOAA Ship RAINIER</ns2:fieldUnit><ns2:year>2017</ns2:year><ns2:relativeLocation>NW</ns2:relativeLocation><ns2:registryNumber>H12998</ns2:registryNumber></ns2:survey><ns2:discussion>The junction with survey H12998 encompassed 0.29 square nautical miles along the northwestern boundary of H12999.  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 H12999 is an average of 0.10 meters deeper than H12998 with a standard deviation of 0.21 meters.  For the respective depths, the difference surface was compared to the allowable TVU standards specified in the HSSD.  In total, 99.85% of the depth differences between H12999 and junction survey H12998 were within allowable uncertainties.</ns2:discussion><ns2:images><ns2:link>SupportFiles\H12999_Junction_H12998_4m_labels.jpg</ns2:link><ns2:caption>H12999 junction survey H12998 showing HSSD TVU compliance.</ns2:caption></ns2:images><ns2:images><ns2:link>SupportFiles\H12999_Diff_H12998_4m_Stats.jpg</ns2:link><ns2:caption>Summary table indicating percentage of nodes that met HSSD allowable TVU standards for the H12999 / H12998 junction.</ns2:caption></ns2:images><ns2:comments/></ns2:junction><ns2:junction><ns2:survey><ns2:scale>40000</ns2:scale><ns2:fieldUnit>NOAA Ship RAINIER</ns2:fieldUnit><ns2:year>2017</ns2:year><ns2:relativeLocation>E</ns2:relativeLocation><ns2:registryNumber>H13000</ns2:registryNumber></ns2:survey><ns2:discussion>The junction with survey H13000 encompassed 0.44 square nautical miles along the eastern boundary of H12999.  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 H12999 was an average of 0.08 meters deeper than H13000 with a standard deviation of 0.21 meters.  For the respective depths, the difference surface was compared to the allowable TVU standards specified in the HSSD.  In total, 99.83% of the depth differences between H12999 and junction survey H13000 were within allowable uncertainties.</ns2:discussion><ns2:images><ns2:link>SupportFiles\H12999_Diff_H13000_labels.jpg</ns2:link><ns2:caption>H12999 junction survey H13000 showing HSSD TVU compliance.</ns2:caption></ns2:images><ns2:images><ns2:link>SupportFiles\H12999_Diff_H13000_Stats.jpg</ns2:link><ns2:caption>Summary table indicating percentage of nodes that met HSSD allowable TVU standards for the H12999 / H13000 junction.</ns2:caption></ns2:images><ns2:comments/></ns2:junction><ns2:junction><ns2:survey><ns2:scale>10000</ns2:scale><ns2:fieldUnit>NOAA Ship RAINIER</ns2:fieldUnit><ns2:year>1999</ns2:year><ns2:relativeLocation>N</ns2:relativeLocation><ns2:registryNumber>H10913</ns2:registryNumber></ns2:survey><ns2:discussion>The junction with survey H10913 encompassed approximately 0.08 square nautical miles along the northern boundary of H12999.  An 8-meter surface of H10913 data was created with Caris Base Editor using the following steps: a point cloud was generated from the H10913.a93 file provided by NOAA's Operations Branch, a Triangulated Irregular Network (TIN) model was created, long edges removed, then used to interpolate the surface.  An 8-meter CUBE surface of H12999 data was created in Caris HIPS, then a difference surface was derived between the two.  Analysis of the 8-meter difference surface indicated that H12999 is an average of 0.07 meters shoaler than H10913 with a standard deviation of 1.37 meters.  H10910 is a 1999 vintage survey, acquired during a time when robust uncertainty calculation and documentation was not standard practice, therefore it was not possible to conduct detailed IHO TVU compliance analysis for this junction.  The relatively high standard deviation of the junction data and the larger depth differences seen, are attributed to the comparatively low resolution of the H10913 data set, high seafloor relief in some areas and the lower quality of the surface along some of its edges.</ns2:discussion><ns2:images><ns2:link>SupportFiles\H12999_Diff_H10913_Junction_8m.jpg</ns2:link><ns2:caption>H12999 / H10913 junction.</ns2:caption></ns2:images><ns2:comments/></ns2:junction><ns2:discussion>Three surveys junction with H12999, two are contemporary and part of project OPR-P136-RA-17, the third was conducted by NOAA Ship Rainier in 1999.</ns2:discussion><ns2:images><ns2:link>SupportFiles\H12999_Junction_Surveys.jpg</ns2:link><ns2:caption>H12999 junction surveys.</ns2:caption></ns2:images><ns2:comments/></ns1:junctions></ns1:qualityControl><ns1:backscatter><ns2:results acquired="true"><ns2:discussion>Raw Backscatter data were logged as .7k files for delivery to NOAA's Pacific Hydrographic Branch.  Although not required at the time this survey was conducted, backscatter data were processed by the field unit and mosaics generated.  One 2-meter resolution mosaic was created for each vessel / frequency, as well as a combined 6-meter resolution mosaic of the entire H12999 survey area.</ns2:discussion></ns2:results><ns2:comments/></ns1:backscatter></ns1:dataAcquisitionAndProcessing><ns1:approvalSheet><ns1:statements><ns1:additionalInfo xsi:nil="true"></ns1:additionalInfo><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: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:statements><ns1:signingPersonnel><ns2:approvalDate>2017-10-02</ns2:approvalDate><ns2:approverTitle>Commanding Officer, NOAA Ship Rainier</ns2:approverTitle><ns2:approverName>John J. Lomnicky, CDR/NOAA</ns2:approverName></ns1:signingPersonnel><ns1:signingPersonnel><ns2:approvalDate>2017-10-02</ns2:approvalDate><ns2:approverTitle>Field Operations Officer, NOAA Ship Rainier</ns2:approverTitle><ns2:approverName>Steven Loy, LT/NOAA</ns2:approverName></ns1:signingPersonnel><ns1:signingPersonnel><ns2:approvalDate>2017-10-02</ns2:approvalDate><ns2:approverTitle>Chief Survey Technician, NOAA Ship Rainier</ns2:approverTitle><ns2:approverName>James B. Jacobson</ns2:approverName></ns1:signingPersonnel><ns1:signingPersonnel><ns2:approvalDate>2017-10-02</ns2:approvalDate><ns2:approverTitle>Senior Survey Technician, NOAA Ship Rainier</ns2:approverTitle><ns2:approverName>B.D. Jackson</ns2:approverName></ns1:signingPersonnel></ns1:approvalSheet><ns1:verticalAndHorizontalControl><ns1:additionalIssues><ns2:comments/></ns1:additionalIssues><ns1:verticalControl><ns2:tideStations><ns2:NWLONGauges><ns2:stationID>9457292</ns2:stationID><ns2:stationName>Kodiak Island, Womens Bay</ns2:stationName></ns2:NWLONGauges></ns2:tideStations><ns2:comments/><ns2:standard_or_ERZT used="true"><ns2:methodsUsed>TCARI</ns2:methodsUsed><ns2:discussion>H12999 shoreline features were tide corrected using a .tid file created in Pydro utilizing the &quot;TCARI TID file via S-57&quot; function then loaded in Caris Notebook.  H12999 MBES data were reduced to MLLW using ERZT processing methods. </ns2:discussion><ns2:correctorFiles><ns2:tideCorrectors><ns2:fileName>P136RA2017.tc</ns2:fileName><ns2:status>Final</ns2:status></ns2:tideCorrectors><ns2:waterLevels><ns2:fileName>H12999_TCARI_Features.tid</ns2:fileName><ns2:status>Final Approved</ns2:status></ns2:waterLevels></ns2:correctorFiles><ns2:finalTides><ns2:dateReceived>2017-07-18</ns2:dateReceived><ns2:dateSubmitted>2017-07-02</ns2:dateSubmitted></ns2:finalTides><ns2:comments/></ns2:standard_or_ERZT><ns2:VDATUM_or_constantSep used="true"><ns2:ellipsoidToChartDatumSepFile><ns2:fileName>H12999_NAD83_MLLW_SEP_1000m.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 was computed between the ellipsoid and MLLW using real-time position measurements observed during the survey relative to the vessel water line and the 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).  The 1000-meter resolution separation model was generated in NAD83 as were the SBETs.  Refer to the Rainier 2017 DAPR for additional imformation.</ns2:discussion><ns2:comments/><ns2:methodsUsed>ERS via ERZT</ns2:methodsUsed></ns2:VDATUM_or_constantSep><ns2:verticalDatum>Mean Lower Low Water</ns2:verticalDatum></ns1:verticalControl><ns1:discussion>Additional information discussing the vertical or horizontal control for this survey can be found in the accompanying HVCR.</ns1:discussion><ns1:horizontalControl><ns2:RTK used="false" xsi:nil="true"/><ns2:comments/><ns2:PPK used="true"><ns2:baseStations><ns2:userInstalledStations><ns2:stationID>Woody</ns2:stationID><ns2:HVCRSiteID>9715</ns2:HVCRSiteID></ns2:userInstalledStations></ns2:baseStations><ns2:discussion>The Wide Area Augmentation System (WAAS) was used for real-time horizontal control for this survey.</ns2:discussion><ns2:methodsUsed>Single Base</ns2:methodsUsed><ns2:comments/></ns2:PPK><ns2:horizontalDatum>North American Datum of 1983 (NAD83)</ns2:horizontalDatum><ns2:projection>Universal Transverse Mercator (UTM) Zone 5 North</ns2:projection><ns2:PPP used="false" xsi:nil="true"/><ns2:DGPS used="false" xsi:nil="true"/></ns1:horizontalControl></ns1:verticalAndHorizontalControl></ns1:descriptiveReport>