🔥 Remove cog3pio backend engine, drop xarray dependency#89
Merged
Conversation
Deciding to remove the image-tiff CPU-based Cog3pioBackendEntrypoint, in favour of the nvtiff CUDA-based backend happening over at cupy-xarray. Remove all code related to xarray, and also the rioxarray comparison benchmark. Users should look into other CPU-based TIFF readers (e.g. async-tiff) instead. This will also trim our dependency footprint considerably for easier maintenance and clearer focus on DLPack.
Remove xarray section from quickstart and API pages, deleted mention of xarray in recent changelog, and crossed it out in main README.md.
Take out async-tiff refactor since async-geotiff is out. Want to double-down more on hardware-accelerated decoding instead.
This file contains hidden or 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
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.
Deciding to remove the image-tiff CPU-based Cog3pioBackendEntrypoint, in favour of the nvtiff CUDA-based backend happening over at cupy-xarray. This will trim our dependency footprint considerably for easier maintenance and clearer focus on DLPack.
TODO:
CPU-based users should look into other TIFF readers (e.g. async-tiff) instead, while GPU-based users can look at xarray-contrib/cupy-xarray#81