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

What is the minimum implementation required to be considered to be STAC API compliant? #42

Closed
philvarner opened this issue Sep 15, 2020 · 3 comments
Assignees
Milestone

Comments

@philvarner
Copy link
Collaborator

What is the minimum implementation required to be considered to be STAC API compliant? We don't state explicitly one way or the other. For example, implementing /search is optional.

@m-mohr
Copy link
Collaborator

m-mohr commented Sep 15, 2020

IMHO you should either implement OAFeat and return STAC compliant responses or have / and /search implemented.

@matthewhanson
Copy link
Collaborator

Agree it should implement OAFeat and meet all those requirements.
Then root catalog, collections, and items should all return valid STAC metadata.

Where should we add this?

@cholmes cholmes added this to the 1.0.0-beta.1 milestone Nov 2, 2020
@cholmes cholmes self-assigned this Nov 12, 2020
@m-mohr m-mohr linked a pull request Dec 1, 2020 that will close this issue
3 tasks
@m-mohr m-mohr removed a link to a pull request Dec 3, 2020
3 tasks
@m-mohr
Copy link
Collaborator

m-mohr commented Dec 4, 2020

This has been pretty much answered by #60 - you need to implement the landing page, all other is optional and you can figure out what is supported by the conformance classes published on the landing page.

@m-mohr m-mohr closed this as completed Dec 4, 2020
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

4 participants