== Processing LIDAR data from Leica ALS50 == This page describes the basic steps involved in processing the Raw Scan data from the Leica ALS50 II. More information can be found [wiki:Sensors/LeicaLIDAR/MashUp here] ----- === Navigation Processing === The first stage is to post-process the GNSS data and blend it with the IMU data to get the best position and altitude of the laser scanner for the flight. This uses the IPAS Pro and Grafnav software packages on windows. * [wiki:Processing/IPASPro IPAS Pro guide] * [wiki:Processing/IPASTC IPAS TC guide] * [wiki:Processing/GrafNavProcessing GrafNav guide] === Raw scan to point cloud === This stage of the processing takes the raw scanner files and georeferences them to create a point cloud of the data. This is usually in the binary LAS format but may be output as ASCII if you wish. This uses the ALSPP software. * [wiki:Processing/ALSPP ALS Post Processor guide] After running the ALSPP check the % of first returns column in the main window. This should be high (probably >95%). If not then it may be an indicator to problems with the data (such as a large % of cloud coverage) === Data QC === [wiki:Processing/Lidarqcprocedure Full QC procedure]. The final stages of the processing are to quality check the data and filter out noisy points. This can be very time consuming. See [wiki:Processing/TerrascanTips tips] on using Terrascan and also [wiki:Sensors/LeicaLIDAR/MashUp#QC here] for further notes from leica. The main steps will be: * to re-classify noisy points (haze, low points and isolated points) * check the horizontal overlap between neighbouring lines * check the elevation overlap between neighbouring lines * check the data against OS vectors if available * if GCPs available then compare them against LIDAR '''Once QC is complete, you need to start creating the delivery. Instructions are [wiki:Procedures/DeliveryCreation/LIDAR here].''' === Processing Full Waveform Data === If there is full waveform data with the project then follow the instructions below. Once the discrete data has been processed, use the same .reg file (with the corrected roll value) to process the full waveform data. Load the .reg file in ALSPP. Under Inputs> Waveform Processing check the box Process Waveform Data. Ensure the correct trigger delay values are entered - these should be populated from the calibrated reg file. Load in the !RawLaser data and select Run. If you get an error "Unable to open the waveform file in selected folder" ensure that the raw data folders are in the correct structure - !RawLaser & RawWFD (case sensitive). The full waveform files will be in the format ***_4.LAS. Once the data has been processed it can be viewed in !TerraScan. Details on this can be found [wiki:Processing/TScanFW here ] At the moment, there are no tools available to do any post-processing of the full waveform data. ---------------- == Calibration Files == The .reg files for the ALS processing can be found in the calibration directory of the ARSF repository in the lidar subdirectory. After a new calibration, write the details here and copy the new reg file to the arsf repository. '''March 2011 day 082''' - 2011_082_calibration.reg '''April 2010 day 096''' - 2010_096_calibration.reg '''March 2010 day 060''' - 2010_060_calibration.reg '''September 2009 day 268''' - 2009268_final.reg '''September 2009 day 252 ''' - 2009252a_calibration.reg '''June 2009 day 180''' - sn89_calibration_2009180a.reg '''February 2009 day 058''' - sn89_leica_calibrated_ammended_rangecorr.reg '''December 2008''' - SN089_Calibrated_by_Lecia-081206.reg '''November 2008''' - 20081101_calibration.reg