Slide Menu
Search Help Show/Hide Menu
Short Citation:
OCM Partners, 2023: 2005 Puget Sound LiDAR Consortium (PSLC) Topographic LiDAR: Lower Columbia River,

Item Identification

Title: 2005 Puget Sound LiDAR Consortium (PSLC) Topographic LiDAR: Lower Columbia River
Short Name: wa2005_pslc_lowercolariver_m2535_metadata
Status: Completed
Publication Date: 2013-08

Terrapoint, on behalf of multiple agencies, collected topographic lidar of the Lower Columbia River area. Field data collection took place between the dates of January 10th and February 20th, 2005. The control network

and checkpoint surveys were performed from January 4th to February 12th, 2005. The project area covers approximately 890 square miles along the Columbia River, from the Bonneville Dam to the Pacific Ocean.

A total of 431 flightlines were required to cover the project area flightlines.

Terrapoint used a 40 kHz Airborne Laser Terrain Mapping System ALTMS sensor attached to a Navajo Twin-engin aircraft (C-FVZM). The mission was flown at 3500 feet above ground level at an average speed of 140 knots. The system

consists of a 36 degree full scan angle laser, a Trimble 4700 GPS receiver and a Honeywell H764 IMU unit. The nominal flightline spacing was 1070 feet with 30 to 50% sidelap.

The surveyed and processed data was received divided by funding agency. The agency responsible for funding each tile is represented as a number (0:COE, 1:DNR, 2:DOGAMI, 3:DOI) in the "User Data" field of each LAS file.


The purpose of this project was to provide a high quality DEM of the site for multiple participating agencies.



Supplemental Information:

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

A project report for this project from the vendor may be obtained at:


Theme Keywords

Thesaurus Keyword
ISO 19115 Topic Category

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 LAS 1.2 format (ASPRS Classes 1,2,6,7)

Entity Attribute Detail Citation:


Distribution Liability:

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

of Terrapoint, PSLC, NASA, DOI, COE, DOGAMI, DNR, NOAA, the Office for Coastal Management or its partners.

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.

Support Roles

Data Steward

CC ID: 692231
Date Effective From: 2013-08
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: 692233
Date Effective From: 2013-08
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: 692234
Date Effective From: 2013-08
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: 692232
Date Effective From: 2013-08
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: 1134366
W° Bound: -124.094973
E° Bound: -121.92062
N° Bound: 46.474753
S° Bound: 45.401999

Extent Group 1 / Time Frame 1

CC ID: 1134365
Time Frame Type: Range
Start: 2005-01-10
End: 2005-02-20

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: 743294
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: 743295
Download URL:
File Name: Bulk Download

Simple download of data files.



CC ID: 743297
URL Type:
Online Resource


CC ID: 743298
URL Type:
Online Resource


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

This graphic shows the lidar coverage for the Lower Columbia River (from the Bonneville Dam to the Pacific Ocean) along the Washington/Oregon border.

Activity Log

Activity Log 1

CC ID: 692258
Activity Date/Time: 2016-05-23

Date that the source FGDC record was last modified.

Activity Log 2

CC ID: 692257
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: 718752
Activity Date/Time: 2018-02-08

Partial upload of Positional Accuracy fields only.

Activity Log 4

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

Partial upload to move data access links to Distribution Info.

Data Quality


See Vertical Accuracy Report below.

Horizontal Positional Accuracy:

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

Vertical Positional Accuracy:

The GPS and inertial data were processed in tandem to achieve the best positional result. Once the position and attitude of the aircraft were known at each epoch (1-second intervals), then

these data were integrated with the laser ranges to provide a position for each data point on the ground. The data were then processed using the proprietary laser processing software suite to produce

coordinates. Each flight involved setting up two base stations to collect data. Utilizing two base stations ensures GPS data collection in the event that the main base station fails. For all flights

the GPS data were of high quality. This minimized the absolute error for the aircraft position.

To verify that the accuracy criteria were being achieved, 10,092 kinematic checkpoints were compared with a triangulated surface generated from the bald earth LiDAR points.

; Quantitative Value: 0.25 meters, Test that produced the value:

AccuracyZ at the 95% confidence level (2 sigma) for soft/vegetated surface in flat or rolling terrain. 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.

Conceptual Consistency:

Once the data setup has taken place the manual quality control of the surface occurs. This process consists of visually examining the LiDAR points within Terrascan and correcting errors that

occurred during the automated process. These corrections include verifying that all non ground elements, such as vegetation and buildings are removed from the ground model and that all small

terrain undulations such as road beds, dykes, rock cuts and hill tops are present within the model. This process is done with the help of hillshades, contours, profiles and crosssections.

To correct misclassifications, a full suite of Terrascan and custom inhouse data tools are used.


Process Steps

Process Step 1

CC ID: 1134362

The following software was used to reduce the GPS kinematic data, compute the 3-D laser points, classify and edit laser points, produce shaded relief images and transform the ellipsoidal heights to Orthometric:

ArcView, Flykin, Microstation, TerraScan, TerraModeler, TerraModel, and Terrapoint Proprietary LiDAR processing software

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

Process Step 2

CC ID: 1134363

The NOAA Office for Coastal Management (OCM) received topographic files in ASCII .TXT format. The files contained lidar elevation measurements, GPS time measurements (week/second), number of returns, return number, scan angle,

intensity, and classification. 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 ASCII .TXT files were run through a parser to convert GPS Week/Second Time to Adjusted Standard GPS Time and change the format of the Classification field.

2. The parsed ASCII .TXT files were converted to LAS version 1.2 using LAStools' txt2las tool.

3. The User Data field was set depending on agency which funded the tile. The User Data values are: 0 (COE), 1 (DNR), 2 (DOGAMI), 3 (DOI).

4. The topographic las files were converted from orthometric (NAVD88) heights to ellipsoidal heights using Geoid03.

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

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

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

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

Catalog Details

Catalog Item ID: 50147
GUID: gov.noaa.nmfs.inport:50147
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