<?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-J317-KR-18</ns2:number><ns2:name>Approaches to Tampa Bay, FL</ns2:name><ns2:generalLocality>Approaches to Tampa Bay, FL</ns2:generalLocality><ns2:fieldUnit>Oceaneering International, Inc.</ns2:fieldUnit></ns1:projectMetadata><ns1:registryMetadata><ns2:registryNumber>H13173</ns2:registryNumber><ns2:sheetID>4</ns2:sheetID><ns2:registryInstructions>Object Detection Coverage</ns2:registryInstructions><ns2:sublocality>Egmont Channel</ns2:sublocality><ns2:stateOrTerritory>Florida</ns2:stateOrTerritory><ns2:country>United States</ns2:country><ns2:scale>20000</ns2:scale></ns1:registryMetadata><ns1:surveyMetadata><ns2:year>2018</ns2:year><ns2:chiefOfParty>Scott Melancon</ns2:chiefOfParty><ns2:projectType>Navigable Area</ns2:projectType><ns2:PIDate>2018-07-17</ns2:PIDate><ns2:datesOfSurvey><ns2:start>2018-11-09</ns2:start><ns2:end>2019-07-21</ns2:end></ns2:datesOfSurvey><ns2:equipmentTypes><ns2:soundingEquipment>Multibeam Echo Sounder</ns2:soundingEquipment><ns2:imageryEquipment>Multibeam Echo Sounder Backscatter</ns2:imageryEquipment></ns2:equipmentTypes><ns2:acquisition><ns2:units>meters</ns2:units></ns2:acquisition><ns2:horizontalCoordinateSystem zone="17N">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 17N, MLLW. All references to other horizontal or vertical datums in this report are applicable to the processed hydrographic data provided by the field unit.</ns2:branchRemarks></ns2:titlesheetRemarks></ns1:surveyMetadata><ns1:assignment>Contractor</ns1:assignment></ns1:metadata><ns1:areaSurveyed><ns1:areaDescription><ns2:discussion>The survey area is located in the vicinity of Egmont Channel at the Approaches to Tampa Bay, Florida.</ns2:discussion><ns2:limits><ns2:northWest><ns2:latitude hemisphere="N">27.650808</ns2:latitude><ns2:longitude hemisphere="W">83.046439</ns2:longitude></ns2:northWest><ns2:southEast><ns2:latitude hemisphere="N">27.503304</ns2:latitude><ns2:longitude hemisphere="W">82.754561</ns2:longitude></ns2:southEast></ns2:limits><ns2:images><ns2:caption>H13173 Survey Limits</ns2:caption><ns2:link>SupportFiles\Fig01_H73-SurveyLimits.png</ns2:link></ns2:images><ns2:comments/></ns1:areaDescription><ns1:surveyLimits><ns2:results deviation="true"><ns2:discussion>Survey limits were acquired in accordance with the requirements in the Project Instructions and the HSSD (2018).</ns2:discussion></ns2:results><ns2:comments/></ns1:surveyLimits><ns1:surveyPurpose><ns2:discussion>The purpose of the project is to provide contemporary surveys to update the National Ocean Service nautical charting products to support an increase in vessel traffic into Tampa Bay, Florida. There is a lack of modern data in the area, which is subject to strong storm events that have the potential to cause shoaling.</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>Sheet 4</ns2:waterDepth><ns2:requiredCoverage>Object Detection Coverage</ns2:requiredCoverage></ns2:coverageRequirement><ns2:coverageRequirement><ns2:waterDepth>All waters in survey area</ns2:waterDepth><ns2:requiredCoverage>Report significant shoaling via weekly progress reports. PM/COR may adjust survey prioritization based on observed shoaling.</ns2:requiredCoverage></ns2:coverageRequirement><ns2:coverageRequirement><ns2:waterDepth>All waters in survey area</ns2:waterDepth><ns2:requiredCoverage>Acquire backscatter data during all multibeam data acquisition.</ns2:requiredCoverage></ns2:coverageRequirement><ns2:results deviation="true"><ns2:discussion>Issues were recognized with respect to data collected with the EM2040C dual head configuration. For the majority of data collected in the dual head configuration, only one head acquired time series backscatter data; beam average backscatter data exists.</ns2:discussion></ns2:results><ns2:comments/></ns1:surveyCoverage><ns1:coverageGraphic><ns2:coverageGraphicImage><ns2:images><ns2:caption>H13173 Survey Coverage</ns2:caption><ns2:link>SupportFiles\Fig02_H73-SurveyCoverage.png</ns2:link></ns2:images></ns2:coverageGraphicImage></ns1:coverageGraphic><ns1:surveyStatistics><ns2:LNM><ns2:vesselLNM><ns2:vessel><ns2:hullID>1237094</ns2:hullID><ns2:statistics><ns2:MS_SBES>0.00</ns2:MS_SBES><ns2:MS_MBES>984.33</ns2:MS_MBES><ns2:MS_lidar>0.00</ns2:MS_lidar><ns2:MS_SSS>0.00</ns2:MS_SSS><ns2:MS_SBES_MBES>0.00</ns2:MS_SBES_MBES><ns2:MS_MBES_SSS>0.00</ns2:MS_MBES_SSS><ns2:MS_SBES_SSS>0.00</ns2:MS_SBES_SSS><ns2:XL_MBES_SBES>55.19</ns2:XL_MBES_SBES><ns2:XL_lidar>0.00</ns2:XL_lidar></ns2:statistics></ns2:vessel><ns2:vessel><ns2:hullID>QN00027J708</ns2:hullID><ns2:statistics><ns2:MS_SBES>0.00</ns2:MS_SBES><ns2:MS_MBES>480.86</ns2:MS_MBES><ns2:MS_lidar>0.00</ns2:MS_lidar><ns2:MS_SSS>0.00</ns2:MS_SSS><ns2:MS_SBES_MBES>0.00</ns2:MS_SBES_MBES><ns2:MS_MBES_SSS>0.00</ns2:MS_MBES_SSS><ns2:MS_SBES_SSS>0.00</ns2:MS_SBES_SSS><ns2:XL_MBES_SBES>21.69</ns2:XL_MBES_SBES><ns2:XL_lidar>0.00</ns2:XL_lidar></ns2:statistics></ns2:vessel></ns2:vesselLNM><ns2:totalLNM><ns2:MS_SBES>0.00</ns2:MS_SBES><ns2:MS_MBES>1465.19</ns2:MS_MBES><ns2:MS_lidar>0.00</ns2:MS_lidar><ns2:MS_SSS>0.00</ns2:MS_SSS><ns2:MS_SBES_MBES>0.00</ns2:MS_SBES_MBES><ns2:MS_MBES_SSS>0.00</ns2:MS_MBES_SSS><ns2:MS_SBES_SSS>0.00</ns2:MS_SBES_SSS><ns2:XL_MBES_SBES>76.89</ns2:XL_MBES_SBES><ns2:XL_lidar>0.00</ns2:XL_lidar><ns2:percentXLLNM>5.2</ns2:percentXLLNM></ns2:totalLNM></ns2:LNM><ns2:totalSurveyStats><ns2:bottomSamples>11</ns2:bottomSamples><ns2:maritimeBoundaryPoints>0</ns2:maritimeBoundaryPoints><ns2:DP>92</ns2:DP><ns2:diveOps>0</ns2:diveOps><ns2:SNM>35.78</ns2:SNM></ns2:totalSurveyStats><ns2:surveyDates>2019-11-09</ns2:surveyDates><ns2:surveyDates>2019-11-09</ns2:surveyDates><ns2:surveyDates>2019-02-27</ns2:surveyDates><ns2:surveyDates>2019-02-28</ns2:surveyDates><ns2:surveyDates>2019-03-01</ns2:surveyDates><ns2:surveyDates>2019-03-03</ns2:surveyDates><ns2:surveyDates>2019-03-07</ns2:surveyDates><ns2:surveyDates>2019-03-08</ns2:surveyDates><ns2:surveyDates>2018-03-09</ns2:surveyDates><ns2:surveyDates>2019-03-10</ns2:surveyDates><ns2:surveyDates>2019-03-11</ns2:surveyDates><ns2:surveyDates>2019-03-12</ns2:surveyDates><ns2:surveyDates>2019-03-14</ns2:surveyDates><ns2:surveyDates>2019-03-15</ns2:surveyDates><ns2:surveyDates>2019-03-16</ns2:surveyDates><ns2:surveyDates>2019-03-17</ns2:surveyDates><ns2:surveyDates>2019-03-23</ns2:surveyDates><ns2:surveyDates>2019-03-24</ns2:surveyDates><ns2:surveyDates>2019-03-25</ns2:surveyDates><ns2:surveyDates>2019-03-26</ns2:surveyDates><ns2:surveyDates>2019-03-29</ns2:surveyDates><ns2:surveyDates>2019-04-27</ns2:surveyDates><ns2:surveyDates>2019-04-28</ns2:surveyDates><ns2:surveyDates>2019-04-29</ns2:surveyDates><ns2:surveyDates>2019-04-30</ns2:surveyDates><ns2:surveyDates>2019-05-01</ns2:surveyDates><ns2:surveyDates>2019-05-02</ns2:surveyDates><ns2:surveyDates>2019-05-03</ns2:surveyDates><ns2:surveyDates>2019-05-04</ns2:surveyDates><ns2:surveyDates>2019-05-05</ns2:surveyDates><ns2:surveyDates>2019-05-06</ns2:surveyDates><ns2:surveyDates>2019-05-07</ns2:surveyDates><ns2:surveyDates>2019-05-08</ns2:surveyDates><ns2:surveyDates>2019-05-09</ns2:surveyDates><ns2:surveyDates>2019-05-11</ns2:surveyDates><ns2:surveyDates>2019-05-12</ns2:surveyDates><ns2:surveyDates>2019-05-13</ns2:surveyDates><ns2:surveyDates>2019-05-14</ns2:surveyDates><ns2:surveyDates>2019-05-15</ns2:surveyDates><ns2:surveyDates>2019-05-16</ns2:surveyDates><ns2:surveyDates>2019-05-17</ns2:surveyDates><ns2:surveyDates>2019-05-18</ns2:surveyDates><ns2:surveyDates>2019-05-19</ns2:surveyDates><ns2:surveyDates>2019-05-20</ns2:surveyDates><ns2:surveyDates>2019-05-21</ns2:surveyDates><ns2:surveyDates>2019-05-22</ns2:surveyDates><ns2:surveyDates>2019-05-24</ns2:surveyDates><ns2:surveyDates>2019-05-25</ns2:surveyDates><ns2:surveyDates>2019-05-26</ns2:surveyDates><ns2:surveyDates>2019-07-21</ns2:surveyDates><ns2:discussion>It was observed that there were several unit options for nautical miles within the CARIS program. However, 'area' only had one option for the nautical mile units as Square Int. Nautical Miles. To be consistent, Int. Nautical Miles was used as the unit for the LNM shown in Table 3. Detached Positions (DP) include fixes taken for CTD casts, lead line comparisons (if applicable) and buoys within survey bounds, but not bottom samples because there is a separate entry for those.</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>1237094</ns2:hullID><ns2:LOA units="meters">40.84</ns2:LOA><ns2:draft units="meters">1.98</ns2:draft></ns1:vessel><ns1:vessel><ns2:hullID>QN00027J708</ns2:hullID><ns2:LOA units="meters">9.144</ns2:LOA><ns2:draft units="meters">0.762</ns2:draft></ns1:vessel><ns1:discussion>The R/V Sea Scout (Hull ID 1237094) and R/V C-Wolf (Hull ID JQN00027J708) were used as the survey platforms for data acquisition within H13173.</ns1:discussion><ns1:comments/></ns1:vessels><ns1:equipment><ns1:majorSystem><ns2:manufacturer>Kongsberg Maritime</ns2:manufacturer><ns2:model>EM 2040C</ns2:model><ns2:type>MBES</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>Kongsberg Maritime</ns2:manufacturer><ns2:model>EM 3002</ns2:model><ns2:type>MBES</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>C-Nav</ns2:manufacturer><ns2:model>3050</ns2:model><ns2:type>Positioning System</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>CodaOctopus</ns2:manufacturer><ns2:model>F180</ns2:model><ns2:type>Positioning and Attitude System</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>Teledyne TSS</ns2:manufacturer><ns2:model>DMS05</ns2:model><ns2:type>Attitude System</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>Teledyne TSS</ns2:manufacturer><ns2:model>Meridian Surveyor</ns2:model><ns2:type>Gyrocompass</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>Sea-Bird Scientific</ns2:manufacturer><ns2:model>SBE 19</ns2:model><ns2:type>Conductivity, Temperature, and Depth Sensor</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>Sea-Bird Scientific</ns2:manufacturer><ns2:model>SBE 19plus</ns2:model><ns2:type>Conductivity, Temperature, and Depth Sensor</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>YSI</ns2:manufacturer><ns2:model>600R-BCR-C-T</ns2:model><ns2:type>Conductivity, Temperature, and Depth Sensor</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>Crosslines were run generally perpendicular to main scheme survey lines in order for quality control statistics to be generated after completion of main scheme lines. The total crossline mileage was 76.89 LNM and the total mainline mileage was 1465.19 LNM. Multibeam fill-ins were included in the total mainline mileage but lines collected specifically for investigation purposes were not included.

Separate 50-cm mainline and crossline Combined Uncertainty and Bathymetric Estimator (CUBE) surfaces were generated and the surface difference tool within CARIS HIPS was used to evaluate crossline and main scheme line agreement. The mainline surface was used as Input A and the crossline surface as Input B. Statistical information about the difference surface was generated using the Compute Statistics tool (Figure 3). The analysis shows that greater than 99% of depth difference values are between -0.32 and 0.28 meters. This is well within the maximum allowable Total Vertical Uncertainty (TVU) for the depths of the comparison area of the mainline surface (2.64 – 28.54 meters), which ranges from ±0.501 to ±0.623 meters. It is evident from the histogram (Figure 3) that several depth difference values exceed the maximum allowable TVU. 

Difference values greater than the maximum TVU were addressed using the following methodology. An absolute difference layer for the mainline/crossline difference surface was created by squaring all difference values and then taking the square root of those values. A maximum TVU layer was generated for the H13173_MB_MLLW_50cm_Mainlines surface using the following formula: (0.5^2+(0.013*Depth)^2)^0.5. The absolute difference layer was subtracted from the maximum TVU layer. Positive values indicate that the difference between the mainline and crossline data sets are less than the maximum TVU while negative values indicate that the difference between the two data sets are greater than the maximum TVU. Areas of disagreement were evaluated. Correspondence with CARIS indicates a known issue with the Compute Layer tool in CARIS 10.4. When Depth is in the middle of an expression, the Compute Layer function assumes Depth is negative even if Z-axis convention is set to positive. It was observed that the signs of computed layers in CARIS were not consistent in CARIS 10.4 and all junction analyses were conducted using CARIS 9.1. Further examination indicates depth differences greater than the maximum TVU (Figure 4) are generally associated with sea floor features with a more notable exception in the central portion of the survey area. Refer to section B.2.5 for additional information.

The crossline surface, mainline surface, difference surface and exported ASCII file of histogram results are located in Separates\II_Digital_Data\Crossline_Comparison.</ns2:discussion><ns2:images><ns2:caption>H13173 crossline comparison statistics and histogram output from CARIS compute statistics tool.</ns2:caption><ns2:link>SupportFiles\Fig03_H73-CrosslineComparison-1.png</ns2:link></ns2:images><ns2:images><ns2:caption>H13173 survey area overlain with black compass features that indicate where depth difference values between mainlines and crosslines are greater than the maximum TVU.</ns2:caption><ns2:link>SupportFiles\Fig04_H73-CrosslineComparison-2.png</ns2:link></ns2:images><ns2:comments/></ns1:crosslines><ns1:uncertainty><ns2:values><ns2:tideUncertainty><ns2:measured units="meters">0.1</ns2:measured><ns2:zoning units="meters">0.131</ns2:zoning><ns2:tideMethod>ERS via VDATUM</ns2:tideMethod></ns2:tideUncertainty><ns2:soundSpeedUncertainty><ns2:hullID>1237094</ns2:hullID><ns2:measuredCTD units="meters/second">2</ns2:measuredCTD><ns2:measuredMVP units="meters/second">n/a</ns2:measuredMVP><ns2:surface units="meters/second">0.8</ns2:surface></ns2:soundSpeedUncertainty><ns2:soundSpeedUncertainty><ns2:hullID>JQN00027J708</ns2:hullID><ns2:measuredCTD units="meters/second">2</ns2:measuredCTD><ns2:measuredMVP units="meters/second">n/a</ns2:measuredMVP><ns2:surface units="meters/second">0.8</ns2:surface></ns2:soundSpeedUncertainty></ns2:values><ns2:discussion>The Total Propagated Uncertainty (TPU) for each sounding was computed within CARIS, the MBES data processing software. The vessel file stores static values of the estimated uncertainties associated with each individual sensor. The Compute TPU dialog contains placeholders for the user to specify tidal and sound speed uncertainty, as well as whether the sources of uncertainty are static (come from the vessel file) or were collected in real-time. This particular survey contains all static uncertainty sources. The above uncertainty estimates are combined with a DeviceModels.xml that contains individual sonar model characteristics to calculate the total TPU.

Currently there is no entry for static vertical uncertainty associated with a positioning system or a separation model within CARIS. The workaround is to enter these values in the Tide Measured and Zoning entry locations. Internal verification indicates the C-Nav™ 3050 systems have a vertical uncertainty of ~20 cm at the 95% confidence level. The 95% confidence level is expressed as 1.96 standard deviations from the mean. CARIS entries of uncertainty are assumed to be 1-sigma (one standard deviation from the mean) and this value of 20 cm is divided by 1.96 for a value of 10 cm to enter into CARIS. The 1-sigma VDATUM Maximum Combined Uncertainty (MCU) value for the separation model (13.1 cm) is provided in the project instructions.

An Uncertainty layer is generated during the bathymetric surface creation process that shows the uncertainty at each node of the surface. HydrOffice QCTools was used to analyze the uncertainty of all finalized and un-finalized grids. It was observed that all uncertainty values are within specifications for all un-finalized surfaces and (Figures 5-6) but the finalized surfaces contain less than 0.1% of values that do not meet specifications (Figures 7-8). Review indicates this is due to the finalization parameter where the uncertainty is defined as the greater of either the standard deviation or uncertainty for a particular node. The majority of nodes that do not meet specifications are associated with seafloor features, contacts, changes in bathymetry and along areas where data indicate evidence of potential sound speed artifacts and/or erroneous data points. The areas with a potential artifact and/or erroneous data points do not appear to contribute substantially to the overall surface depth value as reviewed in subset editor with the reference surface loaded, but appear to still contribute to the overall standard deviation.</ns2:discussion><ns2:images><ns2:caption>Uncertainty QA output from HydrOffice QCTools for surface H13173_MB_50cm_MLLW.</ns2:caption><ns2:link>SupportFiles\Fig05_H73_MB_50cm_MLLW.QAv5.tvu_qc.png</ns2:link></ns2:images><ns2:images><ns2:caption>Uncertainty QA output from HydrOffice QCTools for surface H13173_MB_1m_MLLW.</ns2:caption><ns2:link>SupportFiles\Fig06_H73_MB_1m_MLLW.QAv5.tvu_qc.png</ns2:link></ns2:images><ns2:images><ns2:caption>Uncertainty QA output from HydrOffice QCTools for surface H13173_MB_50cm_MLLW_Final.</ns2:caption><ns2:link>SupportFiles\Fig07_H3_MB_50cm_MLLW_Final.QAv5.tvu_qc.png</ns2:link></ns2:images><ns2:images><ns2:caption>Uncertainty QA output from HydrOffice QCTools for surface H13173_MB_1m_MLLW_Final.</ns2:caption><ns2:link>SupportFiles\Fig08_H73_MB_1m_MLLW_Final.QAv5.tvu_qc.png</ns2:link></ns2:images><ns2:comments/></ns1:uncertainty><ns1:junctions><ns2:discussion>H13173 junctions with six contemporary surveys (H13170, H13171, H13172, H13176, H13177 and H13178) and one prior survey (W00312) as shown in Figure 9. Difference surfaces between the depth layers of 1-meter resolution surfaces for H13173 and the adjoining surveys were generated and areas of disagreement were evaluated. Finalized surfaces were used when available. The analysis addresses difference values greater than 2^0.5 * TVU, as outlined in the HSSD (2018). The minimum depth for the H13173 survey area is 2.57 meters with a TVU of ±0.501 meters and 2^0.5 * TVU of ±0.709 meters. Depth difference values greater than 2^0.5 meters would need to at least exceed ±0.709 meters. 

Difference values greater than 2^0.5 * TVU were addressed using the following methodology. An absolute difference layer for each junction difference surface was created by squaring all difference values and then taking the square root of those values. A junction compliance layer was generated for the H13173_MB_MLLW_1m surface using the following formula: 2^0.5 * TVU where TVU is (0.5^2+(0.013*Depth)^2)^0.5, as outlined in section 8.1.4 of the HSSD (2018). The absolute difference layer was subtracted from the junction compliance layer. Positive values indicate the difference between the two data sets is less than 2^0.5 * TVU while negative values indicate the difference between the two data sets is greater than 2^0.5 * TVU. Areas of disagreement were evaluated. Correspondence with CARIS indicates a known issue with the Compute Layer tool in CARIS 10.4. When Depth is in the middle of an expression, the Compute Layer function assumes Depth is negative even if Z-axis convention is set to positive. It was observed that the signs of computed layers in CARIS were not consistent in CARIS 10.4 and all junction analyses were conducted using CARIS 9.1.</ns2:discussion><ns2:images><ns2:caption>H13173 Survey Junctions</ns2:caption><ns2:link>SupportFiles\Fig09_H73-SurveyJunctions.png</ns2:link></ns2:images><ns2:junction><ns2:survey><ns2:registryNumber>W00312</ns2:registryNumber><ns2:scale>20000</ns2:scale><ns2:year>2016</ns2:year><ns2:fieldUnit>LiDAR</ns2:fieldUnit><ns2:relativeLocation>E</ns2:relativeLocation></ns2:survey><ns2:discussion>Sheet H13173 junctions with W00312 to the east. A 5-meter grid of the eastern portion of H13173 was used for comparison. This junction is located at the mouth of the Egmont Channel. The difference surface shows large discrepancies between the two surfaces with only 50% of soundings falling between -0.435 and 0.465 meters.  Depths from H13173 are generally deeper along the northern boundary and shallower along the southern boundary. Along the northern boundary one area indicates differences up to 7 meters, with H13173 data being deeper (blue box Figure 11).</ns2:discussion><ns2:images><ns2:caption>Histogram of depth difference values between overlapping data of H13173 and W00312.</ns2:caption><ns2:link>SupportFiles\Fig10_H73JunctionW00312-1.png</ns2:link></ns2:images><ns2:images><ns2:caption>Depth difference surface between H13173 and W00312. Blue box shows area where differences are up to 7 meters.</ns2:caption><ns2:link>SupportFiles\Fig11_H73JunctionW00312-2.png</ns2:link></ns2:images><ns2:comments/></ns2:junction><ns2:junction><ns2:survey><ns2:registryNumber>H13170</ns2:registryNumber><ns2:scale>20000</ns2:scale><ns2:year>2018</ns2:year><ns2:fieldUnit>Oceaneering</ns2:fieldUnit><ns2:relativeLocation>N</ns2:relativeLocation></ns2:survey><ns2:discussion>H13173 junctions with H13170 to the north. The overlap consists of mainlines and crosslines that extend into the adjoining sheet.  A difference surface was generated between the two surveys with H13173_MB_1m_MLLW as Input A and H13170_MB_1m_MLLW_Final as Input B.  The difference surface indicates over 99% of nodes are within ±40 cm (Figure 12). Figure 13 shows the nodes where differences are greater than 2^0.5 *TVU. These are areas of bathymetric change and review of the surfaces indicates features are different from one data set to the other.</ns2:discussion><ns2:images><ns2:caption>Histogram of depth difference values between overlapping data of H13173 and H13170.</ns2:caption><ns2:link>SupportFiles\Fig12_H73JunctionH70-1.png</ns2:link></ns2:images><ns2:images><ns2:caption>Overlap of H13173 and H13170 with cartographic symbols indicating nodes that exceed the 2^0.5 * TVU threshold.</ns2:caption><ns2:link>SupportFiles\Fig13_H73JunctionH70-2.png</ns2:link></ns2:images><ns2:comments/></ns2:junction><ns2:junction><ns2:survey><ns2:registryNumber>H13171</ns2:registryNumber><ns2:scale>20000</ns2:scale><ns2:year>2018</ns2:year><ns2:fieldUnit>Oceaneering</ns2:fieldUnit><ns2:relativeLocation>N</ns2:relativeLocation></ns2:survey><ns2:discussion>H13173 junctions with H13171 to the north. The overlap consists of mainlines and crosslines that extend into the adjoining sheet.  A difference surface was generated between the two surveys with H13173_MB_1m_MLLW as Input A and H13171_MB_1m_MLLW_Final as Input B.  The difference surface indicates over 99% of nodes are within ±35 cm (Figure 14). All depth difference values are less than 2^0.5 * TVU.</ns2:discussion><ns2:images><ns2:caption>Histogram of depth difference values between overlapping data of H13173 and H13171.</ns2:caption><ns2:link>SupportFiles\Fig14_H73JunctionH71-1.png</ns2:link></ns2:images><ns2:comments/></ns2:junction><ns2:junction><ns2:survey><ns2:registryNumber>H13172</ns2:registryNumber><ns2:scale>20000</ns2:scale><ns2:year>2018</ns2:year><ns2:fieldUnit>Oceaneering</ns2:fieldUnit><ns2:relativeLocation>S</ns2:relativeLocation></ns2:survey><ns2:discussion>H13173 junctions with H13172 to the south. The overlap consists of mainlines and crosslines that extend into the adjoining sheet.  A difference surface was generated between the two surveys with H13173_MB_1m_MLLW as Input A and H13172_MB_1m_MLLW_Final as Input B. Over 99% of nodes are between -0.26 and 0.24 meters (Figure 15). All depth difference values are less than 2^0.5 * TVU.</ns2:discussion><ns2:images><ns2:caption>Histogram of depth difference values between overlapping data of H13173 and H13172.</ns2:caption><ns2:link>SupportFiles\Fig15_H73JunctionH72-1.png</ns2:link></ns2:images><ns2:comments/></ns2:junction><ns2:junction><ns2:survey><ns2:registryNumber>H13176</ns2:registryNumber><ns2:scale>20000</ns2:scale><ns2:year>2018</ns2:year><ns2:fieldUnit>Oceaneering</ns2:fieldUnit><ns2:relativeLocation>W</ns2:relativeLocation></ns2:survey><ns2:discussion>H13173 junctions with H13176 to the west. The overlap consists of mainlines and crosslines that extend into the adjoining sheet.  A difference surface was generated between the two surveys with H13173_MB_1m_MLLW as Input A and H13176_MB_1m_MLLW as Input B. Over 99% of nodes are within -0.19 to 0.21 meters (Figure 16). The difference value of one node is greater than 2^0.5 * TVU (Figure 17). This node is on the edge of a bathymetric feature and may represent a positional offset between the two data sets.</ns2:discussion><ns2:images><ns2:caption>Histogram of depth difference values between overlapping data of H13173 and H13176.</ns2:caption><ns2:link>SupportFiles\Fig16_H73JunctionH76-1.png</ns2:link></ns2:images><ns2:images><ns2:caption>Overlap of H13173 and H13176 with cartographic symbol indicating node that exceeds the 2^05 * TVU threshold.</ns2:caption><ns2:link>SupportFiles\Fig17_H73JunctionH76-2.png</ns2:link></ns2:images><ns2:comments/></ns2:junction><ns2:junction><ns2:survey><ns2:registryNumber>H13177</ns2:registryNumber><ns2:scale>20000</ns2:scale><ns2:year>2018</ns2:year><ns2:fieldUnit>Oceaneering</ns2:fieldUnit><ns2:relativeLocation>S</ns2:relativeLocation></ns2:survey><ns2:discussion>H13177 junctions with H13177 to the south and southwest. The overlap consists of mainlines and crosslines that extend into the adjoining sheet.  A difference surface was generated between the two surveys with H13173_MB_1m_MLLW as Input A and H13177_MB_1m_MLLW_Final as Input B.  Over 99% of nodes are within -0.28 and 0.32 meters (Figure 18). All depth difference values are less than 2^0.5 * TVU.</ns2:discussion><ns2:images><ns2:caption>Histogram of depth difference values between overlapping data of H13173 and H13177.</ns2:caption><ns2:link>SupportFiles\Fig18_H73JunctionH77-1.png</ns2:link></ns2:images><ns2:comments/></ns2:junction><ns2:junction><ns2:survey><ns2:registryNumber>H13178</ns2:registryNumber><ns2:scale>40000</ns2:scale><ns2:year>2018</ns2:year><ns2:fieldUnit>Oceaneering</ns2:fieldUnit><ns2:relativeLocation>SW</ns2:relativeLocation></ns2:survey><ns2:discussion>The survey junction between H13173 and H13178 will be addressed in the Descriptive Report for H13178.</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="true"><ns2:issue><ns2:title>Sonar Settings</ns2:title><ns2:discussion>If necessary, the angle of the multibeam sonars were modified in order to moderate the effects of factors such as increased sea state or to increase coverage; any changes are documented in the acquisition logs. Aboard the R/V Sea Scout, data were collected with a combination of a dual head EM2040C and single head EM2040C MBES system in a dual head configuration after issues with the system prevented both heads from being operational. Although it was attempted to run both heads as much as possible, fill-ins were conducted as necessary when gaps in coverage occurred.</ns2:discussion><ns2:comments/></ns2:issue><ns2:issue><ns2:title>&quot;W&quot; Pattern Artifacts</ns2:title><ns2:discussion>The data collected with the EM3002 multibeam echo sounder aboard the R/V C-Wolf (Hull ID JQN00027J708) exhibits a thicker region of nadir depth returns that manifests as an along track data artifact (Figure 19). This is more noticeable in the higher resolution, 50-cm grids. Although individual soundings can deviate up to one meter, the surface does not honor these deep soundings.</ns2:discussion><ns2:images><ns2:caption>&quot;W&quot; pattern artifact evident in data collected aboard the R/V C-Wolf.</ns2:caption><ns2:link>SupportFiles\Fig19_H73-CwolfData.png</ns2:link></ns2:images><ns2:comments/></ns2:issue><ns2:issue><ns2:title>Motion Artifacts, Ping Drops and Vertical Offsets</ns2:title><ns2:discussion>Minor motion artifacts on the outer swath (Figure 20) and ping drops (Figure 21) were evident periodically  throughout the data collected with the R/V Sea Scout; if overlapping data did not exist, fill-ins were collected. In addition, some vertical offsets exist in the data. These appear to generally occur on lines that exhibit a curve, but one line in particular shows an offset (Figure 22). The cause is not readily evident, though the project acquisition logs indicate this was the last line run before the decision was made to attempt north/south lines due to weather conditions. The vertical difference is within the maximum allowable TVU and no additional post-processing of this line was conducted.</ns2:discussion><ns2:images><ns2:caption>Motion artifacts within data collected with the R/V Sea Scout.</ns2:caption><ns2:link>SupportFiles\Fig20_H73-SeaScoutData-1.png</ns2:link></ns2:images><ns2:images><ns2:caption>Ping drops within data collected with the R/V Sea Scout.</ns2:caption><ns2:link>SupportFiles\Fig21_H73-SeaScoutData-2.png</ns2:link></ns2:images><ns2:images><ns2:caption>Vertical offset of line 4347 within R/V Sea Scout data.</ns2:caption><ns2:link>SupportFiles\Fig22_H73-SeaScoutData-3.png</ns2:link></ns2:images><ns2:comments/></ns2:issue></ns2:results><ns2:comments/></ns1:equipmentEffectiveness><ns1:factorsAffectingSoundings><ns2:results deviation="true"><ns2:issue><ns2:title>Environmental Factors</ns2:title><ns2:discussion>Weather, sea state, thermoclines, and fish/marine life were all temporary factors that affected the data periodically throughout the duration of the survey.  These are noted in the acquisition and processing logs and reruns were collected when necessary.</ns2:discussion><ns2:comments/></ns2:issue></ns2:results><ns2:comments/></ns1:factorsAffectingSoundings><ns1:soundSpeedMethods><ns1:castFrequency>Twice per day and more often as necessary aboard the R/V Sea Scout and once per day and more often if necessary aboard the R/V C-Wolf.</ns1:castFrequency><ns1:discussion>Sea-Bird Scientific SBE19 and SBE19plus Conductivity, Temperature, and Depth (CTD) sensors were used for speed of sound measurements through the water column. Endeco YSI sondes were used to determine the sound speed at the transducer. The multibeam data were corrected for the water column sound speed in real-time using the SIS control software. Sound speed data are located in Separates\II_Digital_Data\Sound_Speed_Data_Summary.</ns1:discussion><ns1:comments/></ns1:soundSpeedMethods><ns1:coverageEquipmentAndMethods><ns2:results deviation="true"><ns2:discussion>Coverage within the survey area consisted of Object Detection MBES data acquisition. Bathymetric data were acquired with a combination of a single head Kongsberg EM3002 MBES system (aboard the R/V C-Wolf) and dual head and single-head Kongsberg EM2040C MBES systems (aboard the R/V Sea Scout). </ns2:discussion></ns2:results><ns2:comments/></ns1:coverageEquipmentAndMethods><ns1:additionalQualityControl><ns2:issue><ns2:title>Density</ns2:title><ns2:discussion>HydrOffice QCTools was used to analyze the density of all finalized surfaces.  The density of all finalized surfaces meets the density requirements for which at least 95% of all nodes on the surface shall be populated with at least 5 soundings (Figures 23-24).</ns2:discussion><ns2:images><ns2:caption>Statistical information about the density child layer of the H13173_MB_50cm_MLLW_Final surface.</ns2:caption><ns2:link>SupportFiles\Fig23_H73_MB_50cm_MLLW_Final.QAv5.density.png</ns2:link></ns2:images><ns2:images><ns2:caption>Statistical information about the density child layer of the H13173_MB_1m_MLLW_Final surface.</ns2:caption><ns2:link>SupportFiles\Fig24_H73_MB_1m_MLLW_Final.QAv5.density.png</ns2:link></ns2:images><ns2:comments/></ns2:issue><ns2:issue><ns2:title>Holidays</ns2:title><ns2:discussion>HydrOffice QCTools was used to determine the existence of holidays within all finalized Object Detection MBES grids. The results show over 1000 holidays within the H13173_MB_1m_MLLW_Final surface within survey bounds. Review of this surface indicates these holidays are due to the depth threshold applied during the finalization process. Review of the 1-meter un-finalized surface does not indicate any holidays within survey bounds. The HydrOffice QCTools results also indicate over 100 holidays within the H13173_MB_50cm_MLLW_Final surface within survey bounds. Review of this surface indicates this is mainly due to the depth threshold applied during the finalization process, but three holidays do exist that are not a function of the depth threshold applied during the finalization process, but appear to be due to rejecting noisy data. Review of holidays within the 50-cm un-finalized surface indicates only the three aforementioned holidays within survey bounds. The field crew has since left the survey site and these could not be filled in.</ns2:discussion><ns2:comments/></ns2:issue><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:comments/></ns1:additionalIssues></ns1:echoSoundingCorrections><ns1:backscatter><ns2:results acquired="true"><ns2:discussion>Raw backscatter data were logged within the Kongsberg .all file and has been sent to the Processing Branch. An issue was recognized with respect to the dual head configuration in that for the majority of the data collected with the EM2040C dual head, only one head acquired time series backscatter data; beam average backscatter data exist.</ns2:discussion></ns2:results><ns2:comments/></ns1:backscatter><ns1:dataProcessing><ns1:drSoftware><ns1:bathySoftware deviation="true"><ns1:manufacturer>Caris</ns1:manufacturer><ns1:name>HIPS/SIPS</ns1:name><ns1:version>10.4</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_8</ns1:featureObjectCatalog><ns1:discussion xsi:nil="true"></ns1:discussion><ns1:comments/></ns1:drSoftware><ns1:surfaces><ns1:surface><ns2:surfaceName>H13173_MB_50cm_MLLW</ns2:surfaceName><ns2:surfaceType>CARIS Raster Surface (CUBE)</ns2:surfaceType><ns2:resolution units="meters">0.5</ns2:resolution><ns2:depthRange><ns2:min units="meters">2.52</ns2:min><ns2:max units="meters">28.54</ns2:max></ns2:depthRange><ns2:surfaceParameter>NOAA_0.5m</ns2:surfaceParameter><ns2:purpose>Object Detection</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceName>H13173_MB_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">2.49</ns2:min><ns2:max units="meters">20.00</ns2:max></ns2:depthRange><ns2:surfaceParameter>NOAA_0.5m</ns2:surfaceParameter><ns2:purpose>Object Detection</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceName>H13173_MB_1m_MLLW</ns2:surfaceName><ns2:surfaceType>CARIS Raster Surface (CUBE)</ns2:surfaceType><ns2:resolution units="meters">1</ns2:resolution><ns2:depthRange><ns2:min units="meters">2.57</ns2:min><ns2:max units="meters">28.41</ns2:max></ns2:depthRange><ns2:surfaceParameter>NOAA_1m</ns2:surfaceParameter><ns2:purpose>Object Detection</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceName>H13173_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">18.00</ns2:min><ns2:max units="meters">28.41</ns2:max></ns2:depthRange><ns2:surfaceParameter>NOAA_1m</ns2:surfaceParameter><ns2:purpose>Object Detection</ns2:purpose></ns1:surface><ns1:discussion xsi:nil="true"></ns1:discussion><ns1:comments/></ns1:surfaces><ns1:additionalDataProcessing><ns2:issue><ns2:title>MBES Data Review</ns2:title><ns2:discussion>It was recognized that the CARIS project indicated 6 lines collected with the R/V Sea Scout (4300, 4345, 4346, 4247, 4350 and TIE-427) had a tide file loaded during processing. The CARIS processing log indicates the tide file was loaded after the GPS tide was computed. These 6 lines were reprocessed (Load ASCII Navigation &gt; Compute GPS tide &gt; Merge) to ensure GPS tide was applied even though the CARIS log will still note the presence of a tide file.

Surface filters were attempted, but it was decided to re-accept the filtered data due to more data than the processor was comfortable with being rejected. The data were manually reviewed for outliers (fliers) using the standard deviation and depth layers. Higher standard deviation is generally associated with bathymetric features, contacts and/or areas of bathymetric change.  Noise can also be identified by high standard deviation.  The Flier Finder utility within HydrOffice QCTools was used as an additional quality control tool to evaluate the surface for fliers. Identified fliers were manually rejected.

A final check on the H13173_MB_50cm_MLLW_Final and H13173_MB_1m_MLLW_Final surfaces was conducted using HydrOffice QCTools 2 v2.7.0 Flier Finder with the default parameters selected. The results indicate a total of 73 potential fliers within survey bounds for the H13173_MB_50cm_MLLW_Final surface. Twenty-seven are flagged as flier finder flag 1 (Laplacian Operator), which are all associated with designated soundings. Forty-five are flagged as flier finder flag 5 (isolated nodes) and one is flagged as flier finder flag 6 (noisy edges), which appear associated with the depth threshold applied during the surface finalization process. The results indicate a total of 301 potential fliers within survey bounds for the H13173_MB_1m_MLLW_Final surface with 20 nodes flagged as flier finder flag 6 (noisy edges) and the remaining 281 nodes flagged as flier finder flag '5' (isolated nodes); these all appear associated with the depth parameter threshold applied during the surface finalization process. </ns2:discussion><ns2:comments/></ns2:issue><ns2:issue><ns2:title>Fixed File Path</ns2:title><ns2:discussion>During post-processing, ASCII navigation files (time, lat, lon, GPS height) were imported into CARIS with an associated .info file, which contains information on the contents and formatting of the ASCII navigation files.

When projects processed in the above manner were copied from a network location to external or internal drives or from internal to external drives it was observed that the path of the *.info file remained fixed to the original path name. Upon opening the copied project, the CARIS program asked to update the navigation folder, but not the *.info file. Keeping the info file in with the ASCII navigation did not appear to change this.  Certain editors such as navigation editor or swath editor could not be opened within CARIS and the lines became locked.

The workaround is to recreate the exact folder structure of the original project on the internal or external drive. However, it is recognized that this is an issue for submission because files are placed in the appropriate submission folders without regard for how the projects were originally set up.

A request was logged with CARIS support and the information sent to the development team. Information from CARIS support indicates that the Check Project process was not checking for an *.info file when using an ASCII file for auxiliary navigation. CARIS correspondence indicates that this has been fixed so that the check process will look for *.info missing files, enabling users to update their location using the Reset Raw Data Location dialog box. This fix should be available in both versions 10.4.10 and 11.1.0. Due to licensing limitations this has not been tested in-house and the workaround to maintain original path names and drive letters was used. The original path for this project is: N:\NOAA\2018-OPR-J317-KR-18_193519- TampaBay\Sheets\H13173-Sheet4\Geo\Software_Projects\CARIS. </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="false" xsi:nil="true"/><ns2:VDATUM_or_constantSep used="true"><ns2:methodsUsed>ERS via VDATUM</ns2:methodsUsed><ns2:ellipsoidToChartDatumSepFile><ns2:fileName>TampaBay_EC_poly_xyNAD83-MLLW_geoid12b</ns2:fileName></ns2:ellipsoidToChartDatumSepFile><ns2:discussion xsi:nil="true"></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 17</ns2:projection><ns2:PPK used="false" xsi:nil="true"/><ns2:PPP used="true"><ns2:discussion>The positioning systems aboard the vessels utilize Oceaneering C-Nav systems which deliver Precise Point Positioning (PPP).  The C-Nav GPS receives corrections through the C-Nav Subscription Services.</ns2:discussion><ns2:comments/></ns2:PPP><ns2:RTK used="false" xsi:nil="true"/><ns2:DGPS used="false" xsi:nil="true"/><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 combination of sounding selection layers and user-defined depth ranges, if applicable, were used to compare surveyed soundings to charted depths using tools within the CARIS MBES data processing software. Figure 25 shows the color range that was used in the chart comparison images. Surveyed depths of the un-finalized 50-cm surface range from 2.52 - 28.54 meters with the shallowest depths on either side of the dredged portion of Egmont Channel and the deepest depths within the channel in the far east portion of the survey area.</ns2:discussion><ns2:images><ns2:caption>Color range chart used in chart comparisons.</ns2:caption><ns2:link>SupportFiles\Fig25_ChartComparison-Colormap.png</ns2:link></ns2:images><ns2:comments/></ns1:methods><ns1:charts><ns2:ENC><ns2:chart><ns2:name>US4FL10M</ns2:name><ns2:scale>80000</ns2:scale><ns2:edition>34</ns2:edition><ns2:updateApplicationDate>2019-03-18</ns2:updateApplicationDate><ns2:issueDate>2019-07-30</ns2:issueDate><ns2:preliminary>false</ns2:preliminary></ns2:chart><ns2:discussion>NOAA Local Notice to Mariners (LNM) were reviewed for Chart: 11412, Current Edition: 49, Print Date: Feb. /2019, Tampa Bay and St. Joseph Sound subsequent to the data of the Project Instructions and before the end of the survey. The last LNM reviewed was LNM 27/19, 7th Dist to Add a Sounding in Feet posted on 06/27/2019. Four LNM were issued within survey bounds subsequent to the date of the Project Instructions and before the end of the survey. Two were issued to Change Egmont Channel Lighted Buoy 4 (LNM 11/19 and LNM 22/19, posted 3/21/2019 and 6/13/2019, respectively) and two were issued to Change Egmont Channel Lighted Buoy 6 (LNM 11/19 and LNM 15/19, posted 3/21/2019 and 4/25/2019).

This chart covers all but the furthest west part of the survey area.  The eastern portion of the Egmont Channel is difficult to compare due to the changes in depth, so this comparison will look at the charted contours as the primary comparison. There are two areas where H13173 survey depths shallower than 3.6 meters extend beyond the charted contour (Figure 26). The same areas of shoaling have affected the charted 5.4-meter contour, with depths as little as 2.6 meters going beyond the contour in the larger area to the west (Figure 27). In Figure 28, red indicates areas where depths shallower than 9.1 meters extend beyond the charted contour and Figure 29 indicates areas where depths shallower than 10.9 meters extend beyond the charted contour. Like the 9.1-meter contour, the discrepancy between the chart and surveyed depths is less drastic than what was seen with the 3.6 and 5.4-meter contours. Other than the areas pointed out in Figures 26 - 29, depths in the far eastern area of the survey area are deeper than charted.

Moving west through the survey area, surveyed depths are generally within a meter of charted.  There are dumping grounds along the southern edge of the survey area, and while survey data indicate some of the dumped material exists outside of the designated zones, depths remain in line with the chart (Figure 30 with charted soundings black against the surveyed soundings). Throughout the rest of the survey area, surveyed depths agree to within a meter of charted depths.  In the west and southwest portions of the survey area is it evident surveyed depths deeper than 18.2 meters extend shoreward of the currently charted contours. There are, however, some areas where depths surveyed depths are shallower than charted. Figure 31 shows areas in green that indicate where depths shallower than 10.9 meters have extended beyond the charted 10.9-meter contours.</ns2:discussion><ns2:images><ns2:caption>Areas where surveyed depths shallower than 3.6 meters extend beyond the charted contour.</ns2:caption><ns2:link>SupportFiles\Fig26_H73-ChartComparison-US4FL10M-1.png</ns2:link></ns2:images><ns2:images><ns2:caption>Areas where surveyed depths shallower than 5.4 meters extend beyond the charted contour.</ns2:caption><ns2:link>SupportFiles\Fig27_H73-ChartComparison-US4FL10M-2.png</ns2:link></ns2:images><ns2:images><ns2:caption>Areas where surveyed depths shallower than 9.1 meters extend beyond the charted contour.</ns2:caption><ns2:link>SupportFiles\Fig28_H73-ChartComparison-US4FL10M-3.png</ns2:link></ns2:images><ns2:images><ns2:caption>Areas where surveyed depths shallower than 10.9 meters extend beyond the charted contour.</ns2:caption><ns2:link>SupportFiles\Fig29_H73-ChartComparison-US4FL10M-4.png</ns2:link></ns2:images><ns2:images><ns2:caption>Comparison of central survey area to charted depths and contours.</ns2:caption><ns2:link>SupportFiles\Fig30_H73-ChartComparison-US4FL10M-5.png</ns2:link></ns2:images><ns2:images><ns2:caption>Areas in green indicate where depths shallower than 10.9 meters have extended beyond the charted 10.9 meter contours.</ns2:caption><ns2:link>SupportFiles\Fig31_H73-ChartComparison-US4FL10M-6.png</ns2:link></ns2:images><ns2:comments/></ns2:ENC><ns2:ENC><ns2:chart><ns2:name>US5FL11M</ns2:name><ns2:scale>40000</ns2:scale><ns2:edition>47</ns2:edition><ns2:updateApplicationDate>2019-03-11</ns2:updateApplicationDate><ns2:issueDate>2019-07-16</ns2:issueDate><ns2:preliminary>false</ns2:preliminary></ns2:chart><ns2:discussion>NOAA Local Notice to Mariners (LNM) were reviewed for Chart: 11415, Current Edition: 13, Print Date: Nov. /2018, Tampa Bay Entrance; Manatee River Extension subsequent to the date of the Project Instructions and before the end of the survey. The last LNM reviewed was LNM 30/19, 7th Dist to Add an Obstruction in Feet posted on 07/18/2019. Four LNM were issued within survey bounds subsequent to the date of the Project Instructions and before the end of the survey. Two were issued to Change Egmont Channel Lighted Buoy 4 (LNM 11/19 and LNM 22/19, posted 3/21/2019 and 6/13/2019, respectively) and two were issued to Change Egmont Channel Lighted Buoy 6 (LNM 11/19 and LNM 15/19, posted 3/21/2019 and 4/25/2019).

Compared to chart US4FL10M, the charted contours are not quite in the same position and the 10.9-meter contour is not present, but the general trend of comparison is the same. Figure 32 displays an area where surveyed soundings shallower than 3.6 meters extend beyond the charted 3.6-meter contour.  In this same area, depths as little as 2.6 meters go beyond the 5.4-meter contour as well. Figure 33 shows the full extents of surveyed soundings shallower than 5.4 meters that extend beyond the charted 5.4-meter contour. Figure 34 indicates where depths are up to a meter shallower than the charted 9.1-meter contour. Throughout the rest of the survey area, including the dumping grounds, surveyed depths generally agree to within 1-meter of charted soundings.  There are several areas where survey data is deeper by over a meter, but no areas that indicate substantial shoaling in the western portion of the survey area.</ns2:discussion><ns2:images><ns2:caption>Depths shallower than 3.6 meters extend beyond the 3.6-meter contour.</ns2:caption><ns2:link>SupportFiles\Fig32_H73-ChartComparison-US5FL11M-1.png</ns2:link></ns2:images><ns2:images><ns2:caption>Full extents of surveyed soundings shallower than 5.4 meters extend beyond the charted 5.4-meter contour.</ns2:caption><ns2:link>SupportFiles\Fig33_H73-ChartComparison-US5FL11M-2.png</ns2:link></ns2:images><ns2:images><ns2:caption>Depths up to a meter shallower than the charted 9.1-meter contour.</ns2:caption><ns2:link>SupportFiles\Fig34_H73-ChartComparison-US5FL11M-3.png</ns2:link></ns2:images><ns2:comments/></ns2:ENC><ns2:ENC><ns2:chart><ns2:name>US3GC07M</ns2:name><ns2:scale>350000</ns2:scale><ns2:edition>34</ns2:edition><ns2:updateApplicationDate>2019-03-11</ns2:updateApplicationDate><ns2:issueDate>2019-07-12</ns2:issueDate><ns2:preliminary>false</ns2:preliminary></ns2:chart><ns2:discussion>NOAA Local Notice to Mariners (LNM) for Chart: 11420, Current Edition: 32, Print Date: Oct. /2018, Havana to Tampa Bay were reviewed subsequent to the date of the Project Instructions and before the end of the survey. The last LNM reviewed was LNM 30/19, 7th Dist to Add an Obstruction in Fathoms posted on 7/18/2019. No LNM were issued within the survey area subsequent to the date of the Project Instructions and before the end of the survey.

This chart covers all but the northernmost part of the survey area. In the southwest part of the survey area, there are two charted soundings, and both are 1 to 2 meters shallower than surveyed soundings (Figure 35). Figure 36 shows the charted 9.1 and 5.4-meter contours.  Surveyed depths in this area are deeper than the 9.1-meter contours by up to 3 meters, and deeper than the 5.4 meter contour by nearly 5 meters. In the easternmost part of the survey area, there are 6.8 and 13.7-meter charted depths.  Figure 37 shows that surveyed soundings are deeper than these charted depths by up to 2 meters.  There are a number of soundings in the survey area that are associated with charted obstructions.  These will be addressed in the Final Feature File.</ns2:discussion><ns2:images><ns2:caption>Comparison of surveyed soundings and US3GC07M charted depths in the southwest portion of the survey area.</ns2:caption><ns2:link>SupportFiles\Fig35_H73-ChartComparison-US3GC07M-1.png</ns2:link></ns2:images><ns2:images><ns2:caption>Comparison of surveyed soundings and US3GC07M charted contours in the central portion of the survey area.</ns2:caption><ns2:link>SupportFiles\Fig36_H73-ChartComparison-US3GC07M-2.png</ns2:link></ns2:images><ns2:images><ns2:caption>Comparison of surveyed soundings and US3GC07M charted depths in the eastern portion of the survey area.</ns2:caption><ns2:link>SupportFiles\Fig37_H73-ChartComparison-US3GC07M-3.png</ns2:link></ns2:images><ns2:comments/></ns2:ENC><ns2:ENC><ns2:chart><ns2:name>US3GC06M</ns2:name><ns2:scale>456394</ns2:scale><ns2:edition>24</ns2:edition><ns2:updateApplicationDate>2019-03-12</ns2:updateApplicationDate><ns2:issueDate>2019-06-10</ns2:issueDate><ns2:preliminary>false</ns2:preliminary></ns2:chart><ns2:discussion>NOAA Local Notice to Mariners (LNM) for Chart: 11400, Current Edition: 37, Print Date: Apr. /2019, Tampa Bay to Cape San Blas were reviewed subsequent to the date of the Project Instructions and before the end of the survey. The last LNM reviewed was LNM 30/19, 7th Dist to Add an Obstruction in Fathoms posted on 7/18/2019. No LNM were issued within the survey area subsequent to the date of the Project Instructions and before the end of the survey.

This chart covers only a slice of the survey area to the north. Figure 38 shows surveyed depths are at least 1-meter deeper than the two charted depths in the western part of this slice.  The 11.8-meter obstruction will be addressed in the final feature file. Moving east, portions of the 9.1 and 5.4-meter contours are present within the survey area.  Depths greater than 9.1 meters are present within the charted contour. Surveyed soundings greater than 5.4-meters are observed to extend within the charted 5.4-meter contour as well (Figure 39).</ns2:discussion><ns2:images><ns2:caption>Comparison of surveyed soundings and US3GC06M charted depths in the northwestern portion of the survey area.</ns2:caption><ns2:link>SupportFiles\Fig38_H73-ChartComparison-US3GC06M-1.png</ns2:link></ns2:images><ns2:images><ns2:caption>Comparison of surveyed soundings and US3GC06M charted contour in the northeastern portion of the survey area.</ns2:caption><ns2:link>SupportFiles\Fig39_H73-ChartComparison-US3GC06M-2.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>Prior to starting survey operations, the CSF indicates one pipeline, one cable, one weed/kelp area, 12 obstructions, three underwater/awash rocks and two wrecks within survey bounds. Seventeen ATONs and one Special/General Purpose buoy exist within survey bounds. Egmont Channel is located within survey bounds and the surrounding fairway and two anchorages are also partially present within the survey area. Nine dumping areas are partially present within survey bounds.</ns2:discussion></ns2:results><ns2:comments/></ns1:chartedFeatures><ns1:unchartedFeatures><ns2:results investigated="Investigated"><ns2:discussion>An additional seventeen obstructions were added to the Final Feature File that were not addressed as DtoNs and not associated with charted (CSF) features. Refer to the Final Feature File for additional information. Contacts observed within the MBES data that were less than 1 meter in height were often 'Examined' to show they had been reviewed; these remain examined in the CARIS project.  </ns2:discussion></ns2:results><ns2:comments/></ns1:unchartedFeatures><ns1:shoalAndHazardousFeatures><ns2:results investigated="Investigated"><ns2:discussion>Twelve Dangers to Navigation were submitted for this survey. Refer to the Final Feature File for additional information.</ns2:discussion></ns2:results><ns2:comments/></ns1:shoalAndHazardousFeatures><ns1:channels><ns2:results investigated="Investigated"><ns2:discussion>Egmont Channel is located within survey bounds. A comparison between the H13173_MB_50cm_MLLW_Final surface and Egmont Channel Dredged Area controlling depths was conducted. Chart US5FL11M was used to determine the controlling depths of the ROQ, RIQ, LIQ and LOQ. 

The ROQ (Right Outside Quarter) has a controlling depth of 12.80 meters. It was observed that nearly all surveyed depths from the H13173_MB_50cm_MLLW_Final surface were 12.80 meters or deeper with the exception of some small areas along the very outer edge of the ROQ. These areas appear to be less than 3 meters from the edge of the ROQ with depths only a few centimeters shallower than 12.8 meters. 

The RIQ (Right Inside Quarter) has a controlling depth of 13.60 meters. It was observed that nearly all surveyed depths from the 50 cm surface within the RIQ were 13.60 m or deeper with one area of exception (Figure 40). 

The LIQ (Left Inside Quarter) has a controlling depth of 13.50 meters. It was observed that nearly all surveyed depths from the 50 cm surface within the RIQ were 13.50 meters or deeper with one area of exception along the northern boundary (Figure 41). These depths are very close to 13.50 m and off by 1 or 2 cm. 

The LOQ (Left Outside Quarter) has a controlling depth of 10.10 meters. It was observed that nearly all surveyed depths from the H13173_MB_50cm_MLLW_Final surface were 10.10 meters or deeper with one exception along the northern boundary (Figure 42). Depths less than 10.10 meters extend less than 3 meters into the LOQ and drop off very quickly along this edge.

Refer to Supplemental Survey Records and Correspondence for additional information.</ns2:discussion><ns2:images><ns2:caption>Comparison of surveyed depths to the controlling depth for Egmont Channel RIQ.</ns2:caption><ns2:link>SupportFiles\Fig40_H73-ChannelComparison-RIQ.png</ns2:link></ns2:images><ns2:images><ns2:caption>Comparison of surveyed depths to the controlling depth for Egmont Channel LIQ.</ns2:caption><ns2:link>SupportFiles\Fig41_H73-ChannelComparison-LIQ.png</ns2:link></ns2:images><ns2:images><ns2:caption>Comparison of surveyed depths to the controlling depth for Egmont Channel LOQ.</ns2:caption><ns2:link>SupportFiles\Fig42_H73-ChannelComparison-LOQ.png</ns2:link></ns2:images></ns2:results><ns2:comments/></ns1:channels><ns1:bottomSamples><ns2:results investigated="Investigated"><ns2:discussion>Eleven bottom samples were acquired within H13173 survey bounds in accordance with the locations in the PRF. Refer to the FFF for additional information.</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 for this particular Sheet. However, the inshore limit of hydrography and feature verification for Navigable Area Surveys is the Navigable Area Limit Line (NALL), as stated in section 1.3.2 of the HSSD (2018). For this survey the NALL consisted of the 3.5-meter depth contour, which was surveyed north of Egmont Channel. Please refer to the chart comparison section for additional information.</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>Seventeen ATONs and one Special/General Purpose buoy exist within survey bounds. During field operations fixes were recorded in the acquisition logs, as well as heading and estimated distance to the buoys from the vessel (with the exception of Buoy 16 for which no estimated distance from the vessel was logged). Buoy positions were calculated from the aforementioned information and compared to both the CSF and Light List information. 

Egmont Channel Lighted Buoy 4 was noted as missing in the field project logs on 11/9/2019. Review of the District 7 Navigation Center Local Notice to Mariners indicates this buoy was noted as OFF STA/HAZ NAV/SINKING as of LNM 43/18 and discontinued as of LNM 44/18 dated October 31, 2018 with a note to temporarily Delete the buoy from charts 11412 and 11415. LNM 10/19 indicates this buoy was returned to the assigned position. The buoy was again noted as missing as of the 18/19 LNM and reset on location as of LNM 25/19. 

It is also recognized, as of LNM 43/18, that Egmont Channel Light Buoys 9, 11, 12, 13 were relocated for dredging operations. The proximity of the field fix positions to the relocated positions indicate the fixes were obtained at the temporary buoy positions.

The other aids to navigation are determined to be on station. However, review of the Light List Volume III Atlantic and Gulf Coasts (2019) obtained here: https://www.navcen.uscg.gov/pdf/lightlists/LightList_V3_2019.pdf indicates several of the positions from the CSF are different than the positions listed. Please refer to Processed\Reports\Project\HVCR\Digital_B-Horizontal_Control_Data\ATON_Data for additional information.</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>A portion of the 'Gulfstream Natural Gas System' pipeline, as labeled in the Composite Source File, extends east west through the central southwest portion of the survey area. Trench features are evident in the bathymetry data, as well as 2 potential pipeline exposures, which were submitted to BSEE as per the
HSSD (2018). No large material coverings over the pipeline were observed. Data indicate the pipeline is well charted. One submarine cable is also present within the survey bounds. Bathymetric data do not indicate the presence of the cable.  </ns2:discussion></ns2:results><ns2:comments/></ns1:submarineFeatures><ns1:platforms><ns2:results investigated="None Exist"><ns2:discussion>No platforms exist for this survey.</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="Investigated"><ns2:discussion>Drag scars are evident in the bathymetry data and two sets of three square features with numerous contacts were observed (Figure 43). These appear to be purposefully introduced and may be some sort of artificial fish haven, but the purpose is largely unknown.</ns2:discussion><ns2:images><ns2:caption>Abnormal seafloor feature evident in H13173 data.</ns2:caption><ns2:link>SupportFiles\Fig43_H73-AbnormalSeafloorFeature.png</ns2:link></ns2:images></ns2:results><ns2:comments/></ns1:abnormalSeafloorEnviroCond><ns1:constructionOrDredging><ns2:results investigated="None Exist"><ns2:discussion>Review of Local Notice to Mariners (LNM 39/18) indicate dredging activities in Egmont Key Channel (Cuts 1 and 2) in the eastern portion of the survey area commencing September 12, 2018 and ending approximately April 1, 2019. It is also recognized, as of LNM 43/18, that Egmont Channel Light Buoys 9, 11, 12, 13 were relocated for dredging operations. LNM review indicates at least Egmont Channel Lighted Buoys 11 and 12 were returned to their assigned positions as of LNM 06/19. According to LNM 20/19, dredging activities commenced in Egmont Channel Cuts 1 and 2 again around May 10, 2019 until approximately August 2019. However, the field survey logs and field correspondence do not indicate dredging or construction activities taking place during survey operations. </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.</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 meet or exceed requirements as set forth in the NOS Hydrographic Surveys Specifications and Deliverables, Statement of Work and Project Instructions. 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>Scott Melancon</ns2:approverName><ns2:approverTitle>Chief of Party</ns2:approverTitle><ns2:approvalDate>2019-08-16</ns2:approvalDate></ns1:signingPersonnel><ns1:signingPersonnel><ns2:approverName>John Baker</ns2:approverName><ns2:approverTitle>Senior Survey Technician</ns2:approverTitle><ns2:approvalDate>2019-08-16</ns2:approvalDate></ns1:signingPersonnel><ns1:signingPersonnel><ns2:approverName>Nicole Galloway</ns2:approverName><ns2:approverTitle>Geoscientist</ns2:approverTitle><ns2:approvalDate>2019-08-16</ns2:approvalDate></ns1:signingPersonnel><ns1:additionalReports><ns2:reportName>Horizontal and Vertical Control Report</ns2:reportName><ns2:reportDateSent>2019-03-11</ns2:reportDateSent></ns1:additionalReports><ns1:additionalReports><ns2:reportName>Data Acquisition and Processing Report</ns2:reportName><ns2:reportDateSent>2019-06-28</ns2:reportDateSent></ns1:additionalReports></ns1:approvalSheet></ns1:descriptiveReport>