Skip to content

feat(rust/sedona-raster-zarr): derive Zarr transform from spatial:bbox#975

Draft
james-willis wants to merge 1 commit into
apache:mainfrom
james-willis:jw/zarr-bbox-transform
Draft

feat(rust/sedona-raster-zarr): derive Zarr transform from spatial:bbox#975
james-willis wants to merge 1 commit into
apache:mainfrom
james-willis:jw/zarr-bbox-transform

Conversation

@james-willis

Copy link
Copy Markdown
Contributor

No description provided.

@github-actions github-actions Bot requested a review from paleolimbot June 17, 2026 23:28
@james-willis james-willis force-pushed the jw/zarr-bbox-transform branch 2 times, most recently from eb8071d to 068099c Compare June 18, 2026 21:59
When a group has no explicit spatial:transform, derive a GDAL-order geotransform
from spatial:bbox plus the array's own spatial shape (+ optional
spatial:registration, default "pixel").

The derivation lives in the loader's transform-fallback chain, ahead of the
coordinate-array path, so it uses the array shape already in hand rather than a
separate, drift-prone spatial:shape attribute (bbox alone is sufficient).
geozarr.rs stays a pure attribute decoder that surfaces the bbox and
registration; the loader applies them.

A malformed or degenerate/inverted bbox is non-fatal: it warns and falls through
to the coordinate arrays (then identity), matching how a bad coordinate array is
handled. When the bbox path derives a transform and the group declares no CRS, a
geographic CRS is inferred from the spatial dim names, mirroring the
coordinate-array path.
@james-willis james-willis force-pushed the jw/zarr-bbox-transform branch from 068099c to 35ac003 Compare June 18, 2026 22:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant