Sor3 fr updates

instantiation/app_code_server.md

@@ -146,9 +146,12 @@ manual testing overhead and accelerates the rollout of new features or updates.
 
 It is important to note that a valid APEx account and permissions from the project are required to access an environment.
 
-| Project                         | URL                                                                                        |
-| :------------------------------ | :----------------------------------------------------------------------------------------- |
-| APEx (Demo)                     | [https://apphub.demo.apex.esa.int/](https://apphub.demo.apex.esa.int/)                     |
+| Project               | URL                                                                                |
+| :-------------------- | :--------------------------------------------------------------------------------- |
+| APEx (Demo)           | [https://apphub.demo.apex.esa.int/](https://apphub.demo.apex.esa.int/)             |
+| EO4CM                 | [https://apphub.eo4cm.apex.esa.int/](https://apphub.eo4cm.apex.esa.int/)           |
+| EO4SEM                | [https://apphub.eo4sem.apex.esa.int/](https://apphub.eo4sem.apex.esa.int/)         |
+| Information Factories | [https://apphub.info-factories.apex.esa.int/](https://apphub.eo4sem.apex.esa.int/) |
 
 : APEx Code Server IDE - Project Examples {#tbl-ide-examples}{tbl-colwidths="[20,80]"}
 

instantiation/app_jupyterlab.md

@@ -89,9 +89,12 @@ working with notebooks, with its native support for data science, data visualisa
 
 It is important to note that a valid APEx account and permissions from the project are required to access an environment.
 
-| Project                         | URL                                                                                        |
-| :------------------------------ | :----------------------------------------------------------------------------------------- |
-| APEx (Demo)                     | [https://apphub.demo.apex.esa.int/](https://apphub.demo.apex.esa.int/)                     |
+| Project               | URL                                                                                |
+| :-------------------- | :--------------------------------------------------------------------------------- |
+| APEx (Demo)           | [https://apphub.demo.apex.esa.int/](https://apphub.demo.apex.esa.int/)             |
+| EO4CM                 | [https://apphub.eo4cm.apex.esa.int/](https://apphub.eo4cm.apex.esa.int/)           |
+| EO4SEM                | [https://apphub.eo4sem.apex.esa.int/](https://apphub.eo4sem.apex.esa.int/)         |
+| Information Factories | [https://apphub.info-factories.apex.esa.int/](https://apphub.eo4sem.apex.esa.int/) |
 
 : APEx JuyterLab IDE - Project Examples {#tbl-ide-examples}{tbl-colwidths="[20,80]"}
 

instantiation/app_qgis.md

@@ -54,9 +54,12 @@ of data scientists might collaboratively develop crop yields scenario maps based
 
 Several examples are under development and will be added on this page.
 
-| Project                         | URL                                                                                        |
-| :------------------------------ | :----------------------------------------------------------------------------------------- |
-| APEx (Demo)                     | [https://apphub.demo.apex.esa.int/](https://apphub.demo.apex.esa.int/)                     |
+| Project               | URL                                                                                |
+| :-------------------- | :--------------------------------------------------------------------------------- |
+| APEx (Demo)           | [https://apphub.demo.apex.esa.int/](https://apphub.demo.apex.esa.int/)             |
+| EO4CM                 | [https://apphub.eo4cm.apex.esa.int/](https://apphub.eo4cm.apex.esa.int/)           |
+| EO4SEM                | [https://apphub.eo4sem.apex.esa.int/](https://apphub.eo4sem.apex.esa.int/)         |
+| Information Factories | [https://apphub.info-factories.apex.esa.int/](https://apphub.eo4sem.apex.esa.int/) |
 
 : APEx QGIS - Project Examples {#tbl-qgis-examples}{tbl-colwidths="[20,80]"}
 

instantiation/catalog.qmd

@@ -126,20 +126,5 @@ The following guides showcase how you can interact with the catalogue API:
 
 ## Examples
 
-@tbl-catalogue-examples showcases example projects that use the APEx Product Catalogue:
-
-| Project                                | URL                                                                                  |
-| :------------------------------------- | :----------------------------------------------------------------------------------- |
-| APEx                                   | [https://browser.apex.esa.int](https://browser.apex.esa.int/?.language=en)           |
-| APEx (Demo)                            | [https://browser.demo.apex.esa.int](https://browser.demo.apex.esa.int/?.language=en) |
-| World Ecosystem Extent Dynamics (WEED) | [https://browser.weed.apex.esa.int](https://browser.weed.apex.esa.int/?.language=en) |
-| EO4SEM                                 | [https://browser.eo4sem.apex.esa.int](https://browser.eo4sem.apex.esa.int)           |
-
-: APEx Product Catalogue - Project Examples {#tbl-catalogue-examples}{tbl-colwidths="[30,70]"}
-
-:::{.callout-tip}
-
-## Stay Tuned
-
-Additional information will be shared on this page as the project progresses.
-:::
+Explore the different Product Catalogue examples through our
+[Solutions Gallery](https://apex.esa.int/resources/solutions-gallery?field_services=Product+Catalogue).

instantiation/geospatial_explorer.md

@@ -18,22 +18,38 @@ support for features such as cursor inspection, queries, distance measurements a
 integrated charts and graphs. The UI will also provide access to metadata records associated with the data that is
 rendered in the Explorer.
 
-## Examples
-
-@tbl-explorer-examples showcases example projects that use the APEx Geospatial Explorer:
+## Geospatial Explorer Configuration Builder
+
+Maintenance of the Geospatial Explorer JSON configuration files can be undertaken using the GE Configuration Builder,
+a web based application that allows in browser JSON editing via bespoke User Interface, thereby negating the need for
+configuration “authors” to learn how to produce valid JSON, or understand the specifics of the GE schema.
+
+The GE Configuration Builder development is done in parallel to the GE, with Configuration Builder feature kept in line
+with the schema of the latest GE release, and potentially multiple Configuration Builder enhancements being undertaken
+between GE releases.
+
+![APEx Geospatial Explorer Configuation Builder](images/ge_config_builder.png)
+
+Features of the configuration builder include:
+
+* Compose an APEx Geospatial Explorer configuration from data sources and services (WMTS, WMS, WFS, COG, XYZ, GeoJSON,
+FlatGeoBuf, CSV) using layers organised into interface groups
+* Define the background maps that are available
+* Style raster layers with categories and colormaps, build RGB composites and style vector layers with rule-based filters
+and stops.
+* Define statistics and constraint layers
+* Author charts from CSV, COG pixel values, or vector feature properties.
+* Configure specific functional controls for each layer - e.g opacity slider, download links
+* Browse remote catalogues with the STAC and S3 browsers.
+* Inspect the metadata of data sources to understand their content
+* Validate every URL in your config with the Run Healthcheck tool and see data-access plus performance scores at a glance.
+* Define specific branding and navigation defaults (e.g. projection; start location and scale)
+* Preview the resulting APEx Geospatial Explorer inline using GE Preview before exporting JSON.
 
-| Project                         | URL                                                                                            |
-| :------------------------------ | :--------------------------------------------------------------------------------------------- |
-| APEx (Demo)                     | [https://explorer.demo.apex.esa.int/](https://explorer.demo.apex.esa.int/)                     |
-| SEF - Food Systems              | [https://explorer.sef-food.apex.esa.int/](https://explorer.sef-foodsystems.apex.esa.int/)             |
-| SEF - Ecosystems & Biodiversity | [https://explorer.sef-ecosystems.apex.esa.int/](https://explorer.sef-ecosystems.apex.esa.int/) |
-| SEF - Urban                     | [https://explorer.sef-urban.apex.esa.int/](https://explorer.sef-urban.apex.esa.int/)           |
-| EOBPs – Road and Railway        | [https://explorer.eobp-transport.apex.esa.int/](https://explorer.eobp-transport.apex.esa.int/) |
-| EOBPs – Solar Energy            | [https://explorer.eobp-energy.apex.esa.int/](https://explorer.eobp-energy.apex.esa.int/)       |
-| EOBPs – Health                  | [https://explorer.eobp-health.apex.esa.int/](https://explorer.eobp-health.apex.esa.int/)       |
-| EO4SEM                          | [https://explorer.eo4sem.apex.esa.int/](https://explorer.eo4sem.apex.esa.int/)                 |
+## Examples
 
-: APEx Geospatial Explorer - Project Examples {#tbl-explorer-examples}{tbl-colwidths="[20,80]"}
+Explore the different Geospatial Explorer examples through our
+[Solutions Gallery](https://apex.esa.int/resources/solutions-gallery?field_services=Geospatial+Explorer).
 
 ## User Guide
 
@@ -48,10 +64,3 @@ refer to the our [APEx Geospatial Explorer Recommendations](../interoperability/
 
 Numerous example configurations can be found in the
 [APEx Geospatial Explorer Configurations](https://github.com/ESA-APEx/apex_geospatial_explorer_configs) repository on GitHub.
-
-:::{.callout-tip}
-
-## Stay Tuned
-
-Additional information will be shared on this page as the project progresses.
-:::

instantiation/project_portal.md

@@ -113,20 +113,8 @@ the EO community without requiring dedicated hosting resources.
 
 ## Examples
 
-@tbl-portal-examples showcases example projects that use the APEx Project Web Portal:
-
-| Project                         | URL                                                                                  |
-| :------------------------------ | :----------------------------------------------------------------------------------- |
-| APEx                            | [https://apex.esa.int/](https://apex.esa.int/)                                       |
-| APEx (Demo)                     | [https://demo.apex.esa.int/](https://demo.apex.esa.int/)                             |
-| World Ecosystem Extent Dynamics | [https://esa-worldecosystems.org/](https://esa-worldecosystems.org/)                 |
-| EO4SEM                          | [https://eo4sem.apex.esa.int/en](https://eo4sem.apex.esa.int/en)                     |
-| EOBPs – Solar Energy            | [https://eobp-energy.apex.esa.int/en](https://eobp-energy.apex.esa.int/en)           |
-| EOBPs – Health                  | [https://eobp-health.apex.esa.int/en/home](https://eobp-health.apex.esa.int/en/home) |
-| EOBPs- Road and Rail            | [https://eobp-transport.apex.esa.int/en](https://eobp-transport.apex.esa.int/en)     |
-| RAVE                            | [https://rave.apex.esa.int/en](https://rave.apex.esa.int/en)                         |
-
-: APEx Project Web Portal - Project Examples {#tbl-portal-examples}{tbl-colwidths="[30,70]"}
+Explore the different Project Web Portal examples through our
+[Solutions Gallery](https://apex.esa.int/resources/solutions-gallery?field_services=Web+Portal).
 
 ## User Documentation
 

interoperability/datahosting.qmd

@@ -70,6 +70,10 @@ the produced data can reach a broad audience beyond the earth observation commun
 extra guidance, we refer to the [cloud native geospatial guide](https://guide.cloudnativegeo.org/) for a comprehensive
 comparison.
 
+Next to the use of cloud native formats, accompanying metadata is crucial for describing the content of the data. This
+ensures that datasets can be easily integrated into various tools and processed by cloud platforms. In the case of
+metadata, APEx recommends using STAC, as described in our [STAC section](#stac).
+
 | Scenario | Formats | Builds on |
 | :--- | :--- | :--- |
 | 1 – Cloud-based Processing | COG, GeoZarr, NetCDF\ GeoParquet, FlatGeobuf, GeoJSON | (baseline) |
@@ -78,7 +82,7 @@ comparison.
 
 :File Format Scenarios
 
-### STAC Metadata Recommendations
+### STAC
 
 The STAC specification provides a comprehensive and interoperable framework for describing geospatial datasets. Within
 APEx, STAC serves as the foundation to enhance the discoverability, interoperability, and integration of data across a
@@ -169,11 +173,12 @@ where columnar access patterns are beneficial.
 
 #### STAC Metadata
 
-When sharing geospatial datasets in cloud-optimised formats, such as Cloud Optimised GeoTIFF (COG), NetCDF, Zarr and
-FlatGeobuf, it is essential to embed as much relevant metadata as possible directly within the files. Although these
-formats are designed for efficient cloud access, their interoperability potential is enhanced when the files carry rich,
-standardised metadata aligned with their respective specifications. Doing so not only improves data reuse by third-party
-tools but also enables more reliable automatic inference of STAC metadata during cataloguing or dataset publication.
+When sharing geospatial datasets in cloud-optimised formats such as Cloud Optimised GeoTIFF (COG), NetCDF, Zarr, and
+FlatGeobuf, it’s essential to embed as much relevant metadata as possible directly within the files. While these formats
+are designed for efficient cloud access, their interoperability is further enhanced when accompanied by a separate,
+standardised STAC metadata file that aligns with their respective specifications. This not only improves data reuse by
+third-party tools but also facilitates more reliable automatic inference of STAC metadata during cataloguing or dataset
+publication.
 
 @tbl-processing-stac offers an overview of the general STAC recommendations for cloud-based processing. For more
 details and examples on adding this additional metadata to your results, please consult the specific tools (e.g.

propagation/onboarding.md

@@ -109,9 +109,12 @@ ESA’s [Network of Resources (NoR)](https://portfolio.nor-discover.org/). When
 service, onboarded to the ESA NoR, APEx can facilitate access to cloud processing resources on the corresponding
 platform as a central gateway and catalogue of federated services.
 
-In the long term, APEx plans to integrate the execution of services through its [APEx Geospatial Explorer](https://explorer.apex.esa.int/),
-simplifying the execution of onboarded services. However, it’s important to note that even with this user-friendly interface,
-users will still need to have access to the necessary processing resources on that platform.
+The [APEx Geospatial Explorer](https://explorer.apex.esa.int/) now also offers the ability to execute a variety of
+onboarded services directly. This functionality can be set up within the Geospatial Explorer instance itself, providing
+users with a streamlined and configurable execution environmentHowever, it’s important to note that even with this
+user-friendly interface, users will still need to have access to the necessary processing resources on that platform.
+
+![APEx Geospatial Explorer - Algorithm Execution](./images/ge_execution.png)
 
 ### Large-scale Data Processing
 
@@ -121,7 +124,7 @@ for [algorithm upscaling](upscaling.md).
 
 ## Onboard Your Algorithm on the [APEx Algorithm Catalogue](#apex-algorithm-catalogue)
 
-Onboarding your algorithm to the APEx Algorithm Catalogue is a straightforward process. Follow these
+Onboarding your algorithm to the APEx Algorithm Catalogue is a well-defined 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

propagation/upscaling.md

@@ -2,8 +2,11 @@
 title: Algorithm Upscaling
 ---
 
-The APEx Algorithm Upscaling approach implies designing a solution for services having a scaling factor that may differ
-from one algorithm to the other (spatial, temporal, track-based, etc…).
+The APEx Algorithm Upscaling approach involves designing a solution for services with varying scaling factors, such as
+spatial, temporal, or track-based. This concept elevates the execution of services hosted in the
+[APEx Algorithm Catalogue](./onboarding.md#apex-algorithm-catalogue) by providing tools to upscale service calls that
+process limited data to optimise processing for large data sets. These tools automatically create and manage multiple
+service calls to enhance performance and reduce costs.
 
 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