Improve handling of OME-TIFF multi-file filesets with partial metadata blocks (rebased onto dev_5_1) #2320
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.
This is the same as gh-2314 but rebased onto dev_5_1.
See https://trello.com/c/mVFYhwcJ/87-ome-tiff-missing-metadata-file
This commit partly reverts a previous bug fix for OME-TIFF with
BinaryOnly
blocks where theMetatadaFile
check inisThisType(RandomAccessInputStream)
was solely based on the file extension. Instead, an extra check is performed at theisThisType(String, boolean)
level ifmetadataFile
has been set byisThisType(RandomAccessInputStream)
to parse the metadata.To test this PR:
>
. In all cases, runningshowinf
at one of theBinaryOnly
OME-TIFF should display the image without error but fall back to being detected as TIFF