Use length of Base64 binary array instead of bin data length#2039
Merged
petebankhead merged 1 commit intoqupath:mainfrom Nov 19, 2025
Merged
Conversation
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.
When importing a particular OME TIFF image with its OME XML shapes, the following exception occured:
This PR fixes that.
Note that support for OME XML masks is quite brittle, mainly because I don't think the OME XML Schema matches with real examples. For example:
1, while in reality the masks have widths of around30. So, the current code in QuPath is not using these mask width values. Same for the mask height.Because of these issues, the current QuPath code skips problematic shapes and doesn't import them. This means that in the future, it is not unlikely to have a user reporting missing shapes when importing OME XML shapes to QuPath.