<?xml version="1.0" encoding="UTF-8"?><ns1:descriptiveReport xmlns:ns1="http://Pydro.com/2014/02/DescriptiveReport" xmlns:ns2="http://Pydro.com/2014/02/AllGlobalTypes" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><ns1:metadata><ns1:projectMetadata><ns2:number>OPR-S313-KR-15</ns2:number><ns2:name>Cape Prince of Wales Shoal, AK</ns2:name><ns2:generalLocality>Bering Strait</ns2:generalLocality><ns2:fieldUnit>Terrasond Limited</ns2:fieldUnit></ns1:projectMetadata><ns1:registryMetadata><ns2:registryNumber>H12753</ns2:registryNumber><ns2:sheetID>1</ns2:sheetID><ns2:registryInstructions>Registry Instructions</ns2:registryInstructions><ns2:sublocality>30 NM North of Cape Prince of Wales</ns2:sublocality><ns2:stateOrTerritory>Alaska</ns2:stateOrTerritory><ns2:country>United States</ns2:country><ns2:scale>40000</ns2:scale></ns1:registryMetadata><ns1:surveyMetadata><ns2:year>2015</ns2:year><ns2:chiefOfParty>Andrew Orthmann</ns2:chiefOfParty><ns2:projectType>Navigable Area</ns2:projectType><ns2:PIDate>2015-05-05</ns2:PIDate><ns2:datesOfSurvey><ns2:start>2015-07-04</ns2:start><ns2:end>2015-07-26</ns2:end></ns2:datesOfSurvey><ns2:equipmentTypes><ns2:soundingEquipment>Multibeam Echosounder</ns2:soundingEquipment><ns2:soundingEquipment>Singlebeam Echosounder</ns2:soundingEquipment><ns2:imageryEquipment></ns2:imageryEquipment></ns2:equipmentTypes><ns2:acquisition><ns2:units>meters</ns2:units></ns2:acquisition><ns2:horizontalCoordinateSystem zone="3">NAD83</ns2:horizontalCoordinateSystem><ns2:timeZone>UTC</ns2:timeZone><ns2:verifier>Pacific Hydrographic Branch</ns2:verifier><ns2:titlesheetRemarks><ns2:fieldRemarks xsi:nil="true"></ns2:fieldRemarks><ns2:branchRemarks>The purpose of this survey is to provide contemporary surveys to update National Ocean Service (NOS) nautical charts. All separates are filed with the
hydrographic data. Notes in red were generated during office processing. The processing branch concurs with all information and recommendations
in the DR unless otherwise noted. Page numbering may be interrupted or non-sequential. All pertinent records for this survey, including the
Descriptive Report, are archived at the National Centers for Environmental Information (NCEI) and can be retrieved via http://www.ncei.noaa.gov/.</ns2:branchRemarks></ns2:titlesheetRemarks></ns1:surveyMetadata><ns1:assignment>Contractor</ns1:assignment></ns1:metadata><ns1:areaSurveyed><ns1:areaDescription><ns2:discussion>A navigable area survey (H12753) was conducted in the area 30 NM North of Cape Prince of Wales, Alaska, in accordance with the NOAA, National Ocean Service, Statement of Work (SOW), OPR-S313-KR-15, dated March 13th, 2015, and Hydrographic Survey Project Instructions dated May 5th, 2015.  Hydrographic survey data collection began July 4th, 2015 and ended July 26th, 2015. 
			
			The area is in a remote region just south of the Arctic circle. Sea ice covers the area for the majority of the year, with a limited ice-free season with open navigable water from approximately late June through October. Vessel traffic in the region primarily consists of barges serving communities along Alaska's north coast with fuel and supplies, freighters moving lead and zinc from Red Dog Mine to the north, and research vessels involved in Arctic studies. Traffic is relatively sparse but has been increasing in recent years along with economic and scientific interest in the Arctic.
			
			The survey area is centered on Prince of Wales Shoal. This shoal is a relatively narrow ridge of sediment, covered 3 1/2 to 5 fathoms, which extends NNE from Cape Prince of Wales approximately 35 NM. The shoal is built and maintained by sediment transport caused by tidal current flow between the Arctic Ocean and the Pacific Ocean by way of the Bering Strait. The shoal is unmarked because of the ice conditions and remoteness of the locality.
			
			Weather during the ice-free season is frequently inclement. The area is fully exposed in most directions and offers no anchorages or other protected areas. Rapidly changing wind and current conditions offshore of the shoal frequently cause confused and choppy seas which can be dangerous for small craft.
		
			Multibeam echosounder (MBES) and single beam echosounder (SBES) operations were conducted in the area in accordance with the project instructions, which specified set line spacing SBES or MBES with backscatter. Requirements called for 200 m set line spacing SBES (or MBES) within the project extents, with no inshore limit.
			</ns2:discussion><ns2:limits><ns2:northWest><ns2:latitude hemisphere="N">66.163152</ns2:latitude><ns2:longitude hemisphere="W">168.034122</ns2:longitude></ns2:northWest><ns2:southEast><ns2:latitude hemisphere="N">65.98975</ns2:latitude><ns2:longitude hemisphere="W">167.674166</ns2:longitude></ns2:southEast></ns2:limits><ns2:images><ns2:caption>Survey extents and overview.</ns2:caption><ns2:link>SupportFiles\1_H12753_SurveyExtents.jpg</ns2:link></ns2:images><ns2:comments/></ns1:areaDescription><ns1:surveyLimits><ns2:results deviation="false"><ns2:discussion>Survey limits were achieved.</ns2:discussion></ns2:results><ns2:comments/></ns1:surveyLimits><ns1:surveyPurpose><ns2:discussion>The purpose of the survey, as well as three adjacent surveys completed co-incidentally during project OPR-S313-KR-15, was to update NOS nautical charts in the general vicinity of the Bering Strait, addressing approximately 297 SQ NM of Priority 3 area identified in the NOAA Hydrographic Survey Priorities, 2012 edition. 
			
			The survey also addresses United States Coast Guard (USCG) requests for defining the extent of Cape Prince of Wales Shoal due to increased vessel traffic in the region. Prior to this survey, the degree to which the shoal may have shifted from the charted position was unknown, especially given that the best scale chart at the time of this survey (Chart 16190) is out of date, with source soundings acquired from 1940 to 1969.</ns2:discussion><ns2:comments/></ns1:surveyPurpose><ns1:surveyQuality><ns2:adequacy>The entire survey is adequate to supersede previous data.</ns2:adequacy><ns2:discussion xsi:nil="true"></ns2:discussion><ns2:comments/></ns1:surveyQuality><ns1:surveyCoverage><ns2:results deviation="true"><ns2:discussion>The 200 m spacing requirement for set line spacing within the survey extents was met.
				
				Line splits on charted soundings were not conducted because the nature of the bottom in the area reduced the likelihood of pinnacles or shoals between lines.</ns2:discussion></ns2:results><ns2:comments><ns2:branchComment concurrence="Comment Only"><ns2:comment>Line splits are required in for set line spacing surveys in accordance with section 5.2.2.3 of the HSSD.  There was no correspondence indicating that this requirement was waived.</ns2:comment></ns2:branchComment></ns2:comments></ns1:surveyCoverage><ns1:coverageGraphic><ns2:caption>Survey overview showing coverage.</ns2:caption><ns2:link>SupportFiles\2_H12753_Coverage.jpg</ns2:link></ns1:coverageGraphic><ns1:surveyStatistics><ns2:LNM><ns2:vesselLNM><ns2:vessel><ns2:hullID>Qualifier 105</ns2:hullID><ns2:statistics><ns2:MS_SBES>0</ns2:MS_SBES><ns2:MS_MBES>742</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>71</ns2:XL_MBES_SBES><ns2:XL_lidar>0</ns2:XL_lidar></ns2:statistics></ns2:vessel><ns2:vessel><ns2:hullID>ASV-CT3</ns2:hullID><ns2:statistics><ns2:MS_SBES>146</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>0</ns2:XL_MBES_SBES><ns2:XL_lidar>0</ns2:XL_lidar></ns2:statistics></ns2:vessel></ns2:vesselLNM><ns2:totalLNM><ns2:MS_SBES>146</ns2:MS_SBES><ns2:MS_MBES>742</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>71</ns2:XL_MBES_SBES><ns2:XL_lidar>0</ns2:XL_lidar><ns2:percentXLLNM>8.0</ns2:percentXLLNM></ns2:totalLNM></ns2:LNM><ns2:totalSurveyStats><ns2:bottomSamples>9</ns2:bottomSamples><ns2:AWOIS>0</ns2:AWOIS><ns2:maritimeBoundaryPoints>0</ns2:maritimeBoundaryPoints><ns2:DP>0</ns2:DP><ns2:diveOps>0</ns2:diveOps><ns2:SNM>85</ns2:SNM></ns2:totalSurveyStats><ns2:surveyDates>2015-07-04</ns2:surveyDates><ns2:surveyDates>2015-07-05</ns2:surveyDates><ns2:surveyDates>2015-07-06</ns2:surveyDates><ns2:surveyDates>2015-07-07</ns2:surveyDates><ns2:surveyDates>2015-07-08</ns2:surveyDates><ns2:surveyDates>2015-07-11</ns2:surveyDates><ns2:surveyDates>2015-07-12</ns2:surveyDates><ns2:surveyDates>2015-07-14</ns2:surveyDates><ns2:surveyDates>2015-07-15</ns2:surveyDates><ns2:surveyDates>2015-07-16</ns2:surveyDates><ns2:surveyDates>2015-07-17</ns2:surveyDates><ns2:surveyDates>2015-07-22</ns2:surveyDates><ns2:surveyDates>2015-07-25</ns2:surveyDates><ns2:surveyDates>2015-07-26</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>Qualifier 105</ns2:hullID><ns2:LOA units="meters">32</ns2:LOA><ns2:draft units="meters">1.8</ns2:draft></ns1:vessel><ns1:vessel><ns2:hullID>ASV-CT3</ns2:hullID><ns2:LOA units="meters">3.5</ns2:LOA><ns2:draft units="meters">0.3</ns2:draft></ns1:vessel><ns1:discussion>The Qualifier 105 (Q105) is a 32 m aluminum hull vessel owned and operated by Support Vessels of Alaska. The Q105 acquired all multibeam data and provided housing and facilities for on-site data processing. The vessel also collected bottom samples, deployed BMPG tide gauges, and deployed/recovered the ASV-CT3 vessel as necessary.
				
				The ASV-CT3 is a 3.5 m aluminum hull Autonomous Surface Vessel (ASV) owned and operated by ASV Global. The ASV was operated in an unmanned but monitored mode, collecting SBES data in close vicinity to the Q105 when weather conditions allowed. The ASV collected a minority of the mileage on this project because weather conditions were usually not conducive to its operations, deployment, or recovery. Note that a general-interest report regarding the ASV titled &quot;ASV_Operations_Summary_Report_TerraSond_2015&quot; was submitted to NOAA separately; it is included in the Appendix II subdirectory.</ns1:discussion><ns1:comments/></ns1:vessels><ns1:equipment><ns1:majorSystem><ns2:manufacturer>Teledyne Odom</ns2:manufacturer><ns2:model>Echotrac CV100</ns2:model><ns2:type>SBES</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>Teledyne Reson</ns2:manufacturer><ns2:model>Seabat 7101</ns2:model><ns2:type>MBES</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>Applanix</ns2:manufacturer><ns2:model>POSMV 320 V5</ns2:model><ns2:type>Positioning and Attitude</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>AML Oceanographic</ns2:manufacturer><ns2:model>MinosX with Xchange Sensors</ns2:model><ns2:type>Sound Speed Profiler</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>Hemisphere</ns2:manufacturer><ns2:model>Vector V113 GPS Compass</ns2:model><ns2:type>Positioning and Attitude</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>Valeport</ns2:manufacturer><ns2:model>Rapid SVT 200Bar</ns2:model><ns2:type>Sound Speed Profiler</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>Teledyne Oceanscience</ns2:manufacturer><ns2:model>RapidCAST</ns2:model><ns2:type>Sound Speed Profiler Deployment System</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>Trimble</ns2:manufacturer><ns2:model>5700</ns2:model><ns2:type>Base Station</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>Trimble</ns2:manufacturer><ns2:model>5700</ns2:model><ns2:type>Positioning</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>Sea-Bird Electronics</ns2:manufacturer><ns2:model>SBE 26+</ns2:model><ns2:type>Submerged Tide Gauge</ns2:type></ns1:majorSystem><ns1:majorSystem><ns2:manufacturer>AML Oceanographic</ns2:manufacturer><ns2:model>MinosX with Xchange Sensors</ns2:model><ns2:type>Conductivity and Temperature Gauges</ns2:type></ns1:majorSystem><ns1:discussion>Equipment configurations and operations as well as data acquisition and processing are described in the DAPR.</ns1:discussion><ns1:comments/></ns1:equipment><ns1:comments/></ns1:equipmentAndVessels><ns1:qualityControl><ns1:crosslines><ns2:discussion>Crosslines were acquired to meet or exceed the 8% of mainscheme requirements required in the HSSD.
				
				Effort was made to ensure crosslines were geographically distributed across the survey area. Crosslines were run perpendicular to mainscheme lines whenever possible to ensure higher quality nadir beams crossed lower quality outer beams. Multibeam lines intersected SBES lines as an additional cross-system/vessel check.
				
				The crossline analysis was conducted using CARIS HIPS “QC Report” routine. Each crossline was selected and run through the process, which calculated the depth difference between each accepted crossline sounding and a QC BASE (CUBE-type) surface’s depth layer created from the mainscheme data. QC BASE surfaces were created with the same CUBE parameters and resolutions as the final BASE surfaces, with the important distinction that the QC BASE surfaces did not include crosslines so as to not bias the QC report results. Differences in depth were grouped by beam number and statistics computed, which included the percentage of soundings with differences from the BASE surface falling within IHO Order 1. When at least 95% of the sounding differences exceed IHO Order 1, the crossline was considered to “pass,” but when less than 95% of the soundings compare within IHO Order 1, the crossline was considered to “fail.”
				
				Agreement between the BASE surfaces and crossline soundings is excellent. All crossline comparisons pass with 95% (or more) of soundings comparing to within IHO Order 1. 
				
				Note that this sheet included a section of SBES mainscheme, which was intersected by MBES crosslines. The SBES surface versus MBES crossline sounding agreement is also excellent, passing with 95% (or more) of soundings comparing to within IHO Order 1.
		
				Refer to Separate II: Digital Data for the detailed Crossline QC Reports.</ns2:discussion><ns2:comments/></ns1:crosslines><ns1:uncertainty><ns2:values><ns2:tideUncertainty><ns2:measured units="meters">0</ns2:measured><ns2:zoning units="meters">0</ns2:zoning></ns2:tideUncertainty><ns2:soundSpeedUncertainty><ns2:hullID>Qualifier 105</ns2:hullID><ns2:measuredCTD units="meters/second">0</ns2:measuredCTD><ns2:measuredMVP units="meters/second">2.111</ns2:measuredMVP><ns2:surface units="meters/second">0.025</ns2:surface></ns2:soundSpeedUncertainty><ns2:soundSpeedUncertainty><ns2:hullID>ASV-CT3</ns2:hullID><ns2:measuredCTD units="meters/second">0</ns2:measuredCTD><ns2:measuredMVP units="meters/second">2.111</ns2:measuredMVP><ns2:surface units="meters/second">0</ns2:surface></ns2:soundSpeedUncertainty></ns2:values><ns2:discussion>All soundings were assigned a horizontal and vertical value for estimated total propagated uncertainty (TPU). Tidal error (measured and zoning) was computed using the &quot;real-time&quot; values in the tide zone definition file (ZDF). The parameters and methods used for computation of sounding uncertainty are detailed in the project DAPR. The ASV-CT3 uses identical uncertainty values for measured sound speed as the Q105 because the Q105 performed all sound speed casts on the project.
				
				The BASE surfaces were finalized in CARIS HIPS so that the final uncertainty value for each grid cell is the greater of either standard deviation or uncertainty. The uncertainty layer of the final surface was then examined for areas of uncertainty that exceeded IHO Order 1.
				
				Uncertainty for the SBES surface ranged from 0.28 m to 0.40 m. Uncertainty for the MBES surface ranged from 0.13 m to 0.59 m. Few exceeded IHO Order 1.
				
				Highest uncertainties were found in areas of varying bottom topography such as slopes and sand waves where high standard deviations are caused by the wide depth ranges of soundings contributing to each grid cell, outer edges of multibeam swathes without adjacent line overlap, and areas exhibiting sound speed or motion artifact error. Despite elevated TPU values for these grid cells, the data is within specifications.</ns2:discussion><ns2:comments><ns2:branchComment concurrence="Comment Only"><ns2:comment>Table 6 incorrectly implies TPU values for Tide Measured and Tide Zoning were 0-meters.  For this survey, the field unit used a realtime method to apply tide TPU values.  All of the tidal uncertainties have been dealt with appropriately and the data is adequate to supersede charted data in the common area.</ns2:comment></ns2:branchComment></ns2:comments></ns1:uncertainty><ns1:junctions><ns2:discussion>This survey junctions with two contemporary surveys: H12754 and H12752. Both were conducted concurrent with this survey.
				
				Junctions were compared by creating difference surfaces in CARIS HIPS. 4-m resolution CUBE BASE surfaces were generated for each survey, and then differenced. Results were extracted and analyzed.</ns2:discussion><ns2:images><ns2:caption>Survey junctions with this sheet.</ns2:caption><ns2:link>SupportFiles\3_H12753_Junctions.jpg</ns2:link></ns2:images><ns2:junction><ns2:survey><ns2:registryNumber>H12752</ns2:registryNumber><ns2:scale>40000</ns2:scale><ns2:year>2015</ns2:year><ns2:fieldUnit>TerraSond</ns2:fieldUnit><ns2:relativeLocation>S</ns2:relativeLocation></ns2:survey><ns2:discussion>Agreement is excellent, averaging 0.003 m, with a standard deviation of 0.069 m, and differences falling in a range of -0.388 to 0.363 m.</ns2:discussion><ns2:comments/></ns2:junction><ns2:junction><ns2:survey><ns2:registryNumber>H12754</ns2:registryNumber><ns2:scale>40000</ns2:scale><ns2:year>2015</ns2:year><ns2:fieldUnit>TerraSond</ns2:fieldUnit><ns2:relativeLocation>N</ns2:relativeLocation></ns2:survey><ns2:discussion>Agreement is excellent, comparing to within 0.048 m on average, with a standard deviation of 0.072 m, and differences falling in a range of -0.487 to 0.342 m.</ns2:discussion><ns2:comments/></ns2:junction><ns2:comments/></ns1:junctions><ns1:sonarQCChecks><ns2:results deviation="true"><ns2:discussion>Echosounder confidence checks consisting of bar checks, lead lines, and acoustic comparisons between vessels were undertaken on this project.
					
					Two bar checks were completed for the MBES on the Q105, while one bar check was completed for the SBES system on the ASV-CT3. Bar checks served as a check on both real-time as well as processed depth accuracy, and were also used to determine and refine the sonar acoustic center offsets. Results were excellent, with processed sonar depths comparing on average to 0.033 m (or better) of the actual bar depth for MBES, and to 0.015 m for SBES.
					
					Lead line comparisons were also undertaken. Over the course of the project, two were completed for the MBES on the Q105 and one was completed for the SBES on the ASV-CT3. Processed sonar results versus depth measured by lead line were 0.051 m or better for the MBES, and 0.046 m for the SBES. Results were deemed acceptable given the variables associated with lead line checks.
					
					During acquisition, care was taken to ensure significant overlap between the two survey vessels for comparison purposes. Q105 MBES lines commonly intersect ASV-CT3 SBES data, and in several instances the Q105 surveyed completely over ASV-CT3 lines, creating ample comparable data. To compare the echosounder data, CARIS BASE surfaces at 4 m resolution were created for each vessel, and differenced from each other. The difference surfaces were exported to text and analyzed. Project wide, the MBES data agrees with the SBES data to 0.012 m on average, with a standard deviation of 0.051 m, with the MBES data slightly shoaler. The maximum difference was 0.426 m, and minimum difference was -0.238 m.
					
					Refer to the bar check and lead line logs available in Separate I: Acquisition and Processing Logs for specific results. Refer to the project DAPR for more information regarding QC checks methodology.</ns2:discussion></ns2:results><ns2:comments/></ns1:sonarQCChecks><ns1:equipmentEffectiveness><ns2:results deviation="true"><ns2:issue><ns2:title>7101 Beam Pattern</ns2:title><ns2:discussion>A distinct beam pattern was obvious in the data set in certain areas, with a fuzziness or “horn” like features on both sides of nadir on multibeam swaths, coinciding with the bottom detection shift from phase to amplitude detection. The pattern is common with Reson 8101/7101 multibeam echosounders in certain bottom types. Power and range settings were adjusted in acquisition to minimize the issue, with little effect. However, the “horns,” which can be as great as 0.20 m in height, appear to be largely ignored by the CUBE algorithm during surface creation, with minimal to no effect on the final surfaces.</ns2:discussion><ns2:comments/></ns2:issue><ns2:issue><ns2:title>ASV-CT3 Pitch and Roll</ns2:title><ns2:discussion>Pitch and roll records were logged aboard the the ASV-CT3 using a Hemisphere Vector V113, but were not applied to the SBES data. Although pitch and roll corrections are not required by the HSSD for SBES data, application to the SBES data was attempted on a test set of SBES data  in order to minimize effects of motion (especially pitch) on the SBES soundings, but resulted in no noticeable benefit. Therefore, roll and pitch were not applied to the SBES data by way of setting the sensors to &quot;Apply=NO&quot; in the CARIS HVF.</ns2:discussion><ns2:comments/></ns2:issue></ns2:results><ns2:comments/></ns1:equipmentEffectiveness><ns1:factorsAffectingSoundings><ns2:results deviation="true"><ns2:issue><ns2:title>Sound Speed Error</ns2:title><ns2:discussion>A general downward or upward across-track cupping in multibeam data, indicative of sound speed error, is present periodically in the data set. The sound speed error adversely affected outer beams by up to 0.20 m in places. To minimize the error, sound speed profiles were collected in sets every two hours during multibeam operations, and filters were used in processing to remove the outermost beams. The effect of sound speed error on final surfaces is relatively minor, normally not exceeding 0.10 m, and is within specifications.</ns2:discussion><ns2:comments><ns2:branchComment concurrence="Comment Only"><ns2:comment>The outer beams of the MBES lines were rejected in swath editor to account for the SS errors.  In some cases, good data was rejected.</ns2:comment></ns2:branchComment></ns2:comments></ns2:issue><ns2:issue><ns2:title>Motion Artifact</ns2:title><ns2:discussion>Motion artifact is occasionally visible in the final multibeam surfaces. This is the result of uncompensated effects of motion, particularly due to roll. Poor sea states (normally seas 1.5 m or greater) were common on this project and were the primary contributor. A survey-grade, high-end Applanix POSMV 320 V5 was used for motion compensation but residual error within the manufacturer specifications for the system remains nonetheless. The problem was addressed in processing by identifying lines with the greatest error and iteratively applying more aggressive outer beam filters, in some instances rejecting beams greater than 50 degrees either side of nadir. No adjustments to line spacing were made in acquisition to compensate for the rejected outer beam data because as a set-spaced survey, complete coverage was not required. Following the additional filtering the effect on the final surface is 0.20 m or less, which is within specifications.</ns2:discussion><ns2:comments/></ns2:issue><ns2:issue><ns2:title>ASV-CT3 Pitch and Roll</ns2:title><ns2:discussion>As described previously, corrections for pitch and roll were not applied to ASV-CT3 data. This sometimes results in downward &quot;spikes&quot; in the SBES data where the sounder erroneously digitized the depth as deeper than actual due to angle of the transducer relative to the seafloor while the vessel was pitching. To a lesser extent roll similarly affects the data. The relatively large (4 m) grid cell size used for the final BASE surfaces smooths and mitigates the effect of the error. Despite the apparent error the gridded SBES data passes crossline analysis, and compares to overlapping MBES data to 0.012 m on average with a low standard deviation of 0.051 m, and is within specifications.</ns2:discussion><ns2:comments/></ns2:issue><ns2:issue><ns2:title>Tide Error</ns2:title><ns2:discussion>Periodic vertical offsets or “busts”, indicative of tide error, is present sporadically in the data set. The majority of lines show excellent matchup with crosslines, but busts of up to 0.15 m are occasionally present and attributable to tide error.  The observed amount of tide error was deemed acceptable given that it was not possible for the project tide station and zoning gauges to capture all water level changes across the survey area, especially in this wide open region where winds frequently have more effect on water levels than the daily lunar and solar cycles. Despite the error, data is within specifications.</ns2:discussion><ns2:comments/></ns2:issue></ns2:results><ns2:comments/></ns1:factorsAffectingSoundings><ns1:soundSpeedMethods><ns1:castFrequency>2 hours</ns1:castFrequency><ns1:discussion>Sound speed profiles were acquired aboard the Q105 while underway with an Oceanscience RapidCAST system, which utilized a Valeport sound speed profiler. Normally two or three profile &quot;casts&quot; were taken along a survey line, with casts near the beginning, end, and middle of the line (depending on line length), in order to capture spatial variance across the area. The set was then repeated on an interval of approximately two hours in order to capture temporal variance. The sound speed sensor was lowered as close as possible to the seafloor, and then retracted to the vessel and downloaded. 
				
				The ASV-CT3 vessel was not equipped to collect sound speed profiles. Instead, the profile data collected aboard the Q105 was used to correct all ASV-CT3 SBES data. This was possible because the ASV-CT3 worked simultaneously and in close proximity (usually within 200 m) of the Q105 at all times.
				
				Up and down portions of the profiles were averaged and a combined profile at a standardized 0.10 m depth increment was output to CARIS SVP format with time and position. Sound speed profiles were applied with the “nearest in distance within time” method in CARIS HIPS, with time set to two hours for multibeam and four hours for single beam.</ns1:discussion><ns1:comments/></ns1:soundSpeedMethods><ns1:coverageEquipmentAndMethods><ns2:results deviation="true"><ns2:discussion>Set line spacing requirements called for 200 m spaced lines within the survey extents.
					
					Line plans were defined in CAD software prior to the commencement of survey operations and were executed line by line during acquisition. Two line sets were available, with north-south and east-west orientations, which provided options for line direction depending on prevailing weather conditions. 
					
					Refer to the project DAPR for additional methods used to meet coverage requirements.</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>Corrections applied to echo soundings are detailed in the project DAPR. No deviations occurred.
</ns2:discussion></ns2:results><ns2:comments/></ns1:corrections><ns1:calibrations><ns2:results deviation="false"><ns2:discussion>Calibrations were undertaken as described in the DAPR; no deviations occurred.</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>Multibeam backscatter was logged during this survey, but not processed. The vessel Q105 multibeam DB and XTF files contain the backscatter records.</ns2:discussion></ns2:results><ns2:comments/></ns1:backscatter><ns1:dataProcessing><ns1:softwareUpdates><ns1:featureObjectCatalog>V5.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>H12753_MB_4m_MLLW</ns2:surfaceName><ns2:surfaceType>MBES</ns2:surfaceType><ns2:resolution units="meters">4</ns2:resolution><ns2:depthRange><ns2:min units="meters">0</ns2:min><ns2:max units="meters">40</ns2:max></ns2:depthRange><ns2:surfaceParameter>NOAA_4m</ns2:surfaceParameter><ns2:purpose>Set-spaced MBES</ns2:purpose></ns1:surface><ns1:surface><ns2:surfaceName>H12753_SB_4m_MLLW</ns2:surfaceName><ns2:surfaceType>SBES</ns2:surfaceType><ns2:resolution units="meters">4</ns2:resolution><ns2:depthRange><ns2:min units="meters">0</ns2:min><ns2:max units="meters">40</ns2:max></ns2:depthRange><ns2:surfaceParameter>NOAA_4m</ns2:surfaceParameter><ns2:purpose>Set-spaced SBES</ns2:purpose></ns1:surface><ns1:discussion>The final depth information for this survey was submitted as two CARIS BASE surfaces which best represented the seafloor at the time of the 2015 survey. The surfaces were created from fully processed soundings with all final corrections applied.
				
				The MBES surface was created using CUBE parameters that ensured a maximum sounding propagation distance of the grid resolution divided by √2. The SBES surface was created as a Uncertainty surface. A resolution of 4 m was selected for both surfaces based on the requirements for set-spaced surveys described in the HSSD.  Surfaces were finalized, and designated soundings were applied where applicable. Horizontal projection was selected as UTM Zone 3 North, NAD 1983.
				
				Notes:
				
				* Any non-final surfaces submitted with the survey deliverables are interim products and are marked with &quot;nonFinal&quot; in their filename(s).
				* 4 m resolution was used per HSSD requirements for Set Line Spacing. All depths were less than 40 m.
				
				A CARIS HOB file was submitted (H12753_FFF.HOB) with the survey deliverables as well. The final feature file (FFF) contains meta-data and other data not readily represented by the final surfaces, including bottom samples. Each object is encoded with mandatory S-57 attributes, additional attributes, and NOAA Extended Attributes (V#5.3.2).
				
				Refer to the DAPR for more detailed discussion of the steps followed when acquiring and processing the 2015 survey data.</ns1:discussion><ns1:comments><ns2:branchComment concurrence="Comment Only"><ns2:comment>The first sentence of the second paragraph is simply describing the NOAA 4m CUBE Parameters.  The grid resolution is divided by the square root of 2.</ns2:comment></ns2:branchComment></ns1:comments></ns1:surfaces><ns1:additionalDataProcessing><ns2:comments/></ns1:additionalDataProcessing></ns1:dataProcessing></ns1:dataAcquisitionAndProcessing><ns1:verticalAndHorizontalControl><ns1:discussion>Additional information discussing the vertical or horizontal control for this survey can be found in the accompanying HVCR.</ns1:discussion><ns1:verticalControl><ns2:verticalDatum>Mean Lower Low Water</ns2:verticalDatum><ns2:standard_or_ERZT used="true"><ns2:methodsUsed>Discrete Zoning</ns2:methodsUsed><ns2:tideStations><ns2:subordinateGauges><ns2:stationName>Outside Lopp Lagoon</ns2:stationName><ns2:stationID>9469515</ns2:stationID></ns2:subordinateGauges></ns2:tideStations><ns2:correctorFiles><ns2:waterLevels><ns2:fileName>9469515.tid</ns2:fileName><ns2:status>Final Approved</ns2:status></ns2:waterLevels><ns2:tideCorrectors><ns2:fileName>S313KR2015CORP_20151008.zdf</ns2:fileName><ns2:status>Final</ns2:status></ns2:tideCorrectors></ns2:correctorFiles><ns2:finalTides><ns2:dateSubmitted>9999-01-01</ns2:dateSubmitted><ns2:dateReceived>9999-01-01</ns2:dateReceived></ns2:finalTides><ns2:discussion>In addition to the subordinate tide station installed to support the project, submerged BMPG (bottom mounted pressure gauges) were also deployed throughout the survey area to capture zoning characteristics. Data from all stations were used to derive the tide zones.</ns2:discussion><ns2:comments/></ns2:standard_or_ERZT><ns2:VDATUM_or_constantSep used="false"><ns2:discussion xsi:nil="true"></ns2:discussion><ns2:comments/></ns2:VDATUM_or_constantSep><ns2:comments/></ns1:verticalControl><ns1:horizontalControl><ns2:horizontalDatum>NAD83</ns2:horizontalDatum><ns2:projection>UTM Zone 3N</ns2:projection><ns2:PPK used="true"><ns2:methodsUsed>Single Base</ns2:methodsUsed><ns2:baseStations><ns2:userInstalledStations><ns2:HVCRSiteID>0056</ns2:HVCRSiteID><ns2:stationID>Outside Lopp Lagoon</ns2:stationID></ns2:userInstalledStations></ns2:baseStations><ns2:discussion>The project base continuously logged GPS data at 1 Hz and was utilized to post-process position data in Applanix POSPac software. All real-time positions for both vessels were replaced in processing with post-processed kinematic (PPK) solutions.</ns2:discussion><ns2:comments/></ns2:PPK><ns2:PPP used="false" xsi:nil="true"/><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>The chart comparison was performed by examining all Raster Navigational Charts (RNCs) and Electronic Navigational Charts (ENCs) that intersect the survey area.
				
				The chart comparison was accomplished by overlaying the finalized BASE surfaces with shoal-biased soundings, and final feature file on the charts in CARIS HIPS. The general agreement between charted soundings and survey soundings was then examined and a more detailed comparison was undertaken for any shoals or other dangerous features. In areas where a large scale chart overlapped with a small scale chart, only the larger scale chart was examined. Results are shown in the following sections.
				
				It is recommended that this survey supersede charted data where they overlap.
				
				USCG Notice to Mariners (NM) and USCG Local Notice to Mariners were checked for updates affecting the area. None were found that were issued subsequent to issuance date of the project instructions.</ns2:discussion><ns2:comments/></ns1:methods><ns1:charts><ns2:rasterChart><ns2:chart><ns2:number>16190</ns2:number><ns2:kapp>2350</ns2:kapp><ns2:scale>100000</ns2:scale><ns2:edition>1</ns2:edition><ns2:editionDate>2013-05</ns2:editionDate><ns2:LNMDate>2015-10-20</ns2:LNMDate><ns2:NMDate>2015-10-17</ns2:NMDate></ns2:chart><ns2:discussion>Sounding agreement is excellent. All charted soundings agree to this survey to 1 fathom or better. See figure below.</ns2:discussion><ns2:images><ns2:caption>Example of the excellent agreement between this survey and chart 16190. Soundings from this survey (blue) agree with soundings on the chart (black) to 1 fathom or better.</ns2:caption><ns2:link>SupportFiles\4_H12753_GeneralChartAgreement.jpg</ns2:link></ns2:images><ns2:comments/></ns2:rasterChart><ns2:ENC><ns2:chart><ns2:name>US4AK8DM</ns2:name><ns2:scale>100000</ns2:scale><ns2:edition>3</ns2:edition><ns2:updateApplicationDate>2015-04-22</ns2:updateApplicationDate><ns2:issueDate>2015-04-22</ns2:issueDate><ns2:preliminary>false</ns2:preliminary></ns2:chart><ns2:discussion>The same differences observed for the RNC apply to the ENC.</ns2:discussion><ns2:comments/></ns2:ENC><ns2:comments/></ns1:charts><ns1:AWOISItems><ns2:results investigated="None Exist"><ns2:discussion>There were no assigned AWOIS items 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="None Exist"><ns2:discussion>There are no charted features labeled PA, ED, PD, or Rep. within the survey extents.</ns2:discussion></ns2:results><ns2:comments/></ns1:chartedFeatures><ns1:unchartedFeatures><ns2:results investigated="None Exist"><ns2:discussion>No uncharted features were found during this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:unchartedFeatures><ns1:DTONS><ns2:results reportSubmitted="false"><ns2:numberSubmitted xsi:nil="true"></ns2:numberSubmitted><ns2:discussion>No DTONs were found during this survey.</ns2:discussion></ns2:results><ns2:comments/></ns1:DTONS><ns1:shoalAndHazardousFeatures><ns2:results investigated="Investigated"><ns2:discussion>Prince of Wales Shoal, over which this survey was conducted, could be potentially hazardous to vessels of significant draft. However, soundings from this survey compare well to the charted soundings on chart 16190. Therefore, the chart already adequately depicts potential dangers.</ns2:discussion></ns2:results><ns2:comments/></ns1:shoalAndHazardousFeatures><ns1:channels><ns2:results investigated="None Exist"><ns2:discussion>No channels exist in the survey area.</ns2:discussion></ns2:results><ns2:comments/></ns1:channels><ns1:bottomSamples><ns2:results investigated="Investigated"><ns2:discussion>Bottom samples were collected for this survey. Most returned brown silt, with some clay and fine sand. 
					
					Samples were not retained. Bottom characteristics are encoded as SBDARE objects in the FFF, with photos of each sample in the accompanying &quot;multimedia&quot; directory, included with the survey deliverables.</ns2:discussion></ns2:results><ns2:comments/></ns1:bottomSamples></ns1:chartComparison><ns1:additionalResults><ns1:shoreline><ns2:results investigated="None Exist"><ns2:discussion>This survey did not intersect shoreline, and shoreline investigation was not assigned.</ns2:discussion></ns2:results><ns2:comments/></ns1:shoreline><ns1:priorSurveys><ns2:results investigated="Exist - Not Investigated"><ns2:discussion>Comparison with prior surveys was not required.</ns2:discussion></ns2:results><ns2:comments/></ns1:priorSurveys><ns1:ATONS><ns2:results investigated="None Exist"><ns2:discussion>No ATONs were observed in the survey area, and none were assigned for investigation.</ns2:discussion></ns2:results><ns2:comments/></ns1:ATONS><ns1:overheadFeatures><ns2:results investigated="None Exist"><ns2:discussion>No overhead features existed within the survey area.</ns2:discussion></ns2:results><ns2:comments/></ns1:overheadFeatures><ns1:submarineFeatures><ns2:results investigated="None Exist"><ns2:discussion>None to note.</ns2:discussion></ns2:results><ns2:comments/></ns1:submarineFeatures><ns1:ferryRoutesAndTerminals><ns2:results investigated="None Exist"><ns2:discussion>Ferry routes and terminals do not exist within the survey area.</ns2:discussion></ns2:results><ns2:comments/></ns1:ferryRoutesAndTerminals><ns1:platforms><ns2:results investigated="None Exist"><ns2:discussion>Platforms do not exist within the survey area.</ns2:discussion></ns2:results><ns2:comments/></ns1:platforms><ns1:significantFeatures><ns2:results investigated="Investigated"><ns2:discussion>All significant features and conditions encountered have been described previously.</ns2:discussion></ns2:results><ns2:comments/></ns1:significantFeatures><ns1:constructionOrDredging><ns2:results investigated="None Exist"><ns2:discussion>No construction or dredging was occurring within the survey extents, nor are there any known future plans for construction or dredging in the survey area.</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 are recommended in this area.</ns2:discussion></ns2:results><ns2:comments/></ns1:newSurveyRecommendation><ns1:insetRecommendation><ns2:results recommended="false"><ns2:discussion>No new chart insets are recommended in this area.</ns2:discussion></ns2:results><ns2:comments/></ns1:insetRecommendation></ns1:additionalResults></ns1:resultsAndRecommendations><ns1:approvalSheet><ns1:statements><ns1:supervision>Field operations contributing to the completion of survey H12753 were conducted under my direct supervision with frequent personal checks of progress, integrity, and adequacy.</ns1:supervision><ns1:approval>This report, digital data, and all other accompanying records are approved. All records are respectfully submitted and forwarded for final review.</ns1:approval><ns1:adequacyOfSurvey>The survey data was collected in accordance with the Statement of Work and meets or exceeds the requirements set in the 2014 NOS Hydrographic Surveys and Specifications Deliverables (HSSD) document. This data is adequate to supersede charted data in common areas. This survey is complete and no additional work is required with the exception of any deficiencies, if any, noted in the Descriptive Report.</ns1:adequacyOfSurvey><ns1:additionalInfo xsi:nil="true"></ns1:additionalInfo></ns1:statements><ns1:signingPersonnel><ns2:approverName>Andrew Orthmann, C.H.</ns2:approverName><ns2:approverTitle>TerraSond Charting Program Manager</ns2:approverTitle><ns2:approvalDate>2015-11-20</ns2:approvalDate></ns1:signingPersonnel><ns1:additionalReports><ns2:reportName>Coast Pilot Review (CPB9_E33_C09_20151016_1817_Recommendations)</ns2:reportName><ns2:reportDateSent>2015-10-20</ns2:reportDateSent></ns1:additionalReports><ns1:additionalReports><ns2:reportName>OPR S313-KR-15 Tide Station Removal Report (9469515 Outside Lopp Lagoon)</ns2:reportName><ns2:reportDateSent>2015-09-28</ns2:reportDateSent></ns1:additionalReports></ns1:approvalSheet></ns1:descriptiveReport>