2013 UAF/GINA Lidar: Vallenar Bay, Alaska

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.

This graphic displays the footprint for this lidar data set.

Link to data set report.

WSI created a smoothed-best estimated trajectory (SBET) of the sensor at a rate of 200 Hz, by integrating the airborne GPS and IMU data The basis of the GPS coordinates were two dual frequency GPS receivers, collecting data at a rate of 2 Hz operated by Aero-Metric during the acquisition phase of this project, and were referenced to NAD83 (CORS96) ellipsoid heights.

WSI integrated SBET and raw laser data to produce point cloud data in LAS 1.2 format for each flight line.

WSI processed data calibration: An in-situ calibration was performed using the data collect for this project. The data was classified in each line separately for ground and other common features between lines, such as building roofs. This data was processed in TerraMatch 11.001 (TerraSolid, Ltd.), to compute corrections for roll, pitch, heading, and mirror scale. These corrections are applied in order to minimize discrepancies between flight lines.

WSI automated classification of the bare-earth data from the LiDAR point cloud using a series of algorithms customized for the types of terrain encountered in the project.

WSI manually classified any data which appears to be improperly classified using the automated methods.

WSI provided AeroMetric with calibrated, vertically adjusted, and classified LiDAR data in the Vallenar Bay area.

AeroMetric completed a series of evaluations including verifying density requirements, confirming relative and absolute accuracies, reviewing coverage and classification's, and confirming the reproducibility of ranges within the LiDAR Data.

Due to tiling artifacts being identified in the low vegetation and high vegetations, using a automated method those classes were properly re-classified.

Create point cloud data, by tile in LAS 1.2 format.

The NOAA Office for Coastal Management (OCM) downloaded 32 laz files from the Alaska Division of Geological and Geophysical Surveys data Portal (https://elevation.alaska.gov/). The files contained classified elevation and intensity measurements for the 2013 Vallenar Bay data set. The data were in Alaska State Plane, Zone 5001 coordinates (NAD83 2011, US survey feet) and NAVD88 elevations (GEOID12A) in feet. The data were classified: Class 1: Unclassified, Class 2: Bare-earth ground, Class 3: Low vegetation, Class 4: Medium Vegetation, Class 5: High Vegetation, Class 6_ Buildings, Class 7: Noise, Class 8: Ground Model Keypoints, Class 9: Water, Class 10: Breakline Proximity, Class 14: Bridge Decks. Low vegetation is defined in the report as vegetation within 12 inches of the ground surface, medium vegetation as vegetation greater than 12 inches, but less than 36 inches above the ground surface and high vegetation as vegetation greater than 36 inches above the ground surface. OCM processed all points to the Digital Coast Data Access Viewer (DAV).

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

1. The LAStools software scripts lasinfo and lasvalidate were run on the laz files to check for errors.

2. An internal OCM script was run to check the number of points by classification and by flight ID and the gps times and intensity ranges.

3. Internal OCM scripts were run on the laz files to convert from Alaska State Plane, Zone 5001 coordinates to geographic coordinates, to convert from NAVD88 elevations to ellipsoid elevations using the GEOID12A model, to convert from feet to meters, to assign the geokeys, to assign a lidar domain profile, to sort the data by gps time and zip the data to database and to http.