-
Notifications
You must be signed in to change notification settings - Fork 198
[ENH] Add OME-Zarr as a supported format for imaging data #2392
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
base: master
Are you sure you want to change the base?
Changes from 4 commits
b03d776
ac3ecb2
95edd49
76f4397
875ee53
62fcb64
6f61c8a
2fe2e8e
d19dac2
c26e721
c3cd3f4
383df17
e76e757
827e536
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -480,8 +480,13 @@ field in `dataset_description.json` of each subdirectory of `derivatives` to: | |
|
|
||
| ### Imaging files | ||
|
|
||
| All imaging data MUST be stored using the NIfTI file format. We RECOMMEND using | ||
| compressed NIfTI files (.nii.gz), either version 1.0 or 2.0. If using compressed files, | ||
| Imaging data SHOULD be stored using the NIfTI file format. | ||
| Large imaging data MAY instead be stored using the | ||
| [OME-Zarr (OME-NGFF)](https://ngff.openmicroscopy.org/) file format. | ||
|
|
||
| #### NIfTI | ||
|
|
||
| We RECOMMEND using compressed NIfTI files (.nii.gz), either version 1.0 or 2.0. If using compressed files, | ||
| the gzip header SHOULD lack source filenames and timestamps. Imaging data SHOULD | ||
| be converted to the NIfTI format using a tool that provides as much of the NIfTI | ||
| header information (such as orientation and slice timing information) as | ||
|
|
@@ -501,6 +506,24 @@ The [BIDS-validator](https://github.com/bids-standard/bids-validator) | |
| will check for conflicts between the JSON file and the data recorded in the | ||
| NIfTI header. | ||
|
|
||
| #### OME-Zarr | ||
|
|
||
| [Zarr](https://zarr-specs.readthedocs.io/) is a chunked, cloud-optimized format that provides efficient access to | ||
| large multidimensional datasets without requiring a full download. | ||
| [OME-Zarr](https://ngff.openmicroscopy.org/), developed by the Open Microscopy Environment (OME), | ||
| extends Zarr with bioimaging-specific metadata. | ||
| OME-Zarr is particularly suitable for very large imaging volumes (for example, high-resolution | ||
| ex vivo MRI) where NIfTI would be impractical for streaming or web-based visualization. | ||
|
|
||
| OME-Zarr filesets are stored with the `.ome.zarr` extension. | ||
| Spatial metadata (such as the axis names and units, and coordinate transformations) SHOULD | ||
| be stored within the OME-Zarr metadata following the | ||
| [OME-Zarr version 0.5 specification](https://ngff.openmicroscopy.org/specifications/0.5/index.html) | ||
| (the latest released version). | ||
|
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I thought to scream "duplication is evil!" but apparently we do not really disclose much in microscopy section about OME or NGFF but then we should at least take an opportunity to point to this section here from within that microscopy.md section. attn @bids-standard/bep031
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Good idea. I have just pushed a commit. |
||
| Extended support for coordinate systems and transformations is described in | ||
| [RFC-5: Coordinate Systems and Transformations](https://ngff.openmicroscopy.org/rfc/5/index.html) | ||
| (draft, expected to be released as part of OME-Zarr version 0.6). | ||
|
kabilar marked this conversation as resolved.
Outdated
kabilar marked this conversation as resolved.
Outdated
|
||
|
|
||
| ### Tabular files | ||
|
|
||
| Tabular data MUST be saved as plain-text, tab-delimited values (TSV) files | ||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -7,6 +7,7 @@ func: | |
| extensions: | ||
| - .nii.gz | ||
| - .nii | ||
| - .ome.zarr/ | ||
| - .json | ||
| datatypes: | ||
| - func | ||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -6,6 +6,7 @@ asl: | |
| extensions: | ||
| - .nii.gz | ||
| - .nii | ||
| - .ome.zarr/ | ||
| - .json | ||
| datatypes: | ||
| - perf | ||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -5,6 +5,7 @@ pet: | |
| extensions: | ||
| - .nii.gz | ||
| - .nii | ||
| - .ome.zarr/ | ||
| - .json | ||
| datatypes: | ||
| - pet | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder if some schema-level check /could/should be added here based on some characteristics of the volume(s) -- e.g. any dimension having over 1k elements?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could: yes
Should: 🤷🏻
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks. I don't feel too strongly here, but if we do add a check let's use
level: warning.