Changes between Version 2 and Version 3 of Processing/CaliGeo


Ignore:
Timestamp:
Jun 1, 2009 7:24:04 PM (10 years ago)
Author:
mggr
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Processing/CaliGeo

    v2 v3  
    1313'''Process all lines''': Ticked. You can untick it and use a subset of the lines if you want, but this doesn't seem to work every time.
    1414
    15 '''Use DEM''': Ticked or unticked as appropriate. '''Use only DEMs that are in 16-bit unsigned integer format''' - on the current version of CaliGeo (4.9.5) other formats, particularly floating point, take a very, very long time to run and then give a wrong result. Note processing takes significantly longer with a DEM.
     15'''Use DEM''': Ticked or unticked as appropriate. '''Use only DEMs that are in 16-bit unsigned integer format''' - on the current version of CaliGeo (4.9.5) other formats, particularly floating point, take a very, very long time to run and then give a wrong result. Note processing takes significantly longer with a DEM.  Do not use DEMs when auto boresighting (see below)
    1616
    17 '''Average ground elevation from WGS-84 reference surface''': Average height of ground above spheroid. Only really matters if you're not using a DEM.
     17'''Average ground elevation from WGS-84 reference surface''': Average height of ground above spheroid. Only really matters if you're not using a DEM.  Little Riss is 273m.
    1818
    1919'''Unrectified intermediate file''': Level 1 file - *.dat, needs to be created first (use `touch filename.dat` in a terminal)[[BR]]
     
    4040These settings cannot be set from the GUI at all, but are still required. You need to set everything above, save the settings to an options file, adjust these in a text editor then read the options back into Caligeo. You can do the same with any of the options above, but note the angles marked "Boresight" in the options file aren't actually the boresight values as we think of them (they're the sensor co-registration angles).  You need the "Roll_Correction" (etc) angles instead.
    4141
    42 '''AUTOSYNCH_LAGTIME''': -0.055 for Eagle only (leave Hawk at 0)
    43 
     42'''AUTOSYNCH_LAGTIME''': -0.055 for Eagle only (leave Hawk at 0)[[BR]]
     43'''OUTPUT_PIXELSIZE''': whatever is appropriate, doesn't work in the GUI
    4444----
    4545
     
    6161To boresight lines using Caligeo:
    6262
    63  1. Process three (crossing) lines as above. '''Use 0 boresight values and NO DEM''' (forget this and do it over from scratch). The current version of Caligeo (4.9.5) has a bug whereby it will give (obviously) wrong results if using a DEM to boresight. Once they're working, save option files for each.
     63 1. Process three (crossing) lines as above. '''Use 0 boresight values and NO DEM''' (forget this and do it over from scratch).  Use the average elevation for the site (get from SRTM on the web or use 273m for Little Riss).  The current version of Caligeo (4.9.5) has a bug whereby it will give (obviously) wrong results if using a DEM to boresight. Once they're working, save option files for each.
    6464 1. In ENVI, with the three (georectified) lines open use Map > Registration > Select GCPs: Image to Image - it'll ask you which to use as the base and which as the warp image
    6565 1. Find GCPs for the following combinations (if you do this wrong your results will be wrong). You need a minimum of 6 GCPs for each, a few more is good, try and avoid RMS errors that are too high (<0.7 is reasonable, the lower the better):