Changes between Version 18 and Version 19 of Processing/LidarCalibrationProcedure


Ignore:
Timestamp:
Oct 16, 2009 12:47:29 PM (10 years ago)
Author:
knpa
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Processing/LidarCalibrationProcedure

    v18 v19  
    115115 * Save the text file.
    116116
    117 3. Preferably using data including areas of forest and the BIT mode data, run Rangecardcal (from ALSPP tools menu)
     1173. Preferably using data including areas of forest (little riss should do) and the BIT mode data, run Rangecardcal (from ALSPP tools menu) on all flightlines.
    118118 * Enter the average dz value as A1 to get the other offsets.
    119119 * Add the outputs to the ALSPP dialog and save the settings reg file (to a new name)
    120120
    1211214. Analyse the results
    122  * Check these results and re-run using the full FOV (~45 degrees)
     122 * Check these results and re-run using the full FOV (~45 degrees) on the low flightlines again.
    123123 * Check average dz is less than 1cm or so, and standard deviation <5cm in Terrascan control report. (also look at cross sections)
    124  * Then process the 4 high altitude flights in ALSPP and check in Terrascan (around nadir and swath edges)
     124 * Then process the 4 high altitude flights in ALSPP and check in Terrascan (around nadir and swath edges) (looking at absolute height).
    125125 * 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.
    126126-------