Seems large enough for me.
Stephen Mather
On Jan 1, 2011, at 5:47 AM, Even Rouault wrote:
>>
>> What's the new ceiling on image size for overview calculation?
>
> The same as before hopefully. I'm not sure what the limit is. From a quick
> look
> at the code, I'd say perhaps if the raster_wi
>
> What's the new ceiling on image size for overview calculation?
The same as before hopefully. I'm not sure what the limit is. From a quick look
at the code, I'd say perhaps if the raster_width * 64 > 2 billion. This could be
probably overcomeby modifying the algorithm if it became a limit in re
Seems to have done the trick, thanks Even.
What's the new ceiling on image size for overview calculation?
Steve
On Fri, Dec 31, 2010 at 11:38 AM, Even Rouault wrote:
> Stephen,
>
> this should be fixed now in SVN.
>
> This was indeed something wrong in a recent optimization in overview
> com
Stephen,
this should be fixed now in SVN.
This was indeed something wrong in a recent optimization in overview
computation. This could cause integer overflow, that was triggered when dealing
with a dataset where width * height > 2 billion.
Thanks for reporting !
___
Stephen,
I've just managed to reproduce your issue by creating a fake 6x6 3
band tif and running gdaladdo on it. Investigating...
Le vendredi 31 décembre 2010 16:44:04, Stephen Mather a écrit :
> Hi All,
> Testing out gdal 1.8; really excited by
> http://www.gdal.org/gdallocationinfo
Hi All,
Testing out gdal 1.8; really excited by
http://www.gdal.org/gdallocationinfo.html. Below is a comparison of doing
the same process in 1.7.3 and then 1.8dev, released 2010/01/19
$ gdaladdo --version
GDAL 1.7.3, released 2010/11/10
$ gdalbuildvrt LEAP_Tree_Height_low_res_test.vrt *.png
