<?xml version="1.0" encoding="UTF-8"?><ns1:descriptiveReport xmlns:ns1="http://svn.pydro.noaa.gov/2015/02/DescriptiveReport" xmlns:ns2="http://svn.pydro.noaa.gov/2015/02/AllGlobalTypes" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><ns1:metadata><ns1:projectMetadata><ns2:number>OPR-D302-TJ-15</ns2:number><ns2:name>Chincoteague Inlet</ns2:name><ns2:generalLocality>Coastal Virginia</ns2:generalLocality><ns2:fieldUnit>NOAA Ship THOMAS JEFFERSON</ns2:fieldUnit></ns1:projectMetadata><ns1:registryMetadata><ns2:registryNumber>H12856</ns2:registryNumber><ns2:sheetID>4</ns2:sheetID><ns2:registryInstructions> </ns2:registryInstructions><ns2:sublocality>Approach to Chincoteague Inlet </ns2:sublocality><ns2:stateOrTerritory>Virginia</ns2:stateOrTerritory><ns2:country>United States</ns2:country><ns2:scale>10000</ns2:scale></ns1:registryMetadata><ns1:surveyMetadata><ns2:year>2015</ns2:year><ns2:chiefOfParty>Shepard M. Smith, CAPT/NOAA</ns2:chiefOfParty><ns2:projectType>Navigable Area</ns2:projectType><ns2:PIDate>2015-12-04</ns2:PIDate><ns2:datesOfSurvey><ns2:start>2015-12-07</ns2:start><ns2:end>2015-12-16</ns2:end></ns2:datesOfSurvey><ns2:equipmentTypes><ns2:soundingEquipment>Multibeam Echo Sounder</ns2:soundingEquipment><ns2:soundingEquipment>Singlebeam 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="18N">Universal Transverse Mercator (UTM)</ns2:horizontalCoordinateSystem><ns2:timeZone>UTC</ns2:timeZone><ns2:verifier>Atlantic 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>Survey H12856 was conducted in the Coastal Virginia waters in the Approach to Chincoteague Inlet.</ns2:discussion><ns2:limits><ns2:northWest><ns2:latitude hemisphere="N">37.8973955556</ns2:latitude><ns2:longitude hemisphere="W">75.4080469444</ns2:longitude></ns2:northWest><ns2:southEast><ns2:latitude hemisphere="N">37.8485466667</ns2:latitude><ns2:longitude hemisphere="W">75.2659561111</ns2:longitude></ns2:southEast></ns2:limits><ns2:images><ns2:caption>H12856 Survey Limits overlaid on RNC 12210.</ns2:caption><ns2:link>file:///H:/Surveys/OPR-D302-TJ-15/H12856/Data/Separates/Descriptive_Report/DR%20Multimedia/H12856_Coverage_Limits.jpg</ns2:link></ns2:images><ns2:comments/></ns1:areaDescription><ns1:surveyLimits><ns2:results deviation="true"><ns2:discussion>Survey H12856 consolidated sheet H12855 into its survey limits. This was done to more easily collect and package the data for the investigations of sheet H12855, since its limits resided within H12856 limits. Sheet H12856 absorbed approximately 1.75 square miles of the northern portion of sheet H12854 to allow survey vessel S222 safe maneuvering near the shoals present at the junction of sheets H12856 and H12854.

Additionally, the entirety of sheet H12856 survey limits were not surveyed per project instructions due to time constraints, hazardous conditions not accessible by survey vessels, and lack of proper survey equipment by survey platforms aboard S222. </ns2:discussion><ns2:images><ns2:caption>H12855 Survey limits consolidated into H12856 overlaid on RNC 12210.</ns2:caption><ns2:link>file:///H:/Surveys/OPR-D302-TJ-15/H12856/Data/Separates/Descriptive_Report/DR%20Multimedia/H12855_Coverage_Limits.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>Area of H12854 absorbed by H12856. Approximately 1.75 square miles.</ns2:caption><ns2:link>file:///H:/Surveys/OPR-D302-TJ-15/H12856/Data/Separates/Descriptive_Report/DR%20Multimedia/Junction_2_H12856_H12854_absorbed.jpg</ns2:link></ns2:images></ns2:results><ns2:comments/></ns1:surveyLimits><ns1:surveyPurpose><ns2:discussion>Survey data from this project is intended to supersede all prior survey data in the common area. Hydrographic holdings in this area date back to 1930 and prior. Local constituents have raised concern over the accuracy of this data and the ability to safely navigate. In addition, lidar analysis has shown significant shoal movement in shallow areas and cause concern that this is occurring in deeper stretches. This project will cover approximately 86 square nautical miles of navigationally significant area as identified in the 2012 NOAA Hydrographic Survey Priorities (NHSP).</ns2:discussion><ns2:comments/></ns1:surveyPurpose><ns1:surveyQuality><ns2:adequacy>The entire survey is adequate to supersede previous data.</ns2:adequacy><ns2:discussion>Although the entirety of the sheet limits were not surveyed, all data collected are adequate to supersede previous data due to the inaccuracy of previous charts and the long time span between surveys conducted.</ns2:discussion><ns2:comments/></ns1:surveyQuality><ns1:surveyCoverage><ns2:coverageRequirement><ns2:waterDepth>Inshore limit to 4 meters water depth</ns2:waterDepth><ns2:requiredCoverage>100m Set line spacing. Indications of shoaling falling between set line spacing main scheme lines must be investigated. Set line spacing orientation should be approximately perpendicular to countours whenever possible. Refer to HSSD Section 5.2.2.3</ns2:requiredCoverage></ns2:coverageRequirement><ns2:coverageRequirement><ns2:waterDepth>Greater than 4 meters water depth</ns2:waterDepth><ns2:requiredCoverage>Complete Coverage accomplished using either: A) Complete coverage MBES depth and backscatter data, or B) 100% SSS coverage with concurrent set line spacing MBES depth and backscatter data. Refer to HSSD Section 5.2.2.2 </ns2:requiredCoverage></ns2:coverageRequirement><ns2:results deviation="true"><ns2:discussion>Survey H12856 exceeded the specifications set by the Project Instructions by utilizing an 80 meter set line spacing for all vessels in waters less than 4 meters in depth, rather than utilizing the minimum 100 meter line spacing defined in the Project Instructions. This allowed for a tighter coverage over shallow areas, more easily defining where additional coverage was needed. This also allowed for the survey launches to acquire side scan sonar with concurrent multibeam data at a 50 meter range scale with proper overlap. 

Survey H12856 was approached as a highly dynamic and virtually unknown area. Due to the date of the last survey, shifting shoals and various natural hazards, the field ran exploration lines collected by the two launches spaced at 160 meters. Once areas were expanded upon and evaluated by priority determined by the Chief Scientist, the vessels collected data at 80 meter line spacing at minimum. Due to operational, environmental, and temporal constraints, however, not all exploratory lines were filled with the minimum 80 meter lines spacing. Regardless of the completion of the 100% set line spacing data, it is recommended that all H12856 survey data supersede existing chart information.</ns2:discussion><ns2:images><ns2:caption>Area coverage specifications. 40 meters vertical beam line spacing, junctioning 80 meter multi beam data.</ns2:caption><ns2:link>file:///H:/Surveys/OPR-D302-TJ-15/H12856/Data/Separates/Descriptive_Report/DR%20Multimedia/exceeding_coverage.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>80 meter line spacing utilized inshore of the 12 foot contour.</ns2:caption><ns2:link>file:///H:/Surveys/OPR-D302-TJ-15/H12856/Data/Separates/Descriptive_Report/DR%20Multimedia/Spec_line_spacing_1.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>Central portion of Chinctogeaue Inlet with partial coverage.</ns2:caption><ns2:link>file:///H:/Surveys/OPR-D302-TJ-15/H12856/Data/Separates/Descriptive_Report/DR%20Multimedia/Partial_coverage_1.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>Western portion Chinctogeaue Inlet with partial coverage.</ns2:caption><ns2:link>file:///H:/Surveys/OPR-D302-TJ-15/H12856/Data/Separates/Descriptive_Report/DR%20Multimedia/Partial_coverage_2.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>Southeast portion outer Chinctogeaue Inlet with partial coverage.</ns2:caption><ns2:link>file:///H:/Surveys/OPR-D302-TJ-15/H12856/Data/Separates/Descriptive_Report/DR%20Multimedia/Partial_coverage_3.jpg</ns2:link></ns2:images></ns2:results><ns2:comments/></ns1:surveyCoverage><ns1:coverageGraphic><ns2:caption>H12856 total coverage area.</ns2:caption><ns2:link>file:///H:/Surveys/OPR-D302-TJ-15/H12856/Data/Separates/Descriptive_Report/DR%20Multimedia/H12856_Coverage_Limits_2.jpg</ns2:link></ns1:coverageGraphic><ns1:coverageGraphic><ns2:caption>VB data approximately 4.5 nautical miles East of Assateague Beach, absorbed from sheet H12855.</ns2:caption><ns2:link>file:///H:/Surveys/OPR-D302-TJ-15/H12856/Data/Separates/Descriptive_Report/DR%20Multimedia/H12856_Coverage_Limits_3.jpg</ns2:link></ns1:coverageGraphic><ns1:surveyStatistics><ns2:LNM><ns2:vesselLNM><ns2:vessel><ns2:hullID>3101</ns2:hullID><ns2:statistics><ns2:MS_SBES>0</ns2:MS_SBES><ns2:MS_MBES>0.52</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>132.91</ns2:MS_MBES_SSS><ns2:MS_SBES_SSS>0</ns2:MS_SBES_SSS><ns2:XL_MBES_SBES>7.84</ns2:XL_MBES_SBES><ns2:XL_lidar>0</ns2:XL_lidar></ns2:statistics></ns2:vessel><ns2:vessel><ns2:hullID>3102</ns2:hullID><ns2:statistics><ns2:MS_SBES>0</ns2:MS_SBES><ns2:MS_MBES>11.71</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>28.71</ns2:MS_MBES_SSS><ns2:MS_SBES_SSS>0</ns2:MS_SBES_SSS><ns2:XL_MBES_SBES>0</ns2:XL_MBES_SBES><ns2:XL_lidar>0</ns2:XL_lidar></ns2:statistics></ns2:vessel><ns2:vessel><ns2:hullID>Z-1</ns2:hullID><ns2:statistics><ns2:MS_SBES>17.84</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>0</ns2:MS_MBES_SSS><ns2:MS_SBES_SSS>0</ns2:MS_SBES_SSS><ns2:XL_MBES_SBES>4.04</ns2:XL_MBES_SBES><ns2:XL_lidar>0</ns2:XL_lidar></ns2:statistics></ns2:vessel><ns2:vessel><ns2:hullID>Z-2</ns2:hullID><ns2:statistics><ns2:MS_SBES>33.95</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>0</ns2:MS_MBES_SSS><ns2:MS_SBES_SSS>0</ns2:MS_SBES_SSS><ns2:XL_MBES_SBES>3.70</ns2:XL_MBES_SBES><ns2:XL_lidar>0</ns2:XL_lidar></ns2:statistics></ns2:vessel></ns2:vesselLNM><ns2:totalLNM><ns2:MS_SBES>51.79</ns2:MS_SBES><ns2:MS_MBES>12.23</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>161.62</ns2:MS_MBES_SSS><ns2:MS_SBES_SSS>0</ns2:MS_SBES_SSS><ns2:XL_MBES_SBES>15.58</ns2:XL_MBES_SBES><ns2:XL_lidar>0</ns2:XL_lidar><ns2:percentXLLNM>6</ns2:percentXLLNM></ns2:totalLNM></ns2:LNM><ns2:totalSurveyStats><ns2:bottomSamples>7</ns2:bottomSamples><ns2:maritimeBoundaryPoints>0</ns2:maritimeBoundaryPoints><ns2:DP>0</ns2:DP><ns2:diveOps>0</ns2:diveOps><ns2:SNM>9.79</ns2:SNM></ns2:totalSurveyStats><ns2:surveyDates>2015-12-08</ns2:surveyDates><ns2:surveyDates>2015-12-09</ns2:surveyDates><ns2:surveyDates>2015-12-10</ns2:surveyDates><ns2:surveyDates>2015-12-11</ns2:surveyDates><ns2:surveyDates>2015-12-12</ns2:surveyDates><ns2:surveyDates>2015-12-13</ns2:surveyDates><ns2:surveyDates>2015-12-14</ns2:surveyDates><ns2:surveyDates>2015-12-15</ns2:surveyDates><ns2:surveyDates>2015-12-16</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>3101</ns2:hullID><ns2:LOA units="feet">31</ns2:LOA><ns2:draft units="feet">5.2</ns2:draft></ns1:vessel><ns1:vessel><ns2:hullID>3102</ns2:hullID><ns2:LOA units="meters">31</ns2:LOA><ns2:draft units="meters">5.2</ns2:draft></ns1:vessel><ns1:vessel><ns2:hullID>Z-1</ns2:hullID><ns2:LOA units="feet">5.5</ns2:LOA><ns2:draft units="feet">1.0</ns2:draft></ns1:vessel><ns1:vessel><ns2:hullID>Z-2</ns2:hullID><ns2:LOA units="feet">5.5</ns2:LOA><ns2:draft units="feet">1.0</ns2:draft></ns1:vessel><ns1:discussion>Data was acquired by 3101, 3102, Z-1 and Z-2. 3101 and 3102 collected Reson multibeam echosounder soundings, multibeam backscatter data; side scan sonar imagery, sound velocity profiles, surface sound speed readings, and position and attitude data. Z-1 and Z-2 collected Odom Verticalbeam data and position data.</ns1:discussion><ns1:comments/></ns1:vessels><ns1:equipment><ns1:majorSystem><ns2:manufacturer>Reson</ns2:manufacturer><ns2:model>7125-SV1</ns2:model><ns2:type>MBES</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>Reson</ns2:manufacturer><ns2:model>7125-SV2</ns2:model><ns2:type>MBES</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>Odom</ns2:manufacturer><ns2:model>CV100</ns2:model><ns2:type>SBES</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>Klein</ns2:manufacturer><ns2:model>5000 v1</ns2:model><ns2:type>SSS</ns2:type></ns1:majorSystem><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>SP351 DGPS Beacon</ns2:model><ns2:type>Positioning System</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>Seabird</ns2:manufacturer><ns2:model>SBE 19+</ns2:model><ns2:type>Conductivity, Temperature, and Depth Sensor</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>Reson </ns2:manufacturer><ns2:model>SV-70</ns2:model><ns2:type>Sound Speed System</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>Reson</ns2:manufacturer><ns2:model>SV-71</ns2:model><ns2:type>Sound Speed System</ns2:type></ns1:majorSystem><ns1:discussion>Vessel configurations, equipment operations, and data acquisition &amp; processing were consistent with specifications described in the DAPR.</ns1:discussion><ns1:comments/></ns1:equipment><ns1:comments/></ns1:equipmentAndVessels><ns1:qualityControl><ns1:crosslines><ns2:discussion>ASVs Z-1 and Z-2 collected 14.9% in crosslines against their own vertical beam data. Survey launch 3101 collected 4.5 % in crosslines against its own data. 3102 did not collected crosslines due to time constraints, as well as its primary use as a launching and tending platform for Z-Boat operations. In all, crosslines acquired for this survey totaled 6.0% of mainscheme acquisition.

Crosslines were compared to mainscheme using finalized difference surfaces at their pertaining resolutions, created in CARIS HIPS &amp; SIPS. Vertical beam data was compared using surfaces H12856_VB_4m_MLLW_XL_Finalized.csar and H12856_VB_4m_MLLLW_Finalized.csar. A total of 99.9% of 4,991 of nodes were within 0.33 m of each other. Multibeam data was compared using surfaces H12856_MB_1m_MLLW_XL_Finalized.csar and H12856_MB_1m_MLLW_Finalized.csar. A total of 99.9% of 576,491 nodes were within 0.33 m of each other.</ns2:discussion><ns2:images><ns2:caption>H12856 Vertical Beam crossline vs. mainscheme difference statistics.</ns2:caption><ns2:link>file:///H:/Surveys/OPR-D302-TJ-15/H12856/Data/Separates/Descriptive_Report/DR%20Multimedia/H12856_VB_4m_XL_MS_Diff_Stats.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>H12856 Multibeam crossline vs. mainscheme difference statistics. </ns2:caption><ns2:link>file:///H:/Surveys/OPR-D302-TJ-15/H12856/Data/Separates/Descriptive_Report/DR%20Multimedia/H12856_MB_1m_XL_MS_Diff_Stats.jpg</ns2:link></ns2:images><ns2:comments/></ns1:crosslines><ns1:uncertainty><ns2:values><ns2:tideUncertainty><ns2:measured units="meters">0</ns2:measured><ns2:zoning units="meters">0.09</ns2:zoning><ns2:tideMethod>VDATUM</ns2:tideMethod></ns2:tideUncertainty><ns2:tideUncertainty><ns2:measured units="meters">0</ns2:measured><ns2:zoning units="meters">0</ns2:zoning><ns2:tideMethod>TCARI</ns2:tideMethod></ns2:tideUncertainty><ns2:soundSpeedUncertainty><ns2:hullID>3101</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.2</ns2:surface></ns2:soundSpeedUncertainty><ns2:soundSpeedUncertainty><ns2:hullID>3102</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.2</ns2:surface></ns2:soundSpeedUncertainty><ns2:soundSpeedUncertainty><ns2:hullID>Z-1</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.2</ns2:surface></ns2:soundSpeedUncertainty><ns2:soundSpeedUncertainty><ns2:hullID>Z-2</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.2</ns2:surface></ns2:soundSpeedUncertainty></ns2:values><ns2:discussion>Total Propagated Uncertainty values for survey H12856 were derived using a combination of: real time uncertainties for vessel motion; a priori values for equipment and vessel characteristics; an a priori value for the separation model used to reduce soundings to chart datum; and field assigned values for sound speed uncertainties. The realtime uncertainties for vessel motion include roll, pitch, gyro, navigation, and elevation. The uncertainties in these measurements were recorded as part of the POSPac Marinestar 5P 3D positional solution, as well as the POSPac Marinestar IAPPK solution, and were applied to the soundings via an SBET RMS file generated by Applanix POSPac. Uncertainties for sonar mounting and vessel speed were based on Appendix 4, table 4.9 of the NOAA Field Procedures Manual (FPM) (ed 2014). These were applied to the data via the CARIS HIPS Hydrographic Vessel File. The uncertainty associated with the VDatum separation model was supplied by the Hydrographic Services Division’s Operations Branch, and is listed under the Zoning (see Table 6). Finally, the uncertainty associated with sound speed measurements were based on the frequency and location of CTD casts, in accordance with the guidance set by Appendix 4 of the FPM (ed 2014) (see Table 7).

Total Propagated Uncertainty was then evaluated to ensure compliance with section 5.1.3 of NOAA's Hydrographic Survey Specification and Deliverables (HSSD). First the maximum allowable uncertainty for each node was calculated using the equation: -Uncertainty/((0.5^2+((Depth*0.013)^2))^0.5). Second the ratio between actual uncertainty and maximum allowed uncertainty is found for each node. The resulting 'TVU_QC' layer was filtered using a color map to show any areas where actual uncertainty exceeded the maximum allowed uncertainty. Additionally the Pydro Finalized CSAR QA tool was utilized for each surface to be submitted. For H12856_MB_1m_MLLW_Final.csar, 100% of 12,553,976 nodes passed uncertainty standards. For H12856_MB_50cm_MLLW_Final.csar, 100% of 1,559,736 nodes passed uncertainty standards. For H12856_VB_4m_MLLW_Final.csar, 98.4% of 32,549 nodes passed uncertainty standards.

Areas of high uncertainty, visible on surfaces H12856_MB_1m_MLLW_Finalized and H12856_Combined_4m_MLLW_Finalized, arise mostly in the outer beams on lines run as set line spacing. development areas, as well as days which positioning was processed and applied utilizing Fugro Marinestar 5p solutions. </ns2:discussion><ns2:images><ns2:caption>H12856_MB_1m_MLLW_Finalized_TVU_QC uncertainty standards utilizing Pydro Finalized CSAR QA.</ns2:caption><ns2:link>file:///H:/Surveys/OPR-D302-TJ-15/H12856/Data/Separates/Descriptive_Report/DR%20Multimedia/H12856_MB_1m_MLLW_Finalized_TVU_QC.png</ns2:link></ns2:images><ns2:images><ns2:caption>H12856_MB_50cm_MLLW_Finalized_TVU_QC uncertainty standards utilizing Pydro Finalized CSAR QA.</ns2:caption><ns2:link>file:///H:/Surveys/OPR-D302-TJ-15/H12856/Data/Separates/Descriptive_Report/DR%20Multimedia/H12856_MB_50cm_MLLW_Finalized_TVU_QC.png</ns2:link></ns2:images><ns2:images><ns2:caption>H12856_VB_4m_MLLW_Finalized_TVU_QC uncertainty standards utilizing Pydro Finalized CSAR QA.</ns2:caption><ns2:link>file:///H:/Surveys/OPR-D302-TJ-15/H12856/Data/Separates/Descriptive_Report/DR%20Multimedia/H12856_VB_4m_MLLW_Finalized_TVU_QC.png</ns2:link></ns2:images><ns2:images><ns2:caption>Area in North exhibiting high uncertainty was run as a search development. Area in South is a development of submerged piles utilizing a 5P solution.</ns2:caption><ns2:link>file:///H:/Surveys/OPR-D302-TJ-15/H12856/Data/Separates/Descriptive_Report/DR%20Multimedia/Uncertainty.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>Lines exhibiting high uncertainty in the outer beams. Area in the South is a development over an unknown object utilizing a 5P solution.</ns2:caption><ns2:link>file:///H:/Surveys/OPR-D302-TJ-15/H12856/Data/Separates/Descriptive_Report/DR%20Multimedia/Uncertainty_2.jpg</ns2:link></ns2:images><ns2:comments/></ns1:uncertainty><ns1:junctions><ns2:discussion>One contemporary survey, H12854, junctions H12856. Two historic surveys, H12094 and H12092, conducted in 2009, junction H12856.</ns2:discussion><ns2:images><ns2:caption>Survey junctions to H12856.</ns2:caption><ns2:link>file:///H:/Surveys/OPR-D302-TJ-15/H12856/Data/Separates/Descriptive_Report/DR%20Multimedia/Junctions_1.jpg</ns2:link></ns2:images><ns2:junction><ns2:survey><ns2:registryNumber>H12092</ns2:registryNumber><ns2:scale>20000</ns2:scale><ns2:year>2009</ns2:year><ns2:fieldUnit>SAIC</ns2:fieldUnit><ns2:relativeLocation>S</ns2:relativeLocation></ns2:survey><ns2:discussion>Although sheet H12092 does junction with a small portion of H12856, no comparison is available. Due to time constraints and the distance from the high priority area of the inlet no survey data was collected in that area.</ns2:discussion><ns2:images><ns2:caption>H12856 junction area to H12092.</ns2:caption><ns2:link>file:///H:/Surveys/OPR-D302-TJ-15/H12856/Data/Separates/Descriptive_Report/DR%20Multimedia/Junctions_4_H12092.jpg</ns2:link></ns2:images><ns2:comments/></ns2:junction><ns2:junction><ns2:survey><ns2:registryNumber>H12094</ns2:registryNumber><ns2:scale>20000</ns2:scale><ns2:year>2009</ns2:year><ns2:fieldUnit>SAIC</ns2:fieldUnit><ns2:relativeLocation>E</ns2:relativeLocation></ns2:survey><ns2:discussion>The difference between H12856 and H12094 ranged from -3.3 m to 2.3 m with a mean of 0.2 m and a standard deviation of 0.6 m. 64.2% of 65,744 nodes were within 0.33 m of each other. This low percentage is most like due to the 6 year difference in survey dates in such a dynamic area.</ns2:discussion><ns2:images><ns2:caption>H12856 junction area to H12094.</ns2:caption><ns2:link>file:///H:/Surveys/OPR-D302-TJ-15/H12856/Data/Separates/Descriptive_Report/DR%20Multimedia/Junctions_2_H12094.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>Difference statistics comparing H12856 to H12094.</ns2:caption><ns2:link>file:///H:/Surveys/OPR-D302-TJ-15/H12856/Data/Separates/Descriptive_Report/DR%20Multimedia/junction_stats_H12856_H12094.jpg</ns2:link></ns2:images><ns2:comments/></ns2:junction><ns2:junction><ns2:survey><ns2:registryNumber>H12854</ns2:registryNumber><ns2:scale>10000</ns2:scale><ns2:year>2015</ns2:year><ns2:fieldUnit>NOAA Ship THOMAS JEFFERSON</ns2:fieldUnit><ns2:relativeLocation>SE</ns2:relativeLocation></ns2:survey><ns2:discussion>The difference between survey H12856 and H12854 ranged from -2.424 m to 2.106 m with a mean of 0.028 m and a standard deviation of 0.103 m. 99.9% of 266,520 nodes were within 0.33 m of each other. The wide range of vertical differences between H12856 and H12854 arises over a development conducted by both vessels. In  </ns2:discussion><ns2:images><ns2:caption>H12856 junction area to H12854.</ns2:caption><ns2:link>file:///H:/Surveys/OPR-D302-TJ-15/H12856/Data/Separates/Descriptive_Report/DR%20Multimedia/Junctions_3_H12854.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>Difference statistics comparing H12856 to H12854.</ns2:caption><ns2:link>file:///H:/Surveys/OPR-D302-TJ-15/H12856/Data/Separates/Descriptive_Report/DR%20Multimedia/junction_stats_H12856_854.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>Area of greatest vertical difference between H12856 &amp; H12854.</ns2:caption><ns2:link>file:///H:/Surveys/OPR-D302-TJ-15/H12856/Data/Separates/Descriptive_Report/DR%20Multimedia/junction_stats_H12856_854_2.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>Development over same object by 3102 for H12856 and S222 for H12854. </ns2:caption><ns2:link>file:///H:/Surveys/OPR-D302-TJ-15/H12856/Data/Separates/Descriptive_Report/DR%20Multimedia/junction_stats_H12856_854_3.jpg</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="true"><ns2:issue><ns2:title>Sea States Effects</ns2:title><ns2:discussion>Survey day number 345 for vessel 3101 exhibits sound velocity artifacts in the data located south of Fishing Point shoreline. This day logged substantial swell from the South, creating notable motion in the survey lines running North and South. The line segments in waters closer to the shore, depths 7.0 m and less, display the these sound velocity artifacts the most. Once 3101 was in depths 8.0 m and greater the sound velocity artifacts are negligible.</ns2:discussion><ns2:images><ns2:caption>Geographic location of sound velocity artifacts.</ns2:caption><ns2:link>file:///H:/Surveys/OPR-D302-TJ-15/H12856/Data/Separates/Descriptive_Report/DR%20Multimedia/Motion_artifacts_2.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>Close up view of sound velocity artifacts. Vertical exaggeration set at 20. </ns2:caption><ns2:link>file:///H:/Surveys/OPR-D302-TJ-15/H12856/Data/Separates/Descriptive_Report/DR%20Multimedia/Motion_artifacts_1.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>Subset view of sound velocity artifacts. Note the symmetrical curl on the outer edges indicating these errors.</ns2:caption><ns2:link>file:///H:/Surveys/OPR-D302-TJ-15/H12856/Data/Separates/Descriptive_Report/DR%20Multimedia/Motion_artifacts_3.jpg</ns2:link></ns2:images><ns2:comments/></ns2:issue><ns2:issue><ns2:title>3101 and 3102 Vertical Offsets</ns2:title><ns2:discussion>Survey vessels 3101, and 3102 collected positioning data via POSMV units with Fugro Marinestar Precise Point Positioning raw data inputs. All raw data was run through Post Processed Precise Point Positioning (5P) using POSPac MMV 7.1.5812.24143 software. Survey launches 3101 and 3102 exhibited high vertical offsets after the POSPac SBETs were applied. Data which exhibited vertical offset measurements greater than 30 cm were reprocessed using IAPPK solutions. The following survey days' positioning data for launch 3101 was reprocessed using an IAPPK solution; DN342, DN343, DN344 DN345, DN346, DN347, DN347. The following survey days' positioning data for launch 3102 was reprocessed using an IAPPK solution; DN342, DN343. In all, 95.9% of the multibeam data was processed using IAPPK and 4.1% was processed using Marinestar 5P.</ns2:discussion><ns2:images><ns2:caption>Vertical offsets of 3101 and 3102 over charted wreck using a 5P solution. Viewed by a Depth layer.</ns2:caption><ns2:link>file:///H:/Surveys/OPR-D302-TJ-15/H12856/Data/Separates/Descriptive_Report/DR%20Multimedia/Vertical_offset_5P.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>Subset of vertical offsets of 3101 and 3102 over charted wreck using a 5P solution. Approximately 1.309 m difference.</ns2:caption><ns2:link>file:///H:/Surveys/OPR-D302-TJ-15/H12856/Data/Separates/Descriptive_Report/DR%20Multimedia/Vertical_offset_5P_2.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>The same wreck as in the previous images, with an IAPPK solution applied to 3101 and 3102. Viewed by a Depth layer.</ns2:caption><ns2:link>file:///H:/Surveys/OPR-D302-TJ-15/H12856/Data/Separates/Descriptive_Report/DR%20Multimedia/Vertical_offset_IAPPK_1.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>Subset over same wreck as in previous images, with an IAPPK solution. 0.0 m vertical difference.</ns2:caption><ns2:link>file:///H:/Surveys/OPR-D302-TJ-15/H12856/Data/Separates/Descriptive_Report/DR%20Multimedia/Vertical_offset_IAPPK_2.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>Base stations utilized by 3101's IAPPK solutions.</ns2:caption><ns2:link>file:///H:/Surveys/OPR-D302-TJ-15/H12856/Data/Separates/Descriptive_Report/DR%20Multimedia/3101_Days_IAPPK.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>Base stations utilized by 3102's IAPPK solutions.</ns2:caption><ns2:link>file:///H:/Surveys/OPR-D302-TJ-15/H12856/Data/Separates/Descriptive_Report/DR%20Multimedia/3102_Days_IAPPK.jpg</ns2:link></ns2:images><ns2:comments/></ns2:issue></ns2:results><ns2:comments/></ns1:factorsAffectingSoundings><ns1:soundSpeedMethods><ns1:castFrequency>Sound Speed Cast Frequency: CTD cast performed by launches 3101 &amp; 3102 were taken at a minimum of 4 hour intervals; or in areas where surface sound speed changed by 3 m/s compared to the previous cast taken. These cast were also applied to the data collected by Z-1 and Z-2. </ns1:castFrequency><ns1:discussion>Sound speed profiles were distributed based on safe deployment of equipment, depth and notable changes in surface sound speed. To account for differing water masses, casts were taken in both shallow and deep water relative to the areas being surveyed during the 4 hour time frame.</ns1:discussion><ns1:images><ns2:caption>H12856 geographic coverage of sound velocity casts from 3101,3102 and those applied to Z-1 and Z-2.</ns2:caption><ns2:link>file:///H:/Surveys/OPR-D302-TJ-15/H12856/Data/Separates/Descriptive_Report/DR%20Multimedia/SV_Profile_Coverage.jpg</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: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 7k file and has been sent to the Processing Branch. One line per vessel per day was processed by the field unit for quality assurance.</ns2:discussion></ns2:results><ns2:comments/></ns1:backscatter><ns1:dataProcessing><ns1:drSoftware><ns1:bathySoftware deviation="true"><ns1:manufacturer>Caris</ns1:manufacturer><ns1:name>HIPS &amp; SIPS</ns1:name><ns1:version>9.0.20</ns1:version></ns1:bathySoftware><ns1:imagerySoftware deviation="true"><ns1:manufacturer>Fledermaus</ns1:manufacturer><ns1:name>FMGT</ns1:name><ns1:version>7.4.5</ns1:version></ns1:imagerySoftware><ns1:featureObjectCatalog>NOAA Profile V_5_3_3</ns1:featureObjectCatalog><ns1:discussion xsi:nil="true"></ns1:discussion><ns1:comments/></ns1:drSoftware><ns1:surfaces><ns1:surface><ns2:surfaceName>H12856_MB_50cm_MLLW_Finalized.csar</ns2:surfaceName><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:resolution units="meters">0.5</ns2:resolution><ns2:depthRange><ns2:min units="meters">2.58</ns2:min><ns2:max units="meters">11.38</ns2:max></ns2:depthRange><ns2:surfaceParameter>NOAA_0.5m</ns2:surfaceParameter><ns2:purpose>Object Detection</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceName>H12856_MB_1m_MLLW_Finalized.csar</ns2:surfaceName><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:resolution units="meters">1</ns2:resolution><ns2:depthRange><ns2:min units="meters">1.28</ns2:min><ns2:max units="meters">12.83</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>H12856_Combined_4m_MLLW_Finalized</ns2:surfaceName><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:resolution units="meters">4</ns2:resolution><ns2:depthRange><ns2:min units="meters">-0.15</ns2:min><ns2:max units="meters">12.74</ns2:max></ns2:depthRange><ns2:surfaceParameter>NOAA_4m</ns2:surfaceParameter><ns2:purpose>100% SSS</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceName>H12856_VB_4m_MLLW_Finalized.csar</ns2:surfaceName><ns2:surfaceType>CUBE</ns2:surfaceType><ns2:resolution units="meters">4</ns2:resolution><ns2:depthRange><ns2:min units="meters">-0.15</ns2:min><ns2:max units="meters">9.54</ns2:max></ns2:depthRange><ns2:surfaceParameter>NOAA_4m</ns2:surfaceParameter><ns2:purpose>MBES TracklineSBES Set Line Spacing</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceName>H12856_SSS_100</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">0</ns2:max></ns2:depthRange><ns2:surfaceParameter>N/A</ns2:surfaceParameter><ns2:purpose>100% SSS</ns2:purpose></ns1:surface><ns1:discussion>Per section 5.2.2.1 of the NOAA HSSD Manual (ed 2015), all Object Detection MBES data was gridded according to depth: 0.5m resolution for depths ranging from 0 - 20m. 

Per section 5.2.2.2 of the NOAA HSSD Manual (ed 2015), MBES surfaces were gridded according to guidelines for Complete Coverage utilizing Side Scan Sonar coverage with concurrent single beam or multibeam. 

Surface H12856_Combined_4m_MLLW_Finalized was utilized to include all multi beam and vertical beam data.

Surfaces H12856_VB_4m_MLLW_Finalized and H12856_Combined_4m_MLLW_Finalized exhibit a minimum value of -0.15m within their depth ranges. This is due to the respective Z-boat collecting the vertical beam data utilized actually logged data over exposed or awash shoreline. </ns1:discussion><ns1:images><ns2:caption>Area highlighted where vertical beam data exhibits negative depth values. Indicating exposed or awash land or shoreline.</ns2:caption><ns2:link>file:///H:/Surveys/OPR-D302-TJ-15/H12856/Data/Separates/Descriptive_Report/DR%20Multimedia/Negative_value.jpg</ns2:link></ns1:images><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>TCARI</ns2:methodsUsed><ns2:tideStations><ns2:NWLONGauges><ns2:stationName>Wachapreague </ns2:stationName><ns2:stationID>8631044</ns2:stationID></ns2:NWLONGauges></ns2:tideStations><ns2:correctorFiles><ns2:waterLevels><ns2:fileName>8631044.tid</ns2:fileName><ns2:status>Final Approved</ns2:status></ns2:waterLevels><ns2:tideCorrectors><ns2:fileName>D302TJ2015_H12856.tc</ns2:fileName><ns2:status>Final</ns2:status></ns2:tideCorrectors></ns2:correctorFiles><ns2:finalTides><ns2:dateSubmitted>2016-01-06</ns2:dateSubmitted><ns2:dateReceived>2016-01-18</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>OPR-D302-TJ-15_ChincoteagueInlet_VDatum_SEP.csar</ns2:fileName></ns2:ellipsoidToChartDatumSepFile><ns2:discussion>All soundings submitted as H12856 are reduced to MLLW using documented VDatum techniques. If it is deemed necessary to change the water level reduction method to discrete zoning the following additional information will be useful: 
1) The National Water Level Observation Network (NWLON) stations serving as datum control for this survey is Wachapreague, VA (8631044).
2) The submitted water level files (8631044.tid) are the final approved water levels for the period of hydrography. These files have been loaded to all CARIS lines submitted as H12856.
3) The submitted tide corrector (D302TJ2015_H12856.tc) is the preliminary zoning file that was accepted as final per final tide note, submitted in Appendix I. This file has been loaded to all CARIS lines submitted as H12856.</ns2:discussion><ns2:comments/></ns2:VDATUM_or_constantSep><ns2:comments/></ns1:verticalControl><ns1:horizontalControl><ns2:horizontalDatum>North American Datum of 1983 (NAD83)</ns2:horizontalDatum><ns2:projection>UTM zone 18</ns2:projection><ns2:PPK used="true"><ns2:methodsUsed>Smart Base</ns2:methodsUsed><ns2:baseStations><ns2:CORSStations><ns2:HVCRSiteID>N/A</ns2:HVCRSiteID><ns2:stationID>VAWI</ns2:stationID></ns2:CORSStations><ns2:CORSStations><ns2:HVCRSiteID>N/A</ns2:HVCRSiteID><ns2:stationID>COVX</ns2:stationID></ns2:CORSStations><ns2:CORSStations><ns2:HVCRSiteID>N/A</ns2:HVCRSiteID><ns2:stationID>DED2</ns2:stationID></ns2:CORSStations><ns2:CORSStations><ns2:HVCRSiteID>N/A</ns2:HVCRSiteID><ns2:stationID>HNPT</ns2:stationID></ns2:CORSStations><ns2:CORSStations><ns2:HVCRSiteID>N/A</ns2:HVCRSiteID><ns2:stationID>LOYW</ns2:stationID></ns2:CORSStations><ns2:CORSStations><ns2:HVCRSiteID>N/A</ns2:HVCRSiteID><ns2:stationID>NJCM</ns2:stationID></ns2:CORSStations></ns2:baseStations><ns2:discussion xsi:nil="true"></ns2:discussion><ns2:comments/></ns2:PPK><ns2:PPP used="true"><ns2:discussion>NOAA Ship Thomas Jefferson and her launches acquire positioning data via POSMV TPUs. The launches 3101 and 3102 utilize a POSMV 4. The POSMV 4 TPUs have an upgraded firmware package allowing them to collect data comparable to a POSMV 5. All of these TPUs utilize a Fugro Marinestar Virtual Base Station subscription which collects Precise Point Positioning data.</ns2:discussion><ns2:comments/></ns2:PPP><ns2:RTK used="false" xsi:nil="true"/><ns2:DGPS used="false" xsi:nil="true"/><ns2:comments/></ns1:horizontalControl><ns1:additionalIssues><ns2:comments/></ns1:additionalIssues></ns1:verticalAndHorizontalControl><ns1:resultsAndRecommendations><ns1:chartComparison><ns1:methods><ns2:discussion>Chart comparison procedures were followed as outlined in section 4.5 of the FPM (2014 ed) and section 8.1.4 sub section D.1 of the HSSD (2015 ed). The ENC and RNC versions of the relevant charts were reviewed to ensure that the latest USCG Local Notice to Mariners (LNM) has been applied.

Additional chart comparisons for survey H12856 were conducted using selected sounding sets generated from H12856_MB_1m_MLLW_Finalized.csar and H12856_VB_4m_MLLW_Finalized.csar  at chart scale (1:10000) with a radius of 1m. In CARIS BDB, the soundings were then converted into a point cloud, from which a 1m and a 4m interpolated surface were generated. Contouring was run on the interpolated surface and the results are shown in the figure below.</ns2:discussion><ns2:images><ns2:caption>Northern portion of H12856 contours overlaid on RNC 12210_1.</ns2:caption><ns2:link>file:///H:/Surveys/OPR-D302-TJ-15/H12856/Data/Separates/Descriptive_Report/DR%20Multimedia/H12856_Contours_RNC122101_1.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>Southern portion of H12856 contours overlaid on RNC 12210_1.</ns2:caption><ns2:link>file:///H:/Surveys/OPR-D302-TJ-15/H12856/Data/Separates/Descriptive_Report/DR%20Multimedia/H12856_Contours_RNC122101_2.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>Northern portion of H12856 contours overlaid on ENC US4VA70M.</ns2:caption><ns2:link>file:///H:/Surveys/OPR-D302-TJ-15/H12856/Data/Separates/Descriptive_Report/DR%20Multimedia/H12856_Contours_ENCUSFVA70M_1.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>Southern portion of H12856 contours overlaid on ENC US4VA70M.</ns2:caption><ns2:link>file:///H:/Surveys/OPR-D302-TJ-15/H12856/Data/Separates/Descriptive_Report/DR%20Multimedia/H12856_Contours_ENCUSFVA70M_2.jpg</ns2:link></ns2:images><ns2:comments/></ns1:methods><ns1:charts><ns2:rasterChart><ns2:chart><ns2:number>12210</ns2:number><ns2:kapp>550</ns2:kapp><ns2:scale>20000</ns2:scale><ns2:edition>40</ns2:edition><ns2:editionDate>2015-08</ns2:editionDate><ns2:LNMDate>2015-11-28</ns2:LNMDate><ns2:NMDate>2015-11-28</ns2:NMDate></ns2:chart><ns2:discussion>There is much variation and change when comparing the current H12856 survey data to Chart 12210_2. The larger scale of Chart 12210_2 lends to a better comparison of current to historic survey data. In this comparison we see a good agreement between charted and surveyed contours. Depths do vary across a wide range of values. With such a wide range of differences, to quantify or visually describe would be superfluous.  It is suggested to base new contours and depths off complete data collected by survey H12856 per or exceeding Project Instructions. </ns2:discussion><ns2:images><ns2:caption>Northern portion of Chincoteague Inlet. Contours derived from vertical and multibeam data are displayed.</ns2:caption><ns2:link>file:///H:/Surveys/OPR-D302-TJ-15/H12856/Data/Separates/Descriptive_Report/DR%20Multimedia/H12856_Contours_RNC12210_2_1.jpg</ns2:link></ns2:images><ns2:comments/></ns2:rasterChart><ns2:rasterChart><ns2:chart><ns2:number>12210</ns2:number><ns2:kapp>551</ns2:kapp><ns2:scale>80000</ns2:scale><ns2:edition>40</ns2:edition><ns2:editionDate>2015-08</ns2:editionDate><ns2:LNMDate>2015-10-28</ns2:LNMDate><ns2:NMDate>2015-11-28</ns2:NMDate></ns2:chart><ns2:discussion>There is much variation and change when comparing the current H12856 survey data to Chart 12210_1. With such a wide range of differences, to quantify or visually describe would be superfluous.  It is suggested to base new contours and depths off complete data collected by survey H12856 per or exceeding Project Instructions. </ns2:discussion><ns2:images><ns2:caption>Northern portion of Chincoteague Inlet. Contours derived from vertical and multibeam data are displayed.</ns2:caption><ns2:link>file:///H:/Surveys/OPR-D302-TJ-15/H12856/Data/Separates/Descriptive_Report/DR%20Multimedia/H12856_Contours_RNC12210_1_1.jpg</ns2:link></ns2:images><ns2:comments/></ns2:rasterChart><ns2:rasterChart><ns2:chart><ns2:number>12211</ns2:number><ns2:kapp>552</ns2:kapp><ns2:scale>80000</ns2:scale><ns2:edition>45</ns2:edition><ns2:editionDate>2013-05</ns2:editionDate><ns2:LNMDate>2015-10-22</ns2:LNMDate><ns2:NMDate>2015-11-28</ns2:NMDate></ns2:chart><ns2:discussion>RNC 12211 coincides with raster chart 12210 Kapp 551. The comparison between survey H12856 and RNC 12211 is equivalent to the preceding comparison with RNC 12210. The Hydrographer recommends updating all contours and soundings with the digital data from survey H12856.</ns2:discussion><ns2:comments/></ns2:rasterChart><ns2:ENC><ns2:chart><ns2:name>US4VA70M</ns2:name><ns2:scale>80000</ns2:scale><ns2:edition>1</ns2:edition><ns2:updateApplicationDate>2016-02-18</ns2:updateApplicationDate><ns2:issueDate>2016-02-26</ns2:issueDate><ns2:preliminary>false</ns2:preliminary></ns2:chart><ns2:discussion>ENC US4VA70M coincides with raster chart 12210 Kapp 551. The depths and contours on the ENC match the raster 12210. The comparison between survey H12856 and the ENC is equivalent to the preceding comparison with Chart 12210. The Hydrographer recommends updating all contours and soundings with the digital data from survey H12856.</ns2:discussion><ns2:comments/></ns2:ENC><ns2:comments/></ns1:charts><ns1:maritimeBoundary><ns2:results investigated="None Exist"><ns2:discussion>No Maritime Boundary Points were assigned for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:maritimeBoundary><ns1:chartedFeatures><ns2:results investigated="Investigated"><ns2:discussion> See the H12856_FFF.hob final feature file for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:chartedFeatures><ns1:unchartedFeatures><ns2:results investigated="Investigated"><ns2:discussion>  See the H12856_FFF.hob final feature file for this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:unchartedFeatures><ns1:DTONS><ns2:results reportSubmitted="true"><ns2:numberSubmitted>1</ns2:numberSubmitted><ns2:discussion>Danger to Navigation Reports are included in Appendix II of this report.</ns2:discussion></ns2:results><ns2:comments/></ns1:DTONS><ns1:shoalAndHazardousFeatures><ns2:results investigated="Investigated"><ns2:discussion>Danger to Navigation Reports are included in Appendix II of this report.</ns2:discussion></ns2:results><ns2:comments/></ns1:shoalAndHazardousFeatures><ns1:channels><ns2:results investigated="Investigated"><ns2:discussion> Channels were investigated in conjunction with the chart comparison. Generally the contours and depths of the channels were in agreement especially in the northeastern portion of the inlet. Channel depths in the southwestern portion of the sheet had the greatest differences when compared to charted soundings. Refer to the chart comparisons in section D.1.  The Hydrographer recommends updating all contours and soundings with the digital data from survey H12856.</ns2:discussion><ns2:images><ns2:caption>Overview of channel area with greatest difference in surveyed and charted depths.</ns2:caption><ns2:link>file:///H:/Surveys/OPR-D302-TJ-15/H12856/Data/Separates/Descriptive_Report/DR%20Multimedia/Channel_comp_1.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>Depths in channel range from 26' -31' in a charted 33' area. east of Gunboat Point.</ns2:caption><ns2:link>file:///H:/Surveys/OPR-D302-TJ-15/H12856/Data/Separates/Descriptive_Report/DR%20Multimedia/Channel_comp_2.jpg</ns2:link></ns2:images></ns2:results><ns2:comments/></ns1:channels><ns1:bottomSamples><ns2:results investigated="Investigated"><ns2:discussion>A total of 7 bottom samples were taken for survey H12856. These were taken in places in possible anchorage sites, as well as those based on the assigned bottom sample sites provided in the Project Reference File for survey H12856. Many of the sites within the PRF were outside of collected survey data and were shifted to sites with the survey data based on the discretion of the field unit and Chief Hydrographer.</ns2:discussion><ns2:images><ns2:caption>Bottom samples are displayed as point features represented with a SBDARE symbol.</ns2:caption><ns2:link>file:///H:/Surveys/OPR-D302-TJ-15/H12856/Data/Separates/Descriptive_Report/DR%20Multimedia/Bottom_samples_sites.jpg</ns2:link></ns2:images></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/></ns1:shoreline><ns1:priorSurveys><ns2:results investigated="Investigated"><ns2:discussion>Prior surveys were reviewed by the field unit to provided an insight to the dynamics of the environment for survey H12856. </ns2:discussion></ns2:results><ns2:comments/></ns1:priorSurveys><ns1:ATONS><ns2:results investigated="Investigated"><ns2:discussion>Based on field observations, ATONs are properly placed and charted.</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.</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="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="Investigated"><ns2:discussion>Refer to H12856_FFF.hob final feature, as well as the DTON report for survey H12856. </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:comments/></ns1:otherResults><ns1:newSurveyRecommendation><ns2:results recommended="true"><ns2:discussion>Due to time constraints and necessary equipment, it is highly recommended to further investigate and survey Chincoteague Inlet and its surrounding waters.</ns2:discussion></ns2:results><ns2:comments/></ns1:newSurveyRecommendation><ns1:insetRecommendation><ns2:results recommended="true"><ns2:discussion>It is recommend to provide an inset at a higher resolution that overlaps RNC 12210_2. </ns2:discussion><ns2:images><ns2:caption>Recommended inset area for Chincoteague inlet and RNC 12210.</ns2:caption><ns2:link>file:///H:/Surveys/OPR-D302-TJ-15/H12856/Data/Separates/Descriptive_Report/DR%20Multimedia/inset.jpg</ns2:link></ns2:images></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>Shepard M. Smith, CAPT/NOAA</ns2:approverName><ns2:approverTitle>Chief of Party</ns2:approverTitle><ns2:approvalDate>2016-03-21</ns2:approvalDate></ns1:signingPersonnel><ns1:signingPersonnel><ns2:approverName>Joseph K. Carrier III, LT/NOAA</ns2:approverName><ns2:approverTitle>Field Operations Officer</ns2:approverTitle><ns2:approvalDate>2016-03-21</ns2:approvalDate></ns1:signingPersonnel><ns1:signingPersonnel><ns2:approverName>Alex C. Ligon</ns2:approverName><ns2:approverTitle>Sheet Manager</ns2:approverTitle><ns2:approvalDate>2016-03-21</ns2:approvalDate></ns1:signingPersonnel></ns1:approvalSheet></ns1:descriptiveReport>