Replies: 4 comments 9 replies
-
Some quick comments: the initial graph is invalid I think: {
"apply1": {
"arguments": {
"data": {"from_node": "load1"},
"dimension": "t",
"process": {
"process_graph": {
"max1": {
"arguments": {"data": {"from_parameter": "data"}},
"process_id": "max",
"result": true
}
}
}
},
"process_id": "apply_dimension"
} apply_dimensions expects a process that takes an array as input and produces again an array. Here the output (of In the new process graph I also see "array1": {
"process_id": "array_create",
"arguments": {
"data": [
{"from_node": "min1" },
{"from_node": "max1" },
{"from_node": "sd1" },
... |
Beta Was this translation helpful? Give feedback.
-
And, if I understand correctly, the |
Beta Was this translation helpful? Give feedback.
-
FYI, instead of flatten_dimension, in our other online example we still set target='bands' in apply_dimension If that isn't correct, we should flag it as such. |
Beta Was this translation helpful? Give feedback.
-
So is there a recommended implementation for temporal metrics as discussed above? Should we follow the VITO example above? That one works, but for capacity building purposes I don't find it very intuitive or "opene-ophonic".. |
Beta Was this translation helpful? Give feedback.
-
I stumbled across a user-defined process (see the "Original" UDP below) that computes S1 SAR metrics:
I found that it looks overly difficult and verbose. I was wondering whether there's a simpler (and probably more performant) way to achieve this in openEO. I think there is:
See the "New" UDP below. It should lead to exactly the same results. The only issue that I see is that in the underlying back-end (openEO Platform via VITO) the
flatten_dimension
process is missing (and you may want to rename the target dimension frommetrics
tobands
to get exactly the same result).Anyone has any thoughts? @soxofaan
Original
New
Beta Was this translation helpful? Give feedback.
All reactions