Skip to content

docs(spec): require overlap coherence for d8_raster.v1 entries#3

Merged
CooperBigFoot merged 1 commit into
mainfrom
docs/d8-overlap-coherence
Jun 18, 2026
Merged

docs(spec): require overlap coherence for d8_raster.v1 entries#3
CooperBigFoot merged 1 commit into
mainfrom
docs/d8-overlap-coherence

Conversation

@CooperBigFoot

Copy link
Copy Markdown
Owner

Adds a normative Overlap Coherence section to spec/aux/d8_raster/v1.md: overlapping multi-entry D8 declarations MUST carry identical flow_dir/flow_acc in the overlap (windows of one coherent fabric), so consumers MAY pick any covering entry. No wire-shape change; format_version stays 0.2.1. Unblocks the shed manifest-first D8 selection fix.

Multi-entry hfx.aux.d8_raster.v1 datasets partition one source D8 fabric per
basin, but irregular basins do not tile into disjoint rectangles, so entries'
axis-aligned extents overlap. The spec did not say what values overlapping
entries must carry in the overlap, leaving consumer tile-selection
underspecified when more than one entry fully covers a region.

Add a normative Overlap Coherence section: overlapping entries MUST report
identical flow_dir/flow_acc at each shared cell (they MUST be windows of a
single coherent fabric, not independently mosaicked); a producer that cannot
guarantee this MUST NOT declare overlapping entries. Consumers MAY then pick
any covering entry (e.g. manifest-first), choice-independent. No wire-shape
change; format_version stays 0.2.1. Changelog entry added.
@CooperBigFoot CooperBigFoot merged commit 9860ab4 into main Jun 18, 2026
4 checks passed
@CooperBigFoot CooperBigFoot deleted the docs/d8-overlap-coherence branch June 18, 2026 12:28
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