ngff icon indicating copy to clipboard operation
ngff copied to clipboard

Next-generation file format (NGFF) specifications for storing bioimaging data in the cloud.

Results 115 ngff issues
Sort by recently updated
recently updated
newest added

Started to look again at #71 View page at https://github.com/will-moore/ngff/blob/ngff_tools_table/ngff-tools.md Aims of this table/documentation: - Allow data producers and consumers to know whether a particular feature is supported in their...

Fixes #2 I think it is important to include this change rather soon. Right now data with different dtypes across the dimensions is technically valid according to the spec, but...

`json-schema` for coordinate transforms proposal #138. This branch is based off the spec PR. The spec was only modified to move inline examples to the `examples` directory. All other changes...

This PR has four main contributions: * The [existing axis specification](https://ngff.openmicroscopy.org/latest/#axes-md) into `coordinateSystem`s - named collections of axes. * `coordinateTransformations` now have "input" and "output" coordinate systems. * Adds many...

Every example for `multiscales` that I know of orders the objects in the `datasets` arrays from largest to smallest arrays (highest to lowest resolution). Are there any use cases in...

The links for rendered versions of the PRs haven't been working for me for at least the last week. Does anyone know what's up with this? I'm also wondering if...

I understand that the name OME-NGFF was a great choice for rallying the community around a new standardized, chunked, cloud-native image format. However, it is quite unspecific and will not...

There are many use cases in v0.4 spec and in PRs that need to reference zarr arrays or groups: * [`multiscales` reference their child arrays](https://github.com/ome/ngff/blob/main/0.4/index.bs#L364) * [`image-label`s reference source images](https://github.com/ome/ngff/blob/main/0.4/index.bs#L485-L486)...

The ["axes" metadata](https://ngff.openmicroscopy.org/latest/#axes-md) currently contains a "name" that is typically `{ "x", "y", "z", "c", "t' }`. We could also add support for an optional "long_name" to the "axes" metadata....