<?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>S-D927-BH2-15</ns2:number><ns2:name>Delaware River, PA</ns2:name><ns2:generalLocality>Vicinity of Philadelphia</ns2:generalLocality><ns2:fieldUnit>NOAA R/V BAY HYDRO II</ns2:fieldUnit></ns1:projectMetadata><ns1:registryMetadata><ns2:registryNumber>F00668</ns2:registryNumber><ns2:sheetID>1</ns2:sheetID><ns2:registryInstructions>Define the 18 ft contour in the area south of the Walt Whitman Bridge.  At a minimum for the anchorage area, define the 18 ft contour. As safety permits, attempt to define the 12 ft contour at the anchorage area only.</ns2:registryInstructions><ns2:sublocality>Delaware River</ns2:sublocality><ns2:stateOrTerritory>Pennsylvania</ns2:stateOrTerritory><ns2:country>United States</ns2:country><ns2:scale>10000</ns2:scale></ns1:registryMetadata><ns1:surveyMetadata><ns2:year>2015</ns2:year><ns2:chiefOfParty>Robert W. Mowery</ns2:chiefOfParty><ns2:projectType>Navigable Area</ns2:projectType><ns2:PIDate>2015-09-30</ns2:PIDate><ns2:datesOfSurvey><ns2:start>2015-10-20</ns2:start><ns2:end>2015-10-22</ns2:end></ns2:datesOfSurvey><ns2:equipmentTypes/><ns2:acquisition><ns2:units>meters</ns2:units></ns2:acquisition><ns2:horizontalCoordinateSystem zone="18N">Universal Transverse Mercator (UTM)</ns2:horizontalCoordinateSystem><ns2:timeZone>UTC</ns2:timeZone><ns2:verifier>Pacific Hydrographic Branch</ns2:verifier><ns2:titlesheetRemarks><ns2:fieldRemarks xsi:nil="true"></ns2:fieldRemarks><ns2:branchRemarks xsi:nil="true"></ns2:branchRemarks></ns2:titlesheetRemarks></ns1:surveyMetadata><ns1:assignment>NOAA</ns1:assignment></ns1:metadata><ns1:areaSurveyed><ns1:areaDescription><ns2:discussion>F00668 encompassed two separate areas of the Delaware River near Philadelphia, Pennsylvania.  The approximate area for the survey was 0.50 square nautical miles.

The downriver section, charted Navy Anchorage 10, had an area approximately 0.11 square nautical miles.  The outline was approximately 0.45 nautical miles long, 0.26 nautical miles wide at its widest point, and 0.19 nautical miles wide at its narrowest point.  The second area of F00668 was approximately  1.10 nautical miles upriver from Navy Anchorage 10 near Gloucester City.  The upriver area was triangle shaped, approximately 0.27 square nautical miles and had an outline approximately 1.53 nautical miles long by 0.21 nautical miles wide at its widest point.  The upriver extent of this survey was at  Interstate 76, Walt Whitman Bridge, while the downriver extent was 2.62 nautical miles south west of the Walt Whitman Bridge (Figure 1).</ns2:discussion><ns2:limits><ns2:northWest><ns2:latitude hemisphere="N">39.8760989167</ns2:latitude><ns2:longitude hemisphere="W">75.1379238056</ns2:longitude></ns2:northWest><ns2:southEast><ns2:latitude hemisphere="N">39.8747558611</ns2:latitude><ns2:longitude hemisphere="W">75.118709</ns2:longitude></ns2:southEast></ns2:limits><ns2:images><ns2:caption>F00668 Survey limits, relative to Interstate 76, Walt Whitman Bridge.</ns2:caption><ns2:link>file:///M:/SD927BH215/Surveys/F00668/Compilation/Report/F00668_DR_Office/Report%20Images/F00668%20Survey%20Limits.png</ns2:link></ns2:images><ns2:comments/></ns1:areaDescription><ns1:surveyLimits><ns2:results deviation="false"><ns2:discussion>Survey limits were acquired in accordance with the requirements in the Project Instructions and the HSSD.</ns2:discussion></ns2:results><ns2:comments/></ns1:surveyLimits><ns1:surveyPurpose><ns2:discussion>Survey F00668 is a Navigable Area Survey that is intended to supersede all bathymetry, seafloor features, and bottom characteristics within the assigned survey area as defined by the Project Instructions (PI) for updating of NOAA Chart 12313 and NOAA Electronic Navigational Chart (ENC) US5PA12M.  This survey was a request from the Philadelphia Pilots and was requested due to increasing size of container vessels maneuvering in the area.</ns2:discussion><ns2:comments><ns2:branchComment concurrence="Comment Only"><ns2:comment xsi:nil="true"></ns2:comment></ns2:branchComment></ns2:comments></ns1:surveyPurpose><ns1:surveyQuality><ns2:adequacy>The entire survey is adequate to supersede previous data.</ns2:adequacy><ns2:discussion>All data was acquired and processed within the specifications set forth in the Hydrographic Surveys Specifications and Deliverables Manual (HSSD) and Field Procedures Manual for Hydrographic Surveying (FPM).  In order to extract descriptive statistics of the data density achievement, the density layer of each finalized surface was queried within CARIS and examined in Excel (Figure 2).  This analysis indicated that the 0.5m mainscheme surface exceeded the 95% requirement as set forth in the HSSD (Figure 3).</ns2:discussion><ns2:images><ns2:caption>F00668 Sounding density statistics for the 0.5M CUBE Surface.</ns2:caption><ns2:link>file:///M:/SD927BH215/Surveys/F00668/Compilation/Report/F00668_DR_Office/Report%20Images/F00668%20Sounding%20Density%20Statistics.png</ns2:link></ns2:images><ns2:images><ns2:caption>Sounding density for F00668, 0.5M CUBE Surface.</ns2:caption><ns2:link>file:///M:/SD927BH215/Surveys/F00668/Compilation/Report/F00668_DR_Office/Report%20Images/F00668%20Sounding%20Density%20Map.png</ns2:link></ns2:images><ns2:comments/></ns1:surveyQuality><ns1:surveyCoverage><ns2:results deviation="false"><ns2:discussion>Survey coverage was in accordance with the requirements in the Project Instructions and the HSSD.</ns2:discussion></ns2:results><ns2:comments/></ns1:surveyCoverage><ns1:coverageGraphic><ns2:caption>Object detection MBES coverage, in green, overlaid onto Chart 12313.  </ns2:caption><ns2:link>file:///M:/SD927BH215/Surveys/F00668/Compilation/Report/F00668_DR_Office/Report%20Images/F00668%20Survey%20Coverage.png</ns2:link></ns1:coverageGraphic><ns1:surveyStatistics><ns2:LNM><ns2:vesselLNM><ns2:vessel><ns2:hullID>S5401</ns2:hullID><ns2:statistics><ns2:MS_SBES>0</ns2:MS_SBES><ns2:MS_MBES>27.42</ns2:MS_MBES><ns2:MS_lidar>0</ns2:MS_lidar><ns2:MS_SSS>0</ns2:MS_SSS><ns2:MS_SBES_MBES>0</ns2:MS_SBES_MBES><ns2:MS_MBES_SSS>0</ns2:MS_MBES_SSS><ns2:MS_SBES_SSS>0</ns2:MS_SBES_SSS><ns2:XL_MBES_SBES>2.81</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>27.42</ns2:MS_MBES><ns2:MS_lidar>0.00</ns2:MS_lidar><ns2:MS_SSS>0.00</ns2:MS_SSS><ns2:MS_SBES_MBES>0.00</ns2:MS_SBES_MBES><ns2:MS_MBES_SSS>0.00</ns2:MS_MBES_SSS><ns2:MS_SBES_SSS>0.00</ns2:MS_SBES_SSS><ns2:XL_MBES_SBES>2.81</ns2:XL_MBES_SBES><ns2:XL_lidar>0.00</ns2:XL_lidar><ns2:percentXLLNM>10.26</ns2:percentXLLNM></ns2:totalLNM></ns2:LNM><ns2:totalSurveyStats><ns2:bottomSamples>5</ns2:bottomSamples><ns2:AWOIS>0</ns2:AWOIS><ns2:maritimeBoundaryPoints>0</ns2:maritimeBoundaryPoints><ns2:DP>0</ns2:DP><ns2:diveOps>0</ns2:diveOps><ns2:SNM>0.36</ns2:SNM></ns2:totalSurveyStats><ns2:surveyDates>2015-10-20</ns2:surveyDates><ns2:surveyDates>2015-10-21</ns2:surveyDates><ns2:surveyDates>2015-10-22</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>S5401</ns2:hullID><ns2:LOA units="meters">17.3</ns2:LOA><ns2:draft units="meters">1.8</ns2:draft></ns1:vessel><ns1:discussion>R/V BAY HYDRO II collected all MBES data, sound velocity data, and attitude date for F00668.</ns1:discussion><ns1:comments/></ns1:vessels><ns1:equipment><ns1:majorSystem><ns2:manufacturer>Kongberg</ns2:manufacturer><ns2:model>EM2040</ns2:model><ns2:type>MBES</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>Applanix</ns2:manufacturer><ns2:model>POS M/V V5</ns2:model><ns2:type>Positioning and Attitude System</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>SonTek</ns2:manufacturer><ns2:model>CastAway</ns2:model><ns2:type>Conductivity, Temperature, and Depth Sensor</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>Valport</ns2:manufacturer><ns2:model>miniSVS</ns2:model><ns2:type>Sound Speed System</ns2:type></ns1:majorSystem><ns1:discussion>Vessel configurations, equipment operations, and data acquisition and processing were consistent with specifications described in the Data Acquisition &amp; Processing Report (DAPR).  </ns1:discussion><ns1:comments/></ns1:equipment><ns1:comments/></ns1:equipmentAndVessels><ns1:qualityControl><ns1:crosslines><ns2:discussion>Crosslines were collected, processed and compared in accordance with section 5.2.4.3 of the HSSD.  R/V BAY HYDRO II collected 2.81 linear nautical miles (LNM) of MBES of total crosslines, equating to 10% of mainscheme MBES data (Figure 5) that exceeds the 4% requirement for object detection MBES.  Of the 2.81 LNM of crosslines, 0.84LNM of MBES crosslines were in the Navy Anchorage 10, equating to 8.72% of mainscheme MBES data in that area.  The remaining 1.97 LNM of MBES crosslines were in the area near Gloucester City, equating to 11.53% of mainscheme MBES data in that area.

To evaluate the crosslines, a 50cm CUBE surface was created using strictly mainscheme lines, and a second 50cm CUBE surface was created using only crosslines.  From these two surfaces, a difference surface was generated at a 50cm resolution.  This difference surface is submitted digitally in the Separates II folder.  The comparison indicated that the two surfaces had a mean difference of 0.16m and a standard deviation of 0.14m, showing good internal consistency (Figure 6).   The greatest difference was found to be at the shoaling edge of dredge scours.  

In addition to performing a crossline comparison using surface differencing, the CARIS QC Report was used to compare the MBES crossline sounding to the depth estimates of the 50cm CUBE surface.  The depth differences are calculated between each MBES crossline ping and mainscheme surface; and that depth difference is then compared to allowable NOAA uncertainties.  The output QC Report classifies the percentage of pings meeting NOAA orders by beam angle.  This table was copied and examined in Excel (Figure 7).  Over 95% of the crosslines analyzed were within NOAA Order 1a for the entire swath width.  For further discussion of NOAA standards, refer to Section B.2.2, Uncertainty.</ns2:discussion><ns2:images><ns2:caption>Magnitude of the crossline difference surface, overlaid onto F00668 (in pink) and Chart 12313.</ns2:caption><ns2:link>file:///M:/SD927BH215/Surveys/F00668/Compilation/Report/F00668_DR_Office/Report%20Images/F00668%20XL%20vs%20Mainscheme%20Difference.png</ns2:link></ns2:images><ns2:images><ns2:caption>Mainscheme verses crossline difference comparison graph, with zero difference being represented by an orange line.</ns2:caption><ns2:link>file:///M:/SD927BH215/Surveys/F00668/Compilation/Report/F00668_DR_Office/Report%20Images/F00668%20XL%20vs%20Mainscheme%20Difference%20Graph.png</ns2:link></ns2:images><ns2:images><ns2:caption>CARIS crossline quality control report.</ns2:caption><ns2:link>file:///M:/SD927BH215/Surveys/F00668/Compilation/Report/F00668_DR_Office/Report%20Images/F00668%20XLine%20QC%20Report.png</ns2:link></ns2:images><ns2:comments/></ns1:crosslines><ns1:uncertainty><ns2:values><ns2:soundSpeedUncertainty><ns2:hullID>S5401</ns2:hullID><ns2:measuredCTD units="meters/second">4.0</ns2:measuredCTD><ns2:measuredMVP units="meters/second">N/A </ns2:measuredMVP><ns2:surface units="meters/second">0.5</ns2:surface></ns2:soundSpeedUncertainty></ns2:values><ns2:discussion>In addition to the apriori estimates of sound speed uncertainty, real-time and post-processed uncertainty sources were also incorporated into the depth estimates of F00668.  Real-time uncertainties from the EM2040 were recorded and applied in CARIS.  The post-processed uncertainties associated with vessel roll, pitch, gyro, and navigation were directly applied to the POSPac file via Real Time Kinematics (RTK).  These RTK correctors were applied using an NTRIP server software and used the existing US Army Corps of Engineers (USACE) VRS Network in Philadelphia.  Reference the DAPR for information regarding RTK acquisition and processing.

Uncertainty values of submitted finalized grids were calculated in CARIS using the &quot;Greater of the Two&quot; of uncertainty and standard deviation (scaled to 95%).  To visualized the locations in which accuracy requirements were met for the 50cm finalized surface, a custom predicted NOAA-compliance layer was created, based on the difference between calculated uncertainty of the nodes and the allowable NOAA uncertainty (Figure 8).  To quantify the extent to which accuracy requirements were met, the preceding predicted NOAA compliance layers were queried within CARIS and examined in Excel (Figure 9).  Overall, 100% by node of F00668 met the accuracy requirements stated in Section 5.1.3 of the HSSD.</ns2:discussion><ns2:images><ns2:caption>F00668 MBES data colored by NOAA-compliance and overlaid onto Chart 12313.</ns2:caption><ns2:link>file:///M:/SD927BH215/Surveys/F00668/Compilation/Report/F00668_DR_Office/Report%20Images/F00668%20NOAAness%20Map.tif</ns2:link></ns2:images><ns2:images><ns2:caption>Summary table showing the percentage of nodes satisfying applicable NOAA accuracy levels for F00668.</ns2:caption><ns2:link>file:///M:/SD927BH215/Surveys/F00668/Compilation/Report/F00668_DR_Office/Report%20Images/F00668%20NOAAness%20Graph.tif</ns2:link></ns2:images><ns2:comments/></ns1:uncertainty><ns1:junctions><ns2:discussion>There were no junctions with this survey.</ns2:discussion><ns2:comments/></ns1:junctions><ns1:sonarQCChecks><ns2:results deviation="true"><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>Sound speed casts for MBES survey were acquired via CTD profiles.  Casts were conducted at the start of the day and at the end of data collection for that area.  When data collection for one area was completed, and the vessel moved to the second area, a cast was collected before data collection, then at the end of the day.  Additional casts were conducted if the interval was nearing four hours as required by the HSSD, or when sound speed variations of greater than 2m/s were observed.</ns1:castFrequency><ns1:discussion>The distribution of the sound speed profile casts is shown in Figure 10, below.

Surface sound speed was collected in real time and integrated into the Kongsberg EM2040 bathymetric data.

Sound speed was corrected for in CARIS via the &quot;Nearest in Time&quot; option for all days.</ns1:discussion><ns1:images><ns2:caption>F00668 CTD cast position, in red, relative to survey area.</ns2:caption><ns2:link>file:///M:/SD927BH215/Surveys/F00668/Compilation/Report/F00668_DR_Office/Report%20Images/F00668%20SVP%20Cast%20Positions.png</ns2:link></ns1:images><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:issue><ns2:title>Holiday Assessment</ns2:title><ns2:discussion>Two types of holidays occurred in F00668.  The first type of holiday was an area where no data was collected.  There was one of this type of holiday and it occurred in the area around the charted ATON.  This holiday is approximately four meters long and runs parallel to the river itself.  This holiday was caused by running the survey line parallel to a sharp slope that runs along the sea floor in that area (See Figure 11), and is commonly referred to as &quot;slope effect&quot;.  Due to the proximity of the holiday to a floating ATON, a perpendicular line could not be run to gain full coverage of the area.  

The second type of holiday was a density holiday, an area where the data density did not meet the NOAA standard of five soundings per node; three of these holiday exist.  The first is over the charted 39 foot obstruction, located west of Gloucester Point.  In this area, there are two 0.5m by 1.0m lines, 0.5m apart, where only one or two sounding per none were collected (See Figure 12).  This holiday was hypothesized to have been created as a result of the angled, linear section of the obstruction leaving a shadow behind it on the first pass over the object; then only ensonifying the object in the outer beams on the second pass. The second density holiday is located west of Delaware River Port Authority bulkhead, 24m south of the Walt Whitman Bridge (See Figure 13), and had a density of one to four soundings per node.  This holiday is 5.81m long by 1.49m wide, and is located at the edge of a slope.  This holiday was hypothesized to have been the result of slope effect.  The third area is in the southeastern section of the Navy Anchorage (Anchorage 10).  In this area, two 2.75m long density holiday line occur 10.5n apart, and are also located at the edge of a slope (See Figure 14).  This holiday was also hypothesized to have been the result of slope effect.  None of the density holidays were recognized to have existed until the vessel had left the area, therefore the holidays were never required.

Along the New Jersey side of the river, from the Delaware River Port Authority bulkhead south approximately 1100m, the 18ft contour was only sporadically ensonified (See Figure 15).  In these area, reaching the 18ft contour was not attempted due to safety concerns for the vessel and sonar equipment.

See accompanying Holiday Layer file for more in depth details.</ns2:discussion><ns2:images><ns2:caption>MBES holiday, in red box, located proximal to a charted buoy block and a steep slope.</ns2:caption><ns2:link>file:///M:/SD927BH215/Surveys/F00668/Compilation/Report/F00668_DR_Office/Report%20Images/F00668%20True%20Holiday.png</ns2:link></ns2:images><ns2:images><ns2:caption>CARIS subset point cloud of charted 39 foot obstruction west of Gloucester Point to indicate a possible reason for the density holiday, in red, at that location. </ns2:caption><ns2:link>file:///M:/SD927BH215/Surveys/F00668/Compilation/Report/F00668_DR_Office/Report%20Images/F00668%2039%20Foot%20Density%20Holiday.png</ns2:link></ns2:images><ns2:images><ns2:caption>Density holiday, in pink, west of Delaware River Port Authority bulkhead.</ns2:caption><ns2:link>file:///M:/SD927BH215/Surveys/F00668/Compilation/Report/F00668_DR_Office/Report%20Images/F00668%20Density%20Holiday%20South%20of%20Bridge.png</ns2:link></ns2:images><ns2:images><ns2:caption>Density holiday, in pink, in southeastern area of Navy Anchorage (Anchorage 10).</ns2:caption><ns2:link>file:///M:/SD927BH215/Surveys/F00668/Compilation/Report/F00668_DR_Office/Report%20Images/F00668%20Third%20Density%20Holiday.png</ns2:link></ns2:images><ns2:images><ns2:caption>Location south of Delaware River Port Authority bulkhead where 18ft contour was not fully obtained with MBES data. Project outline requirements, in black, depths greater than 18ft, in green, and depths less than 18ft, in red.</ns2:caption><ns2:link>file:///M:/SD927BH215/Surveys/F00668/Compilation/Report/F00668_DR_Office/Report%20Images/F00668%20Failure%20To%20Reach%2018ft%20Contour.png</ns2:link></ns2:images><ns2:comments/></ns2:issue><ns2:comments/></ns1:additionalQualityControl></ns1:qualityControl><ns1:echoSoundingCorrections><ns1:corrections><ns2:results deviation="false"><ns2:discussion>All data reduction procedures conform to those detailed in the DAPR.</ns2:discussion></ns2:results><ns2:comments/></ns1:corrections><ns1:calibrations><ns2:results deviation="false"><ns2:discussion>All sounding systems were calibrated as detailed in the DAPR.</ns2:discussion><ns2:calibration xsi:nil="true"/></ns2:results><ns2:comments/></ns1:calibrations><ns1:additionalIssues><ns2:comments/></ns1:additionalIssues></ns1:echoSoundingCorrections><ns1:backscatter><ns2:results acquired="true"><ns2:discussion>Raw backscatter was logged as a Kongsberg .all file and has been sent to the Processing Branch.  Backscatter was not processed by the field unit.</ns2:discussion></ns2:results><ns2:comments/></ns1:backscatter><ns1:dataProcessing><ns1:softwareUpdates><ns1:featureObjectCatalog>The following Feature Object Catalog was used: NOAA Profile V_5_3_2.</ns1:featureObjectCatalog><ns1:discussion>There were no software configuration changes after the DAPR was submitted.</ns1:discussion><ns1:comments/></ns1:softwareUpdates><ns1:surfaces><ns1:surface><ns2:surfaceName>F00668_MBES_50cm_MLLW</ns2:surfaceName><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:resolution units="centimeters">50</ns2:resolution><ns2:depthRange><ns2:min units="meters">2.08</ns2:min><ns2:max units="meters">20.49</ns2:max></ns2:depthRange><ns2:surfaceParameter>NOAA_0.5m</ns2:surfaceParameter><ns2:purpose>Object Detection</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceName>F00668_MBES_50cm_MLLW_Finalized</ns2:surfaceName><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:resolution units="centimeters">50</ns2:resolution><ns2:depthRange><ns2:min units="meters">2.08</ns2:min><ns2:max units="meters">20.49</ns2:max></ns2:depthRange><ns2:surfaceParameter>NOAA_0.5m</ns2:surfaceParameter><ns2:purpose>Object Detection</ns2:purpose></ns1:surface><ns1:discussion>The surfaces have been reviewed where noisy data, or 'fliers' are incorporated into the gridded solution causing the surface to be shoaler than the true seafloor.  Where these spurious sounding cause the gridded surface to be shoaler than the reliably measured seabed by greater than the maximum allowable vertical uncertainty at that depth, the noise was rejected and the surface recomputed.

After reviewing the child &quot;depth&quot; layer, it was observed that there were 771 nodes that exceed 20m.  However, all of these nodes were located in an area that was above the Walt Whitman Bridge, outside of the the outline set fourth by the PI's (See Figure 16).  Since all of the nodes inside of the PI's project outline were less than 20m, only 50cm CUBE surfaces were created.</ns1:discussion><ns1:images><ns2:caption>Survey F00668 Project Instruction determined outline, in green, compared to 771 nodes that exceed 20m, outlined in red.</ns2:caption><ns2:link>file:///M:/SD927BH215/Surveys/F00668/Compilation/Report/F00668_DR_Office/Report%20Images/F00668%20Nodes%20that%20exceed%2020m.png</ns2:link></ns1:images><ns1:comments/></ns1:surfaces><ns1:additionalDataProcessing><ns2:comments/></ns1:additionalDataProcessing></ns1:dataProcessing></ns1:dataAcquisitionAndProcessing><ns1:verticalAndHorizontalControl><ns1:discussion>RTK was used for vertical control and the real time solution was written directly to the POSPac file.  In CARIS, a GPS tide was calculated during the &quot;Merge&quot; process, then a VDatum separation model was applied to reduce the data to MLLW.  </ns1:discussion><ns1:verticalControl><ns2:verticalDatum>Mean Lower Low Water</ns2:verticalDatum><ns2:standard_or_ERZT used="false"><ns2:tideStations/><ns2:correctorFiles/><ns2:finalTides><ns2:dateSubmitted xsi:nil="true"></ns2:dateSubmitted><ns2:dateReceived xsi:nil="true"></ns2:dateReceived></ns2:finalTides><ns2:discussion xsi:nil="true"></ns2:discussion><ns2:comments/></ns2:standard_or_ERZT><ns2:VDATUM_or_constantSep used="true"><ns2:methodsUsed>VDatum</ns2:methodsUsed><ns2:ellipsoidToChartDatumSepFile><ns2:fileName>2015_D927_VDatum_NAD83_MLLW.csar</ns2:fileName></ns2:ellipsoidToChartDatumSepFile><ns2:discussion>As referenced in Section B.5.3, VDatum was performed for this survey.  A separation file was provided to the field with the Project Instructions.  The separation file is included with the data submission of the DR.

The RTK solutions were used to calculate ellipsoid heights required for the VDatum process.  The RTK solution were written directly to the POSPac file via an NTRIP server, refer to the DAPR for further procedures.   </ns2:discussion><ns2:comments><ns2:branchComment concurrence="Concur with clarification"><ns2:comment>The Descriptive Report for F00668 does not contain Section B.5.3.</ns2:comment></ns2:branchComment></ns2:comments></ns2:VDATUM_or_constantSep><ns2:comments/></ns1:verticalControl><ns1:horizontalControl><ns2:horizontalDatum>North American Datum of 1983 (NAD83)</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="true"><ns2:discussion>RTK data was directly written to the POSPac file during acquisition.  These correctors were streamed using a Network Transport of RTCM via Internet Protocol (NTRIP) and were collected by the US Army Corps of Engineers Philadelphia District via their Virtual Reference System (VRS). The USACE  Virtual Reference System is a network of fourteen (USAGE operated and maintained) Continually Operating Reference Stations (CORS) in eastern Pennsylvania, New Jersey, Maryland, and Delaware.</ns2:discussion><ns2:comments/></ns2:RTK><ns2:DGPS used="false" xsi:nil="true"/><ns2:comments/></ns1:horizontalControl><ns1:additionalIssues><ns2:issue><ns2:title>RTK in Vertical Control</ns2:title><ns2:discussion>The RTK data, as detailed in section C.2, was used to further increase the accuracy associated with the vertical control by applying, in real time, atmospheric variations.</ns2:discussion><ns2:comments/></ns2:issue><ns2:comments/></ns1:additionalIssues></ns1:verticalAndHorizontalControl><ns1:resultsAndRecommendations><ns1:chartComparison><ns1:methods><ns2:discussion>A sounding selection was created, in feet, at a scale of 1:15000 from the F00668 Finalized 50cm resolution surface for comparison with raster Chart 12313 and ENC US5PA12M.  These soundings were then compared to each of the soundings located on the charts for continuity.

Soundings between Chart 12313 and ENC US5PA12M were compared and evaluated for agreement.  The two sources were found to be in close agreement with differences of one foot or less.</ns2:discussion><ns2:comments/></ns1:methods><ns1:charts><ns2:rasterChart><ns2:chart><ns2:number>12313</ns2:number><ns2:kapp>670</ns2:kapp><ns2:scale>15000</ns2:scale><ns2:edition>53</ns2:edition><ns2:editionDate>2012-05</ns2:editionDate><ns2:LNMDate>2015-11-19</ns2:LNMDate><ns2:NMDate>2015-11-19</ns2:NMDate></ns2:chart><ns2:discussion>NOAA Chart 12313 overlaps with all F00668 data and is generally one to two feet shallower than F00668 in the southern, Navy Anchorage (Anchorage 10), section of the survey (Figure 17), and one to three feet shallower than the northern, Gloucester Point, section of the survey (Figure 18).  The data for the area off of Gloucester Point, between the southern tip of the Delaware River Port Authority's bulkhead, south, to the Gloucester Point Fuel Terminal's southern mooring structure indicates that scouring is occurring.  In this area the F00668 data is two to ten feet deeper than charted depths (See Figure 19).</ns2:discussion><ns2:images><ns2:caption>F00668 soundings, in red, compared with sounding from Chart 12313 of the Navy Anchorage (Anchorage 10) section of the survey, in black.  Soundings are in feet.  </ns2:caption><ns2:link>file:///M:/SD927BH215/Surveys/F00668/Compilation/Report/F00668_DR_Office/Report%20Images/F00668%20RNC%20Compare%20Navey%20Yard.png</ns2:link></ns2:images><ns2:images><ns2:caption>F00668 soundings, in red, compared with sounding from Chart 12313 of the Gloucester Point section of the survey, in black.  Soundings are in feet.  </ns2:caption><ns2:link>file:///M:/SD927BH215/Surveys/F00668/Compilation/Report/F00668_DR_Office/Report%20Images/F00668%20RNC%20Compare%20Gloucester%20Point.png</ns2:link></ns2:images><ns2:images><ns2:caption>F00668 soundings, in red, compared with soundings from Chart 12313, in black.  Subset taken from area off of Gloucester Point, indicating scouring.  Soundings are in feet.</ns2:caption><ns2:link>file:///M:/SD927BH215/Surveys/F00668/Compilation/Report/F00668_DR_Office/Report%20Images/F00668%20Gloucester%20Point%20Scour.png</ns2:link></ns2:images><ns2:comments/></ns2:rasterChart><ns2:ENC><ns2:chart><ns2:name>US5PA12M</ns2:name><ns2:scale>15000</ns2:scale><ns2:edition>27</ns2:edition><ns2:updateApplicationDate>2015-12-01</ns2:updateApplicationDate><ns2:issueDate>2015-12-01</ns2:issueDate><ns2:preliminary>false</ns2:preliminary></ns2:chart><ns2:discussion>Analysis shows ENC US5PA12M to be in good agreement with F00668 data, within one to two feet, in the Navy Anchorage (Anchorage 10) section of the survey (See Figure 20), and generally in good agreement, within one to three feet, in the Gloucester Point section of the survey (See Figure 21).  As with the RNC comparison, the data for the area off of Gloucester Point, between the southern tip of the Delaware River Port Authority's bulkhead, south, to the Gloucester Point Fuel Terminal's southern mooring structure indicates that scouring is occurring.  In this area the F00668 data is two to four feet deeper than charted depths (See Figure 22).
</ns2:discussion><ns2:images><ns2:caption>F00668 soundings, in red, compared with sounding from NOAA ENC US5PA12M of the Navy Anchorage (Anchorage 10) section of the survey, in black.  Soundings are in feet.  </ns2:caption><ns2:link>file:///M:/SD927BH215/Surveys/F00668/Compilation/Report/F00668_DR_Office/Report%20Images/F00668%20ENC%20Compare%20Navy%20Yard.png</ns2:link></ns2:images><ns2:images><ns2:caption>F00668 soundings, in red, compared with sounding from NOAA ENC US5PA12M of the Gloucester Point section of the survey, in black.  Soundings are in feet.  </ns2:caption><ns2:link>file:///M:/SD927BH215/Surveys/F00668/Compilation/Report/F00668_DR_Office/Report%20Images/F00668%20ENC%20Gloucester%20Point.png</ns2:link></ns2:images><ns2:images><ns2:caption>F00668 soundings, in red, compared with soundings from NOAA ENC US5PA12M, in black.  Subset taken from area off of Gloucester Point, indicating scouring.  Soundings are in feet.</ns2:caption><ns2:link>file:///M:/SD927BH215/Surveys/F00668/Compilation/Report/F00668_DR_Office/Report%20Images/F00668%20Gloucester%20Point%20Scour%20ENC.png</ns2:link></ns2:images><ns2:comments/></ns2:ENC><ns2:comments/></ns1:charts><ns1:AWOISItems><ns2:results investigated="None Exist"><ns2:discussion>No AWOIS items were assigned for this survey.</ns2:discussion></ns2:results><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> There were fifteen assigned charted features and two unassigned charted features in F00668.  Eight of the features were inside the three meter curve and unapproachable by R/V BAY HYDRO II.  These features, all of which are charted as dolphins, were given a cursory visual inspection.  Six of these dolphins were not visible above the water line, while the remaining two were seen.  Five of the remaining seven features were mooring platforms, see section D.2.7 of this document for further information.  The remaining two features were submerged obstructions, were ensonified using MBES, and were found to be in good agreement with the chart (within one to two feet).  Photographs and further details can be found in the Final Feature File accompanying this submission.</ns2:discussion></ns2:results><ns2:comments/></ns1:chartedFeatures><ns1:unchartedFeatures><ns2:results investigated="Exist - Not Investigated"><ns2:discussion>Uncharted features exist for this survey, but were not investigated because of vessel limitations.  The uncharted feature was a linear series of nine dolphins that extended approximately 88m from the shore, on the western side of Delaware River, approximately 67m south (down river) of a charted pier; in the Navy Anchorage (Anchorage 10).  The approximate location and description of the features are included in the Final Feature File associated with this submission. </ns2:discussion></ns2:results><ns2:comments/></ns1:unchartedFeatures><ns1:DTONS><ns2:results reportSubmitted="false"><ns2:numberSubmitted xsi:nil="true"></ns2:numberSubmitted><ns2:discussion>No Danger to Navigation Reports were submitted for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:DTONS><ns1:shoalAndHazardousFeatures><ns2:results investigated="None Exist"><ns2:discussion>No shoals or potentially hazardous features exist for this survey.</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><ns2:branchComment concurrence="Do not concur"><ns2:comment>Three (3) anchorage areas exist within the survey limits of F00668 and are denoted as Anchorage Area 10, 11, and 12 on NOS chart 12313.</ns2:comment></ns2:branchComment></ns2:comments></ns1:channels><ns1:bottomSamples><ns2:results investigated="Investigated"><ns2:discussion>Five bottom samples were acquired for this survey, see the Final Feature File for further details.</ns2:discussion></ns2:results><ns2:comments/></ns1:bottomSamples></ns1:chartComparison><ns1:additionalResults><ns1:shoreline><ns2:results investigated="None Exist"><ns2:discussion>Shoreline was not assigned in the Hydrographic Survey Project Instructions or Statement of Work.</ns2:discussion></ns2:results><ns2:comments><ns2:branchComment concurrence="Do not concur"><ns2:comment>Limited Shoreline Verification was assigned in the Project Instructions and conducted as part of survey F00668.</ns2:comment></ns2:branchComment></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>One unassigned ATON was in F00668.  It was found to be on station and serving its intended purpose.  See the Final Feature File for further details.</ns2:discussion></ns2:results><ns2:comments/></ns1:ATONS><ns1:overheadFeatures><ns2:results investigated="Exist - Not Investigated"><ns2:discussion>Overhead features exist for this survey, but were not investigated.  This overhead feature was the Walt Whitman bridge which delineated the northern (up river) edge of the survey area, and was not inside the survey area.</ns2:discussion></ns2:results><ns2:comments/></ns1:overheadFeatures><ns1:submarineFeatures><ns2:results investigated="Investigated"><ns2:discussion>A charted submerged sewer pipe runs perpendicular to the shoreline from the New Jersey (eastern side) of the Delaware River, at the southern edge of Gloucester Point, to approximately 229m off shore.  This sewer pipe was not visible in the MBES data of the area.</ns2:discussion></ns2:results><ns2:comments/></ns1:submarineFeatures><ns1:ferryRoutesAndTerminals><ns2:results investigated="Exist - Not Investigated"><ns2:discussion>Ferry routes and/or terminals exist for this survey, but were not investigated (See Figure 23).</ns2:discussion><ns2:images><ns2:caption>Charted ferry terminal at southern edge of Navy Anchorage, Anchorage 10.</ns2:caption><ns2:link>file:///M:/SD927BH215/Surveys/F00668/Compilation/Report/F00668_DR_Office/Report%20Images/Ferry%20Terminal.JPG</ns2:link></ns2:images></ns2:results><ns2:comments/></ns1:ferryRoutesAndTerminals><ns1:platforms><ns2:results investigated="Investigated"><ns2:discussion>Five mooring platforms were assigned in F00668.  After investigation, all were found to be accurately charted.  See the Final Feature File for more information.</ns2:discussion></ns2:results><ns2:comments><ns2:branchComment concurrence="Do not concur"><ns2:comment>Four (4) production platforms were assigned for investigation as part of F00668 and were submitted with the Final Feature File.</ns2:comment></ns2:branchComment></ns2:comments></ns1:platforms><ns1:significantFeatures><ns2:results investigated="Investigated"><ns2:discussion>There are significant features within the F00668 survey area, however, zero currently uncharted features were found.  See Final Feature File for further detail.</ns2:discussion></ns2:results><ns2:comments/></ns1:significantFeatures><ns1:constructionOrDredging><ns2:results investigated="Exist - Not Investigated"><ns2:discussion>Present and/or planned construction or dredging exists within the survey limits, but was not investigated.</ns2:discussion></ns2:results><ns2:comments/></ns1:constructionOrDredging><ns1: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, 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>Robert Mowery</ns2:approverName><ns2:approverTitle>Chief of Party</ns2:approverTitle><ns2:approvalDate>2015-12-21</ns2:approvalDate></ns1:signingPersonnel></ns1:approvalSheet></ns1:descriptiveReport>