<?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:surveyCoverage><ns2:coverageRequirement><ns2:waterDepth>All waters in survey area</ns2:waterDepth><ns2:requiredCoverage>Object Detection Coverage</ns2:requiredCoverage></ns2:coverageRequirement><ns2:results deviation="true"><ns2:discussion>Sections of H13298 were surveyed to object detection coverage by complete object detection multibeam echosounder (MBES) coverage (Figure 8) and by 200% side scan sonar (SSS) coverage with concurrent MBES (Figures 9 and 10), as specified in the Project Instructions (PI) and the Hydrographic Surveys Specifications and Deliverables (HSSD) dated March 2019. Sections of H13298 were also surveyed by 200% SSS coverage with concurrent singlebeam echosounder (SBES) (Figures 11 and 12) (see Appendix II for documentation in regards to use of the SBES). Six holidays exist in SSS coverage (Figures 13 and 14). Four of the holidays exist in the 100% coverage and two of the holidays exist in the 200% coverage. Five of the holidays are covered only once by SSS coverage and no indications of significant features were observed. The sixth holiday was not covered by either SSS coverage or MBES coverage; it is the southernmost holiday shown in Figure 13 and is located at 36°56'21.73&quot;N 076°25'43.33&quot;W. There are 26 holidays in the VR surface that covers the area of 100% MBES coverage. Twelve holidays are covered once by either 100% SSS or 200% SSS coverage, six are covered by both 100% SSS and 200% SSS coverage, and no indications of significant features were observed. The remaining eight MBES holidays are not covered by SSS (Figure 15). Four holidays were observed in SBES data. Two are located at 36°56'23.45&quot;N 076°25'43.60&quot;W where a barge was anchored during survey operations (Figure 16). The other two are located at 36°55'48.66&quot;N 076°25'05.98&quot;W and 37°00'39.66&quot;N 076°29'44.12&quot;W (Figures 16 and 17). Other data deficiencies exist in both the SSS and MBES due to equipment effectiveness and environmental factors; see sections B.2.5 Equipment Effectiveness and B.2.6 Factors Affecting Soundings for a complete discussion.</ns2:discussion><ns2:images><ns2:link>SupportFiles\A.4_MBES_Coverage.png</ns2:link><ns2:caption>Areas outlined in blue represent 100% object detection MBES coverage for H13298.</ns2:caption></ns2:images><ns2:images><ns2:link>SupportFiles\A.4_MBES_SSS_Coverage_South.png</ns2:link><ns2:caption>Area outlined in blue represents the southern portion of H13298 covered by SSS with concurrent MBES.</ns2:caption></ns2:images><ns2:images><ns2:link>SupportFiles\A.4_MBES_SSS_Coverage_North.png</ns2:link><ns2:caption>Area outlined in blue represents the northern portion of H13298 covered by SSS with concurrent MBES.</ns2:caption></ns2:images><ns2:images><ns2:link>SupportFiles\A.4_SBES_SSS_Coverage_South.png</ns2:link><ns2:caption>Area outlined in blue represents the southern portion of H13298 covered by SSS with concurrent SBES.</ns2:caption></ns2:images><ns2:images><ns2:link>SupportFiles\A.4_SBES_SSS_Coverage_North.png</ns2:link><ns2:caption>Area outlined in blue represents the northern portion of H13298 covered by SSS with concurrent SBES.</ns2:caption></ns2:images><ns2:images><ns2:link>SupportFiles\A.4_SSS_100_Holidays.png</ns2:link><ns2:caption>Holidays in 100% SSS coverage. </ns2:caption></ns2:images><ns2:images><ns2:link>SupportFiles\A.4_SSS_200_Holidays.png</ns2:link><ns2:caption>Holidays in 200% SSS coverage. </ns2:caption></ns2:images><ns2:images><ns2:link>SupportFiles\A.4_MBESHolidays.png</ns2:link><ns2:caption>Holidays in complete coverage MBES not covered by SSS coverage.</ns2:caption></ns2:images><ns2:images><ns2:link>SupportFiles\A.4_SBES_Holidays_South.png</ns2:link><ns2:caption>SBES holiday in the southern portion of H13298.</ns2:caption></ns2:images><ns2:images><ns2:link>SupportFiles\A.4_SBES_Holidays_North.png</ns2:link><ns2:caption>SBES holiday in the northern portion of H13298.</ns2:caption></ns2:images></ns2:results><ns2:comments/></ns1:surveyCoverage><ns1:coverageGraphic><ns2:coverageGraphicImage/></ns1:coverageGraphic><ns1:surveyStatistics><ns2:totalSurveyStats><ns2:SNM>11.44</ns2:SNM><ns2:maritimeBoundaryPoints>0</ns2:maritimeBoundaryPoints><ns2:diveOps>0</ns2:diveOps><ns2:bottomSamples>7</ns2:bottomSamples><ns2:DP>0</ns2:DP></ns2:totalSurveyStats><ns2:surveyDates>2019-07-09</ns2:surveyDates><ns2:surveyDates>2019-07-10</ns2:surveyDates><ns2:surveyDates>2019-07-11</ns2:surveyDates><ns2:surveyDates>2019-07-14</ns2:surveyDates><ns2:surveyDates>2019-07-15</ns2:surveyDates><ns2:surveyDates>2019-07-16</ns2:surveyDates><ns2:surveyDates>2019-07-17</ns2:surveyDates><ns2:surveyDates>2019-07-19</ns2:surveyDates><ns2:surveyDates>2019-07-22</ns2:surveyDates><ns2:surveyDates>2019-07-29</ns2:surveyDates><ns2:surveyDates>2019-07-30</ns2:surveyDates><ns2:surveyDates>2019-07-31</ns2:surveyDates><ns2:surveyDates>2019-08-01</ns2:surveyDates><ns2:surveyDates>2019-08-02</ns2:surveyDates><ns2:surveyDates>2019-08-04</ns2:surveyDates><ns2:surveyDates>2019-12-19</ns2:surveyDates><ns2:surveyDates>2019-12-21</ns2:surveyDates><ns2:LNM><ns2:totalLNM><ns2:XL_lidar>0</ns2:XL_lidar><ns2:MS_SBES_SSS>352.91</ns2:MS_SBES_SSS><ns2:MS_MBES>136.06</ns2:MS_MBES><ns2:MS_SSS>0</ns2:MS_SSS><ns2:MS_SBES>0</ns2:MS_SBES><ns2:MS_MBES_SSS>81.46</ns2:MS_MBES_SSS><ns2:MS_SBES_MBES>0</ns2:MS_SBES_MBES><ns2:XL_MBES_SBES>11.04</ns2:XL_MBES_SBES><ns2:percentXLLNM>1.94</ns2:percentXLLNM><ns2:MS_lidar>0</ns2:MS_lidar></ns2:totalLNM><ns2:vesselLNM><ns2:vessel><ns2:statistics><ns2:XL_lidar>0</ns2:XL_lidar><ns2:MS_SBES_SSS>352.91</ns2:MS_SBES_SSS><ns2:MS_MBES>2.36</ns2:MS_MBES><ns2:MS_SSS>0</ns2:MS_SSS><ns2:MS_SBES>0</ns2:MS_SBES><ns2:MS_MBES_SSS>0</ns2:MS_MBES_SSS><ns2:MS_SBES_MBES>0</ns2:MS_SBES_MBES><ns2:XL_MBES_SBES>0</ns2:XL_MBES_SBES><ns2:MS_lidar>0</ns2:MS_lidar></ns2:statistics><ns2:hullID>2903</ns2:hullID></ns2:vessel><ns2:vessel><ns2:statistics><ns2:XL_lidar>0</ns2:XL_lidar><ns2:MS_SBES_SSS>0</ns2:MS_SBES_SSS><ns2:MS_MBES>133.7</ns2:MS_MBES><ns2:MS_SSS>0</ns2:MS_SSS><ns2:MS_SBES>0</ns2:MS_SBES><ns2:MS_MBES_SSS>96.69</ns2:MS_MBES_SSS><ns2:MS_SBES_MBES>0</ns2:MS_SBES_MBES><ns2:XL_MBES_SBES>11.04</ns2:XL_MBES_SBES><ns2:MS_lidar>0</ns2:MS_lidar></ns2:statistics><ns2:hullID>2904</ns2:hullID></ns2:vessel></ns2:vesselLNM></ns2:LNM><ns2:comments/><ns2:discussion xsi:nil="true"></ns2:discussion></ns1:surveyStatistics><ns1:surveyPurpose><ns2:discussion>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. Without recent hydrographic data, USCG lacks confidence that charted shoals are accurately positioned and is having a hard time producing a comprehensive report, and is thus looking forward to new data in the lower James River to update the latest surveys from 1945. This project will provide critical data for the updating of National Ocean Service (NOS) nautical charting products and services 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><ns2:comments/></ns1:surveyPurpose><ns1:surveyLimits><ns2:results deviation="true"><ns2:discussion>The Navigable Area Limit Line (NALL) was met within the limits of H13298 in the southern region around the Nansemond River Channel (Figure 2). Some areas were not surveyed to the NALL because the conditions within those areas were deemed too dangerous for survey operations (Figures 3 and 4, Areas A, B, C, and D). An area of the assigned survey limits was not surveyed due to the restriction of survey operations within a security area around Newport News Shipbuilding (Figure 5, Area E). Some areas of the assigned survey limits were not addressed due to operational time constraints (Figures 6 and 7). </ns2:discussion><ns2:images><ns2:link>SupportFiles\A.1_NallArea.png</ns2:link><ns2:caption>Area where the NALL was met within the limits of H13298. 3.5m depth contour shown in black.</ns2:caption></ns2:images><ns2:images><ns2:link>SupportFiles\A.1_South_Danger_Areas.png</ns2:link><ns2:caption>Survey limits were not met in areas A and B due to proximity to the Monitor Merrimac Memorial Bridge Tunnel. </ns2:caption></ns2:images><ns2:images><ns2:link>SupportFiles\A.1_North_Danger_Areas.png</ns2:link><ns2:caption>Survey limits were not met in areas C and D due to proximity to hazardous features.</ns2:caption></ns2:images><ns2:images><ns2:link>SupportFiles\A.1_Security_Area.png</ns2:link><ns2:caption>Survey limits were not met in the security area surrounding Newport News Shipbuilding in Area E.</ns2:caption></ns2:images><ns2:images><ns2:link>SupportFiles\A.1_Time_Constraints_South.png</ns2:link><ns2:caption>Survey limits were not met in the south east section of H13298 due to operational time constraints.</ns2:caption></ns2:images><ns2:images><ns2:link>SupportFiles\A.1_Time_Constraints_North.png</ns2:link><ns2:caption>Survey limits were not met in the northern section of H13298 due to operational time constraints.</ns2:caption></ns2:images></ns2:results><ns2:comments/></ns1:surveyLimits><ns1:areaDescription><ns2:limits><ns2:southEast><ns2:latitude hemisphere="N">36.921</ns2:latitude><ns2:longitude hemisphere="W">76.412</ns2:longitude></ns2:southEast><ns2:northWest><ns2:latitude hemisphere="N">37.054</ns2:latitude><ns2:longitude hemisphere="W">76.588</ns2:longitude></ns2:northWest></ns2:limits><ns2:discussion>Survey H13298 is located in the White Shoal are of the Chesapeake Bay, VA (Table 1 and Figure 1). </ns2:discussion><ns2:images><ns2:link>SupportFiles\A.1_SurveyLimits_Overview.png</ns2:link><ns2:caption>Survey layout for H13298, plotted over ENC US5VA15M and UA5VA25M. Black outline represents the survey limits set forth by the Project Instructions. </ns2:caption></ns2:images><ns2:comments/></ns1:areaDescription><ns1:surveyQuality><ns2:discussion>Object detection coverage for H13298 was accomplished using three methods. These three methods are 100% bathymetric bottom coverage, 200% side scan sonar (SSS) coverage with concurrent multibeam, and 200% SSS coverage with concurrent single beam. See section A.4 Survey Coverage, B.2.8 Coverage Equipment and Methods, and B.5.2 Surfaces for a complete discussion.</ns2:discussion><ns2:adequacy>The survey is partially adequate to supersede previous data.</ns2:adequacy><ns2:comments/></ns1:surveyQuality></ns1:areaSurveyed><ns1:verticalAndHorizontalControl><ns1:discussion>No Horizontal and Vertical Control Report (HVCR) is required for this survey.</ns1:discussion><ns1:verticalControl><ns2:standard_or_ERZT used="false" xsi:nil="true"/><ns2:verticalDatum>Mean Lower Low Water</ns2:verticalDatum><ns2:tideStations/><ns2:VDATUM_or_constantSep used="true"><ns2:ellipsoidToChartDatumSepFile><ns2:fileName>OPR-E350-TJ-19_NAD83-MLLW_Geoid12B</ns2:fileName></ns2:ellipsoidToChartDatumSepFile><ns2:methodsUsed>ERS via VDATUM</ns2:methodsUsed><ns2:discussion>All soundings submitted for H13327 are reduced to MLLW using VDatum techniques as outlined in the DAPR.</ns2:discussion><ns2:comments/></ns2:VDATUM_or_constantSep><ns2:comments/></ns1:verticalControl><ns1:additionalIssues><ns2:issue><ns2:discussion>HSLs 2903 and 2904 experienced losses of Primary DGPS mode in the POS/MV system on multiple days during survey acquisition. Below is a list of days on which this issue occurred and how many times losses were experienced. These losses were detected while reviewing the SBET's AutoQC graphs (Figure 47). All losses of Primary DGPS mode were less than one second in length and were correllated with losses of satellite coverage across both the primary and secondary GNSS receivers (Figure 48). The cause of this coverage loss is unknown. Neither MBES or SBES data quality appear to be affected by these brief drop outs. Below is a list of days on which this issue occurred and how many times losses were experienced. 
2903 DN197- 2 losses
2903 DN198- 1 loss
2903 DN203- 2 losses
2903 DN210- 1 loss
2903 DN211- 3 losses
2903 DN212- 1 loss
2903 DN213- 2 losses
2903 DN214- 1 loss
2903 DN217- 5 losses (Figures 47 and 48)
2904 DN192- 4 losses
2904 DN211- 1 loss
2904 DN214- 2 losses
2904 DN216- 2 losses
2904 DN353- 1 loss</ns2:discussion><ns2:title>Loss of Primary DGPS fix.</ns2:title><ns2:images><ns2:link>SupportFiles\C.3_2903_217_1.png</ns2:link><ns2:caption>Loss of Primary DGPS mode seen on HSL 2903 DN217.</ns2:caption></ns2:images><ns2:images><ns2:link>SupportFiles\C.3_2903_217_2.png</ns2:link><ns2:caption>Loss of satellite coverage see on HSL 2903 DN217.</ns2:caption></ns2:images><ns2:comments/></ns2:issue><ns2:comments/></ns1:additionalIssues><ns1:horizontalControl><ns2:PPP used="true"><ns2:discussion>Trimble-RTX service was used with an Applanix POS MVv5 GNSS-INS system to obtain highly accurate ellipsoidally referenced position data to meet ERS specifications for H13298 MBES and SBES data.</ns2:discussion><ns2:comments/></ns2:PPP><ns2:DGPS used="false" xsi:nil="true"/><ns2:PPK used="false" xsi:nil="true"/><ns2:horizontalDatum>North American Datum 1983</ns2:horizontalDatum><ns2:RTK used="false" xsi:nil="true"/><ns2:WAAS used="true"><ns2:discussion>The Wide Area Augmentation System (WAAS) was used for real-time horizontal control during data acquisition.</ns2:discussion><ns2:comments/></ns2:WAAS><ns2:projection>Projected UTM 18</ns2:projection><ns2:comments/></ns1:horizontalControl></ns1:verticalAndHorizontalControl><ns1:metadata><ns1:projectMetadata><ns2:number>OPR-E350-TJ-19</ns2:number><ns2:fieldUnit>NOAA Ship Thomas Jefferson (S222)</ns2:fieldUnit><ns2:generalLocality>Southern Chesapeake Bay</ns2:generalLocality><ns2:name>Southern Chesapeake Bay, Virginia</ns2:name></ns1:projectMetadata><ns1:registryMetadata><ns2:scale>10000</ns2:scale><ns2:registryInstructions xsi:nil="true"></ns2:registryInstructions><ns2:stateOrTerritory>Virginia</ns2:stateOrTerritory><ns2:registryNumber>H13298</ns2:registryNumber><ns2:country>United States</ns2:country><ns2:sheetID>2</ns2:sheetID><ns2:sublocality>White Shoal</ns2:sublocality></ns1:registryMetadata><ns1:assignment>NOAA</ns1:assignment><ns1:surveyMetadata><ns2:PIDate>2019-07-05</ns2:PIDate><ns2:projectType>Navigable Area</ns2:projectType><ns2:timeZone>UTC</ns2:timeZone><ns2:verifier>Atlantic Hydrographic Branch</ns2:verifier><ns2:datesOfSurvey><ns2:end>2019-12-21</ns2:end><ns2:start>2019-07-09</ns2:start></ns2:datesOfSurvey><ns2:chiefOfParty>CDR Briana Hillstrom, NOAA</ns2:chiefOfParty><ns2:equipmentTypes><ns2:imageryEquipment>Side Scan Sonar</ns2:imageryEquipment><ns2:imageryEquipment>Multibeam Echo Sounder Backscatter</ns2:imageryEquipment><ns2:soundingEquipment>Singlebeam Echo Sounder </ns2:soundingEquipment><ns2:soundingEquipment>Multibeam Echo Sounder</ns2:soundingEquipment></ns2:equipmentTypes><ns2:year>2019</ns2:year><ns2:titlesheetRemarks><ns2:branchRemarks>Any revisions to the Descriptive Report (DR) applied during office processing are shown in red italic text. The DR is maintained as a field unit product, therefore all information and recommendations within this report are considered preliminary unless otherwise noted. The final disposition of survey data is represented in the NOAA nautical chart products. All pertinent records for this survey are archived at the National Centers for Environmental Information (NCEI) and can be retrieved via https://www.ncei.noaa.gov/. 

Products created during office processing were generated in NAD83 UTM 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.</ns2:branchRemarks><ns2:fieldRemarks xsi:nil="true"></ns2:fieldRemarks></ns2:titlesheetRemarks><ns2:acquisition><ns2:units>meters</ns2:units></ns2:acquisition></ns1:surveyMetadata></ns1:metadata><ns1:resultsAndRecommendations><ns1:additionalResults><ns1:platforms><ns2:results investigated="Exist - Not Investigated"><ns2:discussion>Three platforms exist for this survey, but were not investigated.</ns2:discussion></ns2:results><ns2:comments/></ns1:platforms><ns1:shoreline><ns2:results investigated="None Exist"><ns2:discussion>Shoreline was not assigned in the Project Instructions or Statement of Work.</ns2:discussion></ns2:results><ns2:comments/></ns1:shoreline><ns1:abnormalSeafloorEnviroCond><ns2:results investigated="None Exist"><ns2:discussion>No abnormal seafloor and/or environmental conditions exist for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:abnormalSeafloorEnviroCond><ns1:newSurveyRecommendation><ns2:results recommended="true"><ns2:discussion>The hydrographer recommends further investigation of charted underwater features and shoal areas not fully addressed by current MBES coverage.</ns2:discussion></ns2:results><ns2:comments/></ns1:newSurveyRecommendation><ns1:overheadFeatures><ns2:results investigated="Exist - Not Investigated"><ns2:discussion>Overhead features exist for this survey, but were not investigated. There are two bridges and one overhead cable. </ns2:discussion></ns2:results><ns2:comments/></ns1:overheadFeatures><ns1:otherResults><ns2:comments/></ns1:otherResults><ns1:ATONS><ns2:results investigated="Investigated"><ns2:discussion>22 Aids to Navigation (ATONs) were investigated while conducting survey H13298. One ATON was found to be leaning and an ATON Discrepancy Report was submitted to the Coast Guard Navigation Center in accordance with HSSD requirements. Reference the Final Feature File and Appendix II for relevant ATON Discrepancy Report documents for further information. An image of the leaning Nansemond River Channel Light 2NR is included in the Final Feature File.</ns2:discussion></ns2:results><ns2:comments/></ns1:ATONS><ns1:insetRecommendation><ns2:results recommended="false"><ns2:discussion>No new insets are recommended for this area.</ns2:discussion></ns2:results><ns2:comments/></ns1:insetRecommendation><ns1:submarineFeatures><ns2:results investigated="Investigated"><ns2:discussion>A portion of the Monitor Merrimac Memorial Bridge Tunnel is contained within H13298. The area was covered with 100% object detection MBES coverage and is in agreement with the charted representation of the tunnel (Figure 56). </ns2:discussion><ns2:images><ns2:link>SupportFiles\D.2_15M_MMMBT.png</ns2:link><ns2:caption>MBES coverage of the Monitor Merrimac Memorial Bridge Tunnel within H13298.</ns2:caption></ns2:images></ns2:results><ns2:comments/></ns1:submarineFeatures><ns1:ferryRoutesAndTerminals><ns2:results investigated="None Exist"><ns2:discussion>No ferry routes or terminals exist for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:ferryRoutesAndTerminals><ns1:constructionOrDredging><ns2:results investigated="None Exist"><ns2:discussion>No present or planned construction or dredging exist within the survey limits.</ns2:discussion></ns2:results><ns2:comments/></ns1:constructionOrDredging></ns1:additionalResults><ns1:chartComparison><ns1:chartedFeatures><ns2:results investigated="Exist - Not Investigated"><ns2:discussion>There is one charted dangerous wreck with a status of &quot;Existence Doubtful&quot; within the limits of H13298 near Rocklanding Shoal Channel located at 37°03'13.75&quot;N -076°34'48.76&quot;W. The source of this feature is Chart 12248 with a source date of 19990828. The location was not covered by MBES or SBES and was only covered by 100% SSS coverage. Little evidence of a dangerous wreck can be seen in the SSS imagery (Figure 51), however, coverage is insufficient for disproval.</ns2:discussion><ns2:images><ns2:link>SupportFiles\D.1_25M_ED_Wreck.png</ns2:link><ns2:caption>Charted dangerous wreck near Rockland Shoal Channel.</ns2:caption></ns2:images></ns2:results><ns2:comments/></ns1:chartedFeatures><ns1:unchartedFeatures><ns2:results investigated="Investigated"><ns2:discussion>There are nine new obstruction features identified in the survey in addition to the two reported DTONs. Reference the Final Feature File for more information. Additionally, due to operational time constraints, many of the identified SSS contacts were not able to be further developed by MBES coverage (Figure 52). It is possible that some of these contacts could be charted as new features. See side scan contacts file for images and locations. </ns2:discussion><ns2:images><ns2:link>SupportFiles\D.1_SSSContacts_NotDeveloped.png</ns2:link><ns2:caption>SSS contacts not covered, or partially covered, by MBES.</ns2:caption></ns2:images></ns2:results><ns2:comments/></ns1:unchartedFeatures><ns1:shoalAndHazardousFeatures><ns2:results investigated="Investigated"><ns2:discussion>One DTON was found and reported on Aug. 7, 2019 for US5VA25M and appears on the most recent ENC edition (Figure 53). The danger was initially identified in both 100% SSS and 200% SSS and was further developed using object detection MBES. The least depth was found to be 2.8m with nearby soundings of 6.4-7m. A second DTON was reported on March 18, 2020 for US5VA15M (Figure 54). It was initially reported as a point obstruction but after further analysis, it is suggested that the feature be represented as an area obstruction. The obstruction area was initially identified in both 100% SSS and 200% SSS coverage and was further developed using object detection MBES. The least depth was found to be 3.4m with nearby soundings of 6.4-7.6m.

Due to operational time constraints, the NALL was not met over most of the survey, so most charted shoals could not be addressed, particularly for ENC US5VA25M.</ns2:discussion><ns2:images><ns2:link>SupportFiles\D.1_25M_DTON.png</ns2:link><ns2:caption>DTON reported for chart US5VA25M.</ns2:caption></ns2:images><ns2:images><ns2:link>SupportFiles\D.1_15M_DTON.png</ns2:link><ns2:caption>DTON reported for chart US5VA15M.</ns2:caption></ns2:images></ns2:results><ns2:comments/></ns1:shoalAndHazardousFeatures><ns1:charts><ns2:ENC><ns2:discussion>Sounding sets derived from H13298's bathymetric surfaces generally agreed with soundings from ENC US5VA15M. However, there are two areas with soundings observed of approximately 1m up to 1.6m shoaler than charted soundings (Figures 49 and 50). One DTON was reported on March 18, 2020 (see Appendix II for relevant documents).</ns2:discussion><ns2:images><ns2:link>SupportFiles\D.1_15M_Shoal_Area_1.png</ns2:link><ns2:caption>Area of shoal soundings in the southern reaches of H13298. Charted soundings in black and SBES soundings in red.</ns2:caption></ns2:images><ns2:images><ns2:link>SupportFiles\D.1_15M_Shoal_Area_2.png</ns2:link><ns2:caption>Area of shoal soundings in the mid-region of H13298. Charted soundings in black and SBES soundings in red.</ns2:caption></ns2:images><ns2:chart><ns2:scale>20000</ns2:scale><ns2:updateApplicationDate>2020-01-28</ns2:updateApplicationDate><ns2:preliminary>false</ns2:preliminary><ns2:issueDate>2020-02-28</ns2:issueDate><ns2:edition>54</ns2:edition><ns2:name>US5VA15M</ns2:name></ns2:chart><ns2:comments/></ns2:ENC><ns2:ENC><ns2:discussion>Sounding sets derived from H13298's bathymetric surfaces showed general deepening of US5VA25M particularly in the most northern region surrounding White Shoal. One DTON was identified and reported on Aug. 7, 2019 (see Appendix II for relevant documents).</ns2:discussion><ns2:chart><ns2:scale>40000</ns2:scale><ns2:updateApplicationDate>2020-01-08</ns2:updateApplicationDate><ns2:preliminary>false</ns2:preliminary><ns2:issueDate>2020-02-19</ns2:issueDate><ns2:edition>30</ns2:edition><ns2:name>US5VA25M</ns2:name></ns2:chart><ns2:comments/></ns2:ENC><ns2:comments/></ns1:charts><ns1:methods><ns2:discussion>Chart comparisons were conducted between survey H13298 soundings and previously charted ENCs US5VA15M and US5VA25M using procedures outlined in the DAPR.</ns2:discussion><ns2:comments/></ns1:methods><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:channels><ns2:results investigated="Investigated"><ns2:discussion>A set of SBES soundings was compared to published controlling depths of the Rocklanding Shoal Channel and was found to be in agreement. A set of MBES soundings was compared to published controlling depths of the Channel to Newport News and was found to be in agreement. </ns2:discussion></ns2:results><ns2:comments/></ns1:channels><ns1:bottomSamples><ns2:results investigated="Investigated"><ns2:discussion>Bottom samples were assigned, investigated, and are included in the Final Feature File. See Figure 55 for a generalized view of H13298's bottom sample locations.</ns2:discussion><ns2:images><ns2:link>SupportFiles\D.1_BS_Locations.png</ns2:link><ns2:caption> General location of bottom samples investigated within the sheet limits of H13298.</ns2:caption></ns2:images></ns2:results><ns2:comments/></ns1:bottomSamples></ns1:chartComparison></ns1:resultsAndRecommendations><ns1:dataAcquisitionAndProcessing><ns1:qualityControl><ns1:crosslines><ns2:discussion>Multibeam/single beam echo sounder/side scan sonar crosslines acquired for this survey totaled 1.89%* of mainscheme acquisition. *1.935%

Hydrographic Survey Launch 2904 collected 11.04 linear nautical miles of MBES crosslines in the southern portion of H13298 (Figure 18) which accounted for 3.35% of mainscheme acquisition in this area. Additional crosslines over the northern portion of the survey area were not collected due to operational time constraints. A 50cm single resolution Combined Uncertainty and Bathymetry Estimator (CUBE) surface of mainscheme data and a 50cm single resolution CUBE surface of crossline data were differenced. The resulting mean was -0.01m and the standard deviation was 0.03m (Figure 20). Visual inspection and statistical analysis of the difference surface indicated no systematic issues.

There were no crosslines acquired by the single beam echosounder. Agreement in observed depths between the MBES and SBES systems was evaluated by creating a 4m single resolution CUBE surface of SBES data and a 50cm single resolution CUBE surface of MBES data (including crosslines). See Figure 19 for a sample area where SBES coverage overlaps MBES coverage. The entire MBES surface was used in order to maximize the number of nodes being compared (10,242 nodes versus only 1,274 nodes when using only MBES crosslines). The two surfaces were differenced and the resulting mean was -0.02m and the standard deviation was 0.05m indicating acceptable agreement between the systems (Figure 21).</ns2:discussion><ns2:images><ns2:link>SupportFiles\B.2_XLines_MBES_Overview.png</ns2:link><ns2:caption>H13298 MBES crossline data, shown in color, overlaid on mainscheme MBES data, shown in greyscale.</ns2:caption></ns2:images><ns2:images><ns2:link>SupportFiles\B.2_MBES_SBES_Overview.png</ns2:link><ns2:caption>Example area of SBES lines, shown in color, overlaid on mainscheme MBES data, shown in greyscale.</ns2:caption></ns2:images><ns2:images><ns2:link>SupportFiles\B.2_MBES_Xline_Stats.png</ns2:link><ns2:caption>H13298 crossline/MBES mainscheme comparison statistics.</ns2:caption></ns2:images><ns2:images><ns2:link>SupportFiles\B.2_MBES_SBES_Stats.png</ns2:link><ns2:caption>H13298 SBES/MBES comparison statistics.</ns2:caption></ns2:images><ns2:comments/></ns1:crosslines><ns1:junctions><ns2:discussion>There are no existing surveys that junction with H13298 at this time. </ns2:discussion><ns2:comments/></ns1:junctions><ns1:factorsAffectingSoundings><ns2:results deviation="true"><ns2:issue><ns2:discussion>H13298 is located in a tidal river area that frequently exhibits stratification due to temperature and salinity differences. This layering greatly affects sound speed and results in refraction in the SSS imagery. The side scan towfish are hull-mounted on HSLs 2903 and 2904 and therefore cannot be lowered below the thermocline or halocline. Figures 29 and 30 show a representative area of refraction with associated profiles from a CTD cast. The CTD cast was conducted on Julian day number 190 at 1800 UTC and the section of side scan data started on Julian day number 190 at 1808 UTC. This area is located at 36°57'09.18&quot;N 076°25'57.37&quot;W. Areas of refraction were seen in the data from both vessels and on multiple days, particularly in the middle to northern extents of the survey. The refraction observed throughout the survey area was not severe enough to impede the detection of a 1m x 1m x 1m object. Figure 31 was taken from line 20190717174533H collected by HSL 2903 and shows a crab pot visible through an area of refraction. The crab pots encountered in the survey area were smaller than 1m x 1m x 1m. </ns2:discussion><ns2:title>Refraction seen in SSS data.</ns2:title><ns2:images><ns2:link>SupportFiles\B.2_Refraction_1.png</ns2:link><ns2:caption>Example of refraction seen in SSS imagery. This example is from HSL 2904 line 20190709180922H and is located at 36°57'09.18&quot;N 076°25'57.37&quot;W. </ns2:caption></ns2:images><ns2:images><ns2:link>SupportFiles\B.2_CTD_Refrac_Location.png</ns2:link><ns2:caption>Overview of location of SSS refraction and associated CTD profiles. A difference of 20m/s can be seen from the surface to 1m water depth. </ns2:caption></ns2:images><ns2:images><ns2:link>SupportFiles\B.2_RefracContact.png</ns2:link><ns2:caption>Crab pot visible through area of refraction on line 20190717174533H from HSL 2903.</ns2:caption></ns2:images><ns2:comments/></ns2:issue><ns2:issue><ns2:discussion>Many large schools of fish were encountered in the middle to southern extents of H13298. Some schools were dense enough to create large acoustic shadows that obscured parts of the seafloor and potential contacts (see Figure 32 for an example). This data deficiency could obscure significant features or their shadows. Data for these areas were not re-acquired due to operational time constraints.</ns2:discussion><ns2:title>Schools of fish obscuring the bottom. </ns2:title><ns2:images><ns2:link>SupportFiles\B.2_Fish_Schools.png</ns2:link><ns2:caption>Example of a shadow from a school of fish potentially obscuring a contact located at 36°58'22.37&quot;N 076°26'21.18&quot;W.</ns2:caption></ns2:images><ns2:comments/></ns2:issue><ns2:issue><ns2:discussion>A large barge was anchored at 36°56'23.45&quot;N 076°25'43.60&quot;W during survey operations. This created holidays in two side scan lines collected by HSL 2903 (20190710143835H and 20190714113252H) and can be seen in two additional lines (20190710152018H and  20190714120728H) (Figures 33 and 34). The presence of the barge may have obscured significant contacts in the area. Data for these holidays were not re-acquired due to operational time constraints.</ns2:discussion><ns2:title>Anchored barge.</ns2:title><ns2:images><ns2:link>SupportFiles\B.2_Barge_1.png</ns2:link><ns2:caption>Barge seen in line 20190710152018H from HSL 2903.</ns2:caption></ns2:images><ns2:images><ns2:link>SupportFiles\B.2_Barge_2.png</ns2:link><ns2:caption>Barge seen in line 20190714120728H from HSL 2903.</ns2:caption></ns2:images><ns2:comments/></ns2:issue><ns2:issue><ns2:discussion>H13298 covers a well-trafficked area and numerous small boats crossed in front of the launches while conducting survey operations. The turbulence from their propellers can be seen in the sidescan data (see Figure 35 for an example). Lines that contain this deficiency are listed below. This data deficiency could potentially obscure significant features. Data for these areas were not re-acquired due to operational time constraints. 
Lines containing incidents of propeller turbulence:
HSL 2903:
20190709153041H
	20190710121459H
	20190710130605H
	20190711132048H
	20190711132554H
	20190714122540H
	20190715180649H
	2903_DN210190729161800
	2903_DN210190729131300
	2903_DN210190729150800
	2903_DN212190731141700
2903_DN212190731150400
	2903_DN213190801153500
	2903_DN213190801174900
	2903_DN214190802135200
	2903_DN214190802141200
HSL 2904:
	20190710142440H</ns2:discussion><ns2:title>Propeller turbulence seen in SSS data.</ns2:title><ns2:images><ns2:link>SupportFiles\B.2_Wake_1.png</ns2:link><ns2:caption>Example of propeller turbulence seen in sidescan data from 2903 line 20190709153041 located at 36°55'25.08&quot;N 076°26'10.01&quot;W.</ns2:caption></ns2:images><ns2:comments/></ns2:issue><ns2:issue><ns2:discussion>The launches encountered greater sea states on a few days of acquisition and motion (roll and yaw) artifacts can be seen in the lines listed below. See Figure 36 for a representative example. These motion artifacts can distort significant features. Data for these areas were not re-acquired due to operational time constraints. 
Lines with significant motion artifacts:
HSL 2903:
20190709153041H
20190710164257H
20190710171338H
20190710180152H
	20190711143618H
	20190711150606H
	20190722123540H
	20190722130844H
HSL 2904:
	20190711134905H
	20190711145734H
	20190711155201H</ns2:discussion><ns2:title>Sea state/motion artifacts.</ns2:title><ns2:images><ns2:link>SupportFiles\B.2_Motion_1.png</ns2:link><ns2:caption>An example of motion (roll and yaw) artifacts seen in SSS data from HSL 2904 line 20190711134905 located at 36°57'50.83&quot;N 076°26'29.37&quot;W.</ns2:caption></ns2:images><ns2:comments/></ns2:issue></ns2:results><ns2:comments/></ns1:factorsAffectingSoundings><ns1:sonarQCChecks><ns2:results deviation="false"><ns2:discussion>Sonar system quality control checks were conducted as detailed in the quality control section of the DAPR.</ns2:discussion></ns2:results><ns2:comments/></ns1:sonarQCChecks><ns1:coverageEquipmentAndMethods><ns2:results deviation="true"><ns2:discussion>HSL 2903 acquired 200% SSS data with concurrent SBES data to meet object detection coverage requirements per the waiver from the Project Manager. Additionally, HSL 2903 collected 100% MBES data over a portion of SSS holidays. SSS data was collected using an Edgetech 4200 system and a Klein 5000 system. SBES data was collected using an Odom CV200 and MBES data was collected using a Kongsberg EM2040.

HSL 2904 acquired 200% SSS data with concurrent MBES data as well as 100% MBES data to meet object detection coverage. SSS data was collected using a Klein 5000 system and MBES data was collected using a Kongsberg EM2040. See section A.4 Survey Coverage Figures 8-12 for an overview of areas of coverage using these three methods. </ns2:discussion></ns2:results><ns2:comments/></ns1:coverageEquipmentAndMethods><ns1:soundSpeedMethods><ns1:discussion xsi:nil="true"></ns1:discussion><ns1:images><ns2:link>SupportFiles\B.2_CTD_Locations.png</ns2:link><ns2:caption>Overview of all CTD casts taken on H13298. Casts for 2903 are in red and casts for 2904 are in blue.</ns2:caption></ns1:images><ns1:comments/><ns1:castFrequency>Sound speed profiles were acquired from HSL 2903 and 2904 in accordance with HSSD 2019 standards using a Sea-Bird Scientific SBE 19plus V2 Conductivity, Temperature, and Depth (CTD) Sensor. CTD casts were conducted from the launches at the beginning of acquisition and then within four hours of each previous cast. Sound speed was monitored by the survey watch to assess sound speed variation in the water column and conduct casts accordingly. MBES and SBES data were corrected by applying sound speed profiles nearest in distance within time (4 hours). All sound speed profile data were concatenated into a master file. A total of 51 sound speed measurements were collected within the survey limits of H13298 with two additional measurements collected outside the data extents (Figure 37). These outside measurements were collected within 500m of survey coverage as specified in the HSSD 2019. All casts provide data representative of the conditions found within the survey area and are appropriate for use.</ns1:castFrequency></ns1:soundSpeedMethods><ns1:equipmentEffectiveness><ns2:results deviation="true"><ns2:issue><ns2:discussion>Beginning on Julian day number 192, an anomaly was noticed in the starboard channel of the Edgetech 4200 side scan data for HSL 2903 (Figure 24). This anomaly persisted on all lines collected with the system through Julian day number 198. The Edgetech was then removed and replaced with a Klein 5000 system. During the equipment swap, an area of the Edgetech cable was found chafed with inner wires exposed.</ns2:discussion><ns2:title>Side scan cable chafe.</ns2:title><ns2:images><ns2:link>SupportFiles\B.2_SSS_Cable_Chafe.png</ns2:link><ns2:caption>Example of data anomaly caused by cable chafe outlined in blue box. </ns2:caption></ns2:images><ns2:comments/></ns2:issue><ns2:issue><ns2:discussion>At some point during Julian day numbers 193-194, the initialization file for the Edgetech 4200 side scan TPU was updated on both HSL 2903 and 2904. However, the compass settings were incorrect and resulted in the data for Julian day numbers 195, 196, 197, 198, and 203 having a reciprocal heading (180 degrees off true heading). The lines from these days were re-processed using the heading information from the vessels instead of the towfish that resulted in the heading data. The compass settings in the initialization files were corrected within the Edgetech TPU per manufacturer recommendation and data collected beginning on Julian day number 216 was processed using the compass information from the towfish. </ns2:discussion><ns2:title>Backward SSS compass.</ns2:title><ns2:comments/></ns2:issue><ns2:issue><ns2:discussion>The location of the side scan mount on HSL 2904 was found to interfere with the MBES swath. This can be seen as a &quot;step&quot; in the data in the outer swath on the starboard side for all lines collected on Julian day numbers 190, 191, and 192 (Figures 25 and 26). Swath Editor was used to filter beams 383-400 to exclude them from the surface. The starboard swath angle was adjusted to 45° for acquisition on Julian day numbers 197-216 so that the MBES swath would not interact with the side scan mount. The side scan mount was removed prior to data acquisition on Julian day numbers 353 and 355, therefore the starboard swath angle was adjusted back to 65°.
</ns2:discussion><ns2:title>Starboard MBES swath interacting with side scan mount. </ns2:title><ns2:images><ns2:link>SupportFiles\B.2_SSS_Mount_1.png</ns2:link><ns2:caption>Example of &quot;step&quot; seen in the outer starboard beams caused by MBES swath interacting with the side scan mount. Example is from line 0056_20190711_155136_2904_EM2040 as seen in Swath Editor.</ns2:caption></ns2:images><ns2:images><ns2:link>SupportFiles\B.2_SSS_Mount_2.png</ns2:link><ns2:caption>Example of &quot;step&quot; seen in the outer starboard beams caused by MBES swath interacting with the side scan mount. Example is from line 0056_20190711_155136_2904_EM2040 as seen in Subset Editor.</ns2:caption></ns2:images><ns2:comments/></ns2:issue><ns2:issue><ns2:discussion>A subbottom return was observed in the near-nadir region of HSL 2904 MBES data (Figures 27 and 28). This return was present in all lines collected with 2904 and does not appear to affect the surface. Subset Editor was used to reject this data.</ns2:discussion><ns2:title>MBES subbottom return near nadir.</ns2:title><ns2:images><ns2:link>SupportFiles\B.2_MBES_Subbottom_Return_2.png</ns2:link><ns2:caption>Example of subbottom return in near-nadir region of HSL 2904 MBES data as seen in Swath Editor. Example is from line 0056_20190711_155136_2904_EM2040.</ns2:caption></ns2:images><ns2:images><ns2:link>SupportFiles\B.2_MBES_Subbottom_Return_1.png</ns2:link><ns2:caption>Example of subbottom return in near-nadir region of HSL 2904 MBES data as seen in Subset Editor. Example is from line 0056_20190711_155136_2904_EM2040.</ns2:caption></ns2:images><ns2:comments/></ns2:issue></ns2:results><ns2:comments/></ns1:equipmentEffectiveness><ns1:uncertainty><ns2:values><ns2:tideUncertainty><ns2:measured units="meters">0.00</ns2:measured><ns2:tideMethod>ERS via VDATUM</ns2:tideMethod><ns2:zoning units="meters">0.090</ns2:zoning></ns2:tideUncertainty><ns2:soundSpeedUncertainty><ns2:measuredCTD units="meters/second">4</ns2:measuredCTD><ns2:surface units="meters/second">0.2</ns2:surface><ns2:hullID>2903</ns2:hullID><ns2:measuredXBT xsi:nil="true"/><ns2:measuredMVP xsi:nil="true"/></ns2:soundSpeedUncertainty><ns2:soundSpeedUncertainty><ns2:measuredCTD units="meters/second">4</ns2:measuredCTD><ns2:surface units="meters/second">0.2</ns2:surface><ns2:hullID>2904</ns2:hullID><ns2:measuredXBT xsi:nil="true"/><ns2:measuredMVP xsi:nil="true"/></ns2:soundSpeedUncertainty></ns2:values><ns2:discussion>The MBES and SBES bathymetric surfaces' uncertainty layer is compliant with HSSD 2019 uncertainty standards. Over 99.5% of all nodes pass uncertainty standards (Figures 22 and 23).</ns2:discussion><ns2:images><ns2:link>SupportFiles\B.2_MB_VR_TVU.png</ns2:link><ns2:caption>H13298 MBES surface uncertainty standards.</ns2:caption></ns2:images><ns2:images><ns2:link>SupportFiles\B.2_SB_4m_TVU.png</ns2:link><ns2:caption>H13298 SBES surface uncertainty standards.</ns2:caption></ns2:images><ns2:comments/></ns1:uncertainty><ns1:additionalQualityControl><ns2:comments/></ns1:additionalQualityControl></ns1:qualityControl><ns1:dataProcessing><ns1:additionalDataProcessing><ns2:comments/></ns1:additionalDataProcessing><ns1:surfaces><ns1:discussion>Object Detection coverage requirements were met using three methods: 100% Object Detection MBES coverage, 200% Side Scan coverage with concurrent MBES, and 200% SSS coverage with concurrent SBES per the waiver from the Project Manager. The bathymetric grid for SBES data (H13298_SB_4m_MLLW) did not meet density requirements per the HSSD 2019 (Figure 44, 92% of nodes pass density requirements). Upon close inspection of the density layer of the grid, it was found that most of the nodes that fail are located at the beginning and end of lines where sounding density is low (Figure 45, failed nodes are colored red). There are also some failed nodes that occur in the middle of lines that is likely due to a combination of the density of soundings and the 4m gridding method (Figure 45, failed nodes are colored red). The bathymetric grid for MBES data (H13298_MB_VR_MLLW) meets density requirements per the HSSD 2019 (Figure 46).</ns1:discussion><ns1:comments/><ns1:images><ns2:link>SupportFiles\B.5_SB_4m_density.png</ns2:link><ns2:caption>H13298 SBES data density standards.</ns2:caption></ns1:images><ns1:images><ns2:link>SupportFiles\B.5_SBES_Failed_Nodes.png</ns2:link><ns2:caption>Example of SBES nodes that did not meet density requirements.</ns2:caption></ns1:images><ns1:images><ns2:link>SupportFiles\B.5_MB_VR_density.png</ns2:link><ns2:caption>H13298 MBES data density standards.</ns2:caption></ns1:images><ns1:surface><ns2:resolution units="meters">Variable Resolution</ns2:resolution><ns2:surfaceParameter>NOAA_VR</ns2:surfaceParameter><ns2:surfaceName>H13298_MB_VR_MLLW</ns2:surfaceName><ns2:depthRange><ns2:max units="meters">26.4</ns2:max><ns2:min units="meters">2.4</ns2:min></ns2:depthRange><ns2:surfaceType>CARIS VR Surface (CUBE)</ns2:surfaceType><ns2:purpose>Object Detection</ns2:purpose></ns1:surface><ns1:surface><ns2:resolution units="meters">Variable Resolution</ns2:resolution><ns2:surfaceParameter>NOAA_VR</ns2:surfaceParameter><ns2:surfaceName>H13298_MB_VR_MLLW_Final</ns2:surfaceName><ns2:depthRange><ns2:max units="meters">26.4</ns2:max><ns2:min units="meters">2.4</ns2:min></ns2:depthRange><ns2:surfaceType>CARIS VR Surface (CUBE)</ns2:surfaceType><ns2:purpose>Object Detection</ns2:purpose></ns1:surface><ns1:surface><ns2:resolution units="meters">4</ns2:resolution><ns2:surfaceParameter>NOAA_4m</ns2:surfaceParameter><ns2:surfaceName>H13298_SB_4m_MLLW</ns2:surfaceName><ns2:depthRange><ns2:max units="meters">17.995</ns2:max><ns2:min units="meters">2.626</ns2:min></ns2:depthRange><ns2:surfaceType>CARIS Raster Surface (CUBE)</ns2:surfaceType><ns2:purpose>Object Detection</ns2:purpose></ns1:surface><ns1:surface><ns2:resolution units="meters">4</ns2:resolution><ns2:surfaceParameter>NOAA_4m</ns2:surfaceParameter><ns2:surfaceName>H13298_SB_4m_MLLW_Final</ns2:surfaceName><ns2:depthRange><ns2:max units="meters">17.995</ns2:max><ns2:min units="meters">2.626</ns2:min></ns2:depthRange><ns2:surfaceType>CARIS Raster Surface (CUBE)</ns2:surfaceType><ns2:purpose>Object Detection</ns2:purpose></ns1:surface><ns1:surface><ns2:resolution units="meters">1</ns2:resolution><ns2:surfaceParameter>N/A</ns2:surfaceParameter><ns2:surfaceName>H13298_SSSAB_1m_600kHz_1of4</ns2:surfaceName><ns2:depthRange><ns2:max xsi:nil="true"/><ns2:min xsi:nil="true"/></ns2:depthRange><ns2:surfaceType>SSS Mosaic</ns2:surfaceType><ns2:purpose>100% SSS</ns2:purpose></ns1:surface><ns1:surface><ns2:resolution units="meters">1</ns2:resolution><ns2:surfaceParameter>N/A</ns2:surfaceParameter><ns2:surfaceName>H13298_SSSAB_1m_600kHz_2of4</ns2:surfaceName><ns2:depthRange><ns2:max xsi:nil="true"/><ns2:min xsi:nil="true"/></ns2:depthRange><ns2:surfaceType>SSS Mosaic</ns2:surfaceType><ns2:purpose>200% SSS</ns2:purpose></ns1:surface><ns1:surface><ns2:resolution units="meters">1</ns2:resolution><ns2:surfaceParameter>N/A</ns2:surfaceParameter><ns2:surfaceName>H13298_SSSAB_1m_455kHz_3of4</ns2:surfaceName><ns2:depthRange><ns2:max xsi:nil="true"/><ns2:min xsi:nil="true"/></ns2:depthRange><ns2:surfaceType>SSS Mosaic</ns2:surfaceType><ns2:purpose>100% SSS</ns2:purpose></ns1:surface><ns1:surface><ns2:resolution units="meters">1</ns2:resolution><ns2:surfaceParameter>N/A</ns2:surfaceParameter><ns2:surfaceName>H13298_SSSAB_1m_455kHz_4of4</ns2:surfaceName><ns2:depthRange><ns2:max xsi:nil="true"/><ns2:min xsi:nil="true"/></ns2:depthRange><ns2:surfaceType>SSS Mosaic</ns2:surfaceType><ns2:purpose>200% SSS</ns2:purpose></ns1:surface><ns1:surface><ns2:resolution units="meters">1</ns2:resolution><ns2:surfaceParameter>N/A</ns2:surfaceParameter><ns2:surfaceName>H13298_MBAB_1m_2903_300kHz_1of3</ns2:surfaceName><ns2:depthRange><ns2:max xsi:nil="true"/><ns2:min xsi:nil="true"/></ns2:depthRange><ns2:surfaceType>MB Backscatter Mosaic</ns2:surfaceType><ns2:purpose>Object Detection</ns2:purpose></ns1:surface><ns1:surface><ns2:resolution units="meters">1</ns2:resolution><ns2:surfaceParameter>N/A</ns2:surfaceParameter><ns2:surfaceName>H13298_MBAB_1m_2904_300kHz_2of3</ns2:surfaceName><ns2:depthRange><ns2:max xsi:nil="true"/><ns2:min xsi:nil="true"/></ns2:depthRange><ns2:surfaceType>MB Backscatter Mosaic</ns2:surfaceType><ns2:purpose>Object Detection</ns2:purpose></ns1:surface><ns1:surface><ns2:resolution units="meters">1</ns2:resolution><ns2:surfaceParameter>N/A</ns2:surfaceParameter><ns2:surfaceName>H13298_MBAB_1m_2904_400kHz_3of3</ns2:surfaceName><ns2:depthRange><ns2:max xsi:nil="true"/><ns2:min xsi:nil="true"/></ns2:depthRange><ns2:surfaceType>MB Backscatter Mosaic</ns2:surfaceType><ns2:purpose>Object Detection</ns2:purpose></ns1:surface></ns1:surfaces><ns1:drSoftware><ns1:discussion xsi:nil="true"></ns1:discussion><ns1:bathySoftware deviation="false"><ns1:name xsi:nil="true"></ns1:name><ns1:version xsi:nil="true"></ns1:version><ns1:manufacturer xsi:nil="true"></ns1:manufacturer></ns1:bathySoftware><ns1:comments/><ns1:imagerySoftware deviation="false"><ns1:name xsi:nil="true"></ns1:name><ns1:version xsi:nil="true"></ns1:version><ns1:manufacturer xsi:nil="true"></ns1:manufacturer></ns1:imagerySoftware><ns1:featureObjectCatalog>NOAA Profile Version 2019</ns1:featureObjectCatalog></ns1:drSoftware></ns1:dataProcessing><ns1:backscatter><ns2:results acquired="true"><ns2:discussion>All equipment and survey methods were used as detailed in the DAPR. Multibeam echo sounder acoustic backscatter (MBAB) was logged as part of the .all file of the Kongsberg EM2040 systems. Backscatter was processed in QPS Fledermaus GeoCoder Toolbox (FMGT) software, and the exported geotiff's are included in the final processed data package (Figures 38, 39, and 40). There were five holidays identified in the area of 100% MBES coverage (Figure 41). As previously discussed in section B.2, the side scan mount also created interference in MBAB data that can be seen as dark lines on the starboard side of the swath (Figure 42). There are five anomolies in the MBAB data that were caused by blowouts in MBES coverage (Figure 43). </ns2:discussion><ns2:images><ns2:link>SupportFiles\B.4_2903_300kHz_backscatter.png</ns2:link><ns2:caption>HSL 2903's 300kHz multibeam acoustic backscatter at 1m resolution.</ns2:caption></ns2:images><ns2:images><ns2:link>SupportFiles\B.4_2904_300kHz_backscatter.png</ns2:link><ns2:caption>HSL 2904's 300kHz multibeam acoustic backscatter at 1m resolution.</ns2:caption></ns2:images><ns2:images><ns2:link>SupportFiles\B.4_2904_400kHz_backscatter.png</ns2:link><ns2:caption>HSL 2904's 400kHz multibeam acoustic backscatter at 1m resolution.</ns2:caption></ns2:images><ns2:images><ns2:link>SupportFiles\B.4_Backscatter_Holidays.png</ns2:link><ns2:caption>Backscatter holidays in the area of 100% MBES coverage. </ns2:caption></ns2:images><ns2:images><ns2:link>SupportFiles\B.4_Backscatter_SSMount_Interference.png</ns2:link><ns2:caption>Example area or MBAB showing dark lines on starboard side of MBAB swath created by interference from side scan mount. </ns2:caption></ns2:images><ns2:images><ns2:link>SupportFiles\B.4_Backscatter_Blowouts.png</ns2:link><ns2:caption>MBAB anomolies caused by blowouts in MBES coverage. </ns2:caption></ns2:images></ns2:results><ns2:comments/></ns1:backscatter><ns1:echoSoundingCorrections><ns1:corrections><ns2:results deviation="false"><ns2:discussion>All data reduction procedures conform to those detailed in the DAPR.</ns2:discussion></ns2:results><ns2:comments/></ns1:corrections><ns1:additionalIssues><ns2:comments/></ns1:additionalIssues><ns1:calibrations><ns2:results deviation="false"><ns2:discussion>All sounding systems were calibrated as detailed in the DAPR.</ns2:discussion><ns2:calibration xsi:nil="true"/></ns2:results><ns2:comments/></ns1:calibrations></ns1:echoSoundingCorrections><ns1:equipmentAndVessels><ns1:discussion>Refer to the Data Acquisition and Processing Report (DAPR) for a complete description of data acquisition and processing systems, survey vessels, quality control procedures and data processing methods. Additional information to supplement sounding and survey data, and any deviations from the DAPR are discussed in the following sections.</ns1:discussion><ns1:comments/><ns1:vessels><ns1:discussion xsi:nil="true"></ns1:discussion><ns1:comments/><ns1:vessel><ns2:LOA units="meters">8.5</ns2:LOA><ns2:draft units="meters">1.2</ns2:draft><ns2:hullID>2903</ns2:hullID></ns1:vessel><ns1:vessel><ns2:LOA units="meters">8.5</ns2:LOA><ns2:draft units="meters">1.2</ns2:draft><ns2:hullID>2904</ns2:hullID></ns1:vessel></ns1:vessels><ns1:equipment><ns1:discussion>Vessel configurations, equipment operations, data acquisition, and processing were consistent with specifications described in the DAPR.</ns1:discussion><ns1:comments/><ns1:majorSystem><ns2:type>MBES</ns2:type><ns2:model>EM 2040</ns2:model><ns2:manufacturer>Kongsberg Maritime</ns2:manufacturer></ns1:majorSystem><ns1:majorSystem><ns2:type>SSS</ns2:type><ns2:model>4200</ns2:model><ns2:manufacturer>EdgeTech</ns2:manufacturer></ns1:majorSystem><ns1:majorSystem><ns2:type>SSS</ns2:type><ns2:model>System 5000</ns2:model><ns2:manufacturer>Klein Marine Systems</ns2:manufacturer></ns1:majorSystem><ns1:majorSystem><ns2:type>Positioning and Attitude System</ns2:type><ns2:model>POS MV 320 v5</ns2:model><ns2:manufacturer>Applanix</ns2:manufacturer></ns1:majorSystem><ns1:majorSystem><ns2:type>Conductivity, Temperature, and Depth Sensor</ns2:type><ns2:model>SBE 19plus V2</ns2:model><ns2:manufacturer>Sea-Bird Scientific</ns2:manufacturer></ns1:majorSystem><ns1:majorSystem><ns2:type>Lidar System</ns2:type><ns2:model>VLP-16</ns2:model><ns2:manufacturer>Velodyne LiDAR</ns2:manufacturer></ns1:majorSystem><ns1:majorSystem><ns2:type>SBES</ns2:type><ns2:model>Echotrac CV200</ns2:model><ns2:manufacturer>Teledyne Odom Hydrographic</ns2:manufacturer></ns1:majorSystem><ns1:majorSystem><ns2:type>Sound Speed System</ns2:type><ns2:model>SVP 70</ns2:model><ns2:manufacturer>Teledyne RESON</ns2:manufacturer></ns1:majorSystem></ns1:equipment></ns1:equipmentAndVessels></ns1:dataAcquisitionAndProcessing><ns1:approvalSheet><ns1:statements><ns1:adequacyOfSurvey>The survey data meets or exceeds requirements as set forth in the NOS Hydrographic Surveys Specifications and Deliverables, Field Procedures Manual, Letter Instructions, and all HSD Technical Directives. These data are adequate to supersede charted data in their common areas. This survey is complete and no additional work is required with the exception of deficiencies noted in the Descriptive Report.</ns1:adequacyOfSurvey><ns1:supervision>As Chief of Party, field operations for this hydrographic survey were conducted under my direct supervision, with frequent personal checks of progress and adequacy. I have reviewed the attached survey data and reports.</ns1:supervision><ns1:approval>All field sheets, this Descriptive Report, and all accompanying records and data are approved. All records are forwarded for final review and processing to the Processing Branch.</ns1:approval><ns1:additionalInfo xsi:nil="true"></ns1:additionalInfo></ns1:statements><ns1:signingPersonnel><ns2:approverName>CDR Briana W. Hillstrom</ns2:approverName><ns2:approvalDate>2020-05-18</ns2:approvalDate><ns2:approverTitle>Commanding Officer</ns2:approverTitle></ns1:signingPersonnel><ns1:signingPersonnel><ns2:approverName>LT Calandria DeCastro</ns2:approverName><ns2:approvalDate>2020-05-18</ns2:approvalDate><ns2:approverTitle>Operations Officer</ns2:approverTitle></ns1:signingPersonnel><ns1:signingPersonnel><ns2:approverName>Joshua Hiteshew</ns2:approverName><ns2:approvalDate>2020-05-18</ns2:approvalDate><ns2:approverTitle>Chief Hydrographic Survey Technician</ns2:approverTitle></ns1:signingPersonnel><ns1:signingPersonnel><ns2:approverName>Erin Cziraki</ns2:approverName><ns2:approvalDate>2020-05-18</ns2:approvalDate><ns2:approverTitle>Sheet Manager</ns2:approverTitle></ns1:signingPersonnel></ns1:approvalSheet></ns1:descriptiveReport>