Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Propose resolution _groups_ for xarray support #114

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Commits on Apr 21, 2022

  1. Propose resolution _groups_ for xarray support (see ome#48)

    In discussing with the xarray community, the one change to the NGFF
    specification that needs to occur to prevent errors being raised
    when opening a multiscale is for each resolution _array_ to live
    in a separate _group_. This has already been tested by thewtex
    in https://github.com/spatial-image/spatial-image-multiscale and
    the current spec is permissive enough to allow it. The proposal
    here would enforce the subdirectories moving forward.
    
    The conflict in xarray stems from the fact that each of our
    subresolutions have the same dimension names ("x", "y,", etc.)
    but different sizes. This is not allowed in the xarray (nor NetCDF)
    model. An added benefit of this change is that other arrays with
    the same resolution levels and the same dimensions (e.g. labels!)
    could be stored together:
    
    ```
        ├── resolution-N/.zgroup
        │   ├── image/.zarray
        │   └── labe/.zarray
    ```
    joshmoore committed Apr 21, 2022
    Configuration menu
    Copy the full SHA
    38ab95d View commit details
    Browse the repository at this point in the history