<?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-E347-KR-22</hsd:number>
            <hsd:name>Central Chesapeake Bay, MD</hsd:name>
            <hsd:generalLocality>Central Chesapeake Bay</hsd:generalLocality>
            <hsd:fieldUnit>Leidos</hsd:fieldUnit>
        </dr:projectMetadata>
        <dr:registryMetadata>
            <hsd:registryNumber>H13516</hsd:registryNumber>
            <hsd:sheetID>6</hsd:sheetID>
            <hsd:registryInstructions xsi:nil="true" />
            <hsd:sublocality>3 NM Northwest of Love Point</hsd:sublocality>
            <hsd:stateOrTerritory>Maryland</hsd:stateOrTerritory>
            <hsd:country>United States</hsd:country>
            <hsd:scale>10000</hsd:scale>
        </dr:registryMetadata>
        <dr:surveyMetadata>
            <hsd:year>2023</hsd:year>
            <hsd:chiefOfParty>Bridget W. Bernier</hsd:chiefOfParty>
            <hsd:projectType>Basic Hydrographic Survey</hsd:projectType>
            <hsd:PIDate>2022-08-23</hsd:PIDate>
            <hsd:datesOfSurvey>
                <hsd:start>2022-09-21</hsd:start>
                <hsd:end>2023-04-27</hsd:end>
            </hsd:datesOfSurvey>
            <hsd:equipmentTypes>
                <hsd:soundingEquipment>Multibeam Echo Sounder</hsd:soundingEquipment>
                <hsd:imageryEquipment>Side Scan Sonar</hsd:imageryEquipment>
                <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>Atlantic 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 NAD83 UTM 18N, 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>H13516 was located within the Central Chesapeake Bay, Maryland 3NM northwest of Love Point (Figure 1). The survey was conducted in accordance with coverage requirements listed in the Project Instructions (PI) OPR-E347-KR-22.

</hsd:discussion>
            <hsd:limits>
                <hsd:northWest>
                    <hsd:latitude hemisphere="N">39.14474297222222</hsd:latitude>
                    <hsd:longitude hemisphere="W">76.4070436388889</hsd:longitude>
                </hsd:northWest>
                <hsd:southEast>
                    <hsd:latitude hemisphere="N">39.01976530555555</hsd:latitude>
                    <hsd:longitude hemisphere="W">76.29129072222221</hsd:longitude>
                </hsd:southEast>
            </hsd:limits>
            <hsd:images>
                <hsd:caption>H13516 Survey Bounds</hsd:caption>
                <hsd:link>file:///B:/OPR-E347-KR-22/Surveys/H13516/01_HDR/Reports/Descriptive_Report/SupportFiles/H13516_Figure_01.png</hsd:link>
            </hsd:images>
            <hsd:comments />
        </dr:areaDescription>
        <dr:surveyLimits>
            <hsd:results deviation="true">
                <hsd:discussion>Survey limits were acquired in accordance with the requirements in the PI and the Hydrographic Survey Specifications and Deliverables (HSSD), March 2022.</hsd:discussion>
            </hsd:results>
            <hsd:comments />
        </dr:surveyLimits>
        <dr:surveyPurpose>
            <hsd:topic>
                <hsd:discussion>The Chesapeake Bay is the largest estuary in North America and heavily trafficked by commercial and recreational vessels as tourism, fishing, and marine commerce are economically vital for the region. In addition to fishing and tourism traffic, commercial vessels transit through the project area to reach the Port of Baltimore, which is ranked as a top 15 port in container and tonnage, and a top 10 port for dry bulk.

The majority of the prior data in the project area spans from the 1880s to 1940s. The bathymetric data vintage coupled with numerous storms and hurricanes having potentially changed the seabed over the last century raises a need to survey the area. In addition, the Ever Forward container ship ran aground near the Craighill Channel in March 2022, and was removed after 35 days. 206,230 cubic yards of material was dredged and taken to Poplar Island. The data from this project will provide modern bathymetry for updating National Ocean Service nautical charting products improving the safety of maritime traffic and commerce as well as supporting the Seabed 2030 global mapping initiative. Survey data from this project is intended to supersede all prior survey data in the common area.</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>Leidos warrants only that the survey data acquired by Leidos and delivered to NOAA under Contract 1305M220DNCNJ0056 reflects the state of the sea floor in existence on the day and at the time the survey was conducted.

H13516 was surveyed in accordance with the following documents:
1. 1305M220DNCNJ0056 signed.pdf, received 23 August 2022
2. Hydrographic Survey Specifications and Deliverables (HSSD), March 2022
3. PRF.000, received 24 August 2022
4. CSF.000, received 24 August 2022
5. OPR-E347-KR-22 Project Brief, held 07 September 2022</hsd:discussion>
            <hsd:comments />
        </dr:surveyQuality>
        <dr:surveyCoverage>
            <hsd:coverageRequirement>
                <hsd:waterDepth>Sheet 6</hsd:waterDepth>
                <hsd:requiredCoverage>Object Detection Coverage (Refer to HSSD Section 5.2.2.2)</hsd:requiredCoverage>
            </hsd:coverageRequirement>
            <hsd:coverageRequirement>
                <hsd:waterDepth>Inshore limit to 8 meters water depth</hsd:waterDepth>
                <hsd:requiredCoverage>Sidescan may be acquired at an altitude of 6-20% of the range scale.</hsd:requiredCoverage>
            </hsd:coverageRequirement>
            <hsd:results deviation="true">
                <hsd:discussion>Survey coverage achieved was in accordance with the requirements in the PI and the HSSD (Figure 2). Leidos chose to achieve the coverage requirement using Object Detection Coverage, Option A and B (100% multibeam coverage and 200% side scan sonar coverage with concurrent multibeam). In many areas of H13516 the inshore limit of the Navigable Area Limit Line (NALL) was reached seaward of the assigned survey bounds. Leidos surveyed to the NALL as defined by HSSD Section 1.3.2; within the surveyed bounds. However, due to safety concerns for personnel and survey equipment, some areas were not fully covered with multibeam echo sounder (MBES) data to exactly the 3.5-meter depth contour. This was due to limited vessel maneuverability around the shoal depth areas, at these discrete locations. In these areas the side scan sonar (SSS) swath extended shoreward of the MBES swath, and indicated that the seafloor continued to rise abruptly and in a manner that the vessel could not navigate over for further MBES coverage; while also indicating in the SSS data that there were no significant objects that would require individual cartographic representation.



</hsd:discussion>
                <hsd:images>
                    <hsd:caption>Final Bathymetry Coverage for H13516</hsd:caption>
                    <hsd:link>file:///B:/OPR-E347-KR-22/Surveys/H13516/01_HDR/Reports/Descriptive_Report/SupportFiles/H13516_Figure_02.png</hsd:link>
                </hsd:images>
            </hsd:results>
            <hsd:comments />
        </dr:surveyCoverage>
        <dr:coverageGraphic>
            <hsd:coverageGraphicImage />
        </dr:coverageGraphic>
        <dr:surveyStatistics>
            <hsd:LNM>
                <hsd:vesselLNM>
                    <hsd:vessel>
                        <hsd:hullID>R/V Sea Innovator I</hsd:hullID>
                        <hsd:statistics>
                            <hsd:MS_SBES>0.0</hsd:MS_SBES>
                            <hsd:MS_MBES>0.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>1089.82</hsd:MS_MBES_SSS>
                            <hsd:MS_SBES_SSS>0.0</hsd:MS_SBES_SSS>
                            <hsd:XL_MBES_SBES>56.79</hsd:XL_MBES_SBES>
                            <hsd:XL_lidar>0.0</hsd:XL_lidar>
                        </hsd:statistics>
                    </hsd:vessel>
                    <hsd:vessel>
                        <hsd:hullID>R/V Oyster Bay II</hsd:hullID>
                        <hsd:statistics>
                            <hsd:MS_SBES>0.0</hsd:MS_SBES>
                            <hsd:MS_MBES>0.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>533.48</hsd:MS_MBES_SSS>
                            <hsd:MS_SBES_SSS>0.0</hsd:MS_SBES_SSS>
                            <hsd:XL_MBES_SBES>26.91</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>0.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>1623.3</hsd:MS_MBES_SSS>
                    <hsd:MS_SBES_SSS>0.0</hsd:MS_SBES_SSS>
                    <hsd:XL_MBES_SBES>83.7</hsd:XL_MBES_SBES>
                    <hsd:XL_lidar>0.0</hsd:XL_lidar>
                    <hsd:percentXLLNM>5.15</hsd:percentXLLNM>
                </hsd:totalLNM>
            </hsd:LNM>
            <hsd:totalSurveyStats>
                <hsd:bottomSamples>5</hsd:bottomSamples>
                <hsd:maritimeBoundaryPoints>0</hsd:maritimeBoundaryPoints>
                <hsd:DP>0</hsd:DP>
                <hsd:diveOps>0</hsd:diveOps>
                <hsd:SNM>31.0</hsd:SNM>
            </hsd:totalSurveyStats>
            <hsd:surveyDates>2022-09-21</hsd:surveyDates>
            <hsd:surveyDates>2022-10-04</hsd:surveyDates>
            <hsd:surveyDates>2022-10-05</hsd:surveyDates>
            <hsd:surveyDates>2022-10-06</hsd:surveyDates>
            <hsd:surveyDates>2022-10-07</hsd:surveyDates>
            <hsd:surveyDates>2022-10-08</hsd:surveyDates>
            <hsd:surveyDates>2022-10-09</hsd:surveyDates>
            <hsd:surveyDates>2022-10-10</hsd:surveyDates>
            <hsd:surveyDates>2022-10-11</hsd:surveyDates>
            <hsd:surveyDates>2022-10-12</hsd:surveyDates>
            <hsd:surveyDates>2022-10-13</hsd:surveyDates>
            <hsd:surveyDates>2022-10-14</hsd:surveyDates>
            <hsd:surveyDates>2022-10-16</hsd:surveyDates>
            <hsd:surveyDates>2022-10-21</hsd:surveyDates>
            <hsd:surveyDates>2022-10-22</hsd:surveyDates>
            <hsd:surveyDates>2022-10-24</hsd:surveyDates>
            <hsd:surveyDates>2022-10-25</hsd:surveyDates>
            <hsd:surveyDates>2022-11-02</hsd:surveyDates>
            <hsd:surveyDates>2022-11-03</hsd:surveyDates>
            <hsd:surveyDates>2023-03-05</hsd:surveyDates>
            <hsd:surveyDates>2023-03-06</hsd:surveyDates>
            <hsd:surveyDates>2023-03-12</hsd:surveyDates>
            <hsd:surveyDates>2023-03-13</hsd:surveyDates>
            <hsd:surveyDates>2023-03-16</hsd:surveyDates>
            <hsd:surveyDates>2023-03-20</hsd:surveyDates>
            <hsd:surveyDates>2023-03-21</hsd:surveyDates>
            <hsd:surveyDates>2023-03-22</hsd:surveyDates>
            <hsd:surveyDates>2023-04-27</hsd:surveyDates>
            <hsd:discussion xsi:nil="true" />
            <hsd:comments />
        </dr:surveyStatistics>
    </dr:areaSurveyed>
    <dr:dataAcquisitionAndProcessing>
        <dr:equipmentAndVessels>
            <dr:discussion>Leidos used their ISS-2000 software on a Windows platform to acquire these survey data. Survey planning and data analysis were conducted using the Leidos SABER software on Linux platforms. Side scan sonar (SSS) data were collected on a Windows platform using Klein’s SonarPro software. Subsequent processing and review of the SSS data, including the generation of coverage mosaics, were accomplished using SABER.

A detailed description of the systems and vessel used to acquire and process these data is included in the Data Acquisition and Processing Report (DAPR) for OPR-E347-KR-22, delivered previously with H13511. There were no variations from the equipment configuration described in the DAPR.</dr:discussion>
            <dr:vessels>
                <dr:vessel>
                    <hsd:hullID>R/V Sea Innovator 1</hsd:hullID>
                    <hsd:LOA units="feet">135.0</hsd:LOA>
                    <hsd:draft units="feet">9.0</hsd:draft>
                </dr:vessel>
                <dr:vessel>
                    <hsd:hullID>R/V Oyster Bay II</hsd:hullID>
                    <hsd:LOA units="feet">30.0</hsd:LOA>
                    <hsd:draft units="feet">3.0</hsd:draft>
                </dr:vessel>
                <dr:images>
                    <hsd:caption>R/V Sea Innovator 1</hsd:caption>
                    <hsd:link>file:///B:/OPR-E347-KR-22/Surveys/H13516/01_HDR/Reports/Descriptive_Report/SupportFiles/H13516_Figure_03.png</hsd:link>
                </dr:images>
                <dr:images>
                    <hsd:caption>R/V Oyster Bay II</hsd:caption>
                    <hsd:link>file:///B:/OPR-E347-KR-22/Surveys/H13516/01_HDR/Reports/Descriptive_Report/SupportFiles/H13516_Figure_04.png</hsd:link>
                </dr:images>
                <dr:discussion>The R/V Sea Innovator I (Figure 3) was used to collect multibeam echo sounder (MBES) (RESON SeaBat T50), side scan sonar (SSS) (Klein 4000), and sound speed data during twenty four hours per day survey operations. The R/V Oyster Bay II (Figure 4) was used to collect multibeam echo sounder (MBES) (RESON SeaBat T50), side scan sonar (SSS) (Klein 4900), and sound speed data during twelve hours per day survey operations. 

A detailed description of the vessels used is included in the DAPR.</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>SSS</hsd:type>
                    <hsd:manufacturer>Klein Marine Systems</hsd:manufacturer>
                    <hsd:model>System 4000</hsd:model>
                </dr:majorSystem>
                <dr:majorSystem>
                    <hsd:type>SSS</hsd:type>
                    <hsd:manufacturer>Klein Marine Systems</hsd:manufacturer>
                    <hsd:model>System 4900</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>Conductivity, Temperature, and Depth Sensor</hsd:type>
                    <hsd:manufacturer>AML Oceanographic</hsd:manufacturer>
                    <hsd:model>MVP30</hsd:model>
                </dr:majorSystem>
                <dr:majorSystem>
                    <hsd:type>Sound Speed System</hsd:type>
                    <hsd:manufacturer>AML Oceanographic</hsd:manufacturer>
                    <hsd:model>BaseX</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:discussion>A detailed description of the equipment installed is included in the DAPR.
</dr:discussion>
                <dr:comments />
            </dr:equipment>
            <dr:comments />
        </dr:equipmentAndVessels>
        <dr:qualityControl>
            <dr:crosslines>
                <hsd:topic>
                    <hsd:discussion>Multibeam echo sounder crosslines acquired for this survey totaled 5.15% of mainscheme acquisition. The resulting crossline to mainscheme percentage met the requirement to achieve approximately four percent of mainscheme mileage for a object detection coverage multibeam survey (Section 5.2.4.2 of the HSSD). 

The mainscheme lines were spaced 40 meters apart, and crosslines were generally spaced 750 meters apart. In the field, hydrographers conducted daily comparisons of mainscheme to near nadir crossline data to ensure that no systematic errors were introduced and to identify potential problems with the survey systems. After the application of all correctors and completion of final processing in the office, separate CUBE PFM grids were built at 50-centimeter resolution for all data. One grid contained the full valid swath (±65° from nadir, Class 2) of mainscheme multibeam and the other included only the near nadir swath (±5° from nadir, Class 1) crossline data. The difference grid was created by subtracting the 50-centimeter H13516 mainscheme CUBE depths from the 50-centimeter H13516 crossline CUBE depths. Additional comparisons were conducted of each vessel’s mainscheme to crossline depth data. These results are summarized in Figure 5. 

The SABER Frequency Distribution Tool was used to analyze the difference grid created from the mainscheme and crossline PFM grids and the results of the analysis were compiled into the following section.

Section 5.2.4.2 of the HSSD states that the depth difference values are to be within the maximum allowable Total Vertical Uncertainty [TVU]. For all the crossline to mainscheme analysis conducted for H13516, 100% of the comparisons were within TVU. Results for all crossing analysis are summarized in Figure 5.

As multiple vessels were used to survey H13516 repeatability analysis was performed between the data collected by both vessels where coincident. Of the vessel to vessel analysis, 99.99% of the comparisons were within TVU. Results are summarized in Figure 6; comparisons which exceeded the maximum allowable TVU were associated with features.

Results for analysis conducted are presented in Figure 7 to Figure 14.
</hsd:discussion>
                    <hsd:images>
                        <hsd:caption>Summary of Crossing Analysis</hsd:caption>
                        <hsd:link>file:///B:/OPR-E347-KR-22/Surveys/H13516/01_HDR/Reports/Descriptive_Report/SupportFiles/H13516_Figure_05.png</hsd:link>
                    </hsd:images>
                    <hsd:images>
                        <hsd:caption>Summary of Vessel Comparison Repeatability Analysis</hsd:caption>
                        <hsd:link>file:///B:/OPR-E347-KR-22/Surveys/H13516/01_HDR/Reports/Descriptive_Report/SupportFiles/H13516_Figure_06.png</hsd:link>
                    </hsd:images>
                    <hsd:images>
                        <hsd:caption>Tabular Results Crossing Analysis, Crosslines vs. Mainscheme Lines</hsd:caption>
                        <hsd:link>file:///B:/OPR-E347-KR-22/Surveys/H13516/01_HDR/Reports/Descriptive_Report/SupportFiles/H13516_Figure_07.png</hsd:link>
                    </hsd:images>
                    <hsd:images>
                        <hsd:caption>Plot of Crossing Analysis Crosslines vs. Mainscheme Lines</hsd:caption>
                        <hsd:link>file:///B:/OPR-E347-KR-22/Surveys/H13516/01_HDR/Reports/Descriptive_Report/SupportFiles/H13516_Figure_08.png</hsd:link>
                    </hsd:images>
                    <hsd:images>
                        <hsd:caption>Tabular Results Crossing Analysis, R/V Sea Innovator I Crosslines vs. Mainscheme Lines</hsd:caption>
                        <hsd:link>file:///B:/OPR-E347-KR-22/Surveys/H13516/01_HDR/Reports/Descriptive_Report/SupportFiles/H13516_Figure_09.png</hsd:link>
                    </hsd:images>
                    <hsd:images>
                        <hsd:caption>Plot of Crossing Analysis R/V Sea Innovator I Crosslines vs. Mainscheme Lines</hsd:caption>
                        <hsd:link>file:///B:/OPR-E347-KR-22/Surveys/H13516/01_HDR/Reports/Descriptive_Report/SupportFiles/H13516_Figure_10.png</hsd:link>
                    </hsd:images>
                    <hsd:images>
                        <hsd:caption>Tabular Results Crossing Analysis, R/V Oyster Bay II Crosslines vs. Mainscheme Lines</hsd:caption>
                        <hsd:link>file:///B:/OPR-E347-KR-22/Surveys/H13516/01_HDR/Reports/Descriptive_Report/SupportFiles/H13516_Figure_11.png</hsd:link>
                    </hsd:images>
                    <hsd:images>
                        <hsd:caption>Plot of Crossing Analysis R/V Oyster Bay II Crosslines vs. Mainscheme Lines</hsd:caption>
                        <hsd:link>file:///B:/OPR-E347-KR-22/Surveys/H13516/01_HDR/Reports/Descriptive_Report/SupportFiles/H13516_Figure_12.png</hsd:link>
                    </hsd:images>
                    <hsd:images>
                        <hsd:caption>Tabular Results Vessel Comparison Analysis, R/V Sea Innovator I vs. R/V Oyster Bay II</hsd:caption>
                        <hsd:link>file:///B:/OPR-E347-KR-22/Surveys/H13516/01_HDR/Reports/Descriptive_Report/SupportFiles/H13516_Figure_13.png</hsd:link>
                    </hsd:images>
                    <hsd:images>
                        <hsd:caption>Plot of Vessel Comparison Analysis R/V Sea Innovator I vs. R/V Oyster Bay II</hsd:caption>
                        <hsd:link>file:///B:/OPR-E347-KR-22/Surveys/H13516/01_HDR/Reports/Descriptive_Report/SupportFiles/H13516_Figure_14.png</hsd:link>
                    </hsd:images>
                </hsd:topic>
                <hsd:comments />
            </dr:crosslines>
            <dr:uncertainty>
                <hsd:values>
                    <hsd:tideUncertainty>
                        <hsd:tideMethod>ERS via VDATUM</hsd:tideMethod>
                        <hsd:measured units="meters">0.092</hsd:measured>
                        <hsd:zoning units="meters">0.2</hsd:zoning>
                    </hsd:tideUncertainty>
                    <hsd:soundSpeedUncertainty>
                        <hsd:hullID>R/V Sea Innovator I</hsd:hullID>
                        <hsd:measuredCTD units="meters/second">1.0</hsd:measuredCTD>
                        <hsd:measuredMVP units="meters/second">1.0</hsd:measuredMVP>
                        <hsd:measuredXBT units="meters/second">1.0</hsd:measuredXBT>
                        <hsd:surface units="meters/second">1.0</hsd:surface>
                    </hsd:soundSpeedUncertainty>
                    <hsd:soundSpeedUncertainty>
                        <hsd:hullID>R/V Oyster Bay II</hsd:hullID>
                        <hsd:measuredCTD units="meters/second">1.0</hsd:measuredCTD>
                        <hsd:measuredMVP units="meters/second">1.0</hsd:measuredMVP>
                        <hsd:measuredXBT units="meters/second">1.0</hsd:measuredXBT>
                        <hsd:surface units="meters/second">1.0</hsd:surface>
                    </hsd:soundSpeedUncertainty>
                </hsd:values>
                <hsd:discussion>For specific details on the use and application of the SABER Total Propagated Uncertainty (TPU) model, refer to the DAPR. Once the TPU model was applied to the GSF bathymetry data, each beam was attributed with the horizontal uncertainty and the vertical uncertainty at the 95% confidence level. The vertical and horizontal uncertainty values, estimated by the TPU model for individual multibeam soundings, varied little across the dataset, tending to be most affected by beam angle. Individual soundings that had vertical and horizontal uncertainty values above IHO S-44 6th Edition, Order 1a were flagged as invalid during the uncertainty attribution.

As discussed in the DAPR, SABER generates two vertical uncertainty surfaces; the Hypothesis Standard Deviation (Hyp. StdDev) and the Hypothesis Average Total Propagated Uncertainty (Hyp. AvgTPU). A third vertical uncertainty surface is generated from the larger value of these two uncertainties at each node and is referred to as the Hypothesis Final Uncertainty (Hyp. Final Uncertainty).

The final H13516 50-centimeter PFM CUBE surface contained final vertical uncertainties that ranged from 0.200 meters to 1.699 meters. The IHO Order 1a maximum allowable vertical uncertainty was calculated to range between 0.501 to 0.561 meters, based on the minimum CUBE depth (1.538 meters) and maximum CUBE depth (19.664 meters). Results from the SABER Check PFM Uncertainty function identified that there were 12,607 nodes in the final H13516 50-centimeter PFM CUBE surface with final vertical uncertainties that exceeded IHO Order 1a allowable vertical uncertainty. Nodes which exceeded IHO Order 1a were associated with objects found within the survey area, along steep slopes or areas containing reduced MBES data. The SABER Frequency Distribution Tool was also used to review the Hyp. Final Uncertainty surface within the final H13516 50-centimeter CUBE PFM grid. Results showed that 98.52% of all nodes had final uncertainties less than or equal to 0.220 meters.
</hsd:discussion>
                <hsd:comments />
            </dr:uncertainty>
            <dr:junctions>
                <hsd:discussion>Per the PI, junction analysis was performed between H13516 and the surveys listed in the table below and illustrated in Figure 15; results are discussed below. The analysis between H13516 and H13517 was provided within the H13517 Descriptive Report.


</hsd:discussion>
                <hsd:images>
                    <hsd:caption>General Locality of H13516 with Junctioning Surveys</hsd:caption>
                    <hsd:link>file:///B:/OPR-E347-KR-22/Surveys/H13516/01_HDR/Reports/Descriptive_Report/SupportFiles/H13516_Figure_15.png</hsd:link>
                </hsd:images>
                <hsd:junction>
                    <hsd:survey>
                        <hsd:registryNumber>H13684</hsd:registryNumber>
                        <hsd:scale>10000</hsd:scale>
                        <hsd:year>2023</hsd:year>
                        <hsd:fieldUnit>Leidos</hsd:fieldUnit>
                        <hsd:relativeLocation>W</hsd:relativeLocation>
                    </hsd:survey>
                    <hsd:discussion>Junctioning survey H13684 was conducted in 2022-2023 and junctions to the west of H13516. For this analysis the H13684 1-meter CUBE depth surface was compared to the H13516 50-centimeter CUBE depth surface. Junction analysis was conducted on the common area of these two sheets, with an overlapping area approximately 12,400 by 480 meters meters along the western edge of H13516. Observed depths within the common area were 2.877 to 10.489 meters, which resulted in a calculated allowable TVU range of 0.501 to 0.518 meters. 

The difference grid was generated by subtracting the H13684 data from the H13516 data. Positive values indicate that H13516 depth data were deeper than H13684 depth data. Throughout the common area, H13516 CUBE depths were deeper 96.01% of the time and were shoaler 3.77% of the time (Figure 16). The distribution is centered on zero as presented in Figure 17. Differences exceeding the calculated allowable TVU range are attributed to the bottom topography gridded at different node resolutions. 
</hsd:discussion>
                    <hsd:images>
                        <hsd:caption>Tabular Results Junction Analysis H13516 vs. H13684</hsd:caption>
                        <hsd:link>file:///B:/OPR-E347-KR-22/Surveys/H13516/01_HDR/Reports/Descriptive_Report/SupportFiles/H13516_Figure_16.png</hsd:link>
                    </hsd:images>
                    <hsd:images>
                        <hsd:caption>Plot of Junction Analysis H13516 vs. H13684</hsd:caption>
                        <hsd:link>file:///B:/OPR-E347-KR-22/Surveys/H13516/01_HDR/Reports/Descriptive_Report/SupportFiles/H13516_Figure_17.png</hsd:link>
                    </hsd:images>
                    <hsd:comments />
                </hsd:junction>
                <hsd:junction>
                    <hsd:survey>
                        <hsd:registryNumber>H13508</hsd:registryNumber>
                        <hsd:scale>5000</hsd:scale>
                        <hsd:year>2021</hsd:year>
                        <hsd:fieldUnit>NOAA Ship Thomas Jefferson</hsd:fieldUnit>
                        <hsd:relativeLocation>S</hsd:relativeLocation>
                    </hsd:survey>
                    <hsd:discussion>Junctioning survey H13508 was conducted in 2021 and junctions to the south of H13516. For this analysis the NOAA provided H13508 BAG (H13508_MB_VR_MLLW_1of1.bag) depth surface was compared to the H13516 50-centimeter CUBE depth surface. Junction analysis was conducted on the common area of these two sheets, with an overlapping area approximately 5,100 by 290 meters along the southern edge of H13516. Observed depths within the common area were 2.222 to 18.130 meters, which resulted in a calculated allowable TVU range of 0.501 to 0.553 meters. 

The difference grid was generated by subtracting the H13508 data from the H13516 data. Positive values indicate that H13516 depth data were deeper than H13508 depth data. Throughout the common area, H13516 CUBE depths were deeper 49.02% of the time and were shoaler 50.54% of the time (Figure 18). The distribution is centered on zero as presented in Figure 19. Differences exceeding the calculated allowable TVU range are attributed to the difference in node resolution as the H13508 was a variable resolution source grid stored at a course single node resolution (70-meter) within the NOAA provided BAG file. CUBE depths were in agreement between the two sheets.
</hsd:discussion>
                    <hsd:images>
                        <hsd:caption>Tabular Results Junction Analysis H13516 vs. H13508</hsd:caption>
                        <hsd:link>file:///B:/OPR-E347-KR-22/Surveys/H13516/01_HDR/Reports/Descriptive_Report/SupportFiles/H13516_Figure_18.png</hsd:link>
                    </hsd:images>
                    <hsd:images>
                        <hsd:caption>Plot of Junction Analysis H13516 vs. H13508</hsd:caption>
                        <hsd:link>file:///B:/OPR-E347-KR-22/Surveys/H13516/01_HDR/Reports/Descriptive_Report/SupportFiles/H13516_Figure_19.png</hsd:link>
                    </hsd:images>
                    <hsd:comments />
                </hsd:junction>
                <hsd:comments />
            </dr:junctions>
            <dr:sonarQCChecks>
                <hsd:results deviation="true">
                    <hsd:discussion>Sonar system quality control checks were conducted as detailed in the DAPR.</hsd:discussion>
                </hsd:results>
                <hsd:comments />
            </dr:sonarQCChecks>
            <dr:equipmentEffectiveness>
                <hsd:results deviation="false">
                    <hsd:issue>
                        <hsd:title>None Exist</hsd:title>
                        <hsd:discussion>There were no conditions or deficiencies that affected equipment operational effectiveness.</hsd:discussion>
                        <hsd:comments />
                    </hsd:issue>
                </hsd:results>
                <hsd:comments />
            </dr:equipmentEffectiveness>
            <dr:factorsAffectingSoundings>
                <hsd:results deviation="true">
                    <hsd:issue>
                        <hsd:title>Factors Affecting Soundings</hsd:title>
                        <hsd:discussion>Dense biological interference were observed during discrete areas and during various days of survey which required numerous holiday reruns. Additionally, throughout survey acquisition both commercial and recreational fishing activity was heavy causing deviations in the survey acquisition lines requiring numerous holiday reruns. The end result was that there were no significant impacts to the final sounding data.


</hsd:discussion>
                        <hsd:comments />
                    </hsd:issue>
                </hsd:results>
                <hsd:comments />
            </dr:factorsAffectingSoundings>
            <dr:soundSpeedMethods>
                <dr:castFrequency>On the R/V Sea Innovator I, the MVP30 was the primary system used to collect sound speed profile (SSP) data, and on the R/V Oyster Bay II, the AML BaseX2 was the primary system used to collect SSP data, refer to the DAPR for additional details. SSP data were obtained at intervals frequent enough to meet depth accuracy requirements. </dr:castFrequency>
                <dr:discussion>All sound speed profiles applied for online bathymetry data collection were acquired within 500 meters of the bounds of the survey area as specified in Section 5.2.3.3 of the HSSD.

Confidence checks of the sound speed profile casts were routinely conducted by comparing at least two consecutive casts taken with different SSP sensors. 

All individual SSP files are delivered with the H13516 data and are broken out into sub-folders, which correspond to the purpose of each cast. Also, all individual SSP files for H13516 have been concatenated into two separate files based on the purpose of the cast, provided in CARIS format files (.svp), and delivered under (H13516/Processed/SVP/CARIS_SSP) on the delivery drive. In accordance with HSSD Section 8.3.6, SSP files were also converted to NCEI format, as detailed in the DAPR, and provided as a separate delivery to NCEI. Refer to the DAPR for additional details.
</dr:discussion>
                <dr:comments />
            </dr:soundSpeedMethods>
            <dr:coverageEquipmentAndMethods>
                <hsd:results deviation="true">
                    <hsd:discussion>All equipment and survey methods are detailed in the DAPR.</hsd:discussion>
                </hsd:results>
                <hsd:comments />
            </dr:coverageEquipmentAndMethods>
            <dr:additionalQualityControl>
                <hsd:issue>
                    <hsd:title>Multibeam Coverage Analysis</hsd:title>
                    <hsd:discussion>Leidos chose to achieve the coverage requirement using 200% SSS coverage with concurrent MBES or 100% MBES. To achieve this coverage, main scheme survey lines were spaced approximately 40-meters to ensure coverage was achieved. The SABER Gapchecker program was used to flag MBES data gaps within the CUBE surface. The entire surface was visually scanned for holidays at various points during the data processing effort. Additional survey lines were run to fill any holidays that were detected as defined for object detection coverage surveys in Section 5.2.2.2 of the HSSD and email correspondence dated 02-22-2023 (refer to Project Correspondence for additional details). Bathymetric data and side scan sonar imagery were reviewed and bathymetric splits were acquired if deemed necessary per Hydrographer’s discretion, as noted in Section 5.2.2.1 of the HSSD.

A final review of the CUBE Depth surface for H13516 showed that there were no holidays as defined for object detection coverage surveys in Section 5.2.2.2 of the HSSD or NOAA provided guidance (02/22/2023).

The final CUBE PFM grids were examined for the number of soundings contributing to the chosen CUBE hypotheses for each node by running SABER’s Frequency Distribution Tool on the Hypothesis Number of Soundings (Hyp. # Soundings) surface. The Hyp. # Soundings surface reports the number of soundings that were used to compute the chosen hypothesis. Analysis was conducted on the Hyp. # Soundings surface of the PFM grid to ensure that the requirements for Object Detection Coverage surveys (HSSD Section 5.2.2.2) were met. Within the final 50-centimeter CUBE PFM grid 99.29% of all nodes contained five or more soundings. 

As noted in Section A.4, the assigned survey bounds were achieved across H13516 except where the inshore limit of the NALL was reached or the shoreline bathymetry made it unsafe of equipment and crew to continue into shoaler depths.
</hsd:discussion>
                    <hsd:comments />
                </hsd:issue>
                <hsd:comments />
            </dr:additionalQualityControl>
        </dr:qualityControl>
        <dr:echoSoundingCorrections>
            <dr:corrections>
                <hsd:results deviation="false">
                    <hsd:discussion>All data reduction procedures conform to those detailed in the DAPR.</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>Side Scan Sonar (SSS) Coverage Analysis: For all details regarding SSS data processing, see the DAPR. Leidos chose to adhere to the coverage requirements in the PI as outlined in Section A.4. For H13516 the SSS range scale was set to 50-meters. Leidos generated two separate coverage mosaics at 1-meter cell size resolution as specified in Section 8.2.1 of the HSSD (See section B.2.9 for additional information). The first 100% and second 100% coverage mosaics were independently reviewed using tools in SABER to verify data quality and swath coverage. The SABER Gapchecker routine was used to flag data gaps within each of the 100% SSS coverage mosaics. Additionally, the entirety of each SSS surface was visually scanned for holidays at various points during the data processing effort. Additional survey lines were run to fill any holidays that were detected. All coverage mosaics are determined to be complete and sufficient to meet the requirements contained within the PI and HSSD. Each 100 percent coverage mosaic is delivered as a single georeferenced raster file (datum of NAD-83) in floating point GeoTIFF format, as specified in Sections 8.2.1 and 8.3.3 in the HSSD.

Multibeam Echo Sounder Seafloor Backscatter: For all details regarding MBES backscatter acquisition and processing see the DAPR. Leidos generated a MBES backscatter at 2-meter cell resolution per vessel; per HSSD. The MBES backscatter mosaics were reviewed for data quality and coverage. The MBES backscatter data acquired were written to the GSF in real-time by ISS-2000 and are delivered in the final GSF files for this sheet under the Processed/Sonar_Data/H13516_MB directory. All MBES backscatter mosaics are determined to be complete and sufficient to meet the requirements contained within the PI and HSSD. The coverage mosaics are delivered as a single georeferenced raster file (datum of NAD-83) in floating point GeoTIFF format, as specified in Section 6.2.4.2 in the HSSD.
</hsd:discussion>
            </hsd:results>
            <hsd:comments />
        </dr:backscatter>
        <dr:dataProcessing>
            <dr:drSoftware>
                <dr:bathySoftware>
                    <dr:manufacturer>Leidos</dr:manufacturer>
                    <dr:name>SABER</dr:name>
                    <dr:version>5.4.1.6.1</dr:version>
                </dr:bathySoftware>
                <dr:imagerySoftware>
                    <dr:manufacturer>Leidos</dr:manufacturer>
                    <dr:name>SABER</dr:name>
                    <dr:version>5.4.1.6.1</dr:version>
                </dr:imagerySoftware>
                <dr:imagerySoftware>
                    <dr:manufacturer>QPS</dr:manufacturer>
                    <dr:name>FMGT</dr:name>
                    <dr:version>7.10.3</dr:version>
                </dr:imagerySoftware>
                <dr:featureObjectCatalog>NOAA Profile Version 2022</dr:featureObjectCatalog>
                <dr:discussion>The primary data processing software used for both bathymetry and imagery was SABER.</dr:discussion>
                <dr:comments />
            </dr:drSoftware>
            <dr:surfaces>
                <dr:surface>
                    <hsd:surfaceName>H13685_MB_50cm_MLLW_Final</hsd:surfaceName>
                    <hsd:surfaceType>BAG</hsd:surfaceType>
                    <hsd:resolution units="meters">0.5</hsd:resolution>
                    <hsd:depthRange>
                        <hsd:min units="meters">1.558</hsd:min>
                        <hsd:max units="meters">19.664</hsd:max>
                    </hsd:depthRange>
                    <hsd:surfaceParameter>N/A</hsd:surfaceParameter>
                    <hsd:purpose>Object Detection</hsd:purpose>
                </dr:surface>
                <dr:surface>
                    <hsd:surfaceName>H13516_SSSAB_1m_400kHz_900kHz_1of2</hsd:surfaceName>
                    <hsd:surfaceType>SSS Mosaic</hsd:surfaceType>
                    <hsd:resolution units="meters">1</hsd:resolution>
                    <hsd:depthRange>
                        <hsd:min xsi:nil="true" />
                        <hsd:max xsi:nil="true" />
                    </hsd:depthRange>
                    <hsd:surfaceParameter>N/A</hsd:surfaceParameter>
                    <hsd:purpose>100% SSS</hsd:purpose>
                </dr:surface>
                <dr:surface>
                    <hsd:surfaceName>H13516_SSSAB_1m_400kHz_900kHz_2of2</hsd:surfaceName>
                    <hsd:surfaceType>SSS Mosaic</hsd:surfaceType>
                    <hsd:resolution units="meters">1</hsd:resolution>
                    <hsd:depthRange>
                        <hsd:min xsi:nil="true" />
                        <hsd:max xsi:nil="true" />
                    </hsd:depthRange>
                    <hsd:surfaceParameter>N/A</hsd:surfaceParameter>
                    <hsd:purpose>200% SSS</hsd:purpose>
                </dr:surface>
                <dr:surface>
                    <hsd:surfaceName>H13516_MBAB_2m_SeaInnovatorI_400kHz_1of2</hsd:surfaceName>
                    <hsd:surfaceType>MB Backscatter Mosaic</hsd:surfaceType>
                    <hsd:resolution units="meters">2</hsd:resolution>
                    <hsd:depthRange>
                        <hsd:min xsi:nil="true" />
                        <hsd:max xsi:nil="true" />
                    </hsd:depthRange>
                    <hsd:surfaceParameter>N/A</hsd:surfaceParameter>
                    <hsd:purpose>Multibeam Backscatter Coverage</hsd:purpose>
                </dr:surface>
                <dr:surface>
                    <hsd:surfaceName>H13516_MBAB_2m_OysterBayII_300kHz_2of2</hsd:surfaceName>
                    <hsd:surfaceType>MB Backscatter Mosaic</hsd:surfaceType>
                    <hsd:resolution units="meters">2</hsd:resolution>
                    <hsd:depthRange>
                        <hsd:min xsi:nil="true" />
                        <hsd:max xsi:nil="true" />
                    </hsd:depthRange>
                    <hsd:surfaceParameter>N/A</hsd:surfaceParameter>
                    <hsd:purpose>Multibeam Backscatter Coverage</hsd:purpose>
                </dr:surface>
                <dr:discussion>Object Detection Coverage Section 5.2.2.2 of the HSSD requires 50-centimeter node resolution for depths ranging from zero meters to 20 meters. Leidos generated a CUBE PFM grid for H13516 at 50-centimeter resolution. A small number of CUBE nodes exceeded the 20 meter depth limit; Leidos confirmed that in these areas the requirements for coverage were met at 50-centimeter resolution. 

The final gridded bathymetry data are delivered in Bathymetric Attributed Grid (BAG) format. The BAG files were exported from the CUBE PFM grid as detailed in the DAPR.
</dr:discussion>
                <dr:comments />
            </dr:surfaces>
            <dr:additionalDataProcessing>
                <hsd:comments />
            </dr:additionalDataProcessing>
        </dr:dataProcessing>
    </dr:dataAcquisitionAndProcessing>
    <dr:verticalAndHorizontalControl>
        <dr:discussion>In accordance with HSSD Section 2.2, the horizontal datum for this project is NAD83. HSSD Section 2.2 states that the “only exception for the NAD83 datum requirement is that the S-57 Final Feature File (Section 7.3) will be in the WGS84 datum to comply with international S-57 specifications”. As discussed in the DAPR Section C.7, for every feature flag in a MBES GSF file, SABER converts the position from the NAD83 datum to the WGS84 datum to generate the S-57 file and comply with HSSD and IHO requirements. Feature positions meet the precision stated in HSSD Section 7.4 for each respective datum. Depending on geographic reference there may be approximately a 1-meter difference comparing positions between NAD83 and WGS84 datums. Therefore, if the feature overrides from the BAG surface (NAD83) are compared to the Final Feature File S-57 positions (WGS84) it is anticipated that there could be positional differences exceeding those listed in Section 7.4 of the HSSD. Additional information discussing the vertical and horizontal control for this survey can be found in the DAPR.
</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 VDATUM</hsd:methodsUsed>
                <hsd:ellipsoidToChartDatumSepFile>
                    <hsd:fileName>OPR-E347-KR-22 _NAD83_VDatum_MLLW.cov</hsd:fileName>
                </hsd:ellipsoidToChartDatumSepFile>
                <hsd:discussion>Refer to the DAPR for details regarding the application of VDatum to the MBES data files. No final tide note was provided nor was it required from NOAA Center for Operational Oceanographic Products and Services (CO-OPS). 
</hsd:discussion>
                <hsd:comments />
            </hsd:VDATUM_or_constantSep>
            <hsd:comments />
        </dr:verticalControl>
        <dr:horizontalControl>
            <hsd:horizontalDatum>North American Datum 1983 (2011)</hsd:horizontalDatum>
            <hsd:projection>Projected UTM 18</hsd:projection>
            <hsd:PPK xsi:nil="true" used="false" />
            <hsd:PPP used="true">
                <hsd:discussion>The vessel kinematic data (POS/MV files) were post-processed in Applanix POSPac software using the Applanix PP-RTX solution to generate the Smoothed Best Estimate of Trajectory (SBET) solutions which were applied through SABER to the multibeam data. Refer to the DAPR for additional information and for details regarding all antenna and transducer offsets. Any soundings with total horizontal uncertainties exceeding the maximum allowable IHO S-44 6th Edition Order 1a specifications were flagged as invalid and therefore were not used in the CUBE depth calculations.</hsd:discussion>
                <hsd:comments />
            </hsd:PPP>
            <hsd:RTK xsi:nil="true" used="false" />
            <hsd:DGPS xsi:nil="true" used="false" />
            <hsd:WAAS xsi:nil="true" used="false" />
            <hsd:comments />
        </dr:horizontalControl>
        <dr:additionalIssues>
            <hsd:comments />
        </dr:additionalIssues>
    </dr:verticalAndHorizontalControl>
    <dr:resultsAndRecommendations>
        <dr:chartComparison>
            <dr:methods>
                <hsd:topic>
                    <hsd:discussion>Chart comparisons were conducted using a combination of SABER and CARIS’ HIPS and SIPS. H13516 data met data accuracy standards and bottom coverage requirements. Leidos recommends updating the common areas of all charts using data from this survey. Review showed that the H13516 CUBE data generally agreed well with charted depths compared to the ENCs listed in Section D.1.1. Charting recommendations for new features and updates to charted features, are documented in the H13516 S-57 FFF. Additional charted objects are discussed in later sections.

United States Coast Guard (USCG) District 5 LNM publications were reviewed for changes subsequent to the date of the PI and before the end of survey. The LNM reviewed were from week 35/22 (30 August 2022) until week 24/23 (13 June 2023).
</hsd:discussion>
                </hsd:topic>
                <hsd:comments />
            </dr:methods>
            <dr:charts>
                <hsd:ENC>
                    <hsd:name>US5MD12M</hsd:name>
                    <hsd:scale>40000</hsd:scale>
                    <hsd:edition>50</hsd:edition>
                    <hsd:updateApplicationDate>2021-11-24</hsd:updateApplicationDate>
                    <hsd:issueDate>2023-06-27</hsd:issueDate>
                </hsd:ENC>
                <hsd:ENC>
                    <hsd:name>US5MD22M</hsd:name>
                    <hsd:scale>25000</hsd:scale>
                    <hsd:edition>15</hsd:edition>
                    <hsd:updateApplicationDate>2023-06-20</hsd:updateApplicationDate>
                    <hsd:issueDate>2022-01-07</hsd:issueDate>
                </hsd:ENC>
                <hsd:comments />
            </dr:charts>
            <dr:shoalAndHazardousFeatures>
                <hsd:results investigated="Investigated">
                    <hsd:discussion>Refer to Section D.1.4 for significant shoals or hazardous features within the area covered by this survey. Leidos submitted the following DTON reports to the Atlantic Hydrographic Branch (AHB) in S-57 format per HSSD:
-H13516_DTON_01.000, submitted to AHB 2022-11-03, NDB registration DD-37292
-H13516_DTON_02_07.000, submitted to AHB 2023-08-01, not forwarded by AHB at time of delivery</hsd:discussion>
                </hsd:results>
                <hsd:comments />
            </dr:shoalAndHazardousFeatures>
            <dr:chartedFeatures>
                <hsd:results investigated="Investigated">
                    <hsd:discussion>There were numerous assigned charted features in the final CSF (CSF.000) within the SOW of H13516. Per HSSD Section 8.1.4, these charted features are not addressed in this section, refer to the H13516 S-57 FFF (H13516_FFF.000) for all the details and recommendations regarding these features.
</hsd:discussion>
                </hsd:results>
                <hsd:comments />
            </dr:chartedFeatures>
            <dr:unchartedFeatures>
                <hsd:results investigated="Investigated">
                    <hsd:discussion>See the H13516 S-57 FFF for all the details and recommendations regarding new uncharted features investigated. During the course of H13516 survey operations, fishing gear and temporary floats were observed throughout the survey area. When a temporary fishing surface float was identified and correlated to objects in the MBES data, as these data were not true seafloor the MBES data were invalidated to no longer contributed to a CUBE surface. In many cases, where it was not possible to confirm the fishing gear were not derelict or tied to a surface float, the object was retained in the MBES data. 

</hsd:discussion>
                </hsd:results>
                <hsd:comments />
            </dr:unchartedFeatures>
            <dr:channels>
                <hsd:results investigated="Investigated">
                    <hsd:discussion>There were three channels coincident to H13516: Craighill Channel, Swan Point Channel, and Tolchester Channel. There were no discrepancies within the assigned dredge areas for these channels.
</hsd:discussion>
                </hsd:results>
                <hsd:comments />
            </dr:channels>
        </dr:chartComparison>
        <dr:additionalResults>
            <dr:ATONS>
                <hsd:results investigated="Investigated">
                    <hsd:discussion>While there were no assigned Aids to Navigation (ATON) within the SOW of H13516 from the final CSF; there were numerous USCG and privately maintained fixed and floating ATONs within H13516. Per HSSD Section 7.3.6 and the CSF, ATONs found on-station are not provided within the FFF. Associated contacts are provided within the SSS Contacts S-57.
</hsd:discussion>
                </hsd:results>
                <hsd:comments />
            </dr:ATONS>
            <dr:maritimeBoundary>
                <hsd:results investigated="None Exist">
                    <hsd:discussion>No Maritime Boundary Points were assigned for this survey.</hsd:discussion>
                </hsd:results>
                <hsd:comments />
            </dr:maritimeBoundary>
            <dr:bottomSamples>
                <hsd:results investigated="Investigated">
                    <hsd:discussion>In accordance with both the PI  and Section 7.2.3 of the HSSD, bottom characteristics were obtained for H13516. Bottom characteristics were acquired at the assigned in the final PRF (PRF.000). Leidos did not modify the bottom sample locations from the location proposed by NOAA in the PRF. Bottom characteristics are included in the S-57 FFF. In addition, images of the sediment obtained for each bottom sample are referenced in the S-57 FFF and are included on the delivery drive under the folder H13516/Processed/Multimedia.

</hsd:discussion>
                </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="Investigated">
                    <hsd:discussion>Refer to H13516 FFF for additional details regarding submarine features.
</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="Investigated">
                    <hsd:discussion>Bottom features within Craighill Channel, the slope of the channel was found to have migrated over the course of the survey. The changes in bottom topography created artifacts in the CUBE depth solution. Therefore; to reduce the artifact when there was sufficient data in a newer MBES pass the previous MBES data were invalidated. Smaller artifacts may be present where the two data passes meet. No other abnormal seafloor or environmental conditions, as defined in Section 8.1.4 of the HSSD, exist within this survey area other than those discussed in Section B.2.5 and D.1.2.

</hsd:discussion>
                </hsd:results>
                <hsd:comments />
            </dr:abnormalSeafloorEnviroCond>
            <dr:constructionOrDredging>
                <hsd:results investigated="None Exist">
                    <hsd:discussion>No construction or dredging was observed during H13516 data acquisition. Artifacts from having conducted drege operations to free the Ever Forward container ship ran around Craighill Channel were present in the H13516 data.
</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>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 Hydrographic Survey Specifications and Deliverables, 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. Previously, or previously, submitted deliverables for OPR-E347-KR-22 are provided in the table below.
</dr:adequacyOfSurvey>
            <dr:additionalInfo xsi:nil="true" />
        </dr:statements>
        <dr:signingPersonnel>
            <hsd:approverName>Bridget W. Bernier</hsd:approverName>
            <hsd:approverTitle>Data Processing Manager</hsd:approverTitle>
            <hsd:approvalDate>2023-08-01</hsd:approvalDate>
        </dr:signingPersonnel>
        <dr:additionalReports>
            <hsd:reportName>OPR-E347-KR-22 Final Project Summary Report.pdf</hsd:reportName>
            <hsd:reportDateSent>2023-05-31</hsd:reportDateSent>
        </dr:additionalReports>
        <dr:additionalReports>
            <hsd:reportName>OPR-E347-KR-22_ Marine_Species_Awareness_Training_Record.pdf</hsd:reportName>
            <hsd:reportDateSent>2023-06-21</hsd:reportDateSent>
        </dr:additionalReports>
        <dr:additionalReports>
            <hsd:reportName>OPR-E347-KR-22_Coast Pilot Review Report.pdf </hsd:reportName>
            <hsd:reportDateSent>2023-06-22</hsd:reportDateSent>
        </dr:additionalReports>
        <dr:additionalReports>
            <hsd:reportName>OPR-E347-KR-22_DAPR.pdf</hsd:reportName>
            <hsd:reportDateSent>2023-07-17</hsd:reportDateSent>
        </dr:additionalReports>
        <dr:additionalReports>
            <hsd:reportName>H13511_DR.pdf</hsd:reportName>
            <hsd:reportDateSent>2023-07-17</hsd:reportDateSent>
        </dr:additionalReports>
        <dr:additionalReports>
            <hsd:reportName>H13515_DR.pdf</hsd:reportName>
            <hsd:reportDateSent>2023-07-18</hsd:reportDateSent>
        </dr:additionalReports>
        <dr:additionalReports>
            <hsd:reportName>OPR-E347-KR-22_20230719.zip (NCEI Sound Speed Data)</hsd:reportName>
            <hsd:reportDateSent>2023-07-19</hsd:reportDateSent>
        </dr:additionalReports>
        <dr:additionalReports>
            <hsd:reportName>H13514_DR.pdf</hsd:reportName>
            <hsd:reportDateSent>2023-07-19</hsd:reportDateSent>
        </dr:additionalReports>
        <dr:additionalReports>
            <hsd:reportName>H13517_DR.pdf</hsd:reportName>
            <hsd:reportDateSent>2023-07-20</hsd:reportDateSent>
        </dr:additionalReports>
        <dr:additionalReports>
            <hsd:reportName>H13684_DR.pdf</hsd:reportName>
            <hsd:reportDateSent>2023-07-20</hsd:reportDateSent>
        </dr:additionalReports>
        <dr:additionalReports>
            <hsd:reportName>H13685_DR.pdf</hsd:reportName>
            <hsd:reportDateSent>2023-07-21</hsd:reportDateSent>
        </dr:additionalReports>
        <dr:additionalReports>
            <hsd:reportName>H13512_DR.pdf</hsd:reportName>
            <hsd:reportDateSent>2023-07-28</hsd:reportDateSent>
        </dr:additionalReports>
        <dr:additionalReports>
            <hsd:reportName>H13513_DR.pdf</hsd:reportName>
            <hsd:reportDateSent>2023-08-01</hsd:reportDateSent>
        </dr:additionalReports>
    </dr:approvalSheet>
</dr:descriptiveReport>