[gdal-dev] gdalwarp -ts issue when output size is too large.
Jerl Simpson
jsimpson at wxtrends.com
Tue Dec 11 13:45:09 PST 2012
I'm having an issue using gdalwarp to interpolate over some data to smooth
it out.
gdalwarp --version
GDAL 1.9.1, released 2012/05/16
I have a dataset that's rather small:
gdalinfo shows:
Size is 360, 181
Coordinate System is `'
Origin = (-0.500000000000000,90.500000000000000)
Pixel Size = (1.000000000000000,-1.000000000000000)
Size is 360, 181
Coordinate System is `'
Origin = (-0.500000000000000,90.500000000000000)
Pixel Size = (1.000000000000000,-1.000000000000000)
For testing I'm using
gdalwarp -of netCDF -r cubicspline -ts WIDTH 0 in.nc out.nc
Everything is great, until I get the WIDTH >= 5765
My data goes from 0-360. When I'm below 5765, I see the full set of data
when I use ncview or gdaldem to view results. When I am at or above 5765,
however, I only see the data from 180-360.
Exactly half the data is missing, and it's always missing from 0-180.
File size is 64Mb, so it's not an issue with being over the 2Gb limit.
gdalinfo on the warped image is:
Size is 5765, 2899
Coordinate System is `'
Origin = (-0.500000000000000,90.500000000000000)
Pixel Size = (0.062445793581960,-0.062445793581960)
Does anyone have an insight as to what might be going on?
Thanks
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/gdal-dev/attachments/20121211/fe76783d/attachment.html>
More information about the gdal-dev
mailing list