Fix STAC band parsing for cube dimensions - #103
Merged
Conversation
Backends publish band info in different STAC shapes. The EOPF explorer backend uses summaries.bands (rich per-band objects), but other openEO backends (e.g. openeo.ds.io) only expose bands via the datacube extension's cube:dimensions - a "bands"-type dimension with a bare list of band-name strings (e.g. "B04_20m"). extractBandsFromStac only checked summaries.bands, so the configuration tab showed "The parser could not find suitable bands" for any collection using the latter shape, even though the data was there. Confirmed against the live collection at https://openeo.ds.io/collections/sentinel-2-l2a, which has no summaries.bands but does have a bands-type cube:dimensions entry.
Contributor
Author
|
@danielfdsilva this is important to have this fix for the V1 |
danielfdsilva
approved these changes
Aug 25, 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.
Backends publish band info in different STAC shapes. The EOPF explorer backend uses summaries.bands (rich per-band objects), but other openEO backends (e.g. openeo.ds.io) only expose bands via the datacube extension's cube:dimensions - a "bands"-type dimension with a bare list of band-name strings (e.g. "B04_20m"). extractBandsFromStac only checked summaries.bands, so the configuration tab showed "The parser could not find suitable bands" for any collection using the latter shape, even though the data was there.
Confirmed against the live collection at https://openeo.ds.io/collections/sentinel-2-l2a, which has no summaries.bands but does have a bands-type cube:dimensions entry.