-
Notifications
You must be signed in to change notification settings - Fork 38
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
Allow .
as the dimension separator
#135
Comments
Thanks for capturing this, @jstriebel. I can't remember if I mentioned to you or to Norman but for everyone: the hard requirement on a single separator was required while the (There have also been requests to support Zip-based NGFFs which will touch the same code paths.) |
We are happy to drive this. |
Then we're looking at different implementations which is a good realization itself 😄
|
I see. To me the directory listing seemed more like an example section than a normative section. |
Since v0.2,
/
is the only allowed dimension separator for OME NGFF chunk paths. To be compatible with Zarr arrays in general, it would be great to also allow.
as the dimension separator, depending on the Zarr metadata if available.This allows to add OME metadata to existing Zarr arrays, that already use the
.
dimension separator.The text was updated successfully, but these errors were encountered: