whether is runs the single or multi threaded version.
Thanks,
Leith Bade
le...@leithalweapon.geek.nz
___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/gdal-dev
ong?
Thanks,
Leith Bade
le...@leithalweapon.geek.nz
___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/gdal-dev
I am not paying
them for it...
Thanks,
Leith Bade
le...@leithalweapon.geek.nz
On 19 July 2010 05:58, Greg Coats wrote:
> On Jul 18, 2010, at 12:44 AM, Leith Bade wrote:
>
> kdu_compress also has a memory limit at 2 GB
>
>
> Not true. Based on your comment, I suspect that you are us
Windows boot switch).
I was successfully able to use kdu_compress on the result as well so now I
only need 4GB to store the file! (Although kdu_compress also has a memory
limit at 2GB, but you can flush the codestream after every tile to fix
that).
Thanks,
Leith Bade
le...@leithalweapon.geek.nz
On
large GTiff for kdu_compress to
work on.
Thanks,
Leith Bade
le...@leithalweapon.geek.nz
On 17 July 2010 14:22, Greg Coats wrote:
> I do not see that you specified that the output TIFF image be tiled
> -co TILED=YES -co BLOCKXSIZE=512 -co BLOCKYSIZE=512
> gdal_merge.py supports the -v input opti
which source images
intersect, and working left to right filling with solid color or copying
scanlines from the source image.
This allows the DEFLATE to work far more effciently as the write pattern is
horizontally linear.
What are your views/suggestions/etc.?
Thanks,
Leith Bade
le
Thanks for that.
Thanks,
Leith Bade
le...@leithalweapon.geek.nz
2009/4/28 Roger André
> Hi Leith,
>
> This should help get you started.
>
> Roger
> --
>
> On Sun, Apr 26, 2009 at 11:25 PM, Leith Bade <
> le...@leithalweapon.geek.nz> wrote:
>
>>
into Google Earth.
Thanks,
Leith Bade
le...@leithalweapon.geek.nz
___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/gdal-dev
