Changes between Initial Version and Version 1 of FAQ/processingspeed


Ignore:
Timestamp:
Jun 29, 2009 5:09:49 PM (10 years ago)
Author:
benj
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • FAQ/processingspeed

    v1 v1  
     1=== Q: Is there any way to speed up geocorrecting my data or to reduce the file size of the geocorrected files? ===
     2
     3'''A:'''[[BR]]
     4There are three main ways to do this:
     5
     61. Only geocorrect bands you want to look at. Azgcorr can be passed a -bl parameter that tells it only to geocorrect bands in the given list. For example, to correct bands 4, 5 and 6 you'd use:
     7
     8azgcorr ... -bl 4 5 6 -1 ...
     9
     10...the -1 at the end is necessary to tell azgcorr that you've finished giving it band numbers.
     11
     122. If you're only interested in part of the flightline, don't process the parts you're not interested in. This may require some trial-and-error to establish the line numbers. Use the -l option to azgcorr to process only a certain range of scan lines. You'll need to run the whole thing through once, optionally with only one band as above, to check the total number of scan lines. For example, for a flightline with 10000 scan lines, if you only want lines 2000-6000 you'd use:
     13
     14azgcorr ... -l 2000 6000 ...
     15
     163. Make the pixel size you're using larger - larger pixels give less detail, but the file size is inversely proportional to the square of the pixel size, so if you double the pixel size (if you don't need the extra detail) you will reduce file sizes by roughly 75%.
     17
     18[wiki:FAQ Back to FAQ]