Christophe Noel (Spacebel)

@christophenoel @emmanuelmathot @mdsumner @rabernat Defining a single profile to cover all kinds of rasters and datacubes is difficult. These datasets can include many different combinations—such as time, height, or wavelength—and...

Note: regarding the "meta model" spec approach, see the PR: https://github.com/zarr-developers/geozarr-spec/pull/64

The latest Editor's Draft version of OGC GeoZarr Specificationis found here in [HTML](https://zarr.dev/geozarr-spec/documents/standard/template/geozarr-spec.html) or [PDF](https://zarr.dev/geozarr-spec/documents/standard/template/geozarr-spec.pdf)

Closing as stale. No recent activity and likely no longer relevant. Can be reopened if needed.

Hi @maxrjones There is actually no major difference. What is proposed as a “harmonisation” of NetCDF, CF, and GeoTIFF is, in essence, a meta-model—precisely a translation of existing standards for...

> * GeoZarr does not need to define compatibility across conformance classes From my point of view, _conformance classes_ is just an optional bonus for identifying specific constructs (could also...

I conducted a brief initial review. At this stage, the objective of this PR is not entirely clear to me. It appears to be a reformulation of the CF conventions....

Closing as stale. No recent activity and likely no longer relevant. Can be reopened if needed.

I agree that the current model of overviews described in [clause 7 – unified data model](https://github.com/zarr-developers/geozarr-spec/blob/main/standard/template/sections/clause_7_unified_data_model.adoc) and [clause 9 – Zarr encoding overviews](https://github.com/zarr-developers/geozarr-spec/blob/main/standard/template/sections/clause_9_zarr_encoding_overviews.adoc) is not yet fully clear or complete....

Indeed. I have illustrated in my review: [PR #86](https://github.com/zarr-developers/geozarr-spec/pull/86)