← Back to the vault

Lab Note · updated 2026-06-20

Data Standards and Scalable Storage

The OME data model and OME-NGFF/OME-Zarr exist because a microscopy image without a shared data model and a chunked, cloud-native layout is neither interpretable nor analyzable at scale. Format is not plumbing — it decides whether a petabyte dataset can be opened at all.

IngestMetadataLight-Sheet 3D/4DDigital PathologySpatial OmicsCell PaintingOME-NGFFOME-ZarrBio-FormatsOMEROMoBIEBigStitcher
← Back to constellation

The problem — A microscopy file is two things at once: pixels and the model that explains them. Strip away the data model — what the channels are, the physical pixel size, the dimension order, the acquisition settings — and the pixels become uninterpretable, comparable to no other dataset, and unsafe to feed a pipeline that assumes a layout. At scale a second failure appears: a single light-sheet or whole-slide acquisition can exceed what fits in RAM or downloads in a day, so a monolithic TIFF cannot even be opened, let alone analyzed. Standards and storage layout are not housekeeping; they decide whether the data is usable.

What it is / how it works — Two coupled standards answer the two failures. The OME data model (Linkert et al.) is a common schema for image structure and acquisition metadata, surfaced through Bio-Formats' readers for 150-plus proprietary formats and stored in systems like OMERO — the layer that distinguishes provenance metadata (how an image was made) from quality metadata (how good it is), as the microscopy metadata perspective frames it. OME-NGFF / OME-Zarr (Moore et al.) answers scale: the array is split into a multiscale pyramid of independently addressable chunks, so a viewer or pipeline reads only the region and resolution it needs, directly from object storage, without materializing the whole volume. Chunking is the mechanism behind lazy, cloud-native access — and behind tools like MoBIE and BigStitcher that explore terabyte datasets on a laptop.

Where it breaks — The general failure is treating format as cosmetic: the data model and chunk layout silently dictate what downstream analysis is even possible, and the cost is paid late. In light-sheet a poorly chunked volume forces whole-plane reads, so deconvolution and stitching thrash on I/O instead of compute. In digital pathology a whole-slide pyramid with the wrong tile size makes tile extraction for a foundation model an order of magnitude slower, or loses the physical scale a model assumes. In spatial omics a registration step that drops the OME coordinate metadata misaligns transcripts against cells. In Cell Painting a five-channel plate exported without canonical channel identities becomes uncomparable across sites, the JUMP-scale reuse defeated before analysis starts. The through-line: choose the data model and chunking at ingest, because they are load-bearing for everything that follows — including making data reanalysis-ready.

The format is part of the experiment. A correct data model and a sane chunk layout decided at ingest are cheaper than re-converting a petabyte after the pipeline is written.

References

References

Local graph