Issue81_bapCompositeUpdate

[tho-hole]

Updated the .json file of BAP_composite UPD to reflect changes made in Issue81 of OpenEO community_examples.

[tho-hole]

You can find a simple testcode and a UDP generator, based on the bap_composite example in a separate branch:
https://github.com/ESA-APEx/apex_algorithms/tree/Issue81_bapCompositeUpdate_testcodes/algorithm_catalog/vito/bap_composite/openeo_udp

[tho-hole]

Previous UDP could succesfully run with a negative cloud_cover (job j-2510011253474fdc9708ec23673f97f5).
I've added a min-max value checker on cloud_cover, which makes the process fail but only on the server side. I don't see a solution to stop the process before job submission.

[VincentVerelst]

Currently, I can't successfully run this new UDP. Digging deeper to find out why

[VincentVerelst]

vector_to_raster (part of the coverage score) fails on some spatiotemporal extents with

ProcessParameterInvalidException(status_code=400, code='ProcessParameterInvalid', message="The value passed for parameter 'data' in process 'vector_to_raster' is invalid: Support for input vector cubes without data is not supported.", id='no-request')

Like for example: cdse-j-251013161608436d9e07fda53fe1abc4

[VincentVerelst]

vector_to_raster (part of the coverage score) fails on some spatiotemporal extents with

ProcessParameterInvalidException(status_code=400, code='ProcessParameterInvalid', message="The value passed for parameter 'data' in process 'vector_to_raster' is invalid: Support for input vector cubes without data is not supported.", id='no-request')

Like for example: cdse-j-251013161608436d9e07fda53fe1abc4

Hmm, running the process graph from the latest community examples, instead of from the UDP on the same spatiotemporal extent does work: cdse-j-251014092055477a8c7737997dca13be

[VincentVerelst]

Aha, the geometries in aggregate_spatial aren't parametrized, but are a hard-coded FeatureCollection: https://github.com/ESA-APEx/apex_algorithms/blob/Issue81_bapCompositeUpdate/algorithm_catalog/vito/bap_composite/openeo_udp/bap_composite.json?short_path=30c1689#L23644-L23680

@tho-hole

[VincentVerelst]

Two things:

• The geometries in aggregate_spatial should be parametrized from the user input. Currently they are a hard-coded FeatureCollection, which will make the UDP fail for any other spatial_extent than this hard-coded FeatureCollection
• In the previous UDP the default max_cloud_cover was set to 75. Maybe we should keep that the same in this new UDP?

[algorithm-services-catalogue]

🧹 Catalogue's Preview Site Cleanup

The preview site for this pull request has been cleaned up.

If you need a new preview, please reopen the PR or create a new one.