Hey Matt,
If i remember correctly osgeo4w is 32bit (its been a while since iv
looked at the osgeo4w binaries however so i may be incorrect). If they
are 32bit and you are setting -wm to 2048 (2GB) you might be having
memory limitation issues (which i believe 2GB virtual memory for x86
On 11-06-08 03:05 PM, Matt Wilkie wrote:
Hi Folks,
Can anyone tell me what this error means and how to work around it?
Win7 x64 command shell
osgeo4w gdal 1.8
13gb ram (~4.7gb free according to Process Explorer)
121gb free on the drive (mapped to network)
20gb free on drive pointed to by
Hi Frank,
Thanks for the clear explanation. I've added, with light editing, to
http://trac.osgeo.org/gdal/wiki/UserDocs/GdalWarp.
I imagine you will just have to use more modest buffers or else get a 64bit
executable for gdalwarp.
Running gdalwarp with defaults (no options specified) seems
