50158
2009 Puget Sound LiDAR Consortium (PSLC) Topographic LiDAR: San Juan County and Lummi Island, Washington
wa2009_pslc_sanjuan_m1464_metadata
Data Set
Published / External
49401
Lidar - partner (no harvest)
Project
Completed
2013-02
The dataset encompasses portions of San Juan and Whatcom counties in northwest Washington. The surveyed area is approximately 222 square miles. The LAS V1.1 files are classified into Class 1 (Unclassified) and Class 2 (Bare Earth)
water points are included in both classes. The LAS files are all-return and also include intensity measurements. 50% overlap was used between flightines, resulting in each area being surveyed twice. The nominal point spacing of
the data is 0.408 meters (6 pt/sq. meter).
Watershed Sciences, Inc. collected the LiDAR and created this data set for the Puget Sound LiDAR Consortium
Original contact information:
Contact Name: Diana Martinez
Contact Org: Puget Sound LiDAR Consortium
Phone: 206-971-3052
Provide high resolution terrain elevation and land cover elevation data.
10802
A footprint of this data set may be viewed in Google Earth at:
https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/1464/supplemental/wa2009_pslc_sanjuan_footprint.kmz
Theme
ISO 19115 Topic Category
elevation
Theme
bare earth
Theme
bare ground
Theme
high-resolution
Office for Coastal Management
Charleston
SC
Data Set
As Needed
las
LiDAR points in LAS 1.1 format
none
Any conclusions drawn from the analysis of this information are not the responsibility
of Watershed Sciences, PSLC, NASA, USGS, NOAA, the Office for Coastal Management or its partners.
Puget Sound LiDAR Consortium
Data Steward
2013-02
Organization
NOAA Office for Coastal Management
NOAA/OCM
coastal.info@noaa.gov
2234 South Hobson Ave
Charleston
SC
29405-2413
(843) 740-1202
https://coast.noaa.gov
NOAA Office for Coastal Management Home Page
Online Resource
Distributor
2013-02
Organization
NOAA Office for Coastal Management
NOAA/OCM
coastal.info@noaa.gov
2234 South Hobson Ave
Charleston
SC
29405-2413
(843) 740-1202
https://coast.noaa.gov
NOAA Office for Coastal Management Home Page
Online Resource
Metadata Contact
2013-02
Organization
NOAA Office for Coastal Management
NOAA/OCM
coastal.info@noaa.gov
2234 South Hobson Ave
Charleston
SC
29405-2413
(843) 740-1202
https://coast.noaa.gov
NOAA Office for Coastal Management Home Page
Online Resource
Point of Contact
2013-02
Organization
NOAA Office for Coastal Management
NOAA/OCM
coastal.info@noaa.gov
2234 South Hobson Ave
Charleston
SC
29405-2413
(843) 740-1202
https://coast.noaa.gov
NOAA Office for Coastal Management Home Page
Online Resource
Ground Condition
-123.203513
-122.577637
49.002581
48.413671
Range
2009-02-13
2009-04-30
Yes
Unclassified
This data can be obtained on-line at the following URL:
https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=1464
;
None
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.
https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=1464
Customized Download
Create custom data files by choosing data area, product type, map projection, file format, datum, etc.
https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/1464/index.html
Bulk Download
Simple download of data files.
https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/1464/supplemental/wa2009_pslc_sanjuan_footprint.kmz
Browse Graphic
Browse Graphic
kmz
This graphic shows the lidar coverage for portions of San Juan and Whatcom Counties in Washington.
https://coast.noaa.gov
Online Resource
https://coast.noaa.gov/dataviewer
Online Resource
2016-05-23
Date that the source FGDC record was last modified.
2017-11-14
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.
2018-02-08
Partial upload of Positional Accuracy fields only.
2018-03-13
Partial upload to move data access links to Distribution Info.
Microsoft Windows XP Version 5.1 (Build 2600) Service Pack 3; ESRI ArcCatalog 9.2.6.1500
Statements of statistical accuracy apply to fixed terrestrial surfaces only and may not be applied to areas of dense vegetation or steep terrain. To calibrate laser accuracy for the
LiDAR dataset, 2644 RTK ground survey points were collected on fixed, hard-packed road surfaces within the survey area.
; Quantitative Value: 0.042 meters, Test that produced the value:
The Vertical Root Mean Square Error (RMSEz) of the data set is 0.042m (0.136 feet). Accuracy was assessed using 2644 ground survey (real time kinematic) points. Please see LiDAR data report for a discussion of statistics
related to these datasets.
LiDAR data has been collected and processed for all areas within the project study area.
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. The data was examined at a 1:2000 scale.
1
Acquisition.
The LiDAR data was collected between February 13th-17th, 2009 and April 30th, 2009. The survey used a Leica ALS50 Pase II laser system mounted in a Cessna Caravan 208B, and an Optech 3100 laser system mounted in a Cessna
Caravan 208B. Near nadir scan angles were used to increase penetration of vegetation to ground surfaces. Ground level GPS and aircraft IMU were collected during the flight.
2
Processing.
1. Flight lines and data were reviewed to ensure complete coverage of the study area and positional accuracy of the laser points.
2. Laser point return coordinates were computed using ALS Post Processor software, IPAS Pro GPS/INS software, REALM survey suite, and PosPac software, based on independent data from the LiDAR system, IMU, and aircraft.
3. The raw LiDAR file was assembled into flight lines per return with each point having an associated x, y, and z coordinate.
4. Visual inspection of swath to swath laser point consistencies within the study area were used to perform manual refinements of system alignment.
5. Custom algorithms were designed to evaluate points between adjacent flight lines. Automated system alignment was computed based upon randomly selected swath to swath accuracy measurements that consider elevation, slope, and
intensities. Specifically, refinement in the combination of system pitch, roll and yaw offset parameters optimize internal consistency.
6. Noise (e.g., pits and birds) was filtered using ALS postprocessing software and REALM software tools, based on known elevation ranges and included the removal of any cycle slips.
7. Using TerraScan and Microstation, ground classifications utilized custom settings appropriate to the study area.
8. The corrected and filtered return points were compared to the RTK ground survey points collected to verify the vertical and horizontal accuracies.
9. Points were output as laser points, TINed and GRIDed surfaces.
3
Metadata imported.
2009-06-22T00:00:00
4
The NOAA Office for Coastal Management (OCM) received classified topographic files in LAS V1.1 format. The files contained lidar
elevation 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. All elevations below -4 feet were filtered and removed using LasTools' las2las tool.
2. The topographic las files were converted from orthometric (NAVD88) heights to ellipsoidal heights using Geoid03.
3. The topographic las files were converted from a Projected Coordinate System (WA SP North) to a Geographic Coordinate system (NAD 83).
4. The topographic las files' vertical units were converted from feet to meters.
5. The topographic las files' horizontal units were converted from feet to decimal degrees.
2013-02-01T00:00:00
gov.noaa.nmfs.inport:50158
Anne Ball
2017-11-15T15:24:37
SysAdmin InPortAdmin
2022-08-09T17:11:38
2022-03-16
OCM Partners
OCMP
1002
Public
No
2022-03-16
1 Year
2023-03-16