@@ -65,9 +65,9 @@ parallelization.
6565
6666As a result, a number of formats have been developed more recently which provide
6767the basic data structure of an HDF5 file, but do so in a more cloud-friendly way.
68- In the [ PyData] ( https://pydata.org/ ) community, the Zarr (@ zarr ) format was developed
68+ In the [ PyData] ( https://pydata.org/ ) community, the Zarr ({cite : t } ` zarr ` ) format was developed
6969for easily storing collections of [ NumPy] ( https://numpy.org/ ) arrays. In the
70- [ ImageJ] ( https://imagej.net/ ) community, N5 (@ n5 ) was developed to work around
70+ [ ImageJ] ( https://imagej.net/ ) community, N5 ({cite : t } ` n5 ` ) was developed to work around
7171the limitations of HDF5 ("N5" was originally short for "Not-HDF5").
7272Both of these formats permit storing individual chunks of data either locally in
7373separate files or in cloud-based object stores as separate keys.
@@ -88,7 +88,7 @@ binary containers. Eventually, we hope, the moniker "next-generation" will no lo
8888applicable, and this will simply be the most efficient, common, and useful representation
8989of bioimaging data, whether during acquisition or sharing in the cloud.
9090
91- Note: The following text makes use of OME-Zarr (@ ome-zarr-py ), the current prototype implementation,
91+ Note: The following text makes use of OME-Zarr ({cite : t } ` ome-zarr-py ` ), the current prototype implementation,
9292for all examples.
9393
9494## On-disk (or in-cloud) layout
@@ -568,68 +568,3 @@ version of this diagram is available from the [OME2020 Workshop](https://downloa
568568Mouseover the blackboxes representing the implementations above to get a quick tip on how to use them.
569569
570570Note: If you would like to see your project listed, please open an issue or PR on the [ ome/ngff] ( https://github.com/ome/ngff ) repository.
571-
572- <pre class =" biblio " >
573- {
574- "blogNov2020": {
575- "href": "https://blog.openmicroscopy.org/file-formats/community/2020/11/04/zarr-data/",
576- "title": "Public OME-Zarr data (Nov. 2020)",
577- "authors": [
578- "OME Team"
579- ],
580- "status": "Informational",
581- "publisher": "OME",
582- "id": "blogNov2020",
583- "date": "04 November 2020"
584- },
585- "imagesc26952": {
586- "href": "https://forum.image.sc/t/ome-s-position-regarding-file-formats/26952",
587- "title": "OME’s position regarding file formats",
588- "authors": [
589- "OME Team"
590- ],
591- "status": "Informational",
592- "publisher": "OME",
593- "id": "imagesc26952",
594- "date": "19 June 2020"
595- },
596- "n5": {
597- "id": "n5",
598- "href": "https://github.com/saalfeldlab/n5/issues/62",
599- "title": "N5---a scalable Java API for hierarchies of chunked n-dimensional tensors and structured meta-data",
600- "status": "Informational",
601- "authors": [
602- "John A. Bogovic",
603- "Igor Pisarev",
604- "Philipp Hanslovsky",
605- "Neil Thistlethwaite",
606- "Stephan Saalfeld"
607- ],
608- "date": "2020"
609- },
610- "ome-zarr-py": {
611- "id": "ome-zarr-py",
612- "href": "https://doi.org/10.5281/zenodo.4113931",
613- "title": "ome-zarr-py: Experimental implementation of next-generation file format (NGFF) specifications for storing bioimaging data in the cloud.",
614- "status": "Informational",
615- "publisher": "Zenodo",
616- "authors": [
617- "OME",
618- "et al"
619- ],
620- "date": "06 October 2020"
621- },
622- "zarr": {
623- "id": "zarr",
624- "href": "https://doi.org/10.5281/zenodo.4069231",
625- "title": "Zarr: An implementation of chunked, compressed, N-dimensional arrays for Python.",
626- "status": "Informational",
627- "publisher": "Zenodo",
628- "authors": [
629- "Alistair Miles",
630- "et al"
631- ],
632- "date": "06 October 2020"
633- }
634- }
635- </pre >
0 commit comments