-
Notifications
You must be signed in to change notification settings - Fork 11
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
Job Results: STAC Collections instead of (or in addition to) Items #343
Labels
breaking
Breaking changes, requires a major-version (2.0.0 for example)
job management
incl. /result
minor
requires a minor-version (x.1.0 for example)
platform
PSC vote
Milestone
Comments
m-mohr
added
breaking
Breaking changes, requires a major-version (2.0.0 for example)
job management
incl. /result
labels
Nov 4, 2020
This is something that probably needs to be done via openEO Platform. |
m-mohr
changed the title
Job Results: STAC Collections instead of Items
Job Results: STAC Collections instead of (or in addition to) Items
Feb 16, 2021
I'll draft a (somewhat) backward-compatible PR for this as this is getting important. The idea is to duplicate the assets into Collection Assets, for now, to have the assets available to all clients in a backward-compatible way. I'm checking the client implementations so that they rely on nothing else than assets. Result:
|
m-mohr
added a commit
that referenced
this issue
Feb 17, 2021
3 tasks
3 tasks
m-mohr
added a commit
that referenced
this issue
Apr 19, 2021
This was referenced May 11, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
breaking
Breaking changes, requires a major-version (2.0.0 for example)
job management
incl. /result
minor
requires a minor-version (x.1.0 for example)
platform
PSC vote
Due to the fact that Assets have only recently been added to STAC Collections, we currently return STAC Items in job results although it would likely make more sense to expose them as collections with optional items, depending on the data set that has been generated. Fortunately, the assets dict itself is fully compliant to Items.
The text was updated successfully, but these errors were encountered: