Closed kempenep closed 4 years ago
I did not work yet with using properties with load_collection, so I'm not sure. Hopefully @claxn can help?
@kempenep Sorry for the late reply. There are two things:
"from_parameter": "value"
is replaced by "from_node": "dc_6"
was reverted now, because this was based on non-general assumptions of node relationships (see https://github.com/Open-EO/openeo-pg-parser-python/pull/29). Now taking the correct node and its data as input needs to be solved by the back-end, but still can be done easily with the functions the pg parser provides."x"
refers to, basically it is a placeholder for all values contained in "eo:cloud_cover"
, which is an attribute of the collection (@m-mohr is this right?). The parser will simply tell you that there are 2 nodes "dc_6"
and "cc_8"
linked via two edges "dc_6" <-"process"- "cc_8"
and "dc_6" -"data"-> "cc_8"
.Does this answer your question? If yes, please close this issue, thanks!
Yeah, correct. You basically run the generated "process" on all values and the one's that succeed will be loaded...
I was wondering how to deal with the following situation. When filtering collections based on properties like cloud cover, we can add the following within the node for
load_collection
The
between
process_id is then parsed with the x argument set tofrom_node
pointing to load_collection:How we can know from this parsed node to which property of
dc_6
thisx
is referring to? There might as well be another property that we wanted to filter, or do I miss something here?