<?xml version="1.0" encoding="UTF-8"?><ns1:descriptiveReport xmlns:ns1="http://svn.pydro.noaa.gov/2017/01/DescriptiveReport" xmlns:ns2="http://svn.pydro.noaa.gov/2017/01/AllGlobalTypes" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://svn.pydro.noaa.gov/2017/01/DescriptiveReport http://svn.pydro.noaa.gov/2017/01/DR.xsd"><ns1:verticalAndHorizontalControl><ns1:additionalIssues><ns2:issue><ns2:comments/><ns2:images><ns2:link>file:///M:/OPRB396NRT5BH217/Surveys/H13023/Compilation/Report/Components/DR%20pics/Lack%20of%20VDatum%20Coverage.png</ns2:link><ns2:caption>A small bay on the western side of the Hudson River lacked coverage by the VDatum model provided.</ns2:caption></ns2:images><ns2:title>Lack of VDatum Coverage in Bay</ns2:title><ns2:discussion>A bay on the west side of the Hudson River lacked sufficient coverage from the VDatum model OPR-B396-NRB-17_xyNAD83-MLLW_geoid12b (Figure 13).  The lines in the bay could not use the provided model when computing GPS tides.  The project manager and NRB approved of applying a static value of to those lines using the nearest value provided by the model (-32m).  See the Hudson River VDatum Coverage Fix email discussion in the Supplemental Correspondence for futher information. Once applied, a visual inspection of the data confirmed the fix resulted in a better solution.</ns2:discussion></ns2:issue><ns2:issue><ns2:comments/><ns2:title>RTK Signal Dropouts</ns2:title><ns2:discussion>During survey operations internet connection sometimes cut out, resulting in the loss of CORS corrections being fed to the POS MV5.  Once noticed, the field unit would stop logging, regain internet connection and CORS feeding corrections to the POS MV5, and start surveying where connection was first lost.  On days that had connection issues, SBETs were created and applied to the data.  The application of SBETs resolved much of the vertical drift between RTK and PPK applied lines, but not completely.  These areas were examined for hazards and contacts and none were found.</ns2:discussion></ns2:issue><ns2:issue><ns2:comments/><ns2:title>Vertical offset between NRT5 DN200 and other days</ns2:title><ns2:discussion>There is a 0.2m offset between lines acquired on DN200 by NRT5 and adjacent lines from DN198 and 195 from BHII, and DN206, 207, and 221 from NRT5.  Several tests were done, including applying a SBET and applying TCARI tides.  The application of these other methods either made the data appear worse or had no significant effect.  The lines used in testing had GPS Tides recomputed, some have SBETs still applied, and the offset remains.</ns2:discussion></ns2:issue><ns2:comments/></ns1:additionalIssues><ns1:horizontalControl><ns2:DGPS used="false" xsi:nil="true"/><ns2:PPP used="false" xsi:nil="true"/><ns2:comments/><ns2:projection>Universal Transverse Mercator (UTM) Zone 18 North</ns2:projection><ns2:WAAS used="false" xsi:nil="true"/><ns2:horizontalDatum>North American Datum of 1983 (NAD83)</ns2:horizontalDatum><ns2:PPK used="true"><ns2:baseStations/><ns2:methodsUsed>Smart Base</ns2:methodsUsed><ns2:comments/><ns2:discussion>Real Time Kinematic (RTK) corrections were used using CORS stations maintained by the New York Department of Transportation (NYDOT) as part of the New York State Spatial Reference Network (NYSNet).  Horizontal network datum for NYSNet correctors is NAD83 (CORS96). Additional information regarding the NYSnet system can be found at http://cors.dot.ny.gov/spiderweb/frmIndex.aspx. 

To receive the corrections, a stable internet connection using NTRIP (Network Transport of RTCM data over IP) software was used on a laptop.  A serial connection was then connected to the POS MV5 to transmit the corrections.  The program could be visually monitored on the laptop to watch for connection dropouts, and if that happened the survey line could either be re-run or have an SBET applied during post processing.

Two CORS stations were used, which were NEWBURGH (NYNB) and VALHALLA (NYVH).</ns2:discussion></ns2:PPK><ns2:RTK used="true"><ns2:comments/><ns2:discussion xsi:nil="true"></ns2:discussion></ns2:RTK></ns1:horizontalControl><ns1:verticalControl><ns2:verticalDatum>Mean Lower Low Water</ns2:verticalDatum><ns2:VDATUM_or_constantSep used="true"><ns2:methodsUsed>ERS via VDATUM</ns2:methodsUsed><ns2:comments/><ns2:discussion xsi:nil="true"></ns2:discussion><ns2:ellipsoidToChartDatumSepFile><ns2:fileName>OPR-B396-NRB-17_xyNAD83-MLLW_geoid12b.csar</ns2:fileName></ns2:ellipsoidToChartDatumSepFile></ns2:VDATUM_or_constantSep><ns2:tideStations/><ns2:comments/><ns2:standard_or_ERZT used="false" xsi:nil="true"/></ns1:verticalControl><ns1:discussion>Field installed tide or GPS stations were not utilized for this survey, so no HVCR report is included.

</ns1:discussion></ns1:verticalAndHorizontalControl><ns1:metadata><ns1:registryMetadata><ns2:scale>5000</ns2:scale><ns2:registryNumber>H13023</ns2:registryNumber><ns2:sublocality>Tappan Zee Bridge to Haverstraw</ns2:sublocality><ns2:stateOrTerritory>New York</ns2:stateOrTerritory><ns2:sheetID>2</ns2:sheetID><ns2:registryInstructions>Survey shoreward to the extent necessary to support charting an updated 12 foot contour.</ns2:registryInstructions><ns2:country>United States</ns2:country></ns1:registryMetadata><ns1:projectMetadata><ns2:number>OPR-B396-NRT5BH2-17</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:surveyMetadata><ns2:datesOfSurvey><ns2:end>2017-08-09</ns2:end><ns2:start>2017-07-13</ns2:start></ns2:datesOfSurvey><ns2:verifier>Pacific Hydrographic Branch</ns2:verifier><ns2:timeZone>UTC</ns2:timeZone><ns2:projectType>Navigable Area</ns2:projectType><ns2:year>2017</ns2:year><ns2:chiefOfParty>LTJG Dylan Kosten</ns2:chiefOfParty><ns2:PIDate>2017-05-31</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:equipmentTypes><ns2:imageryEquipment>Multibeam Echo Sounder Backscatter</ns2:imageryEquipment><ns2:soundingEquipment>Multibeam Echo Sounder</ns2:soundingEquipment></ns2:equipmentTypes><ns2:horizontalCoordinateSystem zone="18 North">Universal Transverse Mercator (UTM)</ns2:horizontalCoordinateSystem></ns1:surveyMetadata><ns1:assignment>NOAA</ns1:assignment></ns1:metadata><ns1:areaSurveyed><ns1:surveyCoverage><ns2:coverageRequirement><ns2:requiredCoverage>Object Detection Coverage (refer to HSSD Section 5.2.2.2)</ns2:requiredCoverage><ns2:waterDepth>All waters in survey area</ns2:waterDepth></ns2:coverageRequirement><ns2:comments/><ns2:results deviation="true"><ns2:images><ns2:link>file:///M:/OPRB396NRT5BH217/Surveys/H13023/Compilation/Report/Components/DR%20pics/Survey%20Coverage%20Facility.PNG</ns2:link><ns2:caption>Lack of survey coverage due to facility on the water.</ns2:caption></ns2:images><ns2:images><ns2:link>file:///M:/OPRB396NRT5BH217/Surveys/H13023/Compilation/Report/Components/DR%20pics/Survey%20Coverage%20Holiday%20ATON%20and%20shoal.PNG</ns2:link><ns2:caption>Holidays from a shoal area and an ATON.</ns2:caption></ns2:images><ns2:images><ns2:link>file:///M:/OPRB396NRT5BH217/Surveys/H13023/Compilation/Report/Components/DR%20pics/Survey%20Coverage%20Holiday%20Exploratory%20Lines.PNG</ns2:link><ns2:caption>Holidays created from lines exploring transit paths to deeper areas.</ns2:caption></ns2:images><ns2:images><ns2:link>file:///M:/OPRB396NRT5BH217/Surveys/H13023/Compilation/Report/Components/DR%20pics/Survey%20Coverage%20Holiday%20Deep.PNG</ns2:link><ns2:caption>Holiday located in deeper waters.</ns2:caption></ns2:images><ns2:discussion>Complete multibeam coverage was achieved within the limits of hydrography as defined in the Project Instructions with some exceptions.  The following are examples of areas that do not meet the coverage requirement.

Towards the northwest of the sheet there is a facility with piers and dolphins that blocked access to the 12 foot contour (Figure 3).  Efforts were made to collect data as close to the facility as possible.

There are multiple small areas that do not reach the 12 foot contour, primarily due to working right next to the shore.  For these situations, safety was the concern.

There are some holidays in the sheet.  The majority are surrounding ATONs, shoal areas, or between exploratory lines to or from an isolated deep spot (Figures 4 and 5).  One holiday located towards the middle of the river does not fall under any of those categories (Figure 6).</ns2:discussion></ns2:results></ns1:surveyCoverage><ns1:surveyPurpose><ns2:comments/><ns2:discussion>The Hudson River Pilots Association is requesting updated survey data in the Hudson River from the Tappan Zee 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></ns1:surveyPurpose><ns1:surveyQuality><ns2:comments/><ns2:images><ns2:link>file:///M:/OPRB396NRT5BH217/Surveys/H13023/Compilation/Report/Components/DR%20pics/H13023_MB_50cm_MLLW_FINAL_Density.png</ns2:link><ns2:caption>Pydro derived histogram plot showing HSSD object detection compliance of H13023 MBES data within the 50cm finalized CUBE surface.</ns2:caption></ns2:images><ns2:adequacy>The entire survey is adequate to supersede previous data.</ns2:adequacy><ns2:discussion>The Finalized CSAR QA tool within Pydro Explorer was used to analyze multibeam echosounder (MBES) data density.  The finalized surface met the HSSD data density requirement (Figure 2).</ns2:discussion></ns1:surveyQuality><ns1:surveyStatistics><ns2:comments/><ns2:surveyDates>2017-07-13</ns2:surveyDates><ns2:surveyDates>2017-07-14</ns2:surveyDates><ns2:surveyDates>2017-07-17</ns2:surveyDates><ns2:surveyDates>2017-07-18</ns2:surveyDates><ns2:surveyDates>2017-07-19</ns2:surveyDates><ns2:surveyDates>2017-07-25</ns2:surveyDates><ns2:surveyDates>2017-07-26</ns2:surveyDates><ns2:surveyDates>2017-07-27</ns2:surveyDates><ns2:surveyDates>2017-07-28</ns2:surveyDates><ns2:surveyDates>2017-07-31</ns2:surveyDates><ns2:surveyDates>2017-08-01</ns2:surveyDates><ns2:surveyDates>2017-08-02</ns2:surveyDates><ns2:surveyDates>2017-08-03</ns2:surveyDates><ns2:surveyDates>2017-08-07</ns2:surveyDates><ns2:surveyDates>2017-08-08</ns2:surveyDates><ns2:surveyDates>2017-08-09</ns2:surveyDates><ns2:totalSurveyStats><ns2:SNM>5.57</ns2:SNM><ns2:DP>0</ns2:DP><ns2:diveOps>0</ns2:diveOps><ns2:bottomSamples>9</ns2:bottomSamples><ns2:maritimeBoundaryPoints>0</ns2:maritimeBoundaryPoints></ns2:totalSurveyStats><ns2:LNM><ns2:vesselLNM><ns2:vessel><ns2:statistics><ns2:MS_SBES_SSS>0</ns2:MS_SBES_SSS><ns2:XL_MBES_SBES>24.919</ns2:XL_MBES_SBES><ns2:XL_lidar>0</ns2:XL_lidar><ns2:MS_MBES_SSS>0</ns2:MS_MBES_SSS><ns2:MS_MBES>274.058</ns2:MS_MBES><ns2:MS_lidar>0</ns2:MS_lidar><ns2:MS_SBES_MBES>0</ns2:MS_SBES_MBES><ns2:MS_SBES>0</ns2:MS_SBES><ns2:MS_SSS>0</ns2:MS_SSS></ns2:statistics><ns2:hullID>S3002</ns2:hullID></ns2:vessel><ns2:vessel><ns2:statistics><ns2:MS_SBES_SSS>0</ns2:MS_SBES_SSS><ns2:XL_MBES_SBES>0</ns2:XL_MBES_SBES><ns2:XL_lidar>0</ns2:XL_lidar><ns2:MS_MBES_SSS>0</ns2:MS_MBES_SSS><ns2:MS_MBES>309.365</ns2:MS_MBES><ns2:MS_lidar>0</ns2:MS_lidar><ns2:MS_SBES_MBES>0</ns2:MS_SBES_MBES><ns2:MS_SBES>0</ns2:MS_SBES><ns2:MS_SSS>0</ns2:MS_SSS></ns2:statistics><ns2:hullID>S5401</ns2:hullID></ns2:vessel></ns2:vesselLNM><ns2:totalLNM><ns2:MS_SBES_SSS>0</ns2:MS_SBES_SSS><ns2:percentXLLNM>4.27</ns2:percentXLLNM><ns2:XL_MBES_SBES>24.919</ns2:XL_MBES_SBES><ns2:XL_lidar>0</ns2:XL_lidar><ns2:MS_MBES_SSS>0</ns2:MS_MBES_SSS><ns2:MS_MBES>583.423</ns2:MS_MBES><ns2:MS_lidar>0</ns2:MS_lidar><ns2:MS_SBES_MBES>0</ns2:MS_SBES_MBES><ns2:MS_SBES>0</ns2:MS_SBES><ns2:MS_SSS>0</ns2:MS_SSS></ns2:totalLNM></ns2:LNM><ns2:discussion xsi:nil="true"></ns2:discussion></ns1:surveyStatistics><ns1:coverageGraphic><ns2:coverageGraphicImage/></ns1:coverageGraphic><ns1:areaDescription><ns2:comments/><ns2:images><ns2:link>file:///M:/OPRB396NRT5BH217/Surveys/H13023/Compilation/Report/Components/DR%20pics/A1%20Survey%20Limits.PNG</ns2:link><ns2:caption>Extent of survey coverage with sheet limits shown in black.</ns2:caption></ns2:images><ns2:limits><ns2:northWest><ns2:longitude hemisphere="W">73.961</ns2:longitude><ns2:latitude hemisphere="N">41.216</ns2:latitude></ns2:northWest><ns2:southEast><ns2:longitude hemisphere="W">73.877</ns2:longitude><ns2:latitude hemisphere="N">41.137</ns2:latitude></ns2:southEast></ns2:limits><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 H13023 began south of Grassy Point near Haverstraw, NY, and ended near Scarborough, NY.</ns2:discussion></ns1:areaDescription><ns1:surveyLimits><ns2:comments/><ns2:results deviation="true"><ns2:discussion>Data were acquired within survey limits in accordance with the requirements in the Project Instructions and the HSSD.</ns2:discussion></ns2:results></ns1:surveyLimits></ns1:areaSurveyed><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:approverTitle>Chief of Party</ns2:approverTitle><ns2:approverName>LTJG Dylan Kosten</ns2:approverName><ns2:approvalDate>2017-12-20</ns2:approvalDate></ns1:signingPersonnel><ns1:signingPersonnel><ns2:approverTitle>Sheet Manager</ns2:approverTitle><ns2:approverName>PST Michael Bloom</ns2:approverName><ns2:approvalDate>2017-12-20</ns2:approvalDate></ns1:signingPersonnel></ns1:approvalSheet><ns1:dataAcquisitionAndProcessing><ns1:echoSoundingCorrections><ns1:additionalIssues><ns2:comments/></ns1:additionalIssues><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: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:echoSoundingCorrections><ns1:backscatter><ns2:comments/><ns2:results acquired="true"><ns2:images><ns2:link>file:///M:/OPRB396NRT5BH217/Surveys/H13023/Compilation/Report/Components/DR%20pics/Backscatter.PNG</ns2:link><ns2:caption>Coverage of backscatter mosaics.</ns2:caption></ns2:images><ns2:discussion>Raw Backscatter was logged in the .all file and will be sent to the Processing Branch. Backscatter was processed by the field unit for the purpose of bottom sample classification (Figure 12).</ns2:discussion></ns2:results></ns1:backscatter><ns1:qualityControl><ns1:factorsAffectingSoundings><ns2:comments/><ns2:results deviation="false"><ns2:issue><ns2:comments/><ns2:title>None Exist</ns2:title><ns2:discussion>There were no other factors that affected corrections to soundings.</ns2:discussion></ns2:issue></ns2:results></ns1:factorsAffectingSoundings><ns1:junctions><ns2:junction><ns2:survey><ns2:registryNumber>H13022</ns2:registryNumber><ns2:scale>5000</ns2:scale><ns2:relativeLocation>N</ns2:relativeLocation><ns2:fieldUnit>NOAA R/V BAY HYDRO II</ns2:fieldUnit><ns2:year>2017</ns2:year></ns2:survey><ns2:comments/><ns2:images><ns2:link>file:///M:/OPRB396NRT5BH217/Surveys/H13023/Compilation/Report/Components/DR%20pics/Junction%20H13022%20Statistics.PNG</ns2:link><ns2:caption>Absolute difference statistics between H13023 and H13022.</ns2:caption></ns2:images><ns2:images><ns2:link>file:///M:/OPRB396NRT5BH217/Surveys/H13023/Compilation/Report/Components/DR%20pics/Junction%20Abs%20Diff%20surface.PNG</ns2:link><ns2:caption>A region of greater vertical difference between H13023 and H13022 occurs toward the eastern side of the river.</ns2:caption></ns2:images><ns2:discussion>Overlap between H13022 and H13023 was approximately 200 meters.  In CARIS HIPS a difference surface was made using 50cm surfaces and statistics computed (Figure 10).  The mean difference was 0.077, with a standard deviation of 0.059.  An area of greater disagreement was present on the east side of the river (Figure 11)</ns2:discussion></ns2:junction><ns2:junction><ns2:survey><ns2:registryNumber>H13092</ns2:registryNumber><ns2:scale>5000</ns2:scale><ns2:relativeLocation>S</ns2:relativeLocation><ns2:fieldUnit>Navigation Response Team 5</ns2:fieldUnit><ns2:year>2017</ns2:year></ns2:survey><ns2:comments/><ns2:discussion>Junction analysis between H13023 and H13092 is located in the DR of H13092.</ns2:discussion></ns2:junction><ns2:comments/><ns2:discussion>There are two surveys that junction with H13023, both acquired in the same season as part of the same project.  To the north, H13022 was processed by Bay Hydrographer II and consisted of data from S5401 and S3002.  To the south, H13092 was processed by NRT5 and consisted of data from S5401, S3002, and S3007.</ns2:discussion></ns1:junctions><ns1:soundSpeedMethods><ns1:comments/><ns1:castFrequency>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:castFrequency><ns1:discussion xsi:nil="true"></ns1:discussion></ns1:soundSpeedMethods><ns1:uncertainty><ns2:values><ns2:tideUncertainty><ns2:measured units="meters">0</ns2:measured><ns2:zoning units="meters">0.094</ns2:zoning><ns2:tideMethod>ERS via VDATUM</ns2:tideMethod></ns2:tideUncertainty><ns2:soundSpeedUncertainty><ns2:measuredMVP units="meters/second">0</ns2:measuredMVP><ns2:measuredCTD units="meters/second">2</ns2:measuredCTD><ns2:surface units="meters/second">0.5</ns2:surface><ns2:hullID>S3002</ns2:hullID></ns2:soundSpeedUncertainty><ns2:soundSpeedUncertainty><ns2:measuredMVP units="meters/second">0</ns2:measuredMVP><ns2:measuredCTD units="meters/second">2</ns2:measuredCTD><ns2:surface units="meters/second">0.5</ns2:surface><ns2:hullID>S5401</ns2:hullID></ns2:soundSpeedUncertainty></ns2:values><ns2:comments/><ns2:images><ns2:link>file:///M:/OPRB396NRT5BH217/Surveys/H13023/Compilation/Report/Components/DR%20pics/H13023_MB_50cm_MLLW_FINAL_TVU_QC.png</ns2:link><ns2:caption>Pydro derived histogram plot showing HSSD uncertainty standards compliance of H13023 0.5m finalized surface.</ns2:caption></ns2:images><ns2:discussion>The uncertainty statistics (Figure 9) were calculated using Pydro Explorer's Finalized CSAR QA tool.

Total Propagated Uncertainty (TPU) values for H13023 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.  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 on the outside border of the survey coverage.

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, and navigation were applied real-time, because H13023 used a real-time kinematic (RTK) positioning service. The recorded delayed heave Applanix files included an estimate of the heave uncertainty and were applied during post-processing. All of the aforementioned uncertainties were applied in CARIS. As stated, H13023 is an ellipsoidally referenced survey (ERS) and the tidal component was accomplished with a separation model. Additional information about RTK and the separation model is
located in section C.1 and C.2 of this document.</ns2:discussion></ns1:uncertainty><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:images><ns2:link>file:///M:/OPRB396NRT5BH217/Surveys/H13023/Compilation/Report/Components/DR%20pics/XL%20Compute%20Statistics.PNG</ns2:link><ns2:caption>Statistics from the difference between the crosslines and mainscheme lines.</ns2:caption></ns2:images><ns2:images><ns2:link>file:///M:/OPRB396NRT5BH217/Surveys/H13023/Compilation/Report/Components/DR%20pics/Crossline%20Separation.PNG</ns2:link><ns2:caption>Subset showing roughly 0.2m offset between NRT5 crossline and BHII mainscheme line.</ns2:caption></ns2:images><ns2:discussion>Multibeam crosslines were acquired by S3002.  A 50cm CUBE surface was created using only mainscheme lines, and a second 50cm CUBE surface was created using only crosslines.  A difference surface was generated from these two surfaces in CARIS HIPS and SIPS, and then statistics computed using the Diff sublayer (Figure 7).  The mean was 0.12m and the standard deviation was 0.08m.  The areas of highest difference were typically between the crosslines, which were acquired solely by S3002, and mainscheme data acquired by S5401 (Figure 8).</ns2:discussion></ns1:crosslines><ns1:equipmentEffectiveness><ns2:comments/><ns2:results deviation="true"><ns2:issue><ns2:comments/><ns2:title>Cellular network dropouts</ns2:title><ns2:discussion>The use of the New York State Spatial Reference Network (for RTK corrections) required a stable internet connection, which the field units (BHII and NRT5) connected to using a Sierra Wireless cellular Internet Wi-Fi modem.  Both teams had RTK dropouts when internet connection failed.  If the dropout was noticed quickly, the teams would reacquire the data once RTK corrections were once again being fed to the POS MV5.  In the cases where data could not be reacquired, SBETs were created.  Vertical offsets could be partly reduced once SBETs were applied and meet HSSD specifications.  </ns2:discussion></ns2:issue></ns2:results></ns1:equipmentEffectiveness><ns1:coverageEquipmentAndMethods><ns2:comments/><ns2:results deviation="true"><ns2:discussion>All equipment and survey methods were used as detailed in the DAPR.</ns2:discussion></ns2:results></ns1:coverageEquipmentAndMethods><ns1:additionalQualityControl><ns2:comments/></ns1:additionalQualityControl></ns1:qualityControl><ns1:dataProcessing><ns1:drSoftware><ns1:imagerySoftware deviation="false"><ns1:version xsi:nil="true"></ns1:version><ns1:name xsi:nil="true"></ns1:name><ns1:manufacturer xsi:nil="true"></ns1:manufacturer></ns1:imagerySoftware><ns1:featureObjectCatalog>NOAA Profile V_5_6</ns1:featureObjectCatalog><ns1:comments/><ns1:bathySoftware deviation="true"><ns1:version>10.3.3</ns1:version><ns1:name>HIPS/SIPS</ns1:name><ns1:manufacturer>CARIS</ns1:manufacturer></ns1:bathySoftware><ns1:discussion xsi:nil="true"></ns1:discussion></ns1:drSoftware><ns1:surfaces><ns1:surface><ns2:resolution units="meters">0.5</ns2:resolution><ns2:purpose>Object Detection</ns2:purpose><ns2:surfaceType>CARIS Raster Surface (CUBE)</ns2:surfaceType><ns2:depthRange><ns2:min units="meters">0.02</ns2:min><ns2:max units="meters">15.93</ns2:max></ns2:depthRange><ns2:surfaceName>H13023_MB_50cm_MLLW</ns2:surfaceName><ns2:surfaceParameter>NOAA_0.5m</ns2:surfaceParameter></ns1:surface><ns1:surface><ns2:resolution units="meters">0.5</ns2:resolution><ns2:purpose>Object Detection</ns2:purpose><ns2:surfaceType>CARIS Raster Surface (CUBE)</ns2:surfaceType><ns2:depthRange><ns2:min units="meters">0</ns2:min><ns2:max units="meters">15.9</ns2:max></ns2:depthRange><ns2:surfaceName>H13023_MB_50cm_MLLW_FINAL</ns2:surfaceName><ns2:surfaceParameter>NOAA_0.5m</ns2:surfaceParameter></ns1:surface><ns1:comments/><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 (2017 ed).

QC Tools in PydroExplorer was used to analyze the surfaces for fliers.  There were 19 fliers, and upon review were found to be located on a man-made pipe feature and piles from a pier.  The pipe is well defined by other soundings and the pier is charted, so no fliers were found to be of concern.</ns1:discussion></ns1:surfaces><ns1:additionalDataProcessing><ns2:comments/></ns1:additionalDataProcessing></ns1:dataProcessing><ns1:equipmentAndVessels><ns1:vessels><ns1:vessel><ns2:draft units="feet">2.5</ns2:draft><ns2:LOA units="feet">33</ns2:LOA><ns2:hullID>S3002</ns2:hullID></ns1:vessel><ns1:vessel><ns2:draft units="feet">6</ns2:draft><ns2:LOA units="feet">57</ns2:LOA><ns2:hullID>S5401</ns2:hullID></ns1:vessel><ns1:comments/><ns1:discussion>All data for survey H13023 was acquired by S3002 and S5401.  The vessels acquired multibeam depth soundings, backscatter data, sound speed profiles, and bottom samples.</ns1:discussion></ns1:vessels><ns1:comments/><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:comments/><ns1:majorSystem><ns2:type>Positioning and Attitude System</ns2:type><ns2:manufacturer>Applanix</ns2:manufacturer><ns2:model>POS M/V V5</ns2:model></ns1:majorSystem><ns1:majorSystem><ns2:type>Sound Speed System</ns2:type><ns2:manufacturer>AML</ns2:manufacturer><ns2:model>Micro X</ns2:model></ns1:majorSystem><ns1:majorSystem><ns2:type>MBES</ns2:type><ns2:manufacturer>Kongsberg</ns2:manufacturer><ns2:model>EM3002</ns2:model></ns1:majorSystem><ns1:majorSystem><ns2:type>Conductivity, Temperature, and Depth Sensor</ns2:type><ns2:manufacturer>SonTek</ns2:manufacturer><ns2:model>Castaway-CTD</ns2:model></ns1:majorSystem><ns1:majorSystem><ns2:type>Positioning System</ns2:type><ns2:manufacturer>Trimble</ns2:manufacturer><ns2:model>SPS361</ns2:model></ns1:majorSystem><ns1:majorSystem><ns2:type>Sound Speed System</ns2:type><ns2:manufacturer>Valeport</ns2:manufacturer><ns2:model>miniSVS</ns2:model></ns1:majorSystem><ns1:majorSystem><ns2:type>MBES</ns2:type><ns2:manufacturer>Kongsberg</ns2:manufacturer><ns2:model>EM 2040</ns2:model></ns1:majorSystem><ns1:discussion xsi:nil="true"></ns1:discussion></ns1:equipment></ns1:equipmentAndVessels></ns1:dataAcquisitionAndProcessing><ns1:resultsAndRecommendations><ns1:chartComparison><ns1:charts><ns2:ENC><ns2:comments/><ns2:chart><ns2:scale>40000</ns2:scale><ns2:name>US5NY40M</ns2:name><ns2:edition>14</ns2:edition><ns2:issueDate>2017-03-08</ns2:issueDate><ns2:preliminary>false</ns2:preliminary><ns2:updateApplicationDate>2016-12-06</ns2:updateApplicationDate></ns2:chart><ns2:images><ns2:link>file:///M:/OPRB396NRT5BH217/Surveys/H13023/Compilation/Report/Components/DR%20pics/Chart%20Comparison%20No%20Soundings%20Bay.PNG</ns2:link><ns2:caption>Bay with no soundings was surveyed.  </ns2:caption></ns2:images><ns2:images><ns2:link>file:///M:/OPRB396NRT5BH217/Surveys/H13023/Compilation/Report/Components/DR%20pics/Chart%20Comparison%20Ferry%20Terminal.PNG</ns2:link><ns2:caption>Ferry terminal with multiple sounding discrepancies.</ns2:caption></ns2:images><ns2:images><ns2:link>file:///M:/OPRB396NRT5BH217/Surveys/H13023/Compilation/Report/Components/DR%20pics/Chart%20Comparison%20charted%2015%20ft.PNG</ns2:link><ns2:caption>Charted 15ft sounding is seven feet different than the H13023 sounding.</ns2:caption></ns2:images><ns2:discussion>H13023 and ENC US5NY40M show general agreement between soundings and contours in most areas.  The largest differences are near the shore on the northwest side of the sheet, where some H13023 soundings are shoaler than charted by around 7-10 feet and the 12ft and 6ft contours are further offshore.  One bay had no charted soundings (see Figure 14), and has charted soundings outside its entrance of 16ft and 13ft, about 7 feet different than H13023 soundings.  A ferry terminal (see Figure 15) has multiple charted soundings that differ by 6 to 10 feet from H13023 soundings, and another sounding further north (Figure 16) differs by 7 feet between the two sets of data.</ns2:discussion></ns2:ENC><ns2:comments/></ns1:charts><ns1:methods><ns2:comments/><ns2:discussion>The chart comparison was made using a CARIS sounding and contour layer derived from a 50cm CUBE surface.  The contours and soundings were overlaid on the chart and compared for general agreement and to identify areas of significant change.</ns2:discussion></ns1:methods><ns1:unchartedFeatures><ns2:comments/><ns2:results investigated="Investigated"><ns2:discussion>Several new features were found and are detailed in the Final Feature File.</ns2:discussion></ns2:results></ns1:unchartedFeatures><ns1:shoalAndHazardousFeatures><ns2:comments><ns2:branchComment concurrence="Do not concur"><ns2:comment>SAR: Though documented in section DR section D1.1, the three Dangers to Navigation submitted on Dec 18th are shoals and hazardous. The chart containing these three shoals have been updated with the surveyed least depths as of May 22, 2018</ns2:comment></ns2:branchComment></ns2:comments><ns2:results investigated="None Exist"><ns2:discussion>No shoals or potentially hazardous features exist for this survey.</ns2:discussion></ns2:results></ns1:shoalAndHazardousFeatures><ns1:channels><ns2:comments/><ns2:results investigated="Investigated"><ns2:discussion>The northern portion of the sheet has a maintained channel.  Soundings from H13023 data found the channel depth to be greater than or equal to the stated channel depth on the chart.</ns2:discussion></ns2:results></ns1:channels><ns1:chartedFeatures><ns2:comments/><ns2:results investigated="Investigated"><ns2:images><ns2:link>file:///M:/OPRB396NRT5BH217/Surveys/H13023/Compilation/Report/Components/DR%20pics/Charted%20Feature%20Rk%20rep.PNG</ns2:link><ns2:caption>Rk rep feature found to be correctly located (Chart 12343_1) .</ns2:caption></ns2:images><ns2:images><ns2:link>file:///M:/OPRB396NRT5BH217/Surveys/H13023/Compilation/Report/Components/DR%20pics/Charted%20Feature%20PD.PNG</ns2:link><ns2:caption>PD feature not seen (Chart 12343_1).</ns2:caption></ns2:images><ns2:discussion>There were two charted features for this survey.  The Rock Reported feature (see Figure 17) was found to be correctly placed and is attributed as part of the Final Feature File.  The Position Doubtful feature, which was assumed to be referencing the charted 11ft shoal (see Figure 18), was not seen in the data and should be removed.  </ns2:discussion></ns2:results></ns1:chartedFeatures><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:bottomSamples><ns2:comments/><ns2:results investigated="Investigated"><ns2:discussion>The field processed backscatter to create mosaics, which were examined to determine areas of similar and different seafloor bottom types.  Nine sample sites were selected and acquired.  While backscatter can't tell the user exactly what the bottom type is, it's ability to differentiate between different bottom types proved successful in selecting bottom sample locations and should be used for future surveys.</ns2:discussion></ns2:results></ns1:bottomSamples></ns1:chartComparison><ns1:additionalResults><ns1:shoreline><ns2:comments/><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.  Of note is a missing picture for Hudson River light 21.  The hydrographer recalls seeing the light, working as intended, and a holiday is associated with the location of the light.  There are some features that were tagged as redundant.  Upon review these features were located by ATONs, and are due to environmental conditions that require the USCG to switch out the equipment during the winter months.  These features were provided to the field units in the CSF and were not removed.  Lastly, there is an obstruction that is missing a VALSOU.  The height of the obstruction was not noted in the field.</ns2:discussion></ns2:results></ns1:shoreline><ns1:ferryRoutesAndTerminals><ns2:comments/><ns2:results investigated="Investigated"><ns2:images><ns2:link>file:///M:/OPRB396NRT5BH217/Surveys/H13023/Compilation/Report/Components/DR%20pics/IMG_20170802_093248.jpg</ns2:link><ns2:caption>Ferry at Haverstraw, NY.</ns2:caption></ns2:images><ns2:discussion>A ferry exists that goes from Haverstraw, NY to Ossining, NY.  The route the ferry takes was observed visually in the field and found online, see http://web.mta.info/mnr/html/raillink/schedules/haverstraw_start.htm.  The route has been attributed in the final feature file.  </ns2:discussion></ns2:results></ns1:ferryRoutesAndTerminals><ns1:ATONS><ns2:comments/><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 to be on station and serving their intended purpose.</ns2:discussion></ns2:results></ns1:ATONS><ns1:abnormalSeafloorEnviroCond><ns2:comments/><ns2:results investigated="None Exist"><ns2:discussion>Abnormal seafloor and/or environmental conditions were not observed for this survey.</ns2:discussion></ns2:results></ns1:abnormalSeafloorEnviroCond><ns1:otherResults><ns2:comments/></ns1:otherResults><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:platforms><ns2:comments/><ns2:results investigated="None Exist"><ns2:discussion>No platforms exist for this survey.</ns2:discussion></ns2:results></ns1:platforms><ns1:constructionOrDredging><ns2:comments/><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></ns1:constructionOrDredging><ns1:submarineFeatures><ns2:comments/><ns2:results investigated="Investigated"><ns2:discussion>A submerged pipe exists by the facility on the west side of the Hudson River.  There are a couple of buoys that warn mariners of dangers nearby.  See the Final Feature File for more details.</ns2:discussion></ns2:results></ns1:submarineFeatures><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: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:insetRecommendation><ns2:comments/><ns2:results recommended="false"><ns2:discussion>No new insets are recommended for this area.</ns2:discussion></ns2:results></ns1:insetRecommendation></ns1:additionalResults></ns1:resultsAndRecommendations></ns1:descriptiveReport>