<?xml version="1.0" encoding="UTF-8"?><ns1:descriptiveReport xmlns:ns1="http://svn.pydro.noaa.gov/2019/01/DescriptiveReport" xmlns:ns2="http://svn.pydro.noaa.gov/2019/01/AllGlobalTypes" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://svn.pydro.noaa.gov/2019/01/DescriptiveReport http://svn.pydro.noaa.gov/2019/01/DR.xsd"><ns1:areaSurveyed><ns1:coverageGraphic><ns2:coverageGraphicImage><ns2:images><ns2:link>SupportFiles\H13295_Figure_02.jpg</ns2:link><ns2:caption>Final Bathymetry Coverage for H13295</ns2:caption></ns2:images><ns2:images><ns2:link>SupportFiles\H13295_Figure_03.jpg</ns2:link><ns2:caption>Final Side Scan Coverage for H13295 (First 100% coverage)</ns2:caption></ns2:images><ns2:images><ns2:link>SupportFiles\H13295_Figure_04.jpg</ns2:link><ns2:caption>Final Side Scan Coverage for H13295 (Second 100% coverage)</ns2:caption></ns2:images></ns2:coverageGraphicImage></ns1:coverageGraphic><ns1:surveyCoverage><ns2:results deviation="false"><ns2:discussion>Leidos chose to achieve the coverage requirement using Object Detection Coverage, Option B (200% side scan sonar coverage with concurrent multibeam). Survey coverage achieved was in accordance with the requirements in the Project Instructions and the HSSD (Figure 2 through Figure 4).</ns2:discussion></ns2:results><ns2:comments/><ns2:coverageRequirement><ns2:requiredCoverage>Object Detection Coverage (Refer to HSSD Section 5.2.2.2)</ns2:requiredCoverage><ns2:waterDepth>H13295</ns2:waterDepth></ns2:coverageRequirement><ns2:coverageRequirement><ns2:requiredCoverage>Sidescan may be acquired at an altitude of 6-20% of the range scale</ns2:requiredCoverage><ns2:waterDepth>8 meters water depth and shoaler</ns2:waterDepth></ns2:coverageRequirement><ns2:coverageRequirement><ns2:requiredCoverage>Complete 5,553 LNM. 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 Project Manager/COR 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.</ns2:requiredCoverage><ns2:waterDepth>All waters in survey area</ns2:waterDepth></ns2:coverageRequirement></ns1:surveyCoverage><ns1:surveyQuality><ns2:adequacy>The entire survey is adequate to supersede previous data.</ns2:adequacy><ns2:comments/><ns2:discussion>Leidos warrants only that the survey data acquired by Leidos and delivered to NOAA under Contract EA-133C-14-CQ-0033 reflects the state of the sea floor in existence on the day and at the time the survey was conducted.

H13295 was surveyed in accordance with the following documents:
1.	Project Instructions, OPR-E350-KR-19, dated 27 August 2019
2.	Hydrographic Surveys Specifications and Deliverables (HSSD), March 2019
3.	OPR-E350-KR-19 Statement of Work, dated 28 August 2019
4.	Final_OPR-E350-KR-19_PRF.000, received 18 September 2019
5.	Final_OPR-E350-KR-19_CSF.000, received 18 September 2019
6.	OPR-E350-KR-19_Southern_Chesapeake_Bay_Questions.pdf, dated 05 November 2019
7.	OPR-E350-KR-19: H13295 Grid Resolution Waiver, dated 05 March 2020
8.	OPR-E350-KR-19_VERBAL AUTHORIZATION_ Southern OPR-E350-KR-19_Chesapeake Bay No-cost Extension - EA133C14CQ0033 1305M219FNCNJ0356, dated 08 May 2020</ns2:discussion></ns1:surveyQuality><ns1:surveyPurpose><ns2:comments/><ns2:discussion>The purpose of this survey is to provide contemporary surveys to update National Ocean Service (NOS) nautical charting products. This project is located in the Chesapeake Bay in Virginia. The Chesapeake Bay is the largest of 130 estuaries in the United States. The Coast Guard is currently conducting a Waterways Assessment and Management Survey of the lower James River. This data will be used to assess if ATONs are correctly placed and help inform a comprehensive report regarding the location of shoals within the lower James River. Survey vintage in this area dates back to 1945. This project will provide critical data for the updating of National Ocean Service (NOS) nautical charting products to increase maritime safety in the region. Survey data from this project is intended to supersede all prior survey data in the common area.</ns2:discussion></ns1:surveyPurpose><ns1:surveyLimits><ns2:results deviation="false"><ns2:discussion>Survey limits were acquired in accordance with the requirements in the Project Instructions and the Hydrographic Surveys Specifications and Deliverables (HSSD), March 2019.</ns2:discussion></ns2:results><ns2:comments/></ns1:surveyLimits><ns1:surveyStatistics><ns2:discussion xsi:nil="true"></ns2:discussion><ns2:LNM><ns2:vesselLNM><ns2:vessel><ns2:hullID>M/V Atlantic Surveyor</ns2:hullID><ns2:statistics><ns2:XL_lidar>0.0</ns2:XL_lidar><ns2:MS_MBES_SSS>1630.32</ns2:MS_MBES_SSS><ns2:MS_lidar>0.0</ns2:MS_lidar><ns2:MS_MBES>0.0</ns2:MS_MBES><ns2:XL_MBES_SBES>67.4</ns2:XL_MBES_SBES><ns2:MS_SBES>0.0</ns2:MS_SBES><ns2:MS_SBES_MBES>0.0</ns2:MS_SBES_MBES><ns2:MS_SBES_SSS>0.0</ns2:MS_SBES_SSS><ns2:MS_SSS>0.0</ns2:MS_SSS></ns2:statistics></ns2:vessel></ns2:vesselLNM><ns2:totalLNM><ns2:MS_SBES_SSS>0.0</ns2:MS_SBES_SSS><ns2:MS_MBES_SSS>1630.32</ns2:MS_MBES_SSS><ns2:MS_lidar>0.0</ns2:MS_lidar><ns2:MS_MBES>0.0</ns2:MS_MBES><ns2:percentXLLNM>4.13</ns2:percentXLLNM><ns2:XL_MBES_SBES>67.4</ns2:XL_MBES_SBES><ns2:MS_SBES>0.0</ns2:MS_SBES><ns2:MS_SBES_MBES>0.0</ns2:MS_SBES_MBES><ns2:XL_lidar>0.0</ns2:XL_lidar><ns2:MS_SSS>0.0</ns2:MS_SSS></ns2:totalLNM></ns2:LNM><ns2:totalSurveyStats><ns2:bottomSamples>9</ns2:bottomSamples><ns2:maritimeBoundaryPoints>0</ns2:maritimeBoundaryPoints><ns2:DP>0</ns2:DP><ns2:SNM>33.44</ns2:SNM><ns2:diveOps>0</ns2:diveOps></ns2:totalSurveyStats><ns2:comments/><ns2:surveyDates>2019-10-26</ns2:surveyDates><ns2:surveyDates>2019-10-27</ns2:surveyDates><ns2:surveyDates>2019-10-28</ns2:surveyDates><ns2:surveyDates>2019-10-29</ns2:surveyDates><ns2:surveyDates>2019-10-30</ns2:surveyDates><ns2:surveyDates>2019-10-31</ns2:surveyDates><ns2:surveyDates>2019-11-01</ns2:surveyDates><ns2:surveyDates>2019-11-02</ns2:surveyDates><ns2:surveyDates>2019-11-03</ns2:surveyDates><ns2:surveyDates>2019-11-04</ns2:surveyDates><ns2:surveyDates>2019-11-05</ns2:surveyDates><ns2:surveyDates>2019-11-06</ns2:surveyDates><ns2:surveyDates>2019-11-07</ns2:surveyDates><ns2:surveyDates>2019-11-08</ns2:surveyDates><ns2:surveyDates>2019-11-09</ns2:surveyDates><ns2:surveyDates>2019-11-10</ns2:surveyDates><ns2:surveyDates>2019-11-11</ns2:surveyDates><ns2:surveyDates>2019-11-13</ns2:surveyDates><ns2:surveyDates>2019-12-10</ns2:surveyDates><ns2:surveyDates>2019-12-11</ns2:surveyDates><ns2:surveyDates>2019-12-12</ns2:surveyDates><ns2:surveyDates>2020-06-25</ns2:surveyDates><ns2:surveyDates>2020-06-26</ns2:surveyDates></ns1:surveyStatistics><ns1:areaDescription><ns2:limits><ns2:northWest><ns2:latitude hemisphere="N">37.301824</ns2:latitude><ns2:longitude hemisphere="W">76.1449</ns2:longitude></ns2:northWest><ns2:southEast><ns2:latitude hemisphere="N">37.094326</ns2:latitude><ns2:longitude hemisphere="W">76.031198</ns2:longitude></ns2:southEast></ns2:limits><ns2:comments/><ns2:images><ns2:link>SupportFiles\H13295_Figure_01.jpg</ns2:link><ns2:caption>H13295 Survey Bounds</ns2:caption></ns2:images><ns2:discussion>The area surveyed was a section of the Southern Chesapeake Bay west of Old Plantation Flats (Figure 1).</ns2:discussion></ns1:areaDescription></ns1:areaSurveyed><ns1:resultsAndRecommendations><ns1:chartComparison><ns1:chartedFeatures><ns2:results investigated="Investigated"><ns2:discussion>There were six assigned charted features in the final CSF (Final_OPR-E350-KR-19_CSF.000) within the SOW of H13295; however none of these features contained the label PA, ED, PD, or Rep. Per HSSD Section 8.1.4, these charted features are not addressed in this section, refer to the H13295 S-57 FFF (H13295_FFF.000) for all the details and recommendations regarding these features.</ns2:discussion></ns2:results><ns2:comments/></ns1:chartedFeatures><ns1:charts><ns2:comments/><ns2:ENC><ns2:images><ns2:link>SupportFiles\H13295_Figure_08.jpg</ns2:link><ns2:caption>ENC US5VA13M Charted Soundings (black) with H13295 CUBE Depth Selected Soundings (blue)</ns2:caption></ns2:images><ns2:images><ns2:link>SupportFiles\H13295_Figure_09.jpg</ns2:link><ns2:caption>ENC US5VA13M with Charted Contour (red) with H13295 CUBE Depth Selected Soundings (blue)</ns2:caption></ns2:images><ns2:chart><ns2:name>US5VA13M</ns2:name><ns2:edition>41</ns2:edition><ns2:preliminary>false</ns2:preliminary><ns2:scale>40000</ns2:scale><ns2:issueDate>2020-06-23</ns2:issueDate><ns2:updateApplicationDate>2019-10-24</ns2:updateApplicationDate></ns2:chart><ns2:comments/><ns2:discussion>ENC US5VA13M covers the H13295 survey limit from 37° 08’ 30.60”N southward.

CUBE depths within H13295 agreed well with the charted depths across the contemporaneous survey area; observed depths were primarily within ±0.7 meters of charted depths (Figure 8). The depth contours on ENC US5VA13M generally agreed with depths that fell within the H13295 survey area (Figure 9).</ns2:discussion></ns2:ENC><ns2:ENC><ns2:images><ns2:link>SupportFiles\H13295_Figure_10.jpg</ns2:link><ns2:caption>ENC US5VA14M Charted Soundings (black) with H13295 CUBE Depth Selected Soundings (blue)</ns2:caption></ns2:images><ns2:images><ns2:link>SupportFiles\H13295_Figure_11.jpg</ns2:link><ns2:caption>ENC US5VA14M Charted Soundings (black) with H13295 CUBE Depth Selected Soundings (blue)</ns2:caption></ns2:images><ns2:images><ns2:link>SupportFiles\H13295_Figure_12.jpg</ns2:link><ns2:caption>ENC US5VA14M Charted Contour (red) with H13295 CUBE Depth Selected Soundings (blue)</ns2:caption></ns2:images><ns2:images><ns2:link>SupportFiles\H13295_Figure_13.jpg</ns2:link><ns2:caption>ENC US5VA14M with H13295 Survey Area and Anchorage R (magenta)</ns2:caption></ns2:images><ns2:chart><ns2:name>US5VA14M</ns2:name><ns2:edition>33</ns2:edition><ns2:preliminary>false</ns2:preliminary><ns2:scale>40000</ns2:scale><ns2:issueDate>2020-06-23</ns2:issueDate><ns2:updateApplicationDate>2019-06-12</ns2:updateApplicationDate></ns2:chart><ns2:comments/><ns2:discussion>ENC US5VA14M covers the H13295 survey limit from 37° 08’ 30.60”N northward.

CUBE depths within H13295 agreed well with the charted depths across the contemporaneous survey area; observed depths were primarily within ±0.7 meters of charted depths (Figure 10).There was greater variability along the eastern extent of H13295 with observed depths deeper than charted depths (Figure 11). The depth contours on ENC US5VA14M generally agreed with depths that fell within the H13295 survey area (Figure 12). 

LNM 26/20 notes that on June 29, 2020, the Coast Guard established a new Quarantine Anchorage R. Anchorage area R is contained within ENC US5VA14M and is coincident to the H13295 survey area along the western extent (Figure 13). This has been updated on the latest US5VA14M ENC.</ns2:discussion></ns2:ENC></ns1:charts><ns1:bottomSamples><ns2:results investigated="Investigated"><ns2:discussion>In accordance with both the Project Instructions and Section 7.2.3 of the HSSD, bottom characteristics were obtained for H13295. Bottom characteristics were acquired at the nine locations assigned in the final PRF (Final_OPR-E350-KR-19_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 H13295/Processed/Multimedia.</ns2:discussion></ns2:results><ns2:comments/></ns1:bottomSamples><ns1:maritimeBoundary><ns2:results investigated="None Exist"><ns2:discussion>No Maritime Boundary Points were assigned for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:maritimeBoundary><ns1:methods><ns2:comments/><ns2:discussion>The chart comparisons were conducted using a combination of SABER and CARIS’ HIPS and SIPS.

United States Coast Guard (USCG) District 5 Local Notice to Mariners (LNM) publications were reviewed for changes subsequent to the date of the Project Instructions and before the end of survey (as specified in Section 8.1.4 of the HSSD). The LNM reviewed were from week 42/19 (15 October 2019) until week 28/20 (14 July 2020).

H13295 data met data accuracy standards and bottom coverage requirements. Leidos recommends updating the common areas of all charts using data from this survey. Charting recommendations for new features, and updates to charted features, are documented in the H13295 S-57 FFF. Additional charted objects are discussed in later sections.</ns2:discussion></ns1:methods><ns1:channels><ns2:results investigated="Investigated"><ns2:discussion>There were no assigned channels within the H13295 SOW from the final CSF. However, as the survey limit acquired by Leidos extended beyond the assigned SOW; there is some data within H13295 coincident to the York Spit Channel. Survey depths did not exceed the controlling depths. Within the final CSF was an assigned anchorage area, Quarantine Anchorage Area Q, which was covered in its entirety by H13295. No significant features were identified within the anchorage area. This anchorage area has been expanded and is captured on ENC US5VA14M on 29 June 2020 (LNM 26/20) and renamed to be Quarantine Anchorage Area R see Section D.1.1. Per the investigation requirements from the CSF for the York Spit Channel and anchorage area these features are not included in the H13295 FFF.</ns2:discussion></ns2:results><ns2:comments/></ns1:channels><ns1:shoalAndHazardousFeatures><ns2:results investigated="Investigated"><ns2:images><ns2:link>SupportFiles\H13295_Figure_14.jpg</ns2:link><ns2:caption>DTON Reports</ns2:caption></ns2:images><ns2:discussion>There were no significant shoals or hazardous features within the area covered by this survey other than those referenced in Section D.1.4.

Leidos submitted one DTON for H13295. The DTON was submitted in S-57 format to the Atlantic Hydrographic Branch (AHB).

•	DTON 01 was submitted on 04 November 2019, per HSSD Section 1.6.1 the observed wreck was submitted as an obstruction. This DTON was submitted to Nautical Data Brach (NDB) and Marine Chart Division (MCD) on 05 November 2019.
•	DTON 02 was submitted to the US Coast Guard on 22 July 2020, for a missing buoy. The submission was made to the non-NOAA source authorities in accordance with HSSD Section 1.6.2. The buoy was not present, refer to the H13295 S-57 FFF.
 
Copies of the email correspondence for Leidos’ submissions of H13295 DTON Report, as well as the DTON recommendation file, are included within Appendix II of this Descriptive Report. Figure 14 details the submitted DTON and the associated Feature number and object class in the S-57 FFF.</ns2:discussion></ns2:results><ns2:comments/></ns1:shoalAndHazardousFeatures><ns1:unchartedFeatures><ns2:results investigated="Investigated"><ns2:discussion>See the H13295 S-57 FFF for all the details and recommendations regarding new uncharted features investigated.</ns2:discussion></ns2:results><ns2:comments/></ns1:unchartedFeatures></ns1:chartComparison><ns1:additionalResults><ns1:ATONS><ns2:results investigated="Investigated"><ns2:discussion>There were no assigned aids to navigation (ATON) within the SOW of H13295 from the final CSF. There were four charted unassigned ATONs which fell within survey limits of H13295; three within ENC US5VA13M and one within ENC US5VA14M. Three of these ATONs were observed on station and serving their intended purpose. Per the investigation requirements from the CSF, as they were on station and serving intended purpose, they are included in the H13295 FFF with description of retain (H13295 Feature 13, 14, and 15). There was one ATON that was not observed during H13295 data collection; therefore Leidos submitted an ATON Discrepancy Report (Appendix II) regarding the absence of Chesapeake Channel Calibration Buoy (ENC US5VA14M). See the H13295 S-57 FFF for all the details and recommendations regarding the ATONs.</ns2:discussion></ns2:results><ns2:comments/></ns1:ATONS><ns1:ferryRoutesAndTerminals><ns2:results investigated="None Exist"><ns2:discussion>No ferry routes or terminals exist within this survey area.</ns2:discussion></ns2:results><ns2:comments/></ns1:ferryRoutesAndTerminals><ns1:otherResults><ns2:comments/><ns2:issue><ns2:title>Designated Soundings</ns2:title><ns2:comments/><ns2:discussion>As discussed in the DAPR within Generic Sensor Format (GSF) there are separate flags for a designated sounding of a feature. During data analysis, these flags are used to preserve the shoalest sounding relative to the computed depth surface. All depths flagged as a feature or designated sounding in GSF override the CUBE best estimate of the depth in the final BAG files. GSF feature flags were set on significant features within H13295, and all information is contained in the H13295 S-57 FFF.</ns2:discussion></ns2:issue><ns2:issue><ns2:title>Final Feature S-57 File</ns2:title><ns2:comments/><ns2:discussion>Included with the H13295 delivery is the S-57 FFF, H13295_FFF.000. Details on how this file was generated and quality controlled can be found in the DAPR. The S-57 FFF delivered for H13295 contains millimeter precision for the value of sounding (VALSOU) attribute. As specified in Section 2.2 of the HSSD, the S-57 FFF is in the WGS84 datum and is unprojected with all depth units in meters. Per HSSD Section 2.2 bathymetry data were positioned to NAD83. All significant and recommended for charting features found in H13295 are included within the S-57 FFF.

In accordance with the HSSD, Leidos addressed all assigned objects from the provided CSF S-57 file that fell within the bounds of H13295 in the S-57 FFF.</ns2:discussion></ns2:issue><ns2:issue><ns2:title>Side Scan Sonar Contacts S-57 File</ns2:title><ns2:comments/><ns2:discussion>Included with the H13295 delivery is the Side Scan Sonar Contact S-57 File, H13295_SSCon.000. Details on how this file was generated and quality controlled can be found in the DAPR. As specified in Section 2.2 of the HSSD, the S-57 file is in the WGS84 datum and is unprojected with all depth units in meters. Per HSSD Section 2.2 side scan data were positioned to NAD83.

Side scan sonar contacts were investigated and confirmed using SABER Contact Review. All side scan contacts are retained within the Side Scan Sonar Contact S-57 File. For each contact included in this S-57 file, a JPEG image of the side scan contact is included under the NOAA Extended Attribute field “images”.</ns2:discussion></ns2:issue><ns2:issue><ns2:title>Coast Pilot Review Report</ns2:title><ns2:comments/><ns2:discussion>In accordance with the Project Instructions and HSSD Section 8.1.3, a Coast Pilot Review was performed for OPR-E350-KR-19. Within the Coast Pilot Field Report (OPR-E350-KR-19CoastPilotReport.docx) provided by NOAA to Leidos on 28 October 2019, there were assigned investigation items and inquiries from the Nautical Publications Branch. During survey, Leidos reviewed and updated the assigned and additional Coast Pilot paragraphs as possible for the survey area, port of call, and areas frequently transited. Recommendations were documented using the text from the 53rd Edition (19 July 2020) and are marked following the HSSD Section 8.1.3. Leidos followed NOAA’s strategy for designating omitted paragraphs as provided in the delivered Coast Pilot Field Report (OPR-E350-KR-19CoastPilotReport.docx). Leidos submitted the Coast Pilot Field Report on 26 July 2020. The email correspondence for Leidos’ submission of the Coast Pilot Review Report is included within the Project Correspondence.</ns2:discussion></ns2:issue></ns1:otherResults><ns1:insetRecommendation><ns2:results recommended="false"><ns2:discussion>No inset recommendations are made for the area covered by this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:insetRecommendation><ns1:overheadFeatures><ns2:results investigated="None Exist"><ns2:discussion>There were no overhead features within this survey area.</ns2:discussion></ns2:results><ns2:comments/></ns1:overheadFeatures><ns1:newSurveyRecommendation><ns2:results recommended="false"><ns2:discussion>No new survey recommendations are made for the area surrounding this survey area.</ns2:discussion></ns2:results><ns2:comments/></ns1:newSurveyRecommendation><ns1:shoreline><ns2:results investigated="None Exist"><ns2:discussion>All features in the CSF within the assigned Survey Limits of H13295 were resolved. There were no assigned features inshore of the NALL.</ns2:discussion></ns2:results><ns2:comments/></ns1:shoreline><ns1:platforms><ns2:results investigated="None Exist"><ns2:discussion>No platforms exist within this survey area.</ns2:discussion></ns2:results><ns2:comments/></ns1:platforms><ns1:constructionOrDredging><ns2:results investigated="None Exist"><ns2:discussion>No construction or dredging exists for this survey area.</ns2:discussion></ns2:results><ns2:comments/></ns1:constructionOrDredging><ns1:abnormalSeafloorEnviroCond><ns2:results investigated="Investigated"><ns2:images><ns2:link>SupportFiles\H13295_Figure_15.jpg</ns2:link><ns2:caption>2019 (Red and Yellow Lines) vs. 2020 (Blue Lines) Bathymetry Data Causing Elevated Uncertainties (Shown in Red) Due to Migrating Sand Waves</ns2:caption></ns2:images><ns2:discussion>Sand waves were observed along the eastern extent of H13295. Bathymetric data acquired on different days indicated that these sand waves were shifting. While generally in the same area, the positional differences caused the CUBE calculated uncertainty (Hyp, Final Uncertainty) to be increase and in some areas exceed the allowable uncertainty. Figure 15 illustrates sand waves that had shifted during data acquisition. In the image, the bottom right show colors each line, the data from 30 October 2019 (JD 303 in red) and 02 November 2019 (JD 306 in yellow) in agreement while more recent data from 26 June 2020 (JD 178 in green and blue) also in agreement. </ns2:discussion></ns2:results><ns2:comments/></ns1:abnormalSeafloorEnviroCond><ns1:submarineFeatures><ns2:results investigated="Investigated"><ns2:discussion>Within the final CSF there was one assigned submarine cable with investigation requirements “Visually confirm feature object existence. If discrepancy, discuss in DR (see HSSD Section 8.1.4). Do not include feature in FFF”. The disused submarine cable was covered by 200% SSS with concurrent multibeam within the survey limits of H13295, no signature of a cable was observed within the area. This assigned submarine cable is not included in the H13295 FFF as there was no discrepancy from the CSF or ENC US5VA14M.</ns2:discussion></ns2:results><ns2:comments/></ns1:submarineFeatures></ns1:additionalResults></ns1:resultsAndRecommendations><ns1:approvalSheet><ns1:signingPersonnel><ns2:approverName>Bridget W. Bernier</ns2:approverName><ns2:approvalDate>2020-07-29</ns2:approvalDate><ns2:approverTitle>Data Processing Manager</ns2:approverTitle></ns1:signingPersonnel><ns1:statements><ns1:adequacyOfSurvey>The survey data meets or exceeds requirements as set forth in the Hydrographic Surveys 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 concurrently, submitted deliverables for OPR-E350-KR-19 are provided in the table below.</ns1:adequacyOfSurvey><ns1:approval>This Descriptive Report, all BAG files, and all accompanying records and data are approved. All records are forwarded for final review and processing to the Processing Branch.</ns1:approval><ns1:supervision>As Chief of Party, field operations for this hydrographic survey were conducted under my direct supervision, with frequent personal checks of progress and adequacy. I have reviewed the attached survey data and reports.</ns1:supervision><ns1:additionalInfo xsi:nil="true"></ns1:additionalInfo></ns1:statements><ns1:additionalReports><ns2:reportName>OPR-E350-KR-19_Marine_Species_Awareness_Training_Record.pdf </ns2:reportName><ns2:reportDateSent>2020-07-20</ns2:reportDateSent></ns1:additionalReports><ns1:additionalReports><ns2:reportName>OPR-E350-KR-19_20200724.zip (NCEI Sound Speed Data 2019 data only)</ns2:reportName><ns2:reportDateSent>2020-07-24</ns2:reportDateSent></ns1:additionalReports><ns1:additionalReports><ns2:reportName>OPR-E350-KR-19_Coast Pilot Review Report.pdf </ns2:reportName><ns2:reportDateSent>2020-07-26</ns2:reportDateSent></ns1:additionalReports><ns1:additionalReports><ns2:reportName>OPR-E350-KR-19_DAPR.pdf</ns2:reportName><ns2:reportDateSent>2020-07-29</ns2:reportDateSent></ns1:additionalReports></ns1:approvalSheet><ns1:verticalAndHorizontalControl><ns1:discussion>Additional information discussing the vertical and horizontal control for this survey can be found in the DAPR.</ns1:discussion><ns1:horizontalControl><ns2:PPK used="false" xsi:nil="true"/><ns2:projection>Projected UTM 18</ns2:projection><ns2:comments/><ns2:DGPS used="false" xsi:nil="true"/><ns2:RTK used="false" xsi:nil="true"/><ns2:WAAS used="false" xsi:nil="true"/><ns2:horizontalDatum>North American Datum 1983</ns2:horizontalDatum><ns2:PPP used="true"><ns2:comments/><ns2: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 5th Edition Order 1a specifications were flagged as invalid and therefore were not used in the CUBE depth calculations.</ns2:discussion></ns2:PPP></ns1:horizontalControl><ns1:additionalIssues><ns2:comments/></ns1:additionalIssues><ns1:verticalControl><ns2:tideStations/><ns2:standard_or_ERZT used="false" xsi:nil="true"/><ns2:VDATUM_or_constantSep used="true"><ns2:methodsUsed>ERS via VDATUM</ns2:methodsUsed><ns2:comments/><ns2:ellipsoidToChartDatumSepFile><ns2:fileName>OPR-E350-KR-19_NAD83_VDatum_MLLW.cov</ns2:fileName></ns2:ellipsoidToChartDatumSepFile><ns2:discussion>Refer to the DAPR for details regarding the application of VDatum to the MBES data files. No final tide note was provided from NOAA Center for Operational Oceanographic Products and Services (CO-OPS). While a final tide note was not required, a final tide note has been provided by Leidos in Appendix I.</ns2:discussion></ns2:VDATUM_or_constantSep><ns2:comments/><ns2:verticalDatum>Mean Lower Low Water</ns2:verticalDatum></ns1:verticalControl></ns1:verticalAndHorizontalControl><ns1:dataAcquisitionAndProcessing><ns1:equipmentAndVessels><ns1:discussion>Leidos used their ISS-2000 software on a Windows 7 platform to acquire these survey data. Survey planning and data analysis were conducted using the Leidos SABER software on Red Hat Enterprise 7 Linux platforms. Klein 3000 side scan sonar (SSS) data were collected on a Windows 7 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-E350-KR-19, delivered concurrently with this Descriptive Report (DR). There were no variations from the equipment configuration described in the DAPR.</ns1:discussion><ns1:equipment><ns1:discussion>A detailed description of the equipment installed is included in the DAPR.</ns1:discussion><ns1:majorSystem><ns2:manufacturer>Teledyne RESON</ns2:manufacturer><ns2:type>MBES</ns2:type><ns2:model>SeaBat T50-R</ns2:model></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>Klein Marine Systems</ns2:manufacturer><ns2:type>SSS</ns2:type><ns2:model>System 3000</ns2:model></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>Applanix</ns2:manufacturer><ns2:type>Positioning and Attitude System</ns2:type><ns2:model>POS MV 320 v5</ns2:model></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>AML Oceanographic</ns2:manufacturer><ns2:type>Sound Speed System</ns2:type><ns2:model>MVP30</ns2:model></ns1:majorSystem><ns1:comments/></ns1:equipment><ns1:vessels><ns1:discussion>The M/V Atlantic Surveyor (Figure 5) was used to collect multibeam echo sounder (MBES) (RESON SeaBat T50), side scan sonar (SSS) (Klein 3000), and sound speed data during twenty-four hours per day survey operations.

A detailed description of the vessel used is included in the DAPR.</ns1:discussion><ns1:vessel><ns2:hullID>M/V Atlantic Surveyor</ns2:hullID><ns2:LOA units="feet">110.0</ns2:LOA><ns2:draft units="feet">9.0</ns2:draft></ns1:vessel><ns1:comments/><ns1:images><ns2:link>SupportFiles\H13295_Figure_05.jpg</ns2:link><ns2:caption>M/V Atlantic Surveyor</ns2:caption></ns1:images></ns1:vessels><ns1:comments/></ns1:equipmentAndVessels><ns1:echoSoundingCorrections><ns1:calibrations><ns2:results deviation="false"><ns2:calibration xsi:nil="true"/><ns2:discussion>All sounding systems were calibrated as detailed in the DAPR. Multibeam files associated with calibration are provided within the H13295/Processed/Sonar_Data/H13295_MB/Calibration_Files/ directory.</ns2:discussion></ns2:results><ns2:comments/></ns1:calibrations><ns1:additionalIssues><ns2:comments/></ns1:additionalIssues><ns1:corrections><ns2:results deviation="false"><ns2:discussion>All data reduction procedures conform to those detailed in the DAPR.</ns2:discussion></ns2:results><ns2:comments/></ns1:corrections></ns1:echoSoundingCorrections><ns1:backscatter><ns2:results acquired="true"><ns2: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 Project Instructions using Object Detection Coverage, Option B (200% side scan sonar coverage with concurrent multibeam). As referenced in Section A.4, the Project Instructions provided a waiver to HSSD Section 6.1.2.3 for towed side scan towfish height. In waters less than 8 meters the towfish height above the bottom could be 6% of the range scale. Mosaics were analyzed for coverage at both 8% and 6% of range based on water depths greater or less than 8 meters.

Leidos generated two separate coverage mosaics at 1-meter cell size resolution as specified in Section 8.2.1 of the HSSD. 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. Both coverage mosaics are determined to be complete and sufficient to meet the requirements contained within the Project Instructions and HSSD. Each 100 percent coverage mosaic is delivered as a single georeferenced raster file (datum of NAD83) in floating point GeoTIFF format, as specified in Sections 8.2.1 and 8.3.3 in the HSSD.

Multibeam Echo Sounder Seafloor Backscatter: Leidos collected MBES backscatter data with all GSF data acquired, in accordance with HSSD Section 6.2. The MBES settings used were checked to ensure acceptable quality standards were met and to mitigate acoustic saturation of the backscatter data. 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. Evaluation of backscatter data and processing were not required for OPR-E350-KR-19 and therefore no additional processing was performed by Leidos and no additional products were produced. </ns2:discussion></ns2:results><ns2:comments/></ns1:backscatter><ns1:dataProcessing><ns1:additionalDataProcessing><ns2:comments/></ns1:additionalDataProcessing><ns1:drSoftware><ns1:discussion>The primary data processing software used for both bathymetry and imagery was SABER.</ns1:discussion><ns1:featureObjectCatalog>NOAA Profile Version 2019</ns1:featureObjectCatalog><ns1:comments/><ns1:imagerySoftware deviation="true"><ns1:name>SABER</ns1:name><ns1:manufacturer>Leidos</ns1:manufacturer><ns1:version>5.4.0.30.1</ns1:version></ns1:imagerySoftware><ns1:bathySoftware deviation="true"><ns1:name>SABER</ns1:name><ns1:manufacturer>Leidos</ns1:manufacturer><ns1:version>5.4.0.30.1</ns1:version></ns1:bathySoftware></ns1:drSoftware><ns1:surfaces><ns1: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, 1-meter node resolution for depths ranging from 18 meters to 40 meters, and 4-meter node resolution for depths ranging from 36 meters to 80 meters. As noted in Section B.2.2, Leidos was granted a grid resolution waiver per correspondence with NOAA (Appendix II); Leidos generated CUBE PFM grids for H13295 at 50-centimeter and 1-meter resolution and used these surfaces to assess and document multibeam survey coverage for their respective depth ranges. Included within the waiver was the ability to provide the bathymetric coverage with minimum and maximum depth ranges that fell outside of the depth limits defined within the HSSD.

SABER populates the CUBE depth with either the node’s chosen hypothesis or the depth of a feature or designated sounding set by the hydrographer, which overrides the chosen hypothesis. The range of CUBE depths of the H13295 50-centimeter and 1-meter PFM grids were from 4.098 meters (13.445 feet; 0.210 meters Total Vertical Uncertainty [TVU]) to 20.851 meters (68.409 feet; 0.210 meters TVU) and 16.623 meters (54.537 feet; 0.210 meters TVU) to 44.153 meters (144.859 feet; 0.239 meters TVU) respectively. 

The final gridded bathymetry data are delivered as a Bathymetric Attributed Grid (BAG). The BAG files were exported from the CUBE PFM grid as detailed in the DAPR.</ns1:discussion><ns1:surface><ns2:purpose>Object detection coverage, Option B (200% side scan sonar coverage with concurrent multibeam)</ns2:purpose><ns2:surfaceName>H13295_MB_50cm_MLLW_Final_1of6</ns2:surfaceName><ns2:surfaceType>BAG</ns2:surfaceType><ns2:surfaceParameter>N/A</ns2:surfaceParameter><ns2:depthRange><ns2:min units="meters">6.331</ns2:min><ns2:max units="meters">16.964</ns2:max></ns2:depthRange><ns2:resolution units="centimeters">50</ns2:resolution></ns1:surface><ns1:surface><ns2:purpose>Object detection coverage, Option B (200% side scan sonar coverage with concurrent multibeam)</ns2:purpose><ns2:surfaceName>H13295_MB_50cm_MLLW_Final_2of6</ns2:surfaceName><ns2:surfaceType>BAG</ns2:surfaceType><ns2:surfaceParameter>N/A</ns2:surfaceParameter><ns2:depthRange><ns2:min units="meters">5.525</ns2:min><ns2:max units="meters">12.762</ns2:max></ns2:depthRange><ns2:resolution units="centimeters">50</ns2:resolution></ns1:surface><ns1:surface><ns2:purpose>Object detection coverage, Option B (200% side scan sonar coverage with concurrent multibeam)</ns2:purpose><ns2:surfaceName>H13295_MB_50cm_MLLW_Final_3of6</ns2:surfaceName><ns2:surfaceType>BAG</ns2:surfaceType><ns2:surfaceParameter>N/A</ns2:surfaceParameter><ns2:depthRange><ns2:min units="meters">5.461</ns2:min><ns2:max units="meters">18.626</ns2:max></ns2:depthRange><ns2:resolution units="centimeters">50</ns2:resolution></ns1:surface><ns1:surface><ns2:purpose>Object detection coverage, Option B (200% side scan sonar coverage with concurrent multibeam)</ns2:purpose><ns2:surfaceName>H13295_MB_50cm_MLLW_Final_4of6</ns2:surfaceName><ns2:surfaceType>BAG</ns2:surfaceType><ns2:surfaceParameter>N/A</ns2:surfaceParameter><ns2:depthRange><ns2:min units="meters">4.098</ns2:min><ns2:max units="meters">20.396</ns2:max></ns2:depthRange><ns2:resolution units="centimeters">50</ns2:resolution></ns1:surface><ns1:surface><ns2:purpose>Object detection coverage, Option B (200% side scan sonar coverage with concurrent multibeam)</ns2:purpose><ns2:surfaceName>H13295_MB_50cm_MLLW_Final_5of6</ns2:surfaceName><ns2:surfaceType>BAG</ns2:surfaceType><ns2:surfaceParameter>N/A</ns2:surfaceParameter><ns2:depthRange><ns2:min units="meters">5.637</ns2:min><ns2:max units="meters">20.851</ns2:max></ns2:depthRange><ns2:resolution units="centimeters">50</ns2:resolution></ns1:surface><ns1:surface><ns2:purpose>Object detection coverage, Option B (200% side scan sonar coverage with concurrent multibeam)</ns2:purpose><ns2:surfaceName>H13295_MB_50cm_MLLW_Final_6of6</ns2:surfaceName><ns2:surfaceType>BAG</ns2:surfaceType><ns2:surfaceParameter>N/A</ns2:surfaceParameter><ns2:depthRange><ns2:min units="meters">8.91</ns2:min><ns2:max units="meters">20.339</ns2:max></ns2:depthRange><ns2:resolution units="centimeters">50</ns2:resolution></ns1:surface><ns1:surface><ns2:purpose>Object detection coverage, Option B (200% side scan sonar coverage with concurrent multibeam)</ns2:purpose><ns2:surfaceName>H13295_MB_1m_MLLW_Final</ns2:surfaceName><ns2:surfaceType>BAG</ns2:surfaceType><ns2:surfaceParameter>N/A</ns2:surfaceParameter><ns2:depthRange><ns2:min units="meters">16.623</ns2:min><ns2:max units="meters">44.153</ns2:max></ns2:depthRange><ns2:resolution units="meters">1</ns2:resolution></ns1:surface><ns1:surface><ns2:purpose>First 100% SSS</ns2:purpose><ns2:surfaceName>H13295_SSSAB_1m_100kHz_1of2</ns2:surfaceName><ns2:surfaceType>SSS Mosaic (.tif)</ns2:surfaceType><ns2:surfaceParameter>N/A</ns2:surfaceParameter><ns2:depthRange><ns2:min units="meters">0.0</ns2:min><ns2:max units="meters">0.0</ns2:max></ns2:depthRange><ns2:resolution units="meters">1</ns2:resolution></ns1:surface><ns1:surface><ns2:purpose>Second 100% SSS </ns2:purpose><ns2:surfaceName>H13295_SSSAB_1m_100kHz_2of2</ns2:surfaceName><ns2:surfaceType>SSS Mosaic (.tif)</ns2:surfaceType><ns2:surfaceParameter>N/A</ns2:surfaceParameter><ns2:depthRange><ns2:min units="meters">0.0</ns2:min><ns2:max units="meters">0.0</ns2:max></ns2:depthRange><ns2:resolution units="meters">1</ns2:resolution></ns1:surface><ns1:comments/></ns1:surfaces></ns1:dataProcessing><ns1:qualityControl><ns1:uncertainty><ns2:comments/><ns2:values><ns2:soundSpeedUncertainty><ns2:hullID>Atlantic Surveyor</ns2:hullID><ns2:measuredXBT units="meters/second">1</ns2:measuredXBT><ns2:surface units="meters/second">1</ns2:surface><ns2:measuredCTD units="meters/second">1</ns2:measuredCTD><ns2:measuredMVP units="meters/second">1</ns2:measuredMVP></ns2:soundSpeedUncertainty><ns2:tideUncertainty><ns2:tideMethod>ERS via VDATUM</ns2:tideMethod><ns2:zoning units="meters">0.09</ns2:zoning><ns2:measured units="meters">0.15</ns2:measured></ns2:tideUncertainty></ns2:values><ns2: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 5th 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).

Per HSSD Section 5.2.2.2, H13295 depth data fell within three grid resolutions (50-centimeter, 1-meter, and 4-meter). Leidos was granted a waiver (05 March 2020) and the H13295 data are presented at 50-centimeter and 1-meter grid resolution. The email correspondence for the grid resolution waiver is included within Appendix II of this Descriptive Report. 

The final H13295 50-centimeter PFM CUBE surface contained final vertical uncertainties that ranged from 0.210 meters to 1.476 meters. The IHO Order 1a maximum allowable vertical uncertainty was calculated to range between 0.503 to 0.569 meters, based on the minimum CUBE depth (4.098 meters) and maximum CUBE depth (20.851 meters). Results from the SABER Check PFM Uncertainty function identified that there were 1,267nodes in the final H13295 50-centimeter PFM CUBE surface with final vertical uncertainties that exceeded IHO Order 1a allowable vertical uncertainty. Nodes were associated along features and shifting sand waves, discussed in Section D.2.7. The SABER Frequency Distribution Tool was also used to review the Hyp. Final Uncertainty surface within the final H13295 50-centimeter PFM grid. Results showed that 99.99% of all nodes had final uncertainties less than or equal to 0.569 meters.

The final H13295 1-meter PFM CUBE surface contained final vertical uncertainties that ranged from 0.210 meters to 0.716 meters. The IHO Order 1a maximum allowable vertical uncertainty was calculated to range between 0.545 to 0.781 meters, based on the minimum CUBE depth (16.623 meters) and maximum CUBE depth (44.153 meters). Results from the SABER Check PFM Uncertainty function identified that there were 20 nodes in the final H13295 1-meter PFM CUBE surface with final vertical uncertainties that exceeded IHO Order 1a allowable vertical uncertainty. These nodes were associated shifting sand waves, discussed in Section D.2.7.The SABER Frequency Distribution Tool was also used to review the Hyp. Final Uncertainty surface within the final H13295 1-meter PFM grid. Results showed that 99.99% of all nodes had final uncertainties less than or equal to 0.760 meters.</ns2:discussion></ns1:uncertainty><ns1:additionalQualityControl><ns2:comments/><ns2:issue><ns2:title>Multibeam Coverage Analysis</ns2:title><ns2:comments/><ns2:discussion>Leidos  chose to achieve the coverage requirement using 200% side scan sonar coverage with concurrent multibeam bathymetry. To achieve this coverage, the M/V Atlantic Surveyor used a towed Klein 3000 SSS set to 50-meter range scale. Mainscheme line spacing was set to 40 meters, which ensured 200% SSS coverage.

The SABER Gapchecker program was used to flag MBES data gaps within the CUBE surface. Additionally, 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 referenced in Section B.2.2, the depth data for H13295 fell within multiple grid resolutions listed in the HSSD. Leidos received a waiver regarding the grid resolutions. A final review conducted on the CUBE Depth surfaces from the 50-centimeter and 1-meter PFM grids showed that there were no holidays as defined for object detection coverage surveys, HSSD Section 5.2.2.2.

Within the final CUBE surfaces (50-centimeter and 1-meter), there were instances where a three by one node gap exists, however, these were not considered holidays in the final multibeam CUBE surface as these instances generally resulted from either the holiday line data being slightly offset from the original line due to vessel line steering, or the swath width of the holiday lines being reduced compared to the original line due to water level differences.

The final H13295 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 surfaces from each of the PFM grids to ensure that the requirements for object detection coverage surveys, as specified in HSSD Section 5.2.2.2 were met. Within the final 50-centimeter PFM grid 99.24% of all nodes contained five or more soundings; and in the 1-meter PFM grid 99.95% of all nodes contained five or more soundings.</ns2:discussion></ns2:issue></ns1:additionalQualityControl><ns1:sonarQCChecks><ns2:results deviation="false"><ns2:discussion>Sonar system quality control checks were conducted as detailed in the DAPR; quality control checks conducted during H13295 are reported in Separates I.</ns2:discussion></ns2:results><ns2:comments/></ns1:sonarQCChecks><ns1:equipmentEffectiveness><ns2:results deviation="false"><ns2:issue><ns2:title>None Exist</ns2:title><ns2:comments/><ns2:discussion>There were no conditions or deficiencies that affected equipment operational effectiveness.</ns2:discussion></ns2:issue></ns2:results><ns2:comments/></ns1:equipmentEffectiveness><ns1:soundSpeedMethods><ns1:discussion xsi:nil="true"></ns1:discussion><ns1:castFrequency>On the M/V Atlantic Surveyor, the MVP30 was the primary system used to collect sound speed profile (SSP) data, refer to the DAPR for additional details. SSP data were obtained at intervals frequent enough to meet depth accuracy requirements. Section 5.2.3.3 of the HSSD requires that if the sound speed measured at the sonar head differs by more than two meters/second from the commensurate profile data, then another cast shall be acquired.

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 conducted by comparing at least two consecutive casts taken with different SSP sensors. Six sound speed confidence checks were conducted during H13295 and the results can be found in Separates II within the “Comparison Cast Log” section.

All individual SSP files are delivered with the H13295 data and are broken out into sub-folders, which correspond to the purpose of each cast. Also, all individual SSP files for H13295 have been concatenated into four separate files based on the purpose of the cast, provided in CARIS format files (.svp), and delivered under (H13295/Processed/SVP/CARIS_SSP) on the delivery drive. In accordance with HSSD Section 8.3.6 H13295 data were collected over two years, the submission of the NCEI data is separated by calendar year. Refer to Separates II for additional details. </ns1:castFrequency><ns1:comments/></ns1:soundSpeedMethods><ns1:coverageEquipmentAndMethods><ns2:results deviation="false"><ns2:discussion>All equipment and survey methods are detailed in the DAPR.</ns2:discussion></ns2:results><ns2:comments/></ns1:coverageEquipmentAndMethods><ns1:factorsAffectingSoundings><ns2:results deviation="false"><ns2:issue><ns2:title>None Exist</ns2:title><ns2:comments/><ns2:discussion>There were no other factors that affected corrections to soundings.</ns2:discussion></ns2:issue></ns2:results><ns2:comments/></ns1:factorsAffectingSoundings><ns1:junctions><ns2:images><ns2:link>SupportFiles\H13295_Figure_07.jpg</ns2:link><ns2:caption>General Locality of H13295 with Junctioning Surveys</ns2:caption></ns2:images><ns2:comments/><ns2:junction><ns2:comments/><ns2:survey><ns2:fieldUnit>NOAA Ship Thomas Jefferson</ns2:fieldUnit><ns2:year>2010</ns2:year><ns2:relativeLocation>SW</ns2:relativeLocation><ns2:scale>20000</ns2:scale><ns2:registryNumber>H12182</ns2:registryNumber></ns2:survey><ns2:discussion>H13295 junctions with H12182 to the southwest; 100% of the comparisons agreed within ±0.829 meters while 99.96% of the comparison results fell within the calculated maximum allowable TVU of 0.540 meters.</ns2:discussion></ns2:junction><ns2:junction><ns2:comments/><ns2:survey><ns2:fieldUnit>NOAA Ship Thomas Jefferson</ns2:fieldUnit><ns2:year>2012</ns2:year><ns2:relativeLocation>NE</ns2:relativeLocation><ns2:scale>20000</ns2:scale><ns2:registryNumber>H12421</ns2:registryNumber></ns2:survey><ns2:discussion>H13295 junctions with H12421 to the northeast; 100% of the comparisons agreed within ±1.965 meters while 77.22% of the comparison results fell within the calculated maximum allowable TVU of 0.710 meters.</ns2:discussion></ns2:junction><ns2:discussion>Per the Project Instructions, analyses of the H13295 junctions with adjacent surveys were performed between H13295 and the surveys listed in Table 7. Figure 7 shows the general locality of H13295 as it relates to the sheets to which junctions were performed. Refer to Separates II for details about how junction analyses were performed and a complete discussion of each analysis and tabular results. </ns2:discussion></ns1:junctions><ns1:crosslines><ns2:images><ns2:link>SupportFiles\H13295_Figure_06.jpg</ns2:link><ns2:caption>Summary of Crossing Analysis</ns2:caption></ns2:images><ns2:comments/><ns2:discussion>Refer to Separates II for details about how the crossing analyses were performed and a complete discussion of each analysis and tabular results. Figure 6 summarizes the crossline comparison results.</ns2:discussion></ns1:crosslines></ns1:qualityControl></ns1:dataAcquisitionAndProcessing><ns1:metadata><ns1:surveyMetadata><ns2:titlesheetRemarks><ns2:fieldRemarks>Contract: EA-133C-14-CQ-0033/TO-0006. 
Contractor: Leidos, 221 Third Street, Newport, RI 02840 USA. 
Subcontractors: Divemasters, Inc., 15 Pumpshire Road, Toms River, NJ 08753; OARS, 8705 Shoal Creek Blvd, Suite 109, Austin, TX 78757. 
Leidos Doc. 20-TR-022.
All times were recorded in UTC. 
Final data are corrected to North American Datum of 1983 (NAD83) 2011 realization 2010 (NAD83(2011)2010.0), UTM Zone 18N.</ns2:fieldRemarks><ns2:branchRemarks xsi:nil="true"></ns2:branchRemarks></ns2:titlesheetRemarks><ns2:year>2020</ns2:year><ns2:acquisition><ns2:units>meters</ns2:units></ns2:acquisition><ns2:projectType>Basic Hydrographic Survey</ns2:projectType><ns2:chiefOfParty>Bridget W. Bernier</ns2:chiefOfParty><ns2:datesOfSurvey><ns2:end>2020-06-26</ns2:end><ns2:start>2019-10-26</ns2:start></ns2:datesOfSurvey><ns2:equipmentTypes><ns2:soundingEquipment>Multibeam Echo Sounder</ns2:soundingEquipment><ns2:imageryEquipment>Side Scan Sonar</ns2:imageryEquipment><ns2:imageryEquipment>Multibeam Echo Sounder Backscatter</ns2:imageryEquipment></ns2:equipmentTypes><ns2:PIDate>2019-08-27</ns2:PIDate><ns2:timeZone>UTC</ns2:timeZone><ns2:verifier>Atlantic Hydrographic Branch</ns2:verifier></ns1:surveyMetadata><ns1:assignment>Contractor</ns1:assignment><ns1:registryMetadata><ns2:sublocality>Old Plantation Flats</ns2:sublocality><ns2:registryNumber>H13295</ns2:registryNumber><ns2:sheetID>1</ns2:sheetID><ns2:stateOrTerritory>Virginia</ns2:stateOrTerritory><ns2:scale>20000</ns2:scale><ns2:country>United States</ns2:country><ns2:registryInstructions xsi:nil="true"></ns2:registryInstructions></ns1:registryMetadata><ns1:projectMetadata><ns2:fieldUnit>SAIC</ns2:fieldUnit><ns2:generalLocality>Southern Chesapeake Bay</ns2:generalLocality><ns2:name>Southern Chesapeake Bay, Virginia</ns2:name><ns2:number>OPR-E350-KR-19</ns2:number></ns1:projectMetadata></ns1:metadata></ns1:descriptiveReport>