Francisco, > Bingo! I've just tested with an ENVI dataset and is failing, same issue > with a few random blocks missing in the resulting rasters. Find below a > link with the code for a simple test reproducing the issue (also included > the ENVI dataset used). Just bear in mind that sometimes may generate the > final raster properly, although, based on my testing, it is highly > probable to get missing blocks with just a few runs: > > https://drive.google.com/open?id=0B-OCl1FjBi0YUkN4WWZmRjRfM1k >
Please create a ticket about that in Trac. > I'm not sure if it is related with the RawRasterBand, as my custom-driver > does not inherit from that class. However, both drivers, ENVI and mine, > inherit its custom raster band from GDALPamRasterBand. Oh .... now I see, > RawRasterBand/RawDataset inherit from GDALPam corresponding objects .... > Something weird its happening in the common part of these drivers... I don't think this comes from GDALPam, but rather from the lower level machinery of GDALRasterBand & GDALRasterBlock. As I said before, multi- threaded writing has never properly worked and I'm not sure if the issue you see is just an implementation bug or a design bug. Even -- Spatialys - Geospatial professional services http://www.spatialys.com _______________________________________________ gdal-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/gdal-dev
