2018 USFS Lidar DEM: Tieton Basin, WA

Create custom data files by choosing data area, product type, map projection, file format, datum, etc. A new metadata will be produced to reflect your request using this record as a base. Change to an orthometric vertical datum is one of the many options.

Bulk download of data files in GeoTiff format, WA State Plane South NAD83(HARN) US survey feet coordinates and orthometric heights in feet.

The Data Access Viewer (DAV) allows a user to search for and download elevation, imagery, and land cover data for the coastal U.S. and its territories. The data, hosted by the NOAA Office for Coastal Management, can be customized and requested for free download through a checkout interface. An email provides a link to the customized data, while the original data set is available through a link within the viewer.

This graphic displays the footprint for this lidar data set.

Link to the Atlantic, Inc. Technical Lidar Report from the Washington Lidar Portal.

Link to custom download, from the Data Access Viewer (DAV), the lidar point data from which these raster Digital Elevation Model (DEM) data were created.

Atlantic acquired 1588 passes of the entire AOI as a series of perpendicular and/or adjacent flight-lines executed in 44 flight missions conducted between June 29, 2018 and January 24, 2019. Onboard differential Global Navigation Satellite System (GNSS) unit(s) recorded sample aircraft positions at 2 hertz (Hz) or more frequency. LiDAR data was only acquired when a minimum of six (6) satellites were in view.

Ninety (90) Continuously Operating Reference Stations (CORS) were used to control the LiDAR acquisition for the entire defined project area.

A total of 545 ground survey points were collected in support of this project. Point cloud data accuracy was tested against a Triangulated Irregular Network (TIN) constructed from LiDAR points in clear and open areas. A clear and open area can be characterized with respect to topographic and ground cover variation such that a minimum of five (5) times the Nominal Pulse Spacing (NPS) exists with less than 1/3 of the RMSEZ deviation from a low-slope plane. Slopes that exceed ten (10) percent were avoided.

Each land cover type representing ten (10) percent or more of the total project area were tested and reported with a GCP. In land cover categories other than dense urban areas, the tested points did not have obstructions forty-five (45) degrees above the horizon to ensure a satisfactory TIN surface. The GCP value is provided as a target. It is understood that in areas of dense vegetation, swamps, or extremely difficult terrain, this value may be exceeded.

The GCP value is a requirement that must be met, regardless of any allowed busts in the VVA(s) for individual land cover types within the project. Checkpoints for the assessment are required to be well-distributed throughout the land cover type, for the entire project area.

Atlantic used Leica software products to download the IPAS ABGNSS/IMU data and raw laser scan files from the airborne system. Waypoint Inertial Explorer is used to extract the raw IPAS ABGNSS/IMU data, which is further processed in combination with controlled base stations to provide the final Smoothed Best Estimate Trajectory (SBET) for each mission. The SBETs are combined with the raw laser scan files to export the LiDAR ASCII Standard (*.las) formatted swath point clouds.

Departures from planarity of first returns within single swaths in non-vegetated areas were assessed at multiple locations with hard surface areas (parking lots or large rooftops) inside the project area. Each area was evaluated using signed difference rasters (maximum elevation - minimum elevation) at a cell size equal to 2 x ANPS, rounded to the next integer.

Using a combination of GeoCue, TerraScan and TerraMatch; overlapping swath point clouds are corrected for any orientation or linear deviations to obtain the best fit swath-to-swath calibration. Relative calibration was evaluated using advanced plane-matching analysis and parameter corrections derived. This process was repeated interactively until residual errors between overlapping swaths, across all project missions, was reduced to less than or equal to 2 cm. A final analysis of the calibrated lidar is performed using a TerraMatch tie line report for an overall statistical model of the project area.

Upon completion of the data calibration, a complete set of elevation difference intensity rasters (dZ Orthos) are produced. A user-defined color ramp is applied depicting the offsets between overlapping swaths based on project specifications. The dZ orthos provide an opportunity to review the data calibration in a qualitative manner. Atlantic assigns green to all offset values that fall below the required RMSDz requirement of the project. A yellow color is assigned for offsets that fall between the RMSDz value and 1.5x of that value. Finally, red values are assigned to all values that fall beyond 1.5x of the RMSDz requirements of the project.

Multiple automated filtering routines are applied to the calibrated LiDAR point cloud identifying and extracting bare-earth and above ground features. GeoCue, TerraScan, and TerraModeler software was used for the initial batch processing, visual inspection and any manual editing of the LiDAR point clouds. Classified point clouds were cut to match the tile index and its corresponding tile names and delivered in .laz format.

Bare earth Digital Elevation Models (DEMs) were derived using the bare earth (ground) LiDAR points. All DEMs were created with a grid spacing of 1 meter. DEMs were cut to match the tile index and its corresponding tile names and delivered in .img format.

Washington DNR converted the data to US survey feet to match the state coordinate system, Washington State Plane South.

The NOAA Office for Coastal Management (OCM) downloaded 21 raster DEM files in GeoTiff format from the Washington Lidar Portal. The data were in Washington State Plane South NAD83(HARN), US survey feet coordinates and NAVD88 (Geoid12B) elevations in feet. The bare earth raster files were at a 3 feet grid spacing. No metadata record was provided with the data. This record is populated with information from the Atlantic, Inc. technical report downloaded from the Washington Dept. of Natural Resources Washington Lidar Portal.

OCM performed the following processing on the data for Digital Coast storage and provisioning purposes:

1. Used an internal script to assign the EPSG codes (Horizontal EPSG: 2927 and Vertical EPSG: 6360) to the GeoTiff formatted files.

2. Copied the files to https.