<?xml version="1.0" encoding="UTF-8"?>
<inport-metadata xmlns:xs="http://www.w3.org/2001/XMLSchema"
                 version="1.11"
                 source="https://www.fisheries.noaa.gov">
   <item-identification>
      <catalog-item-id>79179</catalog-item-id>
      <title>2022 USGS Lidar DEM: Umatilla Wallowa Whitman (ID, OR, WA)</title>
      <short-name>or2022_uma_wall_whit_dem_m13945</short-name>
      <catalog-item-type>Data Set</catalog-item-type>
      <metadata-workflow-state ccs-id="9">Published / External</metadata-workflow-state>
      <parent-catalog-item-id>49404</parent-catalog-item-id>
      <parent-title>DEMs - partner (no harvest)</parent-title>
      <parent-catalog-item-type>Project</parent-catalog-item-type>
      <status>Completed</status>
      <creation-date>2022</creation-date>
      <publication-date>2026</publication-date>
      <abstract>Original Product: These are Digital Elevation Model (DEM) data for Umatilla Wallowa Whitman Lidar Project as part of the required deliverables for the Umatilla Lidar project. Class 2 (ground) lidar points in conjunction with the hydro breaklines were used to create a 0.5 meter hydro-flattened Raster DEM.

Original Geographic Extent: Umatilla Wallowa Whitman Lidar Project covering approximately 557 square miles in Wallowa County, OR; Asotin County, WA; Idaho County, ID

Dataset Description of the Original Data: The Umatilla Wallowa Whitman Lidar Project called for the Planning, Acquisition, processing and derivative products of lidar data to be collected at a nominal pulse spacing (NPS) of 0.35 meter. Project specifications are based on the U.S. Geological Survey National Geospatial Program Lidar Base Specification 2021 Rev. A. The data was developed based on a horizontal datum/projection of NAD83 (2011) UTM Zone 11, Universal Transverse Mercator, meters and vertical datum of NAVD88 (GEOID18), meters. Lidar data was delivered as processed Classified LAS 1.4 files, formatted to 1,706 individual 1,000 m x 1,000 m tiles, and as tiled bare earth DEMs; all tiled to the same 1,000 m x 1,000 m schema. 

Ground Conditions: Lidar was collected in August 2022, while no snow was on the ground and rivers were at or below normal levels.  In order to post process the lidar data to meet task order specifications and meet ASPRS vertical accuracy guidelines, Aero-graphics, Inc. established a total of 37 ground control points that were used to calibrate the lidar to known ground locations established throughout the Umatilla Wallowa Whitman project area. An additional 50 independent accuracy checkpoints, 29 in Bare Earth and Urban landcovers (29 NVA points), 21 in Tall Grass and Brushland/Low Trees categories (21 VVA points), were used to assess the vertical accuracy of the data. These checkpoints were not used to calibrate or post process the data.

This metadata record supports the data entry in the NOAA Digital Coast Data Access Viewer (DAV). For this data set, the DAV is leveraging the GeoTIFF files hosted by USGS on Amazon Web Services.
</abstract>
      <purpose>To acquire detailed surface elevation data for use in conservation planning, design, research, floodplain mapping, dam safety assessments and elevation modeling, etc. Classified LAS files are used to show the manually reviewed bare earth surface. This allows the user to create Intensity Images, Breaklines and Raster DEM. The purpose of these lidar data was to produce high accuracy 3D hydro-flattened Digital Elevation Model (DEM) with a 0.5 meter cell size. These lidar point cloud data were used to create intensity images, 3D breaklines, and hydro-flattened DEMs as necessary.</purpose>
      <supplemental-information>Raster File Type = TIFF Bit Depth/Pixel Type = 32-bit float Raster Cell Size = 0.5 Meter Interpolation or Resampling Technique = Triangulated Irregular Network Required Vertical Accuracy = 19.6 cm NVA</supplemental-information>
   </item-identification>
   <keywords>
      <keyword controlled="Yes">
         <keyword-type>Theme</keyword-type>
         <thesaurus version="23.3">Global Change Master Directory (GCMD) Science Keywords</thesaurus>
         <keyword identifier="74ed1690-968e-444c-8a31-7b8344a2aad3">EARTH SCIENCE &gt; LAND SURFACE &gt; TOPOGRAPHY &gt; TERRAIN ELEVATION</keyword>
      </keyword>
      <keyword controlled="Yes">
         <keyword-type>Theme</keyword-type>
         <thesaurus version="23.3">Global Change Master Directory (GCMD) Science Keywords</thesaurus>
         <keyword identifier="395372ad-2883-4b6a-a481-6383a310ca47">EARTH SCIENCE &gt; LAND SURFACE &gt; TOPOGRAPHY &gt; TERRAIN ELEVATION &gt; DIGITAL ELEVATION/TERRAIN MODEL (DEM)</keyword>
      </keyword>
      <keyword controlled="Yes">
         <keyword-type>Theme</keyword-type>
         <thesaurus>ISO 19115 Topic Category</thesaurus>
         <keyword>elevation</keyword>
      </keyword>
      <keyword controlled="Yes">
         <keyword-type>Spatial</keyword-type>
         <thesaurus version="23.3">Global Change Master Directory (GCMD) Location Keywords</thesaurus>
         <keyword identifier="0a672f19-dad5-4114-819a-2eb55bdbb56a">CONTINENT</keyword>
      </keyword>
      <keyword controlled="Yes">
         <keyword-type>Spatial</keyword-type>
         <thesaurus version="23.3">Global Change Master Directory (GCMD) Location Keywords</thesaurus>
         <keyword identifier="753f915c-70d4-49e1-9bd5-83e75f461e30">CONTINENT &gt; NORTH AMERICA &gt; UNITED STATES OF AMERICA</keyword>
      </keyword>
      <keyword controlled="Yes">
         <keyword-type>Spatial</keyword-type>
         <thesaurus version="23.3">Global Change Master Directory (GCMD) Location Keywords</thesaurus>
         <keyword identifier="5e4b6864-4bf7-43a9-8ca6-2099cc40dd25">CONTINENT &gt; NORTH AMERICA &gt; UNITED STATES OF AMERICA &gt; IDAHO</keyword>
      </keyword>
      <keyword controlled="Yes">
         <keyword-type>Spatial</keyword-type>
         <thesaurus version="23.3">Global Change Master Directory (GCMD) Location Keywords</thesaurus>
         <keyword identifier="699d5c22-6bcd-4cfa-be0f-f06e34a63513">CONTINENT &gt; NORTH AMERICA &gt; UNITED STATES OF AMERICA &gt; OREGON</keyword>
      </keyword>
      <keyword controlled="Yes">
         <keyword-type>Spatial</keyword-type>
         <thesaurus version="23.3">Global Change Master Directory (GCMD) Location Keywords</thesaurus>
         <keyword identifier="dcef091b-18b5-48bf-b191-69ab7a3511f1">CONTINENT &gt; NORTH AMERICA &gt; UNITED STATES OF AMERICA &gt; WASHINGTON</keyword>
      </keyword>
      <keyword controlled="Yes">
         <keyword-type>Spatial</keyword-type>
         <thesaurus version="23.3">Global Change Master Directory (GCMD) Location Keywords</thesaurus>
         <keyword identifier="90761f8d-6abe-499c-b711-acec394daa59">VERTICAL LOCATION &gt; LAND SURFACE</keyword>
      </keyword>
      <keyword controlled="Yes">
         <keyword-type>Instrument</keyword-type>
         <thesaurus version="23.3">Global Change Master Directory (GCMD) Instrument Keywords</thesaurus>
         <keyword identifier="7166c458-f935-4bd9-a322-d92830cf0c33">LIDAR &gt; Light Detection and Ranging</keyword>
      </keyword>
      <keyword controlled="Yes">
         <keyword-type>Platform</keyword-type>
         <thesaurus version="23.3">Global Change Master Directory (GCMD) Platform Keywords</thesaurus>
         <keyword identifier="8b7834c1-2c66-414e-a655-2298e7dcc479">Airplane &gt; Airplane</keyword>
      </keyword>
   </keywords>
   <physical-location>
      <organization>Office for Coastal Management</organization>
      <city>Charleston</city>
      <state-province>SC</state-province>
   </physical-location>
   <data-set-information>
      <data-set-scope-code>Data Set</data-set-scope-code>
      <data-set-type>Elevation</data-set-type>
      <maintenance-frequency>None Planned</maintenance-frequency>
      <data-presentation-form>Model (digital)</data-presentation-form>
      <distribution-liability>Any conclusions drawn from the analysis of this information are not the responsibility of NOAA, the Office for Coastal Management or its partners.</distribution-liability>
      <data-set-credit>Aero-Graphics, Inc., USGS</data-set-credit>
   </data-set-information>
   <entity-attribute-information partial-listing="No" total-count="0"/>
   <support-roles>
      <support-role cc-id="1463483" in-effect="Yes">
         <support-role-type>Data Steward</support-role-type>
         <from-date>2026</from-date>
         <contact-type>Organization</contact-type>
         <contact-name>NOAA Office for Coastal Management</contact-name>
         <contact-noaa-acronym>NOAA/OCM</contact-noaa-acronym>
         <contact-email>coastal.info@noaa.gov</contact-email>
         <contact-address>2234 South Hobson Ave</contact-address>
         <contact-address-city>Charleston</contact-address-city>
         <contact-address-state>SC</contact-address-state>
         <contact-address-zip>29405-2413</contact-address-zip>
         <contact-phone-number>(843) 740-1202</contact-phone-number>
         <contact-url>https://coast.noaa.gov</contact-url>
         <contact-url-description>NOAA Office for Coastal Management Home Page</contact-url-description>
         <contact-url-function>Online Resource</contact-url-function>
      </support-role>
      <support-role cc-id="1463482" in-effect="Yes">
         <support-role-type>Distributor</support-role-type>
         <from-date>2026</from-date>
         <contact-type>Organization</contact-type>
         <contact-name>NOAA Office for Coastal Management</contact-name>
         <contact-noaa-acronym>NOAA/OCM</contact-noaa-acronym>
         <contact-email>coastal.info@noaa.gov</contact-email>
         <contact-address>2234 South Hobson Ave</contact-address>
         <contact-address-city>Charleston</contact-address-city>
         <contact-address-state>SC</contact-address-state>
         <contact-address-zip>29405-2413</contact-address-zip>
         <contact-phone-number>(843) 740-1202</contact-phone-number>
         <contact-url>https://coast.noaa.gov</contact-url>
         <contact-url-description>NOAA Office for Coastal Management Home Page</contact-url-description>
         <contact-url-function>Online Resource</contact-url-function>
      </support-role>
      <support-role cc-id="1463486" in-effect="Yes">
         <support-role-type>Distributor</support-role-type>
         <from-date>2023</from-date>
         <contact-type>Organization</contact-type>
         <contact-name>U.S. Geological Survey</contact-name>
         <contact-address>12201 Sunrise Valley Drive </contact-address>
         <contact-address-city>Reston</contact-address-city>
         <contact-address-state>VA</contact-address-state>
         <contact-address-zip>20191</contact-address-zip>
         <contact-address-country>USA</contact-address-country>
         <contact-url>https://usgs.gov</contact-url>
         <contact-url-name>USGS Home</contact-url-name>
         <contact-url-description>Home page for USGS</contact-url-description>
         <contact-url-function>Online Resource</contact-url-function>
      </support-role>
      <support-role cc-id="1463484" in-effect="Yes">
         <support-role-type>Metadata Contact</support-role-type>
         <from-date>2026</from-date>
         <contact-type>Organization</contact-type>
         <contact-name>NOAA Office for Coastal Management</contact-name>
         <contact-noaa-acronym>NOAA/OCM</contact-noaa-acronym>
         <contact-email>coastal.info@noaa.gov</contact-email>
         <contact-address>2234 South Hobson Ave</contact-address>
         <contact-address-city>Charleston</contact-address-city>
         <contact-address-state>SC</contact-address-state>
         <contact-address-zip>29405-2413</contact-address-zip>
         <contact-phone-number>(843) 740-1202</contact-phone-number>
         <contact-url>https://coast.noaa.gov</contact-url>
         <contact-url-description>NOAA Office for Coastal Management Home Page</contact-url-description>
         <contact-url-function>Online Resource</contact-url-function>
      </support-role>
      <support-role cc-id="1463485" in-effect="Yes">
         <support-role-type>Point of Contact</support-role-type>
         <from-date>2026</from-date>
         <contact-type>Organization</contact-type>
         <contact-name>NOAA Office for Coastal Management</contact-name>
         <contact-noaa-acronym>NOAA/OCM</contact-noaa-acronym>
         <contact-email>coastal.info@noaa.gov</contact-email>
         <contact-address>2234 South Hobson Ave</contact-address>
         <contact-address-city>Charleston</contact-address-city>
         <contact-address-state>SC</contact-address-state>
         <contact-address-zip>29405-2413</contact-address-zip>
         <contact-phone-number>(843) 740-1202</contact-phone-number>
         <contact-url>https://coast.noaa.gov</contact-url>
         <contact-url-description>NOAA Office for Coastal Management Home Page</contact-url-description>
         <contact-url-function>Online Resource</contact-url-function>
      </support-role>
   </support-roles>
   <extents>
      <currentness-reference>Ground Condition</currentness-reference>
      <extent cc-id="1463511">
         <geographic-areas>
            <geographic-area cc-id="1463513">
               <west-bound>-117.482033</west-bound>
               <east-bound>-116.37041</east-bound>
               <north-bound>46.280972</north-bound>
               <south-bound>45.392623</south-bound>
            </geographic-area>
         </geographic-areas>
         <time-frames>
            <time-frame cc-id="1463512">
               <time-frame-type>Range</time-frame-type>
               <start-date-time>2022-08-11</start-date-time>
               <end-date-time>2022-08-29</end-date-time>
            </time-frame>
         </time-frames>
      </extent>
   </extents>
   <spatial-information>
      <spatial-representation>
         <representations-used>
            <grid>Yes</grid>
            <vector>No</vector>
            <text-table>No</text-table>
            <tin>No</tin>
            <stereo-model>No</stereo-model>
            <video>No</video>
         </representations-used>
      </spatial-representation>
      <reference-systems>
         <reference-system>
            <coordinate-reference-system>
               <crs-type>Vertical</crs-type>
               <epsg-code>EPSG:5703</epsg-code>
               <epsg-name>NAVD88 height</epsg-name>
               <datum-name>North American Vertical Datum 1988</datum-name>
               <axes>
                  <axis>
                     <order>1</order>
                     <name>Gravity-related height</name>
                     <abbreviation>H</abbreviation>
                     <units>metre</units>
                     <orientation>up</orientation>
                  </axis>
               </axes>
            </coordinate-reference-system>
         </reference-system>
         <reference-system>
            <coordinate-reference-system>
               <crs-type>Projected</crs-type>
               <epsg-code>EPSG:6340</epsg-code>
               <epsg-name>NAD83(2011) / UTM zone 11N</epsg-name>
               <datum-name>NAD83 (National Spatial Reference System 2011)</datum-name>
               <ellipsoid>GRS 1980</ellipsoid>
               <semimajor-axis>6378137</semimajor-axis>
               <flattening-ratio>298.257222101</flattening-ratio>
               <base-crs-name>NAD83(2011)</base-crs-name>
               <projection-name>UTM zone 11N</projection-name>
               <conversion-method>Transverse Mercator</conversion-method>
               <parameters>
                  <parameter>
                     <parameter-name>Latitude of natural origin</parameter-name>
                     <parameter-value>0° 0' 0" N</parameter-value>
                  </parameter>
                  <parameter>
                     <parameter-name>Longitude of natural origin</parameter-name>
                     <parameter-value>117° 0' 0" W</parameter-value>
                  </parameter>
                  <parameter>
                     <parameter-name>Scale factor at natural origin</parameter-name>
                     <parameter-value>0.9996</parameter-value>
                  </parameter>
                  <parameter>
                     <parameter-name>False easting</parameter-name>
                     <parameter-value>500000</parameter-value>
                     <parameter-units>metre</parameter-units>
                  </parameter>
                  <parameter>
                     <parameter-name>False northing</parameter-name>
                     <parameter-value>0</parameter-value>
                     <parameter-units>metre</parameter-units>
                  </parameter>
               </parameters>
               <axes>
                  <axis>
                     <order>1</order>
                     <name>Easting</name>
                     <abbreviation>E</abbreviation>
                     <units>metre</units>
                     <orientation>east</orientation>
                  </axis>
                  <axis>
                     <order>2</order>
                     <name>Northing</name>
                     <abbreviation>N</abbreviation>
                     <units>metre</units>
                     <orientation>north</orientation>
                  </axis>
               </axes>
            </coordinate-reference-system>
         </reference-system>
      </reference-systems>
   </spatial-information>
   <access-information>
      <data-license-type>Custom</data-license-type>
      <security-class>Unclassified</security-class>
      <data-access-procedure>Data is available online for bulk and custom downloads.</data-access-procedure>
      <data-access-constraints>None</data-access-constraints>
      <data-use-constraints>Users should be aware that temporal changes may have occurred since this data set was collected and some parts of this data may no longer represent actual surface conditions. Users should not use this data for critical applications without a full awareness of its limitations.</data-use-constraints>
   </access-information>
   <distribution-information>
      <distribution cc-id="1463487">
         <download-url>https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=13945/details/13945</download-url>
         <distributor cc-id="1463482">
            <from-date>2026</from-date>
            <contact-type>Organization</contact-type>
            <contact-name>NOAA Office for Coastal Management</contact-name>
         </distributor>
         <file-name>Customized Download</file-name>
         <description>Create custom data files by choosing data area, map projection, file format, etc. A new metadata will be produced to reflect your request using this record as a base.</description>
         <distribution-format>Not Applicable</distribution-format>
         <compression>Zip</compression>
      </distribution>
      <distribution cc-id="1463488">
         <download-url>https://prd-tnm.s3.amazonaws.com/index.html?prefix=StagedProducts/Elevation/OPR/Projects/OR_UmatillaWallowaWhitman_B22/OR_UmatillaWallowaWhitman_1_B22/TIFF/</download-url>
         <distributor cc-id="1463486">
            <from-date>2023</from-date>
            <contact-type>Organization</contact-type>
            <contact-name>U.S. Geological Survey</contact-name>
         </distributor>
         <file-name>Bulk Download</file-name>
         <description>Bulk download of data files in GeoTIFF format, UTM Zone 11N NAD83(2011), meters coordinates and NAVD88 (GEOID18) elevations in meters.</description>
         <distribution-format>GeoTIFF</distribution-format>
      </distribution>
   </distribution-information>
   <urls>
      <url cc-id="1463494">
         <url>https://coast.noaa.gov/dataviewer/</url>
         <name>NOAA's Office for Coastal Management (OCM) Data Access Viewer (DAV)</name>
         <url-type>Online Resource</url-type>
         <file-resource-format>HTML</file-resource-format>
         <description>The Data Access Viewer (DAV) allows a user to search for and download elevation, imagery, and land cover data for the coastal U.S. and its territories. The data, hosted by the NOAA Office for Coastal Management, can be customized and requested for free download through a checkout interface. An email provides a link to the customized data, while the original data set is available through a link within the viewer.</description>
      </url>
      <url cc-id="1463490">
         <url>https://prd-tnm.s3.amazonaws.com/StagedProducts/Elevation/metadata/OR_UmatillaWallowaWhitman_B22/OR_UmatillaWallowaWhitman_1_B22/reports/300194_%20OR_UmatillaWallowaWhitman_1_B22_ProjectReport.pdf</url>
         <name>Lidar Report</name>
         <url-type>Online Resource</url-type>
         <file-resource-format>pdf</file-resource-format>
         <description>Link to the lidar report</description>
      </url>
      <url cc-id="1463491">
         <url>https://prd-tnm.s3.amazonaws.com/StagedProducts/Elevation/metadata/OR_UmatillaWallowaWhitman_B22/USGS_OR_UmatillaWallowaWhitman_B22_Project_Report.pdf</url>
         <name>USGS Project Report</name>
         <url-type>Online Resource</url-type>
         <file-resource-format>pdf</file-resource-format>
         <description>Link to the USGS Project Report that provides information about the project, vertical accuracy results, and the point classes and sensors used.</description>
      </url>
      <url cc-id="1463489">
         <url>https://prd-tnm.s3.amazonaws.com/index.html?prefix=StagedProducts/Elevation/metadata/OR_UmatillaWallowaWhitman_B22/</url>
         <name>USGS Additional Info</name>
         <url-type>Online Resource</url-type>
         <description>Link to the reports, breaklines, metadata, and spatial metadata.</description>
      </url>
      <url cc-id="1463492">
         <url>https://s3-us-west-2.amazonaws.com/usgs-lidar-public/OR_UmatillaWallowaWhitman_1_B22/ept.json</url>
         <name>USGS Entwine Point Tile (EPT)</name>
         <url-type>Online Resource</url-type>
         <file-resource-format>json</file-resource-format>
         <description>Entwine Point Tile (EPT) is a simple and flexible octree-based storage format for point cloud data. The data is organized in such a way that the data can be reasonably streamed over the internet, pulling only the points you need. EPT files can be queried to return a subset of the points that give you a representation of the area. As you zoom further in, you are requesting higher and higher densities. A dataset in EPT will contain a lot of files, however, the ept.json file describes all the rest. The EPT file can be used in Potree and QGIS to view the point cloud.</description>
      </url>
      <url cc-id="1463493">
         <url>https://usgs.entwine.io/data/view.html?r=%22https://s3-us-west-2.amazonaws.com/usgs-lidar-public/OR_UmatillaWallowaWhitman_1_B22%22</url>
         <name>USGS 3D View</name>
         <url-type>Online Resource</url-type>
         <description>Link to view the point cloud, using the Entwine Point Tile (EPT) format, in the 3D Potree viewer.</description>
      </url>
   </urls>
   <technical-environment>
      <description>Optech LMS; LP360; Microstation; Terrascan; ArcGIS 10.6; Windows 8; .las 858 GB</description>
   </technical-environment>
   <data-quality>
      <horizontal-positional-accuracy>Only checkpoints photo-identifiable in the intensity imagery can be used to test the horizontal accuracy of the lidar. Photo-identifiable checkpoints in intensity imagery typically include checkpoints located at the ends of paint stripes on concrete or asphalt surfaces or checkpoints located at 90 degree corners of different reflectivity, e.g. a sidewalk corner adjoining a grass surface. The xy coordinates of checkpoints, as defined in the intensity imagery, are compared to surveyed xy coordinates for each photo-identifiable checkpoint. These differences are used to compute the tested horizontal accuracy of the lidar. As not all projects contain photo-identifiable checkpoints, the horizontal accuracy of the lidar cannot always be tested.

Lidar vendors calibrate their lidar systems during installation of the system and then again for every project acquired. Typical calibrations include cross flights that capture features from multiple directions that allow adjustments to be performed so that the captured features are consistent between all swaths and cross flights from all directions. This data set was produced to meet ASPRS Positional Accuracy Standards for Digital Geospatial Data (2014) for a 41 cm RMSEx/RMSEy Horizontal Accuracy Class which equates to Positional Horizontal Accuracy = +/- 1 meter at a 95% confidence level</horizontal-positional-accuracy>
      <vertical-positional-accuracy>This data set was produced to meet ASPRS Positional Accuracy Standard for Digital Geospatial Data (2014) for a 10-cm RMSEz Vertical Accuracy Class.

USGS Determined DEM Vertical Accuracy

Tested NVA RMSEz = 7.08 cm

Tested 95th percentile value for VVA is: 15.02 cm

For more information see the USGS project report and the lidar report. The links to these reports are provided in the URL section of this metadata record.</vertical-positional-accuracy>
      <completeness-report>Datasets contain complete coverage of tiles. No points have been removed or excluded. A visual qualitative assessment was performed to ensure data completeness. There are no void areas or missing data. The raw point cloud is of good quality and data passes Non-Vegetated Vertical Accuracy specifications.</completeness-report>
      <conceptual-consistency>Data covers the entire area specified for this project.</conceptual-consistency>
   </data-quality>
   <data-management>
      <resources-identified>Yes</resources-identified>
      <resources-budget-percentage>Unknown</resources-budget-percentage>
      <data-access-directive-compliant>Yes</data-access-directive-compliant>
      <archive-location>NCEI-NC</archive-location>
      <data-protection-plan>Data is backed up to cloud storage.</data-protection-plan>
   </data-management>
   <lineage>
      <lineage-statement>The NOAA Office for Coastal Management (OCM) ingested references to the USGS GeoTIFF files that are hosted on Amazon Web Services (AWS), into the Digital Coast Data Access Viewer (DAV). The DAV accesses the raster data as it resides on AWS.

</lineage-statement>
      <lineage-sources>
         <lineage-source cc-id="1463502">
            <citation-title>USGS AWS GeoTIFF Files - OR_UmatillaWallowaWhitman_1</citation-title>
            <contact-type>Organization</contact-type>
            <contact-name>USGS</contact-name>
            <contact-role-type>Publisher</contact-role-type>
            <citation-url>https://prd-tnm.s3.amazonaws.com/index.html?prefix=StagedProducts/Elevation/OPR/Projects/OR_UmatillaWallowaWhitman_B22/OR_UmatillaWallowaWhitman_1_B22/TIFF/</citation-url>
            <citation-url-name>USGS AWS GeoTIFF Files for OR_UmatillaWallowaWhitman_1</citation-url-name>
         </lineage-source>
      </lineage-sources>
      <lineage-process-steps>
         <lineage-process-step cc-id="1463503">
            <sequence-number>1</sequence-number>
            <description>The boresight for each lift was done individually as the solution may change slightly from lift to lift. The following steps describe the Raw Data Processing and Boresight process: 1) Technicians processed the raw data to LAS format flight lines using the final GPS/IMU solution. This LAS data set was used as source data for boresight. 2) Technicians first used proprietary  and commercial software to calculate initial boresight adjustment angles based on sample areas selected in the lift. These areas cover calibration flight lines collected in the lift, cross tie and production flight lines. These areas are well distributed in the lift coverage and cover multiple terrain types that are necessary for boresight angle calculation. The technician then analyzed the results and made any necessary additional adjustment until it is acceptable for the selected areas. 3) Once the boresight angle calculation was completed for the selected areas, the adjusted settings were applied to all of the flight lines of the lift and checked for consistency. The technicians utilized commercial and proprietary software packages to analyze how well flight line overlaps match for the entire lift and adjusted as necessary until the results met the project specifications. 4) Once all lifts were completed with individual boresight adjustment, the technicians checked and corrected the vertical misalignment of all flight lines and also the matching between data and ground truth. The relative accuracy was less than or equal to 6 cm RMSEz within individual swaths and less than or equal to 8 cm RMSEz or within swath overlap (between adjacent swaths). 5) The technicians ran a final vertical accuracy check of the boresighted flight lines against the surveyed check points after the z correction to ensure the requirement of NVA = 19.6 cm 95% Confidence Level (Required Accuracy) was met. Point classification was performed according to USGS Lidar Base Specification 2021 Rev. A, and breaklines were collected for water features. Bare earth DEMs were exported from the classified point cloud using collected breaklines for hydroflattening.</description>
            <process-date-time>2022-10-01T00:00:00</process-date-time>
         </lineage-process-step>
         <lineage-process-step cc-id="1463504">
            <sequence-number>2</sequence-number>
            <description>LAS Point Classification: The point classification is performed as described below. The bare earth surface is then manually reviewed to ensure correct classification on the Class 2 (Ground) points. After the bare-earth surface is finalized, it is then used to generate all hydro-breaklines through heads-up digitization. All ground (ASPRS Class 2) lidar data inside of the Lake Pond and Double Line Drain hydro flattening breaklines were then classified to water (ASPRS Class 9) using TerraScan macro functionality. A buffer of 0.35 meters was also used around each hydro-flattened feature to classify these ground (ASPRS Class 2) points to Ignored ground (ASPRS Class 20). All Lake Pond Island and Double Line Drain Island features were checked to ensure that the ground (ASPRS Class 2) points were reclassified to the correct classification after the automated classification was completed. All data was manually reviewed and any remaining artifacts removed using functionality provided by TerraScan and TerraModeler. Global Mapper was used as a final check of the bare earth dataset. The withheld bit was set on the withheld points previously identified in TerraScan before the ground classification routine was performed. The withheld bit was set on class 7 and class 18 in TerraScan after all classification was complete. Dewberry proprietary software was then used to create the deliverable industry-standard LAS files for both the Point Cloud Data and the Bare Earth. Dewberry proprietary software was used to perform final statistical analysis of the classes in the LAS files, on a per tile level to verify final classification metrics and full LAS header information.</description>
            <process-date-time>2023-02-15T00:00:00</process-date-time>
         </lineage-process-step>
         <lineage-process-step cc-id="1463505">
            <sequence-number>3</sequence-number>
            <description>Data was tested at 0.27 meter nominal pulse spacing and 13.8 points per square meter (ppsm). The average density was tested on the LAS data using geometrically reliable (withheld and noise points excluded) first-return points. (A)NPD was tested using rasters which produce the average number of points within each cell.</description>
            <process-date-time>2023-03-16T00:00:00</process-date-time>
         </lineage-process-step>
         <lineage-process-step cc-id="1463506">
            <sequence-number>4</sequence-number>
            <description>Maximum Surface Height Rasters were produced using proprietary software as ancillary data from the classified lidar point cloud in order to evaluate the withheld bit flag proof of performance for points that cannot be reasonably interpreted as valid surface returns. These were produced using all returns, withheld flagged points excluded, and using the highest elevation point value from each pixel. These rasters are 32-bit, floating point format and delivered as GeoTIFF files per tile. Cell size of the MSHR is 1 meter. MSHR are generated from the point cloud data and will not be altered after creation nor will there be further maintenance on this product.</description>
            <process-date-time>2023-03-17T00:00:00</process-date-time>
         </lineage-process-step>
         <lineage-process-step cc-id="1463507">
            <sequence-number>5</sequence-number>
            <description>Swath Separation Images were produced using LP360 for the entire project area. Swath separation images use color-coding to illustrate differences in elevation (z-) values where swaths overlap. The color-coded images are semi-transparent and overlay the lidar intensity image. They are ancillary data used as visual aids to more easily identify regions within point cloud datasets that may have suspect interswath alignment or other geometric issues. Imagery was created using last returns with all classification and bit flags, except for noise and withheld bit flag are included. Images are derived from a TIN and have a 50% transparent RGB layer over lidar intensity. Color intervals are as follows for QL1 data: 0-8cm, green; 8-16cm, yellow; &gt;16cm, red. These files were produced as GeoTIFF tiles using a cell size of 1 meter. SSI are generated from the point cloud data and will not be altered after creation nor will there be further maintenance on this product.</description>
            <process-date-time>2023-03-17T00:00:00</process-date-time>
         </lineage-process-step>
         <lineage-process-step cc-id="1463508">
            <sequence-number>6</sequence-number>
            <description>Supplemental Project Information</description>
            <process-date-time>2022-03-24T00:00:00</process-date-time>
         </lineage-process-step>
         <lineage-process-step cc-id="1463509">
            <sequence-number>7</sequence-number>
            <description>Hydro Flattened Raster DEM Process: Class 2 (ground) lidar points in conjunction with the hydro breaklines were used to create a 0.5 meter hydro-flattened Raster DEM. Using LP360, a TIFF file was created for each tile. Each surface is reviewed using ArcMap to check for any surface anomalies or incorrect elevations found within the surface.</description>
            <process-date-time>2023-02-25T00:00:00</process-date-time>
         </lineage-process-step>
         <lineage-process-step cc-id="1463510">
            <sequence-number>8</sequence-number>
            <description>The NOAA Office for Coastal Management (OCM) created references to the USGS GeoTIFF files that were ingested into the NOAA Digital Coast Data Access Viewer (DAV). No changes were made to the data. The DAV will access the raster data as it resides on Amazon Web Services (AWS).

These are the GeoTIFF files that are being accessed:
https://prd-tnm.s3.amazonaws.com/index.html?prefix=StagedProducts/Elevation/OPR/Projects/OR_UmatillaWallowaWhitman_B22/OR_UmatillaWallowaWhitman_1_B22/TIFF/</description>
            <process-date-time>2026-01-29T00:00:00</process-date-time>
            <process-contact>
               <contact-type>Organization</contact-type>
               <contact-name>Office for Coastal Management</contact-name>
               <contact-noaa-acronym>OCM</contact-noaa-acronym>
               <contact-ror>https://ror.org/05v14bq57</contact-ror>
               <contact-address>2234 South Hobson Avenue</contact-address>
               <contact-address-city>Charleston</contact-address-city>
               <contact-address-state>SC</contact-address-state>
               <contact-address-zip>29405-2413</contact-address-zip>
               <contact-url>https://www.coast.noaa.gov/</contact-url>
            </process-contact>
         </lineage-process-step>
      </lineage-process-steps>
   </lineage>
   <related-items>
      <related-item>
         <catalog-item-id>73000</catalog-item-id>
         <catalog-item-type>Data Set</catalog-item-type>
         <title>2022 USGS Lidar: Umatilla Wallowa Whitman (ID, OR, WA)</title>
         <relationship-type>Cross Reference</relationship-type>
      </related-item>
   </related-items>
   <catalog-details>
      <guid>gov.noaa.nmfs.inport:79179</guid>
      <metadata-record-created-by pers-id="20143">Rebecca Mataosky</metadata-record-created-by>
      <metadata-record-created>2026-01-29T16:53:21</metadata-record-created>
      <metadata-record-last-modified-by pers-id="0">SysAdmin InPortAdmin</metadata-record-last-modified-by>
      <metadata-record-last-modified>2026-03-04T19:17:17</metadata-record-last-modified>
      <record-published>2026-01-29</record-published>
      <owner-organization>OCM Partners</owner-organization>
      <owner-organization-acronym>OCMP</owner-organization-acronym>
      <owner-organization-address/>
      <owner-organization-address-city/>
      <owner-organization-address-state/>
      <owner-organization-address-zip/>
      <owner-organization-address-country/>
      <owner-organization-phone/>
      <owner-organization-url/>
      <owner-organization-business-hours/>
      <owner-organization-group-id>1002</owner-organization-group-id>
      <publication-status>Public</publication-status>
      <limited-metadata-available>No</limited-metadata-available>
      <is-do-not-publish>No</is-do-not-publish>
      <metadata-last-review-date>2024-06-24</metadata-last-review-date>
      <metadata-review-frequency>1 Year</metadata-review-frequency>
      <metadata-next-review-date>2025-06-24</metadata-next-review-date>
   </catalog-details>
</inport-metadata>
