Changes between Version 2 and Version 3 of Processing/BoresightCalibration


Ignore:
Timestamp:
Jul 19, 2007, 3:24:36 PM (17 years ago)
Author:
mggr
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Processing/BoresightCalibration

    v2 v3  
    11= Boresight calibration =
    22
     3Copy of email to Andrew Wilson (wikise later)
     4{{{
     5As I understand it, a calibration flight passes over CEH several times in opposing directions.
     6
     7The idea is to process the data sets and overlay them, then adjust the PRH numbers until things line up exactly over the calibration points (and hopefully everywhere else).
     8
     9Because the flights are in opposing directions, one can "focus" the points inwards towards convergence by using estimates of distance and direction of flight/direction to convergence.
     10
     11Additionally, you have the positions of the calibration points exactly measured (by placing a GPS unit on them for several hours at different times of day) and also have a base station in the flight line (in the CEH tower?).  Once the calibration is correct, the mapped position of these points should match your recorded coordinates (if this is correct, how accurate do you normally get this?).
     12
     13Obviously, this would need to be done for each sensor (ATM, CASI, Hawk & Eagle).  The LIDAR correction is handled by Cambridge?
     14
     15Also, which tools do you normally use?  I'm presuming you mostly use Imagine with the GeoTIFFs?
     16}}}
    317-------------------
    418== 2007 point locations and notes ==