Summary
When the boat retracts a tile, handleCatalog's prune removes it from tiles_, the
disk cache, and the reconciler — but it does not touch the overview pyramid: the
retracted fine tile's data stays folded into its parent overviews (stale coarse
coverage), and its overviews/ GeoTIFF files are never deleted (slow disk growth).
Bounded in memory (overviews are display-grade + evictable per #160), but the stale
coverage + orphaned overviews/ files are a lifecycle gap.
Proposed
On catalog prune, either (a) mark the affected overview cells NoData and re-fold from
surviving children, or (b) accept stale coarse coverage but garbage-collect orphaned
overviews/ files (e.g. periodic sweep of overview tiles with no surviving fine
descendants). Decide (a) vs (b) during design.
Part of #160 (deferred follow-up recorded in ADR-0010 Consequences).
Authored-By: Claude Code Agent
Model: Claude Opus 4.8 (1M context)
Summary
When the boat retracts a tile,
handleCatalog's prune removes it fromtiles_, thedisk cache, and the reconciler — but it does not touch the overview pyramid: the
retracted fine tile's data stays folded into its parent overviews (stale coarse
coverage), and its
overviews/GeoTIFF files are never deleted (slow disk growth).Bounded in memory (overviews are display-grade + evictable per #160), but the stale
coverage + orphaned
overviews/files are a lifecycle gap.Proposed
On catalog prune, either (a) mark the affected overview cells NoData and re-fold from
surviving children, or (b) accept stale coarse coverage but garbage-collect orphaned
overviews/files (e.g. periodic sweep of overview tiles with no surviving finedescendants). Decide (a) vs (b) during design.
Part of #160 (deferred follow-up recorded in ADR-0010 Consequences).
Authored-By:
Claude Code AgentModel:
Claude Opus 4.8 (1M context)