<?xml version="1.0" encoding="UTF-8"?><ns1:descriptiveReport xmlns:ns1="http://svn.pydro.noaa.gov/2018/01/DescriptiveReport" xmlns:ns2="http://svn.pydro.noaa.gov/2018/01/AllGlobalTypes" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://svn.pydro.noaa.gov/2018/01/DescriptiveReport http://svn.pydro.noaa.gov/2018/01/DR.xsd"><ns1:verticalAndHorizontalControl><ns1:discussion>Field installed tide or GPS stations were not utilized for this survey, so no HVCR report is included.</ns1:discussion><ns1:verticalControl><ns2:standard_or_ERZT used="false" xsi:nil="true"/><ns2:verticalDatum>Mean Lower Low Water</ns2:verticalDatum><ns2:tideStations/><ns2:VDATUM_or_constantSep used="true"><ns2:comments/><ns2:discussion>For features with heights above water in the FFF, the Shoreline Attribution Machine (SHAM) within Charlene was used to vertically reference them to MLLW using ERS via VDatum calculation.</ns2:discussion><ns2:ellipsoidToChartDatumSepFile><ns2:fileName>S-B929-BH2-18_Sheets_xyNAD83-MLLW_geoid12b.csar</ns2:fileName></ns2:ellipsoidToChartDatumSepFile><ns2:methodsUsed>ERS via VDATUM</ns2:methodsUsed></ns2:VDATUM_or_constantSep><ns2:comments/></ns1:verticalControl><ns1:horizontalControl><ns2:PPP used="false" xsi:nil="true"/><ns2:DGPS used="false" xsi:nil="true"/><ns2:PPK used="true"><ns2:baseStations><ns2:CORSStations><ns2:stationID>MIDDLETOWN</ns2:stationID><ns2:HVCRSiteID>NYMD</ns2:HVCRSiteID></ns2:CORSStations><ns2:CORSStations><ns2:stationID>NEWBURGH</ns2:stationID><ns2:HVCRSiteID>NYNB</ns2:HVCRSiteID></ns2:CORSStations><ns2:CORSStations><ns2:stationID>VALHALLA</ns2:stationID><ns2:HVCRSiteID>NYVH</ns2:HVCRSiteID></ns2:CORSStations><ns2:CORSStations><ns2:stationID>NJ INST OF TECH 2</ns2:stationID><ns2:HVCRSiteID>NJI2</ns2:HVCRSiteID></ns2:CORSStations><ns2:CORSStations><ns2:stationID>BATTERY PARK</ns2:stationID><ns2:HVCRSiteID>NYBP</ns2:HVCRSiteID></ns2:CORSStations></ns2:baseStations><ns2:comments/><ns2:discussion xsi:nil="true"></ns2:discussion><ns2:methodsUsed>Smart Base</ns2:methodsUsed></ns2:PPK><ns2:horizontalDatum>North American Datum 1983</ns2:horizontalDatum><ns2:comments/><ns2:WAAS used="true"><ns2:discussion>WAAS was used for real-time corrections</ns2:discussion><ns2:comments/></ns2:WAAS><ns2:projection>Projected UTM 18</ns2:projection><ns2:RTK used="false" xsi:nil="true"/></ns1:horizontalControl><ns1:additionalIssues><ns2:issue><ns2:discussion>Some altitude spikes, and resulting vertical offsets, were identified in survey H13138. The SBET's related to the problematic survey lines were investigated and cleaned by interpolating over apparent altitude anomalies using Pydro's POSPac Automated QC tool. For SBET's that were edited further using this method, new SBET and RMS files were exported and applied to the bathymetry data in CARIS to help resolve the offsets. All offsets identified met the specified vertical uncertainty requirements.</ns2:discussion><ns2:title>Altitude Spikes and Vertical Offsets</ns2:title><ns2:images><ns2:link>SupportFiles\DN210_DN215 Vert Offset Subset.jpg</ns2:link><ns2:caption>DN210 &amp; DN 215: Vertical offset between survey lines </ns2:caption></ns2:images><ns2:images><ns2:link>SupportFiles\DN215_DN218 Vert Offset Subset.jpg</ns2:link><ns2:caption>DN215 &amp; DN 218: Vertical offset between survey lines </ns2:caption></ns2:images><ns2:images><ns2:link>SupportFiles\DN216 Vert Offset Subset.jpg</ns2:link><ns2:caption>DN216: Vertical offset between survey lines </ns2:caption></ns2:images><ns2:comments/></ns2:issue><ns2:comments/></ns1:additionalIssues></ns1:verticalAndHorizontalControl><ns1:areaSurveyed><ns1:surveyCoverage><ns2:coverageRequirement><ns2:waterDepth>All waters in survey area</ns2:waterDepth><ns2:requiredCoverage>Object Detection Coverage (refer to HSSD Section 5.2.2.2)</ns2:requiredCoverage></ns2:coverageRequirement><ns2:results deviation="true"><ns2:discussion>Survey coverage was in accordance with the requirements listed above and in the HSSD with some exceptions.  The following are examples of areas that do not meet the coverage requirement.

Many holidays within H13138 were caused by surveying around bridge supports, construction, and moored vessels.  There are also gaps in coverage due to set line spacing methods used within the safety zone where vessels were moored to pilings and buoys.  Holidays were also caused by acoustic shadows and by insufficient coverage overlap.  These holidays were investigated and do not appear to contain navigationally significant features. 

Within the SSS coverage holidays primarily occur to the south of the Tappan Zee Bridge within the safety zone, similar to the gaps in multibeam coverage (Figure 3). Many vessels were moored within this area and there were shifting barges with the ongoing bridge construction. A few smaller SSS holidays are present along the western shoreline due to insufficient overlap. Navigationally significant features do not appear to be within these small gaps in coverage.</ns2:discussion><ns2:images><ns2:link>SupportFiles\SSS Holidays 1.jpg</ns2:link><ns2:caption>Holidays within SSS coverage where moored and shifting vessels were avoided</ns2:caption></ns2:images></ns2:results><ns2:comments/></ns1:surveyCoverage><ns1:surveyPurpose><ns2:discussion>The Hudson River Pilots Association is requesting updated survey data in the Hudson River. Ship traffic to the facilities in Albany and along this section of the Hudson River is steadily increasing and the maximum draft of the vessels calling on the port is getting deeper. Existing chart data outside the federal channels in this area dates from prior to 1939. The pilots feel more recent survey data is warranted in this area, especially given the heavy storm activity that has occurred in the past several years, and the increased shipping traffic carrying hazardous cargoes, such as crude oil.</ns2:discussion><ns2:comments/></ns1:surveyPurpose><ns1:surveyStatistics><ns2:totalSurveyStats><ns2:SNM>5.39</ns2:SNM><ns2:maritimeBoundaryPoints>0</ns2:maritimeBoundaryPoints><ns2:diveOps>0</ns2:diveOps><ns2:bottomSamples>7</ns2:bottomSamples><ns2:DP>0</ns2:DP></ns2:totalSurveyStats><ns2:surveyDates>2018-07-26</ns2:surveyDates><ns2:surveyDates>2018-07-27</ns2:surveyDates><ns2:surveyDates>2018-07-28</ns2:surveyDates><ns2:surveyDates>2018-07-29</ns2:surveyDates><ns2:surveyDates>2018-07-30</ns2:surveyDates><ns2:surveyDates>2018-07-31</ns2:surveyDates><ns2:surveyDates>2018-08-01</ns2:surveyDates><ns2:surveyDates>2018-08-02</ns2:surveyDates><ns2:surveyDates>2018-08-03</ns2:surveyDates><ns2:surveyDates>2018-08-04</ns2:surveyDates><ns2:surveyDates>2018-08-05</ns2:surveyDates><ns2:surveyDates>2018-08-06</ns2:surveyDates><ns2:LNM><ns2:totalLNM><ns2:XL_lidar>0</ns2:XL_lidar><ns2:MS_SBES_SSS>0</ns2:MS_SBES_SSS><ns2:MS_MBES>359.34</ns2:MS_MBES><ns2:MS_SSS>90.92</ns2:MS_SSS><ns2:MS_SBES>0</ns2:MS_SBES><ns2:MS_MBES_SSS>0</ns2:MS_MBES_SSS><ns2:MS_SBES_MBES>0</ns2:MS_SBES_MBES><ns2:XL_MBES_SBES>15.52</ns2:XL_MBES_SBES><ns2:percentXLLNM>4.31</ns2:percentXLLNM><ns2:MS_lidar>0</ns2:MS_lidar></ns2:totalLNM><ns2:vesselLNM><ns2:vessel><ns2:statistics><ns2:XL_lidar>0</ns2:XL_lidar><ns2:MS_SBES_SSS>0</ns2:MS_SBES_SSS><ns2:MS_MBES>359.34</ns2:MS_MBES><ns2:MS_SSS>90.92</ns2:MS_SSS><ns2:MS_SBES>0</ns2:MS_SBES><ns2:MS_MBES_SSS>0</ns2:MS_MBES_SSS><ns2:MS_SBES_MBES>0</ns2:MS_SBES_MBES><ns2:XL_MBES_SBES>15.52</ns2:XL_MBES_SBES><ns2:MS_lidar>0</ns2:MS_lidar></ns2:statistics><ns2:hullID>S3007</ns2:hullID></ns2:vessel></ns2:vesselLNM></ns2:LNM><ns2:comments/><ns2:discussion xsi:nil="true"></ns2:discussion></ns1:surveyStatistics><ns1:surveyQuality><ns2:discussion>The Grid QA tool within QC Tools 2 was used to analyze multibeam echosounder (MBES) data density.  The finalized surface meets the HSSD data density requirement (Figure 2).</ns2:discussion><ns2:adequacy>The entire survey is adequate to supersede previous data.</ns2:adequacy><ns2:images><ns2:link>SupportFiles\H13138_50cm_MB_Final.QAv5.density.png</ns2:link><ns2:caption>Pydro derived histogram plot showing HSSD object detection compliance of H13138 MBES data within the 50cm finalized CUBE surface.</ns2:caption></ns2:images><ns2:comments/></ns1:surveyQuality><ns1:coverageGraphic><ns2:coverageGraphicImage><ns2:images><ns2:link>SupportFiles\Coverage_Overview_SSSMBES.png</ns2:link><ns2:caption>Overview of H13138 survey area coverage including MBES and SSS data.</ns2:caption></ns2:images></ns2:coverageGraphicImage></ns1:coverageGraphic><ns1:areaDescription><ns2:comments/><ns2:discussion>This hydrographic survey was acquired in accordance with the requirements defined in the Project Instructions S-B929-NRT5-18. The survey area H13138 extends south from Tarrytown, NY to Alpine, NJ and covers approximately 5.39 square nautical miles (Figure 1).</ns2:discussion><ns2:images><ns2:link>SupportFiles\Survey Limits.jpg</ns2:link><ns2:caption>H13138 survey limits</ns2:caption></ns2:images><ns2:limits><ns2:southEast><ns2:latitude hemisphere="N">40.9501055556</ns2:latitude><ns2:longitude hemisphere="W">73.8994888889</ns2:longitude></ns2:southEast><ns2:northWest><ns2:latitude hemisphere="N">41.0736555556</ns2:latitude><ns2:longitude hemisphere="W">73.9192111111</ns2:longitude></ns2:northWest></ns2:limits></ns1:areaDescription><ns1:surveyLimits><ns2:results deviation="false"><ns2:discussion>Survey limits were acquired in accordance with the requirements in the Project Instructions and the HSSD.</ns2:discussion></ns2:results><ns2:comments/></ns1:surveyLimits></ns1:areaSurveyed><ns1:metadata><ns1:surveyMetadata><ns2:timeZone>UTC</ns2:timeZone><ns2:year>2018</ns2:year><ns2:projectType>Navigable Area</ns2:projectType><ns2:verifier>Pacific Hydrographic Branch</ns2:verifier><ns2:datesOfSurvey><ns2:end>2018-08-06</ns2:end><ns2:start>2018-07-26</ns2:start></ns2:datesOfSurvey><ns2:equipmentTypes><ns2:imageryEquipment>Side Scan Sonar</ns2:imageryEquipment><ns2:soundingEquipment>Multibeam Echo Sounder</ns2:soundingEquipment></ns2:equipmentTypes><ns2:titlesheetRemarks><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:fieldRemarks xsi:nil="true"></ns2:fieldRemarks></ns2:titlesheetRemarks><ns2:acquisition><ns2:units>meters</ns2:units></ns2:acquisition><ns2:horizontalCoordinateSystem zone="18">Universal Transverse Mercator (UTM)</ns2:horizontalCoordinateSystem><ns2:chiefOfParty>LTJG Dylan Kosten</ns2:chiefOfParty><ns2:PIDate>2018-06-12</ns2:PIDate></ns1:surveyMetadata><ns1:assignment>NOAA</ns1:assignment><ns1:registryMetadata><ns2:scale>5000</ns2:scale><ns2:registryInstructions>Survey shoreward to the extent necessary to support charting an updated 12 foot contour.</ns2:registryInstructions><ns2:stateOrTerritory>New York</ns2:stateOrTerritory><ns2:registryNumber>H13138</ns2:registryNumber><ns2:country>United States</ns2:country><ns2:sheetID>1</ns2:sheetID><ns2:sublocality>Tappen Zee Bridge to Yonkers, NY</ns2:sublocality></ns1:registryMetadata><ns1:projectMetadata><ns2:number>S-B929-NRT5-18</ns2:number><ns2:fieldUnit>Navigation Response Team 5</ns2:fieldUnit><ns2:generalLocality>Hudson River</ns2:generalLocality><ns2:name>Hudson River</ns2:name></ns1:projectMetadata></ns1:metadata><ns1:approvalSheet><ns1:signingPersonnel><ns2:approvalDate>2018-12-14</ns2:approvalDate><ns2:approverName>LTJG Dylan Kosten</ns2:approverName><ns2:approverTitle>Chief of Party</ns2:approverTitle></ns1:signingPersonnel><ns1:signingPersonnel><ns2:approvalDate>2018-12-14</ns2:approvalDate><ns2:approverName>PST Michael Bloom</ns2:approverName><ns2:approverTitle>Sheet Manager</ns2:approverTitle></ns1:signingPersonnel><ns1:signingPersonnel><ns2:approvalDate>2018-12-14</ns2:approvalDate><ns2:approverName>PST Eli Smith</ns2:approverName><ns2:approverTitle>Sheet Manager</ns2:approverTitle></ns1:signingPersonnel><ns1:statements><ns1:additionalInfo xsi:nil="true"></ns1:additionalInfo><ns1:adequacyOfSurvey>The survey data meets or exceeds requirements as set forth in the NOS Hydrographic Surveys Specifications and Deliverables, Field Procedures Manual, Letter Instructions, and all HSD Technical Directives. These data are adequate to supersede charted data in their common areas. This survey is complete and no additional work is required with the exception of deficiencies noted in the Descriptive Report.</ns1:adequacyOfSurvey><ns1: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:supervision>As Chief of Party, field operations for this hydrographic survey were conducted under my direct supervision, with frequent personal checks of progress and adequacy. I have reviewed the attached survey data and reports.</ns1:supervision></ns1:statements></ns1:approvalSheet><ns1:resultsAndRecommendations><ns1:chartComparison><ns1:channels><ns2:results investigated="Investigated"><ns2:discussion>Survey depths within special anchorage areas, dredged areas, and the current mooring area for bridge construction crews are equal to or deeper than charted. </ns2:discussion></ns2:results><ns2:comments/></ns1:channels><ns1:bottomSamples><ns2:results investigated="Investigated"><ns2:discussion>Seven bottom samples were acquired for H13138 and are attributed in the FFF.</ns2:discussion><ns2:images><ns2:link>SupportFiles\Bottom_Sample.jpeg</ns2:link><ns2:caption>Collection of a bottom sample on the Hudson River.</ns2:caption></ns2:images></ns2:results><ns2:comments/></ns1:bottomSamples><ns1:shoalAndHazardousFeatures><ns2:results investigated="Investigated"><ns2:discussion>One DToN report was submitted for H13138 on August 15th, 2018, which has since then been applied to the chart.  The feature appeared to be a pipe with gates surrounding it (Figures 25 and 26).</ns2:discussion><ns2:images><ns2:link>SupportFiles\3D View DTON H13138.png</ns2:link><ns2:caption>3D view of DToN.</ns2:caption></ns2:images><ns2:images><ns2:link>SupportFiles\Overview DTON H13138.png</ns2:link><ns2:caption>Location of DToN near Piermont Pier.</ns2:caption></ns2:images></ns2:results><ns2:comments/></ns1:shoalAndHazardousFeatures><ns1:unchartedFeatures><ns2:results investigated="Investigated"><ns2:discussion>Several new features were found and are detailed in the Final Feature File.  One feature of interest (Figure 23) shows several boxes lined up in rows and columns.  These features are not easily identifiable but are believed to be related to fish habitats. Due to their size being under 1m in height, they have not been added to the FFF.  Their locations have been identified in Figure 24.</ns2:discussion><ns2:images><ns2:link>SupportFiles\Fish habitats.JPG</ns2:link><ns2:caption>3D image of box like features found on the seafloor.</ns2:caption></ns2:images><ns2:images><ns2:link>SupportFiles\Seafloor_Boxes_Locations.png</ns2:link><ns2:caption>Location of boxes on the seafloor within the blue circles.</ns2:caption></ns2:images></ns2:results><ns2:comments/></ns1:unchartedFeatures><ns1:maritimeBoundary><ns2:results investigated="None Exist"><ns2:discussion>No Maritime Boundary Points were assigned for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:maritimeBoundary><ns1:charts><ns2:ENC><ns2:discussion>H13138 and US5NY40M generally agree on soundings and contours.  Contours from H13138 are generally closer to shore than those from US5NY40M.  In the figure below, soundings in green are from H13138 and soundings in purple are from US5NY40M.  On the left side of the figure, the blue arrow shows the blue line (H13138, 5.4m contour) is further inshore than the black line (US5NY40M, 5.4m contour) to the right.  The same is true for the 9.1m contour, shown by the green arrow, when comparing the green line (H13138) to the nearby black line (US5NY40M).</ns2:discussion><ns2:images><ns2:link>SupportFiles\US5NY40m_Comparison_2.JPG</ns2:link><ns2:caption>H13138 data compared to US5NY40M data.</ns2:caption></ns2:images><ns2:chart><ns2:scale>40000</ns2:scale><ns2:updateApplicationDate>2018-10-19</ns2:updateApplicationDate><ns2:preliminary>false</ns2:preliminary><ns2:issueDate>2018-10-19</ns2:issueDate><ns2:edition>18</ns2:edition><ns2:name>US5NY40M</ns2:name></ns2:chart><ns2:comments/></ns2:ENC><ns2:ENC><ns2:discussion>H13138 and US5NY42M generally agree on soundings and contours.  Contours from H13138 are generally closer to shore than those from US5NY42M.  In the figure below, soundings in green are from H13138 and soundings in purple are from US5NY42M.  Similar to the above figure, the blue arrow shows the blue line (H13138, 5.4m contour) is further inshore than the black line (US5NY42M, 5.4m contour) to the right.  The same is true for the 9.1m contour, shown by the green arrow, when comparing the green line (H13138) to the nearby black line (US5NY42M).</ns2:discussion><ns2:images><ns2:link>SupportFiles\US5NY42m_Comparison_2.JPG</ns2:link><ns2:caption>H13138 data compared to US5NY42M data.</ns2:caption></ns2:images><ns2:chart><ns2:scale>10000</ns2:scale><ns2:updateApplicationDate>2018-10-19</ns2:updateApplicationDate><ns2:preliminary>false</ns2:preliminary><ns2:issueDate>2018-10-19</ns2:issueDate><ns2:edition>12</ns2:edition><ns2:name>US5NY42M</ns2:name></ns2:chart><ns2:comments/></ns2:ENC><ns2:comments/></ns1:charts><ns1:methods><ns2:discussion>Chart comparisons were made using CARIS sounding and contour layers derived from CUBE surfaces. The contours and soundings were overlaid on the latest ENC and compared for general agreement and to identify areas of significant change.  Another tool used was &quot;Triangle Rule&quot; under the Chart Review tab in QC Tools 2.  The tool highlighted areas of disagreement for further investigation.</ns2:discussion><ns2:comments/></ns1:methods><ns1:chartedFeatures><ns2:results investigated="Investigated"><ns2:discussion>Three charted features with the labels of PA or Rep were investigated.  To the south of Dobbs Ferry is a charted &quot;Obstn PA (17ft rep)&quot; (Figure 19).  This feature does exist within the charted circle, with a depth of 19.7 feet.  North of Piermont pier are two charted features (Figure 20).  The &quot;Obstn rep&quot; feature was not seen in multibeam nor SSS data.  The PA wreck, however, was visible within the SSS data.

Some charted features, like parts of the old Tappan Zee bridge, and an underwater cable near Piermont pier, were not seen in the field or the data.  These features had an investigation requirement to report discrepancies within the DR and to not include them in the FFF.  Some features north of the Tappan Zee bridge were assigned to H13138 but not addressed because they were addressed in the previous years survey, H13092.

Feature scan within QC Tools 2 highlighted an issue with redundant features.  These features were identified as being seasonal buoy types, and therefore both features are retained in the same location.</ns2:discussion><ns2:images><ns2:link>SupportFiles\Charted_Feature_PA.png</ns2:link><ns2:caption>Charted Feature with PA exists.</ns2:caption></ns2:images><ns2:images><ns2:link>SupportFiles\Obstn_rep_WR_PA.png</ns2:link><ns2:caption>Charted Obstn rep (not seen) and charted wreck PA (seen).</ns2:caption></ns2:images><ns2:images><ns2:link>SupportFiles\Bridges.JPG</ns2:link><ns2:caption>Tappan Zee bridge partly demolished, with Governor Mario M. Cuomo bridge to the north.</ns2:caption></ns2:images><ns2:images><ns2:link>SupportFiles\Piermont_Cable.png</ns2:link><ns2:caption>Cable crossing near Piermont Pier not visible within data.</ns2:caption></ns2:images></ns2:results><ns2:comments><ns2:branchComment><ns2:comment>Do not concur with the statement that no obstruction is visible near the charted &quot;Obstn rep&quot; symbol near Piedmont Pier. An obstruction item is visible in the side scan record near the NW edge of the RNC symbol. Recommend charting an obstruction with depth reported, not confirmed per the Final Feature File.  See Figure 22a.</ns2:comment><ns2:images><ns2:link>file:///M:/SB929NRT518/Surveys/H13138/Office_Processing/Review_office/Working/Obst_PA_sidescan.PNG</ns2:link><ns2:caption>Figure 22a. Obrtuction near Peidmont Peir.</ns2:caption></ns2:images></ns2:branchComment></ns2:comments></ns1:chartedFeatures></ns1:chartComparison><ns1:additionalResults><ns1:shoreline><ns2:results investigated="Investigated"><ns2:discussion>Shoreline investigation was conducted for this entire survey area. At low tide, the vessel operator transited slowly along the shoreline while the hydrographer took photographs and notes of visible shoreline features.  These notes and photographs were compared to the assigned features found in the Composite Source File.  Additionally, efforts were made to confirm (photograph) any assigned features inshore of the NALL. These results were compiled to the Final Feature File submitted with this survey.  

Feature Scan within QC Tools was used to verify features had correct attributions. The Feature Scan tool identified a buoy in a redundant position, which was identified as a seasonally changing buoy type, and a foul area without a defined Water Level Effect, for which the attribution meets specfications.</ns2:discussion></ns2:results><ns2:comments/></ns1:shoreline><ns1:constructionOrDredging><ns2:results investigated="Exist - Not Investigated"><ns2:discussion>Present and/or planned construction or dredging exists within the survey limits, but was not investigated.</ns2:discussion></ns2:results><ns2:comments/></ns1:constructionOrDredging><ns1:overheadFeatures><ns2:results investigated="Investigated"><ns2:discussion>The Tappan Zee Bridge was in the process of deconstruction and the Governor Mario M. Cuomo Bridge was fully operational during our survey.  These features have been attributed in the FFF.</ns2:discussion><ns2:images><ns2:link>SupportFiles\Bridges.JPG</ns2:link><ns2:caption>Tappan Zee and Governor Mario M. Cuomo Bridge.</ns2:caption></ns2:images></ns2:results><ns2:comments/></ns1:overheadFeatures><ns1:submarineFeatures><ns2:results investigated="Investigated"><ns2:discussion>Cables and/or pipes were found in numerous locations within H13138 and are attributed in the FFF.  One charted cable area has no visible cables within its charted area, however, a cable was found in the multibeam running just north of it (Figure 29).  Further north a charted cable crossing near Piermont Pier had no visible cable within the multibeam data.</ns2:discussion><ns2:images><ns2:link>SupportFiles\Cable_Area_2.png</ns2:link><ns2:caption>Charted Cable area and found cable north of area.</ns2:caption></ns2:images><ns2:images><ns2:link>SupportFiles\Cable_Crossing.png</ns2:link><ns2:caption>Charted cable crossing near Piermont Pier.</ns2:caption></ns2:images></ns2:results><ns2:comments><ns2:branchComment><ns2:comment>Current editions of the chart have updated the cable area to include the area covered by the cable found previously to the north of the charted area as shown in Figure 29. See new Figure 30a.</ns2:comment><ns2:images><ns2:link>file:///M:/SB929NRT518/Surveys/H13138/Office_Processing/Review_office/Working/Cable_crossing.PNG</ns2:link><ns2:caption>Figure 30a: Updated charted cable crossing.</ns2:caption></ns2:images></ns2:branchComment></ns2:comments></ns1:submarineFeatures><ns1:abnormalSeafloorEnviroCond><ns2:results investigated="None Exist"><ns2:discussion>No abnormal seafloor and/or environmental conditions exist for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:abnormalSeafloorEnviroCond><ns1: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:ATONS><ns2:results investigated="Investigated"><ns2:discussion>All ATONs were found to be on station and serving their intended purpose.  One private buoy was located 130 meters further south than charted but still serving it's intended purpose.</ns2:discussion></ns2:results><ns2:comments/></ns1:ATONS><ns1:platforms><ns2:results investigated="None Exist"><ns2:discussion>No platforms exist for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:platforms><ns1:otherResults><ns2:comments/></ns1:otherResults><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:insetRecommendation><ns2:results recommended="false"><ns2:discussion>No new insets are recommended for this area.</ns2:discussion></ns2:results><ns2:comments/></ns1:insetRecommendation><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:additionalResults></ns1:resultsAndRecommendations><ns1:dataAcquisitionAndProcessing><ns1:qualityControl><ns1:factorsAffectingSoundings><ns2:results deviation="true"><ns2:issue><ns2:discussion>Noted during acquisition and in post processing, several lines of data have noise from side lobes.  The surface has been cleaned of side lobe noise where CUBE failed to accurately represent the riverbed.</ns2:discussion><ns2:title>Nadir Side Lobe Noise</ns2:title><ns2:images><ns2:link>SupportFiles\Nadir Noise.JPG</ns2:link><ns2:caption>Image showing noise found on H13138</ns2:caption></ns2:images><ns2:comments/></ns2:issue><ns2:issue><ns2:discussion>In a few areas within the SSS data set, schools of fish were obscuring the riverbed imagery. In all of these cases, the overlapping line could be evaluated to ensure that no navigationally significant features were in these areas.</ns2:discussion><ns2:title>Fish Obscuring SSS</ns2:title><ns2:images><ns2:link>SupportFiles\SS FISHIES.png</ns2:link><ns2:caption>Fish obscuring SSS data.</ns2:caption></ns2:images><ns2:comments/></ns2:issue></ns2:results><ns2:comments/></ns1:factorsAffectingSoundings><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:junctions><ns2:junction><ns2:survey><ns2:scale>5000</ns2:scale><ns2:fieldUnit>Navigation Response Team 5</ns2:fieldUnit><ns2:year>2017</ns2:year><ns2:relativeLocation>N</ns2:relativeLocation><ns2:registryNumber>H13092</ns2:registryNumber></ns2:survey><ns2:discussion>Overlap between H13138 and H13092 averaged about 130 meters in length.  Using the Compare Grids tool within Pydro, the differences in the areas of overlap were analyzed and 99.5% of nodes were found to meet HSSD standards.</ns2:discussion><ns2:images><ns2:link>SupportFiles\Overlap_H13138_H13092_2.png</ns2:link><ns2:caption>Overlap between H13138 (blue) and H13092 (red)</ns2:caption></ns2:images><ns2:images><ns2:link>SupportFiles\H13138_50cm_MB_Final-H13092_MB_50cm_MLLW_Final_fracAllowErr_Freq.png</ns2:link><ns2:caption>Pydro generated graph comparing H13138 data to H13092.</ns2:caption></ns2:images><ns2:comments/></ns2:junction><ns2:junction><ns2:survey><ns2:scale>5000</ns2:scale><ns2:fieldUnit>Navigation Response Team 5</ns2:fieldUnit><ns2:year>2012</ns2:year><ns2:relativeLocation>S</ns2:relativeLocation><ns2:registryNumber>F00598</ns2:registryNumber></ns2:survey><ns2:discussion>Overlap between H13138 and F00598 averaged about 120 meters in length.  Using the Compare Grids tool within Pydro, the differences in the areas of overlap were analyzed and 99% of nodes were found to meet HSSD standards.</ns2:discussion><ns2:images><ns2:link>SupportFiles\Overlap_H13138_F00598_2.png</ns2:link><ns2:caption>Overlap between H13138 (blue) and F00598 (red).</ns2:caption></ns2:images><ns2:images><ns2:link>SupportFiles\H13138_50cm_MB_Final-F00598_MB_2m_MLLW_Combined_fracAllowErr_Freq.png</ns2:link><ns2:caption>Pydro generated graph comparing H13138 data to F00598.</ns2:caption></ns2:images><ns2:comments><ns2:branchComment><ns2:comment> An area of sandwaves exists where H13138 junctions with F00598. Differences between surveys exceed TVU in this area but is expected given the know changeability. The remainder of the junction area shows good agreement.  See Figure 11a</ns2:comment><ns2:images><ns2:link>file:///M:/SB929NRT518/Surveys/H13138/Office_Processing/Review_office/Working/JunctionF00598_Sandwaves.PNG</ns2:link><ns2:caption>Figure 11a: Area of Sandwaves between H13138 and F00598. </ns2:caption></ns2:images></ns2:branchComment></ns2:comments></ns2:junction><ns2:discussion>H13138 junctions with two prior surveys, H13092 and F00598.  H13092 was acquired the year previously and junctions with the northern end of the sheet. F00598 was acquired in 2012 and junctions with the southern end of the sheet.  </ns2:discussion><ns2:comments/></ns1:junctions><ns1:soundSpeedMethods><ns1:castFrequency>At least once every 4 hours</ns1:castFrequency><ns1:discussion>SVP casts were taken at least once every four hours in the deepest water nearest to the survey area being worked on. The SVP casts were applied to the MBES lines in CARIS using the &quot;nearest in distance within time of 4 hours&quot; method.</ns1:discussion><ns1:comments/></ns1:soundSpeedMethods><ns1:equipmentEffectiveness><ns2:results deviation="false"><ns2:issue><ns2:discussion>There were no conditions or deficiencies that affected equipment operational effectiveness.</ns2:discussion><ns2:title>None Exist</ns2:title><ns2:comments/></ns2:issue></ns2:results><ns2:comments/></ns1:equipmentEffectiveness><ns1:coverageEquipmentAndMethods><ns2:results deviation="true"><ns2:discussion>All equipment and survey methods were used as detailed in the DAPR.</ns2:discussion></ns2:results><ns2:comments/></ns1:coverageEquipmentAndMethods><ns1:additionalQualityControl><ns2:comments/></ns1:additionalQualityControl><ns1:crosslines><ns2:discussion>A 50cm CUBE surface was created using only mainscheme lines, and a second 50cm CUBE surface was created using only crosslines.  These surfaces were then input into the Pydro Tool &quot;Compare Grids&quot;.  The comparison passed HSSD specifications (Figure 6).</ns2:discussion><ns2:images><ns2:link>SupportFiles\H13138_MS_0.5m-H13138_XLs_0.5m_update_fracAllowErr_Freq.png</ns2:link><ns2:caption>Pydro generated graph showing comparison between mainscheme and crosslines.</ns2:caption></ns2:images><ns2:comments/></ns1:crosslines><ns1:uncertainty><ns2:values><ns2:tideUncertainty><ns2:measured units="meters">0.096</ns2:measured><ns2:zoning units="meters">0</ns2:zoning><ns2:tideMethod>ERS via VDATUM</ns2:tideMethod></ns2:tideUncertainty><ns2:soundSpeedUncertainty><ns2:measuredCTD units="meters/second">2</ns2:measuredCTD><ns2:surface units="meters/second">0.5</ns2:surface><ns2:hullID>S3007</ns2:hullID><ns2:measuredMVP units="meters/second">0</ns2:measuredMVP></ns2:soundSpeedUncertainty></ns2:values><ns2:discussion>Total Propagated Uncertainty (TPU) values for H13138 were derived from a combination of fixed values for equipment and vessel characteristics, as well as field assigned values for sound speed uncertainties. The uncertainty for the VDatum model was provided to the field units in the Project Instructions, however, the value provided was different to the value within the text file that is generated when the VDatum is created.  Correspondence with the Project Manager lead to the decision to use the value in the text file as it would be more accurate. A visual inspection of the Uncertainty layer revealed the areas of higher uncertainty occur in the outer beams, and a visual inspection of the Density layer revealed the areas of lowest density are in the deepest areas of the survey.

In addition to the usual a priori estimates of uncertainty, some real time and post processed uncertainty sources were also incorporated into the depth estimates of the survey. Real-time uncertainties from the Kongsberg MBES sonars were incorporated and applied during post processing. Uncertainties associated with vessel roll, pitch, gyro, navigation, and heave were applied during post-processing. All of the aforementioned uncertainties were applied in CARIS. As stated, H13138 is an ellipsoidally referenced survey (ERS) and the tidal component was accomplished with a separation model.</ns2:discussion><ns2:images><ns2:link>SupportFiles\H13138_50cm_MB_Final.QAv5.tvu_qc.png</ns2:link><ns2:caption>Pydro derived histogram plot showing HSSD uncertainty standards compliance of H13138 50cm finalized surface.</ns2:caption></ns2:images><ns2:comments/></ns1:uncertainty></ns1:qualityControl><ns1:dataProcessing><ns1:surfaces><ns1:discussion>Flier Finder was used to analyze the multibeam surfaces for data cleanliness, and all fliers have been addressed  The VALSOU check reported several discrepancies between the surface and the features in the FFF.  Most features were able to be corrected and become compliant, but some features despite repeated efforts continue to get flagged after edits. These features that fail the VALSOU check are included in the submitted FFF.
</ns1:discussion><ns1:comments/><ns1:surface><ns2:surfaceParameter>NOAA_0.5m</ns2:surfaceParameter><ns2:surfaceName>H13138_MB_50cm_MLLW</ns2:surfaceName><ns2:depthRange><ns2:max units="meters">19.5</ns2:max><ns2:min units="meters">0.9</ns2:min></ns2:depthRange><ns2:surfaceType>CARIS Raster Surface (CUBE)</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:surfaceName>H13138_MB_50cm_MLLW_Final</ns2:surfaceName><ns2:depthRange><ns2:max units="meters">19.5</ns2:max><ns2:min units="meters">0.7</ns2:min></ns2:depthRange><ns2:surfaceType>CARIS Raster Surface (CUBE)</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:surfaceName>H13138_SSSAB_50cm_900kHz_1of2</ns2:surfaceName><ns2:depthRange><ns2:max xsi:nil="true"/><ns2:min xsi:nil="true"/></ns2:depthRange><ns2:surfaceType>SSS Mosaic</ns2:surfaceType><ns2:resolution units="meters">0.5</ns2:resolution><ns2:purpose>200% SSS</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceParameter>N/A</ns2:surfaceParameter><ns2:surfaceName>H13138_SSSAB_50cm_900kHz_2of2</ns2:surfaceName><ns2:depthRange><ns2:max xsi:nil="true"/><ns2:min xsi:nil="true"/></ns2:depthRange><ns2:surfaceType>SSS Mosaic</ns2:surfaceType><ns2:resolution units="meters">0.5</ns2:resolution><ns2:purpose>200% SSS</ns2:purpose></ns1:surface></ns1:surfaces><ns1:additionalDataProcessing><ns2:comments/></ns1:additionalDataProcessing><ns1:drSoftware><ns1:imagerySoftware deviation="false"><ns1:manufacturer xsi:nil="true"></ns1:manufacturer><ns1:version xsi:nil="true"></ns1:version><ns1:name xsi:nil="true"></ns1:name></ns1:imagerySoftware><ns1:bathySoftware deviation="false"><ns1:manufacturer xsi:nil="true"></ns1:manufacturer><ns1:version xsi:nil="true"></ns1:version><ns1:name xsi:nil="true"></ns1:name></ns1:bathySoftware><ns1:featureObjectCatalog>NOAA Profile V_5_8</ns1:featureObjectCatalog><ns1:discussion xsi:nil="true"></ns1:discussion><ns1:comments/></ns1:drSoftware></ns1:dataProcessing><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:additionalIssues><ns2:comments/></ns1:additionalIssues><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:echoSoundingCorrections><ns1:backscatter><ns2:results acquired="true"><ns2:discussion>Raw Backscatter was logged in the .all file and will be sent to the Processing Branch.</ns2:discussion></ns2:results><ns2:comments/></ns1:backscatter><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:equipment><ns1:majorSystem><ns2:type>MBES</ns2:type><ns2:model>EM 2040C</ns2:model><ns2:manufacturer>Kongsberg Maritime</ns2:manufacturer></ns1:majorSystem><ns1:majorSystem><ns2:type>SSS</ns2:type><ns2:model>4125</ns2:model><ns2:manufacturer>EdgeTech</ns2:manufacturer></ns1:majorSystem><ns1:majorSystem><ns2:type>Positioning and Attitude System</ns2:type><ns2:model>POS MV 320 v5</ns2:model><ns2:manufacturer>Applanix</ns2:manufacturer></ns1:majorSystem><ns1:majorSystem><ns2:type>Sound Speed System</ns2:type><ns2:model>MicroX SVS</ns2:model><ns2:manufacturer>AML Oceanographic</ns2:manufacturer></ns1:majorSystem><ns1:majorSystem><ns2:type>Conductivity, Temperature, and Depth Sensor</ns2:type><ns2:model>CastAway-CTD</ns2:model><ns2:manufacturer>YSI</ns2:manufacturer></ns1:majorSystem><ns1:discussion xsi:nil="true"></ns1:discussion><ns1:comments/></ns1:equipment><ns1:comments/><ns1:vessels><ns1:images><ns2:link>SupportFiles\S3007 Cornetta's.jpg</ns2:link><ns2:caption>S3007 moored at Cornetta's Marina in Piermont, NY.</ns2:caption></ns1:images><ns1:vessel><ns2:LOA units="meters">10.38</ns2:LOA><ns2:draft units="meters">0.6</ns2:draft><ns2:hullID>S3007</ns2:hullID></ns1:vessel><ns1:discussion xsi:nil="true"></ns1:discussion><ns1:comments/></ns1:vessels></ns1:equipmentAndVessels></ns1:dataAcquisitionAndProcessing></ns1:descriptiveReport>