<?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-C331-KR-13 </ns2:number><ns2:name>Vicinity of Southern Long Island</ns2:name><ns2:generalLocality>Vicinity of Southern Long Island</ns2:generalLocality><ns2:fieldUnit>Williamson &amp; Associates, Inc.</ns2:fieldUnit></ns1:projectMetadata><ns1:registryMetadata><ns2:registryNumber>H12602</ns2:registryNumber><ns2:sheetID>3</ns2:sheetID><ns2:registryInstructions xsi:nil="true"></ns2:registryInstructions><ns2:sublocality>Vicinity of Moriches Inlet</ns2:sublocality><ns2:stateOrTerritory>New York</ns2:stateOrTerritory><ns2:country>United States</ns2:country><ns2:scale>20000</ns2:scale></ns1:registryMetadata><ns1:surveyMetadata><ns2:year>2013</ns2:year><ns2:chiefOfParty>Ransom C. White III</ns2:chiefOfParty><ns2:projectType>Navigable Area</ns2:projectType><ns2:PIDate>2013-06-27</ns2:PIDate><ns2:datesOfSurvey><ns2:start>2013-10-22</ns2:start><ns2:end>2013-12-31</ns2:end></ns2:datesOfSurvey><ns2:equipmentTypes><ns2:soundingEquipment>Multibeam Echo Sounder</ns2:soundingEquipment><ns2:imageryEquipment>Side Scan Sonar</ns2:imageryEquipment></ns2:equipmentTypes><ns2:acquisition><ns2:units>meters</ns2:units></ns2:acquisition><ns2:horizontalCoordinateSystem zone="18 N">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>Contractor</ns1:assignment></ns1:metadata><ns1:areaSurveyed><ns1:areaDescription><ns2:discussion>Williamson &amp; Associates, Inc. conducted a hydrographic survey in the southern waters off of Long Island, NY.  The sub-locality of this survey is described as Vicinity of Moriches Inlet, NY.

The survey encompassed an area of approximately 13 square nautical miles and was assigned registry number H12602.  Project instructions required object detection coverage in 2-4 meters of water with 100% SSS and concurrent set line spacing SBES or MBES and backscatter.  Object detection coverage was required as well in 4-20 meters of water with 200% SSS and concurrent MBES and backscatter.  Complete MBES and backscatter were the only requirements in water depths greater than 20 meters.

It should be noted that the appendices and separates for this report were created using the XML Schema format from XMLDR v13.1 released in June 2013 and will not follow the layout described in HSSD 2012. This was approved through email correspondence with our COTR on 4/10/2013, see correspondence in Appendix II.
</ns2:discussion><ns2:limits><ns2:northWest><ns2:latitude hemisphere="N">40.7822880278</ns2:latitude><ns2:longitude hemisphere="W">72.697101</ns2:longitude></ns2:northWest><ns2:southEast><ns2:latitude hemisphere="N">40.7016797778</ns2:latitude><ns2:longitude hemisphere="W">72.8073808056</ns2:longitude></ns2:southEast></ns2:limits><ns2:images><ns2:caption>H12602 Sheet Boundaries Overlaid on Chart 12352</ns2:caption><ns2:link>SupportFiles\H12602_OverviewChart.JPG</ns2:link></ns2:images><ns2:comments><ns2:fieldComment><ns2:comment>As per the field crew's email confirmation (review Appendix II) with the COTR on Oct 28th, sheet H12602 was surveyed to the 2m contour inshore of the inlet, and to the 4m contour offshore of the inlet within the bounds of vessel safety.  The 2m navigable area limit line (NALL) was frequently unachievable due to shoal waters, breaking seas and inshore man made obstructions.  Vessel and crew safety was a priority concern.</ns2:comment><ns2:initials xsi:nil="true"></ns2:initials></ns2:fieldComment><ns2:branchComment concurrence="Comment Only"><ns2:comment>The correspondence is attached.</ns2:comment></ns2:branchComment></ns2:comments></ns1:areaDescription><ns1:surveyLimits><ns2:results deviation="true"><ns2:discussion>As per the field crews email confirmation (review correspondence folder) with the COTR on Oct 28th, sheet H12602 was surveyed to the 2m contour inshore of the inlet, and to the 4m contour offshore of the inlet within the bounds of vessel safety.</ns2:discussion></ns2:results><ns2:comments/></ns1:surveyLimits><ns1:surveyPurpose><ns2:discussion>As per the project instructions: The purpose of this project is to provide contemporary surveys to update National Ocean Service (NOS) nautical charting products.  This project is in response to different user group needs following Hurricane Sandy landfall. Specifically these data will adjoin updated shoreline, address the need for updated bathymetry for inundation modeling, and help identify marine debris for potential removal.</ns2:discussion><ns2:comments/></ns1:surveyPurpose><ns1:surveyQuality><ns2:adequacy>The entire survey is adequate to supersede previous data.</ns2:adequacy><ns2:discussion>Survey quality was reviewed mainly by utilizing daily checks for data matchup, swath density and motion/refraction artifacts. Sounding density was found to meet or exceed the object detection and single line spacing requirements out to roughly 40-45 degrees from nadir, which was deemed acceptable given that our requirements called for skunk strip MBES as a gap filler for 100% and 200% SSS. A full MBES coverage plan would include at least a 20% swath overlap, which is not possible with a set line spacing. Motion artifacts, when found, were due to excessive weather conditions. Latency values were checked and the motion artifacts were measured. The majority of motion artifacts found fell under our IHO Order 1a error budget and were located well offshore in easily navigable water. Considering the consistently poor working conditions during the winter months, motion artifacts became somewhat frequent, however they posed little threat to the usefulness of the data as expected vessel traffic in the area consists of no vessels that draw more than 2-3 meters.

In-depth crossline comparisons were performed. The results of the crossline comparison can be found in section B.2.1 of this report. The crossline comparisons consisted of analyzing each individual crossline with the finalized CUBE surface using the CARIS surface report tool. Once a CARIS surface report was generated, the results were inserted into a spreadsheet for total calculations of the survey area. The surface report informs the user of the percentage of soundings across the swath in increments set by the user that fall within the desired IHO specifications, in our case 10 degree increments, within IHO Order 1a. Areas that did not pass the IHO order 1a specification were due to shifting bathy near the inlets and can be reviewed in section B.2.6 of this report.

Survey quality is acceptable to supersede previous bathymetric, shoreline, overhead and submerged feature data within the project bounds.  </ns2:discussion><ns2:comments><ns2:branchComment concurrence="Comment Only"><ns2:comment>The motion artifacts were determined to be within NOAA specifications during office review.  The multibeam coverage and sounding density over several features was found to be inadequate during office review.</ns2:comment></ns2:branchComment></ns2:comments></ns1:surveyQuality><ns1:surveyCoverage><ns2:results deviation="true"><ns2:discussion>Due to changing morphology and a combination of shoal and swell conditions, coverage gaps are present in SSS data. Vessel and crew safety was a priority and was always taken into consideration. There are four coverage gaps located on this sheet. Two coverage gaps are located southwest of Moriches Inlet, both of which occurred because of shoal conditions and a large swell that made the area inaccessible. Another shoal-caused gap is located southeast of the inlet. The fourth gap on this sheet is located inside the inlet east of Fire Island National Seashore.

It should be noted that during initial acquisition the survey line plan used was designed to obtain full multibeam coverage in shoal water depths.  A new survey line plan was set in place on October 23rd containing line spacing to result in 200% SSS coverage with skunk strip MBES.  The line plan was implemented on October 25th and was confirmed by the COTR via email on October 30th.  Please refer to Appendix II of this report for email communications.

Certain sections associated with the NALL areas were not fully covered due to the extent of changes in seabed. Please refer to section D.2.1 &quot;Shoreline&quot; for NALL information and shoreline changes.

Please refer to section D.1.3 AWOIS&quot; Items&quot; for information on survey coverage gaps.</ns2:discussion></ns2:results><ns2:comments><ns2:branchComment concurrence="Comment Only"><ns2:comment>The correspondence is attached.</ns2:comment></ns2:branchComment></ns2:comments></ns1:surveyCoverage><ns1:coverageGraphic><ns2:caption>H12602 SSS Mosaic of all Data Acquired Overlaid on Chart 12352</ns2:caption><ns2:link>SupportFiles\H12602_SSS_Mosaic.JPG</ns2:link></ns1:coverageGraphic><ns1:coverageGraphic><ns2:caption>H12600 SSS Coverage Depicting percent of coverage: Yellow = 100%, Cyan = 200%</ns2:caption><ns2:link>SupportFiles\H12602_SSS_Coverage.JPG</ns2:link></ns1:coverageGraphic><ns1:coverageGraphic><ns2:caption>H12600 MBES Coverage Overlaid</ns2:caption><ns2:link>SupportFiles\H12602_MBES_Coverage.JPG</ns2:link></ns1:coverageGraphic><ns1:surveyStatistics><ns2:LNM><ns2:vesselLNM><ns2:vessel><ns2:hullID>HEW46077J708</ns2:hullID><ns2:statistics><ns2:MS_SBES>0</ns2:MS_SBES><ns2:MS_MBES>159.57</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>339.46</ns2:MS_MBES_SSS><ns2:MS_SBES_SSS>0</ns2:MS_SBES_SSS><ns2:XL_MBES_SBES>21.57</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>499.03</ns2:MS_MBES_SSS><ns2:MS_SBES_SSS>0</ns2:MS_SBES_SSS><ns2:XL_MBES_SBES>21.57</ns2:XL_MBES_SBES><ns2:XL_lidar>0</ns2:XL_lidar><ns2:percentXLLNM>0</ns2:percentXLLNM></ns2:totalLNM></ns2:LNM><ns2:totalSurveyStats><ns2:bottomSamples>7</ns2:bottomSamples><ns2:AWOIS>3</ns2:AWOIS><ns2:maritimeBoundaryPoints>0</ns2:maritimeBoundaryPoints><ns2:DP>0</ns2:DP><ns2:diveOps>0</ns2:diveOps><ns2:SNM>13.39</ns2:SNM></ns2:totalSurveyStats><ns2:surveyDates>2013-10-22</ns2:surveyDates><ns2:surveyDates>2013-10-25</ns2:surveyDates><ns2:surveyDates>2013-10-26</ns2:surveyDates><ns2:surveyDates>2013-10-28</ns2:surveyDates><ns2:surveyDates>2013-10-29</ns2:surveyDates><ns2:surveyDates>2013-10-30</ns2:surveyDates><ns2:surveyDates>2013-10-31</ns2:surveyDates><ns2:surveyDates>2013-11-05</ns2:surveyDates><ns2:surveyDates>2013-11-06</ns2:surveyDates><ns2:surveyDates>2013-11-16</ns2:surveyDates><ns2:surveyDates>2013-11-19</ns2:surveyDates><ns2:surveyDates>2013-11-20</ns2:surveyDates><ns2:surveyDates>2013-11-21</ns2:surveyDates><ns2:surveyDates>2013-11-30</ns2:surveyDates><ns2:surveyDates>2013-12-01</ns2:surveyDates><ns2:surveyDates>2013-12-02</ns2:surveyDates><ns2:surveyDates>2013-12-03</ns2:surveyDates><ns2:surveyDates>2013-12-04</ns2:surveyDates><ns2:surveyDates>2013-12-12</ns2:surveyDates><ns2:surveyDates>2013-12-31</ns2:surveyDates><ns2:discussion xsi:nil="true"></ns2:discussion><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>HEW46077J708</ns2:hullID><ns2:LOA units="meters">7.32</ns2:LOA><ns2:draft units="meters">1.2</ns2:draft></ns1:vessel><ns1:images><ns2:caption>M/V Nooit Volmaakt from the port side.  The pole mount on the bow for the Edge Tech SSS can be seen.</ns2:caption><ns2:link>SupportFiles\NV_2.jpg</ns2:link></ns1:images><ns1:images><ns2:caption>M/V Nooit Volmaakt from the starboard bow.  The pole mount on the bow for the Edge Tech SSS can be seen.</ns2:caption><ns2:link>SupportFiles\NV_1.jpg</ns2:link></ns1:images><ns1:discussion>The M/V Nooit Volmaakt acquired all multibeam data with a pole mounted R2Sonic 2024 at 400kHz and a pole mounted EdgeTech 4600 at 540 kHz using a POSMV for position, orientation and motion corrections.    For more detailed information on equipment and vessel please refer to OPR-C331-KR-13 DAPR submitted under a different cover.</ns1:discussion><ns1:comments/></ns1:vessels><ns1:equipment><ns1:majorSystem><ns2:manufacturer>R2Sonic</ns2:manufacturer><ns2:model>2024</ns2:model><ns2:type>MBES</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>EdgeTech</ns2:manufacturer><ns2:model>4600</ns2:model><ns2:type>SSS</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>Applanix</ns2:manufacturer><ns2:model>POS MV 320</ns2:model><ns2:type>Positioning and Attitude System</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>Valeport</ns2:manufacturer><ns2:model>MiniSVS</ns2:model><ns2:type>Sound Speed System</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>SeaBird</ns2:manufacturer><ns2:model>SBE19</ns2:model><ns2:type>Conductivity, Temperature and Depth Sensor</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>SeaBird</ns2:manufacturer><ns2:model>SBE19+</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>Quality control crosslines were planned so that most main scheme lines would intersect with at least one crossline, they were well distributed geographically, and that total crossline nautical miles ran would total more than 4 % of the main scheme nautical miles (a specification set forth by the HSSD 2012). Our quantification of required crossline distance in this sheet was complicated by a change in our line plan to set line spacing from full MBES coverage, causing skunk striping in the shallower areas. Survey that had taken place prior to the line plan change caused there to be far more line miles of data than what the new line plan called for. The quantification for line miles of crosslines was based on the new line plan, which had fewer lines. Additionally, line miles across fouled areas were removed from the calculation. Therefore, the percentage of crosslines to total mainline mileage will appear to be less than what was required, however, the true percentage should be determined as described above.

Total cross-line length surveyed for task order OPR-C331-KR-13 sheet H12602 was 21.57 nautical miles or 4.6% of the total main scheme distance (469.42 nautical miles).  All crosslines were compared to the main scheme line BASE, using the CARIS HIPS QC Report process for individual lines.  The swath was split by swath angles in 10 degree increments for the crossline analysis. The seabed near the inlet was so dynamic, being current driven, that it changed significantly from day to day.  Three crosslines obtained in the inlet failed to meet the standards set forth by the HSSD.  The “outlier” lines only account for 0.1% of the main scheme nautical line mileage, however, the seabed shifting was so significant in the areas surrounding the inlet that with the outlier crosslines included the overall average only passed the 93.93% confidence level.  These lines were deemed unacceptable due to seabed shift and not used resulting in a crossline mileage of 4.49% of the main scheme lines.  The outlier lines are included in with the data delivered however they were not included in the final surface. Without these outlier lines the vast majority of beams passed within the IHO Order 1a specifications at a 95% confidence level or better with an overall confidence level average of 99.9% and a standard deviation of 0.18%. (See Separate IV).  Lines that covered both the 50cm (0-20m water depth) and the 2m (18-40m water depth) surfaces were analyzed independently for each surface.</ns2:discussion><ns2:images><ns2:caption> MBES data overlaid on Chart 12352.  The cross-lines that were flagged as outliers and not used due to shifts over time in the seabed are highlighted in Blue.</ns2:caption><ns2:link>SupportFiles\H12602_Outlier_Xlines.JPG</ns2:link></ns2:images><ns2:comments><ns2:branchComment concurrence="Concur with clarification"><ns2:comment>The crossline calculation method described by the hydrographer was acknowledged and approved by NOAA Operations Branch. See attached correspondence.</ns2:comment></ns2:branchComment></ns2:comments></ns1:crosslines><ns1:uncertainty><ns2:values><ns2:tideUncertainty><ns2:measured units="meters">0</ns2:measured><ns2:zoning units="meters">0.204</ns2:zoning></ns2:tideUncertainty><ns2:soundSpeedUncertainty><ns2:hullID>HEW46077J708</ns2:hullID><ns2:measuredCTD units="meters/second">1.5</ns2:measuredCTD><ns2:measuredMVP xsi:nil="true"/><ns2:surface units="meters/second">0.2</ns2:surface></ns2:soundSpeedUncertainty></ns2:values><ns2:discussion>Refer to the Data Acquisition and Processing Report (DAPR) for a complete description of the uncertainty values used for processing sheet H12602.

According to the confidence interval values reported by JOA Surveys, our tidal uncertainty value at 95% confidence level was 0.399m and includes the estimated gage measurement error, tidal datum computation error and tidal zoning error.  The reported error value was then divided by 1.96 since CARIS assumes TPU values to be 1 sigma (Field Procedures Manual April 2013) resulting in a value of 0.204m.  The tidal uncertainty field labeled in CARIS as “measured” was left at zero as the reported error value of 0.399m included the estimated gage measurement error and the tidal datum computation error as well as the tidal zoning error.  Any max uncertainty measurements exceeding IHO Order 1a specifications are due to shifting sand bars and seabed morphology and are explained in section B.2.6 (Factors Affecting Soundings).</ns2:discussion><ns2:comments/></ns1:uncertainty><ns1:junctions><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="true"><ns2:issue><ns2:title>Motion Correction System</ns2:title><ns2:discussion>B.2.5.1  POS MV 320 functioned adequately throughout the survey considering the frequent higher sea state.  The average sea state offshore during the high majority of survey days was a 1m swell.  Depending on the direction of the swell some attitude artifacting resulted, mostly in deeper areas of the survey.  These lines were not rejected as no latency was found to exist and the QC showed the lines to still be within spec using crossline analysis.  This was concluded to be the result of a small survey vessel in large enough seas to challenge the accuracy of the IMU.  </ns2:discussion><ns2:comments/></ns2:issue></ns2:results><ns2:comments/></ns1:equipmentEffectiveness><ns1:factorsAffectingSoundings><ns2:results deviation="true"><ns2:issue><ns2:title>Shifting Sand Waves / Bars / Features</ns2:title><ns2:discussion>Sand features in waters shallower than 10 meters are constantly shifting, as much as 25cm per day in some areas.  Areas concentrated around the inlet are subject to the strongest and most rapid tidal currents. As a result these areas experience the most morphological shifting resulting in poor data alignment, especially if overlapping acquisition was separated by 5-10 days.  Due to this effect on the data overlapping the timing of acquisition was strongly considered in planning.</ns2:discussion><ns2:images><ns2:caption>MBES soundings showing depths for 4 lines, two acquired on JD 302 and two on JD 337.  The separation in seabed morphologies can be seen well here as the sand has shifted due to currents and other environmental factors.</ns2:caption><ns2:link>SupportFiles\H12602_ShiftingBathy_3D_Bathy.JPG</ns2:link></ns2:images><ns2:images><ns2:caption>Image to be associated with the previous figure.  The colors signify days of acquisition.  Light green for JD 302 and dark green for JD 337.</ns2:caption><ns2:link>SupportFiles\H12602_ShiftingBathy_3D_Day.JPG</ns2:link></ns2:images><ns2:images><ns2:caption>Chart 12352 overlain with a green box highlighting the area of shifting seabed shown in the previous two figures.</ns2:caption><ns2:link>SupportFiles\H12602_ShiftingBathy_Chart.JPG</ns2:link></ns2:images><ns2:comments/></ns2:issue></ns2:results><ns2:comments/></ns1:factorsAffectingSoundings><ns1:soundSpeedMethods><ns1:castFrequency>4 hours</ns1:castFrequency><ns1:discussion>A Sea-Bird CTD was used every 2-4 hours depending on variation in the surface sound velocity.  As per the HSSD casts were taken if the surface sound velocity changed by more than 2 m/s.  Two Sea-Bird CTDs were used aboard the survey vessel, a SBE 19 and SBE 19+.

Sound Velocity was close to homogeneous from day to day.  No significant sound velocity errors were encountered.</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><ns2:fieldComment><ns2:comment>All data reduction procedures conform to those detailed in the DAPR. </ns2:comment><ns2:initials xsi:nil="true"></ns2:initials></ns2:fieldComment></ns2:comments></ns1:corrections><ns1:calibrations><ns2:results deviation="true"><ns2:discussion>Multiple calibration patch tests were conducted for the MBES system after the initial calibration.  These were conducted to account for small shifts in the mounting flange.  No resulting issues were found to adversely affect the data.</ns2:discussion><ns2:calibration><ns2:type>MBES</ns2:type><ns2:date>2013-10-02</ns2:date><ns2:reason>Vessel ran sensor aground on Sand Bar.</ns2:reason></ns2:calibration><ns2:calibration><ns2:type>MBES</ns2:type><ns2:date>2013-10-06</ns2:date><ns2:reason>Vessel ran sensor aground on Sand Bar.</ns2:reason></ns2:calibration><ns2:calibration><ns2:type>MBES</ns2:type><ns2:date>2013-10-15</ns2:date><ns2:reason>Vessel ran sensor aground on Sand Bar.</ns2:reason></ns2:calibration><ns2:calibration><ns2:type>MBES</ns2:type><ns2:date>2013-10-18</ns2:date><ns2:reason>Vessel ran sensor aground on Sand Bar.</ns2:reason></ns2:calibration><ns2:calibration><ns2:type>MBES</ns2:type><ns2:date>2013-11-05</ns2:date><ns2:reason>Vessel ran sensor aground on Sand Bar.</ns2:reason></ns2:calibration><ns2:calibration><ns2:type>MBES</ns2:type><ns2:date>2013-11-11</ns2:date><ns2:reason>Vessel ran sensor hard aground on Sand Bar.</ns2:reason></ns2:calibration></ns2:results><ns2:comments/></ns1:calibrations><ns1:additionalIssues><ns2:comments/></ns1:additionalIssues></ns1:echoSoundingCorrections><ns1:backscatter><ns2:results acquired="true"><ns2:discussion>Backscatter was converted to HDCS file and is included with the data submitted to the Branch.</ns2:discussion></ns2:results><ns2:comments><ns2:branchComment concurrence="Comment Only"><ns2:comment>R2Sonic backscatter data is not supported by NOAA's current backscatter processing software. Backscatter products were not created during office processing.</ns2:comment></ns2:branchComment></ns2:comments></ns1:backscatter><ns1:dataProcessing><ns1:softwareUpdates><ns1:featureObjectCatalog>5.2</ns1:featureObjectCatalog><ns1:discussion>No software updates were implemented since the DAPR.</ns1:discussion><ns1:comments/></ns1:softwareUpdates><ns1:surfaces><ns1:surface><ns2:surfaceName>H12602_West_MB_50cm_MLLW_Final</ns2:surfaceName><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:resolution units="meters">0.5</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>H12602_Central_MB_50cm_MLLW_Final</ns2:surfaceName><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:resolution units="meters">0.5</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>H12602_East_MB_50cm_MLLW_Final</ns2:surfaceName><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:resolution units="meters">0.5</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>H12602_MB_2m_MLLW_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">28.28</ns2:max></ns2:depthRange><ns2:surfaceParameter>NOAA_2m</ns2:surfaceParameter><ns2:purpose>Complete MBES</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceName>H12601_SSS_1m_100%_A</ns2:surfaceName><ns2:surfaceType>SSS Mosaic</ns2:surfaceType><ns2:resolution units="meters">1</ns2:resolution><ns2:depthRange><ns2:min units="meters">0</ns2:min><ns2:max units="meters">22.5</ns2:max></ns2:depthRange><ns2:surfaceParameter>N/A</ns2:surfaceParameter><ns2:purpose>100% SSS</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceName>H12601_SSS_1m_100%_B</ns2:surfaceName><ns2:surfaceType>SSS Mosaic</ns2:surfaceType><ns2:resolution units="meters">1</ns2:resolution><ns2:depthRange><ns2:min units="meters">0</ns2:min><ns2:max units="meters">22.5</ns2:max></ns2:depthRange><ns2:surfaceParameter>N/A</ns2:surfaceParameter><ns2:purpose>100% SSS</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceName>H12602_AWOIS_15112_MB_50cm_MLLW_Final</ns2:surfaceName><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:resolution units="meters">0.5</ns2:resolution><ns2:depthRange><ns2:min units="meters">10.6</ns2:min><ns2:max units="meters">23.61</ns2:max></ns2:depthRange><ns2:surfaceParameter>NOAA_0.5m</ns2:surfaceParameter><ns2:purpose>Object Detection</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceName>H12602_AWOIS_15111_MB_50cm_MLLW_Final</ns2:surfaceName><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:resolution units="meters">0.5</ns2:resolution><ns2:depthRange><ns2:min units="meters">16.25</ns2:min><ns2:max units="meters">20.03</ns2:max></ns2:depthRange><ns2:surfaceParameter>NOAA_0.5m</ns2:surfaceParameter><ns2:purpose>Object Detection</ns2:purpose></ns1:surface><ns1:discussion>As per the project instructions a 1m SSS mosaic resolution was used.  The 200% SSS coverage was split into 100% coverage mosaics.  The MBES data was gridded at 0.5 meters for water depths ranging between 0-20 meters, and gridded at 2 meters in water depths between 18-40m.  Multiple 50cm surfaces were created in lieu of one large surface to reduce the file size and allow for quicker localized surface loading.  Separate surfaces were created for the AWOIS areas that extended into water depths greater than 20m, as the required resolution for data at depths greater than 20m (2m resolution) differ from that required for AWOIS coverage (50cm resolution).</ns1:discussion><ns1:comments/></ns1:surfaces><ns1:additionalDataProcessing><ns2:comments/></ns1:additionalDataProcessing></ns1:dataProcessing></ns1:dataAcquisitionAndProcessing><ns1:verticalAndHorizontalControl><ns1:discussion>Additional information discussing the vertical or horizontal control for this survey can be found in the accompanying HVCR.</ns1:discussion><ns1:verticalControl><ns2:verticalDatum>Mean Lower Low Water</ns2:verticalDatum><ns2:standard_or_ERZT used="true"><ns2:methodsUsed>Discrete Zoning</ns2:methodsUsed><ns2:tideStations><ns2:subordinateGauges><ns2:stationName>Moriches Coast Guard Station</ns2:stationName><ns2:stationID>8513388</ns2:stationID></ns2:subordinateGauges><ns2:subordinateGauges><ns2:stationName>Moriches Inlet Open Coast</ns2:stationName><ns2:stationID>8513398</ns2:stationID></ns2:subordinateGauges></ns2:tideStations><ns2:correctorFiles><ns2:waterLevels><ns2:fileName>Z:\CARIS\Tide\8513388.tid</ns2:fileName><ns2:status>Final Approved</ns2:status></ns2:waterLevels><ns2:waterLevels><ns2:fileName>Z:\CARIS\Tide\8513398.tid</ns2:fileName><ns2:status>Final Approved</ns2:status></ns2:waterLevels><ns2:tideCorrectors><ns2:fileName>Z:\CARIS\Tide\JOA-C331KR2013-MORICHES BAY 20140419.zdf</ns2:fileName><ns2:status>Final</ns2:status></ns2:tideCorrectors></ns2:correctorFiles><ns2:finalTides><ns2:dateSubmitted>2014-03-17</ns2:dateSubmitted><ns2:dateReceived>2014-03-25</ns2:dateReceived></ns2:finalTides><ns2:discussion>Two subordinate tide gauges, 8513388 and 8513398 were installed for final use in sheet H12602.  An auxiliary pressure gauge was used just offshore of the inlet to aid in finalized zoning procedures.  Staff observations were performed for gauge 8513398 once per week for a 2 hour period weather permitting.  Refer to Appendix I for tide notes.</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/></ns1:verticalControl><ns1:horizontalControl><ns2:horizontalDatum>North American Datum of 1983 (NAD83). Date were acquired in WGS84, as shown in the HVF, but were converted to NAD83 for processing and delivery. See DAPR A.3 and B.1</ns2:horizontalDatum><ns2:projection>UTM 18N</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, Broadcast Site ID: 803</ns2:name></ns2:USCGStations><ns2:discussion xsi:nil="true"></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 xsi:nil="true"></ns2:discussion><ns2:comments/></ns1:methods><ns1:charts><ns2:rasterChart><ns2:chart><ns2:number>12352</ns2:number><ns2:kapp>694</ns2:kapp><ns2:scale>40000</ns2:scale><ns2:edition>34</ns2:edition><ns2:editionDate>2012-09</ns2:editionDate><ns2:LNMDate>2014-04-18</ns2:LNMDate><ns2:NMDate>2014-04-18</ns2:NMDate></ns2:chart><ns2:discussion>Refer to the discussion for chart 12353.</ns2:discussion><ns2:comments><ns2:branchComment concurrence="Concur with clarification"><ns2:comment>Raster chart 12352_1</ns2:comment></ns2:branchComment></ns2:comments></ns2:rasterChart><ns2:rasterChart><ns2:chart><ns2:number>12352</ns2:number><ns2:kapp>695</ns2:kapp><ns2:scale>40000</ns2:scale><ns2:edition>34</ns2:edition><ns2:editionDate>2012-09</ns2:editionDate><ns2:LNMDate>2014-04-17</ns2:LNMDate><ns2:NMDate>2014-04-17</ns2:NMDate></ns2:chart><ns2:discussion>Refer to the discussion for chart 12353.</ns2:discussion><ns2:comments><ns2:branchComment concurrence="Concur with clarification"><ns2:comment>Raster chart 12352_2</ns2:comment></ns2:branchComment></ns2:comments></ns2:rasterChart><ns2:rasterChart><ns2:chart><ns2:number>12353</ns2:number><ns2:kapp>701</ns2:kapp><ns2:scale>80000</ns2:scale><ns2:edition>19</ns2:edition><ns2:editionDate>2011-11</ns2:editionDate><ns2:LNMDate>2014-04-18</ns2:LNMDate><ns2:NMDate>2014-04-18</ns2:NMDate></ns2:chart><ns2:discussion>H12602 survey data was compared to Raster Chart 12352 and 12353.  In general chart and survey depths match well.  The areas that have shoaled or are constantly shifting are discussed in the section labeled Shoal and Hazardous Features.</ns2:discussion><ns2:comments/></ns2:rasterChart><ns2:ENC><ns2:chart><ns2:name>ENC US4NY53M</ns2:name><ns2:scale>80000</ns2:scale><ns2:edition>9</ns2:edition><ns2:updateApplicationDate>2012-11-30</ns2:updateApplicationDate><ns2:issueDate>2012-11-30</ns2:issueDate><ns2:preliminary>false</ns2:preliminary></ns2:chart><ns2:discussion>H12602 survey data was compared to Electronic Chart US4NY53N.  Results were very similar to the above comparisons with Raster Chart 12352 and 12353.  See discussion for chart 12353 for Chart comparison.</ns2:discussion><ns2:comments/></ns2:ENC><ns2:ENC><ns2:chart><ns2:name>ENC US5NY52M</ns2:name><ns2:scale>40000</ns2:scale><ns2:edition>10</ns2:edition><ns2:updateApplicationDate>2012-12-27</ns2:updateApplicationDate><ns2:issueDate>2013-03-12</ns2:issueDate><ns2:preliminary>false</ns2:preliminary></ns2:chart><ns2:discussion>H12602 survey data was compared to Electronic Chart US5NY52M.  Results were very similar to the above comparisons with Raster Chart 12352 and 12353.  See discussion for Chart 12353 for chart comparison.</ns2:discussion><ns2:comments/></ns2:ENC><ns2:comments/></ns1:charts><ns1:AWOISItems><ns2:results investigated="Investigated"><ns2:discussion>Three AWOIS items were investigated, items 1685, 15111 and 15112.

We investigated the three AWOIS items listed above. The search radius for items1685 contained three contacts: two small rocks and the third was an 80m long ship.  This wreck associated with AWOIS item  1685 was in very shallow water near the coastline and has retained the shape of its hull as it is sitting flat on the seabed.  The housing structures of the vessel have been heavily corroded and worn down.  The search radius for both items 15111 and 15112 contained no contacts or features, significant or otherwise.

As discussed in section A.4 regarding shoal and swell conditions degrading survey data, there were some AWOIS items with nodes containing less than the required number of soundings.  Feature UWTROC 4925 contains less than the required density of soundings.  Seas did not always allow many passes over certain locations.  We did achieve 200% SSS coverage in these areas and operated under the assumption that this would make up for small discrepancies of this nature.  </ns2:discussion><ns2:images><ns2:caption>SSS imagery showing the central portion of the wreck associated with AWOIS 1685.</ns2:caption><ns2:link>SupportFiles\H12602_324_001.JPG</ns2:link></ns2:images></ns2:results><ns2:comments><ns2:branchComment concurrence="Do not concur"><ns2:comment>The multibeam coverage  over UWTROC 4925 was determined to meet requirements for  object detection sounding density during office review.</ns2:comment></ns2:branchComment><ns2:branchComment concurrence="Comment Only"><ns2:comment>The AWOIS Report is attached.</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>One charted feature was investigated that was not assigned as an AWOIS.  An offshore fish haven was found to be charted correctly with at least 11 associated significant wrecks.</ns2:discussion></ns2:results><ns2:comments><ns2:branchComment concurrence="Do not concur"><ns2:comment>Do not concur, multiple wrecks and  obstructions were found outside the charted fish haven. The extents of the fish haven were recommended to be expanded to include these new features.</ns2:comment></ns2:branchComment></ns2:comments></ns1:chartedFeatures><ns1:unchartedFeatures><ns2:results investigated="Investigated"><ns2:discussion> H12602 did not contain a large number of uncharted features.  Only 4 significant features were found that were not associated with either an AWOIS radius or a fish haven, two of which were wreckage.  These two wrecks were both located near to shore and not far from AWOIS item 1685, one looks to be a barge while the other appears to be a mast of sorts.
</ns2:discussion><ns2:images><ns2:caption>MBES image showing the mast-like wreckage.</ns2:caption><ns2:link>SupportFiles\H12602_303_009_3D.PNG</ns2:link></ns2:images><ns2:images><ns2:caption>SSS Imagery showing significant barge feature.</ns2:caption><ns2:link>SupportFiles\H12602_299_002.JPG</ns2:link></ns2:images></ns2:results><ns2:comments/></ns1:unchartedFeatures><ns1:DTONS><ns2:results reportSubmitted="true"><ns2:numberSubmitted>2</ns2:numberSubmitted><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>The DTON Report is attached.</ns2:comment></ns2:branchComment></ns2:comments></ns1:DTONS><ns1:shoalAndHazardousFeatures><ns2:results investigated="Investigated"><ns2:discussion>In order to investigate shoaling areas and compare to charted depths a grid was overlaid on raster chart 12352.  This allowed the area to be compared visually and easily obtain depth value differences with a high level of accuracy.  The only significant shoaling differing from the chart is occurring inshore of the inlet along the eastern channel.  The shoal just offshore and surrounding the inlet is significant and can be very perilous during a strong southern sea.  Breaking seas can often be seen focused over the offshore east portion of the inlet where the sand bar is the most shoal.  The chart accurately reflects this.
 </ns2:discussion><ns2:images><ns2:caption>Overhead image of the Moriches Inlet in sheet H12602.  The area circled in green highlights the shoaling area inshore.  The area circled in yellow highlights the area of dangerous shoals and breaking seas offshore of the inlet.</ns2:caption><ns2:link>SupportFiles\H12602_Shoals.JPG</ns2:link></ns2:images></ns2:results><ns2:comments/></ns1:shoalAndHazardousFeatures><ns1:channels><ns2:results investigated="Investigated"><ns2:discussion>There are no prominent channels in sheet H12602 besides the channel into the inlet.  The inlet is as charted.  Channel buoys do exist in the inshore area however it should be noted the Moriches Coast Guard Station monitor and move them to adapt with the shifting sand bars just inshore of the inlet.  No channel markers are charted. </ns2:discussion></ns2:results><ns2:comments/></ns1:channels><ns1:bottomSamples><ns2:results investigated="Investigated"><ns2:discussion>Seven bottom samples were acquired for this survey. </ns2:discussion></ns2:results><ns2:comments/></ns1:bottomSamples></ns1:chartComparison><ns1:additionalResults><ns1:shoreline><ns2:results investigated="Investigated"><ns2:discussion>A limited shoreline investigation was completed as per the project instructions.  The majority of the shoreline associated with the survey sheet remained as charted.  A small portion of shoreline was assigned to investigate.  This was the northern coast of the barrier island just to the east of the inshore side of the inlet.  The shore line had been eroded shore-ward roughly 35 meters at the most extreme point.  More information concerning the verified shoreline can be found in the Final Feature File.

Sheet H12602 contains areas where the NALL requirements were not achieved. Any areas that were not satisfied were due to safety concerns with swell or sand bar impacts on the vessel. The sonar was grounded several times, so the crew became more cautious of shallow water as the survey continued. In some areas, however, survey coverage exceeded NALL because water depths were deeper than previously charted due to Sandy.

The area located near Moriches Inlet contained several new sand bars and shoal areas. The largest of unsatisfied NALL areas are located south of the inlet and run parallel to the shoreline. Another NALL area not surveyed is located northeast of the inlet. </ns2:discussion></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>All ATONS were found in place and serving their intended purpose.</ns2:discussion></ns2:results><ns2:comments/></ns1:ATONS><ns1:overheadFeatures><ns2:results investigated="None Exist"><ns2:discussion>Overhead features do not exist for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:overheadFeatures><ns1:submarineFeatures><ns2:results investigated="Investigated"><ns2:discussion>Sheet H12602 contained one feature that appeared to be a submerged exposed pipe or cable.  This feature was found near the western inshore edge of the inlet and is not associated with a charted cable area.  Details for this feature can be found in the H12602 Final Feature File.</ns2:discussion><ns2:images><ns2:caption>MBES Image showing the exposed portion of the long linear feature that was classified as a submerged pipe/cable.</ns2:caption><ns2:link>SupportFiles\H12602_298_001_3D.JPG</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="Not Investigated"><ns2:discussion>Features that we identified as significant and not pre-existing were investigated and the LEAST depth sounding was used as the designated sounding.  Additionally, see previous sections D.1.4 &quot;Charted Features&quot; and D.1.5  &quot;Uncharted Features.&quot;</ns2:discussion></ns2:results><ns2:comments/></ns1:significantFeatures><ns1:constructionOrDredging><ns2:results investigated="None Exist"><ns2:discussion>There is no present or planned construction or dredging within the survey limits. </ns2:discussion></ns2:results><ns2:comments/></ns1:constructionOrDredging><ns1:otherResults><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, Standing and 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>Ransom C. White III</ns2:approverName><ns2:approverTitle>Cheif of Party</ns2:approverTitle><ns2:approvalDate>2014-11-20</ns2:approvalDate></ns1:signingPersonnel><ns1:signingPersonnel><ns2:approverName>Curtis Clement</ns2:approverName><ns2:approverTitle>Project Manager</ns2:approverTitle><ns2:approvalDate>2014-11-20</ns2:approvalDate></ns1:signingPersonnel></ns1:approvalSheet></ns1:descriptiveReport>