<?xml version="1.0" encoding="utf-8"?>
<smd:surveyMetadata xmlns:hsd="http://svn.pydro.noaa.gov/2025/01/AllGlobalTypes" xmlns:smd="http://svn.pydro.noaa.gov/2025/01/SurveyMetadata" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://svn.pydro.noaa.gov/2025/01/SurveyMetadata http://svn.pydro.noaa.gov/2025/01/SurveyMetadata.xsd">
    <smd:metadata>
        <smd:project>
            <smd:uniqueId>OPR-N360-RA-24</smd:uniqueId>
            <smd:name>Central and Southern Puget Sound</smd:name>
            <smd:state>Washington</smd:state>
        </smd:project>
        <smd:survey>
            <smd:uniqueId>H13868</smd:uniqueId>
            <smd:name>Pickering Passage</smd:name>
        </smd:survey>
        <smd:date>
            <smd:utc>-0800</smd:utc>
            <smd:start>2024-06-10</smd:start>
            <smd:end>2024-07-15</smd:end>
        </smd:date>
        <smd:poc>
            <smd:responsibleParty>DOC/NOAA/NOS/OCS -- Office of Coast Survey</smd:responsibleParty>
            <smd:contactInfo>NOAA Ship RAINIER OPS</smd:contactInfo>
            <smd:fieldUnit>NOAA Ship Rainier (S221)</smd:fieldUnit>
        </smd:poc>
        <smd:dataLicense>
            <hsd:classification>CC0-1.0 (NOAA Field Units)</hsd:classification>
            <hsd:spdx>
                <hsd:licenseIdentifier>CC0-1.0</hsd:licenseIdentifier>
                <hsd:licenseDeed>https://creativecommons.org/publicdomain/zero/1.0/</hsd:licenseDeed>
                <hsd:legalCode>https://creativecommons.org/publicdomain/zero/1.0/legalcode</hsd:legalCode>
            </hsd:spdx>
            <hsd:description>These data were produced by NOAA and are in the public domain within the United States. NOAA waives any potential copyright and related rights in these data worldwide through the Creative Commons Zero 1.0 Universal Public Domain Dedication (CC0).</hsd:description>
        </smd:dataLicense>
        <smd:graphics>
            <smd:overview>file:./SupportFiles/H13868.PNG</smd:overview>
        </smd:graphics>
        <smd:grid>
            <smd:gridName>H13868_MB_VR_MLLW_1of1</smd:gridName>
            <smd:coordinateReferenceSystem>
                <smd:projection>Projected UTM 10</smd:projection>
                <smd:horizontal>
                    <smd:datum>North American Datum 1983 (2011)</smd:datum>
                    <smd:unit>arc degree</smd:unit>
                </smd:horizontal>
                <smd:vertical>
                    <smd:datum>Mean Lower Low Water</smd:datum>
                    <smd:unit>meters</smd:unit>
                </smd:vertical>
            </smd:coordinateReferenceSystem>
            <smd:soundingTechnique>found by multi beam</smd:soundingTechnique>
            <smd:detection>
                <smd:significantFeature>Yes</smd:significantFeature>
                <smd:leastDepth>Yes</smd:leastDepth>
                <smd:size>
                    <smd:fixed>2.0m (General 1)</smd:fixed>
                    <smd:variable>10% (General 1)</smd:variable>
                </smd:size>
            </smd:detection>
            <smd:coverageAssessment>
                <smd:fullSeafloor>Yes</smd:fullSeafloor>
                <smd:bathymetric>Yes</smd:bathymetric>
                <smd:interpolated>No</smd:interpolated>
            </smd:coverageAssessment>
            <smd:uncertainty>
                <smd:horizontal>
                    <smd:fixed>1m (Exceptional)</smd:fixed>
                    <smd:variable>N/A</smd:variable>
                </smd:horizontal>
                <smd:vertical>
                    <smd:fixed>0.15m (Exceptional)</smd:fixed>
                    <smd:variable>1% (General 1)</smd:variable>
                </smd:vertical>
            </smd:uncertainty>
        </smd:grid>
    </smd:metadata>
    <smd:equipmentList>
        <smd:platform>
            <smd:vessel>
                <smd:hull>
                    <smd:idNumber>2803</smd:idNumber>
                    <smd:name>RA-3</smd:name>
                </smd:hull>
                <smd:positioningSystem>
                    <smd:equipment>
                        <smd:type>Positioning and Attitude System</smd:type>
                        <smd:manufacturer>Applanix</smd:manufacturer>
                        <smd:systemName>POS MV 320 v5</smd:systemName>
                        <smd:modelNumber>POS MV 320 V5</smd:modelNumber>
                        <smd:serialNumber>7272</smd:serialNumber>
                        <smd:calibrationDate>2024-03-26</smd:calibrationDate>
                    </smd:equipment>
                </smd:positioningSystem>
                <smd:depthHeightSensor>
                    <smd:equipment>
                        <smd:type>Multibeam</smd:type>
                        <smd:manufacturer>Kongsberg Maritime</smd:manufacturer>
                        <smd:systemName>EM 2040</smd:systemName>
                        <smd:modelNumber>EM2040-07</smd:modelNumber>
                        <smd:serialNumber>256</smd:serialNumber>
                        <smd:frequency>300 kHz</smd:frequency>
                        <smd:calibrationDate>2024-03-26</smd:calibrationDate>
                        <smd:accuracyCheckDate>2024-03-26</smd:accuracyCheckDate>
                    </smd:equipment>
                </smd:depthHeightSensor>
                <smd:soundSpeedSensor>
                    <smd:equipment>
                        <smd:type>Sound Speed System</smd:type>
                        <smd:manufacturer>Teledyne RESON</smd:manufacturer>
                        <smd:systemName>SVP 70</smd:systemName>
                        <smd:modelNumber>SVP 70</smd:modelNumber>
                        <smd:serialNumber>3417109</smd:serialNumber>
                        <smd:frequency>20 Hz</smd:frequency>
                        <smd:calibrationDate>2018-03-05</smd:calibrationDate>
                        <smd:accuracyCheckDate>2024-03-26</smd:accuracyCheckDate>
                    </smd:equipment>
                    <smd:equipment>
                        <smd:type>Conductivity, Temperature, and Depth Sensor</smd:type>
                        <smd:manufacturer>Sea-Bird Scientific</smd:manufacturer>
                        <smd:systemName>SBE 19plus V2</smd:systemName>
                        <smd:modelNumber>SBE 19 Plus</smd:modelNumber>
                        <smd:serialNumber>4343</smd:serialNumber>
                        <smd:frequency>4 Hz</smd:frequency>
                        <smd:calibrationDate>2021-11-26</smd:calibrationDate>
                        <smd:accuracyCheckDate>2024-05-31</smd:accuracyCheckDate>
                    </smd:equipment>
                </smd:soundSpeedSensor>
            </smd:vessel>
            <smd:vessel>
                <smd:hull>
                    <smd:idNumber>2904</smd:idNumber>
                    <smd:name>RA-6</smd:name>
                </smd:hull>
                <smd:positioningSystem>
                    <smd:equipment>
                        <smd:type>Positioning and Attitude System</smd:type>
                        <smd:manufacturer>Applanix</smd:manufacturer>
                        <smd:systemName>POS MV 320 v5</smd:systemName>
                        <smd:modelNumber>POS MV 320 V5</smd:modelNumber>
                        <smd:serialNumber>7274</smd:serialNumber>
                        <smd:calibrationDate>2024-04-02</smd:calibrationDate>
                    </smd:equipment>
                </smd:positioningSystem>
                <smd:depthHeightSensor>
                    <smd:equipment>
                        <smd:type>Multibeam</smd:type>
                        <smd:manufacturer>Kongsberg Maritime</smd:manufacturer>
                        <smd:systemName>EM 2040</smd:systemName>
                        <smd:modelNumber>EM2040-07</smd:modelNumber>
                        <smd:serialNumber>257</smd:serialNumber>
                        <smd:frequency>300 kHz</smd:frequency>
                        <smd:calibrationDate>2024-03-26</smd:calibrationDate>
                        <smd:accuracyCheckDate>2024-03-26</smd:accuracyCheckDate>
                    </smd:equipment>
                </smd:depthHeightSensor>
                <smd:soundSpeedSensor>
                    <smd:equipment>
                        <smd:type>Sound Speed System</smd:type>
                        <smd:manufacturer>Teledyne RESON</smd:manufacturer>
                        <smd:systemName>SVP 70</smd:systemName>
                        <smd:modelNumber>SVP 70</smd:modelNumber>
                        <smd:serialNumber>2817018</smd:serialNumber>
                        <smd:frequency>20 Hz</smd:frequency>
                        <smd:calibrationDate>2018-03-01</smd:calibrationDate>
                        <smd:accuracyCheckDate>2024-03-26</smd:accuracyCheckDate>
                    </smd:equipment>
                    <smd:equipment>
                        <smd:type>Conductivity, Temperature, and Depth Sensor</smd:type>
                        <smd:manufacturer>Sea-Bird Scientific</smd:manufacturer>
                        <smd:systemName>SBE 19plus V2</smd:systemName>
                        <smd:modelNumber>SBE Plus</smd:modelNumber>
                        <smd:serialNumber>4676</smd:serialNumber>
                        <smd:frequency>4 Hz</smd:frequency>
                        <smd:calibrationDate>2018-01-31</smd:calibrationDate>
                        <smd:accuracyCheckDate>2024-05-31</smd:accuracyCheckDate>
                    </smd:equipment>
                </smd:soundSpeedSensor>
            </smd:vessel>
        </smd:platform>
        <smd:controlPoint />
    </smd:equipmentList>
    <smd:qualityControlProcedures>
        <smd:methods>
            <smd:crossline performed="true">
                <smd:discussion>
                    <smd:text>As a quality control measure for each survey, section 5.9 of the HSSD requires approximately 4% for 100% or greater bathymetric coverage surveys of the linear nautical mile total of mainscheme multibeam lines be run as crosslines. Following acquisition, a surface containing strictly data from mainscheme lines and a surface containing strictly data from crosslines are generated and analyzed with the Compare Grids tool in Pydro. This tool analyzes the difference between the two grids and outputs a difference surface between the depths, as well as a second surface that contains the fraction of NOAA allowable error represented by that depth difference for each node. Additionally, statistics/distribution summary plots of the difference surface and the fraction of allowable error are generated to provide easily interpretable analyses of the differences between the surfaces.

NOAA Ship RAINIER launches collected 8.52 nautical miles of multibeam crosslines, approximately 3.30 percent of total bathymetry coverage, across a range of depths in the maincheme data. The Compare Grids function in Pydro Explorer was used to analyze the finalized VR surfaces of H13868 mainscheme only and crossline only data. Pydro determined that 99.9 percent of nodes met allowable uncertainties.</smd:text>
                    <smd:images>
                        <smd:caption>H13868 crossline surface colored by depth overlaid on mainscheme tracklines.</smd:caption>
                        <smd:link>file:./SupportFiles/xl.PNG</smd:link>
                    </smd:images>
                    <smd:images>
                        <smd:caption>Pydro derived plot showing absolute difference statistics of H13868 mainscheme to crossline data. </smd:caption>
                        <smd:link>file:./SupportFiles/H13868_MS_VR-H13868_XL_VR_depth_delta_2024.png</smd:link>
                    </smd:images>
                    <smd:images>
                        <smd:caption>Pydro derived plot showing percentage-pass value of H13868 mainscheme to crossline data. </smd:caption>
                        <smd:link>file:./SupportFiles/H13868_MS_VR-H13868_XL_VR_fracAllowErr_vsDepth_General_1.png</smd:link>
                    </smd:images>
                </smd:discussion>
            </smd:crossline>
            <smd:junctionOverlap performed="true">
                <smd:discussion>
                    <smd:text>Survey managers perform junction analyses between the current survey and all adjacent contemporary surveys. To ensure proper overlap between surveys, approximately one bathymetric swath of overlap is acquired at each junction. Surface based and statistical analysis of the junctions is performed through the Compare Grids tool as described in the "Crossline" section of this report.

Survey H13868 junctions with two sheets, H13866 and H13960. The junction analysis with H13866 is described below. For the H13960 junction analysis, see the H13960 survey metadata report.</smd:text>
                    <smd:images>
                        <smd:caption>Junction surface H13868 with H13866 survey extents.</smd:caption>
                        <smd:link>file:./SupportFiles/H13960.PNG</smd:link>
                    </smd:images>
                </smd:discussion>
                <smd:discussion>
                    <smd:text>The junction with survey H13866 runs along an eastern border of coverage. The Compare Grids function of Pydro Explorer derived a difference surface from H13866 variable resolution surface and H13868 variable resolution surface. Pydro Compare Grids showed that 100 percent of nodes in the overlapping area met NOAA General 1 allowable error standards. Analysis of the difference surface indicated that there is a 0.04 meter average difference between the two surveys. See Compare Grids derived plots below.</smd:text>
                    <smd:images>
                        <smd:caption>H13866 and H13868 difference of depth surface.</smd:caption>
                        <smd:link>file:./SupportFiles/Capture.PNG</smd:link>
                    </smd:images>
                    <smd:images>
                        <smd:caption>Pydro derived plot showing absolute difference statistics of the junction between H13866 and H13868 variable resolution surface.</smd:caption>
                        <smd:link>file:./SupportFiles/H13868_MB_VR_MLLW_1of1-H13866_MB_VR_MLLW_FINAL_depth_delta_2024.png</smd:link>
                    </smd:images>
                    <smd:images>
                        <smd:caption>Pydro derived plot showing percentage-pass volume of the junction between H13866 and H13868 variable resolution surface.</smd:caption>
                        <smd:link>file:./SupportFiles/H13868_MB_VR_MLLW-H13960_MB_VR_MLLW_Final_fracAllowErr_vsDepth_General_1.png</smd:link>
                    </smd:images>
                </smd:discussion>
            </smd:junctionOverlap>
            <smd:statisticalAnalysis performed="true">
                <smd:discussion>
                    <smd:text>Pydro’s QC Tools included the tool “Grid QA” which automates the computation of grid statistics to ensure compliance with HSSD’s specifications. This tool plots node percentage histograms for resolution requirements, uncertainty standards and data density which demonstrate surface compliance with the standards set forth in the HSSD. Each of these plots includes the percent of nodes that pass the specific test in addition to statistical results such as mode, median and quartile values. 

Pydro QC Tools (v4.5.4) Grid QA was used to analyze H13868 multibeam echosounder (MBES) data density and data resolution. The submitted H13868 finalized variable-resolution (VR) surface met HSSD General 1 density requirements and resolution requirements, as shown in the histograms below. Grid QA results determined that 99.9 percent of H13868 nodes met full data density requirements and 100 percent of H13868 nodes met data resolution requirements. 

Uncertainty values of the submitted finalized grids were calculated in CARIS using "Uncertainty" when creating the finalized surface. Grid QA within Pydro QC Tools was used to analyze H13868 TVU compliance. H13868 met HSSD Exceptional uncertainty standards with 99.9 percent of grid nodes passing, which is shown in the histogram plot below.</smd:text>
                    <smd:images>
                        <smd:caption>Pydro Grid QA derived histogram plot showing HSSD density
requirements of H13868 finalized variable-resolution MBES data.</smd:caption>
                        <smd:link>file:./SupportFiles/H13868_MB_VR_MLLW_1of1.QAv7.density.png</smd:link>
                    </smd:images>
                    <smd:images>
                        <smd:caption>Pydro Grid QA derived histogram plot showing HSSD resolution
requirements of H13868 finalized variable-resolution MBES data.</smd:caption>
                        <smd:link>file:./SupportFiles/H13868_MB_VR_MLLW_1of1.QAv7.pct_res.gn1.png</smd:link>
                    </smd:images>
                    <smd:images>
                        <smd:caption>Pydro Grid QA derived histogram plot showing HSSD uncertainty requirements of H13868 finalized variable-resolution MBES data.</smd:caption>
                        <smd:link>file:./SupportFiles/H13868_MB_VR_MLLW_1of1.QAv7.tvu_qc.exc.png</smd:link>
                    </smd:images>
                </smd:discussion>
            </smd:statisticalAnalysis>
            <smd:directedEditing performed="true">
                <smd:discussion>
                    <smd:text>Directed editing involves an overview examination of the depth layer in addition to the available child layers to find problems with the data. This processing method works under the premise that if a surface “looks good” then the underlying data requires no additional cleaning. The hydrographer is then free to concentrate on trouble spots and make any necessary edits. While good at spotting bursts of noise and disagreement between overlapping lines, directed editing can have issues with finding single sounding fliers that may show up as only a single pixel if at all.

Preliminary data cleaning is performed daily during night processing following acquisition, addressing the most blatant fliers and blowouts. Cleaning is primarily done in Subset Editor, rejecting data that cause fliers in the CUBE grid.

Following this gross cleaning, Flier Finder, part of the QC Tools package in Pydro, is used to assist the search for spurious soundings. Flier Finder is run iteratively until all remaining flagged fliers are deemed to be valid aspects of the steep slopes and dynamic nature of the seafloor. Additionally, the uncertainty,hypothesis count, hypothesis strength, and node standard deviation child layers of the surface in CARIS HIPS are utilized to identify potential problem areas. These child layers may also cause seafloor features with high hypothesis counts or standard deviation such as man-made obstructions or wrecks to be easier identified.

On rare occasions the resolution of the CUBE surface may not be sufficient to capture the conditions throughout the entirety of a survey area. Only as a last resort should the hydrographer designate soundings that are not incorporated in the gridded surface. Detailed designated sounding searches in Subset Editor are only performed in regions expected to contain variation not captured in the standard grid, or when searching for known features. As a rule, sounding designation solely to adjust the surface is frowned upon and rarely used. Rather, sounding designation is typically used when those soundings are of critical importance, such as in the case of Dangers to Navigation (DTONs). In addition, all features found in the bathymetry that the Hydrographer wants included in the Final Feature File (FFF) should be correlated
between MBES and S-57 data. This is accomplished by designating the most reliable least depth of the feature in question and importing the designated sounding into the FFF as a feature for additional attribution.

Fliers were edited utilizing subset editor in CARIS. Pydro QC Tools (v4.5.4) Flier finder was used with default settings and found 6 fliers. These fliers were checked and deemed as edge fliers or false fliers.</smd:text>
                </smd:discussion>
            </smd:directedEditing>
            <smd:holidayIdentification performed="true">
                <smd:discussion>
                    <smd:text>Pydro's "Holiday Finder" tool scans the CUBE surfaces for any empty grid nodes that are surrounded by populated nodes, and flags holidays dependent on the criteria set by the coverage requirements. All flags are then visually inspected to determine the validity of each holiday, and all confirmed holidays are addressed either by acquiring additional data over the gaps, or explaining the cause and likelihood of hazards within each gap. 

Pydro QC Tools (v4.5.4) Holiday Finder was used with default settings to find holidays in the finalized H13868 VR surface. Holiday Finder detected zero certain holidays from the finalized surface.</smd:text>
                </smd:discussion>
            </smd:holidayIdentification>
            <smd:surveyAdequacy performed="true">
                <smd:discussion>
                    <smd:text>This survey is adequate to supersede all previous data.</smd:text>
                </smd:discussion>
            </smd:surveyAdequacy>
            <smd:imageryCoverage performed="false">
                <smd:discussion>
                    <smd:text>Imagery coverage assessment was not performed for this survey</smd:text>
                </smd:discussion>
            </smd:imageryCoverage>
            <smd:dataInterpolation performed="false">
                <smd:discussion>
                    <smd:text>Data interpolation was not performed for this survey</smd:text>
                </smd:discussion>
            </smd:dataInterpolation>
            <smd:backscatter performed="true">
                <smd:calibration>Relative</smd:calibration>
                <smd:dynamicRange>
                    <smd:discussion>
                        <smd:text>Due to variation in depth, the sonar pulse characteristics were automatically adjusted throughout the survey to optimize the quality of the bathymetry measurements. Pulse-characteristic-dependent offsets are visible in the final mosaic.</smd:text>
                    </smd:discussion>
                </smd:dynamicRange>
                <smd:acquisitionConfiguration>
                    <smd:discussion>
                        <smd:text>Kongsberg EM 2040 Echosounders automatically adjusts power and gain to ensure that the received intensity is within the usable dynamic range of the system.</smd:text>
                    </smd:discussion>
                </smd:acquisitionConfiguration>
                <smd:environmentalVariable>
                    <smd:discussion>
                        <smd:text>Absorption coefficients were derived from sound velocity casts and integrated in real-time in the sonar acquisition software.</smd:text>
                    </smd:discussion>
                </smd:environmentalVariable>
                <smd:acquisitionOutput>
                    <smd:discussion>
                        <smd:text>Acoustic intensity data was recorded by the sonar, enabling it to be post-processed into the final mosaic.</smd:text>
                        <smd:images>
                            <smd:caption>H13868 backscatter mosaic created in FMGT (v.7.11.1)</smd:caption>
                            <smd:link>file:./SupportFiles/BACKSCATT.PNG</smd:link>
                        </smd:images>
                    </smd:discussion>
                </smd:acquisitionOutput>
            </smd:backscatter>
        </smd:methods>
    </smd:qualityControlProcedures>
    <smd:controlPointEstablishment />
    <smd:reportOfSurvey>
        <smd:HSSD>
            <smd:version>2025-0-00</smd:version>
        </smd:HSSD>
        <smd:uncertaintySource>
            <smd:discussion>
                <smd:text>Any individual sounding’s Total Propagated Uncertainty (TPU), is derived from the assumed uncertainty in the echosounder measurement itself, as well as the contributing correctors from sound speed, water levels, position, and attitude. There are two places in CARIS where the user directly defines uncertainty values for use in CARIS to calculate TPU values, in the HVF and the direct input of SV and tide values during the TPU computation.

The TPU section of the HVF captures fixed estimates of uncertainty estimates for latency, sensor offset measurements, attitude and navigation measurements, and draft measurements. These uncertainty values are compiled from manufacturer specification sheets for each sensor, Appendix IV (Uncertainty values for use in CARIS with vessels equipped WITH an attitude sensor) of the 2014 FPM and from those set forth in Section 4.2.9 of the 2020 FPM.

Source of TPU Values: 28-foot Survey Launches

Commonly reported ranges of TPU values for all motion, navigation position and timing values are found in the FPM. All timing values were set to 0.005 seconds as outlined for setups with Ethernet connections and precise timing. All offset values were chosen to be 0.010 meters based on the accuracy provided by professional surveys. Vessel speed uncertainty was defined as 0.03 m/s plus an average value (assumed to be 0.05 m/s) for currents for a total of 0.08 m/s.

Starting in 2021 Rainier made the decision to analyze the historic record and come up with a single "launch representative value" Loading TPU value (in meters). This single, all-time loading value was determined by averaging together the Loading TPU values determined annually between the years 2012 to 2021. The resulting value is used for both of the 28-foot survey launches utilized by the Rainier field party in 2024.
Starting in 2021 Rainier made the decision to analyze the historic records and come up with a single "launch representative value" for the Draft TPU value (in meters). This single, all-time draft value was determined by averaging together individual Draft TPU values determined annually for each launch between the years 2012 to 2021. The resulting value is used by the 28-foot survey launches utilized by the Rainier field party in 2024.

Vessel delta draft is set at 0.010 meters in the CARIS HVF, a value which falls within the range recommended in FPM.

In the past Roll/Pitch and Yaw uncertainty were determined individually for each launch on an annual basis by using a number of testers to separately determine the pitch, roll, and yaw angular bias correctors. For each bias the standard deviation was also determined. The MRU Align StdDev Roll/Pitch value entered into the CARIS HVF was calculated by finding the square root of the roll standard deviation squared plus the pitch standard deviation squared. The MRU Align StdDev gyro value entered into the CARIS HVF was simply the yaw standard deviation.

Starting in 2021 Rainier made the decision to analyze the historic record and come up with a single "launch representative value" for both roll/pitch and yaw standard deviation. Each launch’s annual pitch, roll, and yaw standard deviation values were found for each year between 2012 to 2021 and weighed by the number of testers (a roll StdDev with 8 testers had twice the influence of a roll StdDev with 4 testers), these weighted standard deviation values were then averaged using data from all 4 Rainier survey launches, to obtain a "launch representative value" for each of the three angular biases. For all 28-foot survey launches utilized by the Rainier field party in 2024, the MRU Align StdDev Roll/Pitch entered into the CARIS HVF is the square root of the "launch representative" roll standard deviation squared plus the "launchrepresentative" pitch standard deviation squared. The MRU Align StdDev gyro entered into the CARIS HVF is simply the "launch representative" yaw standard deviation.

Source of TPU Values: 29-foot Survey Launch

For this project the field party also utilized a 29-foot survey launch normally maintained by MOC-P as training and testbed vessel. Although this launch looks similar to her 28' cousins, her construction is different enough from Rainier’s launches that the 28-foot "launch representative" values cannot be used. Instead a HVF supplied by the Hydrographic Systems &amp; Technology Branch with recommended standard deviation values from the FPM was used.</smd:text>
            </smd:discussion>
            <smd:discussion>
                <smd:text>Four additional TPU values for tide and sound velocity must be manually entered for TPU computation during the Georeference Bathymetry process:

1) Tide values measured uncertainty is now defunct; referring to accuracy of the tide gauges that are no longer used. A value of 0.0 is entered.

2) Tide values zoning uncertainty value once referred to the tidal error contribution to the total survey error budget which included the tidal datum computation and tidal zoning errors. It now contains the separation uncertainty of the VDATUM model. The actual uncertainty value can be found in either the Vertical Control Requirements section of the Project Instructions or in the metadata associated with the VDATUM model supplied. H13868 utilized the branch provided, ellipse-MLLW: "Vdatum_Outline_100m_2011- MLLW_geoid18" for processing data for GPS vertical adjustment. The separation uncertainty is 13.4 cm.

3) Measured sound speed value error ranges from 0.5 to 4 m/s, dependent on temporal/spatial variability. Although the FPM recommends a value of 4 m/s when one cast is taken every 4-hours, Rainier experience in the field indicates that a value of 3.0 m/s better models this error. If the ship measures sound speed with the MVP, a value of 1.0 m/s is used due to the higher sampling frequency. In cases where XBT casts are used to measure sound speed, the recommended value of 4.0 m/s is used.

4) Surface sound speed value is dependent on the manufacturer specifications of the instrument utilized to measure surface SV values for refraction corrections to flat-faced transducers. The RESON SVP 70 is the only model affixed to Rainier and all her MBES launches and a has a published accuracy of 0.05 m/s.</smd:text>
            </smd:discussion>
            <smd:discussion>
                <smd:text>In addition to the usual a priori estimates of uncertainty, some real-time and post-processed uncertainty sources are also incorporated. Real-time uncertainties from the Kongsberg EM2040 were recorded and applied in post-processing. Applanix TrueHeave files are recorded on all survey vessels, which include an estimate of the heave uncertainty, and are applied during post-processing. Finally, the post-processed uncertainties associated with navigation and GPS Height applied in CARIS HIPS via an SBET RMS file generated in POSPac.</smd:text>
            </smd:discussion>
        </smd:uncertaintySource>
        <smd:errorSource />
        <smd:unusualConditions />
        <smd:junctionAnalysis />
        <smd:additionalInformation />
        <smd:PIAlteration />
        <smd:supplementals>
            <smd:document>
                <smd:subject>NCEI Sound Speed Data</smd:subject>
                <smd:submissionDate>2024-08-21</smd:submissionDate>
            </smd:document>
            <smd:document>
                <smd:subject>Coast Pilot Report</smd:subject>
                <smd:submissionDate>2024-10-10</smd:submissionDate>
            </smd:document>
            <smd:document>
                <smd:subject>Trained Marine Mammal Observers list</smd:subject>
                <smd:submissionDate>2024-08-12</smd:submissionDate>
            </smd:document>
            <smd:document>
                <smd:subject>Final Survey Outline</smd:subject>
                <smd:submissionDate>2025-03-07</smd:submissionDate>
            </smd:document>
        </smd:supplementals>
    </smd:reportOfSurvey>
    <smd:personnel>
        <smd:approvalStatement>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 and approved all data and metadata. The survey meets or exceeds requirements as set forth in the NOS Hydrographic Surveys Specifications and Deliverables, Field Procedures Manual, Letter Instructions, and all HSD Technical Directives. The survey is complete and no additional work is required with the exception of any deficiencies noted in the Report of Survey.</smd:approvalStatement>
        <smd:approver>
            <smd:name>Nicholas C. Morgan CDR/NOAA</smd:name>
            <smd:title>Chief of Party</smd:title>
        </smd:approver>
        <smd:teamMember>
            <smd:name>Justin E. Blancher LT/NOAA</smd:name>
            <smd:title>Field Operations Officer</smd:title>
        </smd:teamMember>
        <smd:teamMember>
            <smd:name>James B. Jacobson</smd:name>
            <smd:title>Chief Survey Technician</smd:title>
        </smd:teamMember>
        <smd:teamMember>
            <smd:name>Charlee Godwin</smd:name>
            <smd:title>Sheet Manager</smd:title>
        </smd:teamMember>
    </smd:personnel>
</smd:surveyMetadata>