Slide Menu
Search Help Show/Hide Menu
Short Citation:
OCM Partners, 2024: 2012 Puget Sound LiDAR Consortium (PSLC) Topographic LiDAR: Quinault River Watershed, Washington (Delivery 1),

Item Identification

Title: 2012 Puget Sound LiDAR Consortium (PSLC) Topographic LiDAR: Quinault River Watershed, Washington (Delivery 1)
Short Name: wa2012_pslc_quinaultriver_m2508_metadata
Status: Completed
Publication Date: 2013-06-13

Watershed Sciences, Inc. (WSI) collected Light Detection and Ranging (LiDAR) data on the Quinault watershed survey area for the Puget Sound LiDAR Consortium. This data set covers approximately 181 square miles. Due to spring snow on the ground WSI was unable to acquire data for the complete survey during the initial flights in April and will return to finish acquisition at a later date. Delivery 1 of the survey area was collected on March 24th and 25th and April 8th and 9th and 22nd.

The LiDAR survey utilized both a Leica ALS60 and a Leica ALS50-II sensor in a Cessna Caravan 208B.All areas were surveyed with an opposing flight line side-lap of =60% (=100% overlap) to reduce laser shadowing and increase

surface laser painting. The Leica laser systems allow up to four range measurements (returns) per pulse, and all discernible laser returns were processed for the output dataset.

This LiDAR survey achieved a nominal point spacing of 9.23 points per square meter.


The LAS files can be used to create DEMs and also to extract topographic data in software that does not support raster data. Other surface features can also be extracted with custom applications. LiDAR data has a wide range of

uses such as earthquake hazard studies, hydrologic modeling, forestry, coastal engineering, roadway and pipeline engineering, flood plain mapping, wetland studies, geologic studies and a variety of analytical and cartographic




Supplemental Information:

A footprint of this data set may be viewed in Google Earth at:

A LiDAR Report from the vendor for this data set may be viewed here:


Theme Keywords

Thesaurus Keyword
ISO 19115 Topic Category
None LAZ

Physical Location

Organization: Office for Coastal Management
City: Charleston
State/Province: SC

Data Set Information

Data Set Scope Code: Data Set
Maintenance Frequency: As Needed
Data Presentation Form: las
Entity Attribute Overview:

LiDAR points in LAZ format

Entity Attribute Detail Citation:


Distribution Liability:

Any conclusions drawn from the analysis of this information are not the responsibility

of Watershed Sciences Inc., PSLC, NOAA, the Office for Coastal Management or its partners.

Data Set Credit: Please credit the Puget Sound LiDAR Consortium (PSLC). 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.

Support Roles

Data Steward

CC ID: 692945
Date Effective From: 2013-06-13
Date Effective To:
Contact (Organization): NOAA Office for Coastal Management (NOAA/OCM)
Address: 2234 South Hobson Ave
Charleston, SC 29405-2413
Email Address:
Phone: (843) 740-1202


CC ID: 692947
Date Effective From: 2013-06-13
Date Effective To:
Contact (Organization): NOAA Office for Coastal Management (NOAA/OCM)
Address: 2234 South Hobson Ave
Charleston, SC 29405-2413
Email Address:
Phone: (843) 740-1202

Metadata Contact

CC ID: 692948
Date Effective From: 2013-06-13
Date Effective To:
Contact (Organization): NOAA Office for Coastal Management (NOAA/OCM)
Address: 2234 South Hobson Ave
Charleston, SC 29405-2413
Email Address:
Phone: (843) 740-1202

Point of Contact

CC ID: 692946
Date Effective From: 2013-06-13
Date Effective To:
Contact (Organization): NOAA Office for Coastal Management (NOAA/OCM)
Address: 2234 South Hobson Ave
Charleston, SC 29405-2413
Email Address:
Phone: (843) 740-1202


Currentness Reference: Ground Condition

Extent Group 1

Extent Group 1 / Geographic Area 1

CC ID: 1134051
W° Bound: -124.498098
E° Bound: -124.117126
N° Bound: 47.353326
S° Bound: 47.244463

Extent Group 1 / Time Frame 1

CC ID: 1134050
Time Frame Type: Range
Start: 2012-04-14
End: 2012-04-21

Spatial Information

Spatial Representation

Representations Used

Vector: Yes

Access Information

Security Class: Unclassified
Data Access Procedure:

This data can be obtained on-line at the following URL:


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.

Distribution Information

Distribution 1

CC ID: 743420
Download URL:
File Name: Customized Download

Create custom data files by choosing data area, product type, map projection, file format, datum, etc.

Distribution 2

CC ID: 743421
Download URL:
File Name: Bulk Download

Simple download of data files.



CC ID: 743423
URL Type:
Online Resource


CC ID: 743424
URL Type:
Online Resource


CC ID: 743425
Name: Browse Graphic
URL Type:
Browse Graphic
File Resource Format: kmz

This graphic shows the LiDAR coverage for a section of Jefferson County, Washington.

Activity Log

Activity Log 1

CC ID: 692964
Activity Date/Time: 2017-04-04

Date that the source FGDC record was last modified.

Activity Log 2

CC ID: 692963
Activity Date/Time: 2017-11-14

Converted from FGDC Content Standards for Digital Geospatial Metadata (version FGDC-STD-001-1998) using '' script. Contact Tyler Christensen (NOS) for details.

Activity Log 3

CC ID: 718773
Activity Date/Time: 2018-02-08

Partial upload of Positional Accuracy fields only.

Activity Log 4

CC ID: 743422
Activity Date/Time: 2018-03-13

Partial upload to move data access links to Distribution Info.

Data Quality


Elevations are recorded in floating-point meters and the vertical datum is ellipsoidal (GEOID03). There are no other attribute tables.

Horizontal Positional Accuracy:

Not applicable for pure elevation data: every XY error has an associated Z error.

Vertical Positional Accuracy:

Relative accuracy refers to the internal consistency of the data set - the ability to place a laser point in the same location over multiple flight lines, GPS conditions, and aircraft attitudes. Affected by system attitude

offsets, scale, and GPS/IMU drift, internal consistency is measured as the divergence between points from different flight lines within an overlapping area. Several Relative Accuracy Calibration Methods were used including

Manual System Calibration, Automated Attitude Calibration, and Automated Z Calibration. A detailed explanation of each is provided in the LiDAR Report listed above.

Absolute accuracy is largely a function of laser noise and relative accuracy. To minimize these contributions to absolute error, a number of noise filtering and calibration procedures were performed prior to

evaluating absolute accuracy. The LiDAR quality assurance process uses the data from the real-time kinematic (RTK) ground survey conducted in the AOI. For the Quinault River watershed survey area a total of 1,212 GPS measurements

were collected on hard surfaces distributed among multiple flight swaths. To assess absolute accuracy the location coordinates of these known RTK ground points were compared to those calculated for the closest ground-classified

laser points. A detailed explanation of steps takes to increase Absolute Accuracy are provided in the LiDAR Report listed above.

The root mean square error (RMSE) for vertical accuracy is provided. These statistics assume the error distributions for x, y, and z are normally distributed, thus we also consider the skew and kurtosis of distributions when

evaluating error statistics. Statements of statistical accuracy apply to fixed terrestrial surfaces only and may not be applied to areas of dense vegetation or steep terrain.

; Quantitative Value: 0.026 meters, Test that produced the value: Root mean square Z error in open, near-horizontal areas, as specified by contract. Units in meters. Accuracy may be significantly less in steep areas and under heavy forest canopy.

Completeness Report:

Elevation data has been collected for all areas inside project boundaries. The data set was flown with a 60% sidelap between flightlines and a 100 meter buffer to ensure all areas are properly sampled.

Conceptual Consistency:

Puget Sound LiDAR Consortium evaluates logical consistency of high-resolution liDAR elevation data with three tests: examination of file names, file formats, and mean and extreme values within each file; internal consistency of

measured Z values in areas where survey swaths overlap; and visual inspection of shaded-relief images calculated from bare-earth models.

File names, formats, and values: All file naming convention and file formats are checked for consistency.

Visual inspection of bare earth surfaces were examined to find any obvious data errors such as blunders, border artifacts, gaps between data quads, no-data gaps between flight lines, hillscarps, land shifting due to GPS time errors, etc.


Process Steps

Process Step 1

CC ID: 1134047

1. Resolved kinematic corrections for aircraft position data using kinematic aircraft GPS and static ground GPS data.

Software: Waypoint GPS v.8.10, Trimble Business Center 2.6

2. Developed a smoothed best estimate of trajectory (SBET) file that blends post-processed aircraft position with attitude data. Sensor head position and attitude were calculated throughout the survey. The SBET data were used

extensively for laser point processing.

Software: IPAS TC v.3.1

3. Calculated laser point position by associating SBET position to each laser point return time, scan angle, intensity, etc. Created raw laser point cloud data for the entire survey in *.las (ASPRS v. 1.2) format. Data were

then converted to orthometric elevations (NAVD88) by applying a Geoid03 correction.

Software: ALS Post Processing Software v.2.74, Corpscon 6

4. Imported raw laser points into manageable blocks (less than 500 MB) to perform manual relative accuracy calibration and filter for pits/birds. Ground points were then classified for individual flight lines (to be used for

relative accuracy testing and calibration).

Software: TerraScan v.12.004

5. Using ground classified points per each flight line, the relative accuracy was tested. Automated line-to-line calibrations were then performed for system attitude parameters (pitch, roll, heading), mirror flex (scale) and

GPS/IMU drift. Calibrations were performed on ground classified points from paired flight lines. Every flight line was used for relative accuracy calibration.

Software: TerraMatch v.12.001

6. Position and attitude data were imported. Resulting data were classified as ground and non-ground points. Statistical absolute accuracy was assessed via direct comparisons of ground classified points to ground RTK survey data.

Software: TerraScan v.12.004, TerraModeler v.12.002

7. Bare Earth models were created as a triangulated surface and exported as ArcInfo ASCII grids at a 3-foot pixel resolution. Highest Hit models were created for any class at 3-foot grid spacing and exported as ArcInfo ASCII grids.

Software: TerraScan v.12.004, ArcMap v.10.0, TerraModeler v.12.002

8. Intensity images were created as Geo TIFFs and mosaicked to the final delineation.

Software: TerraScan v.12.004, ArcMap v.10.0, TerraModeler v.12.002

Process Date/Time: 2012-01-01 00:00:00

Process Step 2

CC ID: 1134048

The NOAA Office for Coastal Management (OCM) downloaded topographic files in .LAZ format from PSLC's website. The files contained LiDAR elevation and intensity measurements. The data were received in

Washington State Plane South Zone 4602, 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 topographic las files were converted from orthometric (NAVD88) heights to ellipsoidal heights using Geoid03.

2. The topographic las files were converted from a Projected Coordinate System (WA SP South) to a Geographic Coordinate system (NAD83).

3. The topographic las files' vertical units were converted from feet to meters.

4. The topographic las files' horizontal units were converted from feet to decimal degrees.

Process Date/Time: 2013-06-01 00:00:00

Catalog Details

Catalog Item ID: 50168
GUID: gov.noaa.nmfs.inport:50168
Metadata Record Created By: Anne Ball
Metadata Record Created: 2017-11-15 15:24+0000
Metadata Record Last Modified By: SysAdmin InPortAdmin
Metadata Record Last Modified: 2022-08-09 17:11+0000
Metadata Record Published: 2022-03-16
Owner Org: OCMP
Metadata Publication Status: Published Externally
Do Not Publish?: N
Metadata Last Review Date: 2022-03-16
Metadata Review Frequency: 1 Year
Metadata Next Review Date: 2023-03-16