Re: [gdal-dev] Help requested: Concurrent read of a GeoTiff

2017-03-28 Thread Grégory Bataille
Hey, just to let you know, I found the issue. So I think it has to do with the fact that I keep some handles opened on the original TIFF In the parent thread. Even setting the variable to None does not change anything, but I guess it's because the garbage collector is asynchronous. So if I do my i

Re: [gdal-dev] Help requested: Concurrent read of a GeoTiff

2017-03-21 Thread Grégory Bataille
hum... debugging in the C layers, that'll be interesting... Ok, I'll continue to dig in, thanks --- Gregory Bataille On Tue, Mar 21, 2017 at 8:44 AM, Even Rouault wrote: > On mardi 21 mars 2017 05:51:18 CET Grégory Bataille wrote: > > > Hey Even, > > > > > > reaching out again, because I just

Re: [gdal-dev] Help requested: Concurrent read of a GeoTiff

2017-03-21 Thread Even Rouault
On mardi 21 mars 2017 05:51:18 CET Grégory Bataille wrote: > Hey Even, > > reaching out again, because I just don't know... > > so here is gdal2tiles_parallel strategy (as far as I understand it) > - in each process, open the input file, compute the autowarped vrt (in the > case of the dataset I

Re: [gdal-dev] Help requested: Concurrent read of a GeoTiff

2017-03-20 Thread Grégory Bataille
Hey Even, reaching out again, because I just don't know... so here is gdal2tiles_parallel strategy (as far as I understand it) - in each process, open the input file, compute the autowarped vrt (in the case of the dataset I use at least) loop over tiles to generate and work only depending on the

Re: [gdal-dev] Help requested: Concurrent read of a GeoTiff

2017-03-16 Thread Grégory Bataille
no luck. I tried this config. I also tried (with this config) to do a copy of the vrt file (with shell utility, not gdal) in each thread before opening it (still goes to the same TIFF file though), but no luck. But at least now that you confirm that it's related to concurrent reads, I have somethi

Re: [gdal-dev] Help requested: Concurrent read of a GeoTiff

2017-03-16 Thread Even Rouault
On jeudi 16 mars 2017 18:45:03 CET Grégory Bataille wrote: > Does that mean a different vrt file or simply reopen the file to create a > gdal object in each process. Because I'm reopening the vrt file in each > thread Ah, that must be issue of http://gdal.org/gdal_vrttut.html#gdal_vrttut_mt Try d

Re: [gdal-dev] Help requested: Concurrent read of a GeoTiff

2017-03-16 Thread Grégory Bataille
Does that mean a different vrt file or simply reopen the file to create a gdal object in each process. Because I'm reopening the vrt file in each thread On Thu, 16 Mar 2017 at 17:23, Even Rouault wrote: > On jeudi 16 mars 2017 17:16:20 CET Grégory Bataille wrote: > > > Hello all, > > > > > > Re

Re: [gdal-dev] Help requested: Concurrent read of a GeoTiff

2017-03-16 Thread Even Rouault
On jeudi 16 mars 2017 17:16:20 CET Grégory Bataille wrote: > Hello all, > > Reaching out to the community caused I have failed for the past few days. > > *short version*, I'm trying to multithread the gdal2tiles utility, and I'm > getting this > > Generating Base Tiles: > ERROR 1: LZWDecode:Wron

[gdal-dev] Help requested: Concurrent read of a GeoTiff

2017-03-16 Thread Grégory Bataille
Hello all, Reaching out to the community caused I have failed for the past few days. *short version*, I'm trying to multithread the gdal2tiles utility, and I'm getting this Generating Base Tiles: ERROR 1: LZWDecode:Wrong length of decoded string: data probably corrupted at scanline 256 ERROR 1: