Skip to content

Add language how to combine (standalone) collections with extensions #344

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

Closed
m-mohr opened this issue Nov 7, 2018 · 2 comments
Closed
Assignees
Milestone

Comments

@m-mohr
Copy link
Collaborator

m-mohr commented Nov 7, 2018

For implementors that are using STAC to just describe collections and (often) no items, e.g. GEE and openEO, there is currently not enough language in the spec where fields such as those from the eo extension are placed. These extensions are scoped for items, but nevertheless they are useful for collections, too. There is the Commons Extension, but I think it is really difficult to understand for novice users that you can extend the collections with the commons extension to use the eo extension. I think there should be a better/more prominent description about this in the STAC Collection specification.

@m-mohr
Copy link
Collaborator Author

m-mohr commented Apr 29, 2019

Added some sentences to #422. This describes how GEE and openEO use collections at the moment and is nothing new in that sense. This is probably a temporary solution until we discuss property summaries (#413) and item schemas for 0.8.0.

@m-mohr
Copy link
Collaborator Author

m-mohr commented Apr 29, 2019

Done.

@m-mohr m-mohr closed this as completed Apr 29, 2019
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