<?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>H12754</ns2:registryNumber><ns2:sheetID>1</ns2:sheetID><ns2:registryInstructions>Registry Instructions</ns2:registryInstructions><ns2:sublocality>43 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-05</ns2:start><ns2:end>2015-07-25</ns2:end></ns2:datesOfSurvey><ns2:equipmentTypes><ns2:soundingEquipment>Multibeam 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. Any revisions to the Descriptive Report (DR) generated during office processing are shown in bold, red italic text.  The processing branch maintains the DR as a field unit product, therefore, all information and recommendations within the body of the DR are considered preliminary unless otherwise noted. The final disposition of surveyed features is represented in the OCS nautical chart update products.  All pertinent records for this survey, including the DR, 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 (H12754) was conducted in the area 43 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 5th, 2015 and ended July 25th, 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 located on the north end of Prince of Wales Shoal. This shoal is a relatively narrow ridge of sediment 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) 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 within the project extents, with no inshore limit.
			</ns2:discussion><ns2:limits><ns2:northWest><ns2:latitude hemisphere="N">66.368428</ns2:latitude><ns2:longitude hemisphere="W">168.086383</ns2:longitude></ns2:northWest><ns2:southEast><ns2:latitude hemisphere="N">66.150804</ns2:latitude><ns2:longitude hemisphere="W">167.674947</ns2:longitude></ns2:southEast></ns2:limits><ns2:images><ns2:caption>Survey extents and overview.</ns2:caption><ns2:link>SupportFiles\1_H12754_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 (or older).</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/></ns1:surveyCoverage><ns1:coverageGraphic><ns2:caption>Survey overview showing coverage.</ns2:caption><ns2:link>SupportFiles\2_H12754_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>1131</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>115</ns2:XL_MBES_SBES><ns2:XL_lidar>0</ns2:XL_lidar></ns2:statistics></ns2:vessel></ns2:vesselLNM><ns2:totalLNM><ns2:MS_SBES>0</ns2:MS_SBES><ns2:MS_MBES>1131</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>115</ns2:XL_MBES_SBES><ns2:XL_lidar>0</ns2:XL_lidar><ns2:percentXLLNM>10.1</ns2:percentXLLNM></ns2:totalLNM></ns2:LNM><ns2:totalSurveyStats><ns2:bottomSamples>12</ns2:bottomSamples><ns2:AWOIS>0</ns2:AWOIS><ns2:maritimeBoundaryPoints>0</ns2:maritimeBoundaryPoints><ns2:DP>0</ns2:DP><ns2:diveOps>0</ns2:diveOps><ns2:SNM>118</ns2:SNM></ns2:totalSurveyStats><ns2:surveyDates>2015-07-05</ns2:surveyDates><ns2:surveyDates>2015-07-06</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-18</ns2:surveyDates><ns2:surveyDates>2015-07-19</ns2:surveyDates><ns2:surveyDates>2015-07-20</ns2:surveyDates><ns2:surveyDates>2015-07-21</ns2:surveyDates><ns2:surveyDates>2015-07-22</ns2:surveyDates><ns2:surveyDates>2015-07-25</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: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 and deployed BMPG tide gauges.</ns1:discussion><ns1:comments/></ns1:vessels><ns1:equipment><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>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>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.
				
				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.
		
				Refer to Separate II: Digital Data for the detailed Crossline QC Reports.</ns2:discussion><ns2:comments><ns2:branchComment concurrence="Comment Only"><ns2:comment>Separate II is not appended to this report.</ns2:comment></ns2:branchComment></ns2:comments></ns1:crosslines><ns1:uncertainty><ns2:values><ns2:tideUncertainty><ns2:measured units="meters">0</ns2:measured><ns2:zoning units="meters">0</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">1.698</ns2:measuredMVP><ns2:surface units="meters/second">0.025</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 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 MBES surface ranged from 0.1 m to 0.46 m. None 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 one contemporary survey, H12753, which was conducted concurrent with this sheet.
				
				The junction was compared by creating difference surfaces in CARIS HIPS and analyzing the results. For the comparison with H12753, the depth layers from each survey's 4-m resolution CUBE surface was differenced.
				</ns2:discussion><ns2:images><ns2:caption>Survey junctions with this sheet.</ns2:caption><ns2:link>SupportFiles\3_H12754_Junctions.jpg</ns2:link></ns2:images><ns2:junction><ns2:survey><ns2:registryNumber>H12753</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, comparing to within 0.048 m on average, with a standard deviation of 0.072 m, with 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. 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.
					
					Lead line comparisons were also undertaken. Over the course of the project, two were completed for the MBES on the Q105. Processed sonar results versus depth measured by lead line were 0.051 m or better for the MBES. Results were deemed acceptable given the variables associated with lead line checks.
					
					A vessel equipped with a SBES system, the ASV-CT3, was used for acquisition in other sheets in this project. 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 and analyzed. Project wide, the MBES data agrees with the SBES data to 0.012 m on average. Differences fall within a range of 0.426 m to -0.238, with a low standard deviation of 0.051 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><ns2:branchComment concurrence="Comment Only"><ns2:comment>Separate I is not appended to this report.</ns2:comment></ns2:branchComment></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: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.20 m, and is within specifications.</ns2:discussion><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 motion 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 normally 0.20 m or less, which 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 very good matchup with crosslines, but busts of 0.10 to 0.20 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 local and regional winds usually have more effect on water levels than the daily lunar and solar cycles. Despite the error, the data is within specifications.</ns2:discussion><ns2:images><ns2:caption>Example of tide bust of up to 0.20 m between a crossline (purple) and mainscheme lines.</ns2:caption><ns2:link>SupportFiles\4_H12754_Tides.jpg</ns2:link></ns2:images><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. 
			
				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, with exceptions noted elsewhere in this report.</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="true"><ns2:discussion>Corrections applied to echo soundings are detailed in the project DAPR. No deviations occurred, with the following exceptions:
					
					Sound Speed Correction Exception
					
					All Q105 multibeam lines were corrected using nearest in distance within two hours, except the following lines:
					
					Line Name - SV method
					0160-186_-D17940NS_-_0001 -- Used nearest in distance within three hours
					0163-186_-D17355NS_-_0001 -- Used nearest in distance within three hours
					0163-186_-D17355NS_-_0002 -- Used nearest in distance within three hours
					XL-0176-187_-D20280EW_-_0001 -- Used nearest in distance within three hours
					XL-0185-187_-D03120EW_-_0001 -- Used nearest in distance within three hours
					XL-0185-187_-D03120EW_-_0002 -- Used nearest in distance within three hours
					XL-0186-187_-D00975EW_-_0001 -- Used nearest in distance within four hours
					XL-0186-187_-D00975EW_-_0002 -- Used nearest in distance within five hours
					
					SBET PPK Exceptions
					
					All lines were loaded with PPK data. However, for unknown reasons, a set of SBET files from JD200 would not load to survey lines directly in CARIS HIPS. The SBETs were successfully exported to text files and imported into the affected lines using the CARIS HIPS Generic Data Parser (GDP). These lines (vessel Q105) are:
					
0368-200_-D09945NS_-_0002
0369-200_-D09750NS_-_0001
0369-200_-D09750NS_-_0002
0370-200_-D09750NS_-_0001
0370-200_-D09750NS_-_0002
0371-200_-D09555NS_-_0001
0371-200_-D09555NS_-_0002
0371-200_-D09555NS_-_0003

SMRMSG Real-time Error Exceptions 

Real-time RMS error was loaded to all Q105 lines for the purpose of TPU computation. However, for unknown reasons, a handful of lines would not accept real-time error data from SMRMSG files. For these lines real-time error was not loaded and static error estimates from the HVF were used during TPU computation instead:

0363-199_-D10530NS_-_0002
0368-200_-D09945NS_-_0002
0369-200_-D09750NS_-_0001
0369-200_-D09750NS_-_0002
0370-200_-D09750NS_-_0001
0370-200_-D09750NS_-_0002
0371-200_-D09555NS_-_0001
0371-200_-D09555NS_-_0002
0371-200_-D09555NS_-_0003


</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>H12754_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:discussion>The final depth information for this survey was submitted as one CARIS BASE surface which best represented the seafloor at the time of the 2015 survey. The surface was 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. A resolution of 4 m was selected 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 (H12754_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 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 in general. The vast majority of charted soundings (exceptions noted below) agree to this survey within 1 fathom or better. No overall trends are apparent in the relatively subtle differences between chart and survey data. See figure below.
					
					1. 10 fathom sounding at 66-17-10.404 N, 168-01-33.835 W was not confirmed by this survey. Depth in the vicinity of this sounding is actually 17 - 18 fathoms. Shown in following figure.
					2. 10 fathom sounding at 66-18-07.638 N, 167-52-31.479 W was not confirmed by this survey. Depth in the vicinity of this sounding is actually 12 fathoms.
					3. 9 fathom sounding at 66-17-22.961 N, 167-46-13.265 W was not confirmed by this survey. Depth in the vicinity of this sounding is actually 12 fathoms.
					
					 Note &quot;H&quot; on the chart indicates the source of soundings in the area of these three soundings may be very old, possibly dating back to Russian charts. It is recommended this soundings be removed from chart 16190 and replaced with data from this survey.
					</ns2:discussion><ns2:images><ns2:caption>Example of the excellent general agreement between this survey and chart 16190. Most soundings from this survey (blue) agree with soundings on the chart (black) to 1 fathom or better.</ns2:caption><ns2:link>SupportFiles\5_H12754_GeneralChartAgreement.jpg</ns2:link></ns2:images><ns2:images><ns2:caption>10 fathom sounding on chart 16190. This survey found depths in the area of 17 - 18 fathoms (blue). Note 'H' indicates the source of this and other nearby soundings may be very old, possibly dating back to Russian charts.</ns2:caption><ns2:link>SupportFiles\6_H12754_Sounding.jpg</ns2:link></ns2:images><ns2:comments/></ns2:rasterChart><ns2:rasterChart><ns2:chart><ns2:number>16005</ns2:number><ns2:kapp>2410</ns2:kapp><ns2:scale>700000</ns2:scale><ns2:edition>11</ns2:edition><ns2:editionDate>2015-05</ns2:editionDate><ns2:LNMDate>2015-10-20</ns2:LNMDate><ns2:NMDate>2015-10-17</ns2:NMDate></ns2:chart><ns2:discussion>Chart 16005 was the largest scale chart intersecting this survey for only a small portion of the area, on the north end. Only this area, where the larger-scale chart 16190 did not apply, was examined. Four charted soundings lie within this area; two agree within 1 fathom. The two that exceed 1 fathom of difference are noted below.
					
					1. 11 fathom sounding at 66-21-14.230 N, 167-58-38.348 W was not confirmed by this survey. Depth in the vicinity of this sounding is actually 13 fathoms.
					2. 9 fathom sounding at 66-19-12.125 N, 167-46-38.853 W was not confirmed by this survey. Depth in the vicinity of this sounding is actually 11 to 12 fathoms.
					
					</ns2:discussion><ns2:comments><ns2:branchComment concurrence="Comment Only"><ns2:comment>H12754 also covers Chart 16220, scale 1:315,350, units in meters.  A brief office comparison with Edition 1, 5/1/2013, Notice Date 4/9/2016 revealed significant discrepancies between the survey data and the chart.  Most notably, the three isolated shoals in the northeast corner of the chart were found not to exist.  The general depiction of the charted contours in the northeast section of chart are no longer accurate and surveyed depths were found to be 2 - 5 meters deeper, with an extreme difference of depths that were 14 meters deeper over the isolated 18.3 meter charted shoal.  Surveyed depths and contours in the southern part of the survey area were found to be in better agreement with the chart with differences typically less than a meter.</ns2:comment></ns2:branchComment></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:ENC><ns2:chart><ns2:name>US2AK92M</ns2:name><ns2:scale>700000</ns2:scale><ns2:edition>7</ns2:edition><ns2:updateApplicationDate>2011-05-02</ns2:updateApplicationDate><ns2:issueDate>2014-11-13</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:branchComment concurrence="Comment Only"><ns2:comment>H12754 also covers ENC US3AK89M.  The differences noted for Chart 16220 also apply to this ENC.</ns2:comment></ns2:branchComment></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 in general 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 brown silt and mud.
					
					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. However, Junction analysis, described previously in this report, was undertaken for overlapping contemporary surveys.</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 H12754 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>