Repository navigation
Proposal: Define processing:expression with format: results - #44
Open
fmigneault wants to merge 4 commits into
Open
fmigneault wants to merge 4 commits into
fmigneault wants to merge 4 commits into
Conversation
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
If a
processing-expressionorprocessing-executionreference (eg: an openEO Process, OGC API Processes, gdal-calc etc.) produced results to be annotated in a STAC Collection/Item for provenance, but that those results contained a mixture of file references (easily integrated as Assets) and data literals (eg: a threshold value or a predicted datetime), theprocessingextension does not offer an explicit method to indicate the data values.If the values are simply placed in the Collection fields or Item properties, there is a risk to clash with actual fields that have semantic meaning for STAC (eg: predicted
datetimewill conflict with thedatetimeof STAC).Therefore, there should be a way to provide such values, since creating an Asset file for small literal data is not practical. One approach would be to leverage the
processing:expressionfree-form object. While this works, it makes it not reusable since anyone can come up with their own thing.This PR indicates this strategy clearly such that it insensitive reuse and guide against anti-patterns.