As a developer I need tiling grid splitting on openEO service side

[HansVRP]

@mbuchhorn @brunosmets this is currently blocked untill we organize an in depth meeting with the core team.

[brunosmets]

See https://jira.vito.be/browse/NCAP-1678

[jdries]

I can't access the jira issue, but important to mention that we now have multiple variants available:

• APEx 'upscaling servcie' is considering to build a web UI that splits the AOI and submits multiple jobs
• When working with a message bus + NiFi (as proposed by BC3), NiFI could also to the splitting via job manager
• The openEO aggregator has a built-in 'partitioned-jobs' feature.

That last feature is relevant, but it currently has the problem that it depends on regular polling of job status, because it needs a valid bearer token.

[HansVRP]

SO this would be directly related to: Open-EO/openeo-python-client#745

Where we include job splitters to the job manager?

[mbuchhorn]

personally all solutions with the jon_manager are too sketchy ... the job_manger is still error prone and needs restarts etc....
so that will become a more complex NiFi workflow to do checks if all files are there and restart lost rows from the job_manager......

I personally prefer the solution with the openEO aggregator has a built-in 'partitioned-jobs' feature.

[HansVRP]

The following ticket is picked up by the DE team (vincent): Open-EO/openeo-python-client#745

We will introduce UTM based splitting in the job manager as a utility function.

[mbuchhorn]

@HansVRP that is not was this ticket is about. the client side splitting with optimised UTM grid we introduced in the WEED jobmanager already long time ago. We really talk about the "server side" splitting which is done by an openEO aggregator.

@DeRooBert is assigned to do the tests on our side. @brunosmets maybe we have to clarify this ticket again and tell why we need that in more detail.

[HansVRP]

I'll check out the aggregator solution and see if it is applicable for your use-case

[HansVRP]

aggregator has been tested for WEED usecase, to be reviewed with @DeRooBert

[brunosmets]

I reopen the ticket as it is not reviewed by Bert (as far as the log shows) & assign to @DeRooBert

[DeRooBert]

I checked it but want to discuss the limitations next week with Marcel.