2012 FWS Lidar DEM: Wapato, OR

Date of collection

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.

Bulk download of data files in the original coordinate system.

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.

An overview of the Tualitin wildlife preserve, including lidar information such as accuracy, which is from where the values reported in this metadata record are derived.

LiDAR Data Acquisition: The LiDAR acquisition mission was flown on May 15, 2012. LiDAR acquisition of the project area consisted of 21 low level flight lines with an average altitude of 375 meters. The imagery acquisition consisted of 9 high level flight lines flown at an average altitude of 860 meters.

A network of control points was established within the project boundary to validate the accuracy of the LiDAR data. The network consisted of Real Time Kinetic (RTK) points collected by Terra Remote Sensing, and existing US Fish and Wildlife Service monuments. The following points, WP02, WP03, WP06, and WP08 were verified by Terra Remote Sensing against the active CORS control stations, JIME (Portland, OR) and NWBG (Newberg, OR). An additional network check was completed between CORS stations FTS5, GOBS, and P367. Points WP02 and WP08 were also used as an RTK/PPK (Post Processed Kinematic) base station for the collection of lidar and orthophoto checkpoints.

The raw project LiDAR data was imported, processed, and outputs were created using the TerraScan software suite. Automated ground filters were run on the raw las data. These filters include factors and settings such as max building size, terrain angle, iteration angle degrees to plane, iteration distance to plane, reduce iteration angle when edge length is less than, and stop triangulation when edge length is less than. After the automated ground filter is run each tile is than checked for spikes and anomalies. Manual edits are applied to any areas that the analysts interpreted the ground doing something other than what the automatic ground filter interpreted. An analyst also classifies and edits any other las point to needed feature classes at this time. Only the LAS inside the provided map limit was classified and checked by analysts. Any points that were relevant to the classification were classified to the SOW requirements and placed using the classes provided in the SOW. Class 1 Processed, but unclassified, Class 2 Bare-Earth Ground, Class 3 Vegetation, Class 4 Roads, Class 7 Noise, Class 9 Water, Class 10 Ignored Ground, Class 11 Withheld. Classified tiles were saved as las (Version 1.2). After classification and edits were complete the projection information was Geo-Coded back into the LAS files.

Hydro break lines that were collected during the ground classification for flowing water greater than 100 feet wide, water bodies larger than 2 acres or 350 feet in diameter, and culvert polygons were used in conjunction with the bare earth LAS. Bare earth points that were within 1 foot proximity of a break line or polygon were buffered out of the ground. Ground inside of the culvert polygons was removed to allow water to flow for hydraulic modeling purposes.

NOAA/OCM received the data from DOGAMI in ESRI GRID format . Data were in NAD83(CORS 96) Oregon Lambert horizontally and NAVD88 (Geoid09) vertically. The data were processed to the Digital Coast.