2011 Puget Sound LiDAR Consortium (PSLC) Topographic LiDAR: Rattlesnake
Data Set (DS) | OCM Partners (OCMP)GUID: gov.noaa.nmfs.inport:50164 | Updated: August 9, 2022 | Published / External
Item Identification
Title: | 2011 Puget Sound LiDAR Consortium (PSLC) Topographic LiDAR: Rattlesnake |
---|---|
Short Name: | wa2011_pslc_rattlesnake_m2587_metadata |
Status: | Completed |
Publication Date: | 2013-11-23 |
Abstract: |
Watershed Sciences, Inc. (WSI) collected Light Detection and Ranging (LiDAR) data on six days between September 15th and November 5th, and from November 6th - 13th, 2010 for the Puget Sound LiDAR Consortium. This report documents the data acquisition, processing methods, accuracy assessment, and deliverables for the Rattlesnake area of interest in Benton County, WA. The requested areas were expanded to include a 100m buffer to ensure complete coverage and adequate point densities around survey area boundaries. The total acreage of the Rattlesnake AOI is 184,359 acres. The average first-return density of the delivered dataset is 8.3 points per square meter for the Rattlesnake study area. The initial datasets, acquired to be =8 points per square meter, were filtered as described previously to remove spurious or inaccurate points. Additionally, some types of surfaces (i.e., dense vegetation, breaks in terrain, water, steep slopes) may return fewer pulses (delivered density) than the laser originally emitted (native density). |
Purpose: |
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 projects. |
Notes: |
10808 |
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/2587/supplemental/wa2011_pslc_rattlesnake.kmz A report explaining collection and quality assurance is available at: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/2587/supplemental/wa2011_pslc_rattlesnake.pdf 2011 Kittitas is not directly associated to the data represented in the Rattlesnake area, though the information in the Kittitas report may be useful to an advanced user for comparative analysis, it is available at: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/2599/supplemental/wa2011_pslc_kittitas.pdf |
Keywords
Theme Keywords
Thesaurus | Keyword |
---|---|
ISO 19115 Topic Category |
elevation
|
UNCONTROLLED | |
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 (ASPRS Classes 1,2) |
Entity Attribute Detail Citation: |
none |
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. |
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
Date Effective From: | 2013-11-23 |
---|---|
Date Effective To: | |
Contact (Organization): | NOAA Office for Coastal Management (NOAA/OCM) |
Address: |
2234 South Hobson Ave Charleston, SC 29405-2413 |
Email Address: | coastal.info@noaa.gov |
Phone: | (843) 740-1202 |
URL: | https://coast.noaa.gov |
Distributor
Date Effective From: | 2013-11-23 |
---|---|
Date Effective To: | |
Contact (Organization): | NOAA Office for Coastal Management (NOAA/OCM) |
Address: |
2234 South Hobson Ave Charleston, SC 29405-2413 |
Email Address: | coastal.info@noaa.gov |
Phone: | (843) 740-1202 |
URL: | https://coast.noaa.gov |
Metadata Contact
Date Effective From: | 2013-11-23 |
---|---|
Date Effective To: | |
Contact (Organization): | NOAA Office for Coastal Management (NOAA/OCM) |
Address: |
2234 South Hobson Ave Charleston, SC 29405-2413 |
Email Address: | coastal.info@noaa.gov |
Phone: | (843) 740-1202 |
URL: | https://coast.noaa.gov |
Point of Contact
Date Effective From: | 2013-11-23 |
---|---|
Date Effective To: | |
Contact (Organization): | NOAA Office for Coastal Management (NOAA/OCM) |
Address: |
2234 South Hobson Ave Charleston, SC 29405-2413 |
Email Address: | coastal.info@noaa.gov |
Phone: | (843) 740-1202 |
URL: | https://coast.noaa.gov |
Extents
Currentness Reference: | Ground Condition |
---|
Extent Group 1
Extent Group 1 / Geographic Area 1
W° Bound: | -119.8917772 | |
---|---|---|
E° Bound: | -119.4011374 | |
N° Bound: | 46.64934815 | |
S° Bound: | 46.32284593 |
Extent Group 1 / Time Frame 1
Time Frame Type: | Discrete |
---|---|
Start: | 2010-09-15 |
Extent Group 1 / Time Frame 2
Time Frame Type: | Discrete |
---|---|
Start: | 2010-11-05 |
Extent Group 1 / Time Frame 3
Time Frame Type: | Discrete |
---|---|
Start: | 2010-11-06 |
Extent Group 1 / Time Frame 4
Time Frame Type: | Discrete |
---|---|
Start: | 2010-11-07 |
Extent Group 1 / Time Frame 5
Time Frame Type: | Discrete |
---|---|
Start: | 2010-11-08 |
Extent Group 1 / Time Frame 6
Time Frame Type: | Discrete |
---|---|
Start: | 2010-11-09 |
Extent Group 1 / Time Frame 7
Time Frame Type: | Discrete |
---|---|
Start: | 2010-11-10 |
Extent Group 1 / Time Frame 8
Time Frame Type: | Discrete |
---|---|
Start: | 2010-11-11 |
Extent Group 1 / Time Frame 9
Time Frame Type: | Discrete |
---|---|
Start: | 2010-11-12 |
Extent Group 1 / Time Frame 10
Time Frame Type: | Discrete |
---|---|
Start: | 2010-11-13 |
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: https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=2587 ; |
Data Access Constraints: |
None |
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
Download URL: | https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=2587 |
---|---|
Distributor: | |
File Name: | Customized Download |
Description: |
Create custom data files by choosing data area, product type, map projection, file format, datum, etc. |
Distribution 2
Download URL: | https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/2587/index.html |
---|---|
Distributor: | |
File Name: | Bulk Download |
Description: |
Simple download of data files. |
URLs
URL 1
URL: | https://coast.noaa.gov/dataviewer |
---|---|
URL Type: |
Online Resource
|
URL 2
URL: | https://coast.noaa.gov |
---|---|
URL Type: |
Online Resource
|
URL 3
URL: | https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/2587/supplemental/wa2011_pslc_rattlesnake.kmz |
---|---|
Name: | Browse Graphic |
URL Type: |
Browse Graphic
|
File Resource Format: | kmz |
Description: |
This graphic shows the lidar coverage for the 2011 Rattlesnake area of Washington, collected in 2010. |
Activity Log
Activity Log 1
Activity Date/Time: | 2016-05-23 |
---|---|
Description: |
Date that the source FGDC record was last modified. |
Activity Log 2
Activity Date/Time: | 2017-11-14 |
---|---|
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. |
Activity Log 3
Activity Date/Time: | 2018-02-08 |
---|---|
Description: |
Partial upload of Positional Accuracy fields only. |
Activity Log 4
Activity Date/Time: | 2018-03-13 |
---|---|
Description: |
Partial upload to move data access links to Distribution Info. |
Data Quality
Accuracy: |
Elevations are recorded in floating-point meters and the vertical datum is ellipsoidal (GEOID03). |
---|---|
Horizontal Positional Accuracy: |
Horizontal positional accuracy for LiDAR is dependent upon the quality of the GPS/INS solution, sensor calibration and ground conditions at the time of data capture. The standard system results for horizontal accuracy are less than 1 meter. ; Quantitative Value: 1.0 meters, Test that produced the value: Lidar horizontal accuracy was not reported. |
Vertical Positional Accuracy: |
To minimize the contributions of laser noise and relative accuracy 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 Rattlesnake study a total 2064 RTK 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. The vertical accuracy of the LiDAR data is described as the mean and standard deviation (sigma ~ s) of divergence of LiDAR point coordinates from RTK ground survey point coordinates. To provide a sense of the model predictive power of the dataset, the root mean square error (RMSE) for vertical accuracy is also 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. ; Quantitative Value: 0.036 meters, Test that produced the value: Absolute vertical accuracy was calculated to 3.6 cm. |
Completeness Report: |
LiDAR data has been collected and processed for all areas within the project study area. |
Conceptual Consistency: |
LiDAR flight lines have been examined to ensure that there was at least 50% sidelap, there are no gaps between flightlines, and overlapping flightlines have consistent elevation values. Shaded relief images have been visually inspected for data errors such as pits, border artifacts, gaps, and shifting. |
Lineage
Process Steps
Process Step 1
Description: |
1. Resolved kinematic corrections for aircraft position data using kinematic aircraft GPS and static ground GPS data. Software used - Waypoint GPS v.8.10, Trimble Geomatics Office v.1.62 2. Developed a smoothed best estimate of trajectory (SBET) file that blends postprocessed 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 used - IPAS v.1.35 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. Software used - ALS Post Processing Software v.2.70 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 used - TerraScan v.10.009 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 used - TerraMatch v.10.006 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. Data were then converted to orthometric elevations (NAVD88) by applying a Geoid03 correction. Software used - TerraScan v.10.009, TerraModeler v.10.004 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 used - TerraScan v.10.009, ArcMap v. 9.3.1, TerraModeler v.10.004 Report compiled 20110207 |
---|---|
Process Date/Time: | 2011-02-07 00:00:00 |
Process Step 2
Description: |
The NOAA Office for Coastal Management (OCM) downloaded topographic files in text format from PSLC's website. The files contained lidar easting, northing, elevation, intensity, return number, class, scan angle and GPS time 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 All-Return ASCII files were converted from txt format to las format using LASTools' txt2las retaining the classified points, 1 (unclassified) and 2 (ground). 2. The las files were converted from orthometric (NAVD88) heights to ellipsoidal heights using Geoid03. 3. The las files' vertical units were converted from feet to meters, removing bad elevations. 4. The las files were converted from a Projected Coordinate System (WA SP South) to a Geographic Coordinate system (NAD83) 5. The las files' horizontal units were converted from feet to decimal degrees and converted to laz format. |
---|---|
Process Date/Time: | 2013-11-23 00:00:00 |
Catalog Details
Catalog Item ID: | 50164 |
---|---|
GUID: | gov.noaa.nmfs.inport:50164 |
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 |