If a file suffix is .ome.tif or .ome.btf or .ome.zarr, it should populate the ome context.
The object needs to follow the protocol bidsschematools.types.protocols.Ome, possibly just using bidsschematools.types.context.Gzip.
For .ome.zarr files, https://github.com/ome/ome-zarr-py is probably the right tool for the job. For .ome.tif/.ome.btf, I think https://github.com/tlambert03/ome-types looks like the right thing. The OME group discussed deprecating their own Python bindings for this project in ome/ome-model#194. It seems like there isn't a lack of options: https://pypi.org/search/?q=ome
Note that our concern is fast metadata access, not data array access.
If a file suffix is
.ome.tifor.ome.btfor.ome.zarr, it should populate theomecontext.The object needs to follow the protocol bidsschematools.types.protocols.Ome, possibly just using bidsschematools.types.context.Gzip.
For
.ome.zarrfiles, https://github.com/ome/ome-zarr-py is probably the right tool for the job. For.ome.tif/.ome.btf, I think https://github.com/tlambert03/ome-types looks like the right thing. The OME group discussed deprecating their own Python bindings for this project in ome/ome-model#194. It seems like there isn't a lack of options: https://pypi.org/search/?q=omeNote that our concern is fast metadata access, not data array access.