feat(stac): eodash layerExclusive + style link for S2 L2A (#206)#278
Merged
Conversation
eodash renders sentinel-2-l2a both as server-side XYZ tiles and as a client-side GeoZarr (reflectance) layer, which visually overlap. Add collection-level metadata so the eodash Layer Control treats them as mutually exclusive and binds a style to the GeoZarr asset: - eodash:layerExclusive: true - a rel:"style" link to eodash-assets geozarr.json with asset:keys:["reflectance"] Applied to the prod and staging collection templates only (per issue thread: "NB only collections"). Adds tests/test_stac_collections.py covering the new fields plus adversarial checks that they don't leak into other collections. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
The staging-codecs collection variant was an experimental scale-offset-codec trial and is no longer used. Remove its collection template and update the obsolete example S3 paths in the codec checker docs to point at the live sentinel-2-l2a-staging path. Does not touch the experimental_scale_offset_codec feature or its tests (tests/unit/test_convert_v1_s2.py uses the name only as a config label). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Collaborator
Author
A-Behairi
approved these changes
Jun 23, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #206.
What & why
eodash renders
sentinel-2-l2aboth as server-side XYZ tiles and as a client-side GeoZarr (reflectance) layer, which currently overlap. This adds collection-level metadata so the eodash Layer Control treats them as mutually exclusive and binds a style to the GeoZarr asset.Changes
Commit A —
feat(stac)(prod + staging templates):eodash:layerExclusive: truerel:"style"link →eodash-assets/.../styles/geozarr.jsonwithasset:keys:["reflectance"](exact values from @A-Behairi's comment; URL verified 200)tests/test_stac_collections.py— validity, field presence, exactly-one style link bound to a realitem_asset, plus adversarial checks that the fields don't leak into other collectionsCommit B —
chore(stac): remove the obsoletesentinel-2-l2a-staging-codecscollection template and repoint stale example S3 paths in the codec checker docs. Leaves theexperimental_scale_offset_codecfeature/tests untouched.Verification
ruff format+ruff checkclean;mypycleanFollow-up ops (not in this PR)
Collection templates still need deploying to the live STAC API, and the live
sentinel-2-l2a-staging-codecscollection deleting — handled separately viamanage_collections.py.🤖 Generated with Claude Code