<?xml version="1.0" encoding="UTF-8"?><ns1:descriptiveReport xmlns:ns1="http://svn.pydro.noaa.gov/2016/01/DescriptiveReport" xmlns:ns2="http://svn.pydro.noaa.gov/2016/01/AllGlobalTypes" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://svn.pydro.noaa.gov/2016/01/DescriptiveReport http://svn.pydro.noaa.gov/2016/01/DR.xsd"><ns1:metadata><ns1:projectMetadata><ns2:number>OPR-B396-NRT5BH2-16</ns2:number><ns2:name>Hudson River</ns2:name><ns2:generalLocality>Hudson River</ns2:generalLocality><ns2:fieldUnit>Navigation Response Team 5 and Bay Hydro II</ns2:fieldUnit></ns1:projectMetadata><ns1:registryMetadata><ns2:registryNumber>H12874</ns2:registryNumber><ns2:sheetID>3</ns2:sheetID><ns2:registryInstructions xsi:nil="true"></ns2:registryInstructions><ns2:sublocality>Danskammer Point to Kingston</ns2:sublocality><ns2:stateOrTerritory>New York</ns2:stateOrTerritory><ns2:country>United States</ns2:country><ns2:scale>5000</ns2:scale></ns1:registryMetadata><ns1:surveyMetadata><ns2:year>2016</ns2:year><ns2:chiefOfParty>LT Andrew R. Clos</ns2:chiefOfParty><ns2:projectType>Navigable Area</ns2:projectType><ns2:PIDate>2016-04-13</ns2:PIDate><ns2:datesOfSurvey><ns2:start>2016-08-10</ns2:start><ns2:end>2016-09-29</ns2:end></ns2:datesOfSurvey><ns2:equipmentTypes><ns2:soundingEquipment>Multibeam Echo Sounder</ns2:soundingEquipment></ns2:equipmentTypes><ns2:acquisition><ns2:units>meters</ns2:units></ns2:acquisition><ns2:horizontalCoordinateSystem zone="18N">Universal Transverse Mercator (UTM)</ns2:horizontalCoordinateSystem><ns2:timeZone>UTC</ns2:timeZone><ns2:verifier>Pacific Hydrographic Branch</ns2:verifier><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></ns1:surveyMetadata><ns1:assignment>NOAA</ns1:assignment></ns1:metadata><ns1:areaSurveyed><ns1:areaDescription><ns2:discussion>This survey was conducted at the request of the Hudson River Pilots Association to update nautical charts on the Hudson River.  Acquisition for survey H12874 began in Kingston NY, and continued about 21 nautical miles south to Danskammer Point.</ns2:discussion><ns2:limits><ns2:northWest><ns2:latitude hemisphere="N">41.9312</ns2:latitude><ns2:longitude hemisphere="W">73.9625</ns2:longitude></ns2:northWest><ns2:southEast><ns2:latitude hemisphere="N">41.5736</ns2:latitude><ns2:longitude hemisphere="W">73.9503</ns2:longitude></ns2:southEast></ns2:limits><ns2:images><ns2:caption>Northern extent of surveyed area.</ns2:caption><ns2:link>SupportFiles\AreaSurveyed_North.bmp</ns2:link></ns2:images><ns2:images><ns2:caption>Southern extent of surveyed area.</ns2:caption><ns2:link>SupportFiles\AreaSurveyed_South.bmp</ns2:link></ns2:images><ns2:comments/></ns1:areaDescription><ns1:surveyLimits><ns2:results deviation="true"><ns2:discussion>Certain areas were surveyed past the sheet limits in preparation for future re-charting of the area at 1:12000 scale.  The assigned sheet limits, set back from the shoreline by 2mm at 1:40000 scale, were exceeded to prevent the need to return to the extreme near shore area when the region is re-charted at a larger scale. </ns2:discussion><ns2:images><ns2:caption>Blue dashed line indicates the nearshore survey limited based on 1:40000 scale raster chart.  </ns2:caption><ns2:link>SupportFiles\SurveyLimitsExceeded.bmp</ns2:link></ns2:images></ns2:results><ns2:comments/></ns1:surveyLimits><ns1:surveyPurpose><ns2:discussion>The Hudson River Pilots Association is requesting updated survey data in the Hudson River from
the Tappan See Bridge up to Albany, NY. 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 and in many cases pre-1900 surveys. The federal channel in this area is only
400-ft wide and the size of ships is exceeding 600-ft in length, which necessitates maneuvering
outside of the federal channel. 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:surveyQuality><ns2:adequacy>The entire survey is adequate to supersede previous data.</ns2:adequacy><ns2:discussion xsi:nil="true"></ns2:discussion><ns2:comments/></ns1:surveyQuality><ns1:surveyCoverage><ns2:coverageRequirement><ns2:waterDepth>All waters in survey area</ns2:waterDepth><ns2:requiredCoverage>Object Detection Coverage accomplished using either: A) Object detection MBES, or B) 200% SSS coverage with concurrent set line spacing SBES or MBES. Refer to HSSD Section 5.2.2.1</ns2:requiredCoverage></ns2:coverageRequirement><ns2:results deviation="true"><ns2:discussion>In some locations, seasonal marinas with floating docks were present which prevented the survey acquisition from occurring up to the 12 foot nearshore limit.  Efforts were made to collect as much data as possible in these areas, but ultimately there are a few small areas with incomplete coverage.</ns2:discussion><ns2:images><ns2:caption>Incomplete coverage to the 12 foot contour due to the presence of floating docks and moored vessels.</ns2:caption><ns2:link>SupportFiles\CantReach12foot.bmp</ns2:link></ns2:images><ns2:images><ns2:caption>Example of seasonal dock with moored vessels found within the survey area.</ns2:caption><ns2:link>SupportFiles\IMG_20160907_155806820.jpg</ns2:link></ns2:images></ns2:results><ns2:comments/></ns1:surveyCoverage><ns1:coverageGraphic><ns2:caption>MBES coverage shown with raster chart 12347 in the background.</ns2:caption><ns2:link>SupportFiles\SurveyOverview.bmp</ns2:link></ns1:coverageGraphic><ns1:surveyStatistics><ns2:LNM><ns2:vesselLNM><ns2:vessel><ns2:hullID>S3002</ns2:hullID><ns2:statistics><ns2:MS_SBES>0</ns2:MS_SBES><ns2:MS_MBES>666.7</ns2:MS_MBES><ns2:MS_lidar>0</ns2:MS_lidar><ns2:MS_SSS>0</ns2:MS_SSS><ns2:MS_SBES_MBES>0</ns2:MS_SBES_MBES><ns2:MS_MBES_SSS>0</ns2:MS_MBES_SSS><ns2:MS_SBES_SSS>0</ns2:MS_SBES_SSS><ns2:XL_MBES_SBES>50.7</ns2:XL_MBES_SBES><ns2:XL_lidar>0</ns2:XL_lidar></ns2:statistics></ns2:vessel></ns2:vesselLNM><ns2:totalLNM><ns2:MS_SBES>0</ns2:MS_SBES><ns2:MS_MBES>666.7</ns2:MS_MBES><ns2:MS_lidar>0</ns2:MS_lidar><ns2:MS_SSS>0</ns2:MS_SSS><ns2:MS_SBES_MBES>0</ns2:MS_SBES_MBES><ns2:MS_MBES_SSS>0</ns2:MS_MBES_SSS><ns2:MS_SBES_SSS>0</ns2:MS_SBES_SSS><ns2:XL_MBES_SBES>50.7</ns2:XL_MBES_SBES><ns2:XL_lidar>0</ns2:XL_lidar><ns2:percentXLLNM>7.6</ns2:percentXLLNM></ns2:totalLNM></ns2:LNM><ns2:totalSurveyStats><ns2:bottomSamples>0</ns2:bottomSamples><ns2:maritimeBoundaryPoints>0</ns2:maritimeBoundaryPoints><ns2:DP>0</ns2:DP><ns2:diveOps>0</ns2:diveOps><ns2:SNM>9.88</ns2:SNM></ns2:totalSurveyStats><ns2:surveyDates>2016-08-10</ns2:surveyDates><ns2:surveyDates>2016-08-22</ns2:surveyDates><ns2:surveyDates>2016-08-23</ns2:surveyDates><ns2:surveyDates>2016-08-24</ns2:surveyDates><ns2:surveyDates>2016-08-25</ns2:surveyDates><ns2:surveyDates>2016-08-30</ns2:surveyDates><ns2:surveyDates>2016-08-31</ns2:surveyDates><ns2:surveyDates>2016-09-01</ns2:surveyDates><ns2:surveyDates>2016-09-02</ns2:surveyDates><ns2:surveyDates>2016-09-06</ns2:surveyDates><ns2:surveyDates>2016-09-07</ns2:surveyDates><ns2:surveyDates>2016-09-08</ns2:surveyDates><ns2:surveyDates>2016-09-13</ns2:surveyDates><ns2:surveyDates>2016-09-14</ns2:surveyDates><ns2:surveyDates>2016-09-15</ns2:surveyDates><ns2:surveyDates>2016-09-16</ns2:surveyDates><ns2:surveyDates>2016-09-19</ns2:surveyDates><ns2:surveyDates>2016-09-20</ns2:surveyDates><ns2:surveyDates>2016-09-21</ns2:surveyDates><ns2:surveyDates>2016-09-27</ns2:surveyDates><ns2:surveyDates>2016-09-28</ns2:surveyDates><ns2:surveyDates>2016-09-29</ns2:surveyDates><ns2:discussion xsi:nil="true"></ns2:discussion><ns2:comments><ns2:branchComment concurrence="Comment Only"><ns2:comment>One (1) DP was acquired as part of H12874.</ns2:comment></ns2:branchComment></ns2:comments></ns1:surveyStatistics></ns1:areaSurveyed><ns1:dataAcquisitionAndProcessing><ns1:equipmentAndVessels><ns1:discussion>Refer to the Data Acquisition and Processing Report (DAPR) for a complete description of data acquisition and processing systems, survey vessels, quality control procedures and data processing methods.  Additional information to supplement sounding and survey data, and any deviations from the DAPR are discussed in the following sections.</ns1:discussion><ns1:vessels><ns1:vessel><ns2:hullID>S3002</ns2:hullID><ns2:LOA units="feet">33</ns2:LOA><ns2:draft units="feet">2.5</ns2:draft></ns1:vessel><ns1:images><ns2:caption>S3002</ns2:caption><ns2:link>SupportFiles\nrt_underway.jpg</ns2:link></ns1:images><ns1:discussion xsi:nil="true"></ns1:discussion><ns1:comments/></ns1:vessels><ns1:equipment><ns1:majorSystem><ns2:manufacturer>Kongsberg</ns2:manufacturer><ns2:model>EM3002</ns2:model><ns2:type>MBES</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>Applanix</ns2:manufacturer><ns2:model>POS M/V V5</ns2:model><ns2:type>Positioning and Attitude System</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>Trimble</ns2:manufacturer><ns2:model>SPS361</ns2:model><ns2:type>Positioning System</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>Seabird</ns2:manufacturer><ns2:model>SBE 19+</ns2:model><ns2:type>Conductivity, Temperature, and Depth Sensor</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>AML</ns2:manufacturer><ns2:model>Micro X</ns2:model><ns2:type>Sound Speed System</ns2:type></ns1:majorSystem><ns1:discussion xsi:nil="true"></ns1:discussion><ns1:comments/></ns1:equipment><ns1:comments/></ns1:equipmentAndVessels><ns1:qualityControl><ns1:crosslines><ns2:discussion>S3002 acquired 666.7 linear nautical miles of mainscheme bathymetry and 50.7 linear nautical miles of MBES cross lines, which equates to 7.6% of mainscheme MBES data.  Crosslines were compared to mainscheme using a difference surface, created in CARIS BathyDataBase. By comparing with the difference surface method, every instance of overlap was evaluated. The mean was 0.011 meters and the standard deviation was 0.091 meters.

Additional comparison was made using CARIS Subset Editor and a 50 centimeter BASE surface to visually identify areas of mainscheme/crossline disagreement.  Areas of largest disagreement near the outer beams of the MBES swath.  Additionally, a slight vertical offset was detected during crossline comparison.  See Section C.3 for additional discussion of this issue.</ns2:discussion><ns2:comments/></ns1:crosslines><ns1:uncertainty><ns2:values><ns2:tideUncertainty><ns2:measured units="meters">0</ns2:measured><ns2:zoning units="centimeters">5.385</ns2:zoning><ns2:tideMethod>ERS via VDATUM</ns2:tideMethod></ns2:tideUncertainty><ns2:soundSpeedUncertainty><ns2:hullID>S3002</ns2:hullID><ns2:measuredCTD units="meters/second">2.0</ns2:measuredCTD><ns2:measuredMVP units="meters/second">0</ns2:measuredMVP><ns2:surface units="meters/second">0.5</ns2:surface></ns2:soundSpeedUncertainty></ns2:values><ns2:discussion>Density and Uncertainty statistics were calculated using Pydro Explorer's CSAR QA tools.

For H12874_MB_50cm_HRD_Final, H12874_MB_1m_HRD_Final, and H12874_MB_2m_HRD_Final, greater than  99.5% of all nodes meet or exceed density and Order 1a uncertainty requirements.  

An accuracy layer named &quot;Order_1a&quot; was created for each finalized BASE surface using the formula: Uncertainty/((0.5^2 +((Depth*0.013)^2))^0.5).  This formula produces a ratio of calculated uncertainty to allowable uncertainty.  Values greater than 1 indicate nodes that surpass NOS Order 1a uncertainty limits.  The generated layer is used for visual identification of areas with unusually high uncertainty.   The majority of nodes that are near or beyond the allowable uncertainty threshold are in areas that are: extremely steep, rocky, only covered by the outer extents of the multibeam swath, or effected by a vertical offset between different survey days.  See section C.3 for further discussion of the vertical offset.

Areas of lowest density were found near the extreme edges of the sheet or where water depths ranged between 15 and 22 meters.  During evening processing, density layers were analyzed in CARIS HIPS and additional bathymetry was later acquired in areas of low density.     </ns2:discussion><ns2:images><ns2:caption>50 centimeter CSAR statistics.</ns2:caption><ns2:link>SupportFiles\H12874_MB_50cm_HRD_Final_UncertaintyDensity.png</ns2:link></ns2:images><ns2:images><ns2:caption>1 meter CSAR statistics.</ns2:caption><ns2:link>SupportFiles\H12874_MB_1m_HRD_Final_UncertaintyDensity.png</ns2:link></ns2:images><ns2:images><ns2:caption>2 meter CSAR statistics.</ns2:caption><ns2:link>SupportFiles\H12874_MB_2m_HRD_Final_UncertaintyDensity.png</ns2:link></ns2:images><ns2:comments><ns2:branchComment concurrence="Comment Only"><ns2:comment>'H12874_MB_2m_Final' was not submitted as part of H12874.  The surfaces submitted as part of H12874 are as shown in section B.5.2, Table 8.  The finalized grid 'H12874_MB_4m_Final' was found to meet density and uncertainty standards (as defined in the HSSDM section 5.2.2.2 and 5.1.3) during office review.</ns2:comment></ns2:branchComment></ns2:comments></ns1:uncertainty><ns1:junctions><ns2:discussion>The northern portion of H12874 junctioned with H12873.  H12873 was collected as part of the same project a few weeks prior to H12874.  Survey vessel S3002 collected all of the data within H12874, while the Bay Hydrographer II collected all data within the junction region of H12873.

Survey H12874 generally junctioned well with H12873.  A difference surface was created using the 50 centimeter finalized BASE surfaces of each survey and then statistics were computed in CARIS HIPS.  The mean difference was 0.13 meters and the standard deviation was 0.058 meters.  The mean difference of 0.13 meters is attributed to a known vertical offset between S3002 and Bay Hydro II, that was discovered and partially resolved earlier in the project (Sheet 1, H12872).   </ns2:discussion><ns2:images><ns2:caption>H12874 junction statistics with H12873.</ns2:caption><ns2:link>SupportFiles\H12873_Junction_stats.png</ns2:link></ns2:images><ns2:comments/></ns1:junctions><ns1:sonarQCChecks><ns2:results deviation="false"><ns2:discussion>Sonar system quality control checks were conducted as detailed in the quality control section of the DAPR.</ns2:discussion></ns2:results><ns2:comments/></ns1:sonarQCChecks><ns1:equipmentEffectiveness><ns2:results deviation="false"><ns2:issue><ns2:title>None Exist</ns2:title><ns2:discussion>There were no conditions or deficiencies that affected equipment operational effectiveness.</ns2:discussion><ns2:comments/></ns2:issue></ns2:results><ns2:comments/></ns1:equipmentEffectiveness><ns1:factorsAffectingSoundings><ns2:results deviation="false"><ns2:issue><ns2:title>None Exist</ns2:title><ns2:discussion>There were no other factors that affected corrections to soundings.</ns2:discussion><ns2:comments/></ns2:issue></ns2:results><ns2:comments/></ns1:factorsAffectingSoundings><ns1:soundSpeedMethods><ns1:castFrequency>SVP casts were typically taken every two to three hours in the deepest area being surveyed at the time.  The SVP casts were applied to the MBES lines in CARIS using the &quot;nearest in time,&quot; method.</ns1:castFrequency><ns1:discussion>Although the survey area covered a 25 nautical mile span of the Hudson River, surface sound velocity and water column sound velocity profiles showed very little variation, even across different days and work areas that were 10-20 miles apart.  Sound velocities ranged from 1496 meters per second (m/s) to 1503 m/s and it was rare to see more than a 3 m/s variation over the course of the day.  Upon inspecting MBES data in CARIS Subset editor, no sound velocity artifacts were found. </ns1:discussion><ns1:comments/></ns1:soundSpeedMethods><ns1:coverageEquipmentAndMethods><ns2:results deviation="false"><ns2:discussion>All equipment and survey methods were used as detailed in the DAPR.</ns2:discussion></ns2:results><ns2:comments/></ns1:coverageEquipmentAndMethods><ns1:additionalQualityControl><ns2:comments/></ns1:additionalQualityControl></ns1:qualityControl><ns1:echoSoundingCorrections><ns1:corrections><ns2:results deviation="false"><ns2:discussion>All data reduction procedures conform to those detailed in the DAPR.</ns2:discussion></ns2:results><ns2:comments/></ns1:corrections><ns1:calibrations><ns2:results deviation="false"><ns2:discussion>All sounding systems were calibrated as detailed in the DAPR.</ns2:discussion><ns2:calibration xsi:nil="true"/></ns2:results><ns2:comments/></ns1:calibrations><ns1:additionalIssues><ns2:comments/></ns1:additionalIssues></ns1:echoSoundingCorrections><ns1:backscatter><ns2:results acquired="true"><ns2:discussion>Raw Backscatter was logged in the .all file. Backscatter was not processed by the field unit.</ns2:discussion></ns2:results><ns2:comments/></ns1:backscatter><ns1:dataProcessing><ns1:drSoftware><ns1:bathySoftware deviation="false"><ns1:manufacturer xsi:nil="true"></ns1:manufacturer><ns1:name xsi:nil="true"></ns1:name><ns1:version xsi:nil="true"></ns1:version></ns1:bathySoftware><ns1:imagerySoftware deviation="false"><ns1:manufacturer xsi:nil="true"></ns1:manufacturer><ns1:name xsi:nil="true"></ns1:name><ns1:version xsi:nil="true"></ns1:version></ns1:imagerySoftware><ns1:featureObjectCatalog>NOAA Extended Attribute Files V_5_4.</ns1:featureObjectCatalog><ns1:discussion xsi:nil="true"></ns1:discussion><ns1:comments/></ns1:drSoftware><ns1:surfaces><ns1:surface><ns2:surfaceName>H12874_MB_50cm_HRD_Final</ns2:surfaceName><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:resolution units="centimeters">50</ns2:resolution><ns2:depthRange><ns2:min units="meters">0</ns2:min><ns2:max units="meters">20</ns2:max></ns2:depthRange><ns2:surfaceParameter>NOAA_0.5m</ns2:surfaceParameter><ns2:purpose>Object Detection</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceName>H12874_MB_1m_HRD_Final</ns2:surfaceName><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:resolution units="meters">1</ns2:resolution><ns2:depthRange><ns2:min units="meters">18</ns2:min><ns2:max units="meters">40</ns2:max></ns2:depthRange><ns2:surfaceParameter>NOAA_1m</ns2:surfaceParameter><ns2:purpose>Object Detection</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceName>H12874_MB_4m_HRD_Final</ns2:surfaceName><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:resolution units="meters">4</ns2:resolution><ns2:depthRange><ns2:min units="meters">36</ns2:min><ns2:max units="meters">80</ns2:max></ns2:depthRange><ns2:surfaceParameter>NOAA_4m</ns2:surfaceParameter><ns2:purpose>Object Detection</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceName>H12874_MB_50cm_HRD</ns2:surfaceName><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:resolution units="centimeters">50</ns2:resolution><ns2:depthRange><ns2:min units="meters">0.27</ns2:min><ns2:max units="meters">44.81</ns2:max></ns2:depthRange><ns2:surfaceParameter>NOAA_0.5m</ns2:surfaceParameter><ns2:purpose>Object Detection</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceName>H12874_MB_1m_HRD</ns2:surfaceName><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:resolution units="meters">1</ns2:resolution><ns2:depthRange><ns2:min units="meters">0.31</ns2:min><ns2:max units="meters">44.60</ns2:max></ns2:depthRange><ns2:surfaceParameter>NOAA_1m</ns2:surfaceParameter><ns2:purpose>Object Detection</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceName>H12874_MB_4m_HRD</ns2:surfaceName><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:resolution units="meters">4</ns2:resolution><ns2:depthRange><ns2:min units="meters">0.41</ns2:min><ns2:max units="meters">43.11</ns2:max></ns2:depthRange><ns2:surfaceParameter>NOAA_4m</ns2:surfaceParameter><ns2:purpose>Object Detection</ns2:purpose></ns1:surface><ns1:discussion>The survey was carried out to meet the Object Detection MBES Coverage requirements as defined by section 5.2.2.2 of the Hydrographic Surveys Specifications and Deliverables (2016 ed).  </ns1:discussion><ns1:comments/></ns1:surfaces><ns1:additionalDataProcessing><ns2:comments/></ns1:additionalDataProcessing></ns1:dataProcessing></ns1:dataAcquisitionAndProcessing><ns1:verticalAndHorizontalControl><ns1:discussion>Field installed tide or GPS stations were not utilized for this survey, so no HVCR report is included.

However, additional information discussing the Real Time Kinematic GPS correction method used for this survey can be found in the accompanying RTK Procedures document in the Project Reports folder.</ns1:discussion><ns1:verticalControl><ns2:verticalDatum>Hudson River Datum</ns2:verticalDatum><ns2:tideStations/><ns2:standard_or_ERZT used="false" xsi:nil="true"/><ns2:VDATUM_or_constantSep used="true"><ns2:methodsUsed>ERS via VDATUM</ns2:methodsUsed><ns2:ellipsoidToChartDatumSepFile><ns2:fileName>OPR-B396-NRT5BH2-16_HRD.csar0</ns2:fileName><ns2:fileName>OPR-B396-NRT5BH2-16_HRD.csar</ns2:fileName></ns2:ellipsoidToChartDatumSepFile><ns2:discussion>A separation model was provided by NOAA's Navigation Response Branch.</ns2:discussion><ns2:comments/></ns2:VDATUM_or_constantSep><ns2:comments/></ns1:verticalControl><ns1:horizontalControl><ns2:horizontalDatum>North American Datum of 1983 (NAD83)</ns2:horizontalDatum><ns2:projection>Universal Transverse Mercator (UTM) - Zone 18</ns2:projection><ns2:PPK used="true"><ns2:methodsUsed>Smart Base</ns2:methodsUsed><ns2:baseStations><ns2:CORSStations><ns2:HVCRSiteID>CTBR</ns2:HVCRSiteID><ns2:stationID>CTBR</ns2:stationID></ns2:CORSStations><ns2:CORSStations><ns2:HVCRSiteID>NYKT</ns2:HVCRSiteID><ns2:stationID>NYKT</ns2:stationID></ns2:CORSStations><ns2:CORSStations><ns2:HVCRSiteID>NYLC</ns2:HVCRSiteID><ns2:stationID>NYLC</ns2:stationID></ns2:CORSStations><ns2:CORSStations><ns2:HVCRSiteID>NYMD</ns2:HVCRSiteID><ns2:stationID>NYMD</ns2:stationID></ns2:CORSStations><ns2:CORSStations><ns2:HVCRSiteID>NYNB</ns2:HVCRSiteID><ns2:stationID>NYNB</ns2:stationID></ns2:CORSStations><ns2:CORSStations><ns2:HVCRSiteID>NYVH</ns2:HVCRSiteID><ns2:stationID>NYVH</ns2:stationID></ns2:CORSStations></ns2:baseStations><ns2:discussion>Due to dropouts of the New York State Department of Transportation Real Time Network, Real Time Kinematic (RTK) solutions were not available for day numbers 264 and 265.  For these days, Post Processed Kinematic (PPK) solutions were calculated using Applanix POS MMS 7.1 software.  The SBET and RMS files were applied to the data in CARIS HIPS.</ns2:discussion><ns2:comments/></ns2:PPK><ns2:PPP used="false" xsi:nil="true"/><ns2:RTK used="true"><ns2:discussion>Use of Real Time Kinematic GPS correctors provided three significant advantages:

1. Reduced Total Vertical Uncertainty (TVU) as compared to the TVU associated with traditional tidal zoning in the survey area.  TVU for tidal zoning is high due to the distance between the controlling gauge and the survey area, compounded by the affects of varying river discharge rates.

2. Reduced time in the field for data acquisition.  RTK allowed surveying at any rate of river discharge, where as traditional tide zoning would have required restricting acquisition to times when river discharge was approximately 7500 cfs or less.

3. Reduced processing time compared to Post Processed Kinematic methods.

Further discussion of the methods employed by the field unit can be found in a report in the Horizontal and Vertical Control folder.  The report is titled: &quot;RTK Procedures Report.&quot;  
</ns2:discussion><ns2:comments/></ns2:RTK><ns2:DGPS used="false" xsi:nil="true"/><ns2:comments/></ns1:horizontalControl><ns1:additionalIssues><ns2:issue><ns2:title>Vertical offset between PPK and RTK solutions</ns2:title><ns2:discussion>A vertical offset was found when comparing lines with PPK positioning to those with RTK positioning.  Specifically, due to the aforementioned RTK dropouts on day numbers 264 and 265, PPK solutions were calculated and applied to all lines for these days.  While application of PPK correctors brought the affected line's vertical agreement to within specification, a 25 cm vertical offset still existed between lines acquired during the drop out period and the rest of the survey.   With the help of HSTP, additional SBET analysis was completed and a processing method was discovered to eliminate this offset.  Please see Appendix II of this report for more information.  </ns2:discussion><ns2:comments/></ns2:issue><ns2:comments/></ns1:additionalIssues></ns1:verticalAndHorizontalControl><ns1:resultsAndRecommendations><ns1:chartComparison><ns1:methods><ns2:discussion>H12874 was compared to affected RNC and ENC products by creating a high density sounding layer in CARIS BathyDataBase and comparing charted water depths with surveyed soundings.  Additionally, shoreline and certain features were compared to the charts using 50 centimeter BASE surfaces generated in CARIS HIPS &amp; SIPS.
</ns2:discussion><ns2:comments/></ns1:methods><ns1:charts><ns2:rasterChart><ns2:chart><ns2:number>12347</ns2:number><ns2:kapp>2226</ns2:kapp><ns2:scale>40000</ns2:scale><ns2:edition>31</ns2:edition><ns2:editionDate>2010-07</ns2:editionDate><ns2:LNMDate>2016-12-31</ns2:LNMDate><ns2:NMDate>2016-12-31</ns2:NMDate></ns2:chart><ns2:discussion>In several places, charted depths differ significantly from soundings collected by this survey.  The area was last surveyed between 1900 and 1939.  Over the years, significant dredging and shoreline construction activities have taken place which has altered the current patterns and caused the river bottom to change shape.  In many areas, the charted shoreline does not give a good indication of the river's actual boundaries.  In several areas, bathymetry was collected over charted land and in others, shoals of 12 feet or less were reached well outside of the blue tinted area and outside of even 18 foot contours as well.  Significant attention to the charted shoreline will need to be given when this data is compiled to the chart, and especially when new chart products at a 1:12,000 scale are created. 

Due to the highly dynamic nature of the riverbed, modifications to its shoreline, and interval between its last survey (~100 years), soundings and features vary significantly when this survey is compared to the chart.  Differences of up to 20 feet can be expected.
</ns2:discussion><ns2:images><ns2:caption>Shallow water found outside of charted blue area (18 foot contour).</ns2:caption><ns2:link>SupportFiles\ShoalsOutside18ftContour.bmp</ns2:link></ns2:images><ns2:images><ns2:caption>MBES data collected over charted land. </ns2:caption><ns2:link>SupportFiles\SurveyOverChartedLand.bmp</ns2:link></ns2:images><ns2:comments/></ns2:rasterChart><ns2:ENC><ns2:chart><ns2:name>US5NY43M</ns2:name><ns2:scale>40000</ns2:scale><ns2:edition>14</ns2:edition><ns2:updateApplicationDate>2016-07-11</ns2:updateApplicationDate><ns2:issueDate>2016-07-11</ns2:issueDate><ns2:preliminary>false</ns2:preliminary></ns2:chart><ns2:discussion>ENC US5NY43M is a digitized version of raster chart 12347 and contains no additional features.  US5NY43M was compared to H12874 and contains the same issues as raster 12347.</ns2:discussion><ns2:comments/></ns2:ENC><ns2:ENC><ns2:chart><ns2:name>US5NY40M</ns2:name><ns2:scale>40000</ns2:scale><ns2:edition>14</ns2:edition><ns2:updateApplicationDate>2016-12-21</ns2:updateApplicationDate><ns2:issueDate>2016-12-21</ns2:issueDate><ns2:preliminary>false</ns2:preliminary></ns2:chart><ns2:discussion>The southern portion of the survey area overlaps US5NY40M.  For this area of overlap, US5NY40M is a digitized version of raster chart 12347 and contains no additional features.  US5NY40M was compared to H12874 and contains the same issues as raster 12347.</ns2:discussion><ns2:comments/></ns2:ENC><ns2:comments/></ns1:charts><ns1:maritimeBoundary><ns2:results investigated="None Exist"><ns2:discussion>No Maritime Boundary Points were assigned for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:maritimeBoundary><ns1:chartedFeatures><ns2:results investigated="Investigated"><ns2:discussion> At location: 41⁰ 36’ 3.58” N, 073⁰ 57’ 36.40”W, a &quot;position approximate&quot; wreck is charted.  This feature was disproved by MBES, but two wrecks were found just to the south.  These wrecks are included in the Final Feature File with least depths. 
At location: 41⁰ 37’ 15.67” N, 073⁰ 57’ 18.38”W, a &quot;position approximate&quot; wreck is charted.  This feature was disproved by MBES, but a wreck was found just to the north.  This wreck is included in the Final Feature File with a least depth. 
At location: 41⁰ 37’ 47.71” N, 073⁰ 57’ 16.09”W, a &quot;position approximate&quot; wreck is charted.  This feature was disproved by MBES, but a wreck was found just to the north.  This wreck is included in the Final Feature File with a least depth. 
At location: 41⁰ 54’ 04.73” N, 073⁰ 57’ 48.01”W, a &quot;position approximate&quot; obstruction (reported to be an anchor) is charted.  No evidence of this feature exists in MBES data.  More information on this PA OBSTRN can be found in the Final Feature File. 
At location: 41⁰ 54’ 34.34” N, 073⁰ 58’ 07.03”W, an assigned “existence doubtful” wreck with portions showing above the waterline is charted.  No evidence of this feature was present visually.  More information on this feature can be found in the Final Feature File.  There are also two other non-assigned wrecks near this location.  These wrecks were not observed by the hydrographer, but could not be disproved with MBES due to shallow water depths.  The hydrographer recommends these visible wrecks be updated to submerged wrecks.  



</ns2:discussion></ns2:results><ns2:comments/></ns1:chartedFeatures><ns1:unchartedFeatures><ns2:results investigated="Investigated"><ns2:discussion> In addition to the assigned features, 59 additional features are included with this survey.  Please refer to the Final Feature File for more details (H12874_FFF.hob).</ns2:discussion></ns2:results><ns2:comments/></ns1:unchartedFeatures><ns1:DTONS><ns2:results reportSubmitted="true"><ns2:numberSubmitted>1</ns2:numberSubmitted><ns2:report><ns2:title>H12874 Area DtoN 1</ns2:title><ns2:dateSubmitted>2017-01-09</ns2:dateSubmitted></ns2:report><ns2:discussion>Danger to Navigation Reports are included in Appendix II of this report.</ns2:discussion></ns2:results><ns2:comments><ns2:branchComment concurrence="Concur"><ns2:comment>The Dton has been applied to the latest charts and the Dton report is appended to this report.</ns2:comment></ns2:branchComment></ns2:comments></ns1:DTONS><ns1:shoalAndHazardousFeatures><ns2:results investigated="Investigated"><ns2:discussion>Shoals and potentially hazardous features have been discussed in D.1.7 Dangers to Navigation.  There are no additional shoals or potentially hazardous features to report. </ns2:discussion></ns2:results><ns2:comments/></ns1:shoalAndHazardousFeatures><ns1:channels><ns2:results investigated="Investigated"><ns2:discussion>In the northern portion of the sheet, part of the Kingston Point Reach channel exists.  Although this maintained channel was not part of the survey area, crosslines and overlap at the sheet edges caused portions of the channel to be surveyed.  Soundings acquired in these areas were compared to the chart's tabulated depths and were generally found to be equal to or deeper than the control depth.  
</ns2:discussion><ns2:images><ns2:caption>Southern portion of Kingston Point Reach maintained channel.</ns2:caption><ns2:link>SupportFiles\KingstonPtReachChannel.bmp</ns2:link></ns2:images></ns2:results><ns2:comments/></ns1:channels><ns1:bottomSamples><ns2:results investigated="None Exist"><ns2:discussion>No bottom samples were required for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:bottomSamples></ns1:chartComparison><ns1:additionalResults><ns1:shoreline><ns2:results investigated="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.</ns2:discussion><ns2:images><ns2:caption>Low tide reconnaissance of shoreline containing wrecks of barges or pier ruins.</ns2:caption><ns2:link>SupportFiles\wreck-barges - just north of South Cross west side of channel.jpg</ns2:link></ns2:images></ns2:results><ns2:comments/></ns1:shoreline><ns1:priorSurveys><ns2:results investigated="None Exist"><ns2:discussion>No prior survey comparisons exist for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:priorSurveys><ns1:ATONS><ns2:results investigated="Investigated"><ns2:discussion>No aids to navigation (ATONs) were assigned for positioning.  Over the course of the survey, all AtoNs were observed during daylight hours to be on station and serving their intended purpose.</ns2:discussion></ns2:results><ns2:comments><ns2:branchComment concurrence="Comment Only"><ns2:comment>During operations for H12874, the Roundout Creek Leading Light was observed to be approximately 50 meters off station; this discrepancy is addressed in the Final Feature File.</ns2:comment></ns2:branchComment></ns2:comments></ns1:ATONS><ns1:overheadFeatures><ns2:results investigated="Investigated"><ns2:discussion>A rail bridge and highway bridge cross the river at the city of Poughkeepsie, NY.  Both of these bridges are charted approximately 35 meters north of their actual positions.  The actual position was determined by acquisition of MBES data up against the bridge piers.  The hydrographer recommends that the compiler re-chart the bridge in the correct location using the holes in the BASE surface or modern shoreline photogrammetry as a guide.  </ns2:discussion><ns2:images><ns2:caption>Charted vs. surveyed position discrepancy of rail bridge in Poughkeepsie, NY.</ns2:caption><ns2:link>SupportFiles\BridgeChartedNorth.bmp</ns2:link></ns2:images><ns2:images><ns2:caption>Charted vs. surveyed position discrepancy of highway bridge in Poughkeepsie, NY.</ns2:caption><ns2:link>SupportFiles\BridgeChartedNorth2.bmp</ns2:link></ns2:images></ns2:results><ns2:comments/></ns1:overheadFeatures><ns1:submarineFeatures><ns2:results investigated="Investigated"><ns2:discussion>Three pipelines are charted within the survey area. The southern two appear to be well buried or non-existent due to a complete lack of evidence found when investigating the MBES data.  At the very northeastern portion of the sheet a charted intake pipeline was confirmed by MBES, although the charted position is slightly north of the actual position.  The updated position and least depth of this feature is included with the Final Feature File. </ns2:discussion><ns2:images><ns2:caption>Charted intake pipeline shown with surveyed evidence of the actual position to the south.</ns2:caption><ns2:link>SupportFiles\IntakePipeline.bmp</ns2:link></ns2:images></ns2:results><ns2:comments/></ns1:submarineFeatures><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:platforms><ns2:results investigated="None Exist"><ns2:discussion>No platforms exist for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:platforms><ns1:significantFeatures><ns2:results investigated="None Exist"><ns2:discussion>No Significant Features exist for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:significantFeatures><ns1:constructionOrDredging><ns2:results investigated="Investigated"><ns2:discussion>As mentioned in section D.2.10, areas of ongoing shoreline construction occur frequently along the river.  Some construction was taking place in Kingston Creek, just outside of the survey limits. 

Dredging occurs at the direction of the Army Corps of Engineers to maintain channel project depth for deep draft commercial vessels that frequently transit this portion of the river.   </ns2:discussion></ns2:results><ns2:comments/></ns1:constructionOrDredging><ns1:otherResults><ns2:comments/></ns1:otherResults><ns1:newSurveyRecommendation><ns2:results recommended="true"><ns2:discussion>Due to extensive shoreline construction, a thorough survey of Rondout Creek could not be conducted at the time of this survey.  Commercial vessels up to 160 feet in length use the creek daily and thousands of recreational boats transit this area seasonally.  The hydrographer recommends a full survey of this creek be conducted upon completion of the current construction activities.

See Appendix II for correspondence relating to Rondout Creek and the ongoing construction.  Initially, the hydrographer recommended that the creek could be surveyed at least back to the first highway bridge as an addition to H12874, but after repeatedly transiting by construction area, it became clear that a survey would have more value if carried out after construction efforts had been completed.  </ns2:discussion><ns2:images><ns2:caption>Ongoing shoreline construction in Rondout Creek, Kingston, NY.</ns2:caption><ns2:link>SupportFiles\RondoutCreekConstruction.jpg</ns2:link></ns2:images></ns2:results><ns2:comments/></ns1:newSurveyRecommendation><ns1:insetRecommendation><ns2:results recommended="true"><ns2:discussion>The current 1:40,000 scale chart does not provide sufficient detail to support the area's commercial and voluminous recreational use. NOAA's Marine Chart Division intends to create 1:12000 scale charts for the Hudson River from Troy, NY to the Tappan Zee Bridge in the next couple years.  The hydrographer recommends creating an inset of this area in the event the pending larger scale chart creating is delayed. </ns2:discussion></ns2:results><ns2:comments/></ns1:insetRecommendation></ns1:additionalResults></ns1:resultsAndRecommendations><ns1:approvalSheet><ns1:statements><ns1:supervision>As Chief of Party, field operations for this hydrographic survey were conducted under my direct supervision, with frequent personal checks of progress and adequacy. I have reviewed the attached survey data and reports.</ns1:supervision><ns1:approval>All field sheets, this Descriptive Report, and all accompanying records and data are approved. All records are forwarded for final review and processing to the Processing Branch.</ns1:approval><ns1:adequacyOfSurvey>The survey data meets or exceeds requirements as set forth in the NOS Hydrographic Surveys and Specifications Deliverables Manual, 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:additionalInfo xsi:nil="true"></ns1:additionalInfo></ns1:statements><ns1:signingPersonnel><ns2:approverName>Andrew R. Clos</ns2:approverName><ns2:approverTitle>Chief of Party</ns2:approverTitle><ns2:approvalDate>2017-01-13</ns2:approvalDate></ns1:signingPersonnel></ns1:approvalSheet></ns1:descriptiveReport>