Declare the EO extension on collections that use eo:bands - #382
Merged
Merged
Conversation
sentinel-2-l2a, naip, planet-nicfi-analytic, planet-nicfi-visual and goes-cmi describe their bands with eo:bands in summaries and item_assets but do not list the EO extension in stac_extensions. Validators therefore skip those fields, and tools that key on the declared extension (for example, band-aware formula defaults) ignore the band metadata. Declare EO v1.1.0, the version most templates here already use. All five pass 'pctasks dataset validate-collection'.
Collaborator
|
Looks good, please go ahead and run the |
DerekTan1
marked this pull request as ready for review
September 29, 2026 15:10
fws-nwi: fws_nwi:state and fws_nwi:state_code summaries hls2-l30: scientific extension hls2-s30: scientific extension and sci:doi nasa-nex-gddp-cmip6: cmip6:model summary sentinel-3-synergy-syn-l2-netcdf: eo:bands summary
Gustavo Hidalgo (ghidalgo3)
approved these changes
Sep 29, 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.
Description
Five collection templates describe their bands with
eo:bands(insummariesand/oritem_assets) but do not list the EO extension instac_extensions:sentinel-2-l2a(datasets/sentinel-2)naipplanet-nicfi-analyticplanet-nicfi-visualgoes-cmiWithout the declaration, STAC validators skip those fields, and tools that key on the declared extension ignore the band metadata. For example, Microsoft Planetary Computer Pro GeoCatalogs only seed built-in band-index formulas (NDVI, NDWI, ...) for collections that declare EO, so mirrored copies of these collections get none today.
This adds
https://stac-extensions.github.io/eo/v1.1.0/schema.json, the EO version most templates in this repo already use (10 on v1.1.0, 7 on v1.0.0). Each change is a one-line addition tostac_extensions; no other fields change.aster-l1thas the same gap but is deliberately not included: its bands use common names outside the EO vocabulary (swir,near infrared,yellow/green), so declaring the extension would make it fail validation. Fixing those names is a separate data change.Type of change
How Has This Been Tested?
pctasks dataset validate-collection <template>passes for all five updated templates.aster-l1twith the extension added ('swir' is not one of [...]), confirming the validator checks the EO schema rather than passing everything.jsonschema.Checklist: