ngff
ngff copied to clipboard
ome
Next-generation file format (NGFF) specifications for storing bioimaging data in the cloud.
In conversations elsewhere @sbesson [says](https://github.com/ome/ngff/pull/170#discussion_r1137471662): > At the moment, the specification enforces that such data must be stored within a well-defined labels hierarchy but moving forward, I could certainly imagine...
Following up on my last PR. Previously, we added a lot more explanation to the 'labels' section of the spec. Now I am not just editing the language, but making...
This PR updates RFC 1 in the following ways: * [x] Lists current reviewers and commenters * [x] Adds a legend for symbols like 🕑 and 📂 * [x] Adds...
@joshmoore Is there anything in the spec about the datatypes of the multiscales as in whether they can be all completely different or not? For example: is this OK? ```...
When going through the documentation I found that link to zenodo points to release 0.1 not the current one 0.4.1. As you do not have `zenodo.json` and do not provide...
In the [latest version of `axes` metadata](https://github.com/ome/ngff/blob/3ab738b3d68c3a579f636a234d29d768af83e09f/latest/index.bs#L192), we allow specifying both a type for an axis (e.g., "space", "time", "channel"), as well as a unit. It seems to me that...
I've been reading the [NetCDF Climate and Forecast metadata conventions](http://cfconventions.org/Data/cf-conventions/cf-conventions-1.8/cf-conventions.html) recently. I _highly_ recommend this document to anyone interested in what a mature, battle-tested metadata model for n-dimensional array data...
I am writing an image for which I wanted to include a dataset description (free text), a license, authorship, and author contributions. I expected that this would go in the...
The anatomical orientation of an array is a critical piece of metadata for downstream analysis, particularly for the increasingly common task of aligning acquired images to an atlas for anatomical...
For the various metadata objects with a `version` field, this PR makes explicit that `version` is a string, and that it must be the current version.