Closed ehusby closed 1 year ago
@ehusby here's a comparison of this PR with the current output for a Float32 ortho job. It appears to have increased the resulting filesize significantly.
I tested predictor values of 2 and 3 on output data types {Byte,UInt16,Float32}, and often the higher predictor value ended up making the output rasters larger than predictor value 1 (same as not setting it at all).
Thanks for testing earlier this year, @Shane98c :) Miss ya!
Currently testing predictor=3 for optimal float compression. Note the FIXMEs about the ideal predictor setting for integer compression.