Skip to content

Update to interoperability guidelines #180

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

Merged
JanssenBrm merged 3 commits into from
Feb 23, 2026
Merged

Update to interoperability guidelines #180

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
dec3651
fix(#179): updated docs
JanssenBrm Jan 5, 2026
7ffa8b2
Merge branch 'main' into standards_update
JanssenBrm Feb 23, 2026
c98f2fa
Merge branch 'main' into standards_update
JanssenBrm Feb 23, 2026
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
8 changes: 6 additions & 2 deletions interoperability/algohostingenv.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -53,10 +53,14 @@ their compatibility with the APEx standards.
<li>At least processes profiles L1-minimal [@openeo_processes_profiles]</li>
</ul>
</li>
<li>OGC API Processes [@apiprocess], supporting the deployment of applications defined by the OGC Best Practice for Earth Observation Application Package [@ap]</li>
<li>OGC API Processes [@apiprocess]</li>
</ul>
</td>
<td>The support for the proposed technologies ensures that APEx-compliant algorithms can be hosted on the algorithm hosting platform and made available as on-demand services.</td>
<td>
<p>The support for the proposed technologies ensures that APEx-compliant algorithms can be hosted on the algorithm hosting platform and made available as on-demand services.</p>
<p>For the OGC API Processes option, APEx recommends following the deployment of applications defined by the OGC Best Practice for Earth Observation Application Package [@ap]. However, it is important to note that APEx only mandates the exposure of an OGC API Processes endpoint. This approach allows for flexibility in choosing the most suitable technology, provided that the platform adheres to the OGC API Processes requirement.
</p>
</td>
</tr>
<tr>
<td>HOST-REQ-04</td>
Expand Down
32 changes: 19 additions & 13 deletions propagation/platforms.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,18 +10,30 @@ process of APEx-compliant services.
Throughout the project, APEx aims to expand this list of compliant platforms, offering users the flexibility to choose
their preferred platform.

## openEO User Defined Processes
## openEO API

An openEO UDP can be developed in any openEO-based environment using existing [openEO tools](https://openeo.org/documentation/1.0/).
APEx can support development activities by providing projects with access to its [Code Server and JupyterLab IDE solutions](../instantiation/index.md).
For testing the UDP, we recommend utilising an APEx-compliant hosting platform.
This ensures platform compatibility and facilitates the deployment of your UDP as an on-demand service. Currently, APEx
as identified the following platforms as compliant with the APEx guidelines:
Algorithms can be offered as services through the openEO API. This API standard enables the execution of processing
workflows on various back-end platforms. The following platforms are currently identified as APEx-compliant for hosting
openEO-based algorithms:

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

## OGC Earth Observation Application Package (EOAP) processes
### openEO User Defined Processes

An openEO UDP can be developed in any openEO-based environment using existing [openEO tools](https://openeo.org/documentation/1.0/).
APEx can support development activities by providing projects with access to its [Code Server and JupyterLab IDE solutions](../instantiation/index.md).
For testing the UDP, we recommend utilising an APEx-compliant hosting platform, as provided in the list above.
This ensures platform compatibility and facilitates the deployment of your UDP as an on-demand service.

## OGC API - Processes

To offer your algorithm as an on-demand processing service, exposed via an OGC API - Processes standard interface,
the following platforms are compliant with the APEx guidelines:

* [Geohazards TEP](https://geohazards-tep.eu/) using [EO Application Package](#ogc-earth-observation-application-package-eoap-processes)

### OGC Earth Observation Application Package (EOAP) processes

To develop and test an OGC Earth Observation Application Package, you can use one of the following environments,
which include the necessary tools and basic infrastructure to support the development process:
Expand All @@ -30,12 +42,6 @@ which include the necessary tools and basic infrastructure to support the develo
* [APEx Code Server IDE](../instantiation/app_code_server.md)
* [APEx JupyterLab IDE](../instantiation/app_jupyterlab.md)

### OGC API - Processes

To offer your algorithm as an on-demand processing service, exposed via an "OGC API - Processes" standard interface, the following platforms are compliant with the APEx guidelines:

* [Geohazards TEP](https://geohazards-tep.eu/)

:::{.callout-tip}

## Is Your Platform APEx-Compliant?
Expand Down