Changes between Version 3 and Version 4 of Processing/LidarCalibrationProcedure
- Timestamp:
- Apr 30, 2009, 12:36:15 PM (16 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Processing/LidarCalibrationProcedure
v3 v4 68 68 * You could just remove the point from one or two images (especially the high altitude images) or from all images. Then recalculate the network adjustment and iterate until Aposteriori reference is approx 1-2 and average residuals are 0.25,0.25 and 0.05. 69 69 * Can remove the points from the lower resolution images if it will help. We want more measurements in the higher resolution images than the lower ones if they are unclear to measure in (so don't just measure in them for the sake of it) 70 * When happy save the solution 70 * When happy save the solution - also note down roll, pitch and heading values in case of crashes 71 71 5. Return to ALS Post Processor 72 72 * Add the Pitch, Roll and Heading values into the boresight calibration dialog. … … 82 82 * Also possible to check for errors by re-ordering points by elevation 83 83 7. The boresight parameters can be manually twiddled (rather than using Attune) by reprocessing in ALS, changing the R,P,H values one at time. Only process parts of the flightlines for speed benefits. 84 85 8. When happy with the results save the ALS Post Processor settings to a .reg file for future reference. 86