Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

load_stac: avoid dependency on eo:bands #762

Open
jdries opened this issue Apr 24, 2024 · 2 comments
Open

load_stac: avoid dependency on eo:bands #762

jdries opened this issue Apr 24, 2024 · 2 comments
Assignees

Comments

@jdries
Copy link
Contributor

jdries commented Apr 24, 2024

When loading our own netcdf metadata, I get:
No band assets found in items; a band asset requires an "eo:bands" property with a "name".
While the use of the name in eo:bands is relevant, all stac assets also have a default name, because assets in STAC are represented by a dictionary.
Can we fall back to those names, if eo:bands is not present? I think that would make our load_stac less extension dependent.

@bossie
Copy link
Collaborator

bossie commented Apr 24, 2024

Yes, I've been considering this as a best-effort approach. The implicit assumption then is that those are single band assets.

@soxofaan
Copy link
Member

soxofaan commented Jun 3, 2024

Maybe worth mentioning that in the python client we're also started to collect functionality to parse band information from stac:

We might want to consolidate efforts here

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

No branches or pull requests

3 participants