# OME-Zarr applications for geoscience?

**URL:** <https://discourse.pangeo.io/t/ome-zarr-applications-for-geoscience/4078>\
**Category:** Data\
**Created:** [March 5, 2024, 7:41pm UTC](https://discourse.pangeo.io/t/ome-zarr-applications-for-geoscience/4078 "2024-03-05T19:41:24Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![JessicaS11](https://yyz2.discourse-cdn.com/flex030/user_avatar/discourse.pangeo.io/jessicas11/32/229_2.png) [@JessicaS11](https://discourse.pangeo.io/u/JessicaS11)\
**Post date:** [March 5, 2024, 7:41pm UTC](https://discourse.pangeo.io/t/ome-zarr-applications-for-geoscience/4078/1 "2024-03-05T19:41:24Z")

</div>

Is anyone here familiar with [OME-Zarr](https://link.springer.com/article/10.1007/s00418-023-02209-1) (or OME-tiff)? I came across the linked article (sorry if it was from someone here!) and the basic premise of needing formatted data + metadata in a data storage format struck me as analogous to many geospatial data workflow challenges. Are these potentially relevant data standards to consider, or are they not-quite-right for many of our use cases?

---

<div class="post-metadata">

**Author:** ![maxrjones](https://yyz2.discourse-cdn.com/flex030/user_avatar/discourse.pangeo.io/maxrjones/32/3190_2.png) [@maxrjones](https://discourse.pangeo.io/u/maxrjones)\
**Post date:** [March 20, 2024, 3:15pm UTC](https://discourse.pangeo.io/t/ome-zarr-applications-for-geoscience/4078/2 "2024-03-20T15:15:04Z")

</div>

Hi Jessica, I think there are definitely lessons to be learned from the success of OME-Zarr. There are also enough unique aspects of geospatial data (e.g., projection information) to motivate a separate metadata convention for the geospatial community. This is a primary motivation of the [GeoZarr specification](https://github.com/zarr-developers/geozarr-spec).