Search results

Clarify spatial:bbox semantics when crossing the antimeridian

Status: Open.

#36 In zarr-conventions/spatial;

· kylebarron opened on Jun 9, 2026

How should non-spatial coordinates be handled ?

Status: Open.

#33 In zarr-conventions/spatial;

· christophenoel opened on May 28, 2026

RFC: single-source rule for spatial: properties (resolves #6, #8, #12, #23)

Status: Open.

#32 In zarr-conventions/spatial;

· wietzesuijker opened on May 20, 2026

make spatial:dimensions an **Array only** properties

needs discussion

Status: Open.

#23 In zarr-conventions/spatial;

· vincentsarago opened on May 13, 2026

Transform order should be the same as in GDAL

documentationImprovements or additions to documentationImprovements or additions to documentation

Status: Open.

#20 In zarr-conventions/spatial;

· felixcremer opened on Apr 23, 2026

spatial:registration

Status: Open.

#19 In zarr-conventions/spatial;

· pvanlaake opened on Apr 14, 2026

Clarify text around transform origin being top-left corner

Status: Open.

#13 In zarr-conventions/spatial;

· kylebarron opened on Apr 7, 2026

Ambiguous usage of spatial:transform in conjunction with multiscales convention

Status: Open.

#12 In zarr-conventions/spatial;

· kylebarron opened on Apr 6, 2026

Have explicit "Inheritance Model" paragraph

Status: Open.

#8 In zarr-conventions/spatial;

· rouault opened on Jan 21, 2026

Address potential floating point mismatch between transform and bbox

Status: Open.

#6 In zarr-conventions/spatial;

· maxrjones opened on Dec 11, 2025

SUGGESTION: consider specs for non projected datasets with GCPs

Status: Open.

#5 In zarr-conventions/spatial;

· Scartography opened on Oct 16, 2025