That seemed to do the trick. It finished overnight, a lot faster than
before.
Final file was 83GB. (Only 1/2 the dataset was used)
Is there a reason GDAL_CACHEMAX 2147 is the maximum? Under 64-bit a 32-bit
process has 4GB of virtual memory rather than 2GB under 32-bit (or 3GB with
the /3GB Window
Howard,
Thanks for the hint. I was able to get what appear to be debug versions of
the extension DLLs (e.g. _gdal_d.pyd) along with symbols (e.g. _gdal_d.pdb).
For the record, here is a basic procedure that seemed to work for VS 2003:
1. Download release-1310-dev.zip and extract someplace, e.g.
C
On Jul 17, 2010, at 10:45 AM, Jason Roberts wrote:
> This is probably a question for Tamas Szekeres and Howard Butler, but I’m
> emailing the whole list in case others are knowledgeable or interested.
>
> As part of trying to figure out http://trac.osgeo.org/gdal/ticket/3672, I
> would like t
This is probably a question for Tamas Szekeres and Howard Butler, but I'm
emailing the whole list in case others are knowledgeable or interested.
As part of trying to figure out http://trac.osgeo.org/gdal/ticket/3672, I
would like to step through GDAL's SWIG-generated Python bindings in the
Vis
