Re: [gdal-dev] RE: Memory Error in _gdal.Band_ReadRaster(*args, **kwargs)

2009-08-16 Thread Paul Meems
Thanks Greg for your help about speeding things up. But speed is the least of my problems. I wouldn't mind waiting 72 hours if it gets the job done. But even with this statement: gdal_retile --config GDAL_CACHEMAX 4000-v -s_srs EPSG:28992 -of ECW -ps 17335 16000 -targetDir tiles large.ecw I get

Re: [gdal-dev] RE: Memory Error in _gdal.Band_ReadRaster(*args, **kwargs)

2009-08-16 Thread Greg Coats
You said you have 8 GB RAM, and gdal_translate was using only 2 GB RAM, and your specific question was Do I need to set some settings to speed things up?. Yes, you should increase the amount of RAM gdal_translate makes available to GDAL_CACHEMAX. For example, gdal_translate --config

[gdal-dev] RE: Memory Error in _gdal.Band_ReadRaster(*args, **kwargs)

2009-08-14 Thread Paul Meems
I've been in contact with Christian the author of gdal_retile and he told me this problem is in the main GDAL library. He also suggested using some of the other GDAL tools to see if the problem persists. So I started using gdal_translate to copy my ecw to a new ecw using this statement:

Re: [gdal-dev] RE: Memory Error in _gdal.Band_ReadRaster(*args, **kwargs)

2009-08-14 Thread Greg Coats
It is my understanding that the default is gdal_translate --config GDAL_CACHEMAX 40 ... which equates to 40 MB of memory. If you want to allow gdal_translate to use say 2 GB of memory for GDAL_CACHEMAX, enter gdal_translate --config GDAL_CACHEMAX 2000 ... In my experience, increasing