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

Use item assets from the base collection when available #4

Open
gjoseph92 opened this issue Mar 13, 2021 · 0 comments
Open

Use item assets from the base collection when available #4

gjoseph92 opened this issue Mar 13, 2021 · 0 comments

Comments

@gjoseph92
Copy link
Owner

The item assets STAC extension allows collections to describe which assets might be available, and give some metadata common to all instances of those assets—for example, ["eo:bands"]["common_name"]. When this extension is present, if a field is missing on an individual asset, you're supposed to fall back on the field as defined on the item_assets of the parent collection.

This would be particularly handy with #3. Some collections (like Sentinel-2 on AWS) don't provide eo:bands on individual items, just at the collection level, so we're missing some metadata right now.

This is easy to implement; the most annoying part is just handling the "get the parent collection" part across satstac vs pystac vs a plain dict.

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

1 participant