OME-NGFF
- Stage boundary
- No direct role is recorded for Plan, Exchange.
- Known limitation
- Pre-1.0 changes and transitional metadata remain; writer/viewer compatibility and round-trip preservation must be tested with the chosen toolchain.
Decision support
Compare standards by the job they do
Place up to three profiles side by side. Focus on architectural role, evidence, and the first limitation to test—not on finding a single all-purpose standard.
Working set
Choose profiles
1 of 3 selected
OME-NGFFData model / schema
Decision lens
Compare roles before you compare maturity.
The useful question is not “Which standard wins?” It is “Which job must this part of the architecture perform, and what remains uncovered?”
- Start with the job
Decide whether you need guidance, a domain payload, exchange, semantics, governance, or a reusable release.
- Map lifecycle reach
Use the matrix to see where each profile has a direct role. A filled cell is coverage, not a quality score.
- Test the boundary
Read what each option leaves unresolved before judging maturity, confidence, or implementation fit.
Three-part assessment
See the reach, the gaps, and the evidence.
Read left to right. Lifecycle reach comes first; maturity remains an editorial roll-up, not certification.
01 · Lifecycle reach
Where each profile contributes directly
Coverage shows a recorded role at that readiness stage. It does not imply end-to-end implementation.
| Profile | Plan | Acquire | Harmonize | Exchange | Learn + reuse |
|---|---|---|---|---|---|
| OME-NGFFData model / schema | OME-Zarr / OME-NGFF has no direct role recorded in Plan. | OME-Zarr / OME-NGFF has a direct role in Acquire. | OME-Zarr / OME-NGFF has a direct role in Harmonize. | OME-Zarr / OME-NGFF has no direct role recorded in Exchange. | OME-Zarr / OME-NGFF has a direct role in Learn + reuse. |
Direct role recordedNo direct role recorded
02 · Boundaries
What each option does not cover
These are design boundaries, not faults. Use them to identify the companion layers your architecture still needs.
03 · Detailed assessment
Check the fit and evidence behind the map
Use the source, status, and limitation together. A higher maturity label does not erase a scope mismatch.
| Assessment | OME-NGFFOME-Zarr / OME-NGFF |
|---|---|
| Purpose & coverage | Cloud/object-store bioimaging data in Zarr v3 with axes, multiscales, transforms, labels, and high-content-screening plates. Best fitLarge multidimensional microscopy, high-content screening, multiscale visualization, and cloud-native image analysis. |
| Readiness stages | AcquireHarmonizeLearn + reuse |
| AI-ready contribution | Chunked multiscale arrays and label images are ML-friendly, but biological labels, QC, sampling, and train/test leakage remain project responsibilities. |
| First limitation to test | Pre-1.0 changes and transitional metadata remain; writer/viewer compatibility and round-trip preservation must be tested with the chosen toolchain. |
| Evidence | E1 + E3 High confidence Formal statusFinal Community Group Report · pre-1.0 ReviewSource-checked · watch |
| Maturity | Scaling Final Community Report; pre-1.0 ecosystem |
| Sources & links | OME-NGFF 0.5 specification (opens in a new tab)Read full profile |