<?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:resultsAndRecommendations><ns1:chartComparison><ns1:methods><ns2:comments/><ns2:discussion>Due to familiarity with the software, chart comparisons were conducted in CARIS using an exported BAG file of the H13172_MB_1m_MLLW_Final surface. A combination of sounding selection layers and user-defined depth ranges were used to compare surveyed soundings to charted depths using tools within the CARIS software. The sounding selection layer was generated from the H13172_MB_1m_MLLW_Final surface using a shoal biased, single-defined radius of 150 and 300 meters, which provided sufficient soundings across the survey area with which to compare charted depths and contours, depending on the scale of the chart. User-defined color maps were generated to match the contour intervals present on US5FL11M, US4FL10M, US4FL18M and USCG07M (Figures 21 - 24).</ns2:discussion><ns2:images><ns2:caption>Color range used to compare H13172 surveyed depths to charted depths (US5FL11M).</ns2:caption><ns2:link>SupportFiles\Fig21-H13172-Chart_Comparison_US5FL11M-ColorMap.png</ns2:link></ns2:images><ns2:images><ns2:caption>Color range used to compare H13172 surveyed depths to charted depths (US4FL10M).</ns2:caption><ns2:link>SupportFiles\Fig22-H13172-Chart_Comparison_US4FL10M-ColorMap.png</ns2:link></ns2:images><ns2:images><ns2:caption>Color range used to compare H13172 surveyed depths to charted depths (US4FL18M).</ns2:caption><ns2:link>SupportFiles\Fig23-H13172-Chart_Comparison_US4FL18M-ColorMap.png</ns2:link></ns2:images><ns2:images><ns2:caption>Color range used to compare H13172 surveyed depths to charted depths (USGC07M).</ns2:caption><ns2:link>SupportFiles\Fig24-H13172-Chart_Comparison_USGC07M-ColorMap.png</ns2:link></ns2:images></ns1:methods><ns1:bottomSamples><ns2:comments/><ns2:results investigated="Investigated"><ns2:discussion>A total of seven bottom samples were acquired within the H13172 survey area. Another two were attempted, but no sample obtained. Refer to the Final Feature File for additional information.</ns2:discussion></ns2:results></ns1:bottomSamples><ns1:charts><ns2:comments/><ns2:ENC><ns2:comments/><ns2:discussion>NOAA Local Notice to Mariners (LNM) were reviewed subsequent to the date of the Project Instructions and before the end of the survey for RNC 11415. The last LNM reviewed for Chart: 11415, Current Edition: 13, Print Date: Nov. /2018, Tampa Bay Entrance; Manatee River Extension was LNM 14/19, 7th Dist posted on 3/28/2019 to add a Sounding in Feet. No LNM were issued within the survey bounds subsequent to the date of the Project Instructions and the before the end of the survey.

The 0.9, 1.8, 3.6, 5.4 and 9.1-meter contours are present on chart US5FL11M within the survey area. In general survey data indicate that the contours have shifted east and landward, particularly within the northeast portion of the survey area. For example, there is only one area where survey data indicate soundings between 0 and 0.9 meters while survey data do not indicate depths of this range within the isolated contours to the south (Figure 25). In addition, survey data indicate the 0.9-1.8 meter depth range covers less area than currently charted. Data indicate several currently charted isolated contours no longer exist while at least two new areas outside the currently charted contour are present to the south (Figure 26). Survey data also indicate the 1.8 to 3.6-meter depth range covers less area than currently charted. Data indicate many of the isolated contours west, southwest and south of the main contour no longer exist while in some areas surveyed soundings less than or equal to 3.6 meters extend seaward of the currently charted contour (Figure 27). Survey data indicate surveyed soundings between 3.6 and 5.4 meters are generally located within the currently charted depth area. However, it is evident in the north-central portion of the survey area surveyed soundings equal to or less than 5.4 meters extend seaward of the currently charted contour. In addition, survey data indicate some isolated charted contours are no longer present while new isolated contours exist (Figure 28). Survey data indicate surveyed soundings between 5.4 and 9.1 meters are generally within or near the charted contour, though data indicate several contours have shifted, mainly to the southeast and three isolated charted contours in the southwest portion of the survey area no longer exist. (Figure 29).    

It was difficult to make generalizations about the degree of agreement between charted depths and the selected sounding layer generated from survey data. While review indicates the majority of surveyed soundings are deeper than charted depths by 30 cm - 2.5 meters, a substantial number of surveyed soundings were found to be shallower than charted depths by up to 2 meters, mainly in the northeastern portion of the survey area. These correlate with the above discussion noting the differences between a surface generated from surveyed soundings and charted depths. The shallow soundings were submitted for review and have been added to the FFF.</ns2:discussion><ns2:chart><ns2:edition>47</ns2:edition><ns2:issueDate>2019-05-13</ns2:issueDate><ns2:preliminary>false</ns2:preliminary><ns2:updateApplicationDate>2019-03-11</ns2:updateApplicationDate><ns2:scale>40000</ns2:scale><ns2:name>US5FL11M</ns2:name></ns2:chart><ns2:images><ns2:caption>Comparison of charted 0.9-meter contour to surveyed depths in northeastern portion of H13172. H13172_MB_1m_MLLW_Final surface colored using colormap shown in Figure 21. Charted 0.9-meter contour in red. Red box shows area where survey data indicate surveyed soundings are equal to or less than 0.9 meters.</ns2:caption><ns2:link>SupportFiles\Fig25-H13172-Chart_Comparison_US5FL11M-1.png</ns2:link></ns2:images><ns2:images><ns2:caption>Comparison of charted 1.8-meter contour to surveyed depths in northeastern portion of H13172. H13172_MB_1m_MLLW_Final surface colored using colormap shown in Figure 21. Charted 1.8-meter contour in orange. Orange boxes show areas where survey data indicate surveyed soundings are between 0.9 and 1.8 meters.</ns2:caption><ns2:link>SupportFiles\Fig26-H13172-Chart_Comparison_US5FL11M-2.png</ns2:link></ns2:images><ns2:images><ns2:caption>Comparison of charted 3.6-meter contour to surveyed depths in northeastern portion of H13172. H13172_MB_1m_MLLW_Final surface colored using colormap shown in Figure 21. Charted 3.6-meter contour in yellow. Yellow boxes show areas where survey data indicate surveyed soundings between 1.8 and 3.6 meters extend seaward of the currently charted contour.</ns2:caption><ns2:link>SupportFiles\Fig27-H13172-Chart_Comparison_US5FL11M-3.png</ns2:link></ns2:images><ns2:images><ns2:caption>Comparison of charted 5.4-meter contour to surveyed depths in northeastern portion of H13172. H13172_MB_1m_MLLW_Final surface colored using colormap shown in Figure 21. Charted 5.4-meter contour in green. Green boxes show areas where survey data indicate surveyed soundings between 3.6 and 5.4 meters extend seaward of the currently charted contour. Black circles indicate areas where survey data indicate depths greater than 5.4 meters within 5.4-meter charted contours.</ns2:caption><ns2:link>SupportFiles\Fig28-H13172-Chart_Comparison_US5FL11M-4.png</ns2:link></ns2:images><ns2:images><ns2:caption>Comparison of charted 9.1-meter contour to surveyed depths in northeastern portion of H13172. H13172_MB_1m_MLLW_Final surface colored using colormap shown in Figure 21. Charted 9.1-meter contour in blue. Blue boxes show areas where survey data indicate surveyed soundings between 5.4 and 9.1 meters extend southeast of the currently charted contour.</ns2:caption><ns2:link>SupportFiles\Fig29-H13172-Chart_Comparison_US5FL11M-5.png</ns2:link></ns2:images></ns2:ENC><ns2:ENC><ns2:comments/><ns2:discussion>NOAA Local Notice to Mariners (LNM) were reviewed subsequent to the date of the Project Instructions and before the end of the survey for RNC 11412. The last LNM reviewed for Chart: 11412, Current Edition: 49, Print Date: Feb. /2019, Tampa Bay and St. Joseph Sound was LNM 14/19, 7th Dist posted on 3/28/2019 to add a Sounding in Feet. No LNM were issued within the survey bounds subsequent to the date of the Project Instructions and the before the end of the survey.

Charted contours on US4FL10M are more generalized than those on US5FL11M, but follow the same trend; no large discrepancies between charted depths were observed between the two charts. Observations made for US5FL11M are valid for US4FL10M with one exception. The 10.9-meter contour is present on US4FL10M that was not present on US5FL11M. Survey data indicate surveyed soundings 9.1-10.9 meters are generally located within the charted contour but that surveyed soundings greater than 10.9 meters extend inside the currently charted contour area (Figure 30).</ns2:discussion><ns2:chart><ns2:edition>34</ns2:edition><ns2:issueDate>2019-05-13</ns2:issueDate><ns2:preliminary>false</ns2:preliminary><ns2:updateApplicationDate>2019-03-18</ns2:updateApplicationDate><ns2:scale>80000</ns2:scale><ns2:name>US4FL10M</ns2:name></ns2:chart><ns2:images><ns2:caption>Comparison of charted 10.9-meter contour to surveyed depths in western portion of H13172. H13172_MB_1m_MLLW_Final surface colored using colormap shown in Figure 22. Charted 10.9-meter contour in blue.</ns2:caption><ns2:link>SupportFiles\Fig30-H13172-Chart_Comparison_US4FL10M-1.png</ns2:link></ns2:images></ns2:ENC><ns2:ENC><ns2:comments/><ns2:discussion>NOAA Local Notice to Mariners (LNM) were reviewed subsequent to the date of the Project Instructions and before the end of the survey for RNC 11424. The last LNM reviewed for Chart: 11424, Current Edition: 21, Print Date: Apr. /2019, Lemon Bay to Passage Key Inlet was LNM 14/19, 7th Dist posted on 3/28/2019 to add a Sounding in Feet. No LNM were issued within the survey bounds subsequent to the date of the Project Instructions and the before the end of the survey.

The very southern portion of the survey area overlaps a small area of chart US4FL18M mainly between the charted 9.1 and 10.9-meter contours. Survey data indicate surveyed soundings greater than 10.9 meters extend eastward of the currently charted contour and while there are some isolated areas less than 9.1 meters at the very edge of the chart overlap, there is a charted contour indicating charted depths less than 9.1 meters; surveyed soundings indicate that depths in this area are 9.1 meters or deeper (Figure 31). </ns2:discussion><ns2:chart><ns2:edition>20</ns2:edition><ns2:issueDate>2018-11-19</ns2:issueDate><ns2:preliminary>false</ns2:preliminary><ns2:updateApplicationDate>2018-03-05</ns2:updateApplicationDate><ns2:scale>80000</ns2:scale><ns2:name>US4FL18M</ns2:name></ns2:chart><ns2:images><ns2:caption>Comparison of charted 9.1-meter contour to surveyed depths in southern portion of H13172. H13172_MB_1m_MLLW_Final surface colored using colormap shown in Figure 23. Charted 9.1-meter contour in red and yellow. Yellow contour indicates area where surveyed soundings are greater than 9.1 meters and deeper than the currently charted contour.</ns2:caption><ns2:link>SupportFiles\Fig31-H13172-Chart_Comparison_US4FL18M-1.png</ns2:link></ns2:images></ns2:ENC><ns2:ENC><ns2:comments/><ns2:discussion>NOAA Local Notice to Mariners (LNM) were reviewed subsequent to the date of the Project Instructions and before the end of the survey for RNC 11420. The last LNM reviewed for Chart: 11420, Current Edition: 32, Print Date: Oct. /2018, Havana to Tampa Bay was LNM 12/19, 7th Dist posted on 3/28/2019 to delete Fort Jefferson Lighted Buoy L. No LNM were issued within the survey bounds subsequent to the date of the Project Instructions and the before the end of the survey.

Due to the scale of the chart, the contours are broad and the soundings sparse as compared to the previous charts. The 5.4 and 9.1-meter contours are present within the survey area. In general, it is evident that surveyed soundings of a particular depth range fall within the charted contours, though there are some differences. Survey data indicate surveyed soundings less than 5.4 meters extend north of the currently charted contour in the north, northeastern and central-eastern portions of the survey area while survey data indicate surveyed soundings greater than 9.1 meters are present within the isolated charted 9.1-meter contour in the southwest portion of the survey area. Survey data also indicate several isolated contours are present that are not currently charted (Figure 32). Surveyed soundings are generally deeper than charted depths by 30 cm - 3 meters, though there is one charted 10-meter depth in the south central portion of the survey area that matches with surveyed soundings well (Figure 33). </ns2:discussion><ns2:chart><ns2:edition>34</ns2:edition><ns2:issueDate>2019-05-08</ns2:issueDate><ns2:preliminary>false</ns2:preliminary><ns2:updateApplicationDate>2019-03-11</ns2:updateApplicationDate><ns2:scale>350000</ns2:scale><ns2:name>US3GC07M</ns2:name></ns2:chart><ns2:images><ns2:caption>Comparison of charted contours to surveyed depths for H13172. H13172_MB_1m_MLLW_Final surface colored using colormap shown in Figure 24. Charted 5.4-meter contour in red and charted 9.1-meter contour in green. Red and green boxes indicate areas where surveyed soundings shallower than the respective contour extend past the respective contour.</ns2:caption><ns2:link>SupportFiles\Fig32-H13172-Chart_Comparison_USGC07M-1.png</ns2:link></ns2:images><ns2:images><ns2:caption>Comparison of charted depths to surveyed soundings for H13172. H13172_MB_1m_MLLW_Final surface colored using colormap shown in Figure 24.</ns2:caption><ns2:link>SupportFiles\Fig33-H13172-Chart_Comparison_USGC07M-2.png</ns2:link></ns2:images></ns2:ENC></ns1:charts><ns1:chartedFeatures><ns2:comments/><ns2:results investigated="Investigated"><ns2:discussion>Prior to starting survey operations, the Composite Source File (CSF) indicated 14 charted features within the survey limits that were assigned for investigation: one Aid to Navigation (with fog signal and light not counted as separate features), one Fish Haven Area, one pipeline, two wrecks, two discrete obstructions, one area obstruction, two land areas and four shoreline features. Unassigned features include five spoil areas partially within the survey area and the navigation fairway south of Egmont Channel.</ns2:discussion></ns2:results></ns1:chartedFeatures><ns1:shoalAndHazardousFeatures><ns2:comments/><ns2:results investigated="Investigated"><ns2:discussion>Two discrete obstructions were submitted as Dangers to Navigation for this survey. In addition, a substantial number of sounding features where survey data indicate shallower depths than currently charted were submitted for review. Four were accepted as DtoNs. Refer to the Final Feature File and Supplemental Survey Records and Correspondence for additional information.</ns2:discussion></ns2:results></ns1:shoalAndHazardousFeatures><ns1:channels><ns2:comments/><ns2:results investigated="Investigated"><ns2:discussion> H13172 is south of Egmont Channel and the survey area covers a portion of the safety fairway around Egmont Channel. In general, surveyed soundings are deeper than charted depths in this area but there are two areas in particular where surveyed soundings are shallower than charted depths (Figure 34).</ns2:discussion><ns2:images><ns2:caption>Comparison of charted depths to surveyed soundings within the safety fairway south of Egmont Channel.</ns2:caption><ns2:link>SupportFiles\Fig34-H13172-Fairway.png</ns2:link></ns2:images></ns2:results></ns1:channels><ns1:maritimeBoundary><ns2:comments/><ns2:results investigated="None Exist"><ns2:discussion>No Maritime Boundary Points were assigned for this survey.</ns2:discussion></ns2:results></ns1:maritimeBoundary><ns1:unchartedFeatures><ns2:comments/><ns2:results investigated="Investigated"><ns2:discussion> An additional nine discrete features and one area feature were added to the Final Feature File that were not addressed as Dangers to Navigation due to factors such as charted depths, proximity to charted features, or proximity to other DtoNs. Refer to the Final Feature File for additional information.</ns2:discussion></ns2:results></ns1:unchartedFeatures></ns1:chartComparison><ns1:additionalResults><ns1:otherResults><ns2:comments/></ns1:otherResults><ns1:ATONS><ns2:comments/><ns2:results investigated="Investigated"><ns2:discussion>One ATON was assigned for investigation during this survey and was determined to be on station. Please refer the the Final Feature File and ATON_Data in the deliverables folders for additional information. In addition, the field took fixes on three small buoys near the Egmont Key Ruins, which were called 'swim buoys' in the logs; one of the fixes fell within the bounds of the survey area. Please refer to Detached_Positions in the deliverables folders for additional information.</ns2:discussion></ns2:results></ns1:ATONS><ns1:insetRecommendation><ns2:comments/><ns2:results recommended="false"><ns2:discussion>No new insets are recommended for this area.</ns2:discussion></ns2:results></ns1:insetRecommendation><ns1:shoreline><ns2:comments/><ns2:results investigated="Investigated"><ns2:discussion>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 defined along the northeastern corner of the survey area, seaward of Egmont Key. Two shoreline features and two shoreline/landarea features were assigned for investigation. Refer to the FFF for additional information.</ns2:discussion></ns2:results></ns1:shoreline><ns1:newSurveyRecommendation><ns2:comments/><ns2:results recommended="false"><ns2:discussion>No new surveys or further investigations are recommended for this area.</ns2:discussion></ns2:results></ns1:newSurveyRecommendation><ns1:overheadFeatures><ns2:comments/><ns2:results investigated="None Exist"><ns2:discussion>No overhead features exist for this survey.</ns2:discussion></ns2:results></ns1:overheadFeatures><ns1:submarineFeatures><ns2:comments/><ns2:results investigated="Investigated"><ns2:discussion>One pipeline, labeled as the 'Gulfstream Natural Gas System' in the CSF file, extends generally northwest/southeast through the survey area. Four potential exposures were identified along the pipeline and submitted to BSEE as per the HSSD (2018). Refer to the Supplemental Survey Records and Correspondence and the Final Feature File for additional information.</ns2:discussion></ns2:results></ns1:submarineFeatures><ns1:abnormalSeafloorEnviroCond><ns2:comments/><ns2:results investigated="Investigated"><ns2:discussion>An area of abnormal seafloor was identified where the MBES appears to have had difficulty detecting the bottom. Review of the SSS data indicates bottom change in this area. Where the seafloor could not be accurately determined from the bathymetry data, the MBES data was rejected completely; nadir coverage still exists (Figure 35).</ns2:discussion><ns2:images><ns2:caption>Abnormal seafloor area where the MBES had difficulty detecting bottom.</ns2:caption><ns2:link>SupportFiles\Fig35-H13172_Abnormal_Seafloor_Conditions.png</ns2:link></ns2:images></ns2:results></ns1:abnormalSeafloorEnviroCond><ns1:constructionOrDredging><ns2:comments/><ns2:results investigated="None Exist"><ns2:discussion>No present or planned construction or dredging exist within the survey limits.</ns2:discussion></ns2:results></ns1:constructionOrDredging><ns1:platforms><ns2:comments/><ns2:results investigated="None Exist"><ns2:discussion>No platforms exist for this survey.</ns2:discussion></ns2:results></ns1:platforms><ns1:ferryRoutesAndTerminals><ns2:comments/><ns2:results investigated="None Exist"><ns2:discussion>No ferry routes or terminals exist for this survey.</ns2:discussion></ns2:results></ns1:ferryRoutesAndTerminals><ns1:priorSurveys><ns2:comments/><ns2:results investigated="None Exist"><ns2:discussion>No prior survey comparisons exist for this survey.</ns2:discussion></ns2:results></ns1:priorSurveys></ns1:additionalResults></ns1:resultsAndRecommendations><ns1:areaSurveyed><ns1:coverageGraphic><ns2:coverageGraphicImage><ns2:images><ns2:caption>H13172 Survey Coverage</ns2:caption><ns2:link>SupportFiles\Fig2-H13172_Survey_Coverage.png</ns2:link></ns2:images></ns2:coverageGraphicImage></ns1:coverageGraphic><ns1:surveyStatistics><ns2:totalSurveyStats><ns2:DP>45</ns2:DP><ns2:diveOps>0</ns2:diveOps><ns2:bottomSamples>7</ns2:bottomSamples><ns2:maritimeBoundaryPoints>0</ns2:maritimeBoundaryPoints><ns2:SNM>26.79</ns2:SNM></ns2:totalSurveyStats><ns2:comments/><ns2:surveyDates>2018-10-17</ns2:surveyDates><ns2:surveyDates>2018-10-18</ns2:surveyDates><ns2:surveyDates>2018-11-13</ns2:surveyDates><ns2:surveyDates>2018-11-14</ns2:surveyDates><ns2:surveyDates>2018-11-17</ns2:surveyDates><ns2:surveyDates>2018-11-18</ns2:surveyDates><ns2:surveyDates>2018-11-19</ns2:surveyDates><ns2:surveyDates>2018-11-20</ns2:surveyDates><ns2:surveyDates>2018-11-21</ns2:surveyDates><ns2:surveyDates>2018-11-22</ns2:surveyDates><ns2:surveyDates>2018-11-23</ns2:surveyDates><ns2:surveyDates>2018-11-24</ns2:surveyDates><ns2:surveyDates>2018-11-29</ns2:surveyDates><ns2:surveyDates>2019-11-30</ns2:surveyDates><ns2:surveyDates>2019-02-05</ns2:surveyDates><ns2:surveyDates>2019-02-06</ns2:surveyDates><ns2:surveyDates>2019-02-07</ns2:surveyDates><ns2:surveyDates>2019-02-08</ns2:surveyDates><ns2:surveyDates>2019-02-10</ns2:surveyDates><ns2:surveyDates>2019-02-11</ns2:surveyDates><ns2:surveyDates>2019-02-12</ns2:surveyDates><ns2:surveyDates>2019-02-21</ns2:surveyDates><ns2:surveyDates>2019-02-22</ns2:surveyDates><ns2:surveyDates>2019-02-23</ns2:surveyDates><ns2:surveyDates>2019-02-24</ns2:surveyDates><ns2:surveyDates>2019-03-09</ns2:surveyDates><ns2:surveyDates>2019-03-25</ns2:surveyDates><ns2:surveyDates>2019-03-26</ns2:surveyDates><ns2:surveyDates>2019-03-29</ns2:surveyDates><ns2:LNM><ns2:totalLNM><ns2:MS_SBES_MBES>0.00</ns2:MS_SBES_MBES><ns2:MS_SBES>0.00</ns2:MS_SBES><ns2:MS_SSS>0.00</ns2:MS_SSS><ns2:MS_MBES_SSS>871.90</ns2:MS_MBES_SSS><ns2:XL_lidar>0.00</ns2:XL_lidar><ns2:percentXLLNM>5.37</ns2:percentXLLNM><ns2:MS_MBES>0.00</ns2:MS_MBES><ns2:MS_SBES_SSS>0.00</ns2:MS_SBES_SSS><ns2:XL_MBES_SBES>46.79</ns2:XL_MBES_SBES><ns2:MS_lidar>0.00</ns2:MS_lidar></ns2:totalLNM><ns2:vesselLNM><ns2:vessel><ns2:hullID>JQN00027J708</ns2:hullID><ns2:statistics><ns2:MS_SBES_MBES>0.00</ns2:MS_SBES_MBES><ns2:MS_SBES>0.00</ns2:MS_SBES><ns2:MS_SSS>0.00</ns2:MS_SSS><ns2:MS_MBES_SSS>871.90</ns2:MS_MBES_SSS><ns2:XL_lidar>0.00</ns2:XL_lidar><ns2:MS_MBES>0.00</ns2:MS_MBES><ns2:MS_SBES_SSS>0.00</ns2:MS_SBES_SSS><ns2:XL_MBES_SBES>46.79</ns2:XL_MBES_SBES><ns2:MS_lidar>0.00</ns2:MS_lidar></ns2:statistics></ns2:vessel></ns2:vesselLNM></ns2:LNM><ns2:discussion>Detached Positions include CTD fixes (including two re-casts), one ATON fix and one fix of a small uncharted buoy near Egmont Ruins (called a 'swim buoy' in the field logs). Bottom sample fixes are not included in Detached Positions because there is a separate entry for those. Bottom sample total includes only those for which a sample was obtained; please refer to section D.1.7 for additional information. The total SNM includes the main H13172 survey area, a detached assigned investigation and a small MB coverage only area in the northeast portion of the survey area connected to the main survey area by a NALL investigation line.</ns2:discussion></ns1:surveyStatistics><ns1:surveyQuality><ns2:comments/><ns2:adequacy>The entire survey is adequate to supersede previous data.</ns2:adequacy><ns2:discussion xsi:nil="true"></ns2:discussion></ns1:surveyQuality><ns1:surveyCoverage><ns2:comments/><ns2:coverageRequirement><ns2:waterDepth>All waters in the survey area (except Sheet 4)</ns2:waterDepth><ns2:requiredCoverage>Complete 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 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="false"><ns2:discussion>Survey coverage was in accordance with the requirements listed above and in the HSSD.</ns2:discussion></ns2:results></ns1:surveyCoverage><ns1:areaDescription><ns2:limits><ns2:southEast><ns2:longitude hemisphere="W">82.7573508056</ns2:longitude><ns2:latitude hemisphere="N">27.47792475</ns2:latitude></ns2:southEast><ns2:northWest><ns2:longitude hemisphere="W">82.8677381944</ns2:longitude><ns2:latitude hemisphere="N">27.6077272778</ns2:latitude></ns2:northWest></ns2:limits><ns2:comments/><ns2:discussion>The survey area is located in the Vicinity of Southwest Channel, in the general locality of the Approaches to Tampa Bay, Florida.</ns2:discussion></ns1:areaDescription><ns1:surveyPurpose><ns2:comments/><ns2:discussion>The purpose of the project is to provide contemporary surveys to update National Ocean Service nautical charting products to support an increase in vessel traffic into Tampa Bay. There is a lack of modern data in the area and the area is subject to strong storm events that have the potential to cause shoaling.</ns2:discussion></ns1:surveyPurpose><ns1:surveyLimits><ns2:comments/><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:images><ns2:caption>H13172 Survey Limits</ns2:caption><ns2:link>SupportFiles\Fig1-H13172_Survey_Limits.png</ns2:link></ns2:images></ns2:results></ns1:surveyLimits></ns1:areaSurveyed><ns1:metadata><ns1:projectMetadata><ns2:fieldUnit>Oceaneering</ns2:fieldUnit><ns2:name>Approaches to Tampa Bay, FL</ns2:name><ns2:generalLocality>Approaches to Tampa Bay, FL</ns2:generalLocality><ns2:number>OPR-J317-KR-18</ns2:number></ns1:projectMetadata><ns1:assignment>Contractor</ns1:assignment><ns1:surveyMetadata><ns2:year>2018</ns2:year><ns2:chiefOfParty>Scott Melancon</ns2:chiefOfParty><ns2:equipmentTypes><ns2:imageryEquipment>Side Scan Sonar</ns2:imageryEquipment><ns2:soundingEquipment>Multibeam Echo Sounder</ns2:soundingEquipment></ns2:equipmentTypes><ns2:PIDate>2018-07-17</ns2:PIDate><ns2:acquisition><ns2:units>meters</ns2:units></ns2:acquisition><ns2:titlesheetRemarks><ns2:fieldRemarks xsi:nil="true"></ns2:fieldRemarks><ns2:branchRemarks>The purpose of this survey is to provide contemporary surveys to update National Ocean Service (NOS) nautical charts. All separates are filed with the hydrographic data. Any revisions to the Descriptive Report (DR) generated during office processing are shown in bold red italic text. The processing branch maintains the DR as a field unit product, therefore, all information and recommendations within the body of the DR are considered preliminary unless otherwise noted. The final disposition of surveyed features is represented in the OCS nautical chart update products. All pertinent records for this survey, including the DR, are archived at the National Centers for Environmental Information (NCEI) and can be retrieved via http://www.ncei.noaa.gov/.
</ns2:branchRemarks></ns2:titlesheetRemarks><ns2:horizontalCoordinateSystem zone="17N">Universal Transverse Mercator (UTM)</ns2:horizontalCoordinateSystem><ns2:timeZone>UTC</ns2:timeZone><ns2:projectType>Navigable Area</ns2:projectType><ns2:datesOfSurvey><ns2:start>2018-10-17</ns2:start><ns2:end>2019-03-29</ns2:end></ns2:datesOfSurvey><ns2:verifier>Atlantic Hydrographic Branch</ns2:verifier></ns1:surveyMetadata><ns1:registryMetadata><ns2:stateOrTerritory>Florida</ns2:stateOrTerritory><ns2:registryNumber>H13172</ns2:registryNumber><ns2:registryInstructions xsi:nil="true"></ns2:registryInstructions><ns2:scale>20000</ns2:scale><ns2:sheetID>3</ns2:sheetID><ns2:sublocality>Vicinity of Southwest Channel</ns2:sublocality><ns2:country>United States</ns2:country></ns1:registryMetadata></ns1:metadata><ns1:dataAcquisitionAndProcessing><ns1:echoSoundingCorrections><ns1:additionalIssues><ns2:comments/></ns1:additionalIssues><ns1:calibrations><ns2:comments/><ns2:results deviation="false"><ns2:calibration xsi:nil="true"/><ns2:discussion>All sounding systems were calibrated as detailed in the DAPR.</ns2:discussion></ns2:results></ns1:calibrations><ns1:corrections><ns2:comments/><ns2:results deviation="false"><ns2:discussion>All data reduction procedures conform to those detailed in the DAPR.</ns2:discussion></ns2:results></ns1:corrections></ns1:echoSoundingCorrections><ns1:equipmentAndVessels><ns1:comments/><ns1:equipment><ns1:discussion xsi:nil="true"></ns1:discussion><ns1:majorSystem><ns2:type>MBES</ns2:type><ns2:manufacturer>Kongsberg Maritime</ns2:manufacturer><ns2:model>EM 3002</ns2:model></ns1:majorSystem><ns1:majorSystem><ns2:type>SSS</ns2:type><ns2:manufacturer>EdgeTech</ns2:manufacturer><ns2:model>4200</ns2:model></ns1:majorSystem><ns1:majorSystem><ns2:type>Positioning and Attitude System</ns2:type><ns2:manufacturer>CodaOctopus</ns2:manufacturer><ns2:model>F180</ns2:model></ns1:majorSystem><ns1:majorSystem><ns2:type>Positioning System</ns2:type><ns2:manufacturer>C-Nav</ns2:manufacturer><ns2:model>3050</ns2:model></ns1:majorSystem><ns1:majorSystem><ns2:type>Conductivity, Temperature, and Depth Sensor</ns2:type><ns2:manufacturer>Sea-Bird Scientific</ns2:manufacturer><ns2:model>SBE 19plus</ns2:model></ns1:majorSystem><ns1:majorSystem><ns2:type>Conductivity, Temperature, and Depth Sensor</ns2:type><ns2:manufacturer>YSI</ns2:manufacturer><ns2:model>600R-BCR-C-T</ns2:model></ns1:majorSystem><ns1:comments/></ns1:equipment><ns1:discussion>Refer to the Data Acquisition and Processing Report (DAPR) for a complete description of data acquisition and processing systems, survey vessels, quality control procedures and data processing methods.  Additional information to supplement sounding and survey data, and any deviations from the DAPR are discussed in the following sections.</ns1:discussion><ns1:vessels><ns1:discussion>The R/V C-Wolf (Hull ID JQN00027J708) was used as the survey platform for all data acquisition within H13172.</ns1:discussion><ns1:vessel><ns2:draft units="meters">0.762</ns2:draft><ns2:hullID>JQN00027J708</ns2:hullID><ns2:LOA units="meters">9.144</ns2:LOA></ns1:vessel><ns1:comments/></ns1:vessels></ns1:equipmentAndVessels><ns1:dataProcessing><ns1:drSoftware><ns1:featureObjectCatalog>noaa_custom.xml and CUBEParams.xml</ns1:featureObjectCatalog><ns1:imagerySoftware deviation="true"><ns1:version>V6005.0025</ns1:version><ns1:manufacturer>Chesapeake Technology</ns1:manufacturer><ns1:name>SonarWiz</ns1:name></ns1:imagerySoftware><ns1:bathySoftware deviation="true"><ns1:version>1.7.6</ns1:version><ns1:manufacturer>QPS</ns1:manufacturer><ns1:name>Qimera</ns1:name></ns1:bathySoftware><ns1:discussion>Qimera installs the standard NOAA custom attributes and are available by default to all users. The above referenced XML files are located within C:\Users\Public\Documents\QPS\Shared\Charts\Custom Attributes and C:\Users\Public\Documents\QPS\Resources, respectively.

Qimera was used to process, clean and review all MBES data collected for H13172 as well as create all bathymetric surfaces. However, CARIS was still used for some review and evaluation procedures including: generating the final survey outline and obtaining area for the total SNM in Table 3, generation of the final SSS contact list and chart comparisons including LNM. In addition, a combination of Qimera and CARIS was used to generate the FFF. </ns1:discussion><ns1:comments/></ns1:drSoftware><ns1:additionalDataProcessing><ns2:comments/><ns2:issue><ns2:comments/><ns2:title>MBES Data Review</ns2:title><ns2:discussion>The data were filtered using a medium spline filter and surfaces examined systematically. The FlierFinder utility within HydrOffice QCTools was used as an additional quality control tool to evaluate the surfaces for fliers. Identified fliers were manually rejected.  </ns2:discussion></ns2:issue></ns1:additionalDataProcessing><ns1:surfaces><ns1:comments/><ns1:discussion>The least depths of contacts that met the threshold for designation (2 m x 2 m x 1 m) or were significant due to other distinguishing characteristics were set as 'custom hypotheses' in Qimera (and subsequently added to the FFF). This ensured the CUBE grid honored these least depths automatically upon updating the Dynamic Surface from edits. No additional finalization parameters were used. Features, both significant, insignificant and shoal soundings were also set as 'Features' to aid in the processing workflow. The fully cleaned CUBE surfaces were exported from Qimera as BAG files and appended with 'Final' as per the HSSD (2018) naming convention for MBES bathymetric surfaces.</ns1:discussion><ns1:surface><ns2:surfaceParameter>NOAA_1m</ns2:surfaceParameter><ns2:depthRange><ns2:max units="meters">16.34</ns2:max><ns2:min units="meters">0.33</ns2:min></ns2:depthRange><ns2:surfaceName>H13172_MB_1m_MLLW_Final</ns2:surfaceName><ns2:surfaceType>BAG</ns2:surfaceType><ns2:resolution units="meters">1</ns2:resolution><ns2:purpose>Complete MBES</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceParameter>NOAA_0.5m</ns2:surfaceParameter><ns2:depthRange><ns2:max units="meters">12.42</ns2:max><ns2:min units="meters">10.05</ns2:min></ns2:depthRange><ns2:surfaceName>H13172_MB_50cm_MLLW_1of2_Final</ns2:surfaceName><ns2:surfaceType>BAG</ns2:surfaceType><ns2:resolution units="meters">0.5</ns2:resolution><ns2:purpose>Object Detection</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceParameter>NOAA_0.5m</ns2:surfaceParameter><ns2:depthRange><ns2:max units="meters">9.94</ns2:max><ns2:min units="meters">4.15</ns2:min></ns2:depthRange><ns2:surfaceName>H13172_MB_50cm_MLLW_2of2_Final</ns2:surfaceName><ns2:surfaceType>BAG</ns2:surfaceType><ns2:resolution units="meters">0.5</ns2:resolution><ns2:purpose>Object Detection</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceParameter>N/A</ns2:surfaceParameter><ns2:depthRange><ns2:max xsi:nil="true"/><ns2:min xsi:nil="true"/></ns2:depthRange><ns2:surfaceName>H13172_SSSAB_1m_545kHz_1of2</ns2:surfaceName><ns2:surfaceType>SSS Mosaic</ns2:surfaceType><ns2:resolution units="meters">1</ns2:resolution><ns2:purpose>100% SSS</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceParameter>N/A</ns2:surfaceParameter><ns2:depthRange><ns2:max xsi:nil="true"/><ns2:min xsi:nil="true"/></ns2:depthRange><ns2:surfaceName>H13172_SSSAB_1m_545kHz_2of2</ns2:surfaceName><ns2:surfaceType>SSS Mosaic</ns2:surfaceType><ns2:resolution units="meters">1</ns2:resolution><ns2:purpose>200% SSS</ns2:purpose></ns1:surface></ns1:surfaces></ns1:dataProcessing><ns1:qualityControl><ns1:uncertainty><ns2:comments/><ns2:values><ns2:soundSpeedUncertainty><ns2:surface units="meters/second">0.8</ns2:surface><ns2:measuredCTD units="meters/second">2</ns2:measuredCTD><ns2:measuredMVP units="meters/second">n/a</ns2:measuredMVP><ns2:hullID>JQN00027J708</ns2:hullID></ns2:soundSpeedUncertainty></ns2:values><ns2:discussion>Surveyed soundings were reduced to MLLW using an ellipsoid separation model within the Qimera data processing software. The Total Propagated Uncertainty (TPU) for each sounding was computed within Qimera. No tide uncertainties were added for either a measured or zoning value. The vessel configuration editor within Qimera stores static values of the estimated uncertainties associated with each individual sensor. Internal verification indicates that 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. Qimera 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 Qimera. The 1-sigma VDATUM Maximum Combined Uncertainty (MCU) value for the separation model (13.1 cm) is provided in the project instructions. The vertical uncertainties associated with the positioning system and separation model were entered in the vessel editor and processing parameters editor, respectively, as shown in the DAPR. There are three places to enter uncertainty associated with the surface sound speed, which was entered in the transducer TPU location, as specified in the DAPR. The uncertainty associated with the measured CTD was entered within each individual sound velocity profile in the SVP Editor (Figure 6).

An uncertainty layer is generated during the CUBE dynamic surface creation process that shows the uncertainty at each node of the surface. HydrOffice QCTools was used to analyze the uncertainty of the final exported BAG files, which contain depth and uncertainty information. Greater than 99% of nodes of the H13172_MB_1m_MLLW_Final surface meet specifications (Figure 7). Areas of higher uncertainty are generally associated with seafloor features and areas where overlapping data are separated by a time period at which the data indicate differences in seafloor bathymetry between time 1 and time 2; residual noise may also show higher uncertainty. Five nodes of the H13172_MB_50cm_MLLW_1of2_Final surface do not meet specifications (Figure 8), which are associated with a contact. All nodes of the H13172_MB_50cm_MLLW_2of2_Final surface meet specifications (Figure 9).</ns2:discussion><ns2:images><ns2:caption>Uncertainty associated with the measured CTD.</ns2:caption><ns2:link>SupportFiles\Fig6-H13172_SD_Sound_Speed.png</ns2:link></ns2:images><ns2:images><ns2:caption>Uncertainty QA output from HydrOffice QCTools for surface H13172_MB_1m_MLLW_Final.</ns2:caption><ns2:link>SupportFiles\Fig7-H13172_MB_1m_MLLW_Final.QAv5.tvu_qc.png</ns2:link></ns2:images><ns2:images><ns2:caption>Uncertainty QA output from HydrOffice QCTools for surface H13172_MB_50cm_MLLW_1of2_Final.</ns2:caption><ns2:link>SupportFiles\Fig8-H13172_MB_50cm_MLLW_1of2_Final.QAv5.tvu_qc.png</ns2:link></ns2:images><ns2:images><ns2:caption>Uncertainty QA output from HydrOffice QCTools for surface H13172_MB_50cm_MLLW_2of2_Final.</ns2:caption><ns2:link>SupportFiles\Fig9-H13172_MB_50cm_MLLW_2of2_Final.QAv5.tvu_qc.png</ns2:link></ns2:images></ns1:uncertainty><ns1:additionalQualityControl><ns2:comments/><ns2:issue><ns2:comments/><ns2:title>Density</ns2:title><ns2:discussion>The Snapshot as Static Surface tool was used within Qimera to generate a Static Surface of the Bin Count (sounding density) layer of each final surface. The attached scalar (bin count) objects were exported as XYZ and further analyzed in either Microsoft Excel or a text editor, depending on the size of the file. It was observed that the density of the final surfaces meet the requirements for which at least 95% of all nodes on the surface shall be populated with at least 5 soundings. Histograms of the extracted sounding density surfaces were generated using Fledermaus (Figures 17 - 19).  Very large density values of the H13172_MB_1m_MLLW_Final surface are associated with one area in particular where the vessel track is offline and the MBES appears to ping stationary for a short period of time (Figure 20). The acquisition logs indicate issues with a crab pot; the line was restarted just prior to where it left off.</ns2:discussion><ns2:images><ns2:caption>Histogram of the density layer of the H13172_MB_1m_MLLW_Final surface generated in Fledermaus.</ns2:caption><ns2:link>SupportFiles\Fig17-H13172_MB_1m_MLLW_Final_Density-1.png</ns2:link></ns2:images><ns2:images><ns2:caption>Histogram of the density layer of the H13172_MB_50cm_MLLW_1of2_Final surface generated in Fledermaus.</ns2:caption><ns2:link>SupportFiles\Fig18-H13172_MB_50cm_MLLW_1of2_Final_Density.png</ns2:link></ns2:images><ns2:images><ns2:caption>Histogram of the density layer of the H13172_MB_50cm_MLLW_2of2_Final surface generated in Fledermaus.</ns2:caption><ns2:link>SupportFiles\Fig19-H13172_MB_50cm_MLLW_2of2_Final_Density.png</ns2:link></ns2:images><ns2:images><ns2:caption>Area of H13172_MB_1m_MLLW_Final surface where large density values exist.</ns2:caption><ns2:link>SupportFiles\Fig20-H13172_MB_1m_MLLW_Final_Density-2.png</ns2:link></ns2:images></ns2:issue><ns2:issue><ns2:comments/><ns2:title>Holidays</ns2:title><ns2:discussion>HydrOffice QCTools was used to determine the existence of holidays within all Object Detection MBES grids. No holidays exist within the H13172_MB_50cm_MLLW_1of2_Final surface. Two holidays exist within the H13172_MB_50cm_MLLW_2of2_Final surface, but both are outside the assigned radius. The main Complete Coverage surface was reviewed visually; MBES fill-ins were conducted when possible where along track data gaps existed. MBES data were acquired over all potentially significant contacts and visually inspected for coverage.</ns2:discussion></ns2:issue></ns1:additionalQualityControl><ns1:coverageEquipmentAndMethods><ns2:comments/><ns2:results deviation="true"><ns2:discussion>Mainline coverage within the survey area consisted of Complete Coverage (100% side scan sonar with concurrent multibeam data) acquisition. Feature disprovals were conducted with either 200% SSS or Object Detection Multibeam Coverage. One assigned radius did not have a corresponding feature in the CSF file; this was reviewed with the PM (please refer to Supplemental Survey Records and Correspondence). Data do not indicate the presence of a contact in this location; no feature was added or removed in the FFF file. The one Fish Haven in the area was covered with Object Detection MBES coverage. Data coverage does not exist in the northeastern portion of the survey area where depths are shallower than 3.5 meters. </ns2:discussion></ns2:results></ns1:coverageEquipmentAndMethods><ns1:equipmentEffectiveness><ns2:comments/><ns2:results deviation="true"><ns2:issue><ns2:comments/><ns2:title>Sonar Settings</ns2:title><ns2:discussion>If necessary, the angle of the multibeam sonar was 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. In addition, the MBES transducer was lowered and raised between two positions to mitigate the effects of sea state on data quality. This is noted in the logs and offsets updated in the MBES acquisition software during acquisition; no post-processing of any offsets occurred.</ns2:discussion></ns2:issue><ns2:issue><ns2:comments/><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 14).</ns2:discussion><ns2:images><ns2:caption>H13172_MB_1m_MLLW_Final Surface with slice editor (3x exaggeration) showing the nadir region.</ns2:caption><ns2:link>SupportFiles\Fig14-H13172_Nadir_Artifact.png</ns2:link></ns2:images></ns2:issue><ns2:issue><ns2:comments/><ns2:title>'Seesaw' Pattern Artifacts</ns2:title><ns2:discussion>Noise is evident in the MBES data periodically throughout the survey area. Particularly, artifacts are evident where one side of the swath gets shallower and one side gets deeper for a small period of time. Although it is unclear exactly the cause of this, field correspondence indicates it may be at least in part be due to aeration under the multibeam head. The noise is not systematic, which indicates it is due at least in part to environmental factors. These were most common on days 11-13-2018, 11-14-2018 and 11-18-2018 in the central-west portion of the survey area and cleaned as necessary, though this often left data gaps on either side of nadir (Figure 15).</ns2:discussion><ns2:images><ns2:caption>Port/starboard 'seesaw' artifact evident in MBES data.</ns2:caption><ns2:link>SupportFiles\Fig15-H13172_Artifact.png</ns2:link></ns2:images></ns2:issue><ns2:issue><ns2:comments/><ns2:title>MBES bottom detect in shallow areas</ns2:title><ns2:discussion>In the northeastern portion of the survey area the survey crew collected lines to determine the extent of the NALL. The multibeam system appeared to have difficulty detecting bottom in the shallowest portions of these lines. While the data were cleaned the bottom detect in this area may not be completely reliable (Figure 16). </ns2:discussion><ns2:images><ns2:caption>MBES bottom detect in shallow northeastern portion of the survey area.</ns2:caption><ns2:link>SupportFiles\Fig16-H13172_Shallow_Bottom_Detect.png</ns2:link></ns2:images></ns2:issue></ns2:results></ns1:equipmentEffectiveness><ns1:factorsAffectingSoundings><ns2:comments/><ns2:results deviation="true"><ns2:issue><ns2:comments/><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:issue></ns2:results></ns1:factorsAffectingSoundings><ns1:sonarQCChecks><ns2:comments/><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></ns1:sonarQCChecks><ns1:crosslines><ns2:comments/><ns2:discussion>Crosslines were generally run perpendicular to mainscheme lines in order for quality control statistics to be generated after completion of mainscheme survey lines. The total crossline mileage was 46.79 nautical miles and total mainline coverage was 871.90 nautical miles. Multibeam fill-ins are included in the total mainline mileage. Investigation lines and SSS rerun and fill-in lines for which MBES data were also acquired are not included.

Separate 1-meter mainline and crossline Combined Uncertainty and Bathymetric Estimator (CUBE) surfaces were generated within Qimera and exported to BAG format. The BAG files were imported into Fledermaus and the surface difference tool used to evaluate crossline and mainscheme line agreement. The crossline surface was used as the reference surface and subtracted from the mainline surface using all data with no constraints. The difference surface was exported as an XYZ file and imported into Microsoft Excel for further review. Analysis indicates greater than 97% of difference values are between ±0.3 meters. This is well within the maximum allowable Total Vertical Uncertainty (TVU) for the depths of the comparison area of the mainline surface (0.41 – 16.34 meters), which ranges from ±0.50 to ±0.54 meters. It is evident from the histogram (Figure 3) that some depth differences exceed the maximum allowable TVU. Further examination indicates that depth differences greater than ±0.50 meters are concentrated within the north-central portion of the survey area (Figure 4). It is observed that the majority of the depth differences greater than ±0.50 meters are associated with mainlines collected in 2019 that overlap crosslines collected in 2018. In these areas data indicate that the seafloor is physically different between the mainline and crossline (Figure 5).

The crossline and mainline BAG files, exported difference XYZ file and exported ASCII file of statistical results are located in Separates\II_Digital_Data\Crossline_Comparison.</ns2:discussion><ns2:images><ns2:caption>H13172 crossline comparison depth difference histogram from Fledermaus.</ns2:caption><ns2:link>SupportFiles\Fig3-H13172_Crossline_Comparison_1.png</ns2:link></ns2:images><ns2:images><ns2:caption>H13172 survey area with crosslines in black and mainline data collected in  2019 in yellow. Purple squares indicate areas of overlap where differences are greater than ±0.50 meters.</ns2:caption><ns2:link>SupportFiles\Fig4-H13172_Crossline_Comparison_2.png</ns2:link></ns2:images><ns2:images><ns2:caption>Example of difference between mainline 3156-1 and H72-TIE-303.</ns2:caption><ns2:link>SupportFiles\Fig5-H13172_Crossline_Comparison_3.png</ns2:link></ns2:images></ns1:crosslines><ns1:soundSpeedMethods><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. An Endeco YSI sonde was used to determine the sound speed at the transducer. The multibeam data were corrected for the water column sound speed in realtime using the SIS control software. Sound speed data are located in Separates II Digital Data\Sound Speed Data Summary.</ns1:discussion><ns1:castFrequency>Once per day and more often if necessary.</ns1:castFrequency><ns1:comments/></ns1:soundSpeedMethods><ns1:junctions><ns2:comments/><ns2:junction><ns2:comments/><ns2:survey><ns2:registryNumber>H13173</ns2:registryNumber><ns2:year>2018</ns2:year><ns2:relativeLocation>N</ns2:relativeLocation><ns2:fieldUnit>Oceaneering</ns2:fieldUnit><ns2:scale>20000</ns2:scale></ns2:survey><ns2:discussion>The survey junction between H13172 and H13173 will be addressed in the Descriptive Report for H13173. </ns2:discussion></ns2:junction><ns2:junction><ns2:comments/><ns2:survey><ns2:registryNumber>H13177</ns2:registryNumber><ns2:year>2018</ns2:year><ns2:relativeLocation>W</ns2:relativeLocation><ns2:fieldUnit>Oceaneering</ns2:fieldUnit><ns2:scale>20000</ns2:scale></ns2:survey><ns2:discussion>Sheet H13172 junctions with H13177 to the west. The overlap consists of mainlines and crosslines that extend into the adjoining survey. A difference surface was generated within Fledermaus between exported BAG files of the H13177_MB_1m_MLLW_Final and H13172_MB_1m_MLLW_Final surfaces with H13172 as the reference surface. All depth difference values range from ±0.61 meters with the majority between ±0.18 meters (Figure 11). All depth difference values are less than 2^0.5*TVU for the depths of the survey area; a depth of 0.5 meters has a maximum TVU of 0.5 meters and 2^0.5 * 0.5 meters is 0.707 meters. All depth difference values are less than 0.707 meters.</ns2:discussion><ns2:images><ns2:caption>Color bar showing the range of depth difference values between overlapping data of H13172 and H13177.</ns2:caption><ns2:link>SupportFiles\Fig11-H13172_H13177_Junction-1.png</ns2:link></ns2:images></ns2:junction><ns2:junction><ns2:comments/><ns2:survey><ns2:registryNumber>W00312</ns2:registryNumber><ns2:year>2016</ns2:year><ns2:relativeLocation>N</ns2:relativeLocation><ns2:fieldUnit>LiDAR</ns2:fieldUnit><ns2:scale>20000</ns2:scale></ns2:survey><ns2:discussion>Survey H13172 junctions with W00312 to the north. There is overlap of H13172 mainline and NALL investigation data with the W00312 junction survey as well as one assigned radius in which Object Detection MBES data was acquired for H13172. A difference surface was generated within Fledermaus between the W00312_LI_5m_MLLW_1of1 surface and a subset of the H13172 survey area covering the junction area gridded at 5-meters as the reference surface. The difference surface generated between the two surveys, in general, indicates that the depth data between the two surveys agree fairly well (Figure 12). However, it is evident that some difference values exceed the nominal 0.707-meter threshold specification.

In order to determine the areas where the depth difference values are greater than 2^0.5*TVU the following steps were taken: An XYZ file of the H13172_MB_5m_MLLW surface was exported and a column of 2^0.5*TVU at the particular Z (depth) value generated (junction compliance). The difference surface between the H13172 and W00312 surfaces was also exported as XYZ and an absolute difference column created. The junction compliance (XYZ where Z is 2^0.5*TVU) and absolute difference (XYZ where Z is the absolute difference) files were imported into Fledermaus as gridded files. The absolute difference surface was subtracted from the junction compliance surface. Negative values indicate areas where the depth differences are greater than 2^0.5*TVU. The resulting surface was colored with one color representing positive values and one color representing negative values. There are three locations in particular where the depth difference values are greater than 2^0.5*TVU (Figure 13).</ns2:discussion><ns2:images><ns2:caption>Color bar showing the range of depth difference values between overlapping data of H13172 and W00312.</ns2:caption><ns2:link>SupportFiles\Fig12-H13172_W00312_Junction-1.png</ns2:link></ns2:images><ns2:images><ns2:caption>Overlapping data from H13172 and W00312 overlain with the depth difference surface. Circles indicate areas where the depth difference values exceed 2^0.5*TVU. Yellow circles indicate areas where H13172 data are shallower than W00312 and red circle indicates area where H13172 data are deeper than W00312.</ns2:caption><ns2:link>SupportFiles\Fig13-H13172_W00312_Junction-2.png</ns2:link></ns2:images></ns2:junction><ns2:discussion>Survey H13172 junctions with two contemporary surveys and one historical survey: H13173, H13177 and W00312 (Figure 10). The surface difference tool within QPS' Fledermaus software was used to ensure general agreement of depths. Difference values greater than 2^0.5 * TVU, as outlined in the HSSD, were further evaluated.</ns2:discussion><ns2:images><ns2:caption>H13172 Survey Junctions</ns2:caption><ns2:link>SupportFiles\Fig10-H13172_Survey_Junctions.png</ns2:link></ns2:images></ns1:junctions></ns1:qualityControl><ns1:backscatter><ns2:comments/><ns2:results acquired="true"><ns2:discussion>Raw Backscatter was logged within the Kongsberg .all file and has been sent to the Processing Branch. Backscatter was not processed by the field unit.</ns2:discussion></ns2:results></ns1:backscatter></ns1:dataAcquisitionAndProcessing><ns1:approvalSheet><ns1:statements><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: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:statements><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-05-29</ns2:reportDateSent></ns1:additionalReports><ns1:signingPersonnel><ns2:approverTitle>Chief of Party</ns2:approverTitle><ns2:approverName>Scott Melancon</ns2:approverName><ns2:approvalDate>2019-06-19</ns2:approvalDate></ns1:signingPersonnel><ns1:signingPersonnel><ns2:approverTitle>Geoscientist</ns2:approverTitle><ns2:approverName>Nicole Galloway</ns2:approverName><ns2:approvalDate>2019-06-19</ns2:approvalDate></ns1:signingPersonnel></ns1:approvalSheet><ns1:verticalAndHorizontalControl><ns1:additionalIssues><ns2:comments/></ns1:additionalIssues><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:comments/><ns2:verticalDatum>Mean Lower Low Water</ns2:verticalDatum><ns2:tideStations/><ns2:VDATUM_or_constantSep used="true"><ns2:methodsUsed>ERS via VDATUM</ns2:methodsUsed><ns2:comments/><ns2:discussion>The ellipsoid separation text file (TampaBay_EC_poly_xyNAD83-MLLW_geoid12b.txt) was gridded using Fledermaus with a cell size of 100 meters and saved as an SD file, which was applied in Qimera in Processing Parameters.  </ns2:discussion><ns2:ellipsoidToChartDatumSepFile><ns2:fileName>TampaBay_EC_poly_xyNAD83-17N-MLLW_geoid12b.sd</ns2:fileName></ns2:ellipsoidToChartDatumSepFile></ns2:VDATUM_or_constantSep><ns2:standard_or_ERZT used="false" xsi:nil="true"/></ns1:verticalControl><ns1:horizontalControl><ns2:horizontalDatum>North American Datum 1983</ns2:horizontalDatum><ns2:comments/><ns2:PPK used="false" xsi:nil="true"/><ns2:PPP used="true"><ns2:comments/><ns2:discussion>The positioning systems aboard the vessels utilize Oceaneering® C-Nav® systems which deliver Precise Point Positioning (PPP). The C-Nav® GPS systems receive corrections through the C-Nav® Subscription Services.</ns2:discussion></ns2:PPP><ns2:RTK used="false" xsi:nil="true"/><ns2:DGPS used="false" xsi:nil="true"/><ns2:projection>Projected UTM 17</ns2:projection><ns2:WAAS used="false" xsi:nil="true"/></ns1:horizontalControl></ns1:verticalAndHorizontalControl></ns1:descriptiveReport>