<?xml version="1.0" encoding="UTF-8"?><ns1:descriptiveReport xmlns:ns1="http://svn.pydro.noaa.gov/2018/01/DescriptiveReport" xmlns:ns2="http://svn.pydro.noaa.gov/2018/01/AllGlobalTypes" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://svn.pydro.noaa.gov/2018/01/DescriptiveReport http://svn.pydro.noaa.gov/2018/01/DR.xsd"><ns1:verticalAndHorizontalControl><ns1:additionalIssues><ns2:comments/></ns1:additionalIssues><ns1:horizontalControl><ns2:WAAS used="false" xsi:nil="true"/><ns2:RTK used="false" xsi:nil="true"/><ns2:DGPS used="true"><ns2:discussion>Correctors from the U.S. Coast Guard Differential GPS (DGPS) station in English Turn, LA were utilized by the secondary GPS, a Trimble MS750, used as a &quot;position integrity&quot; alarm. </ns2:discussion><ns2:USCGStations><ns2:name>English Turn, LA</ns2:name></ns2:USCGStations><ns2:comments/></ns2:DGPS><ns2:comments/><ns2:projection>UTM Zone 15 North</ns2:projection><ns2:PPK used="true"><ns2:discussion>Application of the Applanix POSPac Smart Base process is described in detail in the project HVCR.</ns2:discussion><ns2:comments/><ns2:methodsUsed>Smart Base</ns2:methodsUsed><ns2:baseStations><ns2:CORSStations><ns2:stationID>CALC</ns2:stationID><ns2:HVCRSiteID>Calcasieu Pass</ns2:HVCRSiteID></ns2:CORSStations><ns2:CORSStations><ns2:stationID>DEV1</ns2:stationID><ns2:HVCRSiteID>Eugene Island 337</ns2:HVCRSiteID></ns2:CORSStations><ns2:CORSStations><ns2:stationID>TONY</ns2:stationID><ns2:HVCRSiteID>Abdalla Hall ULL</ns2:HVCRSiteID></ns2:CORSStations><ns2:CORSStations><ns2:stationID>FSHS</ns2:stationID><ns2:HVCRSiteID>Franklin High Sch</ns2:HVCRSiteID></ns2:CORSStations><ns2:CORSStations><ns2:stationID>AMER</ns2:stationID><ns2:HVCRSiteID>Amerada Pass</ns2:HVCRSiteID></ns2:CORSStations><ns2:CORSStations><ns2:stationID>LMCN</ns2:stationID><ns2:HVCRSiteID>Lumcon</ns2:HVCRSiteID></ns2:CORSStations><ns2:CORSStations><ns2:stationID>HOUM</ns2:stationID><ns2:HVCRSiteID>Houma</ns2:HVCRSiteID></ns2:CORSStations><ns2:userInstalledStations><ns2:stationID>OSFL</ns2:stationID><ns2:HVCRSiteID>OSI Freshwater Lock</ns2:HVCRSiteID></ns2:userInstalledStations></ns2:baseStations></ns2:PPK><ns2:PPP used="false" xsi:nil="true"/><ns2:horizontalDatum>North American Datum 1983</ns2:horizontalDatum></ns1:horizontalControl><ns1:discussion>Additional information discussing the vertical or horizontal control for this survey can be found in the accompanying Horizontal and Vertical Control Report (HVCR) for Project OPR-K354-KR-18.</ns1:discussion><ns1:verticalControl><ns2:verticalDatum>Mean Lower Low Water</ns2:verticalDatum><ns2:tideStations/><ns2:comments/><ns2:VDATUM_or_constantSep used="true"><ns2:discussion xsi:nil="true"></ns2:discussion><ns2:comments/><ns2:methodsUsed>ERS via VDATUM</ns2:methodsUsed><ns2:ellipsoidToChartDatumSepFile><ns2:fileName>OPR-K354-KR-2018_NAD83-MLLW_xGeoid17B.csar</ns2:fileName></ns2:ellipsoidToChartDatumSepFile></ns2:VDATUM_or_constantSep><ns2:standard_or_ERZT used="false" xsi:nil="true"/></ns1:verticalControl></ns1:verticalAndHorizontalControl><ns1:resultsAndRecommendations><ns1:additionalResults><ns1:ATONS><ns2:results investigated="None Exist"><ns2:discussion>No Aids to Navigation (ATONs) exist for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:ATONS><ns1:submarineFeatures><ns2:results investigated="Investigated"><ns2:discussion>As discussed above, 17 charted pipelines are located within Survey H13200.  The majority of the charted pipelines were not visible in the SSS or MBES data.

In addition to the ENC and the CSF, pipeline data from the Bureau of Ocean Energy Management (BOEM) were reviewed prior to field operations to identify any potential uncharted BOEM pipelines in the survey area. Three (3) BOEM pipelines are not represented on the chart.  All charted pipelines have a BOEM pipeline counterpart.  Uncharted BOEM pipelines are displayed in Figure 15.

The BOEM pipeline data (last updated on December 3, 2018) were obtained as a shape file &quot;ppl_arcs.shp&quot; from the BOEM website (https://www.data.boem.gov/Main/Mapping.aspx) and re-projected as a .DXF file “BOEM_Pipelines_UTM_15N_NAD83_Meters.dxf.”  These files are included with the digital deliverables for Survey H13200.</ns2:discussion><ns2:images><ns2:caption>BOEM-defined pipelines that are not charted are highlighted in yellow.  Survey H13200 survey boundary limits are shown in black.</ns2:caption><ns2:link>file:///N:/Reports/DRs/H13200/H13200_BOEM_Pipeline_Analysis.jpg</ns2:link></ns2:images></ns2:results><ns2:comments/></ns1:submarineFeatures><ns1:overheadFeatures><ns2:results investigated="None Exist"><ns2:discussion>No overhead features exist for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:overheadFeatures><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:insetRecommendation><ns2:results recommended="false"><ns2:discussion>No new insets are recommended for this area.</ns2:discussion></ns2:results><ns2:comments/></ns1:insetRecommendation><ns1:shoreline><ns2:results investigated="None Exist"><ns2:discussion>Shoreline was not assigned in the Hydrographic Survey Project Instructions or Statement of Work.</ns2:discussion></ns2:results><ns2:comments/></ns1:shoreline><ns1:newSurveyRecommendation><ns2:results recommended="false"><ns2:discussion>No new surveys or further investigations are recommended for this area.</ns2:discussion></ns2:results><ns2:comments/></ns1:newSurveyRecommendation><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: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:priorSurveys><ns2:results investigated="Exist - Not Investigated"><ns2:discussion>Prior survey comparisons exist for this survey, but with the exception of the assigned junction surveys, prior data were not investigated.</ns2:discussion></ns2:results><ns2:comments/></ns1:priorSurveys><ns1:otherResults><ns2:comments/><ns2:issue><ns2:discussion>Per direction in Section 1.5 of the HSSD, all personnel aboard the survey vessel used during Project OPR-K354-KR-18 were trained as Marine Mammal Observers prior to commencement of the survey.  Training consisted of each surveyor and vessel crew member watching the US Navy video referenced in the HSSD.

As noted multiple times in the survey acquisition log, large, mobile water column sonar targets (assumed to be dolphins) were ensonified by either the MBES or the SSS.  The dolphin-assumption is based on both the size and behavior of the sonar targets.  Often times these observations did not coincide with a visual (above water) sighting.  Visual observations, when noted, were recorded on NOAA/NMFS,AFSC/NMML Form 11US (POP) which is included as Appendix L of the HSSD.

Completed digital 11US (POP) forms were compiled and transmitted along with the Project's digital marine mammal training record to pop.information@noaa.gov and ocs.ecc@noaa.gov with a CC to the Project's COR, Starla Robinson. These records are also included in Descriptive Report Appendix II.</ns2:discussion><ns2:comments/><ns2:title>Marine Mammal Observations</ns2:title></ns2:issue><ns2:issue><ns2:discussion>In reference to the OPR-K354-KR-18 survey area the Coast Pilot Report, included with the April 4, 2018 Final Data Package, states that, &quot;there is one paragraph in Coast Pilot 5, chapter 9, that describes Trinity Shoal (paragraph 301).  There are no details on the surrounding area either.  The paragraph appears to be accurate to Chart 11349 and does not need an update.&quot;  The survey area considered in the Coast Pilot Report does not exactly match the area ultimately surveyed (the assigned survey area expanded after issue of the April 4, 2018 Final Data Package).  However, the Report's &quot;no updates needed&quot; statement and the lack of other investigation requirements still applies to the area actually surveyed.  The Hydrographic Survey Project Instructions contained only general guidance regarding the Coast Pilot.  Therefore, in lieu of targeted responses to an assigned Coast Pilot Field Report, OSI conducted a general review of relevant Coast Pilot excerpts.  Specifically, pertinent paragraphs from the following Coast Pilot section were considered: Coast Pilot 5 - 46th Edition, 2018 updated through 21-October-2018, Mississippi River to Sabine Pass.

Within the Coast Pilot Edition mentioned above there is only one specific, detailed, relevant entry concerning the assigned survey area.  Most entries are of a general nature and are not refutable based on the observations of the OSI field team.  Regarding “areas frequently transited and facilities utilized during in-ports” (as mentioned in the HSSD Section 8.1.3) Coast Pilot entries are somewhat more relevant.  However, there are only a few Coast Pilot entries that this document will attempt to address as most entries are not relevant to the &quot;areas frequently transited by the survey vessel and facilities utilized during in-ports.&quot;

OSI's Coast Pilot Review Report and the original Coast Pilot Report, mentioned above, were transmitted to ocs.nbd@noaa.gov and coast.pilot@noaa.gov with a CC to the Project's COR, Starla Robinson.  These records are also included in Descriptive Report Appendix II.</ns2:discussion><ns2:comments/><ns2:title>Coast Pilot Review</ns2:title></ns2:issue></ns1:otherResults><ns1:platforms><ns2:results investigated="Investigated"><ns2:discussion>Of the 10 platforms assigned for investigation for Survey H13200, only 1 platform was found to be present.  This platform is charted on the ENC and was assigned for investigation in the CSF; however, because its surveyed position was greater than 10m from the CSF position, it is recommended for deletion and a new platform is included in the FFF at the surveyed position.  The remaining 9 platforms were disproved and are recommended for deletion.

In addition to the ENC and the CSF, BOEM platform data were reviewed prior to field operations to identify any potential uncharted BOEM platforms in the survey area.  There were 17 BOEM platforms in the data set.  All BOEM platforms coincide with either an assigned BSSE Wellhead, a charted pipe/platform, or an uncharted BOEM-defined pipeline.  10 BOEM platforms coincide with charted, CSF platform positions (including the 1 platform that was found in the survey).

The BOEM platform data (last updated on December 3, 2018) were obtained as a shape file &quot;platforms.shp&quot; from the BOEM website (https://www.data.boem.gov/Main/Mapping.aspx) and re-projected as a .DXF file “BOEM_Platforms_UTM_15N_NAD83_Meters.dxf.”  These files are included with the digital deliverables for Survey H13200.

There were no platform related Local Notice to Mariners or Notice to Mariners notifications within Survey H13200 from March 21, 2018 to December 20, 2018.</ns2:discussion></ns2:results><ns2:comments/></ns1:platforms></ns1:additionalResults><ns1:chartComparison><ns1:bottomSamples><ns2:results investigated="Investigated"><ns2:discussion>Nine (9) bottom samples were acquired in close proximity to the recommended positions included in the PRF provided with the OPR-K354-KR-18 Project Instructions.  A sediment sampler was deployed from a davit to acquire the requisite sample.  Bottom sample locations were logged in a target file in HYPACK SURVEY.  Once the sample was on deck, it was photographed and classified based on the criteria outlined in Appendix H, Bottom Classification, in the HSSD.  Sediment within Survey H13200 was primarily found to be soft mud with fine sand, with some samples also containing stiff mud or broken shells. </ns2:discussion></ns2:results><ns2:comments/></ns1:bottomSamples><ns1:channels><ns2:results investigated="None Exist"><ns2:discussion>No channels exist for this survey.  There are no designated anchorages, precautionary areas, safety fairways, traffic separation schemes, pilot boarding areas, or channel and range lines within the survey limits.</ns2:discussion></ns2:results><ns2:comments/></ns1:channels><ns1:charts><ns2:ENC><ns2:discussion>An overview of the areas of change between charted depths and H13200 surveyed soundings is shown in Figure 13. The figure displays a difference surface made by subtracting a 10m resolution depth surface generated from the H13200 MBES data from a  depth surface interpolated from the charted ENC soundings within the project area. Regions of shoaling are represented by positive depth differences (warm colors) and regions of deepening are represented by negative depth differences (cool colors).  As shown by the coloring in Figure 13 there has been a deepening trend throughout most of Survey H13200, with the areas of greatest change in the southern part of the sheet.

Figure 14 compares US4LA15M ENC contours to H13200 surveyed contours generated from the displayed generalized tinned surface.  As shown, the 30-foot contour that runs across the southern part of Survey H13200 has shifted northwards along its entire length and should be redrawn based on recently surveyed soundings. </ns2:discussion><ns2:chart><ns2:edition>30</ns2:edition><ns2:updateApplicationDate>2018-12-20</ns2:updateApplicationDate><ns2:name>US4LA15M</ns2:name><ns2:scale>80000</ns2:scale><ns2:issueDate>2018-12-12</ns2:issueDate><ns2:preliminary>false</ns2:preliminary></ns2:chart><ns2:images><ns2:caption>A depth difference surface overlaid on RNC 11349 provides an overview of the areas of change between charted depths and H13200 surveyed soundings.</ns2:caption><ns2:link>file:///N:/Reports/DRs/H13200/H13200_Difference_Map.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>A colorized depth surface provides an overview of the change in contours from ENC US4LA15M to the surveyed data.  RNC 11349 is displayed as an overlay.</ns2:caption><ns2:link>file:///N:/Reports/DRs/H13200/H13200_Chart-Comparison.jpg</ns2:link></ns2:images><ns2:comments/></ns2:ENC><ns2:comments/></ns1:charts><ns1:unchartedFeatures><ns2:results investigated="Investigated"><ns2:discussion> In general there were very few new features surveyed in H13200.  Of the relatively few SSS contacts chosen, most were either fish (chosen independently of the mass fish targeting scheme described in the DAPR) or features of insignificant height.

A 0.9m tall feature was surveyed approximately 125m to the east-southeast of an assigned BSSE Wellhead.  The wellhead was disproved within a search area defined by a 50m radius.  While this feature is not navigationally significant, it is possible that it is the assigned wellhead. For this reason, a designated sounding was created from the least depth of this feature (Figure 15).</ns2:discussion><ns2:images><ns2:caption>A 0.9m tall feature is represented in CARIS HIPS Subset Editor 3D with the soundings colored by depth.</ns2:caption><ns2:link>file:///N:/Reports/DRs/H13200/H13200_29-17-56.72N_91-59-19.98W_5-001_OBSTN.JPG</ns2:link></ns2:images></ns2:results><ns2:comments/></ns1:unchartedFeatures><ns1:maritimeBoundary><ns2:results investigated="None Exist"><ns2:discussion>No Maritime Boundary Points were assigned for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:maritimeBoundary><ns1:methods><ns2:discussion>Chart comparisons were performed in CARIS HIPS/SIPS using finalized CUBE surfaces, contours and selected soundings. The latest edition of the NOAA NOS Electronic Nautical Chart (ENC) was downloaded from the NOAA Office of Coast Survey website (http://www.nauticalcharts.noaa.gov/) regularly during survey operations, and after the survey was completed for final comparisons. The ENC used for final comparison was updated with Notice to Mariners data through December 20, 2018 and is submitted with the survey deliverables.

Local Notices to Mariners and Notices to Mariners from March 21, 2018 to December 20, 2018 were reviewed in conjunction with the chart comparison.

The chart comparisons documented below will discuss general seafloor changes, shoaling and deepening trends. All new or charted features identified, updated or disproved within Survey H13200 were addressed and attributed in the S-57 Final Feature File (FFF). For more information on the methodology that was used to build the FFF see Section B.2.5 Feature Verification in the DAPR.</ns2:discussion><ns2:comments/></ns1:methods><ns1:chartedFeatures><ns2:results investigated="Investigated"><ns2:discussion>The Project Instructions' guidance on Shoreline and Nearshore Features states, &quot;Submit a Final Feature File in accordance with HSSD Section 7.  Contact the COR if there are any questions regarding feature assignments and feature management.  All features with attribute ‘asgnmnt’ populated with ‘Assigned’ shall be addressed in accordance with Chapter 7 of the HSSD.  Investigation requirements for all assigned features will be provided in the investigation requirement attribute ‘invreq.’  For the purposes of disproval, charted features labeled with a &quot;PA&quot; will have a search radius of 160 meters, charted features labeled with a &quot;PD&quot; will have a search radius of 240 meters, and other features without a position qualifier will have a search radius of 80 meters.  With respect to wellheads, reference HSSD Chapter 7.5.1.&quot;  The disproval area for wellheads given in the referenced HSSD chapter is a 50m search radius.

Guidance on attribution of charted and CSF-assigned features varies between NOS-NOAA documents pertaining to this survey.  For example, guidance on New/Delete vs. Update attribution is quite detailed in the HSSD Section 7.5.2 which lists numerous attribution change thresholds.  In contrast, the CSF investigation requirements for platforms states, &quot;If feature exists, include in FFF with descrp=retain. If feature is not visible, conduct a feature disproval (Section 7.3.4).&quot;  The addition of uncharted BSSE Wellheads in the CSF (which were often closer to a surveyed platform than the CSF-defined position of the platform) creates further uncertainty on how to attribute certain features.  Given the ambiguity in directives, OSI consulted with the COR for clarification via e-mail on December 6, 2017.  The COR's December 11, 2017 response follows: &quot;Include both the significant wellheads and platform features in the FFF, and reposition any platform that deviates greater than 10 meters from the center point of the corresponding charted feature, based on the Page 97 of the HSSD.  These are all delete/add for the charted platforms.&quot;  A record of this correspondence is included in DR Appendix II.

Within the bounds of Survey H13200, 63 features were assigned for investigation within the CSF: 2 wrecks, 10 platforms, 17 pipeline sections, and 34 obstructions.

Of the 2 assigned wrecks, both were disproved with 200% SSS and partial MBES coverage within the feature-specific search radii.

See DR Section D.2.6 Platforms for information regarding the verification or disproval of the charted platforms.

Of the 34 obstructions assigned for investigation all but 1 are BSSE Wellheads.  The non-BSSE Wellhead assigned obstruction is a non-specific obstruction and was not attributed with a known depth. This obstruction was disproved with 200% SSS and partial MBES coverage.  All 33 BSSE Wellhead obstructions are recommended for deletion.  One (1) BSSE Wellhead obstruction was coincident with a verified and charted platform, but no evidence of a wellhead aside from the verified platform was found within the disproval area.  Each of the remaining 32 BSSE Wellhead obstructions were disproved with 200% SSS and partial MBES or with complete MBES coverage.

Seventeen (17) pipeline features were assigned for investigation in the CSF.  Many of the pipelines, as packaged and assigned in the CSF, extend outside the bounds of the H13200 survey area and were not investigated beyond the survey limits.  During preliminary data processing there were numerous pipeline or potential pipeline detections identified in Survey H13200.  Many of these detections are duplicate detections from a single feature imaged on one or more adjacent tracklines; discounting the duplicate detections leaves 9 unique potential pipeline features.  A number of these potential detections were later deemed to be something other than an exposed pipeline, e.g. a water column dolphin or a low-relief escarpment.  Two(2) pipeline features were confirmed.  All pipeline detections are less than 1.0m above the seafloor, and therefore, are not deemed DTONs.  The valid pipeline detections, as interpreted during late-stage processing, were forwarded to the COR via email on November 16, 2018 according to guidance in Section 1.7 of the HSSD regarding Non-DTON Seeps and Pipelines.  No &quot;seeps&quot; were detected in Survey H13200.

Prior to 2017, exposed pipes and seeps were handled as DTONs and therefore were appended to the FFF.  The 2017 HSSD includes a new category of feature, &quot;non-DTON seeps and pipes.&quot;  However, the 2017 HSSD does not mention whether or not to include these non-DTON features in the FFF.  The HSSD only addresses undetected charted pipelines and recommends that a non-detected pipeline should be attributed &quot;Retain.&quot;  In a December 11, 2017 e-mail to the COR, OSI inquired about how to treat exposed, non-DTON pipes and seeps in the FFF.  The COR's December 12, 2017 response follows, &quot;The current requirement of the &quot;Non-DTON Seep and Pipeline Report&quot; is a separate deliverable from the FFF.  Your historic method of including the pipeline segments in the FFF is good.  How you manage the other features is up to your discretion. The features that are not cartographically significant they will be ignored in the FFF.&quot;  Given this latitude in how to treat the non-DTON seeps and pipes, OSI chose to include them in the FFF as discrete features.</ns2:discussion></ns2:results><ns2:comments/></ns1:chartedFeatures><ns1:shoalAndHazardousFeatures><ns2:results investigated="Investigated"><ns2:discussion>The methods employed in conducting the Shoal and Hazardous Features analysis are the same as described above for the Chart Comparison discussion.

In general there was more deepening than shoaling evident in Survey H13200, and no new discrete dangerous shoals were surveyed.

No DTONs were generated as a result of this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:shoalAndHazardousFeatures></ns1:chartComparison></ns1:resultsAndRecommendations><ns1:metadata><ns1:projectMetadata><ns2:name>Louisiana Coast</ns2:name><ns2:generalLocality>Louisiana Coast</ns2:generalLocality><ns2:number>OPR-K354-KR-18</ns2:number><ns2:fieldUnit>Ocean Surveys, Inc.</ns2:fieldUnit></ns1:projectMetadata><ns1:surveyMetadata><ns2:equipmentTypes><ns2:soundingEquipment>Multibeam Echosounder</ns2:soundingEquipment><ns2:imageryEquipment>Side Scan Sonar</ns2:imageryEquipment><ns2:imageryEquipment>Multibeam Echosounder Backscatter</ns2:imageryEquipment></ns2:equipmentTypes><ns2:acquisition><ns2:units>meters</ns2:units></ns2:acquisition><ns2:titlesheetRemarks><ns2:branchRemarks xsi:nil="true"></ns2:branchRemarks><ns2:fieldRemarks>The purpose of this project is to provide contemporary surveys to update National Ocean Service (NOS) nautical charting products.  All times are recorded in UTC. Data recorded and presented relative to UTM Zone 15 North.  THE INFORMATION PRESENTED IN THIS REPORT AND THE ACCOMPANYING DIGITAL DATA REPRESENTS THE RESULTS OF SURVEYS PERFORMED BY OCEAN SURVEYS, INC. DURING THE PERIOD OF 28 MAY 2018 TO 24 SEPTEMBER 2018 AND CAN ONLY BE CONSIDERED AS INDICATING THE CONDITIONS EXISTING AT THAT TIME.  REUSE OF THIS INFORMATION BY CLIENT OR OTHERS BEYOND THE SPECIFIC SCOPE OF WORK FOR WHICH IT WAS ACQUIRED SHALL BE AT THE SOLE RISK OF THE USER AND WITHOUT LIABILITY TO OSI.</ns2:fieldRemarks></ns2:titlesheetRemarks><ns2:chiefOfParty>George G. Reynolds</ns2:chiefOfParty><ns2:PIDate>2018-08-06</ns2:PIDate><ns2:year>2018</ns2:year><ns2:projectType>Navigable Area</ns2:projectType><ns2:verifier>Atlantic Hydrographic Branch</ns2:verifier><ns2:timeZone>UTC</ns2:timeZone><ns2:datesOfSurvey><ns2:start>2018-05-28</ns2:start><ns2:end>2018-09-24</ns2:end></ns2:datesOfSurvey><ns2:horizontalCoordinateSystem zone="15 N">Universal Transverse Mercator (UTM)</ns2:horizontalCoordinateSystem></ns1:surveyMetadata><ns1:registryMetadata><ns2:sheetID>5</ns2:sheetID><ns2:sublocality>15 Miles South of Diamond Reef</ns2:sublocality><ns2:registryNumber>H13200</ns2:registryNumber><ns2:registryInstructions xsi:nil="true"></ns2:registryInstructions><ns2:scale>40000</ns2:scale><ns2:stateOrTerritory>Louisiana</ns2:stateOrTerritory><ns2:country>United States</ns2:country></ns1:registryMetadata><ns1:assignment>Contractor</ns1:assignment></ns1:metadata><ns1:areaSurveyed><ns1:coverageGraphic><ns2:coverageGraphicImage><ns2:images><ns2:caption>Survey H13200 MBES coverage overlaid on RNC 11340.</ns2:caption><ns2:link>file:///N:/Reports/DRs/H13200/H13200_Survey-Coverage.jpg</ns2:link></ns2:images></ns2:coverageGraphicImage></ns1:coverageGraphic><ns1:surveyQuality><ns2:discussion xsi:nil="true"></ns2:discussion><ns2:comments/><ns2:adequacy>The entire survey is adequate to supersede previous data.</ns2:adequacy></ns1:surveyQuality><ns1:surveyStatistics><ns2:discussion>The linear nautical miles (LNM) for MBES-only development and fill-in lines were included under the heading &quot;Mainscheme MBES&quot; in Table 3,  Hydrographic Survey Statistics.  There was no SSS-only mileage for this survey. </ns2:discussion><ns2:LNM><ns2:vesselLNM><ns2:vessel><ns2:hullID>R/V Ocean Explorer</ns2:hullID><ns2:statistics><ns2:XL_lidar>0</ns2:XL_lidar><ns2:MS_lidar>0</ns2:MS_lidar><ns2:MS_MBES>400.59</ns2:MS_MBES><ns2:XL_MBES_SBES>148.46</ns2:XL_MBES_SBES><ns2:MS_MBES_SSS>2095.68</ns2:MS_MBES_SSS><ns2:MS_SSS>0</ns2:MS_SSS><ns2:MS_SBES_SSS>0</ns2:MS_SBES_SSS><ns2:MS_SBES_MBES>0</ns2:MS_SBES_MBES><ns2:MS_SBES>0</ns2:MS_SBES></ns2:statistics></ns2:vessel></ns2:vesselLNM><ns2:totalLNM><ns2:MS_SBES_SSS>0</ns2:MS_SBES_SSS><ns2:MS_lidar>0</ns2:MS_lidar><ns2:MS_MBES>400.59</ns2:MS_MBES><ns2:XL_MBES_SBES>148.46</ns2:XL_MBES_SBES><ns2:MS_MBES_SSS>2095.68</ns2:MS_MBES_SSS><ns2:percentXLLNM>5.9</ns2:percentXLLNM><ns2:MS_SSS>0</ns2:MS_SSS><ns2:XL_lidar>0</ns2:XL_lidar><ns2:MS_SBES_MBES>0</ns2:MS_SBES_MBES><ns2:MS_SBES>0</ns2:MS_SBES></ns2:totalLNM></ns2:LNM><ns2:surveyDates>2018-08-14</ns2:surveyDates><ns2:surveyDates>2018-08-15</ns2:surveyDates><ns2:surveyDates>2018-08-16</ns2:surveyDates><ns2:surveyDates>2018-08-17</ns2:surveyDates><ns2:surveyDates>2018-08-18</ns2:surveyDates><ns2:surveyDates>2018-08-19</ns2:surveyDates><ns2:surveyDates>2018-08-20</ns2:surveyDates><ns2:surveyDates>2018-08-21</ns2:surveyDates><ns2:surveyDates>2018-08-22</ns2:surveyDates><ns2:surveyDates>2018-08-23</ns2:surveyDates><ns2:surveyDates>2018-08-24</ns2:surveyDates><ns2:surveyDates>2018-08-25</ns2:surveyDates><ns2:surveyDates>2018-08-26</ns2:surveyDates><ns2:surveyDates>2018-08-27</ns2:surveyDates><ns2:surveyDates>2018-08-28</ns2:surveyDates><ns2:surveyDates>2018-08-29</ns2:surveyDates><ns2:surveyDates>2018-08-30</ns2:surveyDates><ns2:surveyDates>2018-08-31</ns2:surveyDates><ns2:surveyDates>2018-09-01</ns2:surveyDates><ns2:surveyDates>2018-09-02</ns2:surveyDates><ns2:surveyDates>2018-09-07</ns2:surveyDates><ns2:surveyDates>2018-09-08</ns2:surveyDates><ns2:surveyDates>2018-09-09</ns2:surveyDates><ns2:surveyDates>2018-09-10</ns2:surveyDates><ns2:surveyDates>2018-09-11</ns2:surveyDates><ns2:surveyDates>2018-09-18</ns2:surveyDates><ns2:surveyDates>2018-09-19</ns2:surveyDates><ns2:surveyDates>2018-09-20</ns2:surveyDates><ns2:surveyDates>2018-09-22</ns2:surveyDates><ns2:surveyDates>2018-09-23</ns2:surveyDates><ns2:totalSurveyStats><ns2:SNM>79.89</ns2:SNM><ns2:DP>0</ns2:DP><ns2:diveOps>0</ns2:diveOps><ns2:maritimeBoundaryPoints>0</ns2:maritimeBoundaryPoints><ns2:bottomSamples>9</ns2:bottomSamples></ns2:totalSurveyStats><ns2:comments/></ns1:surveyStatistics><ns1:surveyCoverage><ns2:results deviation="true"><ns2:discussion>Survey Coverage is in accordance with the requirements in the Hydrographic Survey Project Instructions and the Statement of Work (August 6, 2018), and the Hydrographic Surveys Specifications and Deliverables, [April, 2017 (HSSD)]. Where required, Complete Coverage was accomplished by acquiring one hundred percent (100%) side scan sonar (SSS) coverage with concurrent multibeam echosounder (MBES) with backscatter or Complete Coverage MBES with backscatter.

Additional SSS and MBES coverage was obtained as necessary to fill gaps in coverage, to provide a least depth for all significant SSS contacts, and to disprove charted features. Gaps in the 100% SSS coverage were addressed with SSS fill-in lines or covered with complete MBES data. Bathymetric &quot;sounding stars&quot; were also acquired to verify or disprove charted depths that fell between two MBES survey lines when the charted depth was shallower than the adjacent survey soundings.</ns2:discussion></ns2:results><ns2:comments/><ns2:coverageRequirement><ns2:waterDepth>All waters in survey area</ns2:waterDepth><ns2:requiredCoverage>Complete coverage (refer to HSSD Section 5.2.2.3).  LNM no less than 10,592 LNM.  Acquire backscatter data during all multibeam data acquisition (HSSD Section 6.2).  Report significant shoaling via weekly progress report.  COR may adjust surveying prioritization based on observed shoaling. </ns2:requiredCoverage></ns2:coverageRequirement></ns1:surveyCoverage><ns1:areaDescription><ns2:discussion>This survey provides hydrographic data for the Gulf of Mexico waters approaching the Louisiana Coast south of Vermilion Bay. The general locations of the survey limits are presented in Table 1.</ns2:discussion><ns2:limits><ns2:northWest><ns2:latitude hemisphere="N">29.3095281944</ns2:latitude><ns2:longitude hemisphere="W">92.1502926111</ns2:longitude></ns2:northWest><ns2:southEast><ns2:latitude hemisphere="N">29.1139871111</ns2:latitude><ns2:longitude hemisphere="W">91.8848203889</ns2:longitude></ns2:southEast></ns2:limits><ns2:comments/></ns1:areaDescription><ns1:surveyPurpose><ns2:discussion>As noted in the Hydrographic Title Sheet, the Project Instructions signature date was August 6, 2018.  Before being superseded, the survey priorities from the original signed Project Instructions (March 23, 2018) were modified by a Change Request (July 9, 2018).  The following text is copied verbatim from the latest Project Instructions' Purpose and Location Section.

&quot;The Louisiana Coast project will provide contemporary surveys to update National Ocean Service (NOS) nautical charting products. It is in the vicinity of the Atchafalaya River Delta, and Port of Morgan City, Louisiana. The survey will provide updated bathymetry and feature data to address concerns of migrating shoals and exposed hazards, thus reducing the risk to navigation within the project area.

The Port of Morgan City is growing significantly and is working on programs to deepen and maintain the ship channel through the Gulf, bay, and up the Atchafalaya River to the Port of Morgan City where it intersects with the Gulf of Mexico Intracoastal Waterway.

The Port serves a number of industries, including the offshore oil, chemical and machinery industries, as well as shrimp and other seafood fisheries in the Gulf of Mexico. In addition to the port commerce, the Atchafalaya River delta has a rich ecosystem that supports both commercial fishing and recreational fishing communities. Updated charts from this project will support commerce and protect the environment by improving the safety of navigation for area traffic.

The project will cover approximately 300 square nautical miles of high priority survey area identified in the 2016 Hydrographic Health model. Modern surveys show significant shoaling and sediment transport; OPR-K354-KR-17 documented a shoal that had shifted a mile westward since the area was last surveyed in 1935. Adjacent surveys uncovered numerous exposed pipelines and hazards. Data from this project is intended to supersede all prior survey data, updating the local charting products.&quot;</ns2:discussion><ns2:comments/></ns1:surveyPurpose><ns1:surveyLimits><ns2:results deviation="false"><ns2:discussion>Survey limits were acquired in accordance with the requirements in the Project Instructions and the HSSD.</ns2:discussion></ns2:results><ns2:comments/></ns1:surveyLimits></ns1:areaSurveyed><ns1:dataAcquisitionAndProcessing><ns1:dataProcessing><ns1:surfaces><ns1:comments/><ns1:surface><ns2:surfaceType>CARIS Raster Surface (CUBE)</ns2:surfaceType><ns2:surfaceName>H13200_MB_1m_MLLW</ns2:surfaceName><ns2:resolution units="meters">1</ns2:resolution><ns2:purpose>Complete Coverage (Option B)</ns2:purpose><ns2:surfaceParameter>NOAA_1m</ns2:surfaceParameter><ns2:depthRange><ns2:max units="meters">13.95</ns2:max><ns2:min units="meters">6.12</ns2:min></ns2:depthRange></ns1:surface><ns1:surface><ns2:surfaceType>SSS Mosaic</ns2:surfaceType><ns2:surfaceName>H13200_SSS_1m_100</ns2:surfaceName><ns2:resolution units="meters">1</ns2:resolution><ns2:purpose>100% SSS</ns2:purpose><ns2:surfaceParameter>N/A</ns2:surfaceParameter><ns2:depthRange><ns2:max xsi:nil="true"/><ns2:min xsi:nil="true"/></ns2:depthRange></ns1:surface><ns1:surface><ns2:surfaceType>SSS Mosaic</ns2:surfaceType><ns2:surfaceName>H13200_SSS_Disproval</ns2:surfaceName><ns2:resolution units="meters">1</ns2:resolution><ns2:purpose>200% SSS</ns2:purpose><ns2:surfaceParameter>N/A</ns2:surfaceParameter><ns2:depthRange><ns2:max xsi:nil="true"/><ns2:min xsi:nil="true"/></ns2:depthRange></ns1:surface><ns1:discussion>In addition to the above surfaces, a higher resolution, 0.25m SSS mosaic image composed of all SSS lines was submitted in Enhanced Compressed Wavelet (ECW) format to assist with the survey review. </ns1:discussion></ns1:surfaces><ns1:drSoftware><ns1:discussion>Software versions described in Section A of the DAPR were used throughout acquisition and processing of data for Project OPR-K354-KR-18.</ns1:discussion><ns1:comments/><ns1:bathySoftware deviation="true"><ns1:manufacturer>CARIS</ns1:manufacturer><ns1:name>HIPS</ns1:name><ns1:version>10.4</ns1:version></ns1:bathySoftware><ns1:featureObjectCatalog>NOAA Extended Attribute Files V5_8</ns1:featureObjectCatalog><ns1:imagerySoftware deviation="true"><ns1:manufacturer>CARIS</ns1:manufacturer><ns1:name>SIPS</ns1:name><ns1:version>10.4</ns1:version></ns1:imagerySoftware></ns1:drSoftware><ns1:additionalDataProcessing><ns2:comments/></ns1:additionalDataProcessing></ns1:dataProcessing><ns1:equipmentAndVessels><ns1:comments/><ns1:vessels><ns1:comments/><ns1:discussion xsi:nil="true"></ns1:discussion><ns1:vessel><ns2:hullID>R/V Ocean Explorer</ns2:hullID><ns2:LOA units="meters">18</ns2:LOA><ns2:draft units="meters">2</ns2:draft></ns1:vessel></ns1:vessels><ns1:equipment><ns1:majorSystem><ns2:model>4125</ns2:model><ns2:type>SSS</ns2:type><ns2:manufacturer>EdgeTech</ns2:manufacturer></ns1:majorSystem><ns1:majorSystem><ns2:model>SeaBat 7125 SV2</ns2:model><ns2:type>MBES</ns2:type><ns2:manufacturer>Teledyne RESON</ns2:manufacturer></ns1:majorSystem><ns1:majorSystem><ns2:model>POS MV 320 v5</ns2:model><ns2:type>Positioning and Attitude System</ns2:type><ns2:manufacturer>Applanix</ns2:manufacturer></ns1:majorSystem><ns1:majorSystem><ns2:model>ProBeacon</ns2:model><ns2:type>Positioning System</ns2:type><ns2:manufacturer>Trimble</ns2:manufacturer></ns1:majorSystem><ns1:majorSystem><ns2:model>MS750</ns2:model><ns2:type>Positioning System</ns2:type><ns2:manufacturer>Trimble</ns2:manufacturer></ns1:majorSystem><ns1:majorSystem><ns2:model>NetR9</ns2:model><ns2:type>Positioning System</ns2:type><ns2:manufacturer>Trimble</ns2:manufacturer></ns1:majorSystem><ns1:majorSystem><ns2:model>Micro X</ns2:model><ns2:type>Sound Speed System</ns2:type><ns2:manufacturer>AML Oceanographic</ns2:manufacturer></ns1:majorSystem><ns1:majorSystem><ns2:model>Base X</ns2:model><ns2:type>Sound Speed System</ns2:type><ns2:manufacturer>AML Oceanographic</ns2:manufacturer></ns1:majorSystem><ns1:majorSystem><ns2:model>MVP30</ns2:model><ns2:type>Sound Speed System</ns2:type><ns2:manufacturer>ODIM Brooke Ocean</ns2:manufacturer></ns1:majorSystem><ns1:comments/><ns1:discussion xsi:nil="true"></ns1:discussion></ns1:equipment><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:equipmentAndVessels><ns1:backscatter><ns2:results acquired="true"><ns2:discussion>Backscatter data were acquired concurrent with bathymetry data for Survey H13200.  Backscatter data were recorded with HYSWEEP SURVEY in .7K format, and these data were periodically reviewed to ensure functionality of the backscatter acquisition process.</ns2:discussion></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: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:additionalIssues><ns2:comments/></ns1:additionalIssues></ns1:echoSoundingCorrections><ns1:qualityControl><ns1:uncertainty><ns2:discussion>The methods used to minimize the uncertainty in the corrections to echo soundings are described in detail in Section B, Processing and Quality Control, of the project DAPR.  Survey H13200 did not deviate from the methods documented in the DAPR.

The Total Vertical Uncertainty Quality Check (TVU QC) &quot;Ratio Method&quot; was used to evaluate IHO uncertainty for the finalized surface, which was generated using the &quot;greater of the two&quot; option in the CARIS &quot;Finalize Base Surface&quot; utility.  The TVU QC &quot;Ratio Method&quot; is described in the Chapter 4 Appendices of the NOAA OCS Field Procedures Manual (FPM) dated April 2014.  Per the FPM TVU QC section, &quot;The hydrographer should use the finalized surface because this surface will identify areas where either the uncertainty or the standard deviation exceeded the maximum allowable error and the greater of these two values is used in addition to having the uncertainty scaled to a 95% CI, whereas unfinalized surface uncertainties are reported at the 68% CI.&quot;  The FPM TVU QC section also states that, &quot;[ratio] values which do not require further examination are from -1 to 0 and the values which do require further examination are from -100 to -1&quot;.

Results from the TVU QC indicate that 99.99% of the nodes in this surface meet IHO Order 1 uncertainty specifications, i.e. the ratio values of nearly all the nodes are between 0 and -1.  Of the 175 million nodes considered, only 27 had a ratio value below -1.  Upon examination it was found that the nodes with ratio values below -1 were located over known seafloor disturbances and/or known discrete features, resulting in higher standard deviation values and finalized uncertainty values, which is to be expected.
				</ns2:discussion><ns2:comments/><ns2:values><ns2:tideUncertainty><ns2:zoning units="meters">0.17166</ns2:zoning><ns2:measured units="meters">0</ns2:measured><ns2:tideMethod>ERS via VDATUM</ns2:tideMethod></ns2:tideUncertainty><ns2:soundSpeedUncertainty><ns2:hullID>R/V Ocean Explorer</ns2:hullID><ns2:surface units="meters/second">2</ns2:surface><ns2:measuredCTD units="meters/second">N/A</ns2:measuredCTD><ns2:measuredMVP units="meters/second">1</ns2:measuredMVP></ns2:soundSpeedUncertainty></ns2:values></ns1:uncertainty><ns1:additionalQualityControl><ns2:comments/><ns2:issue><ns2:discussion>The CARIS HIPS and SIPS Compute Statistics tool calculated that 99.74% of the 1.0m grid nodes have 5 soundings or more, which satisfies the density coverage requirements.</ns2:discussion><ns2:comments/><ns2:title>Density</ns2:title></ns2:issue></ns1:additionalQualityControl><ns1:coverageEquipmentAndMethods><ns2:results deviation="true"><ns2:discussion>This survey was conducted to develop 100% SSS coverage along with concurrent MBES with backscatter for all survey depths, i.e. Complete Coverage, Option B as defined in Section 5.2.2.3 of the HSSD 2017.  For all disprovals either 200% SSS or Complete Coverage MBES was achieved.  Per the HSSD which states &quot;Gaps in 100% SSS coverage should be treated as gaps in coverage and addressed accordingly,&quot; gaps in SSS coverage and holidays caused by fish, dolphins, or white line noise were developed with Complete Multibeam or a second side scan coverage.  All potentially significant features located with mainscheme SSS or MBES were developed with multibeam sonar data to meet HSSD 5.2.2.3 Complete Coverage requirements.  All depths within Survey H13200 were shallower than 20m, for which HSSD 5.2.2.3 specifies a grid resolution of 1.0m.

The survey methods used to meet coverage requirements did not deviate from those described in the DAPR.</ns2:discussion></ns2:results><ns2:comments/></ns1:coverageEquipmentAndMethods><ns1:crosslines><ns2:discussion>A total of 148.46 nm of crossline data was acquired on August 14-15 and September 18 (DNs 226-227 and 261).  Crosslines were run northeast-southwest with mainscheme lines running east-west (Figure 2).

Soundings from mainscheme lines and crosslines were compared periodically throughout survey operations by reviewing preliminary MBES surfaces and using CARIS HIPS Subset Editor.  Crossline comparisons provided confirmation that the system offsets and biases were entered correctly and verified the accuracy of sounding correctors (i.e. tide, sound speed, TrueHeave).

Statistical quality control information was compiled from a difference surface, generated in CARIS HIPS, between the depth layer of a 1.0m CUBE surface composed only of crossline data and the depth layer of a 1.0m CUBE surface composed only of mainscheme data.  The crossline analysis results demonstrate very good agreement between crossline soundings and mainscheme soundings; the average difference is 0.007m and 99.99% of the 1.0m comparison cells have differences within +/- 0.25m.

Figure 3 is a histogram showing the distribution of depth differences for all comparison grid cells considered.</ns2:discussion><ns2:images><ns2:caption>An overview of the crossline layout on a 1.0m surface created from mainscheme MBES data and colored by depth.  RNC 11349 is visible in the background.</ns2:caption><ns2:link>file:///N:/Reports/DRs/H13200/H13200_XL_overview.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>The graph shows a frequency distribution of the depth differences between the H13200 mainscheme data and the H13200 crossline MBES data.  Statistics from the depth difference sample set are displayed above the graph.</ns2:caption><ns2:link>file:///N:/Reports/DRs/H13200/H13200_XL-Main_Histogram.jpg</ns2:link></ns2:images><ns2:comments/></ns1:crosslines><ns1:soundSpeedMethods><ns1:castFrequency>Sound speed profile data were acquired with the ODIM MVP30 approximately every 15 minutes as documented in the DAPR.</ns1:castFrequency><ns1:comments/><ns1:discussion>All MBES lines were sound speed corrected using CARIS HIPS' &quot;Nearest in Distance Within Time&quot; method.  The time interval used was 1 hour.

OSI submitted H13200 sound speed data in NetCDF format to the National Centers for Environmental Information (NCEI) on October 15, 2018 via the S2N tool.  NCEI assigned the sound speed submission Accession Number 0177405.  Correspondence regarding the NCEI data submission is included in Appendix II. </ns1:discussion></ns1:soundSpeedMethods><ns1:junctions><ns2:discussion>Three (3) prior surveys and 1 contemporary survey junction with Survey H13200.  Figure 4 displays the location of the prior and contemporary junction surveys for Project OPR-K354-KR-28.  The allowable TVU for the range of water depths within Survey H13200 is 0.51m to 0.53m.  Therefore, according to the XMLDR Junction Area &quot;maximum difference&quot; threshold guidance equation (SQRT2 * TVU), the junction discrepancy action threshold = 0.72m.</ns2:discussion><ns2:images><ns2:caption>Survey junctions for Project OPR_K354-KR-18.  RNC 11340 is displayed in the background.</ns2:caption><ns2:link>file:///N:/Reports/DRs/H13200/H13200_Junction_Overview.jpg</ns2:link></ns2:images><ns2:comments/><ns2:junction><ns2:discussion>Survey H13041, a MBES/SSS survey conducted by Ocean Surveys, Inc. in 2017, overlaps the northern border of H13200.  Depth data for Survey H13041 were taken from the dataset delivered to NOAA by Ocean Surveys, Inc. on February 6, 2018 in the form of a 1.0m resolution CARIS Spatial Archive (CSAR) raster &quot;H13041_MB_1m_MLLW_Final.csar.&quot;  To conduct the junction comparison the depths from the H13041 data were subtracted from the depths in the H13200 surface using the CARIS HIPS Difference Surface function.  A histogram of the differences is shown in Figure 5.

Survey H13041 was run with the intention of achieving 100% SSS coverage, as was H13200 in the northern section where it junctions with H13041. Each survey's MBES coverage is &quot;skunk stripe&quot; coverage.  The two surveys' mainscheme line plans meet at an angle, leading to a patchy junction area.  The surveys share a common border of approximately 4600m, and the mainscheme lines and crosslines overlap by as much as 400m.

Depths from the H13041 survey show good agreement with depths from Survey H13200. The average difference between these surveys is 0.06m, and 99.97% of the 1.0m comparison cells have differences within +/- 0.25m.  Differences were overall more variable on the crosslines than on the mainscheme lines; most mainscheme lines matched closely with few exceptions.

All (100%) junction comparison cells have a difference below the discrepancy action threshold of 0.72m.</ns2:discussion><ns2:images><ns2:caption>Surface-to-surface difference histogram comparing Survey H13200 to H13041.</ns2:caption><ns2:link>file:///N:/Reports/DRs/H13200/H13200_Junction_H13041_Histogram.jpg</ns2:link></ns2:images><ns2:comments/><ns2:survey><ns2:relativeLocation>N</ns2:relativeLocation><ns2:scale>40000</ns2:scale><ns2:year>2017</ns2:year><ns2:registryNumber>H13041</ns2:registryNumber><ns2:fieldUnit>Ocean Surveys, Inc.</ns2:fieldUnit></ns2:survey></ns2:junction><ns2:junction><ns2:discussion>Survey H13042, a MBES/SSS survey conducted by Ocean Surveys, Inc. in 2017, overlaps the northeastern border of H13200.  Depth data for Survey H13042 were taken from the dataset delivered to NOAA by Ocean Surveys, Inc. on February 6, 2018 in the form of a 1.0m resolution CSAR raster &quot;H13042_MB_1m_MLLW_Final.csar.&quot;  To conduct the junction comparison the depths from the H13042 data were subtracted from the depths in the H13200 surface using the CARIS HIPS Difference Surface function.  A histogram of the differences is shown in Figure 6.

Survey H13042 was run with the intention of achieving 100% SSS coverage, as was H13200 in the northern section where it junctions with H13042; each survey's MBES coverage is &quot;skunk stripe&quot; coverage.  The two surveys' mainscheme line plans are almost parallel to one another, but the slight offset in orientation leads to a junction area that varies from nearly complete mainscheme overlap to no overlap at all along the length of the common border, which is approximately 6100m.  The mainscheme lines overlap by as much as 780m, and the crosslines overlap by up to 400m.

Overall agreement between the two surveys is very good. The average difference between these surveys is 0.02m, and 99.99% of the 1.0m comparison cells have differences within +/- 0.25m.  However, there are two distinct peaks in the histogram (Figure 6) that suggest some small biases are present in the data.  Tidal differences are a likely cause of these depth discrepancies; the offset, when present, is noted across the full swath of coincident lines from the same survey day and the offset varies by survey day in H13042.

All (100%) junction comparison cells have a difference below the discrepancy action threshold of 0.72m.</ns2:discussion><ns2:images><ns2:caption>Surface-to-surface difference histogram comparing Survey H13200 to H13042.</ns2:caption><ns2:link>file:///N:/Reports/DRs/H13200/H13200_Junction_H13042_Histogram.jpg</ns2:link></ns2:images><ns2:comments/><ns2:survey><ns2:relativeLocation>N</ns2:relativeLocation><ns2:scale>40000</ns2:scale><ns2:year>2017</ns2:year><ns2:registryNumber>H13042</ns2:registryNumber><ns2:fieldUnit>Ocean Surveys, Inc.</ns2:fieldUnit></ns2:survey></ns2:junction><ns2:junction><ns2:discussion>Survey H13043, a MBES/SSS survey conducted by Ocean Surveys, Inc. in 2017, overlaps the eastern borders of H13200.  Depth data for Survey H13043 were taken from the dataset delivered to NOAA by Ocean Surveys, Inc. on February 6, 2018 in the form of a 1.0m resolution CSAR raster &quot;H13043_MB_1m_MLLW_Final.csar.&quot;  To conduct the junction comparison the depths from the H13043 data were subtracted from the depths in the H13200 surface using the CARIS HIPS Difference Surface function.  A histogram of the differences is shown in Figure 7.

Both Survey H13043 and Survey H13200 were run with the intention of achieving 100% SSS coverage in depths shoaler than 10.0m, and complete MBES coverage in the deeper waters in the southern portions of both survey areas.  Their junction area contains both &quot;skunk stripe&quot; coverage overlap for approximately 19,000m of their common border of 24,000m, and complete MBES overlap for the remaining common border of 5,000m at the south end of the junction.  The mainscheme lines in the 100% SSS coverage area meet at an angle, giving a moderately dense junction area with a few patches of higher density in areas where mainscheme lines were run at 40m spacing rather than 80m spacing.  Overlap of mainscheme lines in the complete coverage MBES area is approximately 260m, with crosslines overlapping by as much as 350m.  Overlap in the 100% SSS coverage area is as much as 450m.

Depth agreement between the two surveys is very good.  The average difference between these surveys is 0.05m and 99.64% of the 1.0m comparison cells have differences within +/- 0.25m.

All (100%) junction comparison cells have a difference below the discrepancy action threshold of 0.72m.</ns2:discussion><ns2:images><ns2:caption>Surface-to-surface difference histogram comparing Survey H13200 to H13043.</ns2:caption><ns2:link>file:///N:/Reports/DRs/H13200/H13200_Junction_H13043_Histogram.jpg</ns2:link></ns2:images><ns2:comments/><ns2:survey><ns2:relativeLocation>E</ns2:relativeLocation><ns2:scale>40000</ns2:scale><ns2:year>2017</ns2:year><ns2:registryNumber>H13043</ns2:registryNumber><ns2:fieldUnit>Ocean Surveys, Inc.</ns2:fieldUnit></ns2:survey></ns2:junction><ns2:junction><ns2:discussion>Data from contemporary Surveys H13103 and H13200 overlap along a common border of approximately 25,000m.  Both surveys were acquired to meet 100% SSS coverage for the majority of the area they cover (approximately 20,600m of the common border), and complete coverage MBES in the southernmost areas of both surveys (approximately 4,400m of the common border).  The mainscheme line plans of the two surveys are parallel and closely aligned; the &quot;skunk stripe&quot; coverage MBES data between the two surveys have nearly complete overlap, producing a dense junction area.  The mainscheme lines overlap by as much as 670m, and there are two locations where the crosslines align between the two surveys; each crossline overlap has a length of approximately 2,100m within the junction area.

Depths from 1.0m CUBE surfaces compiled from the MBES data from each survey were compared using the CARIS HIPS Difference Surface function.  A histogram of the differences is shown in Figure 8.

Depths from the two surveys show good agreement with one another.  The average difference between these surveys is 0.02m, and 99.99% of the 1.0m comparison cells have differences within +/- 0.25m.

All (100%) junction comparison cells have a difference below the discrepancy action threshold of 0.72m.</ns2:discussion><ns2:images><ns2:caption>Surface-to-surface difference histogram comparing Survey H13200 to H13103.</ns2:caption><ns2:link>file:///N:/Reports/DRs/H13200/H13200_Junction_H13103_Histogram.jpg</ns2:link></ns2:images><ns2:comments/><ns2:survey><ns2:relativeLocation>W</ns2:relativeLocation><ns2:scale>40000</ns2:scale><ns2:year>2018</ns2:year><ns2:registryNumber>H13103</ns2:registryNumber><ns2:fieldUnit>Ocean Surveys, Inc.</ns2:fieldUnit></ns2:survey></ns2:junction></ns1:junctions><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:factorsAffectingSoundings><ns2:results deviation="true"><ns2:issue><ns2:discussion>Dynamic sound speed changes affected the SSS imagery at times, causing refraction in the outer ranges of the SSS swath (Figure 9).  To ensure that 100% coverage of high quality SSS data was acquired, when necessary, SSS lines with excessive refraction were rejected or the portion of the line with severe refraction was rerun.  Due to the close line spacing employed in some locations, there were many instances of outer range refraction that did not trigger a re-run or rejection as high quality, 100% SSS coverage was achieved using only a portion of the imagery from a given line.  For example, if refraction affected only the outer 20m of the 50m image range but the vessel was running on a 40m offset line plan, ample overlap was still achieved between adjacent tracklines resulting in greater than 100% SSS coverage of the area.  In this scenario SSS imagery was not rejected.</ns2:discussion><ns2:images><ns2:caption>Refraction in the SSS imagery is visible in both channels of a survey line acquired with the fixed-mount 4125 SSS.</ns2:caption><ns2:link>file:///N:/Reports/DRs/H13200/H13200_FAS_SSS-refraction.jpg</ns2:link></ns2:images><ns2:comments/><ns2:title>SSS Refraction</ns2:title></ns2:issue><ns2:issue><ns2:discussion>The Reson 7125 system experienced periodic bursts of motion-induced noise or “blowouts,” typically affecting between 1 and 4 sequential profiles.  Efforts were made to reduce this noise during acquisition, including adjustments to system gain and power, in addition to the multibeam pole fairing that was installed on the R/V Ocean Explorer to reduce cavitation effects.  The noise bursts were infrequent and were encountered when sea state worsened.  Accepted data affected by blowouts did not show any coverage gaps in excess of 3 x 3 nodes in the 1.0m MBES coverage surface.

The fixed mount SSS data were also impacted by sea state conditions, such that when the wave frequency and height increased, more cavitation effects were observed near the transducer head with a dark return noted at the top of the water column in the raw SSS record.  The cavitation noise at the transducer head resulted in intermittent black lines across the SSS record, which occasionally coincided with blowouts in the MBES data (Figure 10).  The term &quot;black line&quot; is seen in the acquisition log to denote these types of events.  The acquisition SSS waterfall was the opposite palette as the CARIS SSS palate.  Therefore, a &quot;black line&quot; noted in the log coincides with a white line in CARIS.  To ensure that 100% coverage was attained where the white streaks occurred, holiday fill-in lines were acquired over the location of the streaks with either MBES or SSS coverage as necessary.</ns2:discussion><ns2:images><ns2:caption>This figure shows how cavitation noise at the SSS and MBES transducer heads presented in the converted data.  Noise at the 4125 TX head is visible as a dark return at the top of the water column with white streaking across the raw SSS imagery (bottom).  In this instance, the SSS white streak coincided with an MBES blowout (top right and top left images).</ns2:caption><ns2:link>file:///N:/Reports/DRs/H13200/H13200_FAS_streaks-blowout.jpg</ns2:link></ns2:images><ns2:comments/><ns2:title>Sea State Induced White Streaks in SSS Imagery and MBES &quot;Blowouts&quot;</ns2:title></ns2:issue><ns2:issue><ns2:discussion>An abundance of fish and marine life were observed in the SSS and MBES data, either as lone swimmers or in schools, which at times created large shadows in the SSS imagery and gaps in the MBES data (Figures 11 and 12).  Fish and dolphins were noted in the acquisition log by the field team, and these areas were carefully reviewed during data processing.  Shadows in the SSS, usually detached from a dark return, were typically associated with fish either in the water column or at a position closer to nadir.  In the cases where a visible shadow was recorded in the SSS, the contact was designated as a fish, for two reasons: 1) the possibility that the assumed fish was actually a feature and 2) to assist processors in rejecting fish-related noise from the MBES data.  Over 8,500 fish, fish school, dolphin, and other marine life contacts were identified in Survey H13200.

To ensure that possible significant features were not located in these fish and dolphin shadows, the fish/dolphin related coverage gaps were rerun to achieve 100% SSS coverage or complete MBES coverage.</ns2:discussion><ns2:images><ns2:caption>MBES and SSS images showing a school of fish visible in the water column and the acoustic shadow cast in each dataset. In the top panel the rejected MBES soundings are colored yellow.</ns2:caption><ns2:link>file:///N:/Reports/DRs/H13200/H13200_FAS_fish.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>An example of a dolphin as it appears in the water column of the MBES and the SSS, and the acoustic shadow cast in each dataset. In the top panel the rejected MBES soundings are colored yellow.</ns2:caption><ns2:link>file:///N:/Reports/DRs/H13200/H13200_FAS_dolphins.jpg</ns2:link></ns2:images><ns2:comments/><ns2:title>Fish in SSS Imagery and MBES Data</ns2:title></ns2:issue></ns2:results><ns2:comments/></ns1:factorsAffectingSoundings><ns1:equipmentEffectiveness><ns2:results deviation="false"><ns2:issue><ns2:discussion>There were no conditions or deficiencies that affected equipment operational effectiveness.</ns2:discussion><ns2:comments/><ns2:title>None Exist</ns2:title></ns2:issue></ns2:results><ns2:comments/></ns1:equipmentEffectiveness></ns1:qualityControl></ns1:dataAcquisitionAndProcessing><ns1:approvalSheet><ns1:signingPersonnel><ns2:approverName>George G. Reynolds</ns2:approverName><ns2:approverTitle>Chief of Party</ns2:approverTitle><ns2:approvalDate>2019-01-25</ns2:approvalDate></ns1:signingPersonnel><ns1:signingPersonnel><ns2:approverName>John R. Bean</ns2:approverName><ns2:approverTitle>Lead Hydrographer</ns2:approverTitle><ns2:approvalDate>2019-01-25</ns2:approvalDate></ns1:signingPersonnel><ns1:signingPersonnel><ns2:approverName>David T. Somers</ns2:approverName><ns2:approverTitle>Data Processing Manager</ns2:approverTitle><ns2:approvalDate>2019-01-25</ns2:approvalDate></ns1:signingPersonnel><ns1:statements><ns1:supervision>As Chief of Party, field operations for this hydrographic survey were conducted under my direct supervision, with frequent personal checks of progress and adequacy. I have reviewed the attached survey data and reports.</ns1:supervision><ns1:additionalInfo xsi:nil="true"></ns1:additionalInfo><ns1: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: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:statements><ns1:additionalReports><ns2:reportDateSent>2019-01-25</ns2:reportDateSent><ns2:reportName>Data Acquisition and Processing Report</ns2:reportName></ns1:additionalReports><ns1:additionalReports><ns2:reportDateSent>2019-01-25</ns2:reportDateSent><ns2:reportName>Horizontal and Vertical Control Report</ns2:reportName></ns1:additionalReports><ns1:additionalReports><ns2:reportDateSent>2018-11-15</ns2:reportDateSent><ns2:reportName>Coast Pilot Report</ns2:reportName></ns1:additionalReports></ns1:approvalSheet></ns1:descriptiveReport>