Changes between Version 3 and Version 4 of Processing/PixelSize


Ignore:
Timestamp:
Apr 23, 2008 3:24:23 PM (11 years ago)
Author:
benj
Comment:

Changed description of the -g flag (interpolation)

Legend:

Unmodified
Added
Removed
Modified
  • Processing/PixelSize

    v3 v4  
    3232Reduce the pixel size progressively until you stop getting more detail out of the smaller pixel sizes or the edges start tearing.
    3333
    34 If you find that you're getting tearing at the edges but you still want to make the pixel size smaller to increase detail, you can also increase the interpolation value used by azgcorr - use the -g flag, which takes x and y direction values, eg:  azgcorr ... -g 5 5. This represents the maximum multiple of the pixel size across which it will interpolate the value, so if you've got 5m pixels then the above would interpolate across a no-data area of 25m. The default for this is 4 in both directions.
     34If you find that you're getting tearing at the edges but you still want to make the pixel size smaller to increase detail, you can also increase the interpolation value used by azgcorr - use the -g flag, which takes two values, eg:  azgcorr ... -g 5 5. Azgcorr automatically interpolates across any dropped frame gap smaller than the first number times the pixel size, and the second number determines how many successive data frames must be available before it will consider that a gap has ended (default 4 4 - about 10m for 2.5m pixels). Be aware that because this is interpolation, increasing this number does not necessarily improve your data in the gap, but just how it looks.
    3535
    3636---------