Skip to content

Scene overlay: render only the datacube tile of the time series - #8

Merged
vudongpham merged 1 commit into
mainfrom
claude/magical-archimedes-27hvz5
Nov 6, 2026
Merged

vudongpham merged 1 commit into
mainfrom
claude/magical-archimedes-27hvz5

Conversation

@vudongpham

Copy link
Copy Markdown
Owner

Summary

Before this change, the scene overlay was built from the scene's files in every datacube tile in view. Now it is rendered only from the tile of the extracted time series, and neighbouring tiles stay transparent.

  • The browser passes the tile of the last "View time series" run to /overlay/{z}/{x}/{y}.png as ?tile=X####_Y####.
  • The server reads only <level2>/<tile>/<scene>. It rejects a tile name that is invalid or missing, and a scene that is not in that tile, with 400.
  • The multi-tile mosaicking code (cube_tiles, MAX_CUBE_TILES) is removed.

Testing

  • python -m pytest -q: 27 passed.
  • New test: the tile and its neighbour, which holds the same scene, never draw over each other in a shared web tile.
  • Checked in a browser on a synthetic 2×2-tile datacube: only the outlined tile is rendered.

Generated by Claude Code

The overlay used to be put together from the scene's files in all
datacube tiles in view. It now reads only the file in the tile of the
extracted time series (passed as ?tile=), so neighbouring tiles stay
transparent.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01HUYE7j4AsWg97tWfRBT7mu
@vudongpham
vudongpham merged commit a7b178a into main Nov 6, 2026
2 checks passed
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.

2 participants