Repository navigation
Processing Parameters and Asset Roles - #46
fmigneault wants to merge 6 commits into
Conversation
gadomski
left a comment
There was a problem hiding this comment.
Thanks, this makes more sense to me, but there's a few bits that I find confusing ... I might not be the target audience for these changes, though.
| | ------------------ | ------ | ----------- | ------- | | ||
| | `gdal-calc` | string | A [`gdal_calc.py`](https://gdal.org/programs/gdal_calc.html) expression based on numpy syntax. | `A*logical_or(A<=177,A>=185)` | | ||
| | `openeo` | object | An [openEO process](https://openeo.org/documentation/1.0/developers/api/reference.html#section/Processes) | [Example](https://raw.githubusercontent.com/Open-EO/openeo-processes/1.2.0/normalized_difference.json) | | ||
| | `ogcapi-processes` | object | An [OGC ProcessDescription](https://docs.ogc.org/is/18-062r2/18-062r2.html#ogc_process_description) | [Example](https://schemas.opengis.net/ogcapi/processes/part1/1.0/examples/json/ProcessDescription.json) | |
There was a problem hiding this comment.
This change (adding ogcapi-processes) might be easier to review in its own PR, since it's technically independent of processing parameters.
| > [!NOTE] | ||
| > To ensure portability, `format` may employ a specific profile URI from a registered naming authority | ||
| > that explicitly describes the represented `expression` without ambiguity. | ||
|
|
There was a problem hiding this comment.
I'm not familiar with a "profile URI" — it could be helpful to link out to an explanation to help the reader understand how to use a profile?
| | processing-input | An Asset that represents an individual input (e.g., a configuration file required by the processing expression). Note that an input STAC object should instead use the `derived_from` link [relation type](#relation-types). | | ||
| | processing-parameters | An Asset that embeds the entire processing parametrization contents that were submitted. This is similar to [Parameters](#parameters) but is not limited to `application/json` and can contain much more data. | |
There was a problem hiding this comment.
I don't intuitively understand the different between the input and the parameters? In programming terms, aren't they both "function arguments"?
| | processing-output | An Asset that represents an invidivudal output (possibily amongst multiple) that was generated by the processing expression. These Assets should typically include `data` role as well, although not strictly required. | | ||
| | processing-results | An Asset that embeds the entire processing results contents generated by the processing expression (e.g., an _OGC API - Processes_ [Results](https://schemas.opengis.net/ogcapi/processes/part1/1.0/examples/json/Result.json) document. | |
There was a problem hiding this comment.
Similarly, what's the different between an "output" and a "result"? Aren't these both akin to "the return value of the function"?
Note
As discussed at the STAC Community Meeting 2026-10-19, and as replacement of:
processing:expressionwithformat: results#44Changes
parametersfield underprocessing:expressionto provide a mapping of named input values employed.processing-input,processing-output,processing-parametersandprocessing-results.profilein Asset using the above roles and examples for common applications.