You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 2, 2020. It is now read-only.
In zarr-developers/zarr-specs#50, a spec has been been proposed to define the group/array structure as well as metadata in the group:
example/
├── 0 # Full-sized array
├── 1 # Scaled down 0, e.g. 0.5; for images, in the X&Y dimensions
├── 2 # Scaled down 1, ...
├── 3 # Scaled down 2, ...
└── 4 # Etc.
{
“multiscale”: {
“version” : “0.1”,
“series” : [
{
“datasets” : [“0”, “1”, “2”, “3”, "4"]
}
// See link for more details
}
}
While I think having a separate group for "sub-resolutions" makes sense, since an image might be stored in in full resolution as zarr independent of sub-resolutions (and complies with the OME-spec), but I think we should target what is decided here.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Our current approach outputs a directory structure for tiled image pyramids as:
In zarr-developers/zarr-specs#50, a spec has been been proposed to define the group/array structure as well as metadata in the group:
While I think having a separate group for
"sub-resolutions"
makes sense, since an image might be stored in in full resolution as zarr independent of sub-resolutions (and complies with the OME-spec), but I think we should target what is decided here.The text was updated successfully, but these errors were encountered: