Re: [gdal-dev] ECRG RasterIO problem

l-dev@lists.osgeo.org *Subject:* Re: [gdal-dev] ECRG RasterIO problem Martin, I bet you have GDAL_FORCE_CACHING=YES set. At least that was the only way I could trigger the error. I've queued in https://github.com/OSGeo/gdal/pull/6464 a fix for that. The first commit is sufficient to fix the iss

Re: [gdal-dev] ECRG RasterIO problem

change. Best regards, Martin From: Even Rouault Sent: Monday, October 3, 2022 5:08 PM To: mchap...@hyperacktive.com; gdal-dev@lists.osgeo.org Subject: Re: [gdal-dev] ECRG RasterIO problem Martin, I bet you have GDAL_FORCE_CACHING=YES set. At least that was the only way I could trigger

Re: [gdal-dev] ECRG RasterIO problem

Martin, I bet you have GDAL_FORCE_CACHING=YES set. At least that was the only way I could trigger the error. I've queued in https://github.com/OSGeo/gdal/pull/6464 a fix for that. The first commit is sufficient to fix the issue despite being a bit hacky, but you could cherry-pick it without

[gdal-dev] ECRG RasterIO problem

All, I have an ECRG dataset that fails when reading pixels from the gdalrasterband object on one of the subdatasets. It appears that the underlying proxy dataset has a macro check called RB_PROXY_METHOD_WITH_RET_WITH_INIT_BLOCK that fails because the block sizes are different. This happens fo