feat!: Handle transparency/nodata bit masks#205
Merged
kylebarron merged 5 commits intomainfrom Jan 29, 2026
Merged
Conversation
This was referenced Jan 29, 2026
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.
TIFF supports storing nodata values in a transparency bitmask.
Instead of exposing the raw bitmask itself to users, I decided that it would be a better API to expose a
Vec<bool>in theTypedArray. This requires a copy from the bitmask to theVec<bool>.In the future, we could add some sort of
BooleanArrayabstraction like Arrow that interprets the raw bits, but I think this is fine for now.Then in the Python API we expose the
Vec<bool>zero-copy through the buffer protocol as a uint8 array.Change list
Boolvariant toDataType.Bool(Vec<bool>)variant toTypedArray.Vec<bool>is exposed as a uint8 array of 0/1 values.shapeastuple[int, int, int], not aslist[int]