<?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>50173</catalog-item-id>
      <title>2013 Puget Sound LiDAR Consortium (PSLC) Topographic LiDAR: Saddle Mountain</title>
      <short-name>wa2013_pslc_saddlemountain_m3675_metadata</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>
      <publication-date>2014-03-25</publication-date>
      <abstract>In October 2013, WSI, a Quantum Spatial Company (QSI), was contracted by the Puget Sound LiDAR Consortium (PSLC) to collect Light Detection and Ranging (LiDAR) data in the fall of 2013 for the Saddle Mountain site in south-central Washington.  172,093 acres collected.</abstract>
      <purpose>Data were collected to aid the PSLC in providing complete coverage of the Saddle Mountain fault system for earthquake hazard assessment and mapping. The Saddle Mountain study area is a continuation of data collection within the greater Hanford area, and is of key importance due to its proximity to critical infrastructure and development.</purpose>
      <notes>10817</notes>
      <supplemental-information>A footprint of this data set may be viewed in Google Earth at:
https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/3675/supplemental/wa2013_pslc_saddlemountain_m3675.kmz 

The final report for this project can be viewed at: 
https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/3675/supplemental/wa2013_pslc_saddlemountain_m3675_surveyreport.pdf</supplemental-information>
   </item-identification>
   <keywords>
      <keyword controlled="Yes">
         <keyword-type>Theme</keyword-type>
         <thesaurus>ISO 19115 Topic Category</thesaurus>
         <keyword>elevation</keyword>
      </keyword>
      <keyword controlled="No">
         <keyword-type>Theme</keyword-type>
         <keyword>LAZ</keyword>
      </keyword>
      <keyword controlled="No">
         <keyword-type>Theme</keyword-type>
         <keyword>Saddle Mountain Fault</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>
      <maintenance-frequency>As Needed</maintenance-frequency>
      <data-presentation-form>las</data-presentation-form>
      <entity-attribute-overview>LiDAR points in LAZ format (ASPRS Classes 1,2)</entity-attribute-overview>
      <entity-attribute-detail-citation>none</entity-attribute-detail-citation>
      <distribution-liability>Any conclusions drawn from the analysis of this information are not the responsibility
of Terrapoint, PSLC, NOAA, the Office for Coastal Management or its partners.</distribution-liability>
      <data-set-credit>Please credit the Puget Sound LiDAR Consortium (PSLC) for these data. The PSLC is supported by the Puget Sound Regional Council, the National Aeronautical and Space Administration (NASA), the United States Geological Survey (USGS) and numerous partners in local, state, and tribal government.</data-set-credit>
   </data-set-information>
   <entity-attribute-information partial-listing="No" total-count="0"/>
   <support-roles>
      <support-role cc-id="693116" in-effect="Yes">
         <support-role-type>Data Steward</support-role-type>
         <from-date>2014-03-25</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="693118" in-effect="Yes">
         <support-role-type>Distributor</support-role-type>
         <from-date>2014-03-25</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="693119" in-effect="Yes">
         <support-role-type>Metadata Contact</support-role-type>
         <from-date>2014-03-25</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="693117" in-effect="Yes">
         <support-role-type>Point of Contact</support-role-type>
         <from-date>2014-03-25</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="1135841">
         <geographic-areas>
            <geographic-area cc-id="1135843">
               <west-bound>-119.984536</west-bound>
               <east-bound>-119.176177</east-bound>
               <north-bound>46.8621929</north-bound>
               <south-bound>46.6979498</south-bound>
            </geographic-area>
         </geographic-areas>
         <time-frames>
            <time-frame cc-id="1135842">
               <time-frame-type>Range</time-frame-type>
               <start-date-time>2013-11-19</start-date-time>
               <end-date-time>2013-12-03</end-date-time>
            </time-frame>
         </time-frames>
      </extent>
   </extents>
   <spatial-information>
      <spatial-representation>
         <representations-used>
            <vector>Yes</vector>
         </representations-used>
      </spatial-representation>
   </spatial-information>
   <access-information>
      <security-class>Unclassified</security-class>
      <data-access-procedure>This data can be obtained on-line at the following URL:
https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=3675
;</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. These data depict the heights at the time of the survey and are only accurate for that time.</data-use-constraints>
   </access-information>
   <distribution-information>
      <distribution cc-id="743449">
         <download-url>https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=3675</download-url>
         <file-name>Customized Download</file-name>
         <description>Create custom data files by choosing data area, product type, map projection, file format, datum, etc.</description>
      </distribution>
      <distribution cc-id="743450">
         <download-url>https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/3675/index.html</download-url>
         <file-name>Bulk Download</file-name>
         <description>Simple download of data files.</description>
      </distribution>
   </distribution-information>
   <urls>
      <url cc-id="743454">
         <url>https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/3675/supplemental/wa2013_pslc_saddlemountain_m3675.kmz</url>
         <name>Browse Graphic</name>
         <url-type>Browse Graphic</url-type>
         <file-resource-format>kmz</file-resource-format>
         <description>This graphic shows the lidar coverage for the delivery of the 2013 Saddle Mountain lidar project.</description>
      </url>
      <url cc-id="743453">
         <url>https://coast.noaa.gov</url>
         <url-type>Online Resource</url-type>
      </url>
      <url cc-id="743452">
         <url>https://coast.noaa.gov/dataviewer</url>
         <url-type>Online Resource</url-type>
      </url>
   </urls>
   <activity-logs>
      <activity-log cc-id="693138">
         <activity-date-time>2016-05-23</activity-date-time>
         <description>Date that the source FGDC record was last modified.</description>
      </activity-log>
      <activity-log cc-id="693137">
         <activity-date-time>2017-11-14</activity-date-time>
         <description>Converted from FGDC Content Standards for Digital Geospatial Metadata (version FGDC-STD-001-1998) using 'fgdc_to_inport_xml.pl' script. Contact Tyler Christensen (NOS) for details.</description>
      </activity-log>
      <activity-log cc-id="718778">
         <activity-date-time>2018-02-08</activity-date-time>
         <description>Partial upload of Positional Accuracy fields only.</description>
      </activity-log>
      <activity-log cc-id="743451">
         <activity-date-time>2018-03-13</activity-date-time>
         <description>Partial upload to move data access links to Distribution Info.</description>
      </activity-log>
   </activity-logs>
   <data-quality>
      <accuracy>All discernible laser returns were processed for the output dataset. The discrepancy between native and delivered density will vary depending on terrain, land cover, and the prevalence of water bodies.</accuracy>
      <horizontal-positional-accuracy>When collecting RTK and PPK data, the rover records data while stationary for five seconds, then calculates the pseudorange position using at least three one-second epochs. Relative errors for the position must be less than 1.5 cm horizontal and 2.0 cm vertical in order to be accepted.; Quantitative Value: 0.015 meters, Test that produced the value: GSP were collected in areas where good satellite visibility was achieved on paved roads and other hard surfaces such as gravel or packed dirt roads</horizontal-positional-accuracy>
      <vertical-positional-accuracy>The mean and standard deviation (sigma) of divergence of the ground surface model from ground survey point coordinates are also considered during accuracy assessment. These statistics assume the error for x, y and z is normally distributed, and therefore the skew and kurtosis of distributions are also considered when evaluating error statistics. For the Cedar Watershed LiDAR survey, 2,345 ground survey points were collected in total resulting in an average accuracy of -0.012 feet (-0.004 meters).; Quantitative Value: 0.05 meters, Test that produced the value: FVA (1.96 * RMSE) of 0.165 ft (~5.0 cm), RMSE calculated to be 0.085 ft (~2.6 cm)</vertical-positional-accuracy>
      <completeness-report>LiDAR data has been collected and processed for all areas within the project study area.</completeness-report>
      <conceptual-consistency>All areas were surveyed with an opposing flight line side-lap of more than 50 percent (more than 100 percent overlap) in order to reduce laser shadowing and increase surface laser painting. To accurately solve for laser point position (geographic coordinates x, y and z), the positional coordinates of the airborne sensor and the attitude of the aircraft were recorded continuously throughout the LiDAR data collection mission. Position of the aircraft was measured twice per second (2 Hz) by an onboard differential GPS unit, and aircraft attitude was measured 200 times per second (200 Hz) as pitch, roll and yaw (heading) from an onboard inertial measurement unit (IMU). To allow for post-processing correction and calibration, aircraft and sensor position and attitude data are indexed by GPS time.</conceptual-consistency>
   </data-quality>
   <lineage>
      <lineage-process-steps>
         <lineage-process-step cc-id="1135838">
            <sequence-number>1</sequence-number>
            <description>The LiDAR survey was accomplished with a Leica ALS60 system mounted in a Cessna Caravan, and a Leica ALS70 system mounted in a Partenavia aircraft, yielding an average pulse density of more than 8 pulses per sq. meter over the Saddle Mountain terrain. It is not uncommon for some types of surfaces (e.g. dense vegetation or water) to return fewer pulses to the LiDAR sensor than the laser originally emitted. The discrepancy between native and delivered density will vary depending on terrain, land cover, and the prevalence of water bodies. The LiDAR data arrived to the office then QSI processing staff initiates a suite of automated and manual techniques to process the data into the requested deliverables. Processing tasks include GPS control computations, smoothed best estimate trajectory (SBET) calculations, kinematic corrections, calculation of laser point position, sensor and data calibration for optimal relative and absolute accuracy, and LiDAR point classification.</description>
            <process-date-time>2014-03-01T00:00:00</process-date-time>
         </lineage-process-step>
         <lineage-process-step cc-id="1135839">
            <sequence-number>2</sequence-number>
            <description>1. Resolve kinematic corrections for aircraft position data using kinematic aircraft GPS and static ground GPS data. 
2. Develop a smoothed best estimate of trajectory (SBET) file that blends post-processed aircraft position with sensor head position and attitude recorded throughout the survey. 
3. Calculate laser point position by associating SBET position to each laser point return time, scan angle, intensity, etc. Create raw laser point cloud data for the entire survey in *.las (ASPRS v. 1.2) format. Convert data to orthometric elevations by applying a geoid03 correction. 
4. Import raw laser points into manageable blocks (less than 500 MB) to perform manual relative accuracy calibration and filter erroneous points. Classify ground points for individual flight lines 
5. Using ground classified points per each flight line, test the relative accuracy. Perform automated line-to-line calibrations for system attitude parameters (pitch, roll, heading), mirror flex (scale) and GPS/IMU drift. Calculate calibrations on ground classified points from paired flight lines and apply results to all points in a flight line. Use every flight line for relative accuracy calibration. 6. Classify resulting data to ground and other client designated ASPRS classifications. Assess statistical absolute accuracy via direct comparisons of ground classified points to ground control survey data.
7. Generate bare earth models as triangulated surfaces. Generate highest hit models as a surface expression of all classified points.</description>
            <process-date-time>2014-03-01T00:00:00</process-date-time>
         </lineage-process-step>
         <lineage-process-step cc-id="1135840">
            <sequence-number>3</sequence-number>
            <description>The NOAA Office for Coastal Management (OCM) downloaded topographic files in .txt format from PSLC's FTP site. The files contained lidar elevation, intensity, return number, class, scan angle and GPS time measurements. The data were received in Washington State Plane North Zone 4601, NAD83 coordinates and were vertically referenced to NAVD88 using the Geoid03 model. The vertical units of the data were
feet. OCM performed the following processing for data storage and Digital Coast provisioning purposes:
1. The las files were converted from orthometric (NAVD88) heights to ellipsoidal heights using Geoid03, and from feet to meters.
2. The las files were converted from a Projected Coordinate System (WA SP South) to a Geographic Coordinate system (NAD83), converting from feet to decimal degrees.</description>
            <process-date-time>2014-08-20T00:00:00</process-date-time>
         </lineage-process-step>
      </lineage-process-steps>
   </lineage>
   <catalog-details>
      <guid>gov.noaa.nmfs.inport:50173</guid>
      <metadata-record-created-by pers-id="19064">Anne Ball</metadata-record-created-by>
      <metadata-record-created>2017-11-15T15:24:42</metadata-record-created>
      <metadata-record-last-modified-by pers-id="0">SysAdmin InPortAdmin</metadata-record-last-modified-by>
      <metadata-record-last-modified>2022-08-09T17:11:38</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>
      <best-available-metadata>No</best-available-metadata>
      <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>
