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

Add clarification around collection-level assets in item-assets. #880

Merged
merged 3 commits into from
Aug 19, 2020

Conversation

lossyrob
Copy link
Collaborator

@lossyrob lossyrob commented Aug 19, 2020

This PR adds language to the item-assets spec to clarify that collection-level asset objects should not contain properties that are not explicitly stated in the item's asset objects themselves.

This comes out of a discussion during STAC Sprint 6. It was determined that while allowing for asset properties to be defined in only the collection-level asset objects was a way to save space, it would be more in line with the spec to have items explicitly contain all asset property information.

If you're currently using the item-assets extension to consolidate item-level asset object properties in an API setting, consider storing the STAC items without those consolidated properties internally as 'invalid' STAC items, and merge in the desired collection-level asset object properties at serving time.

PR Checklist:

  • This PR is made against the dev branch (all proposed changes except releases should be against dev, not master).
  • This PR has no breaking changes.
  • I have added my changes to the CHANGELOG or a CHANGELOG entry is not required.
  • This PR affects the STAC API spec, and I have opened issue/PR #XXX to track the change.

Co-authored-by: Matthias Mohr <webmaster@mamo-net.de>
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

Successfully merging this pull request may close these issues.

3 participants