diff --git a/_quarto.yml b/_quarto.yml index be470f6..7c49203 100644 --- a/_quarto.yml +++ b/_quarto.yml @@ -82,7 +82,7 @@ website: text: Ingesting STAC metadata in APEx Product Catalogue - href: guides/catalog_openeo.ipynb text: Linking APEx Product Catalogue with an openEO service - - section: APEx Algorithm Services Catalogue + - section: APEx Algorithm Catalogue contents: - href: guides/algorithm_services_catalogue.qmd - href: guides/algorithm_services_catalogue_benchmarks.qmd diff --git a/eo_service_usage/openeo_usage.md b/eo_service_usage/openeo_usage.md index 47176f3..a66f842 100644 --- a/eo_service_usage/openeo_usage.md +++ b/eo_service_usage/openeo_usage.md @@ -2,28 +2,34 @@ title: openEO based services --- -Context: use of APEx services that expose the [openEO](https://openeo.org/) interface standard, when implemented as openEO processes. +Context: use of APEx services that expose the [openEO](https://openeo.org/) interface standard, when implemented as openEO +processes. +In general, services can be executed through the tools that are provided by the APEx supported platforms ("processing platforms" +hereafter). +For OpenEO based services, this is supported by an online user interface, web editor, Client Libraries (JavaScript, Python, +R) and API. -In general, services can be executed through the tools that are provided by the APEx supported platforms ("processing platforms" hereafter). -For OpenEO based services, this is supported by an online user interface, web editor, Client Libraries (JavaScript, Python, R) and API. +There are several ways to discover how a service can be executed. When publishing a service on the +[APEx Algorithm Catalogue](../guides/algorithm_services_catalogue.qmd), a service provider can choose to provide the +following information in the service details: -There are several ways to discover how a service can be executed. When publishing a service on the APEx Algorithm Services Catalogue, a service provider can choose to provide the following information in the service details: - -* An executable link which redirects the user to the user interface of the processing platform. If this is the case, an **Access app** button will appear when opening an EOplaza service. +* An executable link which redirects the user to the user interface of the processing platform. If this is the case, an +**Access app** button will appear when opening an EOplaza service. * Sample code in the service description on how to execute a service. ## openEO backends An APEx openEO service is always associated with one or more openEO backends that have been validated to produce the correct results. So using one of these backends is the recommended approach. Thanks to openEO interoperability and standardization, -it may certainly be possible that other backends can run the same service, but do make sure to validate the results in that case. +it may certainly be possible that other backends can run the same service, but do make sure to validate the results in +that case. To ensure a smooth experience, backends need to be compliant with [APEx guidelines](../interoperability/algohostingenv.md). The currently known list of compliant backends is: -- [CDSE openEO federation](https://openeofed.dataspace.copernicus.eu) -- [openEO platform](https://openeo.cloud) +* [CDSE openEO federation](https://openeofed.dataspace.copernicus.eu) +* [openEO platform](https://openeo.cloud) Both are federations, which means that they in fact are backed by multiple openEO instances. This increases the convenience for the APEx user, avoiding to interact with a high number of backends. @@ -31,7 +37,8 @@ for the APEx user, avoiding to interact with a high number of backends. ## Online user interface OpenEO provides an online user interface where users can execute services directly in a web browser. -Through the graphical user interface, users can execute, link, and configure different services. More information on the usage of the online applications is presented in the table below. +Through the graphical user interface, users can execute, link, and configure different services. More information on the +usage of the online applications is presented in the table below. | OpenEO | |----------------------------------------------------------------------------| @@ -40,15 +47,18 @@ Through the graphical user interface, users can execute, link, and configure dif | [Documentation](https://openeo.org/documentation/1.0/#introduction) | ::: {.callout-tip} + ## Pro-tip: discovering API requests This interface provides a great way to find out how to interact with an openEO backend at the level of the HTTP API. -Just use the 'developer tools' of your favourite browser and inspect HTTP requests to the backend to find out the various options. +Just use the 'developer tools' of your favourite browser and inspect HTTP requests to the backend to find out the various +options. ::: ## Client libraries -OpenEO provides client libraries to support the creation and execution of JavaScript, Python and R services. The full client libraries documentation is available on the official OpenEO support pages: +OpenEO provides client libraries to support the creation and execution of JavaScript, Python and R services. The full +client libraries documentation is available on the official OpenEO support pages: * [JavaScript](https://openeo.org/documentation/1.0/javascript/) * [Python](https://openeo.org/documentation/1.0/python/) @@ -104,7 +114,8 @@ taskmap_job = taskmap.save_result(format='GTiff').send_job() taskmap_job.start_and_wait().get_results() ``` -To execute a service from the APEx through one of the OpenEO client libraries, it is important to use the *datacube_from_process* function. +To execute a service from the APEx through one of the OpenEO client libraries, it is important to use the +*datacube_from_process* function. This accepts the ID and namespace of the service. Both are made available in the service description on the EOplaza. The full documentation on using the function is available on the official [OpenEO documentation](https://open-eo.github.io/openeo-python-client/datacube_construction.html#datacube-from-process). @@ -114,11 +125,12 @@ Examples are available in the [OpenEO GitHub repository](https://github.com/Open ## API -OpenEO provides a fully documented API for a more advanced way to integrate features in any existing application or workflow. The API can also be used to execute EOPlaza services. The documentation is available at: +OpenEO provides a fully documented API for a more advanced way to integrate features in any existing application or workflow. +The API can also be used to execute EOPlaza services. The documentation is available at: | OpenEO | |---| -| https://openeo.org/documentation/1.0/developers/api/reference.html | +| | The following example showcases how to use the OpenEO API to execute a synchronous request for the BioPAR service: diff --git a/guides/eoap_writer_guide.md b/guides/eoap_writer_guide.md index c8f78fe..3e1846b 100644 --- a/guides/eoap_writer_guide.md +++ b/guides/eoap_writer_guide.md @@ -23,7 +23,7 @@ Note that all the guidance material provided hereafter has APEx in mind, but can Observation applications. All APEx recommendations are made to support the FAIR principles, ensuring that your service can be easily shared within a broader community. These guidelines also facilitate the integration of your service into -the [APEx Algorithm Services Catalogue](../propagation/onboarding.md#apex-algorithm-services-catalogue). +the [APEx Algorithm Catalogue](../propagation/onboarding.md#apex-algorithm-catalogue). For best practice illustrations and examples, on how to package Earth Observation applications, the **EOAP Guide** is published here:\ diff --git a/guides/udp_writer_guide.qmd b/guides/udp_writer_guide.qmd index 5f82700..83d9fca 100644 --- a/guides/udp_writer_guide.qmd +++ b/guides/udp_writer_guide.qmd @@ -43,7 +43,7 @@ graph. They can: Keep in mind that APEx offers [Algorithm Porting](../propagation/porting.md) and [Algorithm Onboarding](../propagation/onboarding.md) support to help you with transforming your algorithm into an openEO UDP, onboarding it onto an [APEx-compliant hosting platform](../propagation/platforms.md), registering it in the -[APEx Algorithm Services Catalogue](../propagation/onboarding.md#apex-algorithm-services-catalogue) and its onboarding onto +[APEx Algorithm Catalogue](../propagation/onboarding.md#apex-algorithm-catalogue) and its onboarding onto the [ESA Network of Resources](https://portfolio.nor-discover.org/). ::: @@ -53,7 +53,7 @@ User defined processes (UDPs) are one out of two standardised options that APEx service. This guide gives some concrete steps and guidelines to ensure that your UDP works well for your users. These guidelines are written with APEx in mind, but can also serve as a general guide for openEO UDPs. Where needed, recommendations and choices are made to increase uniformity across -the[APEx Algorithm Services Catalogue](../propagation/onboarding.md#apex-algorithm-services-catalogue). +the[APEx Algorithm Catalogue](../propagation/onboarding.md#apex-algorithm-catalogue). For more background on UDP's, or a basic tutorial on creating them, the open source Python client provides [a good starting point](https://open-eo.github.io/openeo-python-client/udp.html). @@ -110,7 +110,7 @@ a limited set of parameters, and write a single UDP for each piece. This section provides some recommendations on how to name parameters in your UDP. While these are not mandatory, we recommend to consider them to avoid that users of the -APEx [Algorithm Services Catalogue](https://algorithm-catalogue.apex.esa.int/) would be confused by variations in +APEx [Algorithm Catalogue](https://algorithm-catalogue.apex.esa.int/) would be confused by variations in process parameter names. Please [let us know](https://github.com/ESA-APEx/apex_documentation/issues) if you encounter a parameter that could use diff --git a/html/apex-navigation.html b/html/apex-navigation.html index 62773bb..fb6eb8f 100644 --- a/html/apex-navigation.html +++ b/html/apex-navigation.html @@ -7,11 +7,11 @@
- \ No newline at end of file + diff --git a/index.qmd b/index.qmd index 96c8f57..a1d9ef8 100644 --- a/index.qmd +++ b/index.qmd @@ -16,7 +16,7 @@ and capabilities that APEx provides to different stakeholders. * **Curated list of EO services**\ APEx curates a catalogue of earth observation services in - its [APEx Algorithm Services Catalogue](propagation/onboarding.md#apex-algorithm-catalogue), that generate value-added + its [APEx Algorithm Catalogue](propagation/onboarding.md#apex-algorithm-catalogue), that generate value-added products on demand. These services can include capabilities such as deforestation, floods or generate higher level information. These services are built and maintained by various EO projects, which guarantees that they have gone through an extensive review and validation process. Additionally, advanced APEx tooling continuously monitors these diff --git a/interoperability/definitions.qmd b/interoperability/definitions.qmd index 3a61596..f6a78c1 100644 --- a/interoperability/definitions.qmd +++ b/interoperability/definitions.qmd @@ -55,9 +55,9 @@ information on its parameters, expected output, scientific method, and an overvi within the algorithm. Examples of algorithm definitions include openEO’s User Defined Processes (UDP) [@udp] and OGC Application Package [@ap], using the Common Workflow Language (CWL) [@cwl]. -### Algorithm Services Catalogue +### Algorithm Catalogue -The [APEx Algorithm Services Catalogue](https://algorithm-catalogue.apex.esa.int/) is a central register of algorithm +The [APEx Algorithm Catalogue](https://algorithm-catalogue.apex.esa.int/) is a central register of algorithm definitions and the corresponding algorithm service instances that can be executed on APEx-compliant algorithm hosting platforms. Curated by APEx, the catalogue relies on automated checks to ensure that advertised algorithms service instances are available and functional. Whenever a malfunction is detected, this is reported to ESA and the EO project @@ -106,7 +106,7 @@ comply with APEx [Interoperability and Compliance Guidelines](../interoperabilit required, the consortium can utilise various services offered by APEx. Specifically, the [APEx Algorithm Support](../propagation/index.qmd) aims tosupport the enhancement of algorithms on a technical and software level and facilitate the transition to hosted algorithms that can be included in the -[APEx Algorithm Services Catalogue](https://algorithm-catalogue.apex.esa.int/). +[APEx Algorithm Catalogue](https://algorithm-catalogue.apex.esa.int/). ESA EO projects that do not have an explicit compliance requirement are also eligible to receive support. The APEx support can boost project impact, so projects are encouraged to inquire with their ESA technical officer about the @@ -149,7 +149,7 @@ these tools will retrieve EO algorithm results via web service APIs based on op further processed as needed, depending on the application. Note that these applications are not necessarily EO-centric or even geospatial, but could be using an EO algorithm as a small part or in the background. -The [APEx Algorithm Services Catalogue](https://algorithm-catalogue.apex.esa.int/) acts as a discovery tool for last mile +The [APEx Algorithm Catalogue](https://algorithm-catalogue.apex.esa.int/) acts as a discovery tool for last mile application builders. It shows various technical parameters, the cost and potential limitations for specific use cases. This speeds up the discovery and selection process. Application builders will be required to create an account on the hosting platforms and ensure the necessary funds are available, if they want to test or use the API. diff --git a/markdown-link-checker-config.json b/markdown-link-checker-config.json index 03c4532..ff47e07 100644 --- a/markdown-link-checker-config.json +++ b/markdown-link-checker-config.json @@ -15,6 +15,9 @@ { "pattern": "^https://eoepca.org" }, + { + "pattern": "https://data.esa.int/esado" + }, { "pattern": "^@" } diff --git a/propagation/enhancement.md b/propagation/enhancement.md index 60f04eb..b26cdf4 100644 --- a/propagation/enhancement.md +++ b/propagation/enhancement.md @@ -40,7 +40,7 @@ The algorithm enhancement activities offer the following features: * Exploitation of algorithms available on APEx where appropriate, e.g., replacing custom functions with equivalent pre-optimized functions. * Delivery of an enhanced implementation that is ready to be registered in the -[APEx Algorithm Services Catalogue](./onboarding.md#apex-algorithm-services-catalogue). +[APEx Algorithm Catalogue](./onboarding.md#apex-algorithm-catalogue). ### How to get started? diff --git a/propagation/index.qmd b/propagation/index.qmd index 52e6dce..acbcc94 100644 --- a/propagation/index.qmd +++ b/propagation/index.qmd @@ -7,7 +7,7 @@ scalable, cloud-based on-demand services. Currently, ESA EOP R&D projects genera example, EO-derived value-added products (raster or vector files, typically level-3 and level-4), workflows and algorithms, or conventional (open-source) desktop software solutions. The APEx Algorithm Support focusses on transforming and optimising (i.e., propagating) resulting algorithms, applications, workflows and toolboxes and ensuring -their compliance with FAIR data principles. The preservation of these project outcomes is managed through the +their compliance with FAIR data principles. The preservation of these project outcomes is managed through the [ESA Project Results Repository (PRR)](https://eoresults.esa.int/), supported by other APEx services, such as the [APEx Data Catalogue](https://browser.apex.esa.int/?.language=en). @@ -31,7 +31,7 @@ case-by-case basis. The APEx Algorithm Support comprises: * [Refactoring](./porting.md) source code to an openEO process graph * [Packaging](./porting.md) of source code to an OGC Application Package -* [Integration](./onboarding.md) of a service into the [APEx Algorithm Services Catalogue](./onboarding.md#apex-algorithm-services-catalogue) +* [Integration](./onboarding.md) of a service into the [APEx Algorithm Catalogue](./onboarding.md#apex-algorithm-catalogue) * [Cloudification](./toolboxcloud.md) of desktop toolboxes through a tailored approach * Technical performance [optimisation](./enhancement.md), both on the source code or service level * [Deployment and hosting](./onboarding.md) of a service in an existing EO platform diff --git a/propagation/onboarding.md b/propagation/onboarding.md index b6aca96..5320ca2 100644 --- a/propagation/onboarding.md +++ b/propagation/onboarding.md @@ -7,7 +7,7 @@ algorithms remain accessible to the EO community beyond the project’s completi and promote the use of algorithms developed during ESA projects, ensuring their longevity and continued utilisation, but also ensures alignment with the FAIR and open science data principles. This is achieved through the implementation of APEx [Interoperability and Compliance Guidelines](../interoperability/index.md) and by registering the onboarded -services in the [APEx Algorithm Services Catalogue](#apex-algorithm-services-catalogue) for broader visibility and +services in the [APEx Algorithm Catalogue](#apex-algorithm-catalogue) for broader visibility and accessibility. For the engagement with stakeholders of the algorithm, APEx collaborates closely with initiatives such as @@ -22,8 +22,8 @@ of the project and can include one or more of the following components: * **[Algorithm Hosting Platform Onboarding](#hosting-platform-onboarding-support)**\ Assistance in selecting and onboarding the algorithm to an [APEx-compliant hosting platform](./platforms.md), ensuring that the algorithm is available for execution as an on-demand service. -* **[APEx Algorithm Services Catalogue Integration](#apex-algorithm-services-catalogue)**\ - Guidance on how to integrate the hosted algorithm into the [APEx Algorithm Services Catalogue](https://algorithm-catalogue.apex.esa.int/), +* **[APEx Algorithm Catalogue Integration](#apex-algorithm-catalogue)**\ + Guidance on how to integrate the hosted algorithm into the [APEx Algorithm Catalogue](https://algorithm-catalogue.apex.esa.int/), making it discoverable and accessible to the EO community. * **[Automated Testing and Benchmarking](#automated-testing-and-benchmarking)**\ Provision of automated testing and benchmarking services to ensure the algorithm remains functional and accessible over @@ -35,22 +35,22 @@ APEx can help to identify the different hosting environments that the project ca the chosen APEx-compliant standard (openEO or OGC API Processes) or the availability of specific datasets and processing capabilities that are required by the algorithm. If applicable, APEx can also assist in the hosting environment onboarding process, ensuring that your algorithm is available for execution on the selected platform and ready for -further integration into the APEx [Algorithm Services Catalogue](#apex-algorithm-services-catalogue). +further integration into the APEx [Algorithm Catalogue](#apex-algorithm-catalogue). :::{.callout-tip} A full list of the known APEx-compliant algorithm hosting platforms is -available [here](./platforms.md). +available on [Platforms](./platforms.md) page. ::: -### APEx Algorithm Services Catalogue +### APEx Algorithm Catalogue Through comprehensive guidelines and documentation, projects can seamlessly integrate their hosted services in the -APEx [Algorithm Services Catalogue](https://algorithm-catalogue.apex.esa.int/). This process facilitates easy browsing +APEx [Algorithm Catalogue](https://algorithm-catalogue.apex.esa.int/). This process facilitates easy browsing and access to available algorithms, fostering collaboration and innovation within the EO community. -![APEx Algorithm Services Catalogue](images/catalogue.png) +![APEx Algorithm Catalogue](images/catalogue.png) -The APEx [Algorithm Services Catalogue](https://algorithm-catalogue.apex.esa.int/) allows visitors to discover and +The APEx [Algorithm Catalogue](https://algorithm-catalogue.apex.esa.int/) allows visitors to discover and select algorithms for subsequent execution on the corresponding APEx-compliant hosting environment. ::: {.callout-note title="Disclaimer"} @@ -59,7 +59,7 @@ corresponding cloud resources. Users wishing to execute an algorithm will need a platform or make a request through [ESA's Network of Resources (NoR)](https://portfolio.nor-discover.org/). ::: -Stay tuned for more detailed instructions on how to execute an algorithm through the APEx Algorithm Services Catalogue. +Stay tuned for more detailed instructions on how to execute an algorithm through the APEx Algorithm Catalogue. ### Automated Testing and Benchmarking @@ -113,25 +113,25 @@ users will still need to have access to the necessary processing resources on th ### Large-scale Data Processing -Once the algorithm has been integrated into the APEx [Algorithm Services Catalogue](#apex-algorithm-services-catalogue), +Once the algorithm has been integrated into the APEx [Algorithm Catalogue](#apex-algorithm-catalogue), users can leverage it for large-scale data processing. For such activities, APEx offers additional support for [algorithm upscaling](upscaling.md). -## Onboard Your Algorithm on the [APEx Algorithm Services Catalogue](#apex-algorithm-services-catalogue) +## Onboard Your Algorithm on the [APEx Algorithm Catalogue](#apex-algorithm-catalogue) -Onboarding your algorithm to the APEx Algorithm Services Catalogue is a straightforward process. Follow these +Onboarding your algorithm to the APEx Algorithm Catalogue is a straightforward process. Follow these steps to get started: 1. **Host Your Algorithm**: Ensure your algorithm is hosted on an [APEx-compliant platform](./platforms.md). If you need assistance in selecting a suitable platform, refer to the [Hosting Platform Onboarding Support](#hosting-platform-onboarding-support) section. 2. **Prepare Your Algorithm Record**: Create a detailed record of your algorithm service, including its functionalities, -input/output specifications, and any relevant metadata. This record should adhere to the guidelines provided in the -[APEx Algorithm Services Catalogue](https://esa-apex.github.io/apex_algorithms/catalogue.html). +input/output specifications, and any relevant metadata. This record should adhere to the guidelines provided in our +[guide](../guides/algorithm_services_catalogue.qmd) 3. **Submit a Pull Request**: To officially onboard your algorithm service, submit a pull request (PR) to the [APEx Algorithms GitHub Repository](https://github.com/ESA-APEx/apex_algorithms). 4. **Review and Approval**: The APEx team will review your submission. If everything is in order, your algorithm service will be approved and added to the catalogue. 5. **Catalogue Integration**: Once approved, your algorithm service will be listed in the -[APEx Algorithm Services Catalogue](https://algorithm-catalogue.apex.esa.int/), making it accessible to +[APEx Algorithm Catalogue](https://algorithm-catalogue.apex.esa.int/), making it accessible to the EO community. diff --git a/propagation/ondemandservices.qmd b/propagation/ondemandservices.qmd index 84199dd..07da2a9 100644 --- a/propagation/ondemandservices.qmd +++ b/propagation/ondemandservices.qmd @@ -42,7 +42,7 @@ graph. [This notebook](https://documentation.dataspace.copernicus.eu/notebook-sa exactly how to do that. After your UDP is created, it can be registered in -the [APEx Algorithm Services Catalogue](../propagation/onboarding.md#apex-algorithm-services-catalogue) and associated +the [APEx Algorith Catalogue](../propagation/onboarding.md#apex-algorithm-catalogue) and associated with one or more backends or platforms capable of running it. As APEx continues to evolve, additional tools will become available that aid this process, including functionality to check if your service is still functional. @@ -76,7 +76,7 @@ Package (EOAP) [@ap]. APEx can provide the guidance and support you need to effi EOAP implementation. After your EOAP is created, it can be registered in -the [APEx Algorithm Services Catalogue](../propagation/onboarding.md#apex-algorithm-services-catalogue) and associated +the [APEx Algorithm Catalogue](../propagation/onboarding.md#apex-algorithm-catalogue) and associated with one or more backends or platforms capable of running it. As APEx continues to evolve, additional tools will become available that aid this process, including functionality to check if your service remains in operational state, when it has been deployed onto an APEx-compliant algorithm hosting platform. @@ -138,7 +138,7 @@ following Algorithm Support: as openEO User Defined Processes (UDP) or OGC Application Packages. * **[Algorithm Onboarding](onboarding.md)**\ Explore how APEx can assist in deploying your algorithms within an APEx-compatible hosting platform and sharing - them across the EO community through the [APEx Algorithm Services Catalogue](./onboarding.md#apex-algorithm-services-catalogue). + them across the EO community through the [APEx Algorithm Catalogue](./onboarding.md#apex-algorithm-catalogue). * **[Algorithm Upscaling](upscaling.md)**\ Learn how APEx facilitates and simplifies the execution of algorithms at scale. * **[Algorithm Enhancement](enhancement.md)**\ diff --git a/propagation/porting.md b/propagation/porting.md index 4a596a7..3540668 100644 --- a/propagation/porting.md +++ b/propagation/porting.md @@ -56,7 +56,7 @@ practices ensure that EO applications are reproducible and portable across diver Once your algorithm has been successfully ported into APEx-compliant technology, the next step is to make it accessible to a broader audience. This involves onboarding it onto an APEx-compliant hosting platform, offering it as an on-demand -service, and publishing it in the [APEx Algorithm Services Catalogue](./onboarding.md#apex-algorithm-services-catalogue). +service, and publishing it in the [APEx Algorithm Catalogue](./onboarding.md#apex-algorithm-catalogue). By being part of the APEx ecosystem, your algorithm can be reused and scaled by other users and projects, significantly increasing its visibility and impact. This approach helps to maximize the value of your work, fostering collaboration and diff --git a/propagation/upscaling.md b/propagation/upscaling.md index d8d7a4d..2ad62d7 100644 --- a/propagation/upscaling.md +++ b/propagation/upscaling.md @@ -7,7 +7,7 @@ from one algorithm to the other (spatial, temporal, track-based, etc…). As a start, APEx will aim at facilitating the execution of an openEO UDP or OGC application package-based algorithm over larger geographic areas. To support these operations, APEx requires that the algorithm is already optimised for cost-effective -scalability, deployed as a service, and registered in the [APEx Algorithm Services Catalogue](./onboarding.md#apex-algorithm-services-catalogue). +scalability, deployed as a service, and registered in the [APEx Algorithm Catalogue](./onboarding.md#apex-algorithm-catalogue). If needed, APEx can provide additional support to ensure these prerequisites are met. To execute large-scale data processing activities, APEx provides a range of services (from guidance to liaison with Platform @@ -100,7 +100,7 @@ To make use of the upscaling tools, the following aspects should be considered b * The upscaling activities and tools are designed with APEx [guidelines](../interoperability/index.md) in mind, primarily supporting algorithms that have been onboarded to the - APEx [Algorithm Services Catalogue](onboarding.md#apex-algorithm-services-catalogue). While users are able to utilise + APEx [Algorithm Catalogue](onboarding.md#apex-algorithm-catalogue). While users are able to utilise these tools for other algorithms, their proper functionality cannot be guaranteed if the algorithms do not adhere to APEx [guidelines](../interoperability/algohosting.md). If the algorithm has not yet been registered, APEx offers [support](onboarding.md) to assist projects in integrating their algorithms into the catalogue. diff --git a/propagation/usecases.md b/propagation/usecases.md index 0eabc60..d4b7f4f 100644 --- a/propagation/usecases.md +++ b/propagation/usecases.md @@ -94,16 +94,16 @@ APEx-compliant technology and assist the project in its implementation. ## Want to share your algorithm with the APEx community? -Please refer to [Use Case 4](#use-case-4-make-an-algorithm-available-in-the-apex-algorithm-services-catalogue) to learn +Please refer to [Use Case 4](#use-case-4-make-an-algorithm-available-in-the-apex-algorithm-catalogue) to learn how APEx can support you in sharing your algorithm with the community. ::: ### Outcome The algorithm, workflow or application is successfully transformed and is now available on a cloud platform and in -the [APEx Algorithm Services Catalogue](https://algorithm-catalogue.apex.esa.int/) as an openEO UDP or OGC API Process. +the [APEx Algorithm Catalogue](https://algorithm-catalogue.apex.esa.int/) as an openEO UDP or OGC API Process. -## Use Case 4: Make an algorithm available in the APEx Algorithm Services Catalogue +## Use Case 4: Make an algorithm available in the APEx Algorithm Catalogue ### Scenario @@ -130,17 +130,17 @@ to discover how APEx can provide support. ### Solution APEx will provide the necessary tools and comprehensive [support](onboarding.md) for integrating an algorithm into -the [APEx Algorithm Services Catalogue](https://algorithm-catalogue.apex.esa.int), ensuring its availability for reuse +the [APEx Algorithm Catalogue](https://algorithm-catalogue.apex.esa.int), ensuring its availability for reuse within the EO community. The support also includes: * Assistance in selecting and onboarding an APEx-compliant algorithm hosting platform to guarantee that an algorithm is available for execution as an on-demand service. * Provision of guidelines and tools for automated testing and benchmarking of the service. -* Publishing guidelines and documentation for registering an algorithm in the APEx Algorithm Services Catalogue. +* Publishing guidelines and documentation for registering an algorithm in the APEx Algorithm Catalogue. ### Outcome -The algorithm is available in the [APEx Algorithm Services Catalogue](https://algorithm-catalogue.apex.esa.int), +The algorithm is available in the [APEx Algorithm Catalogue](https://algorithm-catalogue.apex.esa.int), enhancing its visibility and usability within the EO community as an APEx-compliant service ## Use Case 5: Generating large-scale value-added products or maps based on on-demand EO services @@ -169,7 +169,7 @@ additional [APEx Algorithm Porting](porting.md) support is available. onto an APEx-compliant hosting platform and the [APEx Algorithm Upscaling](./upscaling.md) services and has requested the related resources to perform these activities, for their algorithm to be exposed behind a referenced API (e.g. openEO UDP endpoint or OGC API - Processes endpoint) and used to run Upscaling tasks. -* The project has discovered an algorithm in the [APEx Algorithm Services Catalogue](https://algorithm-catalogue.apex.esa.int) +* The project has discovered an algorithm in the [APEx Algorithm Catalogue](https://algorithm-catalogue.apex.esa.int) for generating a new air quality index and aims to execute this algorithm on all historical data for the entire continent of Europe.