<?xml version="1.0" encoding="UTF-8"?><ns1:descriptiveReport xmlns:ns1="http://svn.pydro.noaa.gov/2020/01/DescriptiveReport" xmlns:ns2="http://svn.pydro.noaa.gov/2020/01/AllGlobalTypes" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://svn.pydro.noaa.gov/2020/01/DescriptiveReport http://svn.pydro.noaa.gov/2020/01/DR.xsd"><ns1:verticalAndHorizontalControl><ns1:discussion>In accordance with HSSD Section 2.2, the horizontal datum for this project is NAD83. HSSD Section 2.2 states that the “only exception for the NAD83 datum requirement is that the S-57 Final Feature File (Section 7.3) will be in the WGS84 datum to comply with international S-57 specifications”. As discussed in the DAPR Section C.7, for every feature flag in a MBES GSF file, SABER converts the position from the NAD83 datum to the WGS84 datum to generate the S-57 file and comply with HSSD and IHO requirements. Feature positions meet the precision stated in HSSD Section 7.4 for each respective datum. Depending on geographic reference there may be approximately a 1-meter difference comparing positions between NAD83 and WGS84 datums. Therefore, if the feature overrides from the BAG surface (NAD83) are compared to the Final Feature File S-57 positions (WGS84) it is anticipated that there could be positional differences exceeding those listed in Section 7.4 of the HSSD. Additional information discussing the vertical and horizontal control for this survey can be found in the DAPR.</ns1:discussion><ns1:verticalControl><ns2:VDATUM_or_constantSep used="true"><ns2:discussion>Refer to the DAPR for details regarding the application of VDatum to the MBES data files. No final tide note was provided nor was it required from NOAA Center for Operational Oceanographic Products and Services (CO-OPS).</ns2:discussion><ns2:ellipsoidToChartDatumSepFile><ns2:fileName>OPR-K380-KR-21_NAD83_VDatum_MLLW.cov</ns2:fileName></ns2:ellipsoidToChartDatumSepFile><ns2:methodsUsed>ERS via VDATUM</ns2:methodsUsed><ns2:comments/></ns2:VDATUM_or_constantSep><ns2:standard_or_ERZT used="false" xsi:nil="true"/><ns2:tideStations/><ns2:verticalDatum>Mean Lower Low Water</ns2:verticalDatum><ns2:comments/></ns1:verticalControl><ns1:additionalIssues><ns2:comments/></ns1:additionalIssues><ns1:horizontalControl><ns2:projection>Projected UTM 15</ns2:projection><ns2:DGPS used="false" xsi:nil="true"/><ns2:RTK used="false" xsi:nil="true"/><ns2:WAAS used="false" xsi:nil="true"/><ns2:comments/><ns2:horizontalDatum>North American Datum 1983</ns2:horizontalDatum><ns2:PPP used="true"><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 6th Edition Order 1a specifications were flagged as invalid and therefore were not used in the CUBE depth calculations.</ns2:discussion><ns2:comments/></ns2:PPP><ns2:PPK used="false" xsi:nil="true"/></ns1:horizontalControl></ns1:verticalAndHorizontalControl><ns1:areaSurveyed><ns1:surveyCoverage><ns2:results deviation="false"><ns2:discussion>Leidos chose to achieve the coverage requirement using Complete Coverage, Option B (100% 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:coverageRequirement><ns2:requiredCoverage>Complete Coverage 
(Refer to HSSD Section 5.2.2.3)</ns2:requiredCoverage><ns2:waterDepth>All waters in survey area Sheets 2 through 5</ns2:waterDepth></ns2:coverageRequirement><ns2:comments/></ns1:surveyCoverage><ns1:surveyPurpose><ns2:comments/><ns2:topic><ns2:discussion>This survey covers the general vicinity of the entrance channel to Port Freeport, Texas between the U.S. Coast Guard Station on the northwest of the entrance and Quintana Harbor to the southwest. The survey will wind 4.7 nautical miles south and west, around the Dow Chemical Plant Thumb to the Freeport Channel terminus. The surveyed area extends offshore 11 nautical miles to cover the approach channel, and 18 nautical miles southwest and 8 nautical miles northwest, outside safety fairway, where the AIS traffic deems intensity. Port Freeport, TX is undergoing channel expansion and deepening administered by the U.S Army Corps of Engineers. Freeport will become the deepest port in Texas once the entrance and terminal channels reach the authorized 51-56 feet depth. With the physical position on the Intercoastal Waterway, direct rail and highway connections to major Texas hubs, and the deepened channels, Port Freeport is poised to exceed its current 28th ranking as the U.S. busiest port in tonnage transfer. Several powerful storms impacted the Port Freeport since the offshore vicinity was last surveyed in 2002 and the nearshore vicinity was last surveyed in the 1930s and 1960s. The Office of Coast Survey expects that modern hydrographic techniques will find significant changes to the seabed due to hurricane forces transforming the seafloor. Survey data from this project is intended to supersede all prior survey data in the common area.</ns2:discussion></ns2:topic></ns1:surveyPurpose><ns1:surveyStatistics><ns2:LNM><ns2:totalLNM><ns2:MS_SBES>0</ns2:MS_SBES><ns2:MS_SBES_MBES>0</ns2:MS_SBES_MBES><ns2:XL_lidar>0</ns2:XL_lidar><ns2:MS_SSS>0</ns2:MS_SSS><ns2:MS_SBES_SSS>0</ns2:MS_SBES_SSS><ns2:MS_MBES_SSS>1401.75</ns2:MS_MBES_SSS><ns2:XL_MBES_SBES>65.30</ns2:XL_MBES_SBES><ns2:MS_MBES>0</ns2:MS_MBES><ns2:MS_lidar>0</ns2:MS_lidar><ns2:percentXLLNM>4.66</ns2:percentXLLNM></ns2:totalLNM><ns2:vesselLNM><ns2:vessel><ns2:statistics><ns2:MS_SBES>0</ns2:MS_SBES><ns2:MS_SBES_MBES>0</ns2:MS_SBES_MBES><ns2:XL_lidar>0</ns2:XL_lidar><ns2:MS_SSS>0</ns2:MS_SSS><ns2:MS_SBES_SSS>0</ns2:MS_SBES_SSS><ns2:MS_MBES_SSS>1401.75</ns2:MS_MBES_SSS><ns2:XL_MBES_SBES>65.30</ns2:XL_MBES_SBES><ns2:MS_MBES>0</ns2:MS_MBES><ns2:MS_lidar>0</ns2:MS_lidar></ns2:statistics><ns2:hullID>M/V Atlantic Surveyor</ns2:hullID></ns2:vessel></ns2:vesselLNM></ns2:LNM><ns2:discussion xsi:nil="true"></ns2:discussion><ns2:comments/><ns2:totalSurveyStats><ns2:bottomSamples>8</ns2:bottomSamples><ns2:maritimeBoundaryPoints>0</ns2:maritimeBoundaryPoints><ns2:diveOps>0</ns2:diveOps><ns2:DP>0</ns2:DP><ns2:SNM>56.33</ns2:SNM></ns2:totalSurveyStats><ns2:surveyDates>2021-08-18</ns2:surveyDates><ns2:surveyDates>2021-08-23</ns2:surveyDates><ns2:surveyDates>2021-08-24</ns2:surveyDates><ns2:surveyDates>2021-08-25</ns2:surveyDates><ns2:surveyDates>2021-08-26</ns2:surveyDates><ns2:surveyDates>2021-08-27</ns2:surveyDates><ns2:surveyDates>2021-08-28</ns2:surveyDates><ns2:surveyDates>2021-08-29</ns2:surveyDates><ns2:surveyDates>2021-08-30</ns2:surveyDates><ns2:surveyDates>2021-08-31</ns2:surveyDates><ns2:surveyDates>2021-09-01</ns2:surveyDates><ns2:surveyDates>2021-09-02</ns2:surveyDates><ns2:surveyDates>2021-09-03</ns2:surveyDates><ns2:surveyDates>2021-09-04</ns2:surveyDates><ns2:surveyDates>2021-09-29</ns2:surveyDates><ns2:surveyDates>2021-09-30</ns2:surveyDates><ns2:surveyDates>2021-10-02</ns2:surveyDates><ns2:surveyDates>2021-10-05</ns2:surveyDates></ns1:surveyStatistics><ns1:surveyQuality><ns2:discussion>Leidos warrants only that the survey data acquired by Leidos and delivered to NOAA under Contract 1305M220DNCNJ0056 reflects the state of the sea floor in existence on the day and at the time the survey was conducted.

H13504 was surveyed in accordance with the following documents:
1.	1305M221FNCNJ0270 signed.pdf, received 08 June 2021
2.	Hydrographic Survey Specifications and Deliverables (HSSD), April 2021
3.	OPR-K380-KR-21_PRF_FINAL_05032021.000, received 08 June 2021
4.	OPR-K380-KR-21_CSF_FINAL_05032021.000, received 08 June 2021
5.	OPR-K380-KR-21 Project Brief, held 24 June 2021
6.	OPR-K380-KR-21 and OPR-K380-KR-21 feature guidance follow-up.pdf, 30 July 2021
7.	1305M221FNCNJ0270 - Modification P21001.pdf received 11 August 2021</ns2:discussion><ns2:adequacy>The entire survey is adequate to supersede previous data.</ns2:adequacy><ns2:comments/></ns1:surveyQuality><ns1:coverageGraphic><ns2:coverageGraphicImage><ns2:images><ns2:link>SupportFiles\H13504_Figure_02.png</ns2:link><ns2:caption>Final Bathymetry Coverage for H13504</ns2:caption></ns2:images><ns2:images><ns2:link>SupportFiles\H13504_Figure_03.png</ns2:link><ns2:caption>Final Side Scan Coverage for H13504 (First 100% Coverage)</ns2:caption></ns2:images><ns2:images><ns2:link>SupportFiles\H13504_Figure_04.png</ns2:link><ns2:caption>Final Side Scan Coverage for H13504 (Second 100% Coverage)</ns2:caption></ns2:images></ns2:coverageGraphicImage></ns1:coverageGraphic><ns1:areaDescription><ns2:discussion>H13504 was located 10NM SSW from Freeport, Texas; with southern extents approximately 10.2km offshore continuing north to approximately 10.7km offshore of Freeport, TX (Figure 1). The survey was conducted in accordance with coverage requirements listed in the Project Instructions. </ns2:discussion><ns2:comments/><ns2:limits><ns2:northWest><ns2:longitude hemisphere="W">95.486204</ns2:longitude><ns2:latitude hemisphere="N">28.869833</ns2:latitude></ns2:northWest><ns2:southEast><ns2:longitude hemisphere="W">95.17505</ns2:longitude><ns2:latitude hemisphere="N">28.677908</ns2:latitude></ns2:southEast></ns2:limits><ns2:images><ns2:link>SupportFiles\H13504_Figure_01.png</ns2:link><ns2:caption>H13504 Survey Bounds</ns2:caption></ns2:images></ns1:areaDescription><ns1:surveyLimits><ns2:results deviation="false"><ns2:discussion>Survey limits were acquired in accordance with the requirements in the Project Instructions and the Hydrographic Survey Specifications and Deliverables (HSSD), April 2021.</ns2:discussion></ns2:results><ns2:comments/></ns1:surveyLimits></ns1:areaSurveyed><ns1:metadata><ns1:surveyMetadata><ns2:verifier>Atlantic Hydrographic Branch</ns2:verifier><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 15N, 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:projectType>Basic Hydrographic Survey</ns2:projectType><ns2:acquisition><ns2:units>meters</ns2:units></ns2:acquisition><ns2:equipmentTypes><ns2:imageryEquipment>Multibeam Echo Sounder Backscatter</ns2:imageryEquipment><ns2:imageryEquipment>Side Scan Sonar</ns2:imageryEquipment><ns2:soundingEquipment>Multibeam Echo Sounder</ns2:soundingEquipment></ns2:equipmentTypes><ns2:datesOfSurvey><ns2:end>2021-10-05</ns2:end><ns2:start>2021-08-18</ns2:start></ns2:datesOfSurvey><ns2:timeZone>UTC</ns2:timeZone><ns2:year>2021</ns2:year><ns2:PIDate>2021-05-13</ns2:PIDate><ns2:chiefOfParty>Bridget W. Bernier</ns2:chiefOfParty></ns1:surveyMetadata><ns1:assignment>Contractor</ns1:assignment><ns1:registryMetadata><ns2:sublocality>10NM SSW from Freeport</ns2:sublocality><ns2:sheetID>2</ns2:sheetID><ns2:country>United States</ns2:country><ns2:stateOrTerritory>Texas</ns2:stateOrTerritory><ns2:scale>10000</ns2:scale><ns2:registryInstructions xsi:nil="true"></ns2:registryInstructions><ns2:registryNumber>H13504</ns2:registryNumber></ns1:registryMetadata><ns1:projectMetadata><ns2:name>Port Freeport and Approaches, TX</ns2:name><ns2:number>OPR-K380-KR-21</ns2:number><ns2:fieldUnit>Leidos</ns2:fieldUnit><ns2:generalLocality>Western Gulf of Mexico</ns2:generalLocality></ns1:projectMetadata></ns1:metadata><ns1:approvalSheet><ns1:signingPersonnel><ns2:approverTitle>Data Processing Manager</ns2:approverTitle><ns2:approvalDate>2022-02-07</ns2:approvalDate><ns2:approverName>Bridget W. Bernier</ns2:approverName></ns1:signingPersonnel><ns1:additionalReports><ns2:reportDateSent>2021-11-05</ns2:reportDateSent><ns2:reportName>OPR-K380-KR-21 Final Project Summary Report.pdf</ns2:reportName></ns1:additionalReports><ns1:additionalReports><ns2:reportDateSent>2021-11-22</ns2:reportDateSent><ns2:reportName>OPR-K380-KR-21_ Marine_Species_Awareness_Training_Record.pdf</ns2:reportName></ns1:additionalReports><ns1:additionalReports><ns2:reportDateSent>2021-11-30</ns2:reportDateSent><ns2:reportName>OPR-K380-KR-21_Coast Pilot Review Report.pdf </ns2:reportName></ns1:additionalReports><ns1:additionalReports><ns2:reportDateSent>2022-01-21</ns2:reportDateSent><ns2:reportName>OPR-K380-KR-21_DAPR.pdf</ns2:reportName></ns1:additionalReports><ns1:additionalReports><ns2:reportDateSent>2022-01-21</ns2:reportDateSent><ns2:reportName>H13502_DR.pdf</ns2:reportName></ns1:additionalReports><ns1:additionalReports><ns2:reportDateSent>2022-02-01</ns2:reportDateSent><ns2:reportName>OPR-K380-KR-21_20220201.zip (NCEI Sound Speed Data)</ns2:reportName></ns1:additionalReports><ns1:additionalReports><ns2:reportDateSent>2022-02-03</ns2:reportDateSent><ns2:reportName>OPR-K380-KR-21 Marine Mammal Sighting Forms.pdf</ns2:reportName></ns1:additionalReports><ns1:additionalReports><ns2:reportDateSent>2022-02-07</ns2:reportDateSent><ns2:reportName>H13503_DR.pdf</ns2:reportName></ns1:additionalReports><ns1:statements><ns1:approval>This Descriptive Report and all accompanying records and data are approved. All records are forwarded for final review and processing to the Processing Branch.</ns1:approval><ns1:adequacyOfSurvey>The survey data meets or exceeds requirements as set forth in the Hydrographic Survey Specifications and Deliverables, Project Instructions, and Statement of Work. These data are adequate to supersede charted data in their common areas. This survey is complete and no additional work is required. Previously, or concurrently, submitted deliverables for OPR-K380-KR-21 are provided in the table below.</ns1:adequacyOfSurvey><ns1:additionalInfo xsi:nil="true"></ns1:additionalInfo><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:statements></ns1:approvalSheet><ns1:resultsAndRecommendations><ns1:chartComparison><ns1:channels><ns2:results investigated="Investigated"><ns2:discussion>There were no assigned channels within the H13504 SOW from the final CSF. However, the survey area was coincident to Safety Fairway (FAIRWY) to the Freeport Harbor Channel (ENC US4TX41M and US5POBC), H13502 CUBE depths were in agreement with the charted depths.</ns2:discussion></ns2:results><ns2:comments/></ns1:channels><ns1:methods><ns2:comments/><ns2:topic><ns2:discussion>Chart comparisons were conducted using a combination of SABER and CARIS’ HIPS and SIPS. H13504 data meet data accuracy standards and bottom coverage requirements. Leidos recommends updating the common areas of all charts using data from this survey. Review showed that the H13504 depth data were generally in good agreement (primarily within ±0.5 meters) with charted depths compared to the ENCs listed in Section D.1.1.

Charting recommendations for new features and updates to charted features, are documented in the H13504 S-57 FFF. Additional charted objects are discussed in later sections.

United States Coast Guard (USCG) District 8 LNM publications were reviewed for changes subsequent to the date of the Project Instructions and before the end of survey. The LNM reviewed were from week 23/21 (09 June 2021) until week 04/22 (26 January 2022).</ns2:discussion></ns2:topic></ns1:methods><ns1:chartedFeatures><ns2:results investigated="Investigated"><ns2:discussion>There were numerous assigned charted features in the final CSF (OPR-K380-KR-21_CSF_FINAL_05032021.000) within the SOW of H13504. Per HSSD Section 8.1.4, these charted features are not addressed in this section; refer to the H13504 S-57 FFF (H13504_FFF.000) for all the details and recommendations regarding these features. Within the FFF there are several charted obstructions which Leidos covered and identified within the H13504 data, however the objects are not recommended for charting as obstructions. Rather, they are recommended to be charted as a soundings and contours, as Leidos identified the obstructions to be coral outcroppings. These coral outcroppings were found to cover large areas within H13504, intermittently spanning across the middle of the sheet’s SOW area. In all cases where observed, these coral outcroppings were found to be appropriately captured by CUBE (Figure 15).

In addition to the assigned features within the CSF there were several unassigned objects. The DMPGRD (dumping ground) area charted on ENCs US5POBB, US5POBC, and US4TX41M was a particularly dynamic area and exhibited several piles of sediment (Figure 16). Within this area were multiple objects with heights of approximately 1-meter. While the objects met the criteria to be a feature as defined in the HSSD with a 1-meter height; a feature over-ride was not set on all of these observed features within the DMPGRD as the controlling depths within the surrounding area were from the sediment mounds. The sediment mounds were characterized as natural and Leidos utilized HSSD Section 7.3.2 for determining if a feature over-ride was necessary. CUBE depths honored the sediment mounds within 0.5-meter TVU, therefore no feature over-rides were set on sediment mounds either. The DMPGRD is not retained within the FFF per the investigation requirements from the CSF.

SSS contacts associated with the coral outcropping and within the DMPGRD were retained within the H13504 Side Scan Sonar Contact S-57 file (H13504_SSS_Contacts.000).</ns2:discussion><ns2:images><ns2:link>SupportFiles\H13504_Figure_15.png</ns2:link><ns2:caption>Coral Outcroppings within H13504 MBES Coverage</ns2:caption></ns2:images><ns2:images><ns2:link>SupportFiles\H13504_Figure_16.png</ns2:link><ns2:caption>ENC US4TX41M DMPGRD with H13504 MBES Coverage</ns2:caption></ns2:images></ns2:results><ns2:comments/></ns1:chartedFeatures><ns1:unchartedFeatures><ns2:results investigated="Investigated"><ns2:discussion>See the H13504 S-57 FFF for all the details and recommendations regarding new uncharted features investigated.</ns2:discussion></ns2:results><ns2:comments/></ns1:unchartedFeatures><ns1:shoalAndHazardousFeatures><ns2:results investigated="Investigated"><ns2:discussion>Figure 14 details the Leidos submitted DTON and Anti-DTON reports for H13504. Reports were submitted per HSSD in S-57 format to the Atlantic Hydrographic Branch (AHB). DTON 02 was not forwarded by AHB for immediate charting. Refer to the Project Correspondence for email correspondence related to submitted files.</ns2:discussion><ns2:images><ns2:link>SupportFiles\H13504_Figure_14.png</ns2:link><ns2:caption>DTON Reports</ns2:caption></ns2:images></ns2:results><ns2:comments/></ns1:shoalAndHazardousFeatures><ns1:charts><ns2:comments><ns2:fieldComment><ns2:initials>BWB</ns2:initials><ns2:comment>US5POBB
ENC US5POBB is coincident to H13504. CUBE depths within H13504 agreed well with the charted depths across the contemporaneous survey area; observed depths were primarily within ±0.5 meters of charted depths.

US5POBC
ENC US5POBC is coincident to H13504. CUBE depths within H13504 agreed well with the charted depths across the contemporaneous survey area; observed depths were primarily within ±0.5 meters of charted depths. The charted depth contour generally agreed with depths that fell within the H13504 survey area.

US4TX41M
ENC US4TX41M is coincident to H13504. CUBE depths within H13504 agreed well with the charted depths across the contemporaneous survey area; observed depths were primarily within ±0.5 meters of charted depths. The charted depth contours generally agreed with depths that fell within the H13504 survey area.
</ns2:comment></ns2:fieldComment></ns2:comments><ns2:ENC><ns2:name>US5FPOBB</ns2:name><ns2:updateApplicationDate>2020-06-15</ns2:updateApplicationDate><ns2:issueDate>2022-01-05</ns2:issueDate><ns2:edition>1</ns2:edition><ns2:scale>10000</ns2:scale></ns2:ENC><ns2:ENC><ns2:name>US5FPOBC</ns2:name><ns2:updateApplicationDate>2021-09-27</ns2:updateApplicationDate><ns2:issueDate>2022-01-05</ns2:issueDate><ns2:edition>3</ns2:edition><ns2:scale>10000</ns2:scale></ns2:ENC><ns2:ENC><ns2:name>US4TX41M</ns2:name><ns2:updateApplicationDate>2021-09-27</ns2:updateApplicationDate><ns2:issueDate>2022-01-05</ns2:issueDate><ns2:edition>21</ns2:edition><ns2:scale>80000</ns2:scale></ns2:ENC></ns1:charts></ns1:chartComparison><ns1:additionalResults><ns1:platforms><ns2:results investigated="Investigated"><ns2:discussion>Platforms were assigned from the CSF and are addressed in the H13504 FFF.</ns2:discussion></ns2:results><ns2:comments/></ns1:platforms><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:ENCScaleRecommendation><ns2:results recommended="false"><ns2:discussion>No new ENC recommendations are made for the area surrounding this survey area.</ns2:discussion></ns2:results><ns2:comments/></ns1:ENCScaleRecommendation><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: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 H13504. Bottom characteristics were acquired at the eight locations assigned in the final PRF (OPR-K380-KR-21_PRF_FINAL_05032021.000). Leidos did not modify the bottom sample locations from the locations 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 H13504/Processed/Multimedia.</ns2:discussion></ns2:results><ns2:comments/></ns1:bottomSamples><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: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:submarineFeatures><ns2:results investigated="Investigated"><ns2:discussion>Within the final CSF there were several assigned submarine features (cables and pipelines) for investigation. Within the H13504 data Leidos classified three additional features as exposed pipelines based on their characteristics and size in MBES and SSS data. These pipelines fell outside of charted pipeline or cable areas (Features 04, 07, and 09). Feature 04 was exposed approximately 2-meters above the surrounding depth area which Leidos submitted as DTON 01, following HSSD Section 1.7.2. The remaining two exposed pipelines were approximately 0.3m higher than the surrounding depth area, determined to be non-dangerous and were submitted to NOAA following HSSD Section 1.7.3. 

In accordance with Project Instructions, dated 06 July 2021, exposed or unburied pipelines were to be submitted to Texas General Land Office of Texas (GLO) as a .KMZ file if the data fell within the bounds of the State of Texas Coastal Zone Management Area (CZMA), in place of HSSD Section 1.7.1. The three identified exposed pipelines fell within the TX CZMA and Leidos submitted the .KMZ file to TX GLO; refer to Project Correspondence. 

Charted assigned submarine features were not observed in H13504 to be exposed or unburied, refer to the H13504 S-57 FFF.

The CSF investigation requirements for the submerged cables (CBLSUB) listed “Visually confirm feature object existence. If discrepancy, discuss in DR (see HSSD Section 8.1.4). Do not include feature in FFF.” No sections of charted cables were observed within the H13504 MBES or SSS data therefore the CBLSUB are not discussed within the H13504 S-57 FFF.

SSS contacts associated with the submarine features were retained within the H13504 Side Scan Sonar Contact S-57 file (H13504_SSS_Contacts.000).</ns2:discussion></ns2:results><ns2:comments/></ns1:submarineFeatures><ns1:abnormalSeafloorEnviroCond><ns2:results investigated="Investigated"><ns2:discussion>No abnormal seafloor or environmental conditions, as defined in Section 8.1.4 of the HSSD, exist within this survey area other than those discussed in Section B.2.6.</ns2:discussion></ns2:results><ns2:comments/></ns1:abnormalSeafloorEnviroCond><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:ATONS><ns2:results investigated="Investigated"><ns2:discussion>There was one assigned Aid to Navigation (ATON) within the SOW of H13504 within the final CSF. During survey, this BOYSPP (George Vancouver Liberty Ship Reef Buoy FR-TX-5) was not found to be present. Per HSSD Section 1.6.2.2 as the ATON was listed in the USCG Light List, Leidos submitted an ATON Discrepancy Report to the USCG and forwarded to NOAA. LNM 47/21 (24 November 2021) subsequently noted the ATON as MISSING. This assigned BOYSPP is documented within the H13504 FFF. No other ATONs were present within the bounds of the H13504 survey limits.</ns2:discussion></ns2:results><ns2:comments/></ns1:ATONS></ns1:additionalResults></ns1:resultsAndRecommendations><ns1:dataAcquisitionAndProcessing><ns1:qualityControl><ns1:factorsAffectingSoundings><ns2:results deviation="true"><ns2:issue><ns2:discussion>Within the acquired H13504 MBES and SSS data instances of dense biological interference were observed during discrete areas on various days of survey which required numerous holiday fill lines. Throughout survey acquisition sport fishing and commercial shrimping via trawls were common within the H13504 survey bounds. These observances did not have any significant impact on the final CUBE surface.</ns2:discussion><ns2:title>Biological Interference</ns2:title><ns2:comments/></ns2:issue></ns2:results><ns2:comments/></ns1:factorsAffectingSoundings><ns1:crosslines><ns2:comments/><ns2:topic><ns2:discussion>Multibeam echo sounder crosslines acquired for this survey totaled 4.66% of mainscheme acquisition. The resulting crossline to mainscheme percentage met the requirement to achieve approximately four percent of mainscheme mileage for a Complete Coverage multibeam survey (Section 5.2.4.2 of the HSSD). H13504 requirements were for Complete Coverage, Option B, based on the classifications defined in Section 5.2.2.3 of the HSSD. 

The mainscheme lines were spaced 80 meters apart. Crosslines were generally spaced 2,000 meters apart based on line spacing and linear nautical miles of each survey area. In the field, hydrographers conducted daily comparisons of mainscheme to near nadir crossline data to ensure that no systematic errors were introduced and to identify potential problems with the survey systems. After the application of all correctors and completion of final processing in the office, separate CUBE PFM grids were built at 1-meter resolution. One grid contained the full valid swath (±65° from nadir, Class 2) of mainscheme multibeam and the other included only the near nadir swath (±5° from nadir, Class 1) crossline data. The difference grid was created by subtracting the 1-meter H13504 mainscheme CUBE depths from the 1-meter H13504 crossline CUBE depths. 

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

Section 5.2.4.2 of the HSSD states that the depth difference values are to be within the maximum allowable TVU, which for the range of depths observed in the crossline PFM comparison area (12.868 to 20.082 meters) was calculated to be between 0.527 to 0.564 meters. Comparisons of the final crossline data versus final mainscheme data showed that 99.99% of comparisons were within 0.300 meters or less within the calculated allowable TVU ranges (Figure 6). A single difference exceeded the maximum TVU, 0.608 meters, which was due steep slope. The distribution is spread about zero for all comparisons as presented in Figure 7.</ns2:discussion><ns2:images><ns2:link>SupportFiles\H13504_Figure_06.png</ns2:link><ns2:caption>Tabular Results Crossing Analysis, Crosslines vs. Mainscheme Lines</ns2:caption></ns2:images><ns2:images><ns2:link>SupportFiles\H13504_Figure_07.png</ns2:link><ns2:caption>Plot of Crossing Analysis Crosslines vs. Mainscheme Lines</ns2:caption></ns2:images></ns2:topic></ns1:crosslines><ns1:sonarQCChecks><ns2:results deviation="false"><ns2:discussion>Sonar system quality control checks were conducted as detailed in the DAPR.</ns2:discussion></ns2:results><ns2:comments/></ns1:sonarQCChecks><ns1:soundSpeedMethods><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 routinely conducted by comparing at least two consecutive casts taken with different SSP sensors. 

All individual SSP files are delivered with the H13504 data and are broken out into sub-folders, which correspond to the purpose of each cast. Also, all individual SSP files for H13504 have been concatenated into two separate files based on the purpose of the cast, provided in CARIS format files (.svp), and delivered under (H13504/Processed/SVP/CARIS_SSP) on the delivery drive. In accordance with HSSD Section 8.3.6, SSP files were also converted to NCEI format, as detailed in the DAPR, and provided as a separate delivery to NCEI. Refer to the DAPR for additional details.</ns1:castFrequency><ns1:discussion xsi:nil="true"></ns1:discussion><ns1:comments/></ns1:soundSpeedMethods><ns1:equipmentEffectiveness><ns2:results deviation="false"><ns2:issue><ns2:discussion>There were no conditions or deficiencies that affected equipment operational effectiveness.</ns2:discussion><ns2:title>None Exist</ns2:title><ns2:comments/></ns2:issue></ns2:results><ns2:comments/></ns1:equipmentEffectiveness><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:additionalQualityControl><ns2:issue><ns2:discussion>As stated in Section A.4, H13504 was assigned as Complete Coverage; Leidos chose to achieve the coverage requirement following Option B (100% side scan sonar coverage with concurrent multibeam bathymetry). To achieve this coverage, the SSS was set to 50-meter range scale, and main scheme survey lines were spaced at 80-meters to ensure 100% SSS coverage. Disproval areas were covered with either 100% multibeam coverage or 200% side scan 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. Bathymetric data and side scan sonar imagery were reviewed and bathymetric splits were acquired if deemed necessary per Hydrographer’s discretion, as noted in Section 5.2.2.1 of the HSSD.

A final review of the CUBE Depth surface of the H13504 1-meter PFM showed that there were no holidays as defined for complete coverage surveys in Section 5.2.2.3 of the HSSD. Any remaining three by three unpopulated nodes in the final MBES surfaces were along the outer swath data, outside of the SSS nadir coverage gap, and was fully covered with 100% SSS coverage.

The final H13504 CUBE PFM grid was examined for the number of soundings contributing to the chosen CUBE hypotheses for each node by running SABER’s Frequency Distribution Tool on the Hypothesis Number of Soundings (Hyp. # Soundings) surface. The Hyp. # Soundings surface reports the number of soundings that were used to compute the chosen hypothesis. Analysis was conducted on the Hyp. # Soundings surface from the PFM grid to ensure that the requirements for complete coverage surveys, as specified in HSSD Section 5.2.2.3 were met. Within the final 1-meter PFM grid, 99.20% of all nodes contained five or more soundings.</ns2:discussion><ns2:title>Multibeam Coverage Analysis </ns2:title><ns2:comments/></ns2:issue><ns2:comments/></ns1:additionalQualityControl><ns1:junctions><ns2:discussion>Per the Project Instructions, junction analysis was performed between H13504 and the surveys listed in the table below. Figure 9 shows the general locality of H13504 as it relates to the sheets against which junctions were performed. Analysis of H13504 to H13505 and H13506 will be provided within those respective Descriptive Reports as final analysis and processing efforts for H13505 and H13506 remain on-going. Analysis between H13504 to H13502 and H13503 are discussed below.</ns2:discussion><ns2:junction><ns2:discussion>Junctioning survey H13502 was conducted in 2021 and junctions to the north of H13504. For this analysis the H13502 50-centimeter CUBE depth surface was compared to the H13504 1-meter CUBE depth surface. Junction analysis was conducted on the common area of these two sheets, with an overlapping area of approximately 150-1500 meters. Observed depths within the common area were 17.392 to 147.784 meters which resulted in a calculated allowable TVU range of 0.549 to 0.551 meters. 

The difference grid was generated by subtracting the H13502 data from the H13504 data. Positive values indicate that H13504 depth data were deeper than H13502 depth data. Throughout the common area, H13504 CUBE depths were deeper than H13502 13.12% of the time and were shoaler than H13502 86.39% of the time (Figure 10). The distribution is spread about zero for all comparisons as presented in Figure 11.

100.00% of the comparisons were 0.287 meters or less, within the calculated allowable TVU range.</ns2:discussion><ns2:survey><ns2:relativeLocation>N</ns2:relativeLocation><ns2:year>2021</ns2:year><ns2:registryNumber>H13502</ns2:registryNumber><ns2:fieldUnit>Leidos, Inc.</ns2:fieldUnit><ns2:scale>5000</ns2:scale></ns2:survey><ns2:comments/><ns2:images><ns2:link>SupportFiles\H13504_Figure_10.png</ns2:link><ns2:caption>Tabular Results Junction Analysis H13504 vs. H13502</ns2:caption></ns2:images><ns2:images><ns2:link>SupportFiles\H13504_Figure_11.png</ns2:link><ns2:caption>Plot of Junction Analysis H13504 vs. H13502</ns2:caption></ns2:images></ns2:junction><ns2:junction><ns2:discussion>Junctioning survey H13503 was conducted in 2021 and junctions to the north of H13504. For this analysis the H13503 1-meter CUBE depth surface was compared to the H13504 1-meter CUBE depth surface. Junction analysis was conducted on the common area of these two sheets, with an overlapping area approximately 180-29,490 meters. Observed depths within the common area were 13.861 to 17.744 meters which resulted in a calculated allowable TVU range of 0.531 to 0.551 meters. 

The difference grid was generated by subtracting the H13503 data from the H13504 data. Positive values indicate that H13504 depth data were deeper than H13503 depth data. Throughout the common area, H13504 CUBE depths were deeper than H13503 47.25% of the time and were shoaler than H13503 51.58% of the time (Figure 10). The distribution is well spread about zero for all comparisons as presented in Figure 11.

100.00% of the comparisons were 0.298 meters or less, within the calculated allowable TVU range.</ns2:discussion><ns2:survey><ns2:relativeLocation>N</ns2:relativeLocation><ns2:year>2021</ns2:year><ns2:registryNumber>H13503</ns2:registryNumber><ns2:fieldUnit>Leidos, Inc.</ns2:fieldUnit><ns2:scale>5000</ns2:scale></ns2:survey><ns2:comments/><ns2:images><ns2:link>SupportFiles\H13504_Figure_12.png</ns2:link><ns2:caption>Tabular Results Junction Analysis H13504 vs. H13503</ns2:caption></ns2:images><ns2:images><ns2:link>SupportFiles\H13504_Figure_13.png</ns2:link><ns2:caption>Plot of Junction Analysis H13504 vs. H13503</ns2:caption></ns2:images></ns2:junction><ns2:comments/><ns2:images><ns2:link>SupportFiles\H13504_Figure_09.png</ns2:link><ns2:caption>General Locality of H13504 with Junctioning Surveys</ns2:caption></ns2:images></ns1:junctions><ns1:uncertainty><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 6th Edition, Order 1a were flagged as invalid during the uncertainty attribution.

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

Per HSSD Section 5.2.2.2, H13504 depth data fell within a single grid resolution at 1-meter. 

The final H13504 1-meter PFM CUBE surface contained final vertical uncertainties that ranged from 0.210 meters to 1.029 meters. The IHO Order 1a maximum allowable vertical uncertainty was calculated to range between 0.520 to 0.569 meters, based on the minimum CUBE depth (10.959 meters) and maximum CUBE depth (20.939 meters). Results from the SABER Check PFM Uncertainty function identified that there were 324 nodes in the final H13504 1-meter PFM CUBE surface with final vertical uncertainties that exceeded IHO Order 1a allowable vertical uncertainty. These nodes were all associated with features, particularly within the bounds of the charted fish haven area, and in areas of steep slopes along the coral outcroppings. The SABER Frequency Distribution Tool was also used to review the Hyp. Final Uncertainty surface within the final H13504 1-meter PFM grid. Results showed that 99.99% of all nodes had final uncertainties less than or equal to maximum allowable vertical uncertainty of 0.360 meters, which was below the allowable calculated TVU range.</ns2:discussion><ns2:values><ns2:soundSpeedUncertainty><ns2:measuredXBT units="meters/second">1.0</ns2:measuredXBT><ns2:measuredCTD units="meters/second">1.0</ns2:measuredCTD><ns2:measuredMVP units="meters/second">1.0</ns2:measuredMVP><ns2:surface units="meters/second">1.0</ns2:surface><ns2:hullID>M/V Atlantic Surveyor</ns2:hullID></ns2:soundSpeedUncertainty><ns2:tideUncertainty><ns2:zoning units="meters">0.20</ns2:zoning><ns2:tideMethod>ERS via VDATUM</ns2:tideMethod><ns2:measured units="meters">0.093</ns2:measured></ns2:tideUncertainty></ns2:values><ns2:comments/><ns2:images><ns2:link>SupportFiles\H13504_Figure_08.png</ns2:link><ns2:caption>Example Nodes in H13504 1-meter CUBE surface with Uncertainty Exceeding (Blue Symbols) IHO Along Slopes</ns2:caption></ns2:images></ns1:uncertainty></ns1:qualityControl><ns1:dataProcessing><ns1:surfaces><ns1:discussion>Complete Coverage Section 5.2.2.3 of the HSSD requires 1-meter node resolution for depths ranging from 0 meters to 20 meters. Leidos generated the CUBE PFM grid for H13504 at 1-meter resolution. 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 H13504 1-meter PFM grid were from 10.959 meters (35.955 feet; 0.223 meters Total Vertical Uncertainty [TVU]) to 20.939 meters (68.697 feet; 0.210 meters TVU). In the northeast corner of the H13504 survey limits there is an area of approximately 392 meters by 2,736 meters which has resulting CUBE depths deeper than 20 meters. HSSD requirements for node resolution were met at 1-meter node resolution within these depths and therefore these depths deeper than the HSSD 1-meter resolution are retained within the delivered Final 1-meter surface.

The final gridded bathymetry data are delivered as a Bathymetric Attributed Grid (BAG). The BAG file was exported from the CUBE PFM grid as detailed in the DAPR.
</ns1:discussion><ns1:comments/><ns1:surface><ns2:purpose>Complete Coverage, Option B (100% side scan sonar coverage with concurrent multibeam)</ns2:purpose><ns2:depthRange><ns2:min units="meters">10.959</ns2:min><ns2:max units="meters">20.939</ns2:max></ns2:depthRange><ns2:surfaceName>H13504_MB_1m_MLLW_Final</ns2:surfaceName><ns2:surfaceType>BAG</ns2:surfaceType><ns2:resolution units="meters">1</ns2:resolution><ns2:surfaceParameter>N/A</ns2:surfaceParameter></ns1:surface><ns1:surface><ns2:purpose>First 100% SSS</ns2:purpose><ns2:depthRange><ns2:min units="meters">0</ns2:min><ns2:max units="meters">0</ns2:max></ns2:depthRange><ns2:surfaceName>H13504_SSSAB_1m_400kHz_1of1</ns2:surfaceName><ns2:surfaceType>SSS Mosaic (.tif)</ns2:surfaceType><ns2:resolution units="meters">1</ns2:resolution><ns2:surfaceParameter>N/A</ns2:surfaceParameter></ns1:surface><ns1:surface><ns2:purpose>Second 100% SSS (Disproval coverage)</ns2:purpose><ns2:depthRange><ns2:min units="meters">0</ns2:min><ns2:max units="meters">0</ns2:max></ns2:depthRange><ns2:surfaceName>H13504_SSSAB_1m_400kHz_2of2</ns2:surfaceName><ns2:surfaceType>SSS Mosaic (.tif)</ns2:surfaceType><ns2:resolution units="meters">1</ns2:resolution><ns2:surfaceParameter>N/A</ns2:surfaceParameter></ns1:surface></ns1:surfaces><ns1:additionalDataProcessing><ns2:comments/></ns1:additionalDataProcessing><ns1:drSoftware><ns1:featureObjectCatalog>NOAA Profile Version 2021</ns1:featureObjectCatalog><ns1:bathySoftware deviation="true"><ns1:manufacturer>Leidos</ns1:manufacturer><ns1:version>5.4.1.5.5</ns1:version><ns1:name>SABER</ns1:name></ns1:bathySoftware><ns1:imagerySoftware deviation="true"><ns1:manufacturer>Leidos</ns1:manufacturer><ns1:version>5.4.1.5.5</ns1:version><ns1:name>SABER</ns1:name></ns1:imagerySoftware><ns1:discussion>The primary data processing software used for both bathymetry and imagery was SABER. </ns1:discussion><ns1:comments/></ns1:drSoftware></ns1:dataProcessing><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. Multibeam files associated with calibration were listed within the OPR-K380-KR-21 DAPR; the DAPR and calibration data were previously delivered with H13502.</ns2:discussion><ns2:calibration xsi:nil="true"/></ns2:results><ns2:comments/></ns1:calibrations></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 Complete Coverage, Option B (100% side scan sonar coverage with concurrent multibeam). 

Leidos generated two separate coverage mosaics at 1-meter cell size resolution as specified in Section 8.2.1 of the HSSD (See section B.2.9 for additional information). The first 100% and second 100% coverage mosaics were independently reviewed using tools in SABER to verify data quality and swath coverage. The SABER Gapchecker routine was used to flag data gaps within each of the 100% SSS coverage mosaics. Additionally, the entirety of each SSS surface was visually scanned for holidays at various points during the data processing effort. Additional survey lines were run to fill any holidays that were detected. 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-K380-KR-21 and therefore no additional processing was performed by Leidos and no additional products were produced.</ns2:discussion></ns2:results><ns2:comments/></ns1:backscatter><ns1:equipmentAndVessels><ns1:discussion>Leidos used their ISS-2000 software on a Windows platform to acquire these survey data. Survey planning and data analysis were conducted using the Leidos SABER software on Linux platforms. Side scan sonar (SSS) data were collected on a Windows platform using Klein’s SonarPro software. Subsequent processing and review of the SSS data, including the generation of coverage mosaics, were accomplished using SABER.

A detailed description of the systems and vessels used to acquire and process these data is included in the Data Acquisition and Processing Report (DAPR) for OPR-K380-KR-21, delivered previously with H13502. There were no variations from the equipment configuration described in the DAPR.</ns1:discussion><ns1:equipment><ns1:majorSystem><ns2:model>SeaBat T50-R</ns2:model><ns2:manufacturer>Teledyne RESON</ns2:manufacturer><ns2:type>MBES</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:model>System 4000</ns2:model><ns2:manufacturer>Klein Marine Systems</ns2:manufacturer><ns2:type>SSS</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:model>POS MV 320 v5</ns2:model><ns2:manufacturer>Applanix</ns2:manufacturer><ns2:type>Positioning and Attitude System</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:model>MVP30</ns2:model><ns2:manufacturer>AML Oceanographic</ns2:manufacturer><ns2:type>Sound Speed System</ns2:type></ns1:majorSystem><ns1:discussion>A detailed description of the equipment installed is included in the DAPR.</ns1:discussion><ns1:comments/></ns1:equipment><ns1:vessels><ns1:vessel><ns2:draft units="feet">9</ns2:draft><ns2:LOA units="feet">110</ns2:LOA><ns2:hullID>M/V Atlantic Surveyor</ns2:hullID></ns1:vessel><ns1:images><ns2:link>SupportFiles\H13504_Figure_05.png</ns2:link><ns2:caption>M/V Atlantic Surveyor</ns2:caption></ns1:images><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 4000), 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:comments/></ns1:vessels><ns1:comments/></ns1:equipmentAndVessels></ns1:dataAcquisitionAndProcessing></ns1:descriptiveReport>