<?xml version="1.0" encoding="UTF-8"?><ns1:descriptiveReport xmlns:ns1="http://svn.pydro.noaa.gov/2017/01/DescriptiveReport" xmlns:ns2="http://svn.pydro.noaa.gov/2017/01/AllGlobalTypes" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://svn.pydro.noaa.gov/2017/01/DescriptiveReport http://svn.pydro.noaa.gov/2017/01/DR.xsd"><ns1:metadata><ns1:projectMetadata><ns2:number>OPR-O346-FA-17</ns2:number><ns2:name>Yakutat Bay</ns2:name><ns2:generalLocality>Yakutat Bay</ns2:generalLocality><ns2:fieldUnit>NOAA Ship FAIRWEATHER</ns2:fieldUnit></ns1:projectMetadata><ns1:registryMetadata><ns2:registryNumber>H13070</ns2:registryNumber><ns2:sheetID>2</ns2:sheetID><ns2:registryInstructions xsi:nil="true"></ns2:registryInstructions><ns2:sublocality>Monti Bay</ns2:sublocality><ns2:stateOrTerritory>Alaska</ns2:stateOrTerritory><ns2:country>United States</ns2:country><ns2:scale>40000</ns2:scale></ns1:registryMetadata><ns1:surveyMetadata><ns2:year>2017</ns2:year><ns2:chiefOfParty>CDR Mark Van Waes, NOAA</ns2:chiefOfParty><ns2:projectType>Navigable Area</ns2:projectType><ns2:PIDate>2017-08-10</ns2:PIDate><ns2:datesOfSurvey><ns2:start>2017-09-15</ns2:start><ns2:end>2017-10-29</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="07">Universal Transverse Mercator (UTM)</ns2:horizontalCoordinateSystem><ns2:timeZone>UTC</ns2:timeZone><ns2:verifier>Pacific Hydrographic Branch</ns2:verifier><ns2:titlesheetRemarks><ns2:fieldRemarks xsi:nil="true"></ns2:fieldRemarks><ns2:branchRemarks>The purpose of this survey is to provide contemporary surveys to update National Ocean Service (NOS) nautical charts. All separates are filed with the hydrographic data. Any revisions to the Descriptive Report (DR) generated during office processing are shown in bold red italic text. The processing branch maintains the DR as a field unit product, therefore, all information and recommendations within the body of the DR are considered preliminary unless otherwise noted. The final disposition of surveyed features is represented in the OCS nautical chart update products. All pertinent records for this survey, including the DR, are archived at the National Centers for Environmental Information (NCEI) and can be retrieved via http://www.ncei.noaa.gov/. 
 </ns2:branchRemarks></ns2:titlesheetRemarks></ns1:surveyMetadata><ns1:assignment>NOAA</ns1:assignment></ns1:metadata><ns1:areaSurveyed><ns1:areaDescription><ns2:discussion>The survey area is located in Yakutat Bay within the sub-locality of Monti Bay.</ns2:discussion><ns2:limits><ns2:northWest><ns2:latitude hemisphere="N">59.6002074444</ns2:latitude><ns2:longitude hemisphere="W">139.9601855</ns2:longitude></ns2:northWest><ns2:southEast><ns2:latitude hemisphere="N">59.5090099722</ns2:latitude><ns2:longitude hemisphere="W">139.728802917</ns2:longitude></ns2:southEast></ns2:limits><ns2:images><ns2:caption>H13070 sheet limits (in blue) overlaid onto Chart 16761 and Chart 16760</ns2:caption><ns2:link>SupportFiles\H13070_Sheet_Limits.png</ns2:link></ns2:images><ns2:comments/></ns1:areaDescription><ns1:surveyLimits><ns2:results deviation="true"><ns2:discussion>Data were acquired to the survey limits in accordance with the requirements in the Project Instructions and the April 2017 NOS Hydrographic Surveys Specifications and Deliverables (HSSD), as shown in Figure 1. In all areas where the 4 meter depth contour or the sheet limits were not met, the Navigable Area Limit Line (NALL) was defined as the inshore limit of bathymetry due to risks of maneuvering the vessel.  

In the area around Ocean Cape, the NALL was defined by the presence of large swells and breaking waves, rendering the area unsafe to navigate with the launches (Figure 2).</ns2:discussion><ns2:images><ns2:caption>NALL defined by waves and breakers</ns2:caption><ns2:link>SupportFiles\H13070_NALL_wavesbreakers.png</ns2:link></ns2:images></ns2:results><ns2:comments/></ns1:surveyLimits><ns1:surveyPurpose><ns2:discussion>Yakutat Bay has seen a rapid increase in the number and size of visiting vessels in recent years. Much of this can be attributed to ecotourism amid the area's glaciers, wilderness, and Tongass National Forest. Hubbard Glacier, one of four glaciers which terminate in Disenchantment Bay at the north end of Yakutat Bay, is the largest tidewater glacier in North America. Unlike most other glaciers in Alaska, which are receding, Hubbard’s terminus is predicted to continue advancing during the next several years. As a result of this advancement, and the glacier’s dramatic calving displays, the glacier is likely to draw more vessel traffic for the foreseeable future to an area of shifting moraines and lag deposits. 

Under keel clearance is a risk for the larger cruise ships, which can draft up to 8 meters. Although the bay itself is deep, reaching over 140 fathoms, all traffic has to pass over a glacial terminal moraine, which forms a sill at the mouth of the bay. Near the center of this entrance is a shoal reported to be 6.4 meters (3 ½ fathoms) deep in an area where surveys have not been updated in over 35 years. Royal Caribbean has reported significant chart discrepancies off of the primary route. 

The local community of Yakutat is dependent on barge access for delivery of its supplies and groceries. Their economy is largely timber, subsistence hunting, fishing, and tourism. Modern surveys will increase the safety of all of these activities. The Yakutat Bay survey will provide modern bathymetry to update the 1978 vintage survey data. This will update Coast Survey charts and products, improving maritime safety and protecting the local economy. </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 in H13070 meet multibeam echo sounder (MBES) coverage requirements for complete coverage and object detection coverage, as required by the HSSD. This includes crosslines (see Section B.2.1), NOAA allowable uncertainty (see Section B.2.10), and density requirements (see Section B.2.11). Additional compliance statistics can be found in the Standards and Compliance Review located in Appendix II of this report. </ns2:discussion><ns2:comments/></ns1:surveyQuality><ns1:surveyCoverage><ns2:coverageRequirement><ns2:waterDepth>All waters in survey area</ns2:waterDepth><ns2:requiredCoverage>Complete Coverage</ns2:requiredCoverage></ns2:coverageRequirement><ns2:coverageRequirement><ns2:waterDepth>Extents of 1:10000 US5AK3XM within H13070 Monti Bay</ns2:waterDepth><ns2:requiredCoverage>Object Detection Coverage</ns2:requiredCoverage></ns2:coverageRequirement><ns2:results deviation="true"><ns2:discussion>To ensure that all data meet the requirements listed above and in the HSSD, two surfaces were created for this project. Figure 3 provides an overview of the surface generated for the entirety of the project to meet complete coverage specifications. Figure 4 provides an overview of the surface generated within the extents of ENC US5AK3XM to meet object detection specifications.</ns2:discussion><ns2:images><ns2:caption>H13070 survey coverage overlaid onto Chart 16761 and Chart 16760</ns2:caption><ns2:link>SupportFiles\H13070_Coverage.png</ns2:link></ns2:images><ns2:images><ns2:caption>H13070 surface generated for the Monti Bay inset</ns2:caption><ns2:link>SupportFiles\H13070_Object_Detection_Overview.png</ns2:link></ns2:images></ns2:results><ns2:comments/></ns1:surveyCoverage><ns1:coverageGraphic><ns2:coverageGraphicImage/></ns1:coverageGraphic><ns1:surveyStatistics><ns2:LNM><ns2:vesselLNM><ns2:vessel><ns2:hullID>2806</ns2:hullID><ns2:statistics><ns2:MS_SBES>0</ns2:MS_SBES><ns2:MS_MBES>64.10</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>11.26</ns2:XL_MBES_SBES><ns2:XL_lidar>0</ns2:XL_lidar></ns2:statistics></ns2:vessel><ns2:vessel><ns2:hullID>2807</ns2:hullID><ns2:statistics><ns2:MS_SBES>0</ns2:MS_SBES><ns2:MS_MBES>201.16</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>2808</ns2:hullID><ns2:statistics><ns2:MS_SBES>0</ns2:MS_SBES><ns2:MS_MBES>117.50</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>4.48</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>382.83</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>15.75</ns2:XL_MBES_SBES><ns2:XL_lidar>0</ns2:XL_lidar><ns2:percentXLLNM>4.11</ns2:percentXLLNM></ns2:totalLNM></ns2:LNM><ns2:totalSurveyStats><ns2:bottomSamples>12</ns2:bottomSamples><ns2:maritimeBoundaryPoints>0</ns2:maritimeBoundaryPoints><ns2:DP>0</ns2:DP><ns2:diveOps>0</ns2:diveOps><ns2:SNM>14.4</ns2:SNM></ns2:totalSurveyStats><ns2:surveyDates>2017-09-15</ns2:surveyDates><ns2:surveyDates>2017-09-19</ns2:surveyDates><ns2:surveyDates>2017-09-20</ns2:surveyDates><ns2:surveyDates>2017-09-26</ns2:surveyDates><ns2:surveyDates>2017-09-27</ns2:surveyDates><ns2:surveyDates>2017-09-28</ns2:surveyDates><ns2:surveyDates>2017-09-29</ns2:surveyDates><ns2:surveyDates>2017-09-30</ns2:surveyDates><ns2:surveyDates>2017-10-01</ns2:surveyDates><ns2:surveyDates>2017-10-02</ns2:surveyDates><ns2:surveyDates>2017-10-12</ns2:surveyDates><ns2:surveyDates>2017-10-18</ns2:surveyDates><ns2:surveyDates>2017-10-29</ns2:surveyDates><ns2:discussion xsi:nil="true"></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>2806</ns2:hullID><ns2:LOA units="meters">8.6</ns2:LOA><ns2:draft units="meters">1.1</ns2:draft></ns1:vessel><ns1:vessel><ns2:hullID>2807</ns2:hullID><ns2:LOA units="meters">8.6</ns2:LOA><ns2:draft units="meters">1.1</ns2:draft></ns1:vessel><ns1:vessel><ns2:hullID>2808</ns2:hullID><ns2:LOA units="meters">8.6</ns2:LOA><ns2:draft units="meters">1.1</ns2:draft></ns1:vessel><ns1:discussion xsi:nil="true"></ns1:discussion><ns1:comments/></ns1:vessels><ns1:equipment><ns1:majorSystem><ns2:manufacturer>Kongsberg Maritime</ns2:manufacturer><ns2:model>EM 2040</ns2:model><ns2:type>MBES</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>Sea-Bird Scientific</ns2:manufacturer><ns2:model>SBE 19plus V2</ns2:model><ns2:type>Conductivity, Temperature, and Depth Sensor</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>Teledyne RESON</ns2:manufacturer><ns2:model>SVP 71</ns2:model><ns2:type>Sound Speed System</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>Applanix</ns2:manufacturer><ns2:model>POS MV v5</ns2:model><ns2:type>Positioning and Attitude System</ns2:type></ns1:majorSystem><ns1:discussion>The equipment was installed on the survey platforms as follows: all launches utilize Kongsberg EM 2040 MBES, Teledyne RESON SVP71 surface sound speed sensors, and Sea-Bird Scientific 19plus CTD casts.</ns1:discussion><ns1:comments/></ns1:equipment><ns1:comments/></ns1:equipmentAndVessels><ns1:qualityControl><ns1:crosslines><ns2:discussion>Crosslines were collected, processed and compared in accordance with Section 5.2.4.3 of the HSSD. To evaluate crosslines, a surface using strictly mainscheme lines, and a surface using strictly crosslines were created. From these two surfaces, a difference surface (mainscheme - crosslines = difference surface) was generated (Figure 5), and is submitted in the Separates II Digital Data folder. Statistics show the mean difference between the depths derived from mainscheme data and crossline data was 0.00 and 95% of nodes falling within +/- 0.24 meters (Figure 6). For the respective depths, the difference surface was compared to the allowable NOAA uncertainty standards. In total, 99.93% of the depth differences between H13070 mainscheme and crossline data were within allowable NOAA uncertainties.</ns2:discussion><ns2:images><ns2:caption>Overview of H13070 crosslines</ns2:caption><ns2:link>SupportFiles\H13070_XL_Diff.png</ns2:link></ns2:images><ns2:images><ns2:caption>H13070 crossline and mainscheme difference statistics</ns2:caption><ns2:link>SupportFiles\H13070 Crossline Difference_depth_delta.png</ns2:link></ns2:images><ns2:comments/></ns1:crosslines><ns1:uncertainty><ns2:values><ns2:tideUncertainty><ns2:measured units="meters">0.0</ns2:measured><ns2:zoning units="meters">0.0</ns2:zoning><ns2:tideMethod>TCARI</ns2:tideMethod></ns2:tideUncertainty><ns2:tideUncertainty><ns2:measured units="meters">0.0</ns2:measured><ns2:zoning units="meters">0.13</ns2:zoning><ns2:tideMethod>ERS via PMVD</ns2:tideMethod></ns2:tideUncertainty><ns2:soundSpeedUncertainty><ns2:hullID>280X</ns2:hullID><ns2:measuredCTD units="meters/second">2</ns2:measuredCTD><ns2:measuredMVP units="meters/second">N/A</ns2:measuredMVP><ns2:surface units="meters/second">0.5</ns2:surface></ns2:soundSpeedUncertainty></ns2:values><ns2:discussion>In addition to the usual a priori estimates of uncertainty provided via device models for vessel motion, ERZT, and Poor Man's VDatum (PMVD), real-time and post-processed uncertainty sources were also incorporated into the depth estimates of survey H13070. Real-time uncertainties were provided via EM 2040 MBES data, Applanix Delayed Heave RMS, and TCARI tides. Following post-processing of the real-time vessel motion, recomputed uncertainties of vessel roll, pitch, gyro and navigation were applied in CARIS HIPS and SIPS via a Smoothed Best Estimate of Trajectory (SBET) RMS file generated in Applanix POSPac.</ns2:discussion><ns2:comments/></ns1:uncertainty><ns1:junctions><ns2:discussion>H13070 junctions with two adjacent survey from this project, H13069 and H13073, as shown in Figure 7. Data overlap between H13070 and each adjacent survey was achieved. These areas of overlap between surveys were reviewed with CARIS HIPS and SIPS by surface differencing to assess surface agreement. The junctions with H13070 are generally within the NOAA allowable uncertainty in the area of overlap. For the junctions with H13070, a negative difference indicates H13070 was shoaler, and a positive difference indicates H13070 was deeper.
</ns2:discussion><ns2:images><ns2:caption>Overview of H13070 junction surveys</ns2:caption><ns2:link>SupportFiles\H13070_Junction_Overview.png</ns2:link></ns2:images><ns2:junction><ns2:survey><ns2:registryNumber>H13073</ns2:registryNumber><ns2:scale>20000</ns2:scale><ns2:year>2017</ns2:year><ns2:fieldUnit>NOAA Ship FAIRWEATHER</ns2:fieldUnit><ns2:relativeLocation>NW</ns2:relativeLocation></ns2:survey><ns2:discussion>Surface differencing in CARIS HIPS and SIPS was used to assess junction agreement between the surface generated from H13070 data and the surface generated  from H13073 data. The statistical analysis of the difference surface shows a mean of -0.04 meters with 95% of all nodes having a maximum deviation of +/- 0.44 meters, as seen in Figure 9. It was found that 99.86% of nodes are within the NOAA allowable uncertainty. The largest differences are located on the northern side of the junction, as seen in Figure 8.</ns2:discussion><ns2:images><ns2:caption>Difference surface between H13070 (blue) and junctioning survey H13073 (pink)</ns2:caption><ns2:link>SupportFiles\H13070_Junction_H13073_Diff.png</ns2:link></ns2:images><ns2:images><ns2:caption>Difference surface statistics between H13070 and H13073</ns2:caption><ns2:link>SupportFiles\Junction Difference between H13070 and H13073_depth_delta.png</ns2:link></ns2:images><ns2:comments/></ns2:junction><ns2:junction><ns2:survey><ns2:registryNumber>H13069</ns2:registryNumber><ns2:scale>20000</ns2:scale><ns2:year>2017</ns2:year><ns2:fieldUnit>NOAA Ship FAIRWEATHER</ns2:fieldUnit><ns2:relativeLocation>W</ns2:relativeLocation></ns2:survey><ns2:discussion>Surface differencing in CARIS HIPS and SIPS was used to assess junction agreement between the surface generated from H13070 data and the surface generated from H13069 data (Figure 10). The statistical analysis of the difference surface shows a mean of 0.05 meters with 95% of all nodes having a maximum deviation of +/- 0.26 meters, as seen in Figure 11. It was found that 99.91% of nodes are within the NOAA allowable uncertainty. </ns2:discussion><ns2:images><ns2:caption>Difference surface between H13070 (blue) and junctioning survey H13069 (brown)</ns2:caption><ns2:link>SupportFiles\H13070_Junction_H13069_Diff.png</ns2:link></ns2:images><ns2:images><ns2:caption>Difference surface statistics between H13070 and H13069</ns2:caption><ns2:link>SupportFiles\Junction_Diff_13070_13069_depth_delta.png</ns2:link></ns2:images><ns2:comments/></ns2:junction><ns2:comments/></ns1:junctions><ns1:sonarQCChecks><ns2:results deviation="false"><ns2:discussion>Sonar system quality control checks were conducted as detailed in the quality control section of the DAPR.</ns2:discussion></ns2:results><ns2:comments/></ns1:sonarQCChecks><ns1:equipmentEffectiveness><ns2:results deviation="false"><ns2:issue><ns2:title>None Exist</ns2:title><ns2:discussion>There were no conditions or deficiencies that affected equipment operational effectiveness.</ns2:discussion><ns2:comments/></ns2:issue></ns2:results><ns2:comments/></ns1:equipmentEffectiveness><ns1:factorsAffectingSoundings><ns2:results deviation="false"><ns2:issue><ns2:title>None Exist</ns2:title><ns2:discussion>There were no other factors that affected corrections to soundings.</ns2:discussion><ns2:comments/></ns2:issue></ns2:results><ns2:comments/></ns1:factorsAffectingSoundings><ns1:soundSpeedMethods><ns1:castFrequency>Casts were conducted at a minimum of one every four hours during launch acquisition. Casts were conducted more frequently in areas where the influx of freshwater had an effect on the speed of sound in the water column and when there was a change in surface sound speed greater than two meters per second. All sound speed methods were used as detailed in the DAPR.</ns1:castFrequency><ns1:discussion xsi:nil="true"></ns1:discussion><ns1:comments/></ns1:soundSpeedMethods><ns1:coverageEquipmentAndMethods><ns2:results deviation="false"><ns2:discussion>All equipment and survey methods were used as detailed in the DAPR.</ns2:discussion></ns2:results><ns2:comments/></ns1:coverageEquipmentAndMethods><ns1:additionalQualityControl><ns2:issue><ns2:title>Holidays</ns2:title><ns2:discussion>H13070 data were reviewed in CARIS HIPS and SIPS for holidays in accordance with Section 5.2.2.3 of the HSSD. The Pydro QC Tools Holiday Finder tool, which automatically scans surfaces for holidays as defined in the HSSD, was run independently for the complete coverage surface generated from the entirety of the data acquired within H13070, as well as for the object detection surface generated from the data acquired within the Monti Bay inset, adjusting the holiday thresholds accordingly.

Two holidays which meet the definition described in HTD 2017-2 for complete coverage were identified via the Holiday Finder tool in the areas where data were acquired to complete coverage standards. Holiday &quot;1&quot; is a result of shadowing from an object on the seafloor, while holiday &quot;2&quot; is a result of data being rejected upon conversion in CARIS HIPS and SIPS due to flags from realtime analysis by the sonar.  The data over holiday &quot;2&quot; does capture the least depth, while the coverage surrounding Holiday &quot;1&quot; does not does not confidently capture the least depth.

Two holidays which meet the definition described in HTD 2017-2 for object detection were identified via the Holiday Finder tool in the inset where data were acquired to object detection standards. Both holidays are a result of sparse outerbeam data while defining the NALL, and were in areas deemed unsafe to develop further as shown in Figure 14.</ns2:discussion><ns2:images><ns2:caption>H13070 complete coverage holiday overview</ns2:caption><ns2:link>SupportFiles\H13070_Complete_Coverage_Holidays.png</ns2:link></ns2:images><ns2:images><ns2:caption>H13070 complete coverage holidays shown in Caris subset editor</ns2:caption><ns2:link>SupportFiles\H13070_Complete_Coverage_Holidays_Closeup.png</ns2:link></ns2:images><ns2:images><ns2:caption>H13070 object detection holiday overview</ns2:caption><ns2:link>SupportFiles\H13070_Object_Detection_Holidays.png</ns2:link></ns2:images><ns2:comments/></ns2:issue><ns2:issue><ns2:title>NOAA Allowable Uncertainty</ns2:title><ns2:discussion>The complete coverage surface and the object detection surface generated from H13070 data were independently analyzed via the Pydro QC Tools Grid QA feature to determine compliance with specifications. Overall, more than 99% of the nodes in each surface meet NOAA allowable uncertainty specifications. See the Standards and Compliance Review located in Appendix II for a graphical representation of uncertainty compliance.</ns2:discussion><ns2:comments/></ns2:issue><ns2:issue><ns2:title>Density</ns2:title><ns2:discussion>The complete coverage surface and the object detection surface generated from H13070 data were independently analyzed via the Pydro QC Tools Grid QA feature to determine compliance with specifications. Overall, more than 99% of the nodes in the complete coverage surface meet density specifications. For the object detection surface, 96% of the nodes meet density specifications. See the Standards and Compliance Review located in Appendix II for graphical representations of density compliance for each surface.</ns2:discussion><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>Raw backscatter data were stored in the .all file for the Kongsberg systems. All backscatter data were processed by the field unit via Fledermaus FMGT 7.7.4. All processed mosaics and .gsf files have been submitted to the Pacific Hydrographic Branch. See Figure 15 for a complete mosaic.</ns2:discussion><ns2:images><ns2:caption>H13070 backscatter mosaic</ns2:caption><ns2:link>SupportFiles\H13070_BackscatterMosaic.png</ns2:link></ns2:images></ns2:results><ns2:comments/></ns1:backscatter><ns1:dataProcessing><ns1:drSoftware><ns1:bathySoftware deviation="true"><ns1:manufacturer>Teledyne CARIS</ns1:manufacturer><ns1:name>HIPS and SIPS</ns1:name><ns1:version>10.3.3</ns1:version></ns1:bathySoftware><ns1:imagerySoftware deviation="true"><ns1:manufacturer>QPS</ns1:manufacturer><ns1:name>Fledermaus FMGT</ns1:name><ns1:version>7.7.4</ns1:version></ns1:imagerySoftware><ns1:featureObjectCatalog>NOAA Profile V 5.6</ns1:featureObjectCatalog><ns1:discussion xsi:nil="true"></ns1:discussion><ns1:comments/></ns1:drSoftware><ns1:surfaces><ns1:surface><ns2:surfaceName>H13070_MB_VR_MLLW</ns2:surfaceName><ns2:surfaceType>CARIS VR Surface (CUBE)</ns2:surfaceType><ns2:resolution units="meters">Variable Resolution</ns2:resolution><ns2:depthRange><ns2:min units="meters">0</ns2:min><ns2:max units="meters">109.8</ns2:max></ns2:depthRange><ns2:surfaceParameter>NOAA_VR</ns2:surfaceParameter><ns2:purpose>Complete MBES</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceName>H13070_MB_VR_MLLW_Final</ns2:surfaceName><ns2:surfaceType>CARIS VR Surface (CUBE)</ns2:surfaceType><ns2:resolution units="meters">Variable Resolution</ns2:resolution><ns2:depthRange><ns2:min units="meters">0</ns2:min><ns2:max units="meters">109.8</ns2:max></ns2:depthRange><ns2:surfaceParameter>NOAA_VR</ns2:surfaceParameter><ns2:purpose>Complete MBES</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceName>H13070_MB_VR_ObjectDetection_MLLW</ns2:surfaceName><ns2:surfaceType>CARIS VR Surface (CUBE)</ns2:surfaceType><ns2:resolution units="meters">Variable Resolution</ns2:resolution><ns2:depthRange><ns2:min units="meters">0</ns2:min><ns2:max units="meters">57.2</ns2:max></ns2:depthRange><ns2:surfaceParameter>NOAA_VR</ns2:surfaceParameter><ns2:purpose>Object Detection</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceName>H13070_MB_VR_ObjectDetection_MLLW_Final</ns2:surfaceName><ns2:surfaceType>CARIS VR Surface (CUBE)</ns2:surfaceType><ns2:resolution units="meters">Variable Resolution</ns2:resolution><ns2:depthRange><ns2:min units="meters">0</ns2:min><ns2:max units="meters">57.2</ns2:max></ns2:depthRange><ns2:surfaceParameter>NOAA_VR</ns2:surfaceParameter><ns2:purpose>Object Detection</ns2:purpose></ns1:surface><ns1:discussion>The NOAA CUBE parameters defined in the HSSD were used for the generation of all CUBE surfaces for survey H13070. The surfaces have been reviewed where noisy data, or &quot;fliers,&quot; are incorporated into the gridded solutions causing the surface to be shoaler or deeper than the true sea floor. Where these spurious soundings cause the gridded surface to vary from the reliably measured seabed by greater than the maximum allowable Total Vertical Uncertainty at that depth, the noisy data have been rejected by the hydrographer and the surface recomputed.

Flier Finder v5, part of the QC Tools package within Pydro, was used to assist the search for spurious soundings following gross cleaning. Flier Finder was run iteratively until all remaining flagged fliers were deemed to be valid aspects of the steep slopes and dynamic nature of the seafloor.</ns1:discussion><ns1:comments/></ns1:surfaces><ns1:additionalDataProcessing><ns2:issue><ns2:title>Data Logs</ns2:title><ns2:discussion>Data acquisition and processing notes are included in the acquisition and processing logs, and additional processing such as final tide and sound speed application are noted in the H13070 Data Log spreadsheet. All data logs are submitted digitally in the Separates I folder.</ns2:discussion><ns2:comments/></ns2:issue><ns2:comments/></ns1:additionalDataProcessing></ns1:dataProcessing></ns1:dataAcquisitionAndProcessing><ns1:verticalAndHorizontalControl><ns1:discussion>Per section 5.1.2.3 of the Field Procedures Manual (2014 ed), no Horizontal and Vertical Control Report has
been generated for H13070.</ns1:discussion><ns1:verticalControl><ns2:verticalDatum>Mean Lower Low Water</ns2:verticalDatum><ns2:tideStations><ns2:NWLONGauges><ns2:stationName>Yakutat, AK</ns2:stationName><ns2:stationID>9453220</ns2:stationID></ns2:NWLONGauges></ns2:tideStations><ns2:standard_or_ERZT used="true"><ns2:methodsUsed>TCARI</ns2:methodsUsed><ns2:correctorFiles><ns2:waterLevels><ns2:fileName>9453220.tid</ns2:fileName><ns2:status>Final Approved</ns2:status></ns2:waterLevels><ns2:tideCorrectors><ns2:fileName>O346FA2017.tc</ns2:fileName><ns2:status>Final</ns2:status></ns2:tideCorrectors></ns2:correctorFiles><ns2:finalTides><ns2:dateSubmitted>2017-11-01</ns2:dateSubmitted><ns2:dateReceived>2017-11-21</ns2:dateReceived></ns2:finalTides><ns2:discussion>Initial reduction of acquired data to MLLW was accomplished via traditional tidal means using the Tidal Constituent And Residual Interpolation (TCARI) grid provided by HSD-OPS. Following the successful application of SBETs and computation of an Ellipsoidally Referenced Zone Tide (ERZT) separation model, ERS methods were used for reducing data to MLLW. 

After final tides were received, the final TCARI grids were applied to the data and used for reducing features to MLLW.</ns2:discussion><ns2:comments/></ns2:standard_or_ERZT><ns2:VDATUM_or_constantSep used="true"><ns2:methodsUsed>ERS via Poor Mans VDATUM</ns2:methodsUsed><ns2:ellipsoidToChartDatumSepFile><ns2:fileName>O346FA2017_PMVD_EPSG6332_NAD83_MLLW_Debiased.csar</ns2:fileName></ns2:ellipsoidToChartDatumSepFile><ns2:discussion>ERS methods were used as the final means of reducing H13070 to MLLW for submission. Data were initially reduced via traditional tidal means until an ERZT separation model could be calculated. This empirically derived model was then checked for consistency and compared to the Poor Man's VDatum (PMVD) separation model provided with the Project Instructions. The PMVD separation model was then vertically shifted such that the average difference between these two separation models is zero. This vertical shift de-biases the PMVD separation model, correcting for local offsets that cannot be effectively modeled by the PMVD.</ns2:discussion><ns2:comments/></ns2:VDATUM_or_constantSep><ns2:comments/></ns1:verticalControl><ns1:horizontalControl><ns2:horizontalDatum>North American Datum of 1983 (NAD83)</ns2:horizontalDatum><ns2:projection>UTM Zone 7 North</ns2:projection><ns2:PPK used="false" xsi:nil="true"/><ns2:PPP used="false" xsi:nil="true"/><ns2:RTK used="false" xsi:nil="true"/><ns2:DGPS used="false" xsi:nil="true"/><ns2:WAAS used="true"><ns2:discussion>Vessel kinematic data were post-processed using Applanix POSPac processing software and RTX methods described in the DAPR. Smoothed Best Estimate of Trajectory (SBET) and associated error (RMS) data were applied to all MBES data in CARIS HIPS and SIPS.

For further details regarding the processing and quality control checks performed, see the H13070 POSPac Processing Logs spreadsheet located in the Separates folder. </ns2:discussion><ns2:comments/></ns2:WAAS><ns2:comments/></ns1:horizontalControl><ns1:additionalIssues><ns2:issue><ns2:title>Horizontal Control Issue</ns2:title><ns2:discussion>During real-time acquisition, launches 2806, 2807, and 2808 received correctors from the Wide Area Augmentation System (WAS) for increased accuracies similar to USCG DIPS stations. WAS and S Bets were the sole methods of positioning for H13070 as no DIPS stations were available for real-time horizontal control.</ns2:discussion><ns2:comments/></ns2:issue><ns2:comments/></ns1:additionalIssues></ns1:verticalAndHorizontalControl><ns1:resultsAndRecommendations><ns1:chartComparison><ns1:methods><ns2:discussion>A comparison was performed between survey H13070 and ENCs US4AK3XM and US5AK3XM, using CARIS HIPS and SIPS sounding and contour layers derived from the surface generated from H13070 data. The contours and soundings were overlaid on the charts to assess differences between the surveyed soundings and charted depths. An eight meter grid was generated from each ENC by extracting all soundings from the chart and creating an interpolated TIN surface which could be differenced with the surface generated from H13070 data. All H13070 data should supersede charted data. In general, surveyed soundings agree with the majority of charted depths. A full discussion of the comparisons follows below.</ns2:discussion><ns2:comments/></ns1:methods><ns1:charts><ns2:ENC><ns2:chart><ns2:name>US4AK3XM</ns2:name><ns2:scale>80000</ns2:scale><ns2:edition>5</ns2:edition><ns2:updateApplicationDate>2018-02-13</ns2:updateApplicationDate><ns2:issueDate>2018-02-13</ns2:issueDate><ns2:preliminary>false</ns2:preliminary></ns2:chart><ns2:discussion>Soundings from H13070 are in general agreement with charted depths on chart ENC US4AK3XM, with most depths agreeing to 1-4 fathoms.  The largest differences are seen in the entrance to Monti Bay, where the charted contours differ so greatly that they were submitted as a DTON (see section D.1.5 and Appendix II of this report for more detailed discussions).</ns2:discussion><ns2:images><ns2:caption>Difference surface between H13070 and interpolated TIN surface from US4AK3XM</ns2:caption><ns2:link>SupportFiles\H13070_Difference_US4AK3XM.png</ns2:link></ns2:images><ns2:images><ns2:caption>Difference surface statistics between H13070 and interpolated TIN surface from US4AK3XM</ns2:caption><ns2:link>SupportFiles\H13070_US4AK3XM_difference statistics.png</ns2:link></ns2:images><ns2:images><ns2:caption>Overview of H13070 contours overlaid onto ENC US4AK3XM.</ns2:caption><ns2:link>SupportFiles\H13070_CC_ContourComparison_Overview.png</ns2:link></ns2:images><ns2:images><ns2:caption>Close up of Monti Bay where significant differences exist between H13070 contours and ENC US4AK3XM contours.</ns2:caption><ns2:link>SupportFiles\H13070_CC_ContourComparison.png</ns2:link></ns2:images><ns2:comments/></ns2:ENC><ns2:ENC><ns2:chart><ns2:name>US5AK3XM</ns2:name><ns2:scale>10000</ns2:scale><ns2:edition>3</ns2:edition><ns2:updateApplicationDate>2016-11-21</ns2:updateApplicationDate><ns2:issueDate>2016-11-21</ns2:issueDate><ns2:preliminary>false</ns2:preliminary></ns2:chart><ns2:discussion>Soundings from H13070 are in general agreement with charted depths on ENC US5AK3XM, with most depths agreeing to 1-2 fathoms.  </ns2:discussion><ns2:images><ns2:caption>Difference surface between H13070 and interpolated TIN surface from US5AK3XM</ns2:caption><ns2:link>SupportFiles\H13070_Difference_US5AK3XM.png</ns2:link></ns2:images><ns2:images><ns2:caption>Difference surface statistics between H13070 and interpolated TIN surface from US5AK3XM</ns2:caption><ns2:link>SupportFiles\H13070_OD_diff_TINsur_US5AK3XM_Diff.png</ns2:link></ns2:images><ns2:images><ns2:caption>Overview of H13070 contours overlaid onto ENC US5AK3XM.</ns2:caption><ns2:link>SupportFiles\H13070_OD_ContourComparison_Overview.png</ns2:link></ns2:images><ns2:comments/></ns2:ENC><ns2:comments/></ns1:charts><ns1:maritimeBoundary><ns2:results investigated="None Exist"><ns2:discussion>No Maritime Boundary Points were assigned for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:maritimeBoundary><ns1:chartedFeatures><ns2:results investigated="Investigated"><ns2:discussion>H13070 data covers a four fathom shoal that was reported in 2012.  The surveyed area did not show any depths which support this reported sounding, nor are their any significant features in the surrounding area.  The hydrographer recommends replacing the reported sounding with charted depths.</ns2:discussion><ns2:images><ns2:caption>Reported sounding in H13070 (surveyed soundings in red)</ns2:caption><ns2:link>SupportFiles\H13070_ReportedSounding_ChartedFeature.png</ns2:link></ns2:images></ns2:results><ns2:comments/></ns1:chartedFeatures><ns1:unchartedFeatures><ns2:results investigated="None Exist"><ns2:discussion>No uncharted features exist for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:unchartedFeatures><ns1:shoalAndHazardousFeatures><ns2:results investigated="Investigated"><ns2:discussion>A significant discrepancy between the charted contours and surveyed depths was observed during acquisition, prompting one Danger to Navigation Report to be submitted on 11/7/2017 (Figure 24). Surveyed data revealed the 3 fathom contour lies outside of the charted 10 fathom contour line. Additionally, in this area the intertidal zone extends as much as 450 meters from the charted shoreline. The Danger to Navigation Report is included in Appendix II of this report. 

While surveying the area South of Pt. Mulgrove, a shoal area was defined by the 4 meter contour (Figure 25). During shoreline investigation, no features were observed in this area above the surface, and a least depth was unable to safely be obtained within the ensuing gap in coverage. Caution is advised to mariners transiting the area.</ns2:discussion><ns2:images><ns2:caption>Overview of DTON found in entrance to Monti Bay</ns2:caption><ns2:link>SupportFiles\H13070_DTON_Overview.png</ns2:link></ns2:images><ns2:images><ns2:caption>Shoal area south of Pt. Mulgrove with gap in survey coverage</ns2:caption><ns2:link>SupportFiles\H13070_GapinCoverage.png</ns2:link></ns2:images></ns2:results><ns2:comments><ns2:branchComment concurrence="Concur with clarification"><ns2:comment>The field-submitted DTON will be applied to the chart once the survey has been reviewed and submitted to MCD.</ns2:comment></ns2:branchComment></ns2:comments></ns1:shoalAndHazardousFeatures><ns1:channels><ns2:results investigated="None Exist"><ns2:discussion>No channels exist for this survey.  There are no precautionary areas, safety fairways, traffic separation schemes, pilot boarding areas, or channel and range lines within the survey limits. The Rurik Harbor designated anchorage northeast of Port Mulgrave was relocated to reflect the description in the Coast Pilot and conditions observed during field operations.</ns2:discussion></ns2:results><ns2:comments/></ns1:channels><ns1:bottomSamples><ns2:results investigated="Investigated"><ns2:discussion>Twelve bottom samples were acquired in accordance with the Project Instructions for survey H13070 and entered in the H13070 Final Feature File. Additional bottom samples were unable to be collected due to time constraints. See Figure 26 for a graphical overview of the location of the bottom samples. </ns2:discussion><ns2:images><ns2:caption>H13070 bottom sample locations</ns2:caption><ns2:link>SupportFiles\H13070_BottomSamples.png</ns2:link></ns2:images></ns2:results><ns2:comments/></ns1:bottomSamples></ns1:chartComparison><ns1:additionalResults><ns1:shoreline><ns2:results investigated="Investigated"><ns2:discussion>All features within the survey limits and the NALL were addressed and attributed in the H13070 Final Feature File. All features inshore of the NALL were attributed in the Final Feature File with the description of &quot;Not Addressed&quot; and remarks of &quot;Retain as charted, not investigated due to being inshore of NALL&quot; as per HSSD Section 7.3.1. Annotations, information, and diagrams collected on DP forms and boat sheets during field operations are scanned and included in the Separates I Detached Positions folder. </ns2:discussion></ns2:results><ns2:comments/></ns1:shoreline><ns1:priorSurveys><ns2:results investigated="None Exist"><ns2:discussion>No prior survey comparisons exist for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:priorSurveys><ns1:ATONS><ns2:results investigated="Investigated"><ns2:discussion>Buoys numbered 1, 2, and 4 are located within H13070 and were observed to be on station and serving their intended purposes.</ns2:discussion></ns2:results><ns2:comments/></ns1:ATONS><ns1:overheadFeatures><ns2:results investigated="None Exist"><ns2:discussion>No overhead features exist for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:overheadFeatures><ns1:submarineFeatures><ns2:results investigated="None Exist"><ns2:discussion>No submarine features exist for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:submarineFeatures><ns1:platforms><ns2:results investigated="None Exist"><ns2:discussion>No platforms exist for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:platforms><ns1:ferryRoutesAndTerminals><ns2:results investigated="Exist - Not Investigated"><ns2:discussion>Ferry routes and/or terminals exist for this survey, but were not investigated.</ns2:discussion></ns2:results><ns2:comments/></ns1:ferryRoutesAndTerminals><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:constructionOrDredging><ns2:results investigated="None Exist"><ns2:discussion>No present or planned construction or dredging exist within the survey limits.</ns2:discussion></ns2:results><ns2:comments/></ns1:constructionOrDredging><ns1:otherResults><ns2:comments/></ns1:otherResults><ns1:newSurveyRecommendation><ns2:results recommended="false"><ns2:discussion>No new surveys or further investigations are recommended for this area.</ns2:discussion></ns2:results><ns2:comments/></ns1:newSurveyRecommendation><ns1:insetRecommendation><ns2:results recommended="false"><ns2:discussion>No new insets are recommended for this area.</ns2:discussion></ns2:results><ns2:comments/></ns1:insetRecommendation></ns1:additionalResults></ns1:resultsAndRecommendations><ns1:approvalSheet><ns1:statements><ns1:supervision>As Chief of Party, field operations for this hydrographic survey were conducted under my direct supervision, with frequent personal checks of progress and adequacy. I have reviewed the attached survey data and reports.</ns1:supervision><ns1:approval>All field sheets, this Descriptive Report, and all accompanying records and data are approved. All records are forwarded for final review and processing to the Processing Branch.</ns1:approval><ns1:adequacyOfSurvey>The survey data meets or exceeds requirements as set forth in the NOS Hydrographic Surveys 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 herein.</ns1:adequacyOfSurvey><ns1:additionalInfo xsi:nil="true"></ns1:additionalInfo></ns1:statements><ns1:signingPersonnel><ns2:approverName>CDR Mark Van Waes</ns2:approverName><ns2:approverTitle>Chief of Party</ns2:approverTitle><ns2:approvalDate>2018-04-13</ns2:approvalDate></ns1:signingPersonnel><ns1:signingPersonnel><ns2:approverName>LT Damian Manda</ns2:approverName><ns2:approverTitle>Field Operations Officer</ns2:approverTitle><ns2:approvalDate>2018-04-13</ns2:approvalDate></ns1:signingPersonnel><ns1:signingPersonnel><ns2:approverName>HCST Samuel Candio</ns2:approverName><ns2:approverTitle>Chief Survey Technician</ns2:approverTitle><ns2:approvalDate>2018-04-13</ns2:approvalDate></ns1:signingPersonnel><ns1:signingPersonnel><ns2:approverName>LTJG Jeffrey Douglas</ns2:approverName><ns2:approverTitle>Sheet Manager</ns2:approverTitle><ns2:approvalDate>2018-04-13</ns2:approvalDate></ns1:signingPersonnel></ns1:approvalSheet></ns1:descriptiveReport>