<?xml version="1.0" encoding="utf-8"?>
<dr:descriptiveReport xmlns:dr="http://svn.pydro.noaa.gov/2022/01/DescriptiveReport" xmlns:hsd="http://svn.pydro.noaa.gov/2022/01/AllGlobalTypes" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://svn.pydro.noaa.gov/2022/01/DescriptiveReport http://svn.pydro.noaa.gov/2022/01/DR.xsd">
    <dr:metadata>
        <dr:projectMetadata>
            <hsd:number>OPR-R340-KR-23</hsd:number>
            <hsd:name>Bristol Bay, AK</hsd:name>
            <hsd:generalLocality>Bristol Bay</hsd:generalLocality>
            <hsd:fieldUnit>Terrasond</hsd:fieldUnit>
        </dr:projectMetadata>
        <dr:registryMetadata>
            <hsd:registryNumber>H13718</hsd:registryNumber>
            <hsd:sheetID>5</hsd:sheetID>
            <hsd:registryInstructions>na</hsd:registryInstructions>
            <hsd:sublocality>Approach to Kulukak Bay</hsd:sublocality>
            <hsd:stateOrTerritory>Alaska</hsd:stateOrTerritory>
            <hsd:country>United States</hsd:country>
            <hsd:scale>40000</hsd:scale>
        </dr:registryMetadata>
        <dr:surveyMetadata>
            <hsd:year>2023</hsd:year>
            <hsd:chiefOfParty>Andrew Orthmann</hsd:chiefOfParty>
            <hsd:projectType>Navigable Area</hsd:projectType>
            <hsd:PIDate>2023-01-30</hsd:PIDate>
            <hsd:datesOfSurvey>
                <hsd:start>2023-06-03</hsd:start>
                <hsd:end>2023-09-11</hsd:end>
            </hsd:datesOfSurvey>
            <hsd:equipmentTypes>
                <hsd:soundingEquipment>Multibeam Echo Sounder</hsd:soundingEquipment>
                <hsd:imageryEquipment>Multibeam Echo Sounder Backscatter</hsd:imageryEquipment>
            </hsd:equipmentTypes>
            <hsd:acquisition>
                <hsd:units>meters</hsd:units>
            </hsd:acquisition>
            <hsd:timeZone>UTC</hsd:timeZone>
            <hsd:verifier>Pacific Hydrographic Branch</hsd:verifier>
            <hsd:titlesheetRemarks>
                <hsd:fieldRemarks xsi:nil="true" />
                <hsd: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 WGS84 UTM 04N, MLLW. All references to other horizontal or vertical datums in this report are applicable to the processed hydrographic data provided by the field unit.</hsd:branchRemarks>
            </hsd:titlesheetRemarks>
        </dr:surveyMetadata>
        <dr:dataLicense>
            <hsd:classification>CC0-1.0 (NOAA Contractors)</hsd:classification>
            <hsd:spdx>
                <hsd:licenseIdentifier>CC0-1.0</hsd:licenseIdentifier>
                <hsd:licenseDeed>https://creativecommons.org/publicdomain/zero/1.0/</hsd:licenseDeed>
                <hsd:legalCode>https://creativecommons.org/publicdomain/zero/1.0/legalcode</hsd:legalCode>
            </hsd:spdx>
            <hsd:description>These data were produced under contract with NOAA and any potential copyright was assigned to NOAA. NOAA waives any potential copyright and related rights in these data worldwide through the Creative Commons Zero 1.0 Universal Public Domain Dedication (CC0).</hsd:description>
        </dr:dataLicense>
        <dr:assignment>Contractor</dr:assignment>
    </dr:metadata>
    <dr:areaSurveyed>
        <dr:areaDescription>
            <hsd:discussion>The survey area is located in Bristol Bay, Alaska.

Bristol Bay is located in southwestern Alaska. The area is ecologically rich and renowned for its wildlife and salmon fisheries. It is bound by the volcanic mountains of the Alaska Peninsula to the south, and tundra-covered landscapes to the north. The area is remote and disconnected from the road system, with area communities small and accessible only by air or water. The largest nearby community (and hub for the region) is Dillingham (population 2,203 in 2021).

An intricate network of rivers feed the bay, especially the Kvichak, Nushagak, Naknek, and Igushik. The rivers transport and deposit large amounts of sediment into the bay, resulting in seafloor variability with shifting sandbars and constantly changing depths. River current combined with the large daily tide range of the area (4-5 meters) causes very strong currents, especially at the approaches to the area rivers.

The area is unnavigable for much of the year due to sea and river ice. During the ice free period, approximately June through October, weather is frequently inclement, with sudden storms and dense fog common occurrences. The unpredictable weather pattern, coupled with the changeable seafloor and outdated charts of the area, pose significant navigational challenges for vessels.

Vessel traffic in the region is largely from fishing vessels (mostly smaller vessels of approximately 32' length) with a mix of larger fish tender vessels. Tug-and-tow barges also frequent the area, bringing fuel and supplies to the communities that border the bay, as well as communities further up the various rivers.

Field work for hydrographic data collection was carried out from June through September of 2023 under project OPR-R340-KR-23, with final processing and reporting occurring from October, 2023 through January, 2024. This area was surveyed concurrently with fourteen other areas in the Bristol Bay project  in accordance with the Hydrographic Survey Project Instructions (dated January 30th, 2023), accompanying Scope of Work, and the NOAA Hydrographic Surveys Specifications and Deliverables (HSSD, 2022 edition).</hsd:discussion>
            <hsd:limits>
                <hsd:northWest>
                    <hsd:latitude hemisphere="N">58.827065000000005</hsd:latitude>
                    <hsd:longitude hemisphere="W">159.8307625</hsd:longitude>
                </hsd:northWest>
                <hsd:southEast>
                    <hsd:latitude hemisphere="N">58.54023472222222</hsd:latitude>
                    <hsd:longitude hemisphere="W">159.23559361111109</hsd:longitude>
                </hsd:southEast>
            </hsd:limits>
            <hsd:images>
                <hsd:caption>Overview of the survey extents.</hsd:caption>
                <hsd:link>SupportFiles\H13718_Survey_Extents.png</hsd:link>
            </hsd:images>
            <hsd:comments />
        </dr:areaDescription>
        <dr:surveyLimits>
            <hsd:results deviation="false">
                <hsd:discussion>Survey limits were acquired in accordance with the requirements in the Project Instructions and the HSSD.</hsd:discussion>
            </hsd:results>
            <hsd:comments />
        </dr:surveyLimits>
        <dr:surveyPurpose>
            <hsd:topic>
                <hsd:discussion>The purpose of this survey is described as follows in the Project Instructions:

Bristol Bay is important to the US economy as the largest sockeye salmon fishery in the world, and second ranked fishing port in the United States. Known as “America’s Fish Basket”, the
combined economic value of the commercial fishery, processing, visitor industry, and tourism is $1.1 Billion. It is home to 25 Alaska Native villages and communities who rely on the Alaska maritime infrastructure for goods and fuel.

The Bristol Bay project will provide contemporary surveys to update National Ocean Service (NOS) nautical charting products and services. Seventy percent of the project was last surveyed between 1945 and 1960, the rest has never been surveyed. Updated bathymetry and feature data will be used to create larger scale charts in the area, reducing the risk to navigation, and serve as the foundational dataset to support modeling, industry, and science.

The project will directly support the maritime services available to the remote coastal communities by providing the base data to update nautical products for nearby waters, including targeting navigational channels near the Port of Naknek, Ekuk, and Port Heiden. These products can improve the safety of subsistence fishing, marine transportation, and shipment of goods. It is noteworthy that Port Heiden has moved inland because of erosion.

The priority areas focus on collecting data for vessel lightering areas identified by the Western Alaska Tanker Lightering Best Practices Committee, as part of the Alaska Maritime Prevention &amp; Response Network. These areas are used for Ship-to-Ship transfers of oil products, including fuel which is of key importance to local residents.

The lightering areas, together with the Automatic Identification Systems (AIS) traffic patterns, regional requests, and hydrographic health modeling were used to identify 2300 square nautical miles of priority project area. Data from this project will supersede all prior survey data providing modern hydrographic survey data for this area and updating the local charting products.</hsd:discussion>
            </hsd:topic>
            <hsd:comments />
        </dr:surveyPurpose>
        <dr:surveyQuality>
            <hsd:adequacy>The entire survey is adequate to supersede previous data.</hsd:adequacy>
            <hsd:discussion xsi:nil="true" />
            <hsd:comments />
        </dr:surveyQuality>
        <dr:surveyCoverage>
            <hsd:coverageRequirement>
                <hsd:waterDepth>All waters in survey area (Any lines of data provided including opportunity data)</hsd:waterDepth>
                <hsd:requiredCoverage>Complete a minimum of 15,606 LNM. Unlogged transit mileage, system calibration mileage and data which do not meet HSSD specifications shall not count towards the completion of the LNM requirement. Notify the COR/Project Manager upon nearing completion of LNM requirement. The final survey area shall be squared off and ensure the full investigation of any features within the surveyed extent. Set Line Spacing system of MBES (HSSD Section 5.2.2.4 Option A). </hsd:requiredCoverage>
            </hsd:coverageRequirement>
            <hsd:coverageRequirement>
                <hsd:waterDepth>Sheet H13718</hsd:waterDepth>
                <hsd:requiredCoverage>Sounding lines shall be acquired with spacing adequate to collect data at an interval of at least 240 meters.</hsd:requiredCoverage>
            </hsd:coverageRequirement>
            <hsd:coverageRequirement>
                <hsd:waterDepth>All Shoreline Sheets SDB Checklines</hsd:waterDepth>
                <hsd:requiredCoverage>Within each shoreline sheet, acquire four geographically dispersed sounding lines that extend to the inshore limit of safe navigation. The field unit will chose the location for the safe and efficient acquisition of shoal depths.</hsd:requiredCoverage>
            </hsd:coverageRequirement>
            <hsd:results deviation="true">
                <hsd:discussion>Coverage requirements were met. Additional clarification on specific requirements are provided below.

LNM Requirements: A minimum of 15,606 LNM of MBES data was required project-wide. 15,997 was actually acquired. The excess of 391 was collected to compensate for inefficiencies incidental to data collection such as crossline mileage that exceeded requirements, data acquired on run-ins or run-outs (including in shallow water in order to scout between lines), and excess overlap (if any). LNM quantities do not include transit or calibration data, or data that does not meet HSSD requirements.

Splits: Splits were generally not acquired on charted soundings that were shoaler than surrounding survey data. It was observed during survey operations that there was a project-wide trend of nearly all charted soundings being shoaler than survey data, and excessive effort and LNM would be required to perform splits on the charted soundings. This was brought to the attention of the NOAA COR and an exception was approved to de-prioritize bathymetric splits over shoal charted soundings and use hydrographer's discretion when choosing these splits. Splits were still acquired where necessary to develop shoals. Correspondence is included with the survey deliverables.

NALL: The inshore depth contour definition of the NALL was specified to be 4.5 m for this survey. 4.5 m (or shoaler) was successfully achieved fully along the coast. Note that shoreline trace lines that run roughly parallel to the shore was completed early in the project to scout the nearshore area depths in this relatively uncharted area. With the shoreline trace in place, mainscheme lines that were roughly perpendicular to the shore could be collected more safely and efficiently. However, mainscheme lines were terminated when 4.5 m depth was achieved, which did not always coincide with the shoreline trace lines. This left gaps in some areas between the shoreline trace, which were shoaler than 4.5 m in many places, and the mainscheme lines. However, the trace is included with the deliverables as it is good data in uncharted water that adds value to the dataset.

SDB Checklines: SDB (Satellite Derived Bathymetry) checklines, to be used for SDB calibrations, were acquired at geographically dispersed locations chosen by the field crew. These were also run co-incident with NASA ICESat-2 data provided by NOAA when practical per NOAA's request for overlap (see included correspondence), but personnel and vessel safety took precedence in location decisions. For the checklines, the ASV-CW5 vessel collected data as shallow as possible, until it was deemed unsafe to continue closer to shore. These checklines were normally acquired at mid- to high- tide in order to achieve as shoal of a tide-corrected depth as possible. All checkline data is incorporated in the final surface submitted with the survey deliverables.

Four checklines were acquired for this sheet. Their location relative to the survey area and the least depth achieved on each line is shown in the image below.</hsd:discussion>
                <hsd:images>
                    <hsd:caption>Image showing the relative location of SDB checklines. The least depth achieved on each checkline is shown in meters.</hsd:caption>
                    <hsd:link>SupportFiles\H13718_SDB_Locations.png</hsd:link>
                </hsd:images>
            </hsd:results>
            <hsd:comments />
        </dr:surveyCoverage>
        <dr:coverageGraphic>
            <hsd:coverageGraphicImage>
                <hsd:images>
                    <hsd:caption>Overview of the survey coverage.</hsd:caption>
                    <hsd:link>SupportFiles\H13718_Survey_Coverage.png</hsd:link>
                </hsd:images>
            </hsd:coverageGraphicImage>
        </dr:coverageGraphic>
        <dr:surveyStatistics>
            <hsd:LNM>
                <hsd:vesselLNM>
                    <hsd:vessel>
                        <hsd:hullID>Arctic Seal</hsd:hullID>
                        <hsd:statistics>
                            <hsd:MS_SBES>0.0</hsd:MS_SBES>
                            <hsd:MS_MBES>905.1</hsd:MS_MBES>
                            <hsd:MS_lidar>0.0</hsd:MS_lidar>
                            <hsd:MS_SSS>0.0</hsd:MS_SSS>
                            <hsd:MS_SBES_MBES>0.0</hsd:MS_SBES_MBES>
                            <hsd:MS_MBES_SSS>0.0</hsd:MS_MBES_SSS>
                            <hsd:MS_SBES_SSS>0.0</hsd:MS_SBES_SSS>
                            <hsd:XL_MBES_SBES>84.4</hsd:XL_MBES_SBES>
                            <hsd:XL_lidar>0.0</hsd:XL_lidar>
                        </hsd:statistics>
                    </hsd:vessel>
                    <hsd:vessel>
                        <hsd:hullID>ASV-CW5</hsd:hullID>
                        <hsd:statistics>
                            <hsd:MS_SBES>0.0</hsd:MS_SBES>
                            <hsd:MS_MBES>711.0</hsd:MS_MBES>
                            <hsd:MS_lidar>0.0</hsd:MS_lidar>
                            <hsd:MS_SSS>0.0</hsd:MS_SSS>
                            <hsd:MS_SBES_MBES>0.0</hsd:MS_SBES_MBES>
                            <hsd:MS_MBES_SSS>0.0</hsd:MS_MBES_SSS>
                            <hsd:MS_SBES_SSS>0.0</hsd:MS_SBES_SSS>
                            <hsd:XL_MBES_SBES>60.0</hsd:XL_MBES_SBES>
                            <hsd:XL_lidar>0.0</hsd:XL_lidar>
                        </hsd:statistics>
                    </hsd:vessel>
                </hsd:vesselLNM>
                <hsd:totalLNM>
                    <hsd:MS_SBES>0.0</hsd:MS_SBES>
                    <hsd:MS_MBES>1616.1</hsd:MS_MBES>
                    <hsd:MS_lidar>0.0</hsd:MS_lidar>
                    <hsd:MS_SSS>0.0</hsd:MS_SSS>
                    <hsd:MS_SBES_MBES>0.0</hsd:MS_SBES_MBES>
                    <hsd:MS_MBES_SSS>0.0</hsd:MS_MBES_SSS>
                    <hsd:MS_SBES_SSS>0.0</hsd:MS_SBES_SSS>
                    <hsd:XL_MBES_SBES>144.4</hsd:XL_MBES_SBES>
                    <hsd:XL_lidar>0.0</hsd:XL_lidar>
                    <hsd:percentXLLNM>8.9</hsd:percentXLLNM>
                </hsd:totalLNM>
            </hsd:LNM>
            <hsd:totalSurveyStats>
                <hsd:bottomSamples>11</hsd:bottomSamples>
                <hsd:maritimeBoundaryPoints>3</hsd:maritimeBoundaryPoints>
                <hsd:DP>0</hsd:DP>
                <hsd:diveOps>0</hsd:diveOps>
                <hsd:SNM>199.5</hsd:SNM>
            </hsd:totalSurveyStats>
            <hsd:surveyDates>2023-06-03</hsd:surveyDates>
            <hsd:surveyDates>2023-06-04</hsd:surveyDates>
            <hsd:surveyDates>2023-06-27</hsd:surveyDates>
            <hsd:surveyDates>2023-06-28</hsd:surveyDates>
            <hsd:surveyDates>2023-07-02</hsd:surveyDates>
            <hsd:surveyDates>2023-07-03</hsd:surveyDates>
            <hsd:surveyDates>2023-07-07</hsd:surveyDates>
            <hsd:surveyDates>2023-07-08</hsd:surveyDates>
            <hsd:surveyDates>2023-07-09</hsd:surveyDates>
            <hsd:surveyDates>2023-07-10</hsd:surveyDates>
            <hsd:surveyDates>2023-07-16</hsd:surveyDates>
            <hsd:surveyDates>2023-07-17</hsd:surveyDates>
            <hsd:surveyDates>2023-07-18</hsd:surveyDates>
            <hsd:surveyDates>2023-07-19</hsd:surveyDates>
            <hsd:surveyDates>2023-09-10</hsd:surveyDates>
            <hsd:surveyDates>2023-09-11</hsd:surveyDates>
            <hsd:discussion xsi:nil="true" />
            <hsd:comments />
        </dr:surveyStatistics>
    </dr:areaSurveyed>
    <dr:dataAcquisitionAndProcessing>
        <dr:equipmentAndVessels>
            <dr: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.</dr:discussion>
            <dr:vessels>
                <dr:vessel>
                    <hsd:hullID>Arctic Seal</hsd:hullID>
                    <hsd:LOA units="meters">39.6</hsd:LOA>
                    <hsd:draft units="meters">2.0</hsd:draft>
                </dr:vessel>
                <dr:vessel>
                    <hsd:hullID>ASV-CW5</hsd:hullID>
                    <hsd:LOA units="meters">5.5</hsd:LOA>
                    <hsd:draft units="meters">0.6</hsd:draft>
                </dr:vessel>
                <dr:images>
                    <hsd:caption>The Arctic Seal in the Bristol Bay survey area.</hsd:caption>
                    <hsd:link>SupportFiles\Arctic_Seal.png</hsd:link>
                </dr:images>
                <dr:images>
                    <hsd:caption>The ASV-CW5 in the Bristol Bay survey area.</hsd:caption>
                    <hsd:link>SupportFiles\ASV-CW5.png</hsd:link>
                </dr:images>
                <dr:discussion>The Arctic Seal is a 40 m steel-hull, landing craft style vessel owned and operated by Support Vessels of Alaska. The Arctic Seal acquired multibeam data and provided housing and facilities for on-site data processing. The vessel was also used to collect bottom samples, conduct sound speed casts, and deploy/recover the ASV-CW5 (uncrewed) launch and LC-25 (crewed) launch.

The ASV-CW5 (ASV) is a 5.5 m aluminum-hull Autonomous Surface Vessel (ASV), C-Worker 5 model, owned and operated by L3-Harris ASV. The ASV was operated in an uncrewed but monitored mode, collecting multibeam data in close proximity to the Arctic Seal, as well as in areas too shallow for the larger vessel.</dr:discussion>
                <dr:comments />
            </dr:vessels>
            <dr:equipment>
                <dr:majorSystem>
                    <hsd:type>MBES</hsd:type>
                    <hsd:manufacturer>Teledyne RESON</hsd:manufacturer>
                    <hsd:model>SeaBat T50-R</hsd:model>
                </dr:majorSystem>
                <dr:majorSystem>
                    <hsd:type>MBES Backscatter</hsd:type>
                    <hsd:manufacturer>Teledyne RESON</hsd:manufacturer>
                    <hsd:model>SeaBat T50-R</hsd:model>
                </dr:majorSystem>
                <dr:majorSystem>
                    <hsd:type>Positioning and Attitude System</hsd:type>
                    <hsd:manufacturer>Applanix</hsd:manufacturer>
                    <hsd:model>POS MV 320 v5</hsd:model>
                </dr:majorSystem>
                <dr:majorSystem>
                    <hsd:type>Sound Speed System</hsd:type>
                    <hsd:manufacturer>Valeport</hsd:manufacturer>
                    <hsd:model>SWiFT SVP</hsd:model>
                </dr:majorSystem>
                <dr:majorSystem>
                    <hsd:type>Sound Speed System</hsd:type>
                    <hsd:manufacturer>AML Oceanographic</hsd:manufacturer>
                    <hsd:model>MicroX SV</hsd:model>
                </dr:majorSystem>
                <dr:discussion>The survey vessels were configured for MBES data collection with nearly identical survey equipment and software. Both vessels utilized Reson Seabat T50-R MBES systems, with surface sound speed measurements provided by AML Oceanographic Micro-X sensors. Both vessels used Applanix POSMVs (integrated into the T50-R MBES systems) with submersible IP-68 rated IMUs for attitude and position measurements. Sound speed profiles were collected using a Valeport SWiFT sensor, deployed while underway using a C-MAX Vigo winch, on the Arctic Seal. QPS QINSy software, running on Microsoft Windows 10-based PCs, was used for multibeam data logging and vessel navigation.</dr:discussion>
                <dr:comments />
            </dr:equipment>
            <dr:comments />
        </dr:equipmentAndVessels>
        <dr:qualityControl>
            <dr:crosslines>
                <hsd:topic>
                    <hsd:discussion>The percentage of crossline to mainscheme miles is 8.9%.

Effort was made to ensure crosslines (XLs) had good temporal and geographic distribution, were angled to enable nadir-to-nadir comparisons, and that the required minimum percent of mainscheme LNM was achieved.

Crosslines were conducted with all vessels to ensure there was ample overlap for inter-vessel comparisons, with each vessel crossing the other's mainscheme lines. Since the Arctic Seal and ASV-CW5 vessels worked in close proximity and normally ran parallel lines, crosslines were collected in sets whenever both vessels were in simultaneous operation. The collection of crosslines in sets, while spreading sets out across the survey area for good distribution, led to incidental collection of additional crossline LNM beyond the required 8% of mainscheme.

Crosslines were often collected while transiting across the survey area to reach a different survey priority such as bottom sample locations or infills, leading to crosslines that were diagonal to the direction of mainscheme lines.

The crossline analysis was conducted using CARIS HIPS “Line QC Report” process. Each crossline (with all associated file segments) was selected and run separately through the process, which calculated the depth difference between each accepted crossline sounding and a "QC" BASE (CUBE-type) surface’s depth layer created from the mainscheme data. The QC surface was created with the same parameters and resolution used for the final surface, with the important distinction that the QC surface did not include crosslines so as to not bias the results. Differences in depth were grouped by beam number and statistics were computed, including the percentage of soundings with differences from the QC surface falling within IHO Order 1a.

When at least 95% of the sounding differences exceed IHO Order 1a, the crossline was considered to “pass,” but when less than 95% of the soundings compare within IHO Order 1, the crossline was considered to “fail.” A 5% (or less) failure rate was considered acceptable since this approach compares soundings to a surface (instead of a surface to a surface), allowing for the possibility that noisy crossline soundings that don't adversely affect the final surface could be counted as a QC failure in this process.

Lines selected as crosslines and their percentage (%) of soundings passing IHO Order 1a, sorted from highest passing to lowest, are listed below. Note that within the CARIS HIPS projects provided with the survey deliverables, lines used as crosslines have their "Line Class" attribute set to "Check", while all others have this attribute set to "Track".

0024-154-ASV-CW5-E-Shoreline -- 100.0% pass
0025-155-ASV-CW5-E-Shoreline -- 100.0% pass
2751-253-ASV-CW5-E-XL102 -- 100.0% pass
2752-253-ASV-CW5-E-XL103 -- 100.0% pass
2754-253-ASV-CW5-E-XL104 -- 100.0% pass
2770-254-ASV-CW5-E-XL-108 -- 100.0% pass
2771-254-ASV-CW5-E-XL-109 -- 100.0% pass
2773-254-ASV-CW5-E-XL-110 -- 100.0% pass
2775-254-ASV-CW5-E-XL-112 -- 100.0% pass
0056-154-ArcticSeal-E_Shore_XL -- 100.0% pass
0057-154-ArcticSeal-E_Shore_XL -- 100.0% pass
0058-155-ArcticSeal-E_Shore_XL -- 100.0% pass
0683-191-ArcticSeal-E-SouthBorder-XL -- 100.0% pass
1893-253-ArcticSeal-E-XL50 -- 100.0% pass
1894-253-ArcticSeal-E-XL51 -- 100.0% pass
1895-253-ArcticSeal-E-XL52 -- 100.0% pass
1896-253-ArcticSeal-E-XL53 -- 100.0% pass
1897-253-ArcticSeal-E-XL54 -- 100.0% pass
1904-253-ArcticSeal-E-XL55 -- 100.0% pass
1907-254-ArcticSeal-E-XL58 -- 100.0% pass
1908-254-ArcticSeal-E-XL59 -- 100.0% pass
2768-254-ASV-CW5-E-XL-107 -- 100.0% pass
2756-253-ASV-CW5-E-XL105 -- 100.0% pass
2767-253-ASV-CW5-E-XL-106 -- 100.0% pass
1906-254-ArcticSeal-E-XL57 -- 100.0% pass
2774-254-ASV-CW5-E-XL-111 -- 99.8% pass
1905-254-ArcticSeal-E-XL56 -- 99.6% pass

Results: Agreement between them mainscheme surface and crossline soundings is excellent. At least 95% of all crossline soundings compare to the mainscheme surface within IHO Order 1a for all crosslines. Refer to Separate II: Digital Data for the detailed Crossline QC reports.</hsd:discussion>
                </hsd:topic>
                <hsd:comments />
            </dr:crosslines>
            <dr:uncertainty>
                <hsd:values>
                    <hsd:tideUncertainty>
                        <hsd:tideMethod>ERS via ERTDM</hsd:tideMethod>
                        <hsd:measured units="meters">0.18</hsd:measured>
                        <hsd:zoning units="meters">0.0</hsd:zoning>
                    </hsd:tideUncertainty>
                    <hsd:soundSpeedUncertainty>
                        <hsd:hullID>Arctic Seal</hsd:hullID>
                        <hsd:measuredCTD units="meters/second">0</hsd:measuredCTD>
                        <hsd:measuredMVP units="meters/second">2.4</hsd:measuredMVP>
                        <hsd:measuredXBT units="meters/second">0</hsd:measuredXBT>
                        <hsd:surface units="meters/second">0.025</hsd:surface>
                    </hsd:soundSpeedUncertainty>
                    <hsd:soundSpeedUncertainty>
                        <hsd:hullID>ASV-CW5</hsd:hullID>
                        <hsd:measuredCTD units="meters/second">0</hsd:measuredCTD>
                        <hsd:measuredMVP units="meters/second">2.4</hsd:measuredMVP>
                        <hsd:measuredXBT units="meters/second">0</hsd:measuredXBT>
                        <hsd:surface units="meters/second">0.025</hsd:surface>
                    </hsd:soundSpeedUncertainty>
                </hsd:values>
                <hsd:discussion>The uncertainty layer of the final surface was examined in CARIS HIPS software, as well as analyzed in Pydro QC Tools V3.10.9 Grid QA v6.

Uncertainty of the final grid cells range from 0 to 1.26 m. Greater than 99.5% of grid cells have TVU falling within the allowable range by depth. The larger values were observed to be in areas of highly variable seafloor where many soundings of different depths contribute to the value a grid cell and result in a overall higher standard deviation for the final depth of the cell. This was most prevalent around abrupt shoals, sandwaves, and areas exhibiting bottom change. Despite the higher uncertainty computed for some grid cells, depths for all final grid cells are within specifications.</hsd:discussion>
                <hsd:comments />
            </dr:uncertainty>
            <dr:junctions>
                <hsd:discussion>During field operations, effort was made to ensure sufficient overlap was achieved between this survey and any overlapping surveys for junction analysis. This included extending survey lines into overlapping sheets, and in some cases running survey lines along junction boundaries.

The "Gridded Surface Comparison V22.1" utility within Pydro was used to compare survey junctions. The utility differences the surfaces from the two surveys and generates statistics that include the percentage of grid cells that compare to within allowable TVU for the depth. 4 m resolution surfaces were used for all comparisons.</hsd:discussion>
                <hsd:images>
                    <hsd:caption>Overview of survey Junctions.</hsd:caption>
                    <hsd:link>SupportFiles\H13718_Survey_Junctions.png</hsd:link>
                </hsd:images>
                <hsd:junction>
                    <hsd:survey>
                        <hsd:registryNumber>H13717</hsd:registryNumber>
                        <hsd:scale>40000</hsd:scale>
                        <hsd:year>2023</hsd:year>
                        <hsd:fieldUnit>TerraSond</hsd:fieldUnit>
                        <hsd:relativeLocation>SE</hsd:relativeLocation>
                    </hsd:survey>
                    <hsd:discussion>Agreement between the two surveys is excellent. The mean difference is 0.03 m with a standard deviation of 0.09 m. 100% of grid cells agree within allowable TVU by depth.</hsd:discussion>
                    <hsd:comments />
                </hsd:junction>
                <hsd:junction>
                    <hsd:survey>
                        <hsd:registryNumber>H13723</hsd:registryNumber>
                        <hsd:scale>80000</hsd:scale>
                        <hsd:year>2023</hsd:year>
                        <hsd:fieldUnit>TerraSond</hsd:fieldUnit>
                        <hsd:relativeLocation>S</hsd:relativeLocation>
                    </hsd:survey>
                    <hsd:discussion>Agreement between the two surveys is excellent. The mean difference is 0.05 m with a standard deviation of 0.12 m. 100% of grid cells agree within allowable TVU by depth.</hsd:discussion>
                    <hsd:comments />
                </hsd:junction>
                <hsd:comments />
            </dr:junctions>
            <dr:sonarQCChecks>
                <hsd:results deviation="true">
                    <hsd:discussion>In addition to the crossline checks which included inter-vessel comparisons, as an additional area-specific QC check, the depth data acquired by each vessel was gridded separately at 4 m resolution and differenced from each other. The results are excellent, with the two vessels comparing within 0.03 m on average, with a standard deviation of 0.12 m. 100% of the grid cells agree within the allowable TVU by depth. The results are shown below.</hsd:discussion>
                    <hsd:images>
                        <hsd:caption>The results of the difference between ASV and Arctic Seal depth data for this survey.</hsd:caption>
                        <hsd:link>SupportFiles\H13718_ASVvsSeal.png</hsd:link>
                    </hsd:images>
                </hsd:results>
                <hsd:comments />
            </dr:sonarQCChecks>
            <dr:equipmentEffectiveness>
                <hsd:results deviation="true">
                    <hsd:issue>
                        <hsd:title>Along Track Gaps</hsd:title>
                        <hsd:discussion>On both survey vessels, during rough weather conditions air bubbles would occasionally be forced under the multibeam sonar head and result in temporary loss of bottom tracking or "blowouts", sometimes resulting in along-track gaps. Note that data acquired early in the project (prior to JD168) on the Arctic Seal was most affected. On JD168 a 0.6 m extension was installed on the Arctic Seal's MBES pole to position the sonar deeper in the water column. This significantly improved data quality for the remainder of the project, though in adverse conditions air could still be forced under the sonar.

In addition, intermittent sonar issues on the Arctic Seal late in project (approximately JD192 onwards), due to a possible sonar receiver issue, occasionally resulted in dropped pings. Too many consecutive dropped pings could result in an along-track gap.

Along-track gaps, either from weather or sonar issues, were examined and normally only rerun when the along-track gap exceeded three nodes (12 m horizontal distance) for mainscheme lines in depths of 20 m or less. These were not rerun where they occurred on crosslines since there was ample crossline LNM for QC purposes. Final data is within specifications.</hsd:discussion>
                        <hsd:comments />
                    </hsd:issue>
                    <hsd:issue>
                        <hsd:title>Arctic Seal MBES Arm Issues</hsd:title>
                        <hsd:discussion>The Arctic Seal's hydraulic MBES arm experienced movement that had the potential to adversely affect survey data. From approximately JD178 onwards the arm experienced intermittent hydraulic pressure drops which resulted in arm movement and therefore shifts in the sonar and IMU orientation relative to the POSMV reference frame. This was more prevalent in adverse weather when the vessel was experiencing above average roll conditions. A hinged joint in the MBES arm also experienced issues from JD178 until JD181.

Co-location of the IMU and sonar mitigated most of the effects since mount movements were captured in the motion record and largely compensated for. However, some residual error remained as a result of shifts in the reference frame, which shows up periodically as a small roll bias in Arctic Seal data, apparent at crossline intersections. To reduce the effect, small roll corrections were systematically applied in the HVF at obvious change points, and all Arctic Seal MBES data was filtered with a 55 degree nadir filter to remove outer beams most subject to the error. Following these corrections, final data is within allowable TVU.

More information on the issue and mitigation is available in the DAPR.</hsd:discussion>
                        <hsd:comments />
                    </hsd:issue>
                    <hsd:issue>
                        <hsd:title>GNSS Vertical Busts</hsd:title>
                        <hsd:discussion>Although vertical agreement between overlapping lines is generally very good, normally within 0.10 m or better, vertical busts attributable to GNSS positioning error are apparent sporadically in the data set. Any that approached or exceeded allowable TVU for their depth were investigated and addressed in processing. Final data is within specifications.</hsd:discussion>
                        <hsd:comments />
                    </hsd:issue>
                </hsd:results>
                <hsd:comments />
            </dr:equipmentEffectiveness>
            <dr:factorsAffectingSoundings>
                <hsd:results deviation="true">
                    <hsd:issue>
                        <hsd:title>Sound Speed Error</hsd:title>
                        <hsd:discussion>Sound speed error, which is characterized by a general upward or downward across-track cupping of sounding data that increases in magnitude towards the outer beams, is evident sporadically in the dataset.

Profiles were taken frequently, approximately every two hours and whenever changing areas, but some residual error remains. In processing, beam filters were applied to reject outer beams greater than 65 degrees from nadir in order to reject soundings most subject to sound speed error.

The effect on the final surfaces is relatively minor. Final data is within specifications.</hsd:discussion>
                        <hsd:comments />
                    </hsd:issue>
                    <hsd:issue>
                        <hsd:title>Bottom Change</hsd:title>
                        <hsd:discussion>The seafloor in the area is dynamic due to the large amount of sediment deposition from the many rivers draining into the area. The sediment is then readily transported by the strong tidal currents that flood the area daily. Sandwaves are present in the survey area, and data acquired distant in time, for example crosslines late in the job that cross mainscheme acquired earlier in the project, frequently show evidence of bottom change. Note that in most cases of bottom change data was not edited to "choose" a bottom.

Up to 0.4 m of vertical change was observed over the course of this survey due to bottom change in some areas. An example is shown below.</hsd:discussion>
                        <hsd:images>
                            <hsd:caption>Example of bottom change on this survey viewed in CARIS HIPS subset. Cyan line (2767) was run on JD253, 70 days after the green line (0840) run on JD183. This results in about 0.4 m of vertical change. Both lines are from the ASV.</hsd:caption>
                            <hsd:link>SupportFiles\H13718_BtmChange_Example.png</hsd:link>
                        </hsd:images>
                        <hsd:comments />
                    </hsd:issue>
                </hsd:results>
                <hsd:comments />
            </dr:factorsAffectingSoundings>
            <dr:soundSpeedMethods>
                <dr:castFrequency>2 hours</dr:castFrequency>
                <dr:discussion>Sound speed profiles or "casts" were normally acquired aboard the Arctic Seal while underway with a C-MAX Vigo profiling winch, which utilized a Valeport SWiFT sound speed profiler. Note that the ASV-CW5 was not equipped to collect sound speed profiles -- Arctic Seal sound speed profiles were used to correct all ASV sounding data, which was possible because the vessels always worked in close proximity to each other (usually within 2 kilometers).

Surface sound speed at the Arctic Seal sonar head was monitored continuously and a new cast was collected when the surface speed varied from the previous profile's speed at the same depth by greater than 2 m/s, leading to a cast interval of approximately 2 hours.

Casts were taken as deep as possible. On survey lines with significant differences in depth, the deeper portion of the line was normally favored to ensure that changes across the full water column were measured. The cast data was used to correct the sounding data using the "nearest in distance within time" (set to 2 hours) within CARIS HIPS.</dr:discussion>
                <dr:comments />
            </dr:soundSpeedMethods>
            <dr:coverageEquipmentAndMethods>
                <hsd:results deviation="false">
                    <hsd:discussion>All equipment and survey methods were used as detailed in the DAPR.</hsd:discussion>
                </hsd:results>
                <hsd:comments />
            </dr:coverageEquipmentAndMethods>
            <dr:additionalQualityControl>
                <hsd:comments />
            </dr:additionalQualityControl>
        </dr:qualityControl>
        <dr:echoSoundingCorrections>
            <dr:corrections>
                <hsd:results deviation="true">
                    <hsd:discussion>Deviations from the Correction to Echo Soundings section of the DAPR are itemized below. Despite the deviations, final data is within specifications.

GNSS Processing Exceptions

The following lines utilized Applanix Smart Base (ASB) processing instead of PPRTX to address GNSS vertical busts:

ASV, JD184, line 0869
ASV, JD200, line 1074

The following lines had altitudes loaded using CARIS Generic Data Parser (GDP) to address GNSS vertical busts that could not be repaired with other methods. GDP altitudes were smoothed, removing heave from the altitude data, therefore these lines were subsequently georeferenced with "GPS dynamic heave" set to "NONE". 

Arctic Seal, JD155, lines 0061 through 0067
Arctic Seal, JD184, lines 0600 through 0604

Delayed Heave Exceptions

These lines did not have Delayed Heave available. Realtime heave was used instead.

Arctic Seal, JD155, lines 0061 through 0067
Arctic Seal, JD184, lines 0600 through 0604
ASV, JD200, line 1072 (segment 2 only)</hsd:discussion>
                </hsd:results>
                <hsd:comments />
            </dr:corrections>
            <dr:calibrations>
                <hsd:results deviation="false">
                    <hsd:discussion>All sounding systems were calibrated as detailed in the DAPR.</hsd:discussion>
                    <hsd:calibration xsi:nil="true" />
                </hsd:results>
                <hsd:comments />
            </dr:calibrations>
            <dr:additionalIssues>
                <hsd:comments />
            </dr:additionalIssues>
        </dr:echoSoundingCorrections>
        <dr:backscatter>
            <hsd:results acquired="true">
                <hsd:discussion>All equipment and survey methods were used as detailed in the DAPR.</hsd:discussion>
            </hsd:results>
            <hsd:comments />
        </dr:backscatter>
        <dr:dataProcessing>
            <dr:drSoftware>
                <dr:featureObjectCatalog>NOAA Extended Attribute Files V2023_1</dr:featureObjectCatalog>
                <dr:discussion>The most current version of NOAA's Extended Attribute Files available at the start of survey operations was utilized for this project.</dr:discussion>
                <dr:comments />
            </dr:drSoftware>
            <dr:surfaces>
                <dr:surface>
                    <hsd:surfaceName>H13718_MB_4m_MLLW_Final</hsd:surfaceName>
                    <hsd:surfaceType>CARIS Raster Surface (CUBE)</hsd:surfaceType>
                    <hsd:resolution units="meters">4</hsd:resolution>
                    <hsd:depthRange>
                        <hsd:min units="meters">0.431</hsd:min>
                        <hsd:max units="meters">27.264</hsd:max>
                    </hsd:depthRange>
                    <hsd:surfaceParameter>NOAA_4m</hsd:surfaceParameter>
                    <hsd:purpose>MBES Set Line Spacing</hsd:purpose>
                </dr:surface>
                <dr:surface>
                    <hsd:surfaceName>H13718_MBAB_2m_400kHz_1of1</hsd:surfaceName>
                    <hsd:surfaceType>MB Backscatter Mosaic</hsd:surfaceType>
                    <hsd:resolution units="meters">2</hsd:resolution>
                    <hsd:depthRange>
                        <hsd:min units="meters">0.431</hsd:min>
                        <hsd:max units="meters">27.264</hsd:max>
                    </hsd:depthRange>
                    <hsd:surfaceParameter>N/A</hsd:surfaceParameter>
                    <hsd:purpose>MBES Set Line Spacing</hsd:purpose>
                </dr:surface>
                <dr:discussion>The final depth information for this survey was submitted as a 4 m resolution CARIS BASE surface (CSAR format) which best represents the seafloor at the time of the 2023 survey. The surface was created from fully processed data with all final corrections applied.

The surface was created using NOAA CUBE parameters and resolutions in conformance with the 2022 HSSD. The surface was finalized with a 0 to 80 m depth limit, "standard deviation" selected as the final uncertainty source, and designated soundings applied (if present). Horizontal projection was selected as WGS84 / UTM zone 4N.

A non-finalized version of the CSAR surface is also included with the survey deliverables for reference. This does not have the "_Final" designation in the filename.

The Multibeam Acoustic Backscatter (MBAB) surface(s), produced with QPS Fledermaus Geocoder Toolbox (FMGT), is also provided. MBAB data for both vessels, acquired using 400 kHz, is combined in the mosaic.</dr:discussion>
                <dr:comments />
            </dr:surfaces>
            <dr:additionalDataProcessing>
                <hsd:comments />
            </dr:additionalDataProcessing>
        </dr:dataProcessing>
    </dr:dataAcquisitionAndProcessing>
    <dr:verticalAndHorizontalControl>
        <dr:discussion>Additional information discussing the vertical or horizontal control for this survey can be found in the accompanying HVCR.</dr:discussion>
        <dr:verticalControl>
            <hsd:verticalDatum>Mean Lower Low Water</hsd:verticalDatum>
            <hsd:tideStations />
            <hsd:standard_or_ERZT xsi:nil="true" used="false" />
            <hsd:VDATUM_or_constantSep used="true">
                <hsd:methodsUsed>ERS via ERTDM</hsd:methodsUsed>
                <hsd:ellipsoidToChartDatumSepFile>
                    <hsd:fileName>OPR-R340-KR-23_AK_ERTDM_2023_WGS84(G2139)-MLLW_.csar</hsd:fileName>
                </hsd:ellipsoidToChartDatumSepFile>
                <hsd:discussion>All soundings were reduced to MLLW using the ERTDM WGS84 to MLLW separation model grid file provided by NOAA using ERS methodology. The uncertainty stated for the model in the Project Instructions
is 0.18 m.

Note all altitudes are relative to the WGS84 datum, therefore the WGS84 to MLLW ERTDM model was utilized to reduce soundings to MLLW.</hsd:discussion>
                <hsd:comments />
            </hsd:VDATUM_or_constantSep>
            <hsd:comments />
        </dr:verticalControl>
        <dr:horizontalControl>
            <hsd:horizontalDatum>World Geodetic System (WGS) 1984</hsd:horizontalDatum>
            <hsd:projection>Projected UTM 4</hsd:projection>
            <hsd:PPK used="true">
                <hsd:methodsUsed>Smart Base</hsd:methodsUsed>
                <hsd:baseStations />
                <hsd:discussion>Applanix Smart Base (ASB) was used when necessary to address GNSS vertical busts. Any lines that used ASB were itemized earlier in this report.</hsd:discussion>
                <hsd:comments />
            </hsd:PPK>
            <hsd:PPP used="true">
                <hsd:discussion>Post-processing of all navigation data for final positions was done in Applanix POSPac MMS (v8.9) software. Trimble PP-RTX was used as the primary processing methodology within POSPac, with any exceptions noted previously.</hsd:discussion>
                <hsd:comments />
            </hsd:PPP>
            <hsd:RTK used="true">
                <hsd:discussion>Real-time positions were primarily RTK. Hemisphere SmartLink antennas on each vessel were set to receive the subscription-based Atlas H-10 service, which output RTCM corrections to each vessel's POSMV, allowing them to operate in RTK mode. This assisted with real-time positioning. However, all real-time positions were replaced in post-processing with PPK corrections, as described previously.</hsd:discussion>
                <hsd:comments />
            </hsd:RTK>
            <hsd:DGPS xsi:nil="true" used="false" />
            <hsd:WAAS used="true">
                <hsd:discussion>The Wide Area Augmentation System (WAAS) was used incidentally for real-time positions as a backup when there were issues receiving RTK corrections. However, all real-time positions were replaced in postprocessing with PPK corrections, as described previously.</hsd:discussion>
                <hsd:comments />
            </hsd:WAAS>
            <hsd:comments />
        </dr:horizontalControl>
        <dr:additionalIssues>
            <hsd:issue>
                <hsd:title>HSSD Section 2.2 (NAD83)</hsd:title>
                <hsd:discussion>A waiver to HSSD Section 2.2 was was granted for this project. All products are submitted with horizontal positions as WGS84 instead of NAD83(2011). This was done to provide a consistent dataset from raw data, which was acquired in WGS84, through final processed data. See project correspondence for the waiver and additional discussion.</hsd:discussion>
                <hsd:comments />
            </hsd:issue>
            <hsd:comments />
        </dr:additionalIssues>
    </dr:verticalAndHorizontalControl>
    <dr:resultsAndRecommendations>
        <dr:chartComparison>
            <dr:methods>
                <hsd:topic>
                    <hsd:discussion>An overview of this survey overlaid on affected charts is shown below. Most of the area was uncharted at the time of this survey.</hsd:discussion>
                    <hsd:images>
                        <hsd:caption>This survey overlaid on affected ENCs. Soundings from this survey are blue. All soundings in meters.</hsd:caption>
                        <hsd:link>SupportFiles\H13718_Chart.png</hsd:link>
                    </hsd:images>
                </hsd:topic>
                <hsd:comments />
            </dr:methods>
            <dr:charts>
                <hsd:ENC>
                    <hsd:name>US4AK3XU</hsd:name>
                    <hsd:scale>90000</hsd:scale>
                    <hsd:edition>1</hsd:edition>
                    <hsd:updateApplicationDate>2023-12-12</hsd:updateApplicationDate>
                    <hsd:issueDate>2023-12-12</hsd:issueDate>
                </hsd:ENC>
                <hsd:ENC>
                    <hsd:name>US4AK3XT</hsd:name>
                    <hsd:scale>90000</hsd:scale>
                    <hsd:edition>1</hsd:edition>
                    <hsd:updateApplicationDate>2023-12-12</hsd:updateApplicationDate>
                    <hsd:issueDate>2023-12-12</hsd:issueDate>
                </hsd:ENC>
                <hsd:ENC>
                    <hsd:name>US4AK3YU</hsd:name>
                    <hsd:scale>90000</hsd:scale>
                    <hsd:edition>1</hsd:edition>
                    <hsd:updateApplicationDate>2023-12-12</hsd:updateApplicationDate>
                    <hsd:issueDate>2023-12-12</hsd:issueDate>
                </hsd:ENC>
                <hsd:comments />
            </dr:charts>
            <dr:shoalAndHazardousFeatures>
                <hsd:results investigated="None Exist">
                    <hsd:discussion>No shoals or potentially hazardous features exist for this survey. No Danger to Navigation Reports were submitted for this survey.</hsd:discussion>
                </hsd:results>
                <hsd:comments />
            </dr:shoalAndHazardousFeatures>
            <dr:chartedFeatures>
                <hsd:results investigated="None Exist">
                    <hsd:discussion>No charted features exist for this survey.</hsd:discussion>
                </hsd:results>
                <hsd:comments />
            </dr:chartedFeatures>
            <dr:unchartedFeatures>
                <hsd:results investigated="None Exist">
                    <hsd:discussion>No uncharted features exist for this survey.</hsd:discussion>
                </hsd:results>
                <hsd:comments />
            </dr:unchartedFeatures>
            <dr:channels>
                <hsd:results investigated="None Exist">
                    <hsd:discussion>No channels exist within the survey limits.</hsd:discussion>
                </hsd:results>
                <hsd:comments />
            </dr:channels>
        </dr:chartComparison>
        <dr:additionalResults>
            <dr:ATONS>
                <hsd:results investigated="None Exist">
                    <hsd:discussion>No Aids to navigation (ATONs) exist for this survey.</hsd:discussion>
                </hsd:results>
                <hsd:comments />
            </dr:ATONS>
            <dr:maritimeBoundary>
                <hsd:results investigated="Investigated">
                    <hsd:discussion>Three MBPs were assigned for this survey.

The MBPs were investigated with a skiff on July 18th, 2023 (UTC) when the tide was at or near 0 m MLLW. The assigned locations were investigated by approaching as close as safely possible. The western two MBPs were observed to be exposed at MLLW and were confirmed to be at their assigned location by range and bearing. Photographs were taken. They could not be approached closer due to insufficient tide. 

The eastern MBP was similarly investigated during the same skiff deployment, but could not be found. The site could not be visited again for additional investigation due to safety issues as the area was usually awash with swells when in the area.

Refer to the FFF for results.</hsd:discussion>
                    <hsd:images>
                        <hsd:caption>The western-most MBP.</hsd:caption>
                        <hsd:link>SupportFiles\H13718_MBP1.png</hsd:link>
                    </hsd:images>
                </hsd:results>
                <hsd:comments />
            </dr:maritimeBoundary>
            <dr:bottomSamples>
                <hsd:results investigated="Investigated">
                    <hsd:discussion>The Project Instructions required one bottom sample per 20 SNM of surveyed area. 11 were therefore acquired in this area. Bottom sample locations were chosen in regards to the acquired survey data backscatter. Samples were examined, photographed, and then discarded overboard.

All samples returned sand as their primary constituent. The image below shows their relative location within the survey area. Refer to the FFF for results.</hsd:discussion>
                    <hsd:images>
                        <hsd:caption>An overview of bottom sample results.</hsd:caption>
                        <hsd:link>SupportFiles\H13718_Bottom_Samples.png</hsd:link>
                    </hsd:images>
                </hsd:results>
                <hsd:comments />
            </dr:bottomSamples>
            <dr:overheadFeatures>
                <hsd:results investigated="None Exist">
                    <hsd:discussion>No overhead features exist for this survey.</hsd:discussion>
                </hsd:results>
                <hsd:comments />
            </dr:overheadFeatures>
            <dr:submarineFeatures>
                <hsd:results investigated="None Exist">
                    <hsd:discussion>No submarine features exist for this survey.</hsd:discussion>
                </hsd:results>
                <hsd:comments />
            </dr:submarineFeatures>
            <dr:platforms>
                <hsd:results investigated="None Exist">
                    <hsd:discussion>No platforms exist for this survey.</hsd:discussion>
                </hsd:results>
                <hsd:comments />
            </dr:platforms>
            <dr:ferryRoutesAndTerminals>
                <hsd:results investigated="None Exist">
                    <hsd:discussion>No ferry routes or terminals exist for this survey.</hsd:discussion>
                </hsd:results>
                <hsd:comments />
            </dr:ferryRoutesAndTerminals>
            <dr:abnormalSeafloorEnviroCond>
                <hsd:results investigated="None Exist">
                    <hsd:discussion>Any abnormal seafloor or environmental conditions were discussed previously in this report.</hsd:discussion>
                </hsd:results>
                <hsd:comments />
            </dr:abnormalSeafloorEnviroCond>
            <dr:constructionOrDredging>
                <hsd:results investigated="None Exist">
                    <hsd:discussion>No present or planned construction or dredging exist within the survey limits.</hsd:discussion>
                </hsd:results>
                <hsd:comments />
            </dr:constructionOrDredging>
            <dr:newSurveyRecommendation>
                <hsd:results recommended="false">
                    <hsd:discussion>No new surveys or further investigations are recommended for this area.</hsd:discussion>
                </hsd:results>
                <hsd:comments />
            </dr:newSurveyRecommendation>
            <dr:ENCScaleRecommendation>
                <hsd:results recommended="false">
                    <hsd:discussion>No new ENC scales are recommended for this area.</hsd:discussion>
                </hsd:results>
                <hsd:comments />
            </dr:ENCScaleRecommendation>
        </dr:additionalResults>
    </dr:resultsAndRecommendations>
    <dr:approvalSheet>
        <dr:statements>
            <dr: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.</dr:supervision>
            <dr: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.</dr:approval>
            <dr:adequacyOfSurvey>The survey data meets or exceeds requirements as set forth in the NOS Hydrographic Surveys Specifications and Deliverables, Hydrographic Survey Project Instructions, and Statement of Work. 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, if any, noted in the Descriptive Report.</dr:adequacyOfSurvey>
            <dr:additionalInfo xsi:nil="true" />
        </dr:statements>
        <dr:signingPersonnel>
            <hsd:approverName>Andrew Orthmann</hsd:approverName>
            <hsd:approverTitle>Charting Program Manager</hsd:approverTitle>
            <hsd:approvalDate>2024-01-17</hsd:approvalDate>
        </dr:signingPersonnel>
        <dr:additionalReports>
            <hsd:reportName>Final Progress Report</hsd:reportName>
            <hsd:reportDateSent>2023-10-23</hsd:reportDateSent>
        </dr:additionalReports>
        <dr:additionalReports>
            <hsd:reportName>Survey Outline Submittal</hsd:reportName>
            <hsd:reportDateSent>2023-10-23</hsd:reportDateSent>
        </dr:additionalReports>
        <dr:additionalReports>
            <hsd:reportName>MMO Logsheets and Training Observer Logs</hsd:reportName>
            <hsd:reportDateSent>2023-10-23</hsd:reportDateSent>
        </dr:additionalReports>
        <dr:additionalReports>
            <hsd:reportName>NCEI Sound Speed Data Submittal</hsd:reportName>
            <hsd:reportDateSent>2023-12-01</hsd:reportDateSent>
        </dr:additionalReports>
        <dr:additionalReports>
            <hsd:reportName>Coast Pilot Review Report</hsd:reportName>
            <hsd:reportDateSent>2024-01-08</hsd:reportDateSent>
        </dr:additionalReports>
    </dr:approvalSheet>
</dr:descriptiveReport>