openEO

For the interTwin project a specific deployment has been composed that i) based on the available open-source components under the openEO’s GitHub repository and ii) allows the further integration of new component types into the workflows, based on the openEO process graphs. Those new types to be integrated are set up as the so-called application packages that are defined by the EOEPCA architecture and that are used in the OGC standard (e.g. as the OGC API processes). A first prototype has been developed integrating one specific processor in this way, based on the wflow hydrological model. Furthermore, parts of the use case on flood mapping based on the Global Flood Mapping algorithm, have also been ported to openEO (see Task 7.5). Initial OSCAR and openEO integration has started to trigger Application Package processing from openEO in the OSCAR cluster.

This first process can act as a template for other thematic modules, to be defined and set up the same way and then to be executed. Ideally, new components should also be developed to interact with the other core components (e.g. with the iTwinAI package; see Task 6.5) That could probably also fully be described in this way. Also, a connection to the OSCAR and DCNiOS event-driven triggering of workflows is foreseen, so that the event can trigger the execution of openEO process graphs. As a next step, a TOSCA template for this environment should be developed together with Task 6.4.