Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

propagation: overview of supported platforms #83

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

propagation: overview of supported platforms #83

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
25 changes: 22 additions & 3 deletions propagation/ondemandservices.qmd
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -49,6 +49,16 @@ For further guidance on creating and using UDPs, you can explore the following r
* [Jupyter notebook example](https://github.com/Open-EO/openeo-community-examples/blob/main/python/Sentinel1_Stats/Sentinel1_Stats.ipynb)
* [Official openEO specification](https://api.openeo.org/#tag/User-Defined-Processes)

#### Development and Testing Environments

While an openEO UDP can be developed on any supported environment using the
existing [openEO tools](https://openeo.org/documentation/1.0/), we recommend testing the UDP on an APEx-compliant
hosting platform. This ensures platform compatibility and facilitates the deployment of your UDP as an on-demand
service.

For a comprehensive overview of currently APEx-compliant hosting platforms, please refer
to [this section](#openeo-udp).

### Building an OGC Application Package based service

Another option is to package your software using Docker containers. This approach is very generic and is particularly
Expand All @@ -61,21 +71,30 @@ as a service.

[This tutorial](https://terradue.github.io/ogc-eo-application-package-hands-on/) explains more about this option.

#### Development and Testing Environments

To develop and test an OGC Application Package, you can use one of the following environments, which include the
necessary tools and basic infrastructure to support the development process:

* [ELLIP](https://ellip.terradue.com)
* APEx Instantiation Services
* [Workspace](../instantiation/user_workspace.md) and [IDE](../instantiation/ide.md)

### What are the platforms to choose from?

To offer your algorithm as an on-demand service, it must be available for execution on an APEx-compliant algorithm
hosting platform. Currently, APEx supports the integration of services on platforms that adhere to the
APEx [compliance guidelines](../interoperability/algohostingenv.md). It is important to note that this list of supported
platforms is expected to grow as APEx evolves.

For openEO UDPs:
#### openEO UDP

* [openEO platform](https://openeo.cloud)
* [CDSE openEO federation](https://dataspace.copernicus.eu)

For OGC Processes/Application Package:
#### OGC Processes/Application Package

* [ELLIP](https://ellip.terradue.com)
* [Geohazards TEP](https://geohazards-tep.eu/)

:::{.callout-tip}

Expand Down
Loading