I've verified the incorrect interpolation results on another machine (a
laptop with an nVidia gt-555m GPU).
I'm honestly at a loss as to what is causing this, and hope it's not
something simple. Has anyone run across this before?
Best,
Jonathan
On 3/5/2016 8:54 PM, Jonathan Williams wrote:
> To
To clarify: doing the gdalwarp resample without OpenCL is producing a
realistic Float32 value range. Doing it WITH OpenCL is producing far
higher values.
This is on a Tesla M2090. No other experiments/benchmarks have produced
this kind of result, and as I wrote below, gdalwarp itself works when
on
Hello,
I've run into an odd problem that I suspect is the result of some
incorrect variable type casting, but I'm not sure where to look or how
to fix it.
Inputting a raster in Float32 format (or Float64, with -ot Float32
and/or -wt Float32 enabled on the command line) and attempting to do a
resam
