<?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>58285</catalog-item-id>
      <title>2005 USFS Lidar: Yaquina, OR</title>
      <short-name>2005 yaquina m8951</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>49401</parent-catalog-item-id>
      <parent-title>Lidar - partner (no harvest)</parent-title>
      <parent-catalog-item-type>Project</parent-catalog-item-type>
      <status>Completed</status>
      <creation-date>2019-12-06</creation-date>
      <abstract>Watershed Sciences, Inc. (WS) collected Light Detection and Ranging (LiDAR) data for the United States Forest Service (USFS) in the Elk Creek watershed between July 13-15, 2005. The survey area is located inside the Siuslaw National Forest and encompasses all of Spout Creek (northern extent), Feagles Creek (southern extent), the confluence of these streams with Elk Creek (western extent), and up the headwaters of Elk Creek (eastern extent). The initial study area (~23,454 acres) was buffered by 200 meters, extending the contracted survey area to 26,385 acres.
 
Laser points were collected over the study area using an Optech ALTM 3100 LiDAR system set to acquire points at an average spacing of &gt;8 points per square meter. The system also recorded individual return intensities (per laser return) that are used to create models that display surface reflectivity. 


No metadata record for this data set was provided to the NOAA Office for Coastal Management (OCM). This record was created with information from the data report. A link to the data report is provided in the URL section of this metadata record.</abstract>
      <purpose>The primary purpose of the lidar survey was to establish measurements of the bare earth surface, as well as top surface feature data for providing geometric inputs for modeling, other numerical modeling and economic related assessments.</purpose>
   </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>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="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="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="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>Point Cloud (Digital)</data-presentation-form>
      <distribution-liability>Any conclusions drawn from the analysis of this information are not the responsibility of the USDA Forest Service, DOGAMI, NOAA, the Office for Coastal Management or its partners.</distribution-liability>
      <data-set-credit>USDA Forest Service</data-set-credit>
   </data-set-information>
   <entity-attribute-information partial-listing="No" total-count="0"/>
   <support-roles>
      <support-role cc-id="888352" in-effect="Yes">
         <support-role-type>Data Steward</support-role-type>
         <from-date>2019</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="888353" in-effect="Yes">
         <support-role-type>Distributor</support-role-type>
         <from-date>2019</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="888354" in-effect="Yes">
         <support-role-type>Metadata Contact</support-role-type>
         <from-date>2019</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="888355" in-effect="Yes">
         <support-role-type>Point of Contact</support-role-type>
         <from-date>2019</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="1143393">
         <geographic-areas>
            <geographic-area cc-id="1143395">
               <west-bound>-123.75</west-bound>
               <east-bound>-123.55</east-bound>
               <north-bound>44.6</north-bound>
               <south-bound>44.46</south-bound>
            </geographic-area>
         </geographic-areas>
         <time-frames>
            <time-frame cc-id="1143394">
               <time-frame-type>Range</time-frame-type>
               <start-date-time>2005-07-13</start-date-time>
               <end-date-time>2005-07-15</end-date-time>
               <description>Dates of collection.</description>
            </time-frame>
         </time-frames>
      </extent>
   </extents>
   <spatial-information>
      <spatial-resolution>
         <horizontal-distance>.35</horizontal-distance>
         <horizontal-distance-units>Meter</horizontal-distance-units>
      </spatial-resolution>
      <spatial-representation>
         <representations-used>
            <vector>Yes</vector>
         </representations-used>
      </spatial-representation>
      <reference-systems>
         <reference-system>
            <coordinate-reference-system>
               <crs-type>Geographic 3D</crs-type>
               <epsg-code>EPSG:4957</epsg-code>
               <epsg-name>NAD83(HARN)</epsg-name>
               <datum-name>NAD83 (High Accuracy Reference Network)</datum-name>
               <ellipsoid>GRS 1980</ellipsoid>
               <semimajor-axis>6378137</semimajor-axis>
               <flattening-ratio>298.257222101</flattening-ratio>
               <axes>
                  <axis>
                     <order>1</order>
                     <name>Geodetic Lattitude</name>
                     <abbreviation>Lat</abbreviation>
                     <units>degree</units>
                     <orientation>north</orientation>
                  </axis>
                  <axis>
                     <order>2</order>
                     <name>Geodetic Longitude</name>
                     <abbreviation>Lon</abbreviation>
                     <units>degree</units>
                     <orientation>east</orientation>
                  </axis>
                  <axis>
                     <order>3</order>
                     <name>Ellipsoidal height</name>
                     <abbreviation>h</abbreviation>
                     <units>metre</units>
                     <orientation>up</orientation>
                  </axis>
               </axes>
            </coordinate-reference-system>
         </reference-system>
      </reference-systems>
   </spatial-information>
   <access-information>
      <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="888356">
         <download-url>https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=8951</download-url>
         <distributor cc-id="888353">
            <from-date>2019</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, product type, map projection, file format, datum, etc. A new metadata will be produced to reflect your request using this record as a base.</description>
         <!--Note: file-type is deprecated-->
         <file-type>Zip</file-type>
         <compression>Zip</compression>
      </distribution>
      <distribution cc-id="888357">
         <download-url>https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/8951/index.html</download-url>
         <distributor cc-id="888353">
            <from-date>2019</from-date>
            <contact-type>Organization</contact-type>
            <contact-name>NOAA Office for Coastal Management</contact-name>
         </distributor>
         <file-name>Bulk Download</file-name>
         <description>Bulk download of lidar files in laz format, geographic coordinates, orthometric heights.</description>
         <!--Note: file-type is deprecated-->
         <file-type>LAZ</file-type>
         <distribution-format>LAS/LAZ - LASer</distribution-format>
         <compression>Zip</compression>
      </distribution>
   </distribution-information>
   <urls>
      <url cc-id="888359">
         <url>https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/8951/supplemental/extent_2005Yaquina_m8951.kmz</url>
         <name>Browse graphic</name>
         <url-type>Browse Graphic</url-type>
         <file-resource-format>KML</file-resource-format>
         <description>This graphic displays the footprint for this lidar data set.</description>
      </url>
      <url cc-id="888358">
         <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="888360">
         <url>https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/8951/supplemental/Yaquina_LiDAR_Survey_Report.pdf</url>
         <name>Data report</name>
         <url-type>Online Resource</url-type>
         <file-resource-format>pdf</file-resource-format>
         <description>Data report</description>
      </url>
   </urls>
   <data-quality>
      <horizontal-positional-accuracy>As described in Section 7.5 of the ASPRS Positional Accuracy Standards for Digital Geospatial Data, the horizontal errors in lidar data are largely a function of GNSS positional error, INS angular error, and flying altitude. Therefore, lidar data collected with GNSS error of 8cm and the IMU error of 0.00427 degrees at an altitude of 1,965m; the expected radial horizontal positional error will be RMSEr = 28.5cm.</horizontal-positional-accuracy>
      <vertical-positional-accuracy>Absolute Accuracy: This is the comparison of laser points to real time kinematic (RTK) ground level survey data. A total of 354 RTK GPS measurements were compared to ground laser points collected for comparison with the LiDAR point data. The deviation RMSE is 0.054 meters and the standard deviation is 0.053 meters, with a median (50th percentile) absolute deviation of 0.036 meters and a 95th percentile of 0.102 meters.

Internal Consistency: Internal consistency refers to the ability to place a laser point in the same location over multiple flight lines, GPS conditions and aircraft attitudes. The data were analyzed for internal consistency between opposing and orthogonal flight lines and passed divergence test requirements of less than 0.15 meters per any one overlapping flight line.

Laser Noise: For any given target, laser noise is the breadth of the data cloud per laser return (i.e., last, first, etc.). Lower intensity surfaces (roads, rooftops, still/calm water) will experience higher laser noise. The laser noise range for this mission varies between 0.040 - 0.070 meters</vertical-positional-accuracy>
   </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-CO</archive-location>
      <data-protection-plan>Data is backed up to tape and to cloud storage.</data-protection-plan>
   </data-management>
   <lineage>
      <lineage-statement>Watershed Sciences, Inc. (WS) collected Light Detection and Ranging (LiDAR) data for the United States Forest Service (USFS) in the Elk Creek watershed between July 13-15, 2005. NOAA OCM received the data and ingested it into the Digital Coast Data Access Viewer for distribution.</lineage-statement>
      <lineage-sources>
         <lineage-source cc-id="1143387">
            <citation-title>processed lidar data</citation-title>
            <contact-type>Organization</contact-type>
            <contact-name>Watershed Sciences (WSI)</contact-name>
            <contact-role-type>Originator</contact-role-type>
         </lineage-source>
         <lineage-source cc-id="1143388">
            <citation-title>raw lidar data</citation-title>
            <contact-type>Organization</contact-type>
            <contact-name>Watershed Sciences (WSI)</contact-name>
            <contact-role-type>Originator</contact-role-type>
         </lineage-source>
      </lineage-sources>
      <lineage-process-steps>
         <lineage-process-step cc-id="1143389">
            <sequence-number>1</sequence-number>
            <description>Acquisition. 
The Optech 3100 system was set to a 71kHz laser repetition rate and flown at 1,000 meters above ground level (AGL), capturing a 20o scan width (10 o from NADIR). These settings yielded points with an average density of &gt; 8.0 per square meter, with an average spot spacing of 32cm. The entire area was surveyed with opposing flight line overlap of 50% to reduce laser shadowing and increase surface laser painting. The system allows up to four range measurements per pulse, and all were processed for the output datasets. The data stream from the IMU was stored independently during the flight, and was differentially corrected and integrated with LiDAR pulse data during post processing. Throughout the survey, a dual frequency DGPS base station recorded fast static (1 Hz) data. The station was located at the eastern edge of the study area, near Marys Peak, Oregon.</description>
            <process-date-time>2017-01-01T00:00:00</process-date-time>
         </lineage-process-step>
         <lineage-process-step cc-id="1143391">
            <sequence-number>2</sequence-number>
            <description>Two differential GPS units were deployed and used to process kinematic solutions to the onboard GPS and inertial measurement unit (IMU) using PosPAC v4.2. Points were computed per flight line using the REALM Survey Suite v3.5.2. Microstation V8 and TerraScan were used to import the points into bins, remove pits and birds, and compute the bare earth model. TerraModeler was then used to create TINs and output ARCINFO ASCII lattice models, which were then imported into ArcMap to render one-meter mosaics of first returns, vegetation and ground models.</description>
         </lineage-process-step>
         <lineage-process-step cc-id="1143390">
            <sequence-number>3</sequence-number>
            <description>The NOAA Office for Coastal Management (OCM) received 230 lidar point cloud files in laz format from DOGAMI. The files contained lidar elevation and intensity measurements. The data were in UTM 10N coordinates and NAVD88 (Geoid03) elevations, with all units in meters. The data were classified as: 1-Unclassified, 2-Ground. 
OCM performed the following processing on the data for Digital Coast storage and provisioning purposes:

1. An internal OCM script was run to check the number of points by classification and by flight ID and the gps and intensity ranges.

2. Internal OCM scripts were run on the laz files to convert from orthometric (NAVD88) elevations to ellipsoid elevations using the Geoid 03 model, to convert from UTM 10N NAD83  coordinates in meters, to geographic coordinates, to assign the geokeys, and to sort the data by gps time for better compression.</description>
            <process-date-time>2019-11-27T00:00:00</process-date-time>
            <process-contact>
               <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>
            </process-contact>
            <source-citation cc-id="1143387">processed lidar data</source-citation>
         </lineage-process-step>
      </lineage-process-steps>
   </lineage>
   <related-items>
      <related-item>
         <catalog-item-id>58297</catalog-item-id>
         <catalog-item-type>Data Set</catalog-item-type>
         <title>2005 USFS Lidar DEM: Yaquina, OR</title>
         <relationship-type>Cross Reference</relationship-type>
         <notes>Bare Earth DEM</notes>
      </related-item>
   </related-items>
   <catalog-details>
      <guid>gov.noaa.nmfs.inport:58285</guid>
      <metadata-record-created-by pers-id="21148">Blake Waring</metadata-record-created-by>
      <metadata-record-created>2019-12-06T14:01:16</metadata-record-created>
      <metadata-record-last-modified-by pers-id="0">SysAdmin InPortAdmin</metadata-record-last-modified-by>
      <metadata-record-last-modified>2023-10-17T16:12:19</metadata-record-last-modified>
      <record-published>2022-03-16</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>2022-03-16</metadata-last-review-date>
      <metadata-review-frequency>1 Year</metadata-review-frequency>
      <metadata-next-review-date>2023-03-16</metadata-next-review-date>
   </catalog-details>
</inport-metadata>
