<?xml version="1.0" encoding="UTF-8"?><ns1:descriptiveReport xmlns:ns1="http://Pydro.com/2014/02/DescriptiveReport" xmlns:ns2="http://Pydro.com/2014/02/AllGlobalTypes" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><ns1:metadata><ns1:projectMetadata><ns2:number>OPR-B370-NRT5-13</ns2:number><ns2:name>Eastern Long Island Sound</ns2:name><ns2:generalLocality>North Shore of Long Island Sound</ns2:generalLocality><ns2:fieldUnit>Navigation Response Team 5</ns2:fieldUnit></ns1:projectMetadata><ns1:registryMetadata><ns2:registryNumber>H12508</ns2:registryNumber><ns2:sheetID>1</ns2:sheetID><ns2:registryInstructions xsi:nil="true"></ns2:registryInstructions><ns2:sublocality>Saybrook Outer Bar to Salt Works Bay</ns2:sublocality><ns2:stateOrTerritory>Connecticut</ns2:stateOrTerritory><ns2:country>United States</ns2:country><ns2:scale>10000</ns2:scale></ns1:registryMetadata><ns1:surveyMetadata><ns2:year>2013</ns2:year><ns2:chiefOfParty>Andrew Clos LTJG</ns2:chiefOfParty><ns2:projectType>Navigable Area</ns2:projectType><ns2:PIDate>2013-05-16</ns2:PIDate><ns2:datesOfSurvey><ns2:start>2013-07-30</ns2:start><ns2:end>2014-05-29</ns2:end></ns2:datesOfSurvey><ns2:equipmentTypes><ns2:soundingEquipment>Multibeam Echo Sounder</ns2:soundingEquipment><ns2:imageryEquipment>Side Scan Sonar</ns2:imageryEquipment><ns2:imageryEquipment>Multibeam Echo Sounder Backscatter</ns2:imageryEquipment></ns2:equipmentTypes><ns2:acquisition><ns2:units>meters</ns2:units></ns2:acquisition><ns2:horizontalCoordinateSystem zone="18">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. Notes in red were generated during office processing. The processing branch concurs with all information and recommendations in the DR unless otherwise noted. Page numbering may be interrupted or non-sequential. All pertinent records for this survey, including the Descriptive Report, are archived at the National Geophysical Data Center (NGDC) and can be retrieved via http://www.ngdc.noaa.gov/.</ns2:branchRemarks></ns2:titlesheetRemarks></ns1:surveyMetadata><ns1:assignment>NOAA</ns1:assignment></ns1:metadata><ns1:areaSurveyed><ns1:areaDescription><ns2:discussion>The survey extends from Saybrook Outer Bar to Saltworks Bay, and to just south of Long Sand Shoal.  In addition, as part of a Dton investigation, the entire length of Long Sand Shoal was developed out to the 30 ft contour on the western end, and the 18 ft contour on the eastern end.</ns2:discussion><ns2:limits><ns2:northWest><ns2:latitude hemisphere="N">41.2730630278</ns2:latitude><ns2:longitude hemisphere="W">72.4767048611</ns2:longitude></ns2:northWest><ns2:southEast><ns2:latitude hemisphere="N">41.2171829167</ns2:latitude><ns2:longitude hemisphere="W">72.3187357778</ns2:longitude></ns2:southEast></ns2:limits><ns2:images><ns2:caption>Area Surveyed</ns2:caption><ns2:link>file:///M:/OPRB370NRT512/Surveys/H12508/Compilation/Report/Components/Figure1%20-%20Area%20Surveyed.png</ns2:link></ns2:images><ns2:comments/></ns1:areaDescription><ns1:surveyLimits><ns2:results deviation="true"><ns2:discussion>During data acquisition it was discovered that Long Sand Shoal had shifted significantly from what was depicted on the chart.  In some places depths had changed by over 30 ft.  Long Sand Shoal extends past both the west and east limits of the survey sheet. The entire shoal was developed, and submitted as a Dton.</ns2:discussion></ns2:results><ns2:comments/></ns1:surveyLimits><ns1:surveyPurpose><ns2:discussion>This project is being conducted in support of NOAA's Office of Coast Survey to provide contemporary hydrographic data in order to update the nautical charting products and reduce the survey backlog within the area. In addition, data from this project will support the Long Island Sound Seafloor Mapping Initiative in New York and Connecticut.</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:results deviation="true"><ns2:discussion>The portions of  Long Sand shoal lying outside the sheet boundaries were developed as part of a Dton investigation.  Because of the shallow depth, and large extent of the shoal, it was not practical to develop the shoal to Object Detection Standards.  MBES lines were run perpendicular to the shoal to develop the general locations of the contours.  The line spacing chosen by the hydrographer was felt to be adequate to delineate the hazards of the shoal for the purpose of the Dton report, but was not intended to meet any HSSD coverage specification.  

Inside the sheet boundaries, the planned 200% SSS with concurrent MBES lines were acquired over part of the shoal, however, in some areas it was felt unsafe to proceed further with the towfish, so there are some gaps in coverage within the survey limits.</ns2:discussion></ns2:results><ns2:comments/></ns1:surveyCoverage><ns1:coverageGraphic><ns2:caption>Coverage Graphic</ns2:caption><ns2:link>file:///M:/OPRB370NRT512/Surveys/H12508/Compilation/Report/Components/Figure2%20-%20Coverage.png</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>0</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>433.23</ns2:MS_MBES_SSS><ns2:MS_SBES_SSS>0</ns2:MS_SBES_SSS><ns2:XL_MBES_SBES>27.79</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>0</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>433.23</ns2:MS_MBES_SSS><ns2:MS_SBES_SSS>0</ns2:MS_SBES_SSS><ns2:XL_MBES_SBES>27.79</ns2:XL_MBES_SBES><ns2:XL_lidar>0</ns2:XL_lidar><ns2:percentXLLNM>6.4</ns2:percentXLLNM></ns2:totalLNM></ns2:LNM><ns2:totalSurveyStats><ns2:bottomSamples>21</ns2:bottomSamples><ns2:AWOIS>1</ns2:AWOIS><ns2:maritimeBoundaryPoints>0</ns2:maritimeBoundaryPoints><ns2:DP>0</ns2:DP><ns2:diveOps>0</ns2:diveOps><ns2:SNM>9.87</ns2:SNM></ns2:totalSurveyStats><ns2:surveyDates>2013-07-30</ns2:surveyDates><ns2:surveyDates>2013-07-31</ns2:surveyDates><ns2:surveyDates>2013-08-05</ns2:surveyDates><ns2:surveyDates>2013-08-06</ns2:surveyDates><ns2:surveyDates>2013-08-12</ns2:surveyDates><ns2:surveyDates>2013-08-13</ns2:surveyDates><ns2:surveyDates>2013-08-19</ns2:surveyDates><ns2:surveyDates>2013-08-21</ns2:surveyDates><ns2:surveyDates>2013-08-28</ns2:surveyDates><ns2:surveyDates>2013-09-03</ns2:surveyDates><ns2:surveyDates>2013-09-04</ns2:surveyDates><ns2:surveyDates>2013-09-09</ns2:surveyDates><ns2:surveyDates>2013-09-16</ns2:surveyDates><ns2:surveyDates>2013-09-18</ns2:surveyDates><ns2:surveyDates>2013-09-20</ns2:surveyDates><ns2:surveyDates>2013-11-20</ns2:surveyDates><ns2:surveyDates>2014-05-29</ns2:surveyDates><ns2:discussion xsi:nil="true"></ns2:discussion><ns2:comments><ns2:branchComment concurrence="Do not concur"><ns2:comment>382.95 LNM of Mainscheme MS MBES/SSS Combo, 33.82 LNM of MBES/SBES Crosslines and 137.31 LNM of Mainscheme MBES (developments) were calculated during office processing.  Crosslines totaled 8.8% of mainscheme.</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">30</ns2:LOA><ns2:draft units="meters">1</ns2:draft></ns1:vessel><ns1:images><ns2:caption>S3002</ns2:caption><ns2:link>file:///M:/OPRB370NRT512/Surveys/H12508/Compilation/Report/Components/Figure3%20-%20S3002.png</ns2:link></ns1:images><ns1:discussion xsi:nil="true"></ns1:discussion><ns1:comments/></ns1:vessels><ns1:equipment><ns1:majorSystem><ns2:manufacturer>Applanix</ns2:manufacturer><ns2:model>Pos MV v4</ns2:model><ns2:type>Positioning and Attitude System</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>Trimble</ns2:manufacturer><ns2:model>DSM 212</ns2:model><ns2:type>Positioning System</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>Kongsberg</ns2:manufacturer><ns2:model>EM3002</ns2:model><ns2:type>MBES</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>Edgetech</ns2:manufacturer><ns2:model>4125</ns2:model><ns2:type>SSS</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>Digibar</ns2:manufacturer><ns2:model>Digibar Pro</ns2:model><ns2:type>Sound Speed System</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>Seabird</ns2:manufacturer><ns2:model>19 Plus</ns2:model><ns2:type>Conductivity, Temperature, and Depth Sensor</ns2:type></ns1:majorSystem><ns1:discussion xsi:nil="true"></ns1:discussion><ns1:comments/></ns1:equipment><ns1:comments/></ns1:equipmentAndVessels><ns1:qualityControl><ns1:crosslines><ns2:discussion>27.8 nautical miles of crosslines were acquired, which amounts to 6.4% of mainscheme mileage.  The 8% required for set line spacing was not achieved because the crosslines were planned based on the planned mainscheme lines.  During the course of the survey, however, many miles of developments were acquired which caused the percentage to fall below the target of 8%.  Overall, the mainscheme/crossline agreement is good, however, there are some intersections that have a noticeable vertical shift.  The crossline/mainscheme agreement was evaluated by creating a base surface using mainscheme lines only.  A Caris QC report was then generated, comparing the crossline data to the reference surface.  Beam-by-beam statistics were computed.  The standard deviation of the crosslines beams with respect to the mainscheme reference surface shows the expected curve, with standard deviation increasing as the beams move away from nadir.  The standard deviations indicate that the sounding TVU fall well within IHO Order 1a uncertainty requirements.  A plot of the beam-by-beam mean values shows an even scattering around a zero mean, except for an increasing trend in the outer beams on the starboard side.  The reason for this is not known, however, the largest deviation is less than three centimeters.  Additionally, a difference surface was created between the mainscheme-only surface, and the crossline-only surface.  The Caris surface statistics tool was used, and showed the difference surface had a mean value of 0.0, and a standard deviation of .11 meters.  Overall, the crossline analysis indicates good data quality, and vertical sounding uncertainty falling well within IHO order 1a requirements.

Some of the crossline/mainscheme junctions show a vertical offset upto around 15 cm.  Analysis of the data suggests that these are tide artifacts.  Offsets of similiar magnitude can be seen between adjacent mainscheme lines that were collected on different days.  It is possible that there are local dynamic tidal effects caused by the presense of Long Sand Shoal that are not adequately modeled in the TCARI grid.  Local wind setup not measured by the controlling tide gauges is another possible cause.</ns2:discussion><ns2:images><ns2:caption>Crosslines</ns2:caption><ns2:link>file:///M:/OPRB370NRT512/Surveys/H12508/Compilation/Report/Components/Figure4%20-%20Crosslines.png</ns2:link></ns2:images><ns2:images><ns2:caption>Beam-by-beam Standard Deviation</ns2:caption><ns2:link>file:///M:/OPRB370NRT512/Surveys/H12508/Compilation/Report/Components/Figure5%20-%20BeambyBeam%20StDev.png</ns2:link></ns2:images><ns2:images><ns2:caption>Beam-by-beam Mean Difference</ns2:caption><ns2:link>file:///M:/OPRB370NRT512/Surveys/H12508/Compilation/Report/Components/Figure6%20-%20BeambyBeam%20Mean%20Diff.png</ns2:link></ns2:images><ns2:images><ns2:caption>Surface statistics of Mainscheme/Crossline Difference Surface.</ns2:caption><ns2:link>file:///M:/OPRB370NRT512/Surveys/H12508/Compilation/Report/Components/Figure7%20-%20Main%20Cross%20Diff.png</ns2:link></ns2:images><ns2:comments><ns2:branchComment concurrence="Comment Only"><ns2:comment>Crosslines totaled 8.8% of the mainscheme lines, which meets the 8% requirement for set line spacing multibeam.  The crosslines obtained have excellent geographic distribution and compared favorably to the mainscheme lines with differences falling within vertical error budgets.

NOAA does not use IHO uncertainty standards.  Where the field references IHO standards, the statement should be amended to read &quot;TVU falls within NOAA's &quot;Complete Coverage&quot; vertical uncertainty budgets as assigned for this survey.&quot;</ns2:comment></ns2:branchComment></ns2:comments></ns1:crosslines><ns1:uncertainty><ns2:values/><ns2:discussion>An IHO layer was created for the CUBE surfaces to highlight nodes where the IHO TVU was exceeded.  For all surfaces, less than 1% of nodes failed to meet IHO Order 1a TVU requirements.</ns2:discussion><ns2:comments/></ns1:uncertainty><ns1:junctions><ns2:discussion>BAGs from the most recent adjacent surveys were downloaded from NGDC.  Difference surfaces were created, and statistics were computed using the Caris &quot;Compute Statistics&quot; tool.  The results of each comparison are discussed below.</ns2:discussion><ns2:junction><ns2:survey><ns2:registryNumber>H11361</ns2:registryNumber><ns2:scale>10000</ns2:scale><ns2:year>2004</ns2:year><ns2:fieldUnit>NOAA Ship THOMAS JEFFERSON</ns2:fieldUnit><ns2:relativeLocation>SW</ns2:relativeLocation></ns2:survey><ns2:discussion>Data agreement was best for H11361, although it was the oldest survey junction analyzed.  The mean difference was less than 1 cm, with a standard deviation of 20 cm.  The good agreement is likely due the area being deeper, and less dynamic.  The other two junctions are in dynamic areas with significant sand wave formations, which makes a meaningful comparison difficult.</ns2:discussion><ns2:images><ns2:caption>H11361</ns2:caption><ns2:link>file:///M:/OPRB370NRT512/Surveys/H12508/Compilation/Report/Components/Figure8%20-%20H11361%20Junction.png</ns2:link></ns2:images><ns2:comments/></ns2:junction><ns2:junction><ns2:survey><ns2:registryNumber>H12012</ns2:registryNumber><ns2:scale>10000</ns2:scale><ns2:year>2009</ns2:year><ns2:fieldUnit>NOAA Ship THOMAS JEFFERSON</ns2:fieldUnit><ns2:relativeLocation>S</ns2:relativeLocation></ns2:survey><ns2:discussion>The mean difference between H12508 and H12012 in the area of overlap is .1 meters.  The standard deviation is .6 meters.  There are extensive sandwaves in this area, making a meaningful comparison difficult.   Significant sandwave movement was observed within the time span of data acquisition for H12508.
</ns2:discussion><ns2:images><ns2:caption>H12012</ns2:caption><ns2:link>file:///M:/OPRB370NRT512/Surveys/H12508/Compilation/Report/Components/Figure9%20-%20H12012%20Junction.png</ns2:link></ns2:images><ns2:comments/></ns2:junction><ns2:junction><ns2:survey><ns2:registryNumber>H12013</ns2:registryNumber><ns2:scale>10000</ns2:scale><ns2:year>2009</ns2:year><ns2:fieldUnit>NOAA Ship THOMAS JEFFERSON</ns2:fieldUnit><ns2:relativeLocation>E</ns2:relativeLocation></ns2:survey><ns2:discussion>The mean difference between H12508 and H12013 in the area of overlap is .2 meters.  The standard deviation is .8 meters.  There are extensive sandwaves in this area, making a meaningful comparison difficult.  Significant sandwave movement was observed within the time span of data acquisition for H12508.
</ns2:discussion><ns2:images><ns2:caption>H12013</ns2:caption><ns2:link>file:///M:/OPRB370NRT512/Surveys/H12508/Compilation/Report/Components/Figure10%20-%20H12013%20Junction.png</ns2:link></ns2:images><ns2:comments/></ns2:junction><ns2:comments/></ns1:junctions><ns1:sonarQCChecks><ns2:results deviation="false"><ns2:discussion>Sonar system quality control checks were conducted as detailed in the quality control section of the DAPR.</ns2:discussion></ns2:results><ns2:comments/></ns1:sonarQCChecks><ns1:equipmentEffectiveness><ns2:results deviation="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 hours in the deepest area being surveyed at the time.</ns1:castFrequency><ns1:discussion xsi:nil="true"></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><ns2:branchComment concurrence="Do not concur"><ns2:comment>The static offsets from the RP to the transducer in the DAPR don't match the HVF.  The X and Y offset values are reversed from what is shown in the HVF (both in SVP 1 and TPU Offsets) and the Z value is listed as negative in the DAPR, but positive for all entries in the HVF.  The dynamic draft table reported in the DAPR is from 2012 and does not match any of the latest speed or draft values in the HVF which are from 2013 DN 176.  Also, the values reported in the DAPR don't match any of the other entries in the HVF which date back to 2008.  The data quality does not appear to be affected by these inconsistencies, which appear to be simple documentation errors.</ns2:comment></ns2:branchComment></ns2:comments></ns1:coverageEquipmentAndMethods><ns1:additionalQualityControl><ns2:issue><ns2:title>Gaps in along-track MBES Coverage.</ns2:title><ns2:discussion>After MBES acquisition was complete, it was noticed there several small along-track holidays existed in the MBES data.  After some analysis, it was determined that the gaps were caused by the SIS acquisition software automatically breaking, and beginning a new file mid-line.  It appears that the file size was limited to 30 minutes of acquisition.  When this was exceeded, SIS would end the file and create a new file.  During the transition, a few seconds of data were lost, resulting in a holiday.  This limit seemed to be related to acquisition time, rather than file size.  All of these holidays fall within continuous 200% SSS coverage, and after review, the hydrograher is confident no significant features were missed.</ns2:discussion><ns2:comments/></ns2:issue><ns2:comments/></ns1:additionalQualityControl></ns1:qualityControl><ns1:echoSoundingCorrections><ns1:corrections><ns2:results deviation="true"><ns2:discussion>Problems were encountered with the logging and application of TrueHeave files.  Due to frequent crashing of the acquisition computer, and consequently the TrueHeave file logging being cut short, it was not possible to apply TrueHeave to several MBES lines.  Realtime heave was used for these lines instead.  The files affected are listed below:

0038_20130730_202515_S3002.all
0095_20130805_161722_S3002.all
0099_20130805_182659_S3002.all
0099_20130805_175953_S3002.all
0218_20130819_200537_S3002.all
0286_20130903_153248_S3002.all</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 as part of the Kongsberg .all file. The backcatter was converted, and a mosaic was created as a QC  check, but no additional processing was performed.</ns2:discussion></ns2:results><ns2:comments/></ns1:backscatter><ns1:dataProcessing><ns1:softwareUpdates><ns1:featureObjectCatalog>NOAA Profile V_5_3</ns1:featureObjectCatalog><ns1:discussion xsi:nil="true"></ns1:discussion><ns1:comments/></ns1:softwareUpdates><ns1:surfaces><ns1:surface><ns2:surfaceName>H12508_1m</ns2:surfaceName><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:resolution units="meters">1</ns2:resolution><ns2:depthRange><ns2:min xsi:nil="true"/><ns2:max xsi:nil="true"/></ns2:depthRange><ns2:surfaceParameter>NOAA_1m</ns2:surfaceParameter><ns2:purpose>MBES TracklineSBES Set Line Spacing</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceName>H12508_1m_Final</ns2:surfaceName><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:resolution units="meters">1</ns2:resolution><ns2:depthRange><ns2:min units="meters">0</ns2:min><ns2:max units="meters">20</ns2:max></ns2:depthRange><ns2:surfaceParameter>NOAA_1m</ns2:surfaceParameter><ns2:purpose>MBES TracklineSBES Set Line Spacing</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceName>H12508_2m</ns2:surfaceName><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:resolution units="meters">2</ns2:resolution><ns2:depthRange><ns2:min xsi:nil="true"/><ns2:max xsi:nil="true"/></ns2:depthRange><ns2:surfaceParameter>NOAA_2m</ns2:surfaceParameter><ns2:purpose>MBES TracklineSBES Set Line Spacing</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceName>H12508_2m_Final</ns2:surfaceName><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:resolution units="meters">2</ns2:resolution><ns2:depthRange><ns2:min units="meters">18</ns2:min><ns2:max units="meters">40</ns2:max></ns2:depthRange><ns2:surfaceParameter>NOAA_2m</ns2:surfaceParameter><ns2:purpose>MBES TracklineSBES Set Line Spacing</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceName>H12508_50cm</ns2:surfaceName><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:resolution units="meters">0.5</ns2:resolution><ns2:depthRange><ns2:min xsi:nil="true"/><ns2:max xsi:nil="true"/></ns2:depthRange><ns2:surfaceParameter>NOAA_0.5m</ns2:surfaceParameter><ns2:purpose>MBES TracklineSBES Set Line Spacing</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceName>H12508_SSS_Mosaic_100</ns2:surfaceName><ns2:surfaceType>SSS Mosaic</ns2:surfaceType><ns2:resolution units="meters">1</ns2:resolution><ns2:depthRange><ns2:min xsi:nil="true"/><ns2:max xsi:nil="true"/></ns2:depthRange><ns2:surfaceParameter>N/A</ns2:surfaceParameter><ns2:purpose>100% SSS</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceName>H12508_SSS_Mosaic_200</ns2:surfaceName><ns2:surfaceType>SSS Mosaic</ns2:surfaceType><ns2:resolution units="meters">1</ns2:resolution><ns2:depthRange><ns2:min xsi:nil="true"/><ns2:max xsi:nil="true"/></ns2:depthRange><ns2:surfaceParameter>N/A</ns2:surfaceParameter><ns2:purpose>200% SSS</ns2:purpose></ns1:surface><ns1:discussion>Per HSSD 5.2.2.3, only a four meter grid is required, however, the sounding density easily supports Complete Coverage gridding requirements. Therefore, one and two meter surfaces are being submitted.  A 50 cm grid, H12508_50cm, is also being submitted, but is not intended to fulfill any submission requirement.</ns1:discussion><ns1:comments><ns2:branchComment concurrence="Concur with clarification"><ns2:comment>The 50cm grid was required for the AWOIS investigation as stated in the Project Instructions.</ns2:comment></ns2:branchComment></ns1:comments></ns1:surfaces><ns1:additionalDataProcessing><ns2:comments/></ns1:additionalDataProcessing></ns1:dataProcessing></ns1:dataAcquisitionAndProcessing><ns1:verticalAndHorizontalControl><ns1:discussion>No HorCon or VerCon operations were required for this survey.</ns1:discussion><ns1:verticalControl><ns2:verticalDatum>Mean Lower Low Water</ns2:verticalDatum><ns2:standard_or_ERZT used="true"><ns2:methodsUsed>TCARI</ns2:methodsUsed><ns2:tideStations><ns2:NWLONGauges><ns2:stationName>New London</ns2:stationName><ns2:stationID>8461490</ns2:stationID></ns2:NWLONGauges><ns2:NWLONGauges><ns2:stationName>New Haven</ns2:stationName><ns2:stationID>8465705</ns2:stationID></ns2:NWLONGauges></ns2:tideStations><ns2:correctorFiles><ns2:tideCorrectors><ns2:fileName>B370NRT52013.tc</ns2:fileName><ns2:status>Final</ns2:status></ns2:tideCorrectors></ns2:correctorFiles><ns2:finalTides><ns2:dateSubmitted>2014-06-30</ns2:dateSubmitted><ns2:dateReceived>2014-07-17</ns2:dateReceived></ns2:finalTides><ns2:discussion xsi:nil="true"></ns2:discussion><ns2:comments/></ns2:standard_or_ERZT><ns2:VDATUM_or_constantSep used="false"><ns2:discussion xsi:nil="true"></ns2:discussion><ns2:comments/></ns2:VDATUM_or_constantSep><ns2:comments><ns2:branchComment concurrence="Comment Only"><ns2:comment>The Tide Note is attached.</ns2:comment></ns2:branchComment></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="false" xsi:nil="true"/><ns2:PPP used="false" xsi:nil="true"/><ns2:RTK used="false" xsi:nil="true"/><ns2:DGPS used="true"><ns2:USCGStations><ns2:name>Moriches, NY 293 kHz</ns2:name></ns2:USCGStations><ns2:discussion>The Moriches, NY beacon was manually selected in the Trimble DSM212, it was not changed during the project.</ns2:discussion><ns2:comments/></ns2:DGPS><ns2:comments/></ns1:horizontalControl><ns1:additionalIssues><ns2:comments/></ns1:additionalIssues></ns1:verticalAndHorizontalControl><ns1:resultsAndRecommendations><ns1:chartComparison><ns1:methods><ns2:discussion>The chart comparisons were performed using multiple methods.  For each charted contour, the base surface generated  by the survey was filtered to only show areas shallower than that contour.  Doing so highlights areas where contours have shifted significantly, and isolated shoals.  Shoal biased selected sounding layers were also created, and carefully compared to charted soundings to identify areas with depths that would be unexpected by the mariner based on charted depths.</ns2:discussion><ns2:comments/></ns1:methods><ns1:charts><ns2:rasterChart><ns2:chart><ns2:number>12374</ns2:number><ns2:kapp>2162</ns2:kapp><ns2:scale>20000</ns2:scale><ns2:edition>1</ns2:edition><ns2:editionDate>2007-09</ns2:editionDate><ns2:LNMDate>2014-01-28</ns2:LNMDate><ns2:NMDate>2014-02-01</ns2:NMDate></ns2:chart><ns2:discussion>The only survey data lying within the bounds of chart 12374 are the western portions of the Long Sand Shoal Dton investigation.  Long Sand Shoal had shifted, resulting in significant disagreement with charted soundings.  There were depths of less than 25 ft, 150 meters seaward of the charted 30 ft contour.  There are discrepancies of similar magnitude with the 18 ft contour.  At the time of this chart comparison, however, the data from the Dton investigation had been applied to the chart, so the discrepancies do not exist in the most recent chart version.</ns2:discussion><ns2:comments/></ns2:rasterChart><ns2:rasterChart><ns2:chart><ns2:number>12375</ns2:number><ns2:kapp>2161</ns2:kapp><ns2:scale>20000</ns2:scale><ns2:edition>1</ns2:edition><ns2:editionDate>2010-10</ns2:editionDate><ns2:LNMDate>2014-01-28</ns2:LNMDate><ns2:NMDate>2014-02-08</ns2:NMDate></ns2:chart><ns2:discussion>Long Sand Shoal is one of the most prominent features on chart 12375.  During the course of the survey the shoal was found to have shifted significantly, especially in the western portions.  The entire shoal was developed out to the 30 ft contour, and submitted as a DTON.  The most current version of chart 12375 has had the DTON survey data applied, but only in the western portion of Long Sand Shoal.  West of 72-22-23.03W, the contours and soundings are based on the new survey data, and so agree almost perfectly.  East of 72-22-23.03W where the discrepancies were not as large, however, the chart does not appear to have been updated.  Here the survey data shows that the contours have shifted seaward up to 60 meters in some places.

On the western portion of the survey area, between Long Sand Shoal and the Hen and Chickens, there are several uncharted rocky shoals with depths significantly shoaler than the charted depths.  Two of the most navigationally significant shoals were submitted as DTONs, and have already been applied to the chart, but there are several others that deserve attention.  They are discussed in the Shoals and Hazardous Features section.</ns2:discussion><ns2:comments><ns2:branchComment concurrence="Comment Only"><ns2:comment>A very small area in the southern portion of the survey also falls on Chart 12372_11, Scale 1:40,000. 

Three additional shoals and one submerged rock were submitted as DTONs during the SAR. </ns2:comment></ns2:branchComment></ns2:comments></ns2:rasterChart><ns2:ENC><ns2:chart><ns2:name>US5CN16M</ns2:name><ns2:scale>20000</ns2:scale><ns2:edition>8</ns2:edition><ns2:updateApplicationDate>2013-10-03</ns2:updateApplicationDate><ns2:issueDate>2013-10-03</ns2:issueDate><ns2:preliminary>false</ns2:preliminary></ns2:chart><ns2:discussion>Comparing US5CN16M to raster chart 12374, it was noticed that there are some discrepancies in the placement of depth contours around the western end of Long Sand Shoal.  Although, the contours and depths appear to have been updated to include the submitted DTON, there are some small deviations from the raster.</ns2:discussion><ns2:comments/></ns2:ENC><ns2:ENC><ns2:chart><ns2:name>US5CN30M</ns2:name><ns2:scale>20000</ns2:scale><ns2:edition>11</ns2:edition><ns2:updateApplicationDate>2014-01-27</ns2:updateApplicationDate><ns2:issueDate>2014-01-27</ns2:issueDate><ns2:preliminary>false</ns2:preliminary></ns2:chart><ns2:discussion>US5CN30M was compared to the raster chart 12375.  Aside from some very slight differences in contour position, no discrepancies were found.</ns2:discussion><ns2:comments><ns2:branchComment concurrence="Comment Only"><ns2:comment>A very small area in the southern portion of the survey also falls on ENC US5CN20M, Scale 1:40,000. </ns2:comment></ns2:branchComment></ns2:comments></ns2:ENC><ns2:comments/></ns1:charts><ns1:AWOISItems><ns2:results investigated="Investigated"><ns2:discussion>A single AWOIS item, # 6818, was assigned inside the survey area - The wreck of the James Sheridan.  The wreck was fully developed with MBES.  The charted position of the wreck is accurate.  The least depth measured by the current survey was slightly deeper than the charted depth of the wreck, so it is recommend to retain the wreck as it is presently charted.</ns2:discussion></ns2:results><ns2:comments><ns2:branchComment concurrence="Concur with clarification"><ns2:comment>The wreck position was updated to the surveyed position; however the charted least depth was retained.</ns2:comment></ns2:branchComment></ns2:comments></ns1:AWOISItems><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>A Position Approximate wreck is charted at 41-13-54.244N, 72-20-53.625W.  The area surrounding the charted position of the wreck was developed with MBES.  No signs of the wreck were visible in the MBES data.  It is recommended for deletion.</ns2:discussion></ns2:results><ns2:comments/></ns1:chartedFeatures><ns1:unchartedFeatures><ns2:results investigated="Investigated"><ns2:discussion>Within the survey area, one wreck, two submerged rocks, and one obstruction were recommended for charting.

There is an uncharted wreck at 41-15-43.377N, 72-20-41.016W near the entrance to Saybrook Outer Bar Channel.  Possibly a sunken barge.

The two submerged rocks were submitted as Dtons.

One pile-like obstruction was recommended for charting at 41-13-45.219N, 72-22-37.481W.


Note:

This survey area contains numerous uncharted rocks and rocky shoals that meet the HSSD criteria for significant features.  The Pacific Hydrographic Branch was consulted, and at their direction no natural features, including significant rocks and rocky shoals, were included in the Final Features File.  Every significant feature was carefully reviewed to ensure that it was adequately developed, and that its least depth was accurately represented in the BASE surface.  However, only features appearing to be man made obstructions, or those which were determined to be Dtons, were recommended for charting, and included in the Final Features File.</ns2:discussion></ns2:results><ns2:comments/></ns1:unchartedFeatures><ns1:DTONS><ns2:results reportSubmitted="true"><ns2:numberSubmitted>2</ns2:numberSubmitted><ns2:report><ns2:title>H12508_Dton_1</ns2:title><ns2:dateSubmitted>2013-08-26</ns2:dateSubmitted></ns2:report><ns2:report><ns2:title>H12508_Dton_2</ns2:title><ns2:dateSubmitted>2014-01-14</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="Comment Only"><ns2:comment>Three additional shoals and one submerged rock were submitted as DTONs during office review. The DTON Report is attached.</ns2:comment></ns2:branchComment></ns2:comments></ns1:DTONS><ns1:shoalAndHazardousFeatures><ns2:results investigated="Investigated"><ns2:discussion> On the western portion of the survey area, between Long Sand Shoal and the Hen and Chickens, there are several uncharted rocky shoals with depths significantly shoaler than the charted depths.  Two of the most navigationally significant shoals were submitted as Dtons, and have already been applied to the chart, but there are several others that deserve attention: 

At 41-14-18.49N, 72-24-37.49W, there is an uncharted rocky shoal with a least depth of 27 ft under a charted 32 ft sounding.  
At 41-14-19.71N, 72-24-15.30W, there is an uncharted rocky shoal with a least depth of 28 ft under a charted 36 ft sounding.  
At 41-14-41.61N, 72-24-16.59W, there is an uncharted rocky shoal with a least depth of 30 ft under a charted 38 ft sounding.

Between the Hen and Chickens and Halftide Rock, there are several uncharted rocky shoals:

At 41-15-31.08N, 72-24-22.44W, there is an uncharted rocky shoal with a least depth of 22 ft near a charted 37 ft sounding.  
At 41-15-29.71N, 72-24-31.83W, there is an uncharted rocky shoal with a least depth of 26 ft seaward of the 30 ft contour.  The closest charted sounding is 33 ft.  
At 41-15-26.06N, 72-24-41.27W, there is an uncharted rocky shoal with a least depth of 29 ft, seaward of the 30 ft contour, and near a charted 34 ft sounding.  
At 41-15-19.97N, 72-24-18.72W, there is an uncharted rocky shoal with a least depth of 15 ft 120 meters seaward of the 18 ft curve.

On the north side of Halftide Rock the contours do not accurately depict the shoal.  Rocky shoaling with a least depth of 8 ft extends 50 meters seaward of the 18 ft curve.

Between Cornfield Pt Shoal and red buoy &quot;2&quot;, there is a charted shoal, with least depth of 29 ft.  The surveyed least depth on this shoal is 18 ft. 

At 41-15-21.87N 72-22-40.90W, there is an uncharted rocky shoal with a least depth of 24 ft seaward of the 30 ft contour.

Southeast of Old Kelsey Pt, there is an uncharted submerged rock with a least depth of 11 ft near a charted 15 ft sounding.
</ns2:discussion></ns2:results><ns2:comments/></ns1:shoalAndHazardousFeatures><ns1:channels><ns2:results investigated="None Exist"><ns2:discussion>No channels exist for this survey.  There are no designated anchorages, precautionary areas, safety fairways, traffic separation schemes, pilot boarding areas, or channel and range lines within the survey limits.</ns2:discussion></ns2:results><ns2:comments/></ns1:channels><ns1:bottomSamples><ns2:results investigated="Investigated"><ns2:discussion>Twenty-one bottom samples were acquired during the survey.  The samples were taken with a clamshell style bottom sampler.  The bottom type samples were classified, photographed, and then discarded back into the water.  The positions of the samples were captured with Hypack targets.</ns2:discussion></ns2:results><ns2:comments/></ns1:bottomSamples></ns1:chartComparison><ns1:additionalResults><ns1:shoreline><ns2:results investigated="Investigated"><ns2:discussion>Two assigned shoreline features exist within the survey limits, Hen and Chickens Rock, and Halftide Rock.  MBES was acquired around the exposed rocks as close as was considered safe.  No Detached Positions were taken.  The positions of both rocks are accurately charted.</ns2:discussion><ns2:images><ns2:caption>Shoreline Features</ns2:caption><ns2:link>file:///M:/OPRB370NRT512/Surveys/H12508/Compilation/Report/Components/Figure11%20-%20Shoreline%20Features.png</ns2:link></ns2:images></ns2:results><ns2:comments><ns2:branchComment concurrence="Concur with clarification"><ns2:comment>There were three assigned features in the survey limits.  The AWOIS item discussed in Section D.1.3 is the third.</ns2:comment></ns2:branchComment></ns2:comments></ns1:shoreline><ns1:priorSurveys><ns2:results investigated="Exist - Not Investigated"><ns2:discussion>Prior survey comparisons exist for this survey, but were not investigated.</ns2:discussion></ns2:results><ns2:comments/></ns1:priorSurveys><ns1:ATONS><ns2:results investigated="Investigated"><ns2:discussion>All Atons in the survey area appeard to be on station, and serving their intended purpose.</ns2:discussion></ns2:results><ns2:comments/></ns1:ATONS><ns1:overheadFeatures><ns2:results investigated="None Exist"><ns2:discussion>No overhead features exist for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:overheadFeatures><ns1:submarineFeatures><ns2:results investigated="None Exist"><ns2:discussion>No submarine features exist for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:submarineFeatures><ns1:ferryRoutesAndTerminals><ns2:results investigated="Exist - Not Investigated"><ns2:discussion>A ferry route exists between Saybrook Point in Old Saybrook, and Plum Island, but was not investigated.</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="Investigated"><ns2:discussion>Sand waves are a prominent feature in this survey area.  Five  meter high sandwaves exist in the southwest portion of the survey area, south of Long Sand Shoal.  Smaller sandwaves exist north of the shoal.  It is interesting to note that the direction of sandwave propogation appears to change in different parts of the survey area.  On the western portion of the survey area, north of Long Sand Shoal, the sand waves appear to be developing from a west-to-east current, and just south of Long Sand Shoal, the direction seems to reverse, the sandwaves appearing to be created by an east-to-west current.  The sandwaves in the eastern portion of the survey area, north of Long Sand Shoal, have a symetrical shape, and do not suggest a prevailing current direction.  In some areas, the sandwaves appear to be propogating quickly.  Movement of up to 10 meters can be seen by comparing survey lines acquired on different days.

Moderate tide artifacts were observed on some survey days.  It is likely that Long Sand Shoal creates a tidal and current dynamic in the area that is not accounted for in the TCARI grid.</ns2:discussion></ns2:results><ns2:comments/></ns1:significantFeatures><ns1:constructionOrDredging><ns2:results investigated="None Exist"><ns2:discussion>No present or planned construction or dredging exist within the survey limits.</ns2:discussion></ns2:results><ns2:comments/></ns1:constructionOrDredging><ns1:otherResults><ns2:issue><ns2:title>Recommendation for priortiy processing</ns2:title><ns2:discussion>Although the most dangerous and navigationally significant features have been submitted as Dtons, many more uncharted shoals and chart discrepancies exist within the survey area.  The hydrographer recommends that this survey be given priortiy in the processing queue, to hasten the new survey data reaching the chart.</ns2:discussion><ns2:comments/></ns2:issue><ns2:comments/></ns1:otherResults><ns1:newSurveyRecommendation><ns2:results recommended="false"><ns2:discussion>No new surveys or further investigations are recommended for this area.</ns2:discussion></ns2:results><ns2:comments/></ns1:newSurveyRecommendation><ns1:insetRecommendation><ns2:results recommended="false"><ns2:discussion>No new insets are recommended for this area.</ns2:discussion></ns2:results><ns2:comments/></ns1:insetRecommendation></ns1:additionalResults></ns1:resultsAndRecommendations><ns1:approvalSheet><ns1:statements><ns1:supervision>As Chief of Party, Field operations for this hydrographic survey were conducted under my direct supervision, with frequent personal checks of progress and adequacy. 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>LTJG Andrew Clos</ns2:approverName><ns2:approverTitle>Chief of Party</ns2:approverTitle><ns2:approvalDate>2014-11-24</ns2:approvalDate></ns1:signingPersonnel><ns1:additionalReports><ns2:reportName>Data Acquisition and Processing Report</ns2:reportName><ns2:reportDateSent>2014-11-24</ns2:reportDateSent></ns1:additionalReports><ns1:additionalReports><ns2:reportName>Coast Pilot Report</ns2:reportName><ns2:reportDateSent>2014-11-24</ns2:reportDateSent></ns1:additionalReports></ns1:approvalSheet></ns1:descriptiveReport>