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

Implement OME-NGFF metadata conversion according to RFC 2 #5

Open
sbesson opened this issue Aug 26, 2024 · 0 comments · May be fixed by #7
Open

Implement OME-NGFF metadata conversion according to RFC 2 #5

sbesson opened this issue Aug 26, 2024 · 0 comments · May be fixed by #7
Assignees

Comments

@sbesson
Copy link
Member

sbesson commented Aug 26, 2024

The current converter code deals exclusively with the transformation of the data from the Zarr v2 from/to the Zarr v3 without modifying the content of the custom group/array attributes.

As per RFC-2, any metadata following the OME-NGFF specification should be transformed as follows:

  • the top-level keys (plate, multiscales,...) should be migrated under an ome key
  • the version key should be moved under ome

When converting from Zarr v3 to Zarr v2, the attributes should be converted to match the OME-NGFF 0.4 specification.

@sbesson sbesson self-assigned this Aug 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants
@sbesson and others