Slide Menu
Search Help Show/Hide Menu
Short Citation:
OCM Partners, 2023: 2014 PSLC Lidar: City of Redmond,

Item Identification

Title: 2014 PSLC Lidar: City of Redmond
Short Name: wa2014_pslc_redmond_m4735_metadata
Status: Completed
Publication Date: 2014-12-08

In February 2014, Quantum Spatial (QSI) was contracted by the Puget Sound LiDAR Consortium (PSLC) to collect Light Detection and Ranging (LiDAR) data for the City of Redmond site in western Washington. Data were collected to aid PSLC in assessing the topographic and geophysical properties of the study area.

The accompany report discusses the delivered LiDAR data and documents contract specifications, data acquisition procedures, processing methods, and analysis of the final dataset including LiDAR accuracy and density.


This project covers the City of Redmond located in King County. The data was acquired in April 2014.



Supplemental Information:

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

A project report for this data set may be accessed 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.1 format

Entity Attribute Detail Citation:


Distribution Liability:

Any conclusions drawn from the analysis of this information are not the responsibility of Watershed Sciences, PSLC, 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 inlocal, state, and tribal government.

Support Roles

Data Steward

CC ID: 693349
Date Effective From: 2014-12-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: 693351
Date Effective From: 2014-12-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: 693352
Date Effective From: 2014-12-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: 693350
Date Effective From: 2014-12-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: 1136291
W° Bound: -85.215673
E° Bound: -83.90863
N° Bound: 34.576794
S° Bound: 32.854996

Extent Group 1 / Time Frame 1

CC ID: 1136290
Time Frame Type: Range
Start: 2014-04-07
End: 2014-04-09

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: 743484
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: 743485
Download URL:
File Name: Bulk Download

Simple download of data files.



CC ID: 743487
URL Type:
Online Resource


CC ID: 743488
URL Type:
Online Resource


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

This graphic shows the lidar coverage for the city of Redmond (King County) in Washington.

Activity Log

Activity Log 1

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

Date that the source FGDC record was last modified.

Activity Log 2

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

Partial upload of Positional Accuracy fields only.

Activity Log 4

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

Partial upload to move data access links to Distribution Info.

Data Quality


The accuracy of the LiDAR data collection can be described in terms of absolute accuracy (the consistency of the data with external data sources) and relative accuracy (the consistency of the dataset with itself). See Appendix A in the report for further information on sources of error and operational measures used to improve relative 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.02 meters, Test that produced the value: Value reported as RMSE in meters, not tested

Vertical Positional Accuracy:

Lidar accuracies were tested for vertical accuracy. Watershed Sciences collected 222 ground control points for use in verifying the vertical accuracy of the classified LiDAR data in King County, surrounding Redmond.; Quantitative Value: 0.019 meters, Test that produced the value: Value reported as RMSE in meters. FVA (RMSE x 1.96) reported as 0.037 m in open terrain

Completeness Report:


Conceptual Consistency:

Absolute accuracy was assessed using Fundamental Vertical Accuracy (FVA) reporting designed to meet guidelines presented in the FGDC National Standard for Spatial Data Accuracy. FVA compares known RTK and PPK ground control point data collected on open, bare earth surfaces with level slope (+/- 20 degrees) to the triangulated ground surface generated by the LiDAR points. FVA is a measure of the accuracy of LiDAR point data in open areas where the LiDAR system has a high probability of measuring the ground surface and is evaluated at the 95 percent confidence interval (1.96 x RMSE).

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 City of Redmond survey, 224 ground survey points were collected in total resulting in an average accuracy of 0.004 feet (0.001 meters) (Figure 7 in the lidar report).


Process Steps

Process Step 1

CC ID: 1136287

1. Resolve kinematic corrections for aircraft position data using kinematic aircraft GPS and static ground GPS data. 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.

Software: IPAS TC v.3.1 , Waypoint Inertial Explorer v.8.5

2. 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.

Software: ALS Post Processing Software v.2.75

3. 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.

Software: TerraScan v.14

4. 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.

Software: TerraMatch v.14

5. Classify resulting data to ground and other client designated ASPRS classifications (Table 7). Assess statistical absolute accuracy via direct comparisons of ground classified points to ground control survey data.

Software: TerraScan v.14, TerraModeler v.14

6. Generate bare earth models as triangulated surfaces. Generate highest hit models as a surface expression of all classified points. Export all surface models as ESRI GRIDs at a 3.0 foot pixel resolution.

Software: TerraScan v.14, TerraModeler v.14, ArcMap v. 10.1

7. Export intensity images as GeoTIFFs at a 1.5 foot pixel resolution.

Software: TerraScan v.14, TerraModeler v.14, ArcMap v. 10.1

Process Date/Time: 2014-05-01 00:00:00

Process Step 2

CC ID: 1136288

The NOAA Office for Coastal Management (OCM) received topographic file in LAZ format from the Puget Sound Lidar Consortium. The files contained lidar

elevation measurements and other acquisition/post processing attributes. The data were received in Washington State Plane North Zone 4601, NAD83 coordinates

and were vertically referenced to NAVD88 using the Geoid03 model, 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.

2. The LAS files were converted from a Projected Coordinate System (WA SP North) to a Geographic Coordinate system (GCS).

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: 2014-12-08 00:00:00

Catalog Details

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