<?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-K414-NRT4-NRT4-17</ns2:number><ns2:name>Galveston Bay and Vicinity</ns2:name><ns2:generalLocality>Central Galveston Bay</ns2:generalLocality><ns2:fieldUnit>Navigation Response Team 4</ns2:fieldUnit></ns1:projectMetadata><ns1:registryMetadata><ns2:registryNumber>H12392</ns2:registryNumber><ns2:sheetID>1</ns2:sheetID><ns2:registryInstructions>The regional Navigation Manager has received pilot and port authority requests for hydrographic surveys in Galveston Bay and vicinity. The main purpose of this project is to survey the newly charted barge channels along the main Houston Ship Channel. This survey is intended to supersede all bathymetry, seafloor features, and bottom characteristics within the assigned survey area as defined by these instructions for updating of NOAA charts 11327 and 11328.</ns2:registryInstructions><ns2:sublocality>Central Galveston Bay</ns2:sublocality><ns2:stateOrTerritory>Texas</ns2:stateOrTerritory><ns2:country>United States</ns2:country><ns2:scale>10000</ns2:scale></ns1:registryMetadata><ns1:surveyMetadata><ns2:year>2017</ns2:year><ns2:chiefOfParty>Dan Jacobs</ns2:chiefOfParty><ns2:projectType>Navigable Area</ns2:projectType><ns2:PIDate>2017-07-07</ns2:PIDate><ns2:datesOfSurvey><ns2:start>2017-08-23</ns2:start><ns2:end>2018-01-31</ns2:end></ns2:datesOfSurvey><ns2:equipmentTypes><ns2:soundingEquipment>Kongsberg EM2040C Multibeam Echosounder</ns2:soundingEquipment><ns2:imageryEquipment>Edgetech 4125 Side Scan Sonar</ns2:imageryEquipment></ns2:equipmentTypes><ns2:acquisition><ns2:units>meters</ns2:units></ns2:acquisition><ns2:horizontalCoordinateSystem zone="15N">nsverse Mercator (UTM)</ns2:horizontalCoordinateSystem><ns2:timeZone>UTC</ns2:timeZone><ns2:verifier>Pacific Hydrographic Branch</ns2:verifier><ns2:titlesheetRemarks><ns2:fieldRemarks>H12392 Mulitbeam Sonar concurrent with Side Scan Sonar data collection (i.e. Skunk Striping) began in August, 2017.  However, two weeks into the project NRT4 survey assets and priorities abruptly shifted to hurricane response operations in Texas, Florida and Mississippi.  Unprecedented flooding in the greater Houston Region had doubtlessly changed the depths in Galveston Bay as a result of Hurricane Harvey.
In November 2017, NRB proposed NRT4 assess the feasibility of salvaging and submitting some of the H12392 pre-hurricane soundings by rerunning an original argyle cross line and performing a surface difference analysis.  Results of this analysis showed the Houston Ship Channel and its abutting edges to the barge lanes had seen significant change but that the soundings/imagery in the barge lanes proper were in closer (95 percent IHO confidence level) agreement  Thus, it was decided NRT4's course of action would be to acquire soundings/imagery in the barge lanes wherever necessary but exclude the Houston Ship Channel altogether on account of increasingly foul, winter weather.</ns2:fieldRemarks><ns2:branchRemarks xsi:nil="true"></ns2:branchRemarks></ns2:titlesheetRemarks></ns1:surveyMetadata><ns1:assignment>NOAA</ns1:assignment></ns1:metadata><ns1:areaSurveyed><ns1:areaDescription><ns2:discussion>This object detection survey was accomplished with 200 percent side scan sonar coverage concurrent with object detection, MBES bathymetry.  Operations commenced on DN345 (2017) and concluded on DN031 (2018).  </ns2:discussion><ns2:limits><ns2:northWest><ns2:latitude hemisphere="N">29.612193</ns2:latitude><ns2:longitude hemisphere="W">94.953375</ns2:longitude></ns2:northWest><ns2:southEast><ns2:latitude hemisphere="N">29.488875</ns2:latitude><ns2:longitude hemisphere="W">94.865225</ns2:longitude></ns2:southEast></ns2:limits><ns2:images><ns2:caption>H12392 Survey Sheet Limits (green dashed line), Chart 11327, 47 Ed.</ns2:caption><ns2:link>file:///M:/OPRK414NRT417/Surveys/H12392/Office_Processing/Reports_office/Support_Files/Graphics/H12392_sheet_limits.PNG</ns2:link></ns2:images><ns2:comments/></ns1:areaDescription><ns1:surveyLimits><ns2:results deviation="true"><ns2:discussion>NRT4 did not obtain total object detection coverage to the sheet limits of H12392.  Shoals adjacent to commercial shipping traffic generated considerable wakes which precluded a safe approach and/or suitable sea state for surveying, particularly near Red Fish Island Shoal.  Likewise, frequent barge, tanker and commercial fishing traffic all prevented comprehensive, object detection coverage in the vicinity of the Bulkhead Reef spoil area (northern end of the sheet).  Areas of missed Side Scan coverage are outlined in Figures 2-10 shown below.</ns2:discussion><ns2:images><ns2:caption>Index of H12392 100% SSS missed coverage, Chart 11237</ns2:caption><ns2:link>file:///M:/OPRK414NRT417/Surveys/H12392/Office_Processing/Reports_office/Support_Files/Graphics/SSS_Coverage_1.PNG</ns2:link></ns2:images><ns2:images><ns2:caption>100% SSS missed coverage, Inset 1</ns2:caption><ns2:link>file:///M:/OPRK414NRT417/Surveys/H12392/Office_Processing/Reports_office/Support_Files/Graphics/SSS_Coverage_2.PNG</ns2:link></ns2:images><ns2:images><ns2:caption>100% SSS missed coverage, Inset 2</ns2:caption><ns2:link>file:///M:/OPRK414NRT417/Surveys/H12392/Office_Processing/Reports_office/Support_Files/Graphics/SSS_Coverage_3.PNG</ns2:link></ns2:images><ns2:images><ns2:caption>100% SSS missed coverage, Inset 3</ns2:caption><ns2:link>file:///M:/OPRK414NRT417/Surveys/H12392/Office_Processing/Reports_office/Support_Files/Graphics/SSS_Coverage_4.PNG</ns2:link></ns2:images><ns2:images><ns2:caption>100% SSS missed coverage, Inset 4</ns2:caption><ns2:link>file:///M:/OPRK414NRT417/Surveys/H12392/Office_Processing/Reports_office/Support_Files/Graphics/SSS_Coverage_5.PNG</ns2:link></ns2:images><ns2:images><ns2:caption>Index of H12392 200% SSS missed coverage, Chart 11237</ns2:caption><ns2:link>file:///M:/OPRK414NRT417/Surveys/H12392/Office_Processing/Reports_office/Support_Files/Graphics/SSS_Coverage_6.PNG</ns2:link></ns2:images><ns2:images><ns2:caption>200% SSS missed coverage, Inset 1</ns2:caption><ns2:link>file:///M:/OPRK414NRT417/Surveys/H12392/Office_Processing/Reports_office/Support_Files/Graphics/SSS_Coverage_7.PNG</ns2:link></ns2:images><ns2:images><ns2:caption>200% SSS missed coverage, Inset 2</ns2:caption><ns2:link>file:///M:/OPRK414NRT417/Surveys/H12392/Office_Processing/Reports_office/Support_Files/Graphics/SSS_Coverage_8.PNG</ns2:link></ns2:images><ns2:images><ns2:caption>200% SSS missed coverage, Inset 3</ns2:caption><ns2:link>file:///M:/OPRK414NRT417/Surveys/H12392/Office_Processing/Reports_office/Support_Files/Graphics/SSS_Coverage_9.PNG</ns2:link></ns2:images></ns2:results><ns2:comments/></ns1:surveyLimits><ns1:surveyPurpose><ns2:discussion>The regional Navigation Manager has received pilot and port authority requests for hydrographic surveys in Galveston Bay and vicinity. The main purpose of this project is to survey the newly charted barge channels along the main Houston Ship Channel. This survey is intended to supersede all bathymetry, seafloor features, and bottom characteristics within the assigned survey area as defined by these instructions for updating of NOAA charts 11327 and 11328.</ns2:discussion><ns2:comments/></ns1:surveyPurpose><ns1:surveyQuality><ns2:adequacy>The entire survey is adequate to supersede previous data.</ns2:adequacy><ns2:discussion>At the 95 percent confidence interval, the entire survey is adequate to supersede previous data.</ns2:discussion><ns2:comments/></ns1:surveyQuality><ns1:surveyCoverage><ns2:coverageRequirement><ns2:waterDepth>Using Argyle Pattern Crossline, (i.e. zig-zag pattern) seek the 9 foot curve, per project instructions.</ns2:waterDepth><ns2:requiredCoverage>Object Detection</ns2:requiredCoverage></ns2:coverageRequirement><ns2:results deviation="true"><ns2:discussion>Commercial shipping traffic, commercial fishing operations and inclement winter weather (fog, ice, high winds and unfavorable sea states) all  precluded 100 percent object detection coverage to the sheet limits of H12392 during this late field season project.  NRT4 focused hydrography to barge lanes in an effort to capture the essence of the project's stated purpose &quot;to survey the newly charted barge channels along the main Houston Ship Channel&quot; per the project's registry instructions.  Please reference A.1 of this Descriptive Report for specific areas where object detection Side Scan Sonar coverage were not obtained.</ns2:discussion></ns2:results><ns2:comments/></ns1:surveyCoverage><ns1:coverageGraphic><ns2:coverageGraphicImage><ns2:images><ns2:caption>H12392 MBES Coverage, Chart 11327</ns2:caption><ns2:link>file:///M:/OPRK414NRT417/Surveys/H12392/Office_Processing/Reports_office/Support_Files/Graphics/Coverage%20Graphic.PNG</ns2:link></ns2:images></ns2:coverageGraphicImage></ns1:coverageGraphic><ns1:surveyStatistics><ns2:LNM><ns2:vesselLNM><ns2:vessel><ns2:hullID>S3008</ns2:hullID><ns2:statistics><ns2:MS_SBES>0</ns2:MS_SBES><ns2:MS_MBES>0</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>140</ns2:MS_MBES_SSS><ns2:MS_SBES_SSS>0</ns2:MS_SBES_SSS><ns2:XL_MBES_SBES>14</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>0</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>139</ns2:MS_MBES_SSS><ns2:MS_SBES_SSS>0</ns2:MS_SBES_SSS><ns2:XL_MBES_SBES>14</ns2:XL_MBES_SBES><ns2:XL_lidar>0</ns2:XL_lidar><ns2:percentXLLNM>10</ns2:percentXLLNM></ns2:totalLNM></ns2:LNM><ns2:totalSurveyStats><ns2:bottomSamples>0</ns2:bottomSamples><ns2:maritimeBoundaryPoints>0</ns2:maritimeBoundaryPoints><ns2:DP>0</ns2:DP><ns2:diveOps>0</ns2:diveOps><ns2:SNM>2.4</ns2:SNM></ns2:totalSurveyStats><ns2:surveyDates>2017-11-30</ns2:surveyDates><ns2:surveyDates>2018-01-31</ns2:surveyDates><ns2:discussion>Data collection for H12392 originally began on DN223 (11AUG2017) through DN236 (24AUG2017).  Survey operations were interrupted as Hurricane Harvey entered Texas waters.  Reacquisition for H12392 recommenced on DN334 (30NOV2017) and concluded on DN031 (31JAN2018) because pre hurricane data exhibited poor agreement with these more recent soundings.  Pre hurricane SSS/MBES lines totaled 125 Linear Nautical Miles and were not included in the project submission folder.</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>S3008</ns2:hullID><ns2:LOA units="meters">10</ns2:LOA><ns2:draft units="meters">0.5</ns2:draft></ns1:vessel><ns1:images><ns2:caption>S3008</ns2:caption><ns2:link>file:///M:/OPRK414NRT417/Surveys/H12392/Office_Processing/Reports_office/Support_Files/Graphics/Best_Boat.JPG</ns2:link></ns1:images><ns1:discussion>S008 is an aluminum survey vessel manufactured by Lake Assault Boats of Duluth, MN.  It was assigned to NRT4 in the Fall of 2016 and was integrated with a hull mounted multibeam sonar and pole mounted side scan sonar in the weeks preceding the 2017 Field Season.  The vessel is approximately 34 feet in length with a beam of 8 feet and a draft 1.6 feet.  Its powered by two Honda 225 HP outboard engines.  A side scan winch and davit are installed and configurable for either port or starboard gunnel deployment just ahead of the stern.  Additionally, a pole mount my be installed via hardware and tooling plates built onto the port and starboard gunwales amidship.  The vessel may accommodate up to 4 persons and typically sees operation in bays and harbors where depths are between 4 to 50 meters.  </ns1:discussion><ns1:comments/></ns1:vessels><ns1:equipment><ns1:majorSystem><ns2:manufacturer>EdgeTech</ns2:manufacturer><ns2:model>4125</ns2:model><ns2:type>SSS</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>Kongsberg Maritime</ns2:manufacturer><ns2:model>EM 2040C</ns2:model><ns2:type>MBES</ns2:type></ns1:majorSystem><ns1:discussion>Please reference NRT4's 2017 DAPR for equipment specifications.</ns1:discussion><ns1:comments/></ns1:equipment><ns1:comments/></ns1:equipmentAndVessels><ns1:qualityControl><ns1:crosslines><ns2:discussion>The crosslines for H12392 were collected in an &quot;argyle&quot; zig-zag pattern transecting the edge of the sheet limit polygon to approximately 3 meters depth.  This method, prescribed by the Pacific Hydrographic Branch will aid cartographers in determining up-to-date depth contours flanking the Houston Ship Channel and adjoining barge lanes.  10 percent (14 linear nautical miles) of crossline miles were acquired as compared to main scheme miles (140 linear nautical miles).  </ns2:discussion><ns2:comments/></ns1:crosslines><ns1:uncertainty><ns2:values><ns2:tideUncertainty><ns2:measured units="meters">0.090</ns2:measured><ns2:zoning units="meters">0.00</ns2:zoning><ns2:tideMethod>TCARI</ns2:tideMethod></ns2:tideUncertainty><ns2:soundSpeedUncertainty><ns2:hullID>S3008</ns2:hullID><ns2:measuredCTD units="meters/second">4.0</ns2:measuredCTD><ns2:measuredMVP units="meters/second">0.0</ns2:measuredMVP><ns2:surface units="meters/second">1.0</ns2:surface></ns2:soundSpeedUncertainty></ns2:values><ns2:discussion>Tide uncertainty for the project area was 0.09 meters at one sigma.  This value was doubled to 0.18 meters during TPU calculation as CARIS outputs a two sigma value.  Total Vertical Uncertainty (TVU) calculation was calculated via Pydro's Grid QA tool.  The finalized grid passed with better than 99 percent of grid nodes falling inside the IHO Order 1a error budget.  Similarly, the survey's object detection sounding density requirements were satisfied as 99 percent of finalized, 50cm grid nodes contained at least 5 soundings per node.  See uncertainty graphs, below.</ns2:discussion><ns2:images><ns2:caption>TCARI Uncertainty</ns2:caption><ns2:link>file:///M:/OPRK414NRT417/Surveys/H12392/Office_Processing/Reports_office/Support_Files/Graphics/Tide_Error_grab.PNG</ns2:link></ns2:images><ns2:images><ns2:caption>Total Vertical Uncertainty calculation for H12392 Finalized CUBE Surface</ns2:caption><ns2:link>file:///M:/OPRK414NRT417/Surveys/H12392/Office_Processing/Reports_office/Support_Files/Graphics/H12392_MB_50cm_MLLW_Final.QAv5.tvu_qc.png</ns2:link></ns2:images><ns2:images><ns2:caption>Soundings Density Statistics for H12392 Finalized CUBE Surface.</ns2:caption><ns2:link>file:///M:/OPRK414NRT417/Surveys/H12392/Office_Processing/Reports_office/Support_Files/Graphics/H12392_MB_50cm_MLLW_Final.QAv5.density.png</ns2:link></ns2:images><ns2:comments/></ns1:uncertainty><ns1:junctions><ns2:discussion>H12392 50cm grid nodes were compared to historic (2013) H12391 50cm grid nodes invoking the Pydro Surface Difference Tool.  The overlapping nodes did not meet IHO specifications as only 85 percent passed the allowable error fraction.  Sounding disagreement is common from year to year in this waterway as sedimentation from numerous rivers and bayous is constantly occurring.   Consequently, a four year lapse between adjoining surveys and a major flooding event (Hurricane Harvey) both likely contributed to this sounding comparison discrepancy.  Moreover, the USACE and Houston Pilots are cognizant of this shoaling and contract dredging operations are nearly continuous throughout the bay.</ns2:discussion><ns2:images><ns2:caption>50cm Overlap Difference Surface, H12392 minus H12391</ns2:caption><ns2:link>file:///M:/OPRK414NRT417/Surveys/H12392/Office_Processing/Reports_office/Support_Files/Graphics/H12392_MB_50cm_MLLW_Final-H12391_MB_50cm_MLLW_1of1_fracAllowErr_Freq.png</ns2:link></ns2:images><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="true"><ns2:issue><ns2:title>Bubble Sweep Artifacts</ns2:title><ns2:discussion>Bubble Sweep Artifacts we observed throughout the survey.  Although the noise artifact has historically been more prevalent in heavier seas (15 knot plus  winds), this issue seemed to persist even in relatively calmer sea states (5-10 knot winds).  Despite the Hydrographer's best efforts to mitigate the noise (e.g. adjust frequency to from 300 to 200 kHz and vessel speed) bubble sweep artifacts required extensive manual cleaning during post processing in CARIS Subset Editor.  NRB is investigating modification of the sonar blister mounts and hull chines on each of its NRT boats to diminish such noise.</ns2:discussion><ns2:images><ns2:caption>Bubble Sweep Artifacts</ns2:caption><ns2:link>file:///M:/OPRK414NRT417/Surveys/H12392/Office_Processing/Reports_office/Support_Files/Graphics/bubble%20sweep.PNG</ns2:link></ns2:images><ns2:comments/></ns2:issue><ns2:issue><ns2:title>SSS Banding Artifact</ns2:title><ns2:discussion>White bands across the side scan data were recorded throughout the survey. It was found that when the survey speed was reduced to &lt;4 knots the banding mostly went away. It is believed that the banding was a direct result of the sonar limitations and extreme vessel motion brought on because the side scan sonar was pole mounted. Since post processing does not change the imagery, there was nothing further that could be done for the side scan data that was already collected. Further investigation will be done before data is collected in the future.  Banding artifacts were most pronounced on DN235, DN345, and DN347.</ns2:discussion><ns2:images><ns2:caption>SSS Banding Artifact</ns2:caption><ns2:link>file:///M:/OPRK414NRT417/Surveys/H12392/Office_Processing/Reports_office/Support_Files/Graphics/SSS_Artifact2b.JPG</ns2:link></ns2:images><ns2:comments/></ns2:issue></ns2:results><ns2:comments/></ns1:equipmentEffectiveness><ns1:factorsAffectingSoundings><ns2:results deviation="true"><ns2:issue><ns2:title>Fluid Mud Layer</ns2:title><ns2:discussion>A fluid mud layer is know to exist just above a firm mud bottom owing to numerous bayous draining into Galveston Bay.  Shipping traffic propulsion and shrimp trawling operations generated turbidity plumes from this fluid mud layer some of the time.  Soundings/Imagery had to be reaquired on several occasions due to this factor.   
Sedimentation from numerous rivers and bayous upstream of Galveston Bay is constantly occurring in this waterway.  USACE and Houston Pilots are cognizant of this shoaling and contract dredging operations are continuous somewhere in the bay on any given day.</ns2:discussion><ns2:comments/></ns2:issue><ns2:issue><ns2:title>Sound Velocity </ns2:title><ns2:discussion>At times, outer beam soundings were effected by inaccurate sound speed modeling throughout the water column, evident by their &quot;frowning&quot; or falling away from an otherwise collinear bottom trace.  Such data were deleted in post processing when influencing the CUBE surface.</ns2:discussion><ns2:images><ns2:caption>&quot;Frowning&quot; sound speed artifact</ns2:caption><ns2:link>file:///M:/OPRK414NRT417/Surveys/H12392/Office_Processing/Reports_office/Support_Files/Graphics/frown.JPG</ns2:link></ns2:images><ns2:comments><ns2:branchComment><ns2:comment>The &quot;frowning&quot; effect is more likely due to MBES fliers, as the remaining data represents a well formed seabed. These edge fliers have been removed from the dataset.</ns2:comment></ns2:branchComment></ns2:comments></ns2:issue></ns2:results><ns2:comments/></ns1:factorsAffectingSoundings><ns1:soundSpeedMethods><ns1:castFrequency>Sound speed casts were taken every 4 hours IAW 2014 NOAA FPM.</ns1:castFrequency><ns1:discussion>Sound speed casts were processed in Pydro's Sound Speed Manager and applied to soundings during post processing implementing  the  &quot;Nearest in Distance, Within Time&quot; option in CARIS 10.</ns1:discussion><ns1:comments/></ns1:soundSpeedMethods><ns1:coverageEquipmentAndMethods><ns2:results deviation="true"><ns2:discussion>NRT4 attained object detection coverage by collecting 200 percent SSS coverage logged concurrently with  MBES.  Numerous SSS Lines were named with the suffix  &quot;_Fill&quot; where additional SSS coverage was required due to substandard bottom trace.  This unconventional, yet practical naming scheme was given approval by NSD's Project Manager.  His approval email pertaining to the matter may be found in the project correspondence folder. </ns2:discussion></ns2:results><ns2:comments/></ns1:coverageEquipmentAndMethods><ns1:additionalQualityControl><ns2:comments/></ns1:additionalQualityControl></ns1:qualityControl><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:issue><ns2:title>TPU Offsets Error and Waterline Error Discovered after SAR</ns2:title><ns2:discussion>PHB discovered erroneous null entries in NRT4's Multibeam HVF/TPU Offsets during SAR.  There had been previous discussion on this topic between Team Lead and NRB folks however it was thought at that time that these values should be zero.  Subsequent to the project's resubmission, NRT4 populated the HVF's &quot;MRU-Trans&quot; and &quot;NAV-Trans&quot; offset entries and their associated error values.   This way, a valid TPU calculation could occur to those offsets.  Additionally, Team Lead had accounted for the waterline measurement in Seafloor Information Systems (SIS) but was unaware this value (-0.51m) also required an HVF entry.  NRT4 made these necessary offset changes to the multibeam sonar's HVF, re SVP'd, re merged the data and recomputed TPU.  The 50cm finalized surface passed its IHO test above the 99 CI.  Accordingly, these values were also changed for the 2017 DAPR accompanying this report.  All correspondence pertaining to these matters have been documented in the Project Correspondence folder.</ns2:discussion><ns2:images><ns2:caption>TPU Offsets and Waterline missing from HVF</ns2:caption><ns2:link>file:///M:/OPRK414NRT417/Surveys/H12392/Office_Processing/Reports_office/Support_Files/Graphics/TPU_Offsets_Error_Discovered.JPG</ns2:link></ns2:images><ns2:comments/></ns2:issue><ns2:comments/></ns1:additionalIssues></ns1:echoSoundingCorrections><ns1:backscatter><ns2:results acquired="false"><ns2:discussion>Backscatter was not collected for this survey.</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>CARIS_Support_Files_Ver_5_6</ns1:featureObjectCatalog><ns1:discussion>NRT4 updated all processing computer support files with new version (5.6) name in September, 2017.</ns1:discussion><ns1:comments/></ns1:drSoftware><ns1:surfaces><ns1:surface><ns2:surfaceName>H12392_MBES_50cm_MLLW_Final</ns2:surfaceName><ns2:surfaceType>CARIS Raster Surface (CUBE)</ns2:surfaceType><ns2:resolution units="meters">0.5</ns2:resolution><ns2:depthRange><ns2:min units="meters">0.33</ns2:min><ns2:max units="meters">16.11</ns2:max></ns2:depthRange><ns2:surfaceParameter>NOAA_0.5m</ns2:surfaceParameter><ns2:purpose>Object Detection</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceName>H12392_SSSAB_1m_400kHz_1of2</ns2:surfaceName><ns2:surfaceType>SSS Mosaic</ns2:surfaceType><ns2:resolution units="meters">1</ns2:resolution><ns2:depthRange><ns2:min units="meters">1.56</ns2:min><ns2:max units="meters">16.83</ns2:max></ns2:depthRange><ns2:surfaceParameter>N/A</ns2:surfaceParameter><ns2:purpose>100% SSS</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceName>H12392_SSSAB_1m_400kHz_2of2</ns2:surfaceName><ns2:surfaceType>SSS Mosaic</ns2:surfaceType><ns2:resolution units="meters">1</ns2:resolution><ns2:depthRange><ns2:min units="meters">1.56</ns2:min><ns2:max units="meters">16.83</ns2:max></ns2:depthRange><ns2:surfaceParameter>N/A</ns2:surfaceParameter><ns2:purpose>200% SSS</ns2:purpose></ns1:surface><ns1:discussion>The finalized 1m CUBE SSS Mosaic, a 100 percent and a 200 percent side scan mosaic were generated in accordance with 2014 Field Procedures Manual, Paragraph 4.2.1.1.</ns1:discussion><ns1:comments/></ns1:surfaces><ns1:additionalDataProcessing><ns2:issue><ns2:title>Non-standard SSS Line Naming Convention</ns2:title><ns2:discussion>Numerous SSS Lines were named with the suffix  &quot;_Fill&quot; where additional SSS coverage was required due to substandard bottom trace.  This unconventional, yet practical naming scheme was given approval by NSD's Project Manager.  His approval email pertaining to the matter may be found in the project correspondence folder. </ns2:discussion><ns2:comments/></ns2:issue><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="true"><ns2:methodsUsed>TCARI</ns2:methodsUsed><ns2:correctorFiles><ns2:waterLevels><ns2:fileName>8770613.tid</ns2:fileName><ns2:status>Final Approved</ns2:status></ns2:waterLevels><ns2:waterLevels><ns2:fileName>8771013.tid</ns2:fileName><ns2:status>Final Approved</ns2:status></ns2:waterLevels><ns2:waterLevels><ns2:fileName>8771341.tid</ns2:fileName><ns2:status>Final Approved</ns2:status></ns2:waterLevels><ns2:waterLevels><ns2:fileName>8771450.tid</ns2:fileName><ns2:status>Final Approved</ns2:status></ns2:waterLevels><ns2:tideCorrectors><ns2:fileName>K414NRT42017.tc</ns2:fileName><ns2:status>Final</ns2:status></ns2:tideCorrectors></ns2:correctorFiles><ns2:finalTides><ns2:dateSubmitted>2018-02-01</ns2:dateSubmitted><ns2:dateReceived>2018-02-13</ns2:dateReceived></ns2:finalTides><ns2:discussion>Final TCARI tides were requested on February 1, 2018 and received on February 13, 2018.  The preliminary  TCARI grid was accepted as the final grid for H12392.  Please reference the Final Tide NOTE in the Descriptive Report's Appendices folder.</ns2:discussion><ns2:comments/></ns2:standard_or_ERZT><ns2:VDATUM_or_constantSep used="false" xsi:nil="true"/><ns2:comments/></ns1:verticalControl><ns1:horizontalControl><ns2:horizontalDatum>North American Datum 1983</ns2:horizontalDatum><ns2:projection>UTM Zone 15N</ns2:projection><ns2:PPK used="false" xsi:nil="true"/><ns2:PPP used="false" xsi:nil="true"/><ns2:RTK used="false" xsi:nil="true"/><ns2:DGPS used="true"><ns2:discussion>The Differential GPS (DGPS) beacon in Angleton, TX broadcasting at 301 KHz was employed for horizontal control of all survey lines for H12392.</ns2:discussion><ns2:comments/></ns2:DGPS><ns2:WAAS used="false" xsi:nil="true"/><ns2:comments/></ns1:horizontalControl><ns1:additionalIssues><ns2:comments/></ns1:additionalIssues></ns1:verticalAndHorizontalControl><ns1:resultsAndRecommendations><ns1:chartComparison><ns1:methods><ns2:discussion>A chart comparison was performed in CARIS 10 by use of a survey sounding overlay in US Survey Feet atop NOAA Chart 11327 charted soundings.  A font size of 10 with a suppression radius of 75 meters was chosen for a map scale of 10000.  The resulting survey soundings were similarly sized to charted soundings at a 1:10000 scale but nearly 3 times the density/spacing.  The Hydrographer deemed these settings adequate for a generalized comparison between survey depths and charted soundings.  </ns2:discussion><ns2:comments/></ns1:methods><ns1:charts><ns2:ENC><ns2:chart><ns2:name>11327</ns2:name><ns2:scale>25000</ns2:scale><ns2:edition>38</ns2:edition><ns2:updateApplicationDate>2018-03-24</ns2:updateApplicationDate><ns2:issueDate>2018-03-27</ns2:issueDate><ns2:preliminary>true</ns2:preliminary></ns2:chart><ns2:discussion>Notable differences between survey depths and charted sounding are listed below.  Inset 1 charted soundings were within two feet of survey depths with a deepening trend evident near the west side of Bulkhead Reef.  Inset 2 survey soundings exhibited a deeper trend by about 2 feet along Bulkhead Reef.  Inset 3 had two (2) soundings deeper than charted and a 6 foot shoal (blue tint) which likely has reduced in dimension, though not entirely esonified.  These northern reaches of Chart 11327 aside, depths in were good agreement overall, not differing by more than 2 or3 feet from charted.</ns2:discussion><ns2:images><ns2:caption>Inset 1, Sounding Comparison</ns2:caption><ns2:link>file:///M:/OPRK414NRT417/Surveys/H12392/Office_Processing/Reports_office/Support_Files/Graphics/Inset1_for_DR.PNG</ns2:link></ns2:images><ns2:images><ns2:caption>Inset 2, Sounding Comparison</ns2:caption><ns2:link>file:///M:/OPRK414NRT417/Surveys/H12392/Office_Processing/Reports_office/Support_Files/Graphics/Inset2_for_DR.PNG</ns2:link></ns2:images><ns2:images><ns2:caption>Inset 3, Sounding Comparison</ns2:caption><ns2:link>file:///M:/OPRK414NRT417/Surveys/H12392/Office_Processing/Reports_office/Support_Files/Graphics/Inset3_for_DR.PNG</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="Investigated"><ns2:discussion> Two assigned features contained the label &quot;PA&quot; for H12392.  Neither were seen in object detection MBES data or 200 SSS imagery.</ns2:discussion><ns2:images><ns2:caption>2 &quot;PA&quot; features not seen, shown inside yellow callout box.</ns2:caption><ns2:link>file:///M:/OPRK414NRT417/Surveys/H12392/Office_Processing/Reports_office/Support_Files/Graphics/PA_Objects_not_seen_final.PNG</ns2:link></ns2:images></ns2:results><ns2:comments/></ns1:chartedFeatures><ns1:unchartedFeatures><ns2:results investigated="Investigated"><ns2:discussion>New features exist, were investigated and are included in the Final Feature File (FFF) accompanying this project.  The features appear to be remnants of piles or footings belonging to structures and signage that no longer exist.  The new features do not pose a danger to navigation based on their similar height to surrounding depths or are situated below the controlling depth of barge lanes (12 feet).</ns2:discussion><ns2:images><ns2:caption>New feature, added to FFF.</ns2:caption><ns2:link>file:///M:/OPRK414NRT417/Surveys/H12392/Office_Processing/Reports_office/Support_Files/Graphics/OBST_New_6A.PNG</ns2:link></ns2:images></ns2:results><ns2:comments/></ns1:unchartedFeatures><ns1:shoalAndHazardousFeatures><ns2:results investigated="None Exist"><ns2:discussion>No shoals or potentially hazardous features exist for this survey.  Designated soundings lacking feature correlation to the FFF were created in consequence to the CUBE surface not honoring the shoalest point on the seafloor.  Such occurrences were in areas where migrating sand waves had been present or where bottom features existed but were deemed navigationally insignificant.</ns2:discussion></ns2:results><ns2:comments/></ns1:shoalAndHazardousFeatures><ns1:channels><ns2:results investigated="Investigated"><ns2:discussion>The barge lanes paralleling the Houston Shipping Channel have a controlling depth of 12 feet.  As such, the lanes were evaluated for shoals exceeding this depth limit.  Some minor shoaling (1 to 2 feet) was found encroaching the outside edges in several reaches however, discussion with USACE Galveston established these discrepancies as tolerable and not befitting for a formal Danger to Navigation report.  All electronic correspondence pertaining to this matter may be found in Appendix II of this descriptive report.  Chartlets pertaining to the matter and shared with USACE are shown below. </ns2:discussion><ns2:images><ns2:caption>Barge Lane Shoaling Chartlet, Cover Sheet</ns2:caption><ns2:link>file:///M:/OPRK414NRT417/Surveys/H12392/Office_Processing/Reports_office/Support_Files/Graphics/BargeLane1.JPG</ns2:link></ns2:images><ns2:images><ns2:caption>Chartlet Index</ns2:caption><ns2:link>file:///M:/OPRK414NRT417/Surveys/H12392/Office_Processing/Reports_office/Support_Files/Graphics/BargeLane2.JPG</ns2:link></ns2:images><ns2:images><ns2:caption>Chartlet 1</ns2:caption><ns2:link>file:///M:/OPRK414NRT417/Surveys/H12392/Office_Processing/Reports_office/Support_Files/Graphics/BargeLane3.JPG</ns2:link></ns2:images><ns2:images><ns2:caption>Chartlet 2</ns2:caption><ns2:link>file:///M:/OPRK414NRT417/Surveys/H12392/Office_Processing/Reports_office/Support_Files/Graphics/BargeLane4.JPG</ns2:link></ns2:images><ns2:images><ns2:caption>Chartlet 3</ns2:caption><ns2:link>file:///M:/OPRK414NRT417/Surveys/H12392/Office_Processing/Reports_office/Support_Files/Graphics/BargeLane5.JPG</ns2:link></ns2:images><ns2:images><ns2:caption>Chartlet 4</ns2:caption><ns2:link>file:///M:/OPRK414NRT417/Surveys/H12392/Office_Processing/Reports_office/Support_Files/Graphics/BargeLane6.JPG</ns2:link></ns2:images></ns2:results><ns2:comments/></ns1:channels><ns1:bottomSamples><ns2:results investigated="None Exist"><ns2:discussion>No bottom samples were required for this survey.</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 exist for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:priorSurveys><ns1:ATONS><ns2:results investigated="Investigated"><ns2:discussion>The 2017-2018 Eighth District Gulf Coast Local Notice to Mariners listed five (5) ATONS coincident to the H12392 survey area which had been damaged at the time of data acquisition.  All ATONS were lighted channel markers and included numbers &quot;51,&quot; 71,&quot; &quot;73,&quot;75,&quot; and &quot;76.&quot;  Marker Discrepancies for lighted channel markers &quot;71,&quot; &quot;75,&quot; and &quot;76&quot; remained uncorrected by the survey end date, 31JAN2018.  These Aids had been temporarily replaced by lighted buoys.  See LNM tabulation graphics, below.

A feature redundancy discrepancy was discovered for the Lower Galveston Bay Inner Range Front Light invoking the 2017 Features Scan (v8) tool in Pydro QC Tools.  The conflict involved duplication of a light associated to that ATON;  the 2018 USCG Light List only included 2 lights atop the range light however, 3 lights were listed in the ENC .  As a result, the discrepancy was reported to MCD through its Nautical Discrepancy Reporting System on 5JULY2018.  Email correspondences pertaining to this matter can be found in the Project Correspondence folder and show that MCD is making necessary corrections to the cell.</ns2:discussion><ns2:images><ns2:caption>USCG Local Notice to Mariner, Damaged Nav Aids.</ns2:caption><ns2:link>file:///M:/OPRK414NRT417/Surveys/H12392/Office_Processing/Reports_office/Support_Files/Graphics/Discrepancies_Federal%20Aids.PNG</ns2:link></ns2:images><ns2:images><ns2:caption>USCG Local Notice to Mariner, Corrected Nav Aids.</ns2:caption><ns2:link>file:///M:/OPRK414NRT417/Surveys/H12392/Office_Processing/Reports_office/Support_Files/Graphics/Corrected_Federal%20Aids.PNG</ns2:link></ns2:images></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>A pipeline located in the south, just outside of the sheet limits where H12392 junctioned to H12391 was charted however it was not seen in bathymetry or SSS imagery.</ns2:discussion><ns2:images><ns2:caption>Pipeline (highlighted yellow), southern end of H12392.</ns2:caption><ns2:link>file:///M:/OPRK414NRT417/Surveys/H12392/Office_Processing/Reports_office/Support_Files/Graphics/pipeline%20sub%20feature.JPG</ns2:link></ns2:images></ns2:results><ns2:comments/></ns1:submarineFeatures><ns1:platforms><ns2:results investigated="Exist - Not Investigated"><ns2:discussion>Platforms exist for this survey, but were not investigated.</ns2:discussion><ns2:images><ns2:caption>H12392 Submerged Platform, not investigated.</ns2:caption><ns2:link>file:///M:/OPRK414NRT417/Surveys/H12392/Office_Processing/Reports_office/Support_Files/Graphics/submerged%20platform.JPG</ns2:link></ns2:images></ns2:results><ns2:comments><ns2:fieldComment><ns2:comment>Tanker traffic near this 1 foot shoal generated dangerous wakes, preventing a safe approach and favorable survey conditions.</ns2:comment><ns2:initials>DJ</ns2:initials></ns2:fieldComment></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="Exist - Not Investigated"><ns2:discussion>Abnormal seafloor and/or Environmental Conditions were observed in this survey, but were not investigated.  A fluid mud layer is know to exist just above a firm mud bottom owing to numerous bayous draining into Galveston Bay.  Shipping traffic propulsion and shrimp trawling operations generated turbidity plumes from this fluid mud layer some of the time.  Soundings/Imagery had to be reacquired on several occasions due to this factor.   
Likewise, shoaling from sedimentation is persistent in this waterway.  USACE and Houston Pilots are cognizant of this shoaling and contract dredging operations are continuous throughout the bay on any given day.  Note that no dredging operations were observed inside the sheet limits at any time during acquisition of H12392.
</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:issue><ns2:title>Flier Finder v7 QC Check, 12 Fliers</ns2:title><ns2:discussion>Flier Finder v7 QC generates 12 fliers in the finalized 50cm base surface.   Fliers had been inspected and corrected numerous times to no avail and are  all the Number 3 &quot;Adjacent Cells&quot; class.  Default filter values were used for this QC check.  Output files for this check can be found in the DR's &quot;Support _Files//QC_Reports&quot; folder.  See Image below.</ns2:discussion><ns2:images><ns2:caption>12 Fliers, Flier Finder v7 Settings and Results</ns2:caption><ns2:link>file:///M:/OPRK414NRT417/Surveys/H12392/Office_Processing/Reports_office/Support_Files/Graphics/Flier_Finder_12.JPG</ns2:link></ns2:images><ns2:comments/></ns2:issue><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 and Specifications Deliverables, Field Procedures Manual, Project 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:additionalInfo xsi:nil="true"></ns1:additionalInfo></ns1:statements><ns1:signingPersonnel><ns2:approverName>Dan Jacobs</ns2:approverName><ns2:approverTitle>Chief of Party</ns2:approverTitle><ns2:approvalDate>2019-01-31</ns2:approvalDate></ns1:signingPersonnel></ns1:approvalSheet></ns1:descriptiveReport>