Use internal libtiff #4537
Closed
Use internal libtiff #4537
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
So newer features work out of the box, such as `LERC` in `COG`. See https://gdal.org/drivers/raster/cog.html and similar PR at OSGeo/homebrew-osgeo4mac#1087
|
Ping @visr |
|
The homebrew discussion is a few years old. It does seem that since then features have been upstreamed sooner to https://gitlab.com/libtiff/libtiff, which has seen more frequent releases. So perhaps part of the COG docs are outdated already. If I search in the libtiff repo for LERC or JXL, it does seem like there is support. GDAL_jll depends on PROJ_jll which depends on Libtiff_jll, so this does not avoid the dependency. Perhaps it would be good to first ask on the GDAL mailing list if there are still many advantages to internal libtiff? |
|
Ok, so the other route would be to build LERC on Yggdrasil and link it to libtiff. |
|
Closed in favor of #4538. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
So newer compression features work out of the box, such as
LERCinCOG. See https://gdal.org/drivers/raster/cog.html and similar PR at OSGeo/homebrew-osgeo4mac#1087.I'm unsure/unaware about hard differences between the internal and external libtiff library or other drawbacks. I guess it should just work and gives us more features. Looking at https://gdal.org/drivers/raster/gtiff.html#creation-options, newer compression are first introduced in the internal libtiff and only later in the external one (or not yet, such as
JXL).Linking to GDAL.jl driver support issue JuliaGeo/GDAL.jl#65