Changes between Version 30 and Version 31 of Processing/LidarCalibrationProcedure
- Timestamp:
- Aug 21, 2012, 10:03:21 AM (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Processing/LidarCalibrationProcedure
v30 v31 50 50 * If you change the value make a note on the ticket as it will not match the calibrated value given to us by Leica 51 51 * Ask Ops to check the value at the next available opportunity (http://arsf-dan.nerc.ac.uk/trac/wiki/Procedures/NewSeason#Scanencoder) 52 * Uncheck the BIT mode data (we don't need to process this) and run the ALSPP processing 52 * For Attune a minimum of 6 flightlines should be used: 2 orthogonal at mid altitude, 2 orthogonal a high altitude, 1 opposed at high altitude and 1 parallel at high altitude (30% overlap) 53 * Uncheck the BIT mode data (we don't need to process this) and any flightlines not needed for Attune - run the ALSPP processing 53 54 * Look at the filesizes of the output data. If the ATN.LAS files are over 400MB in size then Attune will not run. If this is the case re-process with only the part of interest of the line. 54 55 * Part of interest will be the area where all flight lines overlap. … … 94 95 * Set class as ground = 2 (ground is usually class 2) 95 96 * Adjustment criteria maxiter=50, angular (?)=1.00e-08 96 * Click Solve Calibration parameters and unselect Torsion, just want to solve roll, pitch and heading.97 * Click Solve Calibration parameters and deselect Torsion, just want to solve roll, pitch and heading. 97 98 * Analyse adjustment 98 99 * A good result would have aposteriori reference of between 1 and 2. … … 111 112 * Change output to LAS (not attune) 112 113 * Change output directory 114 * Additional flightlines should be processed to check the validity of the calibration (not just the 6 used for Attune) 113 115 * Re-run the processing 114 116