Thanks @ianshmean for linking the docs to OMETIFF.jl
@tlnagy is this entirely specific to OMETIFFs (would probably make sense given the name), or does it extend to general TIFF images?
@ajsc4 There is nothing specific to OME-TIFFs about my memory mapping code here. I simply create a new type that loads in the plane that you need when you fire off a
getindex call. As an easy workaround, you can convert your TIFFs to OME-TIFFs using ImageJ or some other tool and OMETIFF.jl should work. Word of warning though, OME-TIFF supports a limited subset of TIFF files.
My longer term plan is to transition to the architecture I’m developing in my
TIFF.jl repo which is much more flexible and supports BigTIFFs, compression, and a lot of other TIFF weirdities.
I was planning to refactor
OMETIFF.jl and move the mmap code over to TIFF.jl and have OMETIFF.jl simply be a wrapper that adds some features from the metadata. I haven’t had time to do this port myself yet (blame 2020), but I would be happy to accept a PR over at