Skip to content

feat: globe coverage view renders v2 datasets. - #14

Merged
avsm merged 1 commit into
ucam-eo:mainfrom
adpeace:main
Jul 24, 2026
Merged

avsm merged 1 commit into
ucam-eo:mainfrom
adpeace:main

Conversation

@adpeace

@adpeace adpeace commented Jul 23, 2026

Copy link
Copy Markdown
Contributor

Re https://geotessera.org/coverage/:

The page assumed a single dataset and flat hierarchy but this has been updated in the core repo so that a dataset can have multiple variants. Support the updated format, rendering the first dataset if this format is found.

This was tested locally with coverage I generated using the geotessera CLI. However, I don't have access to a v1 dataset, so it's possible the fallback code doesn't work as intended.

There's another PR for geotessera incoming to switch the palette for the coverage texture to the one expected by this page when there's only a single variant: however that also required changing the globe viewer that the CLI emits to produce a correct legend for both single- and multiple-variant datasets. Not sure if that's how you want to handle it, but I will share the PR for your consideration.

AI usage declaration: Written with the assistance of Claude. Reviewed, updated, and approved by me. I'm hardly a typescript expert, though...

The page assumed a single dataset and flat hierarchy but this has been
updated in the core repo so that a dataset can have multiple variants.
Support the updated format, rendering the first dataset if this format
is found.
@adpeace
adpeace marked this pull request as ready for review July 23, 2026 21:23
@avsm

avsm commented Jul 24, 2026

Copy link
Copy Markdown
Contributor

Thanks Andy!

@avsm
avsm merged commit 0978309 into ucam-eo:main Jul 24, 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