Data Management Plan

This delivery contains point cloud data in LAS 1.1 format, classified in the following manner. Class 0: Never Classified, Class 1: Unclassified, Class 2: Ground, Class 7: Low/High Point (Noise), and

Class 12: Overlap.

The following are the collection parameters and equipment used to create these data sets.

Aircrafts: Cessna 320 (N3443Q) and Piper Navajo (N6GR)

Lidar System: Optech ALTM Gemini (03SEN145)

Approximate Collection Altitude (Above Mean Terrain): 1800 meters

Ground Speed: 180 kts

Pulse Rate Frequency: 70 kHz

Mirror Scan Frequency: 40 Hz

Scan Angle (+/-): 16 degrees

Beam Divergence: Narrow (0.25 mrad)

Accuracy statements are based on areas of moderate terrain, with points classified as ground. Diminished accuracies are to be expected in areas of extreme terrain

and dense vegetation. The accuracy of each point is expected to meet the vertical accuracy standard, derived products may be less accurate in areas of extreme terrain

and dense vegetation due to a lesser number of points defining the ground in these areas.

Classified data sets such as this one may have varying posting due to some pulses not reaching the ground.

Be aware the the Western Kenai Lowlands and Eastern Kenai Watershed have different accuracies and point spacings. Read this metadata record thoroughly to determine what the accuracies and point

spacing are for your area of interest.

USGS Contract No. 07CRCN0002

USGS Task Order No. 07002C0021.

Process Steps:

• 2008-06-10 00:00:00 - System Calibration: Aero-Metric collected data over a previously surveyed area in Palmer, Alaska. Data was collected at the same settings as this project, using two intersecting perpendicular lines. Two GPS ground stations were operating on site in order to minimize GPS error. 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 8.001 (TerraSolid, Ltd.), to compute corrections for roll, pitch, heading, and mirror scale. These corrections were applied to the initial processing settings (.res file). The data was reprocessed to verify the corrections were applied properly. The corrected data was then compared to ground surveyed measurements in order to check for any consistent vertical bias. The final step in calibration verified there was minimal vertical noise due to changes in intensity. This was done by comparing elevations of points on the airport runway, one point on a runway stripe and another adjacent point on the pavement.
• 2008-07-28 00:00:00 - Create 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 provided to Aero-Metric by DOWL/HKM, and were referenced to NAD83 (CORS96) with GEOID06 derived orthometric heights. The maximum baseline distance for this area was 23 km, the average base line length was 15 km. The mean GPS positional accuracy for this area was +/- 0.05 meters.
• 2008-07-28 00:00:00 - Integrate SBET and raw laser data to produce point cloud data in LAS 1.1 format for each flight line.
• 2008-07-28 00:00:00 - Compute the roll, pitch, heading, and mirror scale correction factors for each flight line, then apply corrections to the corresponding flight line.
• 2008-08-21 00:00:00 - 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.
• 2008-08-22 00:00:00 - Manual classification of any data which appears to be bare-earth but was not properly classified using the automated methods.
• 2010-01-21 00:00:00 - Create point clouds in LAS 1.1 format for all returns.
• 2009-10-02 00:00:00 - Data verified using survey control points, located throughout the area.
• 2010-01-21 00:00:00 - Metadata updated for Bounding coordinates, Spatial Reference info using FGDC template
• 2013-07-01 00:00:00 - The NOAA Office for Coastal Management (OCM) received the topographic files in LAS V1.1 format. The files contained lidar elevation and intensity measurements. The data were received in Alaska State Plane Zone 4 (FIPS 5004), NAD83 coordinates and were vertically referenced to NAVD88 using the Geoid06 model. The vertical units of the data were feet. OCM performed the following processing for data storage and Digital Coast provisioning purposes: 1. The User_Data field of the LAS files' header was set to a value (0-7) to reflect the LiDAR Data Areas (Area A: 0, Area B: 1, Area C: 2, Area D: 3, Area E: 4, Area F: 6, Area G: 5, Area H: 7) 2. The classification scheme was rearranged. Class 10 (High Noise) was combined into Class 7 (Low Noise). Class 11 (Single Return, not ground) was reclassified as Class 10. Class 13 (1st return of many returns) was reclassfied as Class 14. Class 14 (2nd return of many) was reclassified as Class 15. Class 15 (3rd of many returns) was reclassified as Class 16. Class 16 (Last return of many) was reclassified as Class 17. (see next processing step for further changes) 3. The topographic las files were converted from orthometric (NAVD88) heights to ellipsoidal heights using Geoid06. 4. The topographic las files were converted from a Projected Coordinate System (AK SP Zone 4) to a Geographic Coordinate system (NAD83). 5. The topographic las files' vertical units were converted from feet to meters. 6. The topographic las files' horizontal units were converted from feet to decimal degrees.
• 2022-08-29 00:00:00 - The NOAA Office for Coastal Management simplified the classification scheme because the classes signifying return numbers were replicating information already in the files. Classes 10, 14, 15, 16, and 17 were moved to class 1. The information content is retained in the return numbers while allowing the files to adhere to the LAS 1.1 classification standard.

This data can be obtained on-line at the following URL:

https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=2512

;