<?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:metadata><ns1:projectMetadata><ns2:number>OPR-K376-KR-18</ns2:number><ns2:name>Port Lavaca, TX</ns2:name><ns2:generalLocality>Port Lavaca, TX</ns2:generalLocality><ns2:fieldUnit>Terrasond, Ltd.</ns2:fieldUnit></ns1:projectMetadata><ns1:registryMetadata><ns2:registryNumber>H13187</ns2:registryNumber><ns2:sheetID>9</ns2:sheetID><ns2:registryInstructions xsi:nil="true"></ns2:registryInstructions><ns2:sublocality>10 NM WSW of Entrance to Colorado River</ns2:sublocality><ns2:stateOrTerritory>Texas</ns2:stateOrTerritory><ns2:country>United States</ns2:country><ns2:scale>40000</ns2:scale></ns1:registryMetadata><ns1:surveyMetadata><ns2:year>2018</ns2:year><ns2:chiefOfParty>Andrew Orthmann</ns2:chiefOfParty><ns2:projectType>Navigable Area</ns2:projectType><ns2:PIDate>2018-07-18</ns2:PIDate><ns2:datesOfSurvey><ns2:start>2018-11-28</ns2:start><ns2:end>2018-12-13</ns2:end></ns2:datesOfSurvey><ns2:equipmentTypes><ns2:soundingEquipment>Multibeam Echo Sounder</ns2:soundingEquipment><ns2:imageryEquipment>Side Scan Sonar</ns2:imageryEquipment></ns2:equipmentTypes><ns2:acquisition><ns2:units>meters</ns2:units></ns2:acquisition><ns2:horizontalCoordinateSystem zone="14N">Universal Transverse Mercator (UTM)</ns2:horizontalCoordinateSystem><ns2:timeZone>UTC</ns2:timeZone><ns2:verifier>Atlantic Hydrographic Branch</ns2:verifier><ns2:titlesheetRemarks><ns2:fieldRemarks xsi:nil="true"></ns2:fieldRemarks><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 ##N, &lt;vertical datum&gt;. 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:titlesheetRemarks></ns1:surveyMetadata><ns1:assignment>Contractor</ns1:assignment></ns1:metadata><ns1:areaSurveyed><ns1:areaDescription><ns2:discussion>The survey area is located offshore SE Texas, centered on Port Lavaca. Water depths range from approximately 15 to 22 meters. Field work was carried out between November and December, 2018. Final processing and reporting was carried out between January and May, 2019. Eight other nearby sheets were surveyed concurrently. Work was done in accordance with the Hydrographic Survey Instructions (dated July 18th, 2018) and the NOS Hydrographic Surveys Specifications and Deliverables (HSSD), April 2018 edition.</ns2:discussion><ns2:limits><ns2:northWest><ns2:latitude hemisphere="N">28.5125580556</ns2:latitude><ns2:longitude hemisphere="W">96.160715</ns2:longitude></ns2:northWest><ns2:southEast><ns2:latitude hemisphere="N">28.3252627778</ns2:latitude><ns2:longitude hemisphere="W">95.9028188889</ns2:longitude></ns2:southEast></ns2:limits><ns2:images><ns2:caption>Graphic showing survey extents.</ns2:caption><ns2:link>SupportFiles\H13187_Survey_Outline.jpg</ns2:link></ns2:images><ns2:comments/></ns1:areaDescription><ns1:surveyLimits><ns2:results deviation="true"><ns2:discussion>The SE portion of the assigned survey area was not surveyed due to reaching the project-wide limit of 7,869 LNM collected.</ns2:discussion></ns2:results><ns2:comments/></ns1:surveyLimits><ns1:surveyPurpose><ns2:discussion>This project is located in the vicinity of Port Lavaca, which includes the Matagorda Bay Shipping Channel. Port Lavaca is a major sea port that allows shipping to support the fishing, manufacturing, agriculture, tourism, as well as the fishing industries in the state of Texas. As a leader in the shrimp processing industry, Port Lavaca allows million tons of seafood to be shipping through its port yearly. Port Lavaca also supports shipping for Matagorda Bay, which houses several large manufacturing plants and a nuclear station. The U.S. Army Corps of Engineers maintains the Matagorda Bay Shipping Channel which is dredged and there are future plans to expand this dredged channel to 44 ft. in depth and 400 ft. wide.4 The survey area covers the approaches to the shipping channel in an effort to cover all shipping traffic into the Matagorda Shipping Channel. Recent hurricane activity in 2017 has made previous bathymetry in the area unreliable. This survey will allow shipping activities to continue into the Port of Lavaca.</ns2:discussion><ns2:comments/></ns1:surveyPurpose><ns1:surveyQuality><ns2:adequacy>The entire survey is adequate to supersede previous data.</ns2:adequacy><ns2:discussion xsi:nil="true"></ns2:discussion><ns2:comments/></ns1:surveyQuality><ns1:surveyCoverage><ns2:coverageRequirement><ns2:waterDepth>H13180-H13187, except H13181</ns2:waterDepth><ns2:requiredCoverage>Complete Coverage (Refer to HSSD Section 5.2.2.3)</ns2:requiredCoverage></ns2:coverageRequirement><ns2:coverageRequirement><ns2:waterDepth>All waters in survey area</ns2:waterDepth><ns2:requiredCoverage>LNM no less than 7869 LNM. Report significant shoaling via weekly progress report. COR may adjust survey prioritization based on observed shoaling.</ns2:requiredCoverage></ns2:coverageRequirement><ns2:results deviation="true"><ns2:discussion>Approximately 9,103 LNM were collected project-wide, which exceeds the minimum of 7,869 required in the Project Instructions. The 13.5% overage was largely due to unplanned infill/rerun work in areas of marginal data.

Both &quot;Option A: Complete Coverage Multibeam&quot; and &quot;Option B: 100% side scan sonar coverage with concurrent multibeam&quot; were used to meet HSSD Section 5.2.2.3 &quot;Complete Coverage&quot; requirements during this survey. Option B was favored whenever possible and used for most of the area, but Option A was also frequently exercised when the SSS equipment was experiencing issues or SSS data quality had degraded to an unacceptable degree. Infills/reruns on holidays in Option B areas were also frequently MBES-only if MBES was capable of efficiently covering the holiday.</ns2:discussion></ns2:results><ns2:comments/></ns1:surveyCoverage><ns1:coverageGraphic><ns2:coverageGraphicImage><ns2:images><ns2:caption>Graphic showing survey coverage extents.</ns2:caption><ns2:link>SupportFiles\H13187_Survey_Coverage.jpg</ns2:link></ns2:images></ns2:coverageGraphicImage></ns1:coverageGraphic><ns1:surveyStatistics><ns2:LNM><ns2:vesselLNM><ns2:vessel><ns2:hullID>Bunny Bordelon</ns2:hullID><ns2:statistics><ns2:MS_SBES>0</ns2:MS_SBES><ns2:MS_MBES>8.3</ns2:MS_MBES><ns2:MS_lidar>0</ns2:MS_lidar><ns2:MS_SSS>0</ns2:MS_SSS><ns2:MS_SBES_MBES>0</ns2:MS_SBES_MBES><ns2:MS_MBES_SSS>668.7</ns2:MS_MBES_SSS><ns2:MS_SBES_SSS>0</ns2:MS_SBES_SSS><ns2:XL_MBES_SBES>37.8</ns2:XL_MBES_SBES><ns2:XL_lidar>0</ns2:XL_lidar></ns2:statistics></ns2:vessel></ns2:vesselLNM><ns2:totalLNM><ns2:MS_SBES>0</ns2:MS_SBES><ns2:MS_MBES>8.3</ns2:MS_MBES><ns2:MS_lidar>0</ns2:MS_lidar><ns2:MS_SSS>0</ns2:MS_SSS><ns2:MS_SBES_MBES>0</ns2:MS_SBES_MBES><ns2:MS_MBES_SSS>668.7</ns2:MS_MBES_SSS><ns2:MS_SBES_SSS>0</ns2:MS_SBES_SSS><ns2:XL_MBES_SBES>37.8</ns2:XL_MBES_SBES><ns2:XL_lidar>0</ns2:XL_lidar><ns2:percentXLLNM>5.5</ns2:percentXLLNM></ns2:totalLNM></ns2:LNM><ns2:totalSurveyStats><ns2:bottomSamples>12</ns2:bottomSamples><ns2:maritimeBoundaryPoints>0</ns2:maritimeBoundaryPoints><ns2:DP>0</ns2:DP><ns2:diveOps>0</ns2:diveOps><ns2:SNM>54.8</ns2:SNM></ns2:totalSurveyStats><ns2:surveyDates>2018-11-28</ns2:surveyDates><ns2:surveyDates>2018-11-29</ns2:surveyDates><ns2:surveyDates>2018-11-30</ns2:surveyDates><ns2:surveyDates>2018-12-01</ns2:surveyDates><ns2:surveyDates>2018-12-02</ns2:surveyDates><ns2:surveyDates>2018-12-03</ns2:surveyDates><ns2:surveyDates>2018-12-12</ns2:surveyDates><ns2:surveyDates>2018-12-13</ns2:surveyDates><ns2:discussion xsi:nil="true"></ns2:discussion><ns2:comments/></ns1:surveyStatistics></ns1:areaSurveyed><ns1:dataAcquisitionAndProcessing><ns1:equipmentAndVessels><ns1:discussion>Refer to the Data Acquisition and Processing Report (DAPR) for a complete description of data acquisition and processing systems, survey vessels, quality control procedures and data processing methods.  Additional information to supplement sounding and survey data, and any deviations from the DAPR are discussed in the following sections.</ns1:discussion><ns1:vessels><ns1:vessel><ns2:hullID>Bunny Bordelon</ns2:hullID><ns2:LOA units="meters">45.7</ns2:LOA><ns2:draft units="meters">3.5</ns2:draft></ns1:vessel><ns1:images><ns2:caption>Bunny Bordelon</ns2:caption><ns2:link>SupportFiles\BunnyBordelon.jpg</ns2:link></ns1:images><ns1:discussion>The RV Bunny Bordelon is owned and operated by Bordelon Marine Services, LLC of Houma, Louisiana. It was outfit with a 20' conex on the back deck for working space, an A-frame and a winch for towed SSS operations, and a retractable MBES pole mid-ship on its port-side.

Note the other vessels detailed in the DAPR were not utilized on this survey sheet.</ns1:discussion><ns1:comments/></ns1:vessels><ns1:equipment><ns1:majorSystem><ns2:manufacturer>Teledyne RESON</ns2:manufacturer><ns2:model>Seabat T50 IDH</ns2:model><ns2:type>MBES</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>EdgeTech</ns2:manufacturer><ns2:model>4200</ns2:model><ns2:type>SSS</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>Applanix</ns2:manufacturer><ns2:model>POS MV 320 v5</ns2:model><ns2:type>Positioning and Attitude System</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>AML Oceanographic</ns2:manufacturer><ns2:model>Minos-X</ns2:model><ns2:type>Sound Speed System</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>AML Oceanographic</ns2:manufacturer><ns2:model>MicroX SVS</ns2:model><ns2:type>Sound Speed System</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>Valeport</ns2:manufacturer><ns2:model>RapidSV</ns2:model><ns2:type>Sound Speed System</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>Valeport</ns2:manufacturer><ns2:model>SWIFT SVP</ns2:model><ns2:type>Sound Speed System</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>Teledyne Oceanscience</ns2:manufacturer><ns2:model>RapidCast</ns2:model><ns2:type>Underway Sound Speed Deployment System</ns2:type></ns1:majorSystem><ns1:discussion xsi:nil="true"></ns1:discussion><ns1:comments/></ns1:equipment><ns1:comments/></ns1:equipmentAndVessels><ns1:qualityControl><ns1:crosslines><ns2:discussion>Effort was made to ensure crosslines had good temporal and geographic distribution, were angled to enable nadir-to-nadir as well as nadir-to-outer beam comparisons, and that the required percent of mainscheme LNM was achieved.

The crossline analysis was conducted using CARIS HIPS “Line QC Report” process. Each crossline was selected individually and run through the process, which calculated the depth difference between each accepted crossline sounding and a &quot;QC&quot; BASE (CUBE-type, 2 m resolution) surface’s depth layer created from the mainscheme data. QC surfaces were created with the same parameters used for 2 m surfaces as the final surfaces, with the important distinction that the QC surfaces did not include crosslines so as to not bias the results. Differences in depth were grouped by beam number and statistics were computed, including the percentage of soundings with differences from the QC surface falling within IHO Order 1a.

When at least 95% of the sounding differences exceed IHO Order 1a, the crossline was considered to “pass,” but when less than 95% of the soundings compare within IHO Order 1, the crossline was considered to “fail.” A 5% (or less) failure rate was considered acceptable since this approach compares soundings to a surface (instead of a surface to a surface), allowing for the possibility that noisy crossline soundings that don't adversely affect the final surface(s) could be counted as a QC failure under this process. Lines used as crosslines and their % of soundings passing IHO Order 1a, sorted from highest passing to lowest, are listed below. 

2192-Bunny-347-J2-XL2 -- 100.0% pass
2052-Bunny-346-J-XL_02 -- 100.0% pass
2014-Bunny-346-J1-XL3 -- 100.0% pass
2013-Bunny-346-J1-XL2 -- 100.0% pass
2011-Bunny-346-J1-XL1 -- 100.0% pass
1286-Bunny-337-J2-XL1 -- 100.0% pass
1247-Bunny-335-J1_XL_01 -- 100.0% pass
1175-Bunny-333-J1_alt -- 100.0% pass
1174-Bunny-333-J1_alt -- 100.0% pass
1165-Bunny-333-J1_alt -- 100.0% pass
1164-Bunny-333-J1_alt -- 100.0% pass
1163-Bunny-333-J1_alt -- 99.9% pass

Note that individual crosslines often have two or more files (or segments) in CARIS due to the automatic file splitting feature in the acquisition software (QPS QINSy). For each individual crossline, all applicable segments were selected and ran together through the QC report process so that the QC report would reflect the crossline as a whole instead of its individual file segments.

Results:

Agreement between the mainscheme-only surface and crossline soundings is excellent. Compared to the mainscheme-only surface, 9 of 10 crosslines had 100% of soundings comparing within IHO Order 1a. One crossline had a 99.9% passing rate, which exceeded the 95% threshold for passing QC results.

Refer to Separate II: Digital Data for the detailed Crossline QC Reports.</ns2:discussion><ns2:comments/></ns1:crosslines><ns1:uncertainty><ns2:values><ns2:tideUncertainty><ns2:measured units="meters">0.104</ns2:measured><ns2:zoning units="meters">0</ns2:zoning><ns2:tideMethod>ERS via VDATUM</ns2:tideMethod></ns2:tideUncertainty><ns2:soundSpeedUncertainty><ns2:hullID>RV Bunny Bordelon</ns2:hullID><ns2:measuredCTD units="meters/second">0</ns2:measuredCTD><ns2:measuredMVP units="meters/second">2</ns2:measuredMVP><ns2:surface units="meters/second">0.025</ns2:surface></ns2:soundSpeedUncertainty></ns2:values><ns2:discussion>The surfaces were finalized in CARIS HIPS so that the uncertainty value for each grid cell is the greater of either standard deviation or uncertainty. The surfaces were then ran through NOAA's QC Tools &quot;QA&quot; utility to compare uncertainty values to allowable TVU by depth.

Results: Greater than 99.5% of grid cells for all final surfaces have uncertainty within the allowable TVU. The relatively few grid cells exceeding allowable TVU were found to primarily be on the edges of swaths without overlap, overlap areas exhibiting sound speed refraction error, or over features. The surfaces in these areas were examined and determined to be within specifications.

Refer to the DAPR for more information on derivation of the values used for TPU estimates.</ns2:discussion><ns2:comments/></ns1:uncertainty><ns1:junctions><ns2:discussion>This survey junctions with one Current surveys. All were surveyed concurrently with this survey.

NOAA's &quot;Gridded Surface Comparison V18.4&quot; utility was used to complete the junction comparisons. The utility differences the surfaces of the junctioning surveys and generates statistics, including the percentage of grid cells that compare to within allowable TVU. 1 m-resolution CUBE surfaces were used for all comparisons.</ns2:discussion><ns2:images><ns2:caption>Graphic showing junctions with this survey.</ns2:caption><ns2:link>SupportFiles\H13187_Survey_Junctions.jpg</ns2:link></ns2:images><ns2:junction><ns2:survey><ns2:registryNumber>H13182</ns2:registryNumber><ns2:scale>40000</ns2:scale><ns2:year>2019</ns2:year><ns2:fieldUnit>Terrasond, Ltd.</ns2:fieldUnit><ns2:relativeLocation>NW</ns2:relativeLocation></ns2:survey><ns2:discussion>Agreement is excellent between the two Current surveys.  The mean difference is 0.01 m, and greater than 99.5% of grid cells compare to within the allowable TVU.</ns2:discussion><ns2:comments/></ns2:junction><ns2:comments/></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:equipmentEffectiveness><ns2:results deviation="false"><ns2:issue><ns2:title>None Exist</ns2:title><ns2:discussion>There were no conditions or deficiencies that affected equipment operational effectiveness.</ns2:discussion><ns2:comments/></ns2:issue></ns2:results><ns2:comments/></ns1:equipmentEffectiveness><ns1:factorsAffectingSoundings><ns2:results deviation="true"><ns2:issue><ns2:title>Sound Speed Error</ns2:title><ns2:discussion>Sound speed error or refraction is common in this data set. This is observed as a general downward or upward cupping (&quot;frowning&quot; or &quot;smiling&quot;) of the seafloor MBES profiles. The issue was exacerbated by use of a dual-head MBES system, which increased swath-width in order to cover more area per LNM collected but also resulted in outer beam data that was more susceptible to induced error from variations in sound speed profiles.

In processing, lines with excessive sound speed error were analyzed to determine if better results could be obtained from manually choosing a specific sound speed profile instead of using the project default &quot;nearest in distance within time 4 hours&quot;. These are itemized later in this report.

Finally, swath filters as well as manual editing in CARIS subset mode was used to reject outer beam soundings that appeared to exceed allowable TVU (considered to be greater than 0.5 m from estimated true seafloor based on nadir depth). Manual editing often left isolated nodes or speckled edges in the final surfaces.

Crossline analysis, which included crossings of good near-nadir crossline data over outerbeam mainscheme data exhibiting sound speed error, passes within IHO Order 1a indicating final surfaces are within specifications.</ns2:discussion><ns2:images><ns2:caption>Example of sound speed error from this survey from CARIS subset. Gray soundings were considered to exceed IHO Order 1a and were rejected so as to be excluded from the final surfaces.</ns2:caption><ns2:link>SupportFiles\SVP_Example.jpg</ns2:link></ns2:images><ns2:comments/></ns2:issue><ns2:issue><ns2:title>SSS Refraction and Surface Noise</ns2:title><ns2:discussion>The SSS image quality is intermittently affected by thermocline refraction as well as water column noise due to waves at the surface, leading to variable artifacts in SSS data. SSS image quality was monitored continually during acquisition and SSS operations were stopped when it was determined that imagery quality had degraded to a point that significant objects were unlikely to be resolved. At this time either MBES-only operations were carried out with a tighter line spacing to obtain Complete Coverage, or vessel downtime due to weather was commenced.</ns2:discussion><ns2:comments/></ns2:issue></ns2:results><ns2:comments/></ns1:factorsAffectingSoundings><ns1:soundSpeedMethods><ns1:castFrequency>2 hours</ns1:castFrequency><ns1:discussion>Sound speed profiles (&quot;casts&quot;) were collected while underway. A combination of AML Minos-X, Valeport RapidSV, and Valeport SWIFT SVP profilers were used over the course of the project. Changes in sound speed at the MBES sonar head were monitored and a sound speed profile was acquired when the sound speed at the head differed from the sound speed at the depth of the sonar head in the previous profile by greater than 2 m/s. This resulted in an interval of approximately 2 hours between subsequent casts. Casts were taken as deep as possible, usually extending to the seafloor. These were normally applied nearest in distance in time within 4 hours in CARIS HIPS to exclude profiles too outdated or distant from the applicable sounding data. Refer to the DAPR for more information on SVP profiling including specific instruments used, SVP confidence checks performed, and processing methodology.</ns1:discussion><ns1:comments/></ns1:soundSpeedMethods><ns1:coverageEquipmentAndMethods><ns2:results deviation="false"><ns2:discussion>All equipment and survey methods were used as detailed in the DAPR.</ns2:discussion></ns2:results><ns2:comments/></ns1:coverageEquipmentAndMethods><ns1:additionalQualityControl><ns2:comments/></ns1:additionalQualityControl></ns1:qualityControl><ns1:echoSoundingCorrections><ns1:corrections><ns2:results deviation="true"><ns2:discussion>SVP Profile Exceptions

As described earlier, in processing, lines with excessive sound speed error were analyzed to determine if better results could be obtained from manually choosing a specific sound speed profile instead of using the project default &quot;nearest in distance within time 4 hours&quot;. To apply in CARIS, this necessitated placing individual casts in their own CARIS SVP file and applying using the custom file instead of the sheet-wide file which contained all casts. These were also required utilizing a custom time allowance instead of the standard 4-hour cast selection criteria. These files are included with the CARIS SVP data and were applied as follows:

JD332

Used Line_1152-Bunny-332-J1-224_-_0003_JD332_2312.svp to force the below-named lines to use the JD332 2312 SVP profile.
	1152-Bunny-332-J1-224_-_0003
	
Used Line_1150-Bunny-332-J1-208_-_0002_JD332_1415.svp to force the below-named lines to use the JD332 1415 SVP profile.
	Line_1150-Bunny-332-J1-208_-_0002
	
Used Line_1154-Bunny-332-J1-240_-_0002_JD332_2025.svp to force the below-named lines to use the JD332 2025 SVP profile.
	1154-Bunny-332-J1-240_-_0002

Used Line_1149-Bunny-332-J1-128_-_0002_JD332_1415.svp to force the below-named lines to use the JD332 14:15 SVP profile.
	1149-Bunny-332-J1-128_-_0002
JD335

Used Line_1248-Bunny-335-J2-1_-_0001_JD336_0129.svp to force the below-named lines to use the JD336 01:29 SVP profile.
	1248-Bunny-335-J2-1_-_0001 (Nearest in distance within 4 hours)
	
Used Line_1242-Bunny-335-J1-992_-_0002_JD335_1608.svp to force the below-named lines to use the JD335 1608 SVP profile.
	1242-Bunny-335-J1-992_-_0002
	
JD336

Used Bunny_JD336_J2_line.file.numbers_1255.0002_1251.0004__1254.0001_JD336_0609.svp to force the lines named below to use the JD336 06:09 SVP profile.
	1251-Bunny-336-J2-17_-_0004 (Nearest in distance within 6 hours)
	1254-Bunny-336-J2-97_-_0001 (Nearest in distance within 4 hours)
	1255-Bunny-336-J2-49_-_0002 (Nearest in distance within 4 hours)
	1252-Bunny-336-J2-81_-_0001 (Nearest in distance)
	1255-Bunny-336-J2-49_-_0003 (Nearest in distance)
	1255-Bunny-336-J2-49_-_0004 (Nearest in distance)
	1253-Bunny-336-J2-33_-_0003 (Nearest in distance)
	1249-Bunny-336-J2-1_-_0001 (Nearest in distance)
	
Used Line_1250-Bunny-336-J2-65_-_0001_JD336_0257_0609.svp to force the named line to use JD336 0257 or 0609 SVP.
	1250-Bunny-336-J2-65_-_0001 (Nearest in distance)
	
Used Line_1253-Bunny-336-J2-33_-_0001_JD336_0257.svp to force the named line to use JD336 0257 SVP.
	1253-Bunny-336-J2-33_-_0001 (Nearest in time)
	
Used Line_1273-Bunny-336-J2-113_-_0002_JD337_0122.svp to force the named line to use JD337 0122 SVP.
	1273-Bunny-336-J2-113_-_0002 (Nearest in distance within 6 hours)
	1273-Bunny-336-J2-113_-_0001 (Nearest in distance)
	1264-Bunny-336-J2-129_-_0004 (Nearest in distance)
	
Used Line_1254-Bunny-336-J2-97_-_0004_JD336_0257.svp to force the named line to use JD336 0257 SVP.
	1254-Bunny-336-J2-97_-_0004_JD336_0257
	1254-Bunny-336-J2-97_-_0003 (Nearest in distance within 4 hours)
	1252-Bunny-336-J2-81_-_0004 (Nearest in distance)

Used Line_1254-Bunny-336-J2-97_-_0002_JD336_0609.svp to force the named line to use JD336 0609 SVP.
	1254-Bunny-336-J2-97_-_0002

Used Line_1256-Bunny-336-J2-145_-_0003_JD336_0801.svp to force the named line to use JD336 0801 SVP.
	1256-Bunny-336-J2-145_-_0003 (Nearest in distance)
	1258-Bunny-336-J2-177_-_0003 (Nearest in distance)
	1258-Bunny-336-J2-177_-_0002 (Nearest in distance)
	1258-Bunny-336-J2-177_-_0001 (Nearest in distance)

Used Line_1260.0004_1262.0003_JD336_1305.svp to force the named line to use JD336 1305 SVP.
	1260-Bunny-336-J2-193_-_0004 (Nearest in distance)
	1262-Bunny-336-J2-209_-_0003 (Nearest in distance)
	1260-Bunny-336-J2-193_-_0003 (Nearest in distance)
	1262-Bunny-336-J2-209_-_0002 (Nearest in distance)

Used Line_1263-Bunny-336-J2-161_-_0003_JD336_1525.svp to force the named line to use JD336 1525 SVP.
	1263-Bunny-336-J2-161_-_0003

Use Nearest Time for SVP correction lines:

	1253-Bunny-336-J2-33_-_0002
	1252-Bunny-336-J2-81_-_0003
	1252-Bunny-336-J2-81_-_0002
	2055-Bunny-346-SheetJ-Infill-11_-_0001
	2193-Bunny-347-SheetJ-Infill-11_-_0001</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:backscatter><ns2:results acquired="true"><ns2:discussion>All equipment and survey methods were used as detailed in the DAPR.</ns2:discussion></ns2:results><ns2:comments/></ns1:backscatter><ns1:dataProcessing><ns1:drSoftware><ns1:bathySoftware deviation="false"><ns1:manufacturer xsi:nil="true"></ns1:manufacturer><ns1:name xsi:nil="true"></ns1:name><ns1:version xsi:nil="true"></ns1:version></ns1:bathySoftware><ns1:imagerySoftware deviation="false"><ns1:manufacturer xsi:nil="true"></ns1:manufacturer><ns1:name xsi:nil="true"></ns1:name><ns1:version xsi:nil="true"></ns1:version></ns1:imagerySoftware><ns1:featureObjectCatalog>NOAA Profile V_5_7</ns1:featureObjectCatalog><ns1:discussion>NOAA Extended Attribute File V5.7 was used as the most current feature file version at the commencement of survey acquisition.</ns1:discussion><ns1:comments/></ns1:drSoftware><ns1:surfaces><ns1:surface><ns2:surfaceName>H13187_MB_1m_MLLW_Final</ns2:surfaceName><ns2:surfaceType>CARIS Raster Surface (CUBE)</ns2:surfaceType><ns2:resolution units="meters">1</ns2:resolution><ns2:depthRange><ns2:min units="meters">0</ns2:min><ns2:max units="meters">20</ns2:max></ns2:depthRange><ns2:surfaceParameter>NOAA_1m</ns2:surfaceParameter><ns2:purpose>Complete MBES</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceName>H13187_MB_2m_MLLW_Final</ns2:surfaceName><ns2:surfaceType>CARIS Raster Surface (CUBE)</ns2:surfaceType><ns2:resolution units="meters">2</ns2:resolution><ns2:depthRange><ns2:min units="meters">18</ns2:min><ns2:max units="meters">40</ns2:max></ns2:depthRange><ns2:surfaceParameter>NOAA_2m</ns2:surfaceParameter><ns2:purpose>Complete MBES</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceName>H13187_SSSAB_1m_400kHz</ns2:surfaceName><ns2:surfaceType>SSS Mosaic</ns2:surfaceType><ns2:resolution units="meters">1</ns2:resolution><ns2:depthRange><ns2:min units="meters">0</ns2:min><ns2:max units="meters">40</ns2:max></ns2:depthRange><ns2:surfaceParameter>N/A</ns2:surfaceParameter><ns2:purpose>100% SSS</ns2:purpose></ns1:surface><ns1:discussion>The final depth information for this survey was submitted as CARIS BASE surfaces (CSAR format) which best represented the seafloor at the time of the survey. The surfaces were created from fully processed data with all final corrections applied. Surfaces were created using NOAA CUBE parameters and resolutions by depth range in conformance with the 2018 HSSD. Surfaces were finalized, and designated soundings were applied. Horizontal projection was selected as UTM Zone 14 North, NAD83. Non-finalized versions of the CSAR surfaces are also included which do not have a depth cutoff applied. These do not have the &quot;_Final&quot; designation in the filename.

A crossline QC surface is also included with the surface deliverables (&quot;H13187_XLQC-MS-only_2m&quot;). This is the 2 m resolution CUBE surface in CSAR format discussed previously in the crossline section used to create the crossline QC reports. This surface excludes crosslines. It is included for reference only and should not be used for charting.

SSS mosaics were exported from Chesapeake SonarWiz 7 software at 1 m resolution using a grayscale pallet per the 2018 HSSD. The grayscale coverages are not the SonarWiz default color pallet, which is a bronze color -- as a result the grayscale images appear rougher and less visually appealing than the bronze images. Therefore, bronze color versions are also included for reference and are recommended for use over the grayscale versions.

An S-57 (.000) Final Feature File (FFF) was submitted with the survey deliverables as well. The FFF contains meta-data and other data not readily represented by the final surfaces, including bottom samples and feature investigation results. An S-57 SSS contact file is also included. Each object is encoded with mandatory S-57 attributes and NOAA Extended Attributes (V#5.7).</ns1:discussion><ns1:comments/></ns1:surfaces><ns1:additionalDataProcessing><ns2:comments/></ns1:additionalDataProcessing></ns1:dataProcessing></ns1:dataAcquisitionAndProcessing><ns1:verticalAndHorizontalControl><ns1:discussion>Additional information discussing the vertical or horizontal control for this survey can be found in the accompanying HVCR.</ns1:discussion><ns1:verticalControl><ns2:verticalDatum>Mean Lower Low Water</ns2:verticalDatum><ns2:tideStations/><ns2:standard_or_ERZT used="false" xsi:nil="true"/><ns2:VDATUM_or_constantSep used="true"><ns2:methodsUsed>ERS via VDATUM</ns2:methodsUsed><ns2:ellipsoidToChartDatumSepFile><ns2:fileName>VDATUM_Outline_Shape_xyNAD83-MLLW_geoid12b.csar</ns2:fileName></ns2:ellipsoidToChartDatumSepFile><ns2:discussion>Reduction to MLLW was accomplished using ERS methodology via VDATUM. The VDATUM model was provided by NOAA prior to operations and had an uncertainty specified as 10.4 cm. The VDATUM model was validated during this survey using comparisons with NWLON gauge data and found to be acceptable for tidal reduction. See the HVCR for validation reports.</ns2:discussion><ns2:comments/></ns2:VDATUM_or_constantSep><ns2:comments/></ns1:verticalControl><ns1:horizontalControl><ns2:horizontalDatum>North American Datum 1983</ns2:horizontalDatum><ns2:projection>Projected UTM 14</ns2:projection><ns2:PPK used="true"><ns2:methodsUsed>Smart Base</ns2:methodsUsed><ns2:baseStations/><ns2:discussion>Applanix Smart Base (ASB) was used as a comparison against Trimble PP-RTX results, and generally compared to 0.10 m or better.</ns2:discussion><ns2:comments/></ns2:PPK><ns2:PPP used="true"><ns2:discussion>All positions were post-processed in Applanix POSPac MMS software using Trimble PP-RTX as the correction source. RMS errors were generally at 0.10 m or better, both horizontally and vertically.</ns2:discussion><ns2:comments/></ns2:PPP><ns2:RTK used="false" xsi:nil="true"/><ns2:DGPS used="false" xsi:nil="true"/><ns2:WAAS used="true"><ns2:discussion>WAAS was used for real-time positioning only, and was replaced in post-processing with PP-RTX solutions for final MBES data. However SSS positions were not post-processed and are therefore based on WAAS positioning.</ns2:discussion><ns2:comments/></ns2:WAAS><ns2:comments/></ns1:horizontalControl><ns1:additionalIssues><ns2:comments/></ns1:additionalIssues></ns1:verticalAndHorizontalControl><ns1:resultsAndRecommendations><ns1:chartComparison><ns1:methods><ns2:discussion>The chart comparison was performed by examining the best-scale Electronic Navigational Charts (ENCs) that intersect the survey area. The latest edition(s) available at the time of the review were used. The chart comparison was accomplished by overlaying the finalized BASE surfaces with shoal-biased soundings, and final feature file on the charts in CARIS HIPS. The general agreement between charted soundings and survey soundings was then examined and a more detailed comparison was undertaken for any shoals or other dangerous features. In areas where a large scale chart overlapped with a small scale chart, only the larger scale chart was examined. 

USCG LNM and NMs applicable to the survey area issued subsequent to the start of operations and prior to completion of operations were also examined. This consisted of LNM/NMs 48/18 through 51/18. None were found that were applicable to this survey.

When comparing to survey data, chart scale was taken into account so that 1 mm at chart scale was considered to be the valid radius for charted soundings and features. 

It is recommended that in all cases of disagreement this survey should supersede charted data. Results are shown in the following sections. </ns2:discussion><ns2:comments/></ns1:methods><ns1:charts><ns2:ENC><ns2:chart><ns2:name>US5TX32M</ns2:name><ns2:scale>50000</ns2:scale><ns2:edition>30</ns2:edition><ns2:updateApplicationDate>2018-07-13</ns2:updateApplicationDate><ns2:issueDate>2019-03-11</ns2:issueDate><ns2:preliminary>false</ns2:preliminary></ns2:chart><ns2:discussion>There is very little overlap between this chart and survey H13187. No charted soundings intersect the survey extents. However, the nearest charted soundings to the overlap area agree to this survey to within 0.5 m or better.
</ns2:discussion><ns2:comments/></ns2:ENC><ns2:ENC><ns2:chart><ns2:name>US4TX31M</ns2:name><ns2:scale>80000</ns2:scale><ns2:edition>26</ns2:edition><ns2:updateApplicationDate>2019-03-11</ns2:updateApplicationDate><ns2:issueDate>2019-03-19</ns2:issueDate><ns2:preliminary>false</ns2:preliminary></ns2:chart><ns2:discussion>General sounding agreement is excellent, with most soundings agreeing to 0.5 m or better. No trends in deepening or shoaling were observed.</ns2:discussion><ns2:images><ns2:caption>Soundings from this survey (blue) overlaid on soundings from US4TX31M. SW part of survey area. Soundings in meters.</ns2:caption><ns2:link>SupportFiles\US4TX31M_SW.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>Soundings from this survey (blue) overlaid on soundings from US4TX31M. NE part of survey area. Soundings in meters.</ns2:caption><ns2:link>SupportFiles\US4TX31M_NE.jpg</ns2:link></ns2:images><ns2:comments/></ns2:ENC><ns2:comments/></ns1:charts><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:chartedFeatures><ns2:results investigated="None Exist"><ns2:discussion>No charted features exist for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:chartedFeatures><ns1:unchartedFeatures><ns2:results investigated="None Exist"><ns2:discussion>No uncharted features exist for this survey that are not discussed elsewhere in this report.</ns2:discussion></ns2:results><ns2:comments/></ns1:unchartedFeatures><ns1:shoalAndHazardousFeatures><ns2:results investigated="Investigated"><ns2:discussion>Shoal and hazardous features in this area consisted primarily of offshore platforms, discussed in later in this report.

Two DTONs were submitted for this survey -- on an uncharted platform and an obstruction:

1. An uncharted platform was found at 28-24-39.1896 N, 96-02-51.76464 W. A photo was taken. Position was derived from MBES soundings on the feature.

2. An obstruction, likely a wellhead, was found at 28-25-19.61184 N, 96-02-21.54804W. The obstruction was picked up in two overlapping MBES lines as well as a 100% SSS pass.

Refer to the FFF for details. DTON submission correspondence is included with the deliverables. Note that DTONs were submitted shortly before submittal of this survey and therefore DTON confirmations / DREG registration emails were not available at the time of compilation of this report.</ns2:discussion></ns2:results><ns2:comments/></ns1:shoalAndHazardousFeatures><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:bottomSamples><ns2:results investigated="Investigated"><ns2:discussion>12 samples were assigned in the project PRF. Samples were successfully obtained at all locations. Photographs were taken but samples were discarded. Bottom sample results are provided in the accompanying FFF.</ns2:discussion></ns2:results><ns2:comments/></ns1:bottomSamples></ns1:chartComparison><ns1:additionalResults><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:priorSurveys><ns2:results investigated="None Exist"><ns2:discussion>No prior survey comparisons were required for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:priorSurveys><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:overheadFeatures><ns2:results investigated="None Exist"><ns2:discussion>No overhead features exist for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:overheadFeatures><ns1:submarineFeatures><ns2:results investigated="Investigated"><ns2:discussion>Charted pipelines exist in the area but were not readily discernible in the survey data. None were found to be elevated or of navigational concern. All are recommended for retention in the FFF.</ns2:discussion></ns2:results><ns2:comments/></ns1:submarineFeatures><ns1:platforms><ns2:results investigated="Investigated"><ns2:discussion>Charted platforms were assigned in the CSF and investigated. Most were found to exist but were commonly 20 to 70 m from the charted/assigned position. Confirmed platforms were photographed when possible, and final positions were derived from the MBES sounding data acquired on their support structure. Platforms not observed were disproved with Complete MBES coverage.

An uncharted platform and uncharted wellhead were found and submitted as DTONs, as described earlier in this report.

 Investigation results are available in the accompanying FFF.</ns2:discussion></ns2:results><ns2:comments/></ns1:platforms><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: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:otherResults><ns2:comments/></ns1:otherResults><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:insetRecommendation><ns2:results recommended="false"><ns2:discussion>No new insets are recommended for this area.</ns2:discussion></ns2:results><ns2:comments/></ns1:insetRecommendation></ns1:additionalResults></ns1:resultsAndRecommendations><ns1:approvalSheet><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: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 document as well as the Hydrographic Survey Project Instructions and Statement of Work. This data is adequate to supersede charted data in their common areas. This survey is complete and no additional work is required with the exception of deficiencies--if any--noted in the Descriptive Report.</ns1:adequacyOfSurvey><ns1:additionalInfo xsi:nil="true"></ns1:additionalInfo></ns1:statements><ns1:signingPersonnel><ns2:approverName>Andrew Orthmann, C.H.</ns2:approverName><ns2:approverTitle>TerraSond Charting Program Manager</ns2:approverTitle><ns2:approvalDate>2019-05-03</ns2:approvalDate></ns1:signingPersonnel><ns1:additionalReports><ns2:reportName>Coast Pilot Report</ns2:reportName><ns2:reportDateSent>2019-04-25</ns2:reportDateSent></ns1:additionalReports><ns1:additionalReports><ns2:reportName>VDatum Validation Report for Port Lavaca</ns2:reportName><ns2:reportDateSent>2019-04-24</ns2:reportDateSent></ns1:additionalReports><ns1:additionalReports><ns2:reportName>NCEI Sound Speed Data Submission</ns2:reportName><ns2:reportDateSent>2019-04-09</ns2:reportDateSent></ns1:additionalReports><ns1:additionalReports><ns2:reportName>Marine Mammal Observers Training Logsheet and Observation Logs</ns2:reportName><ns2:reportDateSent>2019-03-22</ns2:reportDateSent></ns1:additionalReports><ns1:additionalReports><ns2:reportName>Port Lavaca Boat Float Tide Analysis</ns2:reportName><ns2:reportDateSent>2018-09-18</ns2:reportDateSent></ns1:additionalReports></ns1:approvalSheet></ns1:descriptiveReport>