2010 USACE NCMP Topobathy Lidar: Oregon and Washington

Dates of collection for Oregon.

Dates of collection for Washington.

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 LAZ format, geographic coordinates, orthometric heights. Note that the vertical datum (hence elevations) of the files here are different than described in this document.

Information on the NOAA Office for Coastal Management (OCM)

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.

Link to data set footprint.

Link to custom download, from the Data Access Viewer (DAV), the raster Digital Elevation Model (DEM) data that were created from this lidar data set.

These data were collected using the ALS60 lidar system. They are owned by Fugro EarthData and operated through contract. The system collects topographic lidar data at maximum pulse rate of 200 kHz in a wavelength of 1064 nm. A CASI-1500 hyperspectral line scanner integrated with the system. Aircraft position, velocity and acceleration information are collected by the onboard GPS/IMU system. Raw data were transferred to the office and processed in IPAS software. Aircraft position data are processed using POSPac software and the results are combined with the lidar data to produce 3-D positions for each lidar shot. Upon processing, validation and QA/QC in the software packages GeoCue and TerraScan, anomalous data are flagged as invalid and necessary reflights are called. Fugro's proprietary software converts all valid data from ellipsoid to orthometric heights based on the NGS' GEOID09 model and exports topographic data as a series of LAS files with a single file per flightline per 5km box.

1.The raw lidar data was processed through a minimum block mean algorithm, and points were classified as either bare earth or non-bare earth. 2. User developed ""macros"" that factor mean terrain angle and height from the ground were used to determine bare earth point classification. 3. The next phase of the surfacing process was a 2D edit procedure that ensures the accuracy of the automated feature classification. 4. Editors used a combination of imagery, intensity of the lidar reflection, profiles and tin-editing software to assess points. 5. The lidar data was filtered, as necessary, using a quadric error metric to remove redundant points. This method leaves points where there is a change in the slope of surfaces (road ditches) and eliminates points from evenly sloped terrain (flat field) where the points do not affect the surface. 6. The algorithms for filtering data were utilized within Fugro EarthData's proprietary software and commercial software written by TerraSolid. 7. The flight line overlap points were merged back into filtered data set for delivery product. 8. The point cloud data were delivered tiled in LAS 1.2 format; unclassified (1), ground (2), low/noise (7), water (9), and overlap (12).

These data were then imported into GeoCue and combined with valid bathymetric data that was provided by Fugro in ASCII format. The resulting LAS v1.2 file has points classified as unclassified (1), ground (2), and valid bathymetric data (29.)

The NOAA Office for Coastal Management (OCM) received 157 laz files in las 1.2 format. The files contained lidar intensity and elevation measurements for the project area. Horizontal positions were provided in geographic coordinates, referenced to the North American Datum of 1983 (NAD83). Vertical positions were provided in ellipsoid elevations and in meters. OCM performed the following processing for data storage and Digital Coast provisioning purposes:

1. Assigned the geokeys, sorted the data by gps time and copied the data to database and to https.