National Geophysical Data Center (NGDC), NOAA Satellite and Information Service

View Metadata As: Get Data, FAQ, HTML, 19139 XML
Assess Metadata For: Completeness, DOI Readiness, CSW Readiness, Components

2007 Puget Sound LiDAR Consortium (PSLC) Topographic LiDAR: Eastern Washington and River Corridors

browse graphicThis kmz file shows the extent of coverage for the 2007 PSLC Eastern Washington and Oregon River Corridors lidar data set.
Watershed Sciences, Inc. (WS) collected Light Detection and Ranging (LiDAR) data in eastern Washington, eastern Oregon, and southern Canada in October and November, 2006 for the Puget Sound LiDAR Consortium. The survey areas cover portions of the lower Okanogan River in Washington, the Methow River in Washington, Lake Roosevelt in Washington, the Wenatchee River in Washington, and the John Day River in Oregon. The upper Okanogan River area, in Canada, was excluded from this project the data does not lie in borders of the United States. The total delivered acreage for the study areas shown above is >26,000 acres greater than the original amount, due to buffering of the original study areas and flight planning optimization. Collection dates for the project areas: ----- Lower Okanogan (WA) 20060506 ----- Methow (WA) 20061108-20061109 ----- Lake Roosevelt (WA) 20061016-20061020 & 20061029-20061101 ----- John Day River (OR) 20061005-20061007 ----- Wenatchee (WA) 20061012-20061013 & 20061025-20061028 -----

Cite this dataset when used as a source.

Search and Download
    Distribution Formats
    • LAZ
    Distributor DOC/NOAA/NOS/OCM > Office for Coastal Management, National Ocean Service, National Oceanic and Atmospheric Administration, U.S. Department of Commerce
    Point of Contact Diana Martinez
    Puget Sound Lidar Consortium (PSLC)
    206-971-3052
    dmartinez@psrc.org
    Associated Resources
    • Lidar Dataset Supplemental Information
    Originator
    • DOC/NOAA/NOS/OCM > Office for Coastal Management, National Ocean Service, National Oceanic and Atmospheric Administration, U.S. Department of Commerce
    Originator
    • Diana Martinez
      Puget Sound Lidar Consortium (PSLC)
    Publisher
    • DOC/NOAA/NOS/OCM > Office for Coastal Management, National Ocean Service, National Oceanic and Atmospheric Administration, U.S. Department of Commerce
    Date(s)
    • publication: 2013-11-20
    Data Presentation Form: Digital image
    Dataset Progress Status Complete
    Data Update Frequency: As needed
    Purpose: Provide high resolution terrain elevation and land cover elevation data.
    Use Limitations
    • These data depict the elevations at the time of the survey and are only accurate for that time. 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. Any conclusions drawn from analysis of this information are not the responsibility of NOAA or any of its partners. These data are NOT to be used for navigational purposes.
    Time Period: 2006-05-06  to  2006-11-09
    Spatial Reference System: urn:ogc:def:crs:EPSG::4269 Ellipsoid in Meters
    Spatial Bounding Box Coordinates:
    N: 48.95706996
    S: 44.43660155
    E: -117.7205329
    W: -120.9646779
    Spatial Coverage Map:
    Themes
    • Topography
    • Elevation
    • Model
    • LiDAR
    • LAZ
    • LAS
    • Remote Sensing
    Places
    • US
    • Washington
    • Oregon
    • Chelan County
    • Okanogan County
    • Ferry County
    • Stevens County
    • Grant County
    Use Constraints No constraint information available
    Fees Fee information not available.
    Lineage Statement Lineage statement not available.
    Processor
    • DOC/NOAA/NOS/OCM > Office for Coastal Management, National Ocean Service, National Oceanic and Atmospheric Administration, U.S. Department of Commerce
    • DOC/NOAA/NESDIS/NGDC > National Geophysical Data Center, NESDIS, NOAA, U.S. Department of Commerce
    Processing Steps
    • Acquisition. The LiDAR surveys utilized two different laser systems?the Leica ALS50 Phase II and the Optech 3100. Flight parameters were different for each system, resulting in different native pulse densities (the number of pulses emitted by the LiDAR system from the aircraft). Some types of surfaces (i.e., dense vegetation or water) may return fewer pulses than the laser originally emitted. Therefore, the delivered density can be less than the native density and lightly variable according to distributions of terrain, land cover and water bodies. All study areas were surveyed with opposing flight line side-lap of =50% (=100% overlap) to reduce laser shadowing and increase surface laser painting. Both laser systems allow up to four range measurements per pulse, and all discernable laser returns were processed for the output dataset.
    • 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, and Waypoint GPS, 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, 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
    • The NOAA Coastal Services Center (CSC) 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. Lake Roosevelt, John Day River and Lower Okanogan data was received in UTM Zone 10 (in meters); Wenatchee and Methow data were received in UTM Zone 11 (in meters); all datasets were vertically referenced to NAVD88 using the Geoid03 model. The vertical units of the data were meters. CSC performed the following processing for data storage and Digital Coast provisioning purposes: 1. The All-Return ASCII txt files were parsed to LAS files. 2. The All-Return ASCII files were converted from txt format to las format using LASTools' txt2las tool and reclassified to fit the CSC class list, N=1 (unclassified), G=2 (ground). 3. Bad elevations were removed the las files. 4. The las files were converted from a Projected Coordinate System (UTM Zone 10/11) to a Geographic Coordinate system (NAD83). 5. The data were converted to LAZ format.
    • The NOAA National Geophysical Data Center (NGDC) received lidar data files via ftp transfer from the NOAA Coastal Services Center. The data are currently being served via NOAA CSC Digital Coast at http://www.csc.noaa.gov/digitalcoast/. The data can be used to re-populate the system. The data are archived in LAS or LAZ format. The LAS format is an industry standard for LiDAR data developed by the American Society of Photogrammetry and Remote Sensing (ASPRS); LAZ is a loseless compressed version of LAS developed by Martin Isenburg (http://www.laszip.org/). The data are exclusively in geographic coordinates (either NAD83 or ITRF94). The data are referenced vertically to the ellipsoid (either GRS80 or ITRF94), allowing for the ability to apply the most up to date geoid model when transforming to orthometric heights.

    Metadata Last Modified: 2013-12-31

    For questions about the information on this page, please email: mike.sutherland@noaa.gov