Client: Support for multiple result nodes

follow up of Open-EO/openeo-processes#401

python client needs some kind of support for building process graphs with multiple result nodes

It looks like we can create a valid process graph from multiple datacubes, as long as we use the same flattener.

    week = s2cube.aggregate_temporal_period(period="week",reducer="median")
    month = s2cube.aggregate_temporal_period(period="month",reducer="median")

    cube1=week.save_result("netCDF")
    cube2 = month.save_result("netCDF")

    from openeo.internal.graph_building import GraphFlattener
    flattener = GraphFlattener()
    dict1 = flattener.flatten(cube1.result_node())

    #only one node can be marked as 'result':True, so set all others to False
    for v in dict1.values():
        v["result"] = False

    secondary_result = cube2.result_node()

    #by reusing the flattener, the previously flattened nodes are also included
    dict2 = flattener.flatten(secondary_result)

    final_graph = {"process_graph":dict2}
    import json
    merged = json.dumps(final_graph, indent=2)
    print(merged)

    connection = openeo.connect("openeo.dataspace.copernicus.eu")
    connection.create_job(final_graph,title="job with 2 save results")

so way forward is either updating create_job or a variant of that method that accepts multiple datacubes?

or
cube.execute_batch(args..., extra_cubes=[extra_cube1])
or
connection.execute_batch([cube1,cube2]), other args...)

In the python client we already have a base class _ProcessGraphAbstraction, which is further implemented by DataCube, VectorCube, MlModel. So I was thinking along the lines of creating another subclass of that, say ProcessGraph or MultiResult, which you can pass one or more cubes and work with that. E.g.

results = MultiResult([cube_as_tiff, cube_as_netcdf, vector_cube])

results.execute_batch(...)

(all naming up for discussion of course)

Improve auto-adding of save_result (#623, #401, #583, #391)

fixup! Improve auto-adding of save_result (#623, #401, #583, #391)

fixup! fixup! Improve auto-adding of save_result (#623, #401, #583, #391

PR #630 better "weak" format handling in `execute_batch` (#623, #401, #…

PR #630 improve save_result handling in VectorCube too (#623, #401, #583

Improve auto-adding of save_result (#623, #401, #583, #391)

PR #630 better "weak" format handling in `execute_batch` (#623, #401, #…

Issue #391 support shared PGNodes better in MultiResult

Issue #391 avoid multiple "result" modes with MultiResult flattening

Issue #391/#651 add docs, changelog, review tweaks

fixup! Issue #391/#651 add docs, changelog, review tweaks

Issue #391/#651 review tweaks

fixup! Issue #391/#651 review tweaks

Issue #391 Initial implementation of MultiResult

Issue #391 support shared PGNodes better in MultiResult

Issue #391 avoid multiple "result" modes with MultiResult flattening

Issue #391/#651 add docs, changelog, review tweaks

Issue #391/#651 more review tweaks

ready to merge:

Add support for multiple result node #651

just waiting for quick review if possible

Issue #391/#651 import MultiResult in toplevel openeo package

merged #651

Navigation Menu

Repository navigation

Client: Support for multiple result nodes #391

7 remaining items

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Client: Support for multiple result nodes #391

Description

Activity

jdries commented on Aug 14, 2024

jdries commented on Aug 14, 2024

soxofaan commented on Aug 19, 2024

7 remaining items

soxofaan commented on Nov 5, 2024

soxofaan commented on Nov 6, 2024

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions