Changes between Version 20 and Version 21 of Processing/LidarCalibrationProcedure


Ignore:
Timestamp:
Jul 14, 2010 10:19:09 AM (9 years ago)
Author:
emca
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Processing/LidarCalibrationProcedure

    v20 v21  
    9898 * 1. Nominal offset determination A1
    9999 * 2. Define relative differences for A2,A3,A4 and B1,B2,B3,B4
     100 * 3. Check if an offset exists between bank A and bank B
    100101
    101102points have approx. the same range error within +/-7 degrees of Nadir, so we look only at this region firstly.
     
    124125 * Then process the 4 high altitude flights in ALSPP and check in Terrascan (around nadir and swath edges) (looking at absolute height).
    125126 * Finally load in all flights into Terrascan (within a fence if memory issues) and check them (ideally along a stream because this has a “good” profile) Can use the travel path tool in Terrascan for comparing cross sections along a path.
     127
     1285. Check for offset between bank A and bank B
     129 * Leica have advised that *some* systems have an offset between bank A and bank B. To check for an offset process a single line using only returns from bank A then using only returns from bank B (ALSPP: Filters > Pre-Proc Filters > Filter Range Bank A/B).
     130 * Load the results in !TerraScan and check for any elevation difference.
     131    * If there is none then great.
     132    * If a consistent offset is visible then adjust all the values for bank B by this offset. Re-run the line again and check the result.
    126133-------
    127134== Final validation ==