-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
LERC unsupported with 1.3.0 #94
Comments
The dockerfile pulls in the pypi wheel: LERC works with
and not with
And even going back to 1.1.0 and python3.7 with
It looks like the user from #70 is using conda-forge (rasterio/rasterio#2270) not the wheels. Anyway, if LERC isn't explicitly supported by the rasterio wheels that's fine, just wanted you to be aware of the potential regression! It doesn't even actually effect me: I briefly used LERC a while ago before realising that zstd was about the same size and faster (and lossless!) and I had some leftover tests which started failing at 1.3.0. I just removed the tests, I've never seen LERC anywhere else in the wild. |
@ajnisbet thanks for the follow up! I suspect that a switch in this project from using GDAL's internal libtiff (which might have vendored LERC) to a system libtiff (shared with PROJ) is involved. |
Makes sense, I'll close the issue as it sounds like this is a (understandable) wontfix. Thanks for all your work on rasterio! |
We recently came across this behavior while attempting to upgrade rasterio and the titiler stack within the Microsoft Planetary Computer. We have about 380k LERC COGs and so are also interested in rasterio support (our setup previously worked, likely as described in this issue). Thanks for your work on this, and we'll keep an eye on #100. |
rasterio 1.2.10 supported reading from LERC-encoded rasters, but this no longer works since 1.3.0.
Here's a minimal Dockerfile that triggers the error:
fails with
versions 1.3.0 to 1.3.2 inclusive fail, 1.2.10 works fine.
The raster is encoded with
using GDAL 3.3.1 (installed with conda on ubuntu).
The text was updated successfully, but these errors were encountered: