I meant the GDAL_MAX_DATASET_POOL_SIZE option. Don't know if it really
has any influence, but these read errors happened multiple times in the
past when trying to translate VRT's with lots of input files, for tiles
that were actually readable. It could be of course also a problem of the
network file system, short network time-outs etc.
Armin
On 21/12/16 10:49, Even Rouault wrote:
On mercredi 21 décembre 2016 10:29:27 CET Armin Burger wrote:
Margherita
thanks, now that you say this, I remeber a special GDAL option
"GDAL_MAX_DATASET_POOL_SIZE" which by default is 100. The operating system
limit itself is high enough on our server (65k). When running the
processing again with less memory cache (and hence likely less concurrent
opened files) it worked without errors. I will set this GDAL option
and see
if I ever run into this errors again.
On which option did you play exactly ?
The TIFF error you get is a rather low level one (really trying to read
a range of bytes from a file), and I can't explain why GDAL options
would play a role on it.
Even
--
Spatialys - Geospatial professional services
http://www.spatialys.com
_______________________________________________
gdal-dev mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/gdal-dev
