<?xml version="1.0" encoding="UTF-8"?><ns1:descriptiveReport xmlns:ns1="http://svn.pydro.noaa.gov/2021/01/DescriptiveReport" xmlns:ns2="http://svn.pydro.noaa.gov/2021/01/AllGlobalTypes" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://svn.pydro.noaa.gov/2021/01/DescriptiveReport http://svn.pydro.noaa.gov/2021/01/DR.xsd"><ns1:metadata><ns1:surveyMetadata><ns2:timeZone>UTC</ns2:timeZone><ns2:acquisition><ns2:units>meters</ns2:units></ns2:acquisition><ns2:PIDate>2020-10-21</ns2:PIDate><ns2:chiefOfParty>CDR John Lomnicky</ns2:chiefOfParty><ns2:equipmentTypes><ns2:soundingEquipment>Multibeam Echo Sounder</ns2:soundingEquipment><ns2:imageryEquipment>Multibeam Echo Sounder Backscatter</ns2:imageryEquipment></ns2:equipmentTypes><ns2:year>2020</ns2:year><ns2:datesOfSurvey><ns2:start>2020-11-22</ns2:start><ns2:end>2020-12-06</ns2:end></ns2:datesOfSurvey><ns2:projectType>Navigable Area</ns2:projectType><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 10N, 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:verifier>Pacific Hydrographic Branch</ns2:verifier></ns1:surveyMetadata><ns1:projectMetadata><ns2:number>OPR-N305-FA-20</ns2:number><ns2:generalLocality>Approaches to Puget Sound</ns2:generalLocality><ns2:name>Strait of Juan de Fuca, WA</ns2:name><ns2:fieldUnit>NOAA Ship Fairweather (S220)</ns2:fieldUnit></ns1:projectMetadata><ns1:registryMetadata><ns2:scale>5000</ns2:scale><ns2:registryInstructions xsi:nil="true"></ns2:registryInstructions><ns2:registryNumber>H13412</ns2:registryNumber><ns2:stateOrTerritory>Washington</ns2:stateOrTerritory><ns2:country>United States</ns2:country><ns2:sublocality>Kydaka Point to Neah Bay</ns2:sublocality><ns2:sheetID>1</ns2:sheetID></ns1:registryMetadata><ns1:assignment>NOAA</ns1:assignment></ns1:metadata><ns1:areaSurveyed><ns1:surveyStatistics><ns2:comments/><ns2:totalSurveyStats><ns2:diveOps>0</ns2:diveOps><ns2:DP>0</ns2:DP><ns2:SNM>29.46</ns2:SNM><ns2:maritimeBoundaryPoints>0</ns2:maritimeBoundaryPoints><ns2:bottomSamples>6</ns2:bottomSamples></ns2:totalSurveyStats><ns2:discussion xsi:nil="true"></ns2:discussion><ns2:LNM><ns2:totalLNM><ns2:MS_MBES>568.49</ns2:MS_MBES><ns2:percentXLLNM>4.42</ns2:percentXLLNM><ns2:MS_SBES_SSS>0</ns2:MS_SBES_SSS><ns2:MS_MBES_SSS>0</ns2:MS_MBES_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:XL_MBES_SBES>24.07</ns2:XL_MBES_SBES></ns2:totalLNM><ns2:vesselLNM><ns2:vessel><ns2:statistics><ns2:MS_MBES>90.38</ns2:MS_MBES><ns2:MS_SBES_SSS>0</ns2:MS_SBES_SSS><ns2:MS_MBES_SSS>0</ns2:MS_MBES_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:XL_MBES_SBES>10.37</ns2:XL_MBES_SBES></ns2:statistics><ns2:hullID>FA 2805</ns2:hullID></ns2:vessel><ns2:vessel><ns2:statistics><ns2:MS_MBES>71.57</ns2:MS_MBES><ns2:MS_SBES_SSS>0</ns2:MS_SBES_SSS><ns2:MS_MBES_SSS>0</ns2:MS_MBES_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:XL_MBES_SBES>0</ns2:XL_MBES_SBES></ns2:statistics><ns2:hullID>FA 2807</ns2:hullID></ns2:vessel><ns2:vessel><ns2:statistics><ns2:MS_MBES>130.38</ns2:MS_MBES><ns2:MS_SBES_SSS>0</ns2:MS_SBES_SSS><ns2:MS_MBES_SSS>0</ns2:MS_MBES_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:XL_MBES_SBES>13.69</ns2:XL_MBES_SBES></ns2:statistics><ns2:hullID>FA 2808</ns2:hullID></ns2:vessel><ns2:vessel><ns2:statistics><ns2:MS_MBES>252.10</ns2:MS_MBES><ns2:MS_SBES_SSS>0</ns2:MS_SBES_SSS><ns2:MS_MBES_SSS>0</ns2:MS_MBES_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:XL_MBES_SBES>0</ns2:XL_MBES_SBES></ns2:statistics><ns2:hullID>S220</ns2:hullID></ns2:vessel></ns2:vesselLNM></ns2:LNM><ns2:surveyDates>2020-11-22</ns2:surveyDates><ns2:surveyDates>2020-11-23</ns2:surveyDates><ns2:surveyDates>2020-11-28</ns2:surveyDates><ns2:surveyDates>2020-11-29</ns2:surveyDates><ns2:surveyDates>2020-11-30</ns2:surveyDates><ns2:surveyDates>2020-12-01</ns2:surveyDates><ns2:surveyDates>2020-12-02</ns2:surveyDates><ns2:surveyDates>2020-12-03</ns2:surveyDates><ns2:surveyDates>2020-12-04</ns2:surveyDates><ns2:surveyDates>2020-12-06</ns2:surveyDates></ns1:surveyStatistics><ns1:surveyPurpose><ns2:comments/><ns2:topic><ns2:discussion>This 30 square nautical mile project is located within the Strait of Juan de Fuca, WA, a major coastal waterway within the Salish Sea. This area is a navigationally significant waterway within the Salish Sea, which supports transits of deep-draft container ships, cargo and chemical carriers, oil tankers, fuel and coal barges arriving and departing from Puget Sound and Vancouver, Canada along with fishing, recreational, tug and barge vessels, and Washington State Ferries. Furthermore, the region is home to 8 million people including fifty First Nation communities with centuries old cultural ties to traditional fishing. 

This project will occur within the Makah Tribe Usual and Accustomed Fishing Area that includes the Neah Bay emergency tugboat marina and 5 SNM of the Olympic Coast National Marine Sanctuary. The majority of the area was last surveyed in the 1940s and 1960s, with Neah Bay surveyed in 2000.  This project will provide modern bathymetry for updating National Ocean Service Nautical charting products improving maritime safety in this navigationally busy region as well as support the Seabed 2030 global mapping initiative.</ns2:discussion></ns2:topic></ns1:surveyPurpose><ns1:surveyCoverage><ns2:comments/><ns2:results deviation="true"><ns2:images><ns2:caption>H13412 survey coverage overlaid onto Chart 18460</ns2:caption><ns2:link>SupportFiles\DR Coverage and Sheet Limits.PNG</ns2:link></ns2:images><ns2:discussion>The entirety of H13412 was acquired with complete coverage, meeting the requirements listed above and in the HSSD. See Figure 3 for an overview of coverage.</ns2:discussion></ns2:results><ns2:coverageRequirement><ns2:requiredCoverage>Complete Coverage </ns2:requiredCoverage><ns2:waterDepth>All waters in survey area</ns2:waterDepth></ns2:coverageRequirement></ns1:surveyCoverage><ns1:surveyLimits><ns2:comments/><ns2:results deviation="true"><ns2:images><ns2:caption>NALL Defined by Rocks and Kelp</ns2:caption><ns2:link>SupportFiles\Nall Def.png</ns2:link></ns2:images><ns2:discussion>Data were acquired to the survey limits in accordance with the requirements in the Project Instructions and the 2020 NOS Hydrographic Surveys Specifications and Deliverables (HSSD). Coverage acquired in H13412 is shown in Figure 1. In all areas where the 3.5 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 the risks of maneuvering the survey vessel in close proximity to the dense kelp beds or intermittent volcanic rocky shoreline   and at Hydrographers discretion due to dangerous swell. An example of such an area is shown in Figure 2.
</ns2:discussion></ns2:results></ns1:surveyLimits><ns1:areaDescription><ns2:comments/><ns2:images><ns2:caption>H13412 sheet limits (in blue) overlaid onto Chart 18460</ns2:caption><ns2:link>SupportFiles\H13412 Sheet Limits.PNG</ns2:link></ns2:images><ns2:discussion>The survey area is located from Kydaka Point to Neah Bay, Washington.</ns2:discussion><ns2:limits><ns2:southEast><ns2:longitude hemisphere="W">124.3102</ns2:longitude><ns2:latitude hemisphere="N">48.2753138889</ns2:latitude></ns2:southEast><ns2:northWest><ns2:longitude hemisphere="W">124.6897</ns2:longitude><ns2:latitude hemisphere="N">48.4174805556</ns2:latitude></ns2:northWest></ns2:limits></ns1:areaDescription><ns1:coverageGraphic><ns2:coverageGraphicImage/></ns1:coverageGraphic><ns1:surveyQuality><ns2:comments/><ns2:discussion>Data acquired in H13412 meet multibeam echo sounder (MBES) coverage requirements for complete 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).</ns2:discussion><ns2:adequacy>The entire survey is adequate to supersede previous data.</ns2:adequacy></ns1:surveyQuality></ns1:areaSurveyed><ns1:verticalAndHorizontalControl><ns1:horizontalControl><ns2:comments/><ns2:PPP used="false" xsi:nil="true"/><ns2:PPK used="true"><ns2:methodsUsed>RTX</ns2:methodsUsed><ns2:baseStations/><ns2:discussion>Vessel kinematic data were post-processed using Applanix POSPac processing software and RTX positioning 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.</ns2:discussion><ns2:comments/></ns2:PPK><ns2:RTK used="false" xsi:nil="true"/><ns2:horizontalDatum>North American Datum 1983</ns2:horizontalDatum><ns2:WAAS used="true"><ns2:comments/><ns2:discussion>During real-time acquisition, all platforms received correctors from the Wide Area Augmentation System (WAAS) for increased accuracies similar to USCG DGPS stations. WAAS and SBETs were the sole methods of positioning for H13412 as no DGPS stations were available for real-time horizontal control.</ns2:discussion></ns2:WAAS><ns2:projection>Projected UTM 10</ns2:projection><ns2:DGPS used="false" xsi:nil="true"/></ns1:horizontalControl><ns1:verticalControl><ns2:comments/><ns2:VDATUM_or_constantSep used="true"><ns2:ellipsoidToChartDatumSepFile><ns2:fileName>OPR-N305-RA-20_sheetsuffforVdat__100m_NAD83-MLLW_geoid12b.csar</ns2:fileName></ns2:ellipsoidToChartDatumSepFile><ns2:comments/><ns2:discussion>ERS methods were used as the final means of reducing H13412 to MLLW for submission.</ns2:discussion><ns2:methodsUsed>ERS via VDATUM</ns2:methodsUsed></ns2:VDATUM_or_constantSep><ns2:standard_or_ERZT used="false" xsi:nil="true"/><ns2:tideStations/><ns2:verticalDatum>Mean Lower Low Water</ns2:verticalDatum></ns1:verticalControl><ns1:additionalIssues><ns2:comments/></ns1:additionalIssues><ns1:discussion>Per Section 5.2.2.1.3 of the 2020 Field Procedures Manual no Horizontal and Vertical Control Report has been generated for H13412.</ns1:discussion></ns1:verticalAndHorizontalControl><ns1:dataAcquisitionAndProcessing><ns1:equipmentAndVessels><ns1:comments/><ns1:vessels><ns1:vessel><ns2:LOA units="meters">70.4</ns2:LOA><ns2:hullID>S220</ns2:hullID><ns2:draft units="meters">4.8</ns2:draft></ns1:vessel><ns1:vessel><ns2:LOA units="meters">8.6</ns2:LOA><ns2:hullID>2805</ns2:hullID><ns2:draft units="meters">1.1</ns2:draft></ns1:vessel><ns1:vessel><ns2:LOA units="meters">8.6</ns2:LOA><ns2:hullID>2807</ns2:hullID><ns2:draft units="meters">1.1</ns2:draft></ns1:vessel><ns1:vessel><ns2:LOA units="meters">8.6</ns2:LOA><ns2:hullID>2808</ns2:hullID><ns2:draft units="meters">1.1</ns2:draft></ns1:vessel><ns1:comments/><ns1:discussion xsi:nil="true"></ns1:discussion></ns1:vessels><ns1:equipment><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>EM 710</ns2:model><ns2:manufacturer>Kongsberg Maritime</ns2:manufacturer><ns2:type>MBES</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:model>SBE 19plus V2</ns2:model><ns2:manufacturer>Sea-Bird Scientific</ns2:manufacturer><ns2:type>Conductivity, Temperature, and Depth Sensor</ns2:type></ns1:majorSystem><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>MVP200</ns2:model><ns2:manufacturer>AML Oceanographic</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>SVP 71</ns2:model><ns2:manufacturer>Teledyne RESON</ns2:manufacturer><ns2:type>Sound Speed System</ns2:type></ns1:majorSystem><ns1:comments/><ns1:discussion>The equipment was installed on the survey platform as follows: S220 utilizes the Kongsberg EM 710 MBES, a POS M/V v5 system for position and attitude, SVP 70 surface sound speed sensors, and AML Oceanographic MVP 200 for conductivity, temperature, and depth (CTD) casts. All launches utilize the Kongsberg EM 2040 MBES, a POS M/V v5 system for positon and attitude, SVP 71 surface sound speed sensors, and Sea-Bird SBE 19plus v2 CTDs for conductivity, temperature, and depth casts. </ns1:discussion></ns1:equipment><ns1:discussion>Refer to the OPR-N305-FA-20 Data Acquisition and Processing Report 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:equipmentAndVessels><ns1:qualityControl><ns1:additionalQualityControl><ns2:comments/><ns2:issue><ns2:comments/><ns2:images><ns2:caption>H13412 Allowable uncertainty statistics</ns2:caption><ns2:link>SupportFiles\H13412_MB_VR_MLLW_Final.QAv6.tvu_qc.png</ns2:link></ns2:images><ns2:discussion>The surface was analyzed using the HydrOffice QC Tools Grid QA feature to determine compliance with specifications. Overall, 99.5% of nodes within the surface meet NOAA Allowable Uncertainty specifications for H13412 (Figure 11).</ns2:discussion><ns2:title>NOAA Allowable Uncertainty</ns2:title></ns2:issue><ns2:issue><ns2:comments/><ns2:images><ns2:caption>H13412 Data density statistics</ns2:caption><ns2:link>SupportFiles\H13412_MB_VR_MLLW_Final.QAv6.density.png</ns2:link></ns2:images><ns2:discussion>The surface was analyzed using the HydrOffice QC Tools Grid QA feature to determine compliance with specifications. Density requirements for H13412 were achieved with at least 99.5% of surface nodes containing five or more soundings as required by HSSD Section 5.2.2.3 (Figure 12).</ns2:discussion><ns2:title>Density</ns2:title></ns2:issue><ns2:issue><ns2:comments/><ns2:images><ns2:caption>Rock outcropping along shore</ns2:caption><ns2:link>SupportFiles\20201206_122822 Rock Point Outcropping 2.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>Kelp beds along coast adjacent to Kydaka Point to Neah Bay</ns2:caption><ns2:link>SupportFiles\20201206_084857 Kelp Bed area.jpg</ns2:link></ns2:images><ns2:discussion>Gaps in coverage are present at the inshore limits of H13412 and are a result of sparse outer beam data while launches developed the inshore limit of safe navigation (NALL). These gaps are most prevalent in the exposed, rocky areas of H13412 as kelp and nearshore topography made it too dangerous to acquire additional bathymetry, as shown in Figures 13 and Figure 14. </ns2:discussion><ns2:title>Gaps at NALL</ns2:title></ns2:issue></ns1:additionalQualityControl><ns1:equipmentEffectiveness><ns2:comments/><ns2:results deviation="false"><ns2:issue><ns2:comments/><ns2:discussion>There were no conditions or deficiencies that affected equipment operational effectiveness.</ns2:discussion><ns2:title>None Exist</ns2:title></ns2:issue></ns2:results></ns1:equipmentEffectiveness><ns1:soundSpeedMethods><ns1:castFrequency>Casts were conducted at a minimum of one every four hours during launch acquisition. Casts were conducted more frequently when there was a change in surface sound speed greater than two meters per second. MVP casts on S220 were conducted at an average interval of 179 minutes, guided by observation of the surface sound speed and targeted to deeper areas. All sound speed methods were used as detailed in the DAPR.</ns1:castFrequency><ns1:comments/><ns1:discussion xsi:nil="true"></ns1:discussion></ns1:soundSpeedMethods><ns1:junctions><ns2:comments/><ns2:images><ns2:caption>Overview of H13412 junction surveys</ns2:caption><ns2:link>SupportFiles\Junction Overview.png</ns2:link></ns2:images><ns2:discussion>H13412 junctions with 1 adjacent survey from this project, H13414 and H11083 from a prior project, as shown in Figure 6. These areas of overlap between surveys were reviewed in CARIS HIPS and SIPS by surface differencing (at equal resolutions) to assess surface agreement. The junctions with H13412 are generally within the NOAA allowable uncertainty in their areas of overlap. For all junctions with H13412, a negative difference indicates H13412 was shoaler and a positive difference indicates H13412 was deeper.</ns2:discussion><ns2:junction><ns2:comments/><ns2:images><ns2:caption>Difference surface between H13412 (blue) and junctioning survey H13414 (pink)
</ns2:caption><ns2:link>SupportFiles\Junction Difference Statistics.png</ns2:link></ns2:images><ns2:images><ns2:caption>Difference surface statistics between H13412 and H13414 (VR surface)
</ns2:caption><ns2:link>SupportFiles\H13414_MB_VR_MLLW_Final_depth_delta.png</ns2:link></ns2:images><ns2:discussion>Surface differencing in CARIS HIPS and SIPS was used to assess junction agreement between the surface from H13412 and the surface from H13414 (Figure 7). The statistical analysis of the difference surface shows a mean of 0.02 meters with 95% of the nodes having a maximum deviation of +/- 0.16 meters, as seen in Figure 8. It was found that 99.5% of nodes are within NOAA allowable uncertainty.</ns2:discussion><ns2:survey><ns2:scale>20000</ns2:scale><ns2:relativeLocation>SE</ns2:relativeLocation><ns2:fieldUnit>NOAA Ship Fairweather</ns2:fieldUnit><ns2:year>2020</ns2:year><ns2:registryNumber>H13414</ns2:registryNumber></ns2:survey></ns2:junction><ns2:junction><ns2:comments/><ns2:images><ns2:caption>Difference surface between H13412 (blue) and junctioning survey H11083 (brown)</ns2:caption><ns2:link>SupportFiles\H13412_H11083_junction.png</ns2:link></ns2:images><ns2:images><ns2:caption>Difference surface statistics between H13412 and H11083 (10 meter surface)</ns2:caption><ns2:link>SupportFiles\H13412_10m-H11083_10m_UTM10NAD83_depth_delta.png</ns2:link></ns2:images><ns2:discussion>Surface differencing in CARIS HIPS and SIPS was used to assess junction agreement between the surface from H13412 and the surface from H11083 (Figure 9 ). The statistical analysis of the difference surface shows a mean of 0.35 meters with 95% of the nodes having a maximum deviation of +/- 0.82 meters, as seen in Figure 10. It was found that 95.49% of nodes are within NOAA allowable uncertainty. </ns2:discussion><ns2:survey><ns2:scale>5000</ns2:scale><ns2:relativeLocation>W</ns2:relativeLocation><ns2:fieldUnit>NOAA Ship Rainier</ns2:fieldUnit><ns2:year>2000</ns2:year><ns2:registryNumber>H11083</ns2:registryNumber></ns2:survey></ns2:junction></ns1:junctions><ns1:crosslines><ns2:comments/><ns2:topic><ns2:images><ns2:caption>Overview of H13412 Crosslines</ns2:caption><ns2:link>SupportFiles\H13412_Crossline_Overview2.png</ns2:link></ns2:images><ns2:images><ns2:caption>H13412 Crossline and mainscheme difference statistics</ns2:caption><ns2:link>SupportFiles\H13412_Mainscheme-Crosslines_depth_delta.png</ns2:link></ns2:images><ns2:discussion>Crosslines were collected, processed and compared in accordance with Section 5.2.4.2 of the HSSD. To evaluate crosslines, a surface generated via data strictly from mainscheme lines and a surface generated via data strictly from crosslines were created. From these two surfaces, a difference surface (mainscheme - crosslines = difference surface) was generated (Figure 4), 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 meters and 95% of nodes falling within 0.13 meters (with mainscheme being shoaler, as shown in Figure 5). For the respective depths, the difference surface was compared to the allowable NOAA uncertainty standards (Figure 5). In total, 99.5% of the depth differences between H13412 mainscheme and crossline data were within allowable NOAA uncertainties.
</ns2:discussion></ns2:topic></ns1:crosslines><ns1:factorsAffectingSoundings><ns2:comments/><ns2:results deviation="false"><ns2:issue><ns2:comments/><ns2:discussion>There were no other factors that affected corrections to soundings.</ns2:discussion><ns2:title>None Exist</ns2:title></ns2:issue></ns2:results></ns1:factorsAffectingSoundings><ns1:sonarQCChecks><ns2:comments/><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></ns1:sonarQCChecks><ns1:uncertainty><ns2:comments/><ns2:discussion>In addition to the usual a priori estimates of uncertainty via device models for vessel motion and VDATUM, real-time and post-processed uncertainty sources were also incorporated into the depth estimates of survey H13412. Real-time uncertainties were provided via EM 710 and EM 2040 MBES data and Applanix Delayed Heave RMS. 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:values><ns2:tideUncertainty><ns2:zoning units="centimeters">13.2</ns2:zoning><ns2:tideMethod>ERS via VDATUM</ns2:tideMethod><ns2:measured xsi:nil="true"/></ns2:tideUncertainty><ns2:soundSpeedUncertainty><ns2:surface units="meters/second">0.5</ns2:surface><ns2:hullID>280X (All Launches)</ns2:hullID><ns2:measuredXBT units="meters/second">N/A</ns2:measuredXBT><ns2:measuredCTD units="meters/second">2</ns2:measuredCTD><ns2:measuredMVP units="meters/second">N/A</ns2:measuredMVP></ns2:soundSpeedUncertainty><ns2:soundSpeedUncertainty><ns2:surface units="meters/second">0.5</ns2:surface><ns2:hullID>S220</ns2:hullID><ns2:measuredXBT units="meters/second">N/A</ns2:measuredXBT><ns2:measuredCTD units="meters/second">N/A</ns2:measuredCTD><ns2:measuredMVP units="meters/second">1</ns2:measuredMVP></ns2:soundSpeedUncertainty></ns2:values></ns1:uncertainty><ns1:coverageEquipmentAndMethods><ns2:comments/><ns2:results deviation="true"><ns2:discussion>All equipment and survey methods were used as detailed in the DAPR</ns2:discussion></ns2:results></ns1:coverageEquipmentAndMethods></ns1:qualityControl><ns1:backscatter><ns2:comments/><ns2:results acquired="true"><ns2:images><ns2:caption>Backscatter mosaic for H13412</ns2:caption><ns2:link>SupportFiles\Backscatter Mosaic.png</ns2:link></ns2:images><ns2:images><ns2:caption>Backscatter calibration values</ns2:caption><ns2:link>SupportFiles\Backscatter calibration values.PNG</ns2:link></ns2:images><ns2:discussion>Raw backscatter data were stored in the .all file for Kongsberg systems. All backscatter were processed to GSF files and a floating point mosaic was created by the field unit via Fledermaus FMGT 7.9.0 . See Figure 15 for a greyscale representation of the complete mosaic. A relative backscatter calibration was performed by the field unit via a patch test in order to bring the survey systems on each of the launches into alignment. See Figure 16 for a table of the calibration values entered into the Processing Settings within FMGT. Approximate inter-calibration corrections for offsets between sonar systems were applied to the mosaic.
</ns2:discussion></ns2:results></ns1:backscatter><ns1:echoSoundingCorrections><ns1:corrections><ns2:comments/><ns2:results deviation="false"><ns2:discussion>All data reduction procedures conform to those detailed in the DAPR.</ns2:discussion></ns2:results></ns1:corrections><ns1:calibrations><ns2:comments/><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></ns1:calibrations><ns1:additionalIssues><ns2:comments/></ns1:additionalIssues></ns1:echoSoundingCorrections><ns1:dataProcessing><ns1:surfaces><ns1:surface><ns2:depthRange><ns2:max units="meters">177.1</ns2:max><ns2:min units="meters">0.8</ns2:min></ns2:depthRange><ns2:surfaceParameter>NOAA_VR</ns2:surfaceParameter><ns2:surfaceName>H13412_MB_VR_MLLW</ns2:surfaceName><ns2:resolution units="meters">Variable Resolution</ns2:resolution><ns2:purpose>Complete MBES</ns2:purpose><ns2:surfaceType>CARIS VR Surface (CUBE)</ns2:surfaceType></ns1:surface><ns1:surface><ns2:depthRange><ns2:max units="meters">177.1</ns2:max><ns2:min units="meters">0.8</ns2:min></ns2:depthRange><ns2:surfaceParameter>NOAA_VR</ns2:surfaceParameter><ns2:surfaceName>H13412_MB_VR_MLLW_Final</ns2:surfaceName><ns2:resolution units="meters">Variable Resolution</ns2:resolution><ns2:purpose>Complete MBES</ns2:purpose><ns2:surfaceType>CARIS VR Surface (CUBE)</ns2:surfaceType></ns1:surface><ns1:comments/><ns1:discussion>The NOAA CUBE parameters defined in the HSSD were used for the creation of all CUBE surfaces for H13412. 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, part of the QC Tools package within HydrOffice, 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 surface.</ns1:discussion></ns1:surfaces><ns1:drSoftware><ns1:discussion xsi:nil="true"></ns1:discussion><ns1:comments/><ns1:featureObjectCatalog>NOAA Profile Version 2020</ns1:featureObjectCatalog><ns1:imagerySoftware deviation="true"><ns1:manufacturer>QPS</ns1:manufacturer><ns1:name>Fledermaus</ns1:name><ns1:version>7.9.0</ns1:version></ns1:imagerySoftware><ns1:bathySoftware deviation="true"><ns1:manufacturer>CARIS</ns1:manufacturer><ns1:name>HIPS and SIPS</ns1:name><ns1:version>11.3</ns1:version></ns1:bathySoftware></ns1:drSoftware><ns1:additionalDataProcessing><ns2:comments/><ns2:issue><ns2:comments/><ns2:discussion>Data acquisition and processing notes are included in the acquisition and processing logs, and additional processing such as final separation model reduction and sound speed application are noted in the H13412 Data Log spreadsheet. All data logs are submitted digitally in the Separates I folder.</ns2:discussion><ns2:title>Data Logs</ns2:title></ns2:issue><ns2:issue><ns2:comments/><ns2:images><ns2:caption>Surface Comparison between Incorrect HVF and Correct HVF data</ns2:caption><ns2:link>SupportFiles\H13398_MB_VR_MLLW_CST-H13398_HVF_Test_VR_depth_delta.png</ns2:link></ns2:images><ns2:discussion>The DAPR includes the correct offsets in terms of what information is input into our systems. This information, unfortunately, did not make its way into the HVF. The offset inputs in the HVF are not applied directly to the data and are only used to determine uncertainty.  These small differences do not seem to impact the uncertainty values. To assess this we created a test project and processed a small section of the data with the updated HVF and created a surface. We then compared the resulting uncertainty with the old HVF and new HVF which mirrors the DAPR and the POS offsets. We then utilized compare grids to assess the differences between &quot;Correct HVF Surface&quot; and the &quot;Incorrect HVF Surface&quot;.  The mean difference was 0.0m. Output graphs are attached.</ns2:discussion><ns2:title>HVF Error</ns2:title></ns2:issue></ns1:additionalDataProcessing></ns1:dataProcessing></ns1:dataAcquisitionAndProcessing><ns1:resultsAndRecommendations><ns1:additionalResults><ns1:maritimeBoundary><ns2:comments/><ns2:results investigated="None Exist"><ns2:discussion>No Maritime Boundary Points were assigned for this survey.</ns2:discussion></ns2:results></ns1:maritimeBoundary><ns1:ATONS><ns2:comments/><ns2:results investigated="Investigated"><ns2:discussion>There where 7 assigned ATONs for H13412. They are fully attributed in the Final Feature File.</ns2:discussion></ns2:results></ns1:ATONS><ns1:ferryRoutesAndTerminals><ns2:comments/><ns2:results investigated="None Exist"><ns2:discussion>No ferry routes or terminals exist for this survey.</ns2:discussion></ns2:results></ns1:ferryRoutesAndTerminals><ns1:overheadFeatures><ns2:comments/><ns2:results investigated="None Exist"><ns2:discussion>No overhead features exist for this survey.</ns2:discussion></ns2:results></ns1:overheadFeatures><ns1:ENCScaleRecommendation><ns2:comments/><ns2:results recommended="false"><ns2:discussion>No new ENC scales are recommended for this area.</ns2:discussion></ns2:results></ns1:ENCScaleRecommendation><ns1:platforms><ns2:comments/><ns2:results investigated="None Exist"><ns2:discussion>No platforms exist for this survey.</ns2:discussion></ns2:results></ns1:platforms><ns1:bottomSamples><ns2:comments/><ns2:results investigated="Investigated"><ns2:images><ns2:caption>H13412 Bottom sample locations</ns2:caption><ns2:link>SupportFiles\H13412 Bottom sample locations 2.PNG</ns2:link></ns2:images><ns2:discussion>6 bottom samples were acquired in accordance with the Project Instructions for survey H13412. All bottom samples were entered in the H13412 Final Feature File. See Figure 17  for a graphical overview of sample locations.</ns2:discussion></ns2:results></ns1:bottomSamples><ns1:newSurveyRecommendation><ns2:comments/><ns2:results recommended="false"><ns2:discussion>No new surveys or further investigations are recommended for this area.</ns2:discussion></ns2:results></ns1:newSurveyRecommendation><ns1:abnormalSeafloorEnviroCond><ns2:comments/><ns2:results investigated="None Exist"><ns2:discussion>No abnormal seafloor or environmental conditions exist for this survey.</ns2:discussion></ns2:results></ns1:abnormalSeafloorEnviroCond><ns1:submarineFeatures><ns2:comments/><ns2:results investigated="Investigated"><ns2:discussion>The CBLSUB features were not observed in the multibeam bathymetry nor the backscatter mosaic.</ns2:discussion></ns2:results></ns1:submarineFeatures><ns1:constructionOrDredging><ns2:comments/><ns2:results investigated="None Exist"><ns2:discussion>No present or planned construction or dredging exist within the survey limits.</ns2:discussion></ns2:results></ns1:constructionOrDredging></ns1:additionalResults><ns1:chartComparison><ns1:methods><ns2:comments/></ns1:methods><ns1:channels><ns2:comments/><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></ns1:channels><ns1:charts><ns2:comments/><ns2:ENC><ns2:edition>14</ns2:edition><ns2:scale>10000</ns2:scale><ns2:name>US5WA20M</ns2:name><ns2:updateApplicationDate>2018-05-28</ns2:updateApplicationDate><ns2:issueDate>2019-02-04</ns2:issueDate></ns2:ENC><ns2:ENC><ns2:edition>30</ns2:edition><ns2:scale>100000</ns2:scale><ns2:name>US4WA36M</ns2:name><ns2:updateApplicationDate>2020-07-09</ns2:updateApplicationDate><ns2:issueDate>2020-07-09</ns2:issueDate></ns2:ENC></ns1:charts><ns1:shoalAndHazardousFeatures><ns2:comments/><ns2:results investigated="None Exist"><ns2:discussion>No shoals or potentially hazardous features exist for this survey.</ns2:discussion></ns2:results></ns1:shoalAndHazardousFeatures><ns1:unchartedFeatures><ns2:comments/><ns2:results investigated="Investigated"><ns2:discussion>Survey H13412 has 19 new features that are addressed in the H13412 Final Feature File. Of these features, there are 1 new wreck, 2 new obstructions, 6 new seabed areas, 1 new pontoon areas, 2 new piles, and 7 new kelp features.</ns2:discussion></ns2:results></ns1:unchartedFeatures><ns1:chartedFeatures><ns2:comments/><ns2:results investigated="Investigated"><ns2:discussion> All assigned charted features are attributed in the Final Feature File.</ns2:discussion></ns2:results></ns1:chartedFeatures></ns1:chartComparison></ns1:resultsAndRecommendations><ns1:approvalSheet><ns1:signingPersonnel><ns2:approvalDate>2021-05-30</ns2:approvalDate><ns2:approverTitle>Chief of Party</ns2:approverTitle><ns2:approverName>CDR John Lomnicky</ns2:approverName></ns1:signingPersonnel><ns1:signingPersonnel><ns2:approvalDate>2021-05-30</ns2:approvalDate><ns2:approverTitle>Operations Officer</ns2:approverTitle><ns2:approverName>LT Marybeth Head</ns2:approverName></ns1:signingPersonnel><ns1:signingPersonnel><ns2:approvalDate>2021-05-30</ns2:approvalDate><ns2:approverTitle>Chief Survey Technician</ns2:approverTitle><ns2:approverName>CHST Alissa Johnson</ns2:approverName></ns1:signingPersonnel><ns1:signingPersonnel><ns2:approvalDate>2021-05-30</ns2:approvalDate><ns2:approverTitle>Sheet Manager</ns2:approverTitle><ns2:approverName>HAST Brent Humphries</ns2:approverName></ns1:signingPersonnel><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:additionalInfo xsi:nil="true"></ns1:additionalInfo><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:statements></ns1:approvalSheet></ns1:descriptiveReport>