diff --git a/applications/argo.md b/applications/argo.md
index 9299e65d9..1252e1762 100644
--- a/applications/argo.md
+++ b/applications/argo.md
@@ -24,7 +24,7 @@ name: argo_workflows
Argo Workflow server
```
-Argo Workflows also provides detailed logs for all executions, enabling workspace administrator to monitor behavior, trace failures, and debug issues.
+Argo Workflows also provides detailed logs for all executions, enabling workspace administrators to monitor behavior, trace failures, and debug issues.
```{figure} assets/argo_workflow_single_job.png
---
@@ -33,7 +33,7 @@ name: argo_workflow_single_job
Argo Workflows details of a finished workflow with details of a step
```
-Sample templates will become available in the tutorial section once possible
+Sample templates will become available in the tutorial section when possible.
## Capability requirements for integration
@@ -71,4 +71,4 @@ Argo Workflow Server built in resource usage metrics
## Related use cases
- [Generate Results](../use_cases/result_generation.md)
-- [Provide an Algorithm as a Service](../use_cases/algorithm_as_a_service.md)
\ No newline at end of file
+- [Provide an Algorithm as a Service](../use_cases/algorithm_as_a_service.md)
diff --git a/applications/argo/capability_integration.md b/applications/argo/capability_integration.md
index 5455438a0..f62a7dadd 100644
--- a/applications/argo/capability_integration.md
+++ b/applications/argo/capability_integration.md
@@ -1,22 +1,22 @@
# Integration Requirements for Argo Workflows on EOxHub
-This document is intended as support material to describe how to best provide a capability implementation and its description in order to allow EOX to integrate it as a workflow inside of an EOxHub Workspace. This includes input definitions, expected Docker image standards, and output formats.
+This document is intended as support material describing how to provide a capability implementation and its description so that EOX can integrate it as a workflow within an EOxHub Workspace. This includes input definitions, expected Docker image standards, and output formats.
## Input Requirements
-To ensure compatibility with various interfaces (e.g. OGC Process API) to allow on demand execution of the capability some input requirements need to be considered. Furthermore information providing more context is needed regarding following points:
+To ensure compatibility with various interfaces (e.g. OGC Process API) and allow on-demand execution of the capability, some input requirements need to be considered. Furthermore, additional information is needed regarding the following points:
- Description of expected input data - does the service expect data already present or data are downloaded as part of the dockerized algorithm?
-- Description of expected argument and parameters
+- Description of expected arguments and parameters
- Description of expected output - see Output requirements section
### Arguments and parameters
-eodash processing widget support multiple ways how to pass input.
-- Area/location - process can take as input drawn point or polygon from the eodash user interface. For this integration, input field must accept eather coorinates directly or geoJSON as a string. File input is not accepted.
- - Example GeoJSON Feature String '{"type":"Feature","geometry":{"type":"Polygon" "coordinates":[[[30,10],[40,40],[20,40],[10,20],[30,10]]]},"properties":{}}'
-- Date - standard HTML Format date formats are supported. eodash also supports start and end time to create range.
+The eodash processing widget supports multiple ways of passing input.
+- Area/location - the process can take a drawn point or polygon as input from the eodash user interface. For this integration, the input field must accept either coordinates directly or GeoJSON as a string. File input is not accepted.
+ - Example GeoJSON Feature String '{"type":"Feature","geometry":{"type":"Polygon","coordinates":[[[30,10],[40,40],[20,40],[10,20],[30,10]]]},"properties":{}}'
+- Date - standard HTML date formats are supported. eodash also supports start and end times to create a range.
- "YYYY-MM-DD" e.g. 2015-05-30 for date.
- "YYYY-MM-DDThh:mm" for datetime 2025-07-02T06:33
- Numeric fields - integer or float values
@@ -24,17 +24,17 @@ eodash processing widget support multiple ways how to pass input.
- Dropdowns with limited options
-All fields can have default value
+All fields can have a default value
## Docker Image Requirements
Your process must be encapsulated in a Docker image. There are no strict limitations of what can be done, but there are good practices that help integration:
-- image is "slim" - only with required dependencies installed
-- image is tagged with version based on [semantic versioning](https://semver.org/)
-- algorithm logs to standard out (stdout) helping debug potential issues
-- simpler if no sideloading/sidecars (docker in docker) and similar
+- The image is "slim" - only the required dependencies are installed.
+- The image is tagged with a version based on [semantic versioning](https://semver.org/).
+- The algorithm logs to standard output (stdout) helping to debug potential issues.
+- Avoid sideloading/sidecars (Docker in Docker) and similar additional services where possible to keep the structure simple
- no special volumes, network expectations, ...
We expect to know resource usage estimation - RAM consumption and CPU estimates.
@@ -47,7 +47,7 @@ The workflow should store its results in `/output` folder, which will be collect
Expected outputs:
- Results (e.g., COG, geoJSON, CSV)
- - Inputs are expected to be cloud-native so for raster output formats, COGs are expected, for vector data geoJSON for small files up to 5Mb or flatGeobuf
+ - Inputs are expected to be cloud-native. For raster output formats, COGs are expected; for vector data, GeoJSON is recommended for small files up to 5 MB, or FlatGeobuf for larger files.
- Logs (optional but encouraged)
@@ -59,7 +59,7 @@ Outputs must be:
## Sample Checklist
-To submit your process for integration, make sure these information are included:
+To submit your process for integration, make sure this information is included:
- [ ] Dockerfile included and builds correctly
- [ ] README with usage instructions and input/output description
- [ ] Sample call example
@@ -69,4 +69,4 @@ To submit your process for integration, make sure these information are included
---
-Please contact the EOxHub team or submit a ticket if youneed more information.
\ No newline at end of file
+Please contact the EOxHub team or submit a ticket if you need further information.
diff --git a/applications/conda_store.md b/applications/conda_store.md
index f5d146ad7..bf70cc577 100644
--- a/applications/conda_store.md
+++ b/applications/conda_store.md
@@ -1,6 +1,6 @@
# Conda Store
-Within each user workspace where JupyterLab is provisioned also a dedicated [Conda Store](https://conda.store/) is available.
+Within each user workspace where JupyterLab is provisioned, a dedicated [Conda Store](https://conda.store/) is also available.
@@ -13,9 +13,9 @@ name: conda-store2
Conda store User interface
```
-Dedicated environments can be produced based on the user rights either for a user themselves or for a whole workspace and shared with colleagues or other people.
+Dedicated environments can be created based on user permissions, either for an individual user or for an entire workspace, and shared with colleagues or other users.
-Conda Store supports GUI or yaml syntax for environment creation and examples and how to guides can be found in the official [documentation](https://docs.conda.io/projects/conda/en/latest/user-guide/tasks/manage-environments.html)
+Conda Store supports a GUI or YAML syntax for environment creation. Examples and how-to guides can be found in the official [documentation](https://docs.conda.io/projects/conda/en/latest/user-guide/tasks/manage-environments.html).
```{figure} assets/conda_store.png
---
diff --git a/applications/container_registry.md b/applications/container_registry.md
index 4de2863a0..039d1ae07 100644
--- a/applications/container_registry.md
+++ b/applications/container_registry.md
@@ -1,6 +1,6 @@
# Container Registry
-We use **Zot Registry** - a lightweight, OCI-native container image registry - as repository for storing and managing container images within EOxHub Workspaces.
+We use **Zot Registry** - a lightweight, OCI-native container image registry - as a repository for storing and managing container images within EOxHub Workspaces.
You can easily push your custom images to Zot and pull them directly into your **Argo Workflows**.
The login credentials can be found in the secret **registry-login** in the [credentials manager](./secret_manager.md) of your workspace.
@@ -27,7 +27,7 @@ Authenticate with the endpoint and push your locally built images using standard
docker tag my-image:latest registry.[workspace-name].[cluster].eox.at/my-image:latest
```
-3. Push image to registry
+3. Push the image to the registry
```shell
docker push registry.[workspace-name].[cluster].eox.at/my-image:latest
@@ -46,4 +46,4 @@ Update your Argo Workflow templates to point to the Zot registry URL in your `co
## Related use cases
- [Develop an Algorithm](../use_cases/algorithm_development.md)
-- [Provide an Algorithm as a Service](../use_cases/algorithm_as_a_service.md)
\ No newline at end of file
+- [Provide an Algorithm as a Service](../use_cases/algorithm_as_a_service.md)
diff --git a/applications/data_editor.md b/applications/data_editor.md
index a82ce86ed..f8f76a8c7 100644
--- a/applications/data_editor.md
+++ b/applications/data_editor.md
@@ -1,6 +1,6 @@
# Data Editor
-The Data Editor application, provides a traceable review and approval path of collection configurations before data is published to the configured STAC catalog. This STAC catalog is used in the [Publishing Dashboard](publishing_dashboard.md) which is based on [eodash](https://eodash.org).
+The Data Editor application provides a traceable review and approval path for collection configurations before data is published to the configured STAC catalog. This STAC catalog is used in the [Publishing Dashboard](publishing_dashboard.md) which is based on [eodash](https://eodash.org).
It is based on [git-clerk](https://github.com/EOX-A/git-clerk) - Open-Source Content Management System based on Git workflows with a friendly file-editing GUI.
@@ -58,7 +58,7 @@ Currently supported data (resource) types are:
* Copernicus Marine Data Store WMTS
-List of all supported resources is kept up to date on [eodash wiki](https://github.com/eodash/eodash_catalog/wiki/Resource) so please visit this site as well.
+A list of all supported resources is kept up to date on the [eodash wiki](https://github.com/eodash/eodash_catalog/wiki/Resource), so please visit this site as well.
@@ -68,17 +68,17 @@ All required fields are marked in the Data Editor. More information about each o
## Overview of the process
-Generally for including a supported type of EO collection into an eodash deployment within EOxHub, the steps are summarized as follows:
+Generally, to include a supported type of EO collection in an eodash deployment within EOxHub, the steps are as follows:
- Start a new `session` in the Data Editor and create a new collection configuration file.
-- Fill metadata fields split into thematic groups. Mainly filling the [Resource](https://github.com/eodash/eodash_catalog/wiki/Resource) is important to visualize the data on the web map.
-- For raw data and client only rendering (GeoJSON, flatgeobuf or GeoTIFF as direct access), eodash supports an [OpenLayers flatstyle](https://openlayers.org/en/latest/apidoc/module-ol_style_flat.html). More information on styling can be [found here](https://eodash.org/styling.html#vector-styling).
-- eodash project offers [eodash-style-editor](https://github.com/eodash/eodash-style-editor) for editing the flatstyle definitions with updating the visualization in real time when definition is changed
+- Fill in the metadata fields, which are split into thematic groups. Filling in the [Resource](https://github.com/eodash/eodash_catalog/wiki/Resource) field is particularly important for visualizing the data on the web map.
+- For raw data and client-only rendering (GeoJSON, FlatGeobuf, or GeoTIFF as direct access), eodash supports an [OpenLayers flat style](https://openlayers.org/en/latest/apidoc/module-ol_style_flat.html). More information on styling can be [found here](https://eodash.org/styling.html#vector-styling).
+- The eodash project offers [eodash-style-editor](https://github.com/eodash/eodash-style-editor) for editing flat style definitions and updating the visualization in real time as the definition changes.
- To define interactions for the user (e.g. modify the style within the eodash app), the style can be extended with variables, combined with [JSON Form definition](https://eox-a.github.io/EOxElements/?path=/docs/elements-eox-jsonform--docs).
-- After finishing the updates confirmed by the layer live preview panel and approving of the corresponding Data editing session (GitHub Pull Request), the changes can be merged to production catalog.
+- After confirming the updates in the layer live preview panel and approving the corresponding Data Editor session (GitHub pull request), the changes can be merged into the production catalog.
-For learning how to include your data in Narrative publication, read the section [**Narrative Editor**](../applications/narrative_editor.md) and follow the tutorial [**Creating Narrative**](../tutorials/narrative_tutorial.md)
+For learning how to include your data in Narrative publication, read the section [**Narrative Editor**](../applications/narrative_editor.md) and follow the tutorial [**Get Started with the Narrative Editor**](../tutorials/creating_narratives/introduction_narrative_editor.md)
## Related tutorials
@@ -91,4 +91,4 @@ For learning how to include your data in Narrative publication, read the section
## Related use cases
-- [Publish Insights](../use_cases/publish_insights.md)
\ No newline at end of file
+- [Publish Insights](../use_cases/publish_insights.md)
diff --git a/applications/eoapi.md b/applications/eoapi.md
index e549c3c0a..05c23aa69 100644
--- a/applications/eoapi.md
+++ b/applications/eoapi.md
@@ -2,7 +2,7 @@
EOxHub includes robust data visualization capabilities for both raster and vector data based primarily on [eoapi](https://eoapi.dev/). These are powered by [titiler-pgstac](https://github.com/stac-utils/titiler-pgstac) and [PgSTAC](https://github.com/stac-utils/pgstac), which together enable dynamic tiling and rendering of STAC-compliant assets directly from storage based on pre-defined collection-level metadata fields.
-It exposes a [FastAPI](https://fastapi.tiangolo.com/) based interface, supporting image formats such as PNG and JPEG, and standard interfaces like WMTS.
+It exposes a [FastAPI](https://fastapi.tiangolo.com/)-based interface, supporting image formats such as PNG, JPEG and standard interfaces such as WMTS.
Future tutorials for eoAPI will become available in the tutorial section once possible.
@@ -19,7 +19,7 @@ Ingesting the existing STAC items to the database can be done in multiple ways:
### Make it Searchable
-This service utilizes `stac-fastapi` to publish and manage metadata describing their datasets, enabling machine-readable search, query, filter and cataloging across collections.
+This service utilizes `stac-fastapi` to publish and manage metadata describing its datasets, enabling machine-readable search, querying, filtering, and cataloging across collections.
@@ -32,7 +32,7 @@ titiler-pgSTAC is a TiTiler extension that connects to pgSTAC to support large-s
### Visualize Vector Data
-Utilizing [tipg](https://github.com/developmentseed/tipg) - Vector Tiling Service for OGC Features and OGC Tiles specifications.
+It utilizes [tipg](https://github.com/developmentseed/tipg), a Vector Tiling Service for the OGC Features and OGC Tiles specifications.
diff --git a/applications/file_browser.md b/applications/file_browser.md
index 9479ea803..d83cc9bdc 100644
--- a/applications/file_browser.md
+++ b/applications/file_browser.md
@@ -17,9 +17,9 @@ The **File Browser** is a web-based file management application integrated into
EOxHub Workspace employs a public access system to facilitate sharing and accessing datasets:
-- **Public Folder**: Files placed in the `public` directory are accessible via permanent public URLs, allowing for easy sharing and integration into other applications e.g. [Data Editor](data_editor).
+- **Public Folder**: Files placed in the `public` directory are accessible via permanent public URLs, allowing for easy sharing and integration into other applications, e.g. the [Data Editor](data_editor).
- **Shareable Links**: Users can generate shareable links for specific files or folders, providing controlled access to external collaborators.
-- **Access Control**: All areas within the File Browser are restricted to be accessed only by users of the workspace. Data in the `public` folder is openly accessible. By using the creation of shareable links other files can be made accessible to external people.
+- **Access Control**: All areas within the File Browser can only be accessed by users of the workspace. Data in the `public` folder is openly accessible. Shareable links can be used to make other files accessible to external users.
## Related tutorials
@@ -29,4 +29,4 @@ EOxHub Workspace employs a public access system to facilitate sharing and access
## Related use cases
- [Develop an Algorithm](../use_cases/algorithm_development.md)
-- [Publish Insights](../use_cases/publish_insights.md)
\ No newline at end of file
+- [Publish Insights](../use_cases/publish_insights.md)
diff --git a/applications/jupyterlab.md b/applications/jupyterlab.md
index 3121e5ead..99a4decd7 100644
--- a/applications/jupyterlab.md
+++ b/applications/jupyterlab.md
@@ -15,7 +15,7 @@
- View and edit CSVs, images, and text files
- Use drag-and-drop functionality across tabs
-In the context or EOxHub Workspaces, JupyterLab comes pre-configured with common EO and geospatial libraries, making it ideal for analysis, visualization, and prototyping. For more information, please visit the official [documentation](https://jupyterlab.readthedocs.io/)
+In the context of EOxHub Workspaces, JupyterLab comes pre-configured with common EO and geospatial libraries, making it ideal for analysis, visualization, and prototyping. For more information, please visit the official [documentation](https://jupyterlab.readthedocs.io/)
---
@@ -25,9 +25,9 @@ When launching JupyterLab in EOxHub, you will be asked to choose a **user profil
These are examples of common profiles based on the chosen subscription plan:
-- **Trial Profile**: Ideal for lightweight exploration and testing, usually avavilable in workshop settings or trials
+- **Trial Profile**: Ideal for lightweight exploration and testing, usually available in workshop settings or trials
- **Standard Profile**: Recommended for moderate EO processing
-- **Large Profile**: For heavy workloads (model training, large-scale analysis) or usage of GPPU
+- **Large Profile**: For heavy workloads (model training, large-scale analysis) or GPU usage
If your use case requires more resources, longer runtimes or GPU, please reach out to request a **custom setup**.
diff --git a/applications/publishing_dashboard.md b/applications/publishing_dashboard.md
index 7e2309a42..839be2c0b 100644
--- a/applications/publishing_dashboard.md
+++ b/applications/publishing_dashboard.md
@@ -2,7 +2,7 @@
The Publishing Dashboard provides a user-facing web interface for presenting and distributing curated datasets and narratives. It centers interactive maps and charts, as well as search and filter capabilities, and can be configured for public sharing or restricted access for defined user groups.
-Daily operation does not require coding skills or deep technical knowledge: content and configuration are maintained via the Data Editor and Narrative Editor, other applications available inside the EOxHub workspace together with the dashboard.
+Daily operation does not require coding skills or deep technical knowledge: content and configuration are maintained via the Data Editor and Narrative Editor, together with other applications available inside the EOxHub Workspace.
The Publishing Dashboard is based on **[eodash](https://eodash.org/)**, **[EOxElements](https://eox-a.github.io/EOxElements/)** and **[vitepress](https://vitepress.dev/)**. It is a web client instance connected to the information managed in the [Data Editor](data_editor.md) as well as the [Narrative Editor](narrative_editor.md).
@@ -29,7 +29,7 @@ name: eodashboard narratives screenshot
Narratives overview screenshot from eodashboard.org
```
-For more information on how to manage the published data content please have a look at the [Data Editor](data_editor.md) section, or for managing narratives at the [Narrative Editor](narrative_editor.md) section.
+For more information on managing published data content, please see the [Data Editor](data_editor.md) section; for managing narratives, see the [Narrative Editor](narrative_editor.md) section.
## Related tutorials
@@ -44,4 +44,4 @@ For more information on how to manage the published data content please have a l
## Related use cases
- [Provide an Algorithm as a Service](../use_cases/algorithm_as_a_service.md)
-- [Publish Insights](../use_cases/publish_insights.md)
\ No newline at end of file
+- [Publish Insights](../use_cases/publish_insights.md)
diff --git a/applications/secret_manager.md b/applications/secret_manager.md
index 890f50734..835dcdf53 100644
--- a/applications/secret_manager.md
+++ b/applications/secret_manager.md
@@ -37,21 +37,21 @@ Credentials manager
| Type | Example |
| ------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------ |
| **Opaque (key-value)**
You can add **one or more** key-value pairs. |  |
-| **dockerconfigjson**
The provided credentials are **converted to a valid json** and stored in the secret. |  |
+| **dockerconfigjson**
The provided credentials are **converted to valid JSON** and stored in the secret. |  |
| **ssh-auth**
You can either **upload** the key file **or paste the key** in the text area. |  |
#### Modification / Deletion
| Type | Example |
| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------- |
| **Opaque (key-value)**
add / remove key-value pairschange individual keys / values |  |
-| **dockerconfigjson**
The credentials can be changed, the current state of the currently stored json is shown in the (readonly) textarea below. |  |
+| **dockerconfigjson**
The credentials can be changed; the current state of the stored JSON is shown in the (read-only) text area below. |  |
| **ssh-auth**
The ssh-privatekey is masked and immutable once it's stored. If you need to change the key, you need to delete the secret first and then recreate it. |  |
#### Special modes
**Opaque (key-value)** can be set to **readonly** or **key-only** (has to be done by an administrator).
-**Readonly** & **key-only** credentials can only be viewed, but not edited or deleted.
+**Read-only** and **key-only** credentials can only be viewed; they cannot be edited or deleted.
```{figure} assets/credentials-manager/opaque-view-only.png
---
@@ -66,11 +66,11 @@ Credential can only be viewed, not edited or deleted.
| **key-only** |  |
-#### Inject as environment variables into Jupyterlab
+#### Inject as environment variables into JupyterLab
-**Opaque (key-value)** secrets can injected as environment variables in Jupyterlab by enabling the `Inject as env var into jupyterlab` button below the credential.
+**Opaque (key-value)** secrets can be injected as environment variables in JupyterLab by enabling the `Inject as env var into JupyterLab` button below the credential.
-> If you enable/disable this button you need to restart the Jupyterlab session to see its effect.
+> If you enable or disable this button, you need to restart the JupyterLab session to see its effect.
| Inject as env into Jupyterlab | Example |
@@ -84,4 +84,4 @@ Credential can only be viewed, not edited or deleted.
- [Develop an Algorithm](../use_cases/algorithm_development.md)
- [Generate Results](../use_cases/result_generation.md)
-- [Provide an Algorithm as a Service](../use_cases/algorithm_as_a_service.md)
\ No newline at end of file
+- [Provide an Algorithm as a Service](../use_cases/algorithm_as_a_service.md)
diff --git a/introduction/1_intro.md b/introduction/1_intro.md
index 00864f029..4fc251915 100644
--- a/introduction/1_intro.md
+++ b/introduction/1_intro.md
@@ -3,7 +3,7 @@
# Welcome to EOxHub Workspaces
-**EOxHub Workspaces** is a cloud-based environment for Earth Observation (EO) professionals, researchers, and data scientists. An **EOxHub Workspace** is an online-accessible environment where individuals or teams can work with geospatial services and applications — all from a unified web interface. It is designed for flexibility, making it suitable for anyone who need pre-configured tools and cloud resources.
+**EOxHub Workspaces** is a cloud-based environment for Earth Observation (EO) professionals, researchers, and data scientists. An **EOxHub Workspace** is an online-accessible environment where individuals or teams can work with geospatial services and applications — all from a unified web interface. It is designed for flexibility, making it suitable for anyone who needs pre-configured tools and cloud resources.
## Who is this for?
diff --git a/introduction/2_getting_started.md b/introduction/2_getting_started.md
index 3dab4ad65..82e83248f 100644
--- a/introduction/2_getting_started.md
+++ b/introduction/2_getting_started.md
@@ -14,7 +14,7 @@ To use EOxHub Workspaces, all you need is an Internet browser.
4. Agree to the terms and conditions
5. Wait for the confirmation by your workspace manager
-For more detailed instructions, including screenshots, see our tutorial [**How to create an account in EOxHub workspaces**](../tutorials/creating_account.md).
+For more detailed instructions, including screenshots, see our tutorial [**How to create an account in EOxHub workspaces**](../tutorials/getting_started/creating_account.md).
## Log In
diff --git a/introduction/3_faq.md b/introduction/3_faq.md
index 98378e430..b52a562cf 100644
--- a/introduction/3_faq.md
+++ b/introduction/3_faq.md
@@ -12,9 +12,9 @@ A: Everyone with an internet connection! It's designed for scientists, developer
A: No. Everything runs in your browser. All required libraries and tools are pre-installed in the cloud workspace.
-## Q: Can I install additional python packages?
+## Q: Can I install additional Python packages?
-A: Yes! You can install packages using conda store.
+A: Yes! You can install packages using Conda Store.
## Q: Will my work be saved?
@@ -30,4 +30,4 @@ A: Use the built-in support link in the user area or email us at service+tenants
## Q: Can I suggest a feature or report a bug?
-A: Absolutely! We welcome feedback — either via email your workspace support panel.
+A: Absolutely! We welcome feedback — either via email or through your workspace support panel.
diff --git a/tutorials/creating_narratives/introduction_narrative_editor.md b/tutorials/creating_narratives/introduction_narrative_editor.md
index bb863f7da..6d0367de9 100644
--- a/tutorials/creating_narratives/introduction_narrative_editor.md
+++ b/tutorials/creating_narratives/introduction_narrative_editor.md
@@ -21,12 +21,12 @@
\
-4\. After doing so, make sure "All repositories" is selected and click "Install & Authorize". The Narrative Editor requires access to all repositories to be able to create new narratives. It will not however, edit any of your other repositories.
+4\. After doing so, make sure "All repositories" is selected and click "Install & Authorize". The Narrative Editor requires access to all repositories to create new narratives. However, it will not edit any of your other repositories.
\
-5\. In order to create a narrative, you will have to create a session first. Sessions allow you to edit multiple files in one place. You will create your narrative within. To create a session click "Start New Session" towards the top right of your screen.
+5\. To create a narrative, you first need to create a session. Sessions allow you to edit multiple files in one place, and you will create your narrative within the session. To create a session, click "Start New Session" in the top-right corner of your screen.
@@ -36,7 +36,7 @@
\
-7\. Select "Create Narrative" to create a new narrative. The other two options let you edit existing narratives or upload your own. Both without actually making changes to the original Website yet.
+7\. Select "Create Narrative" to create a new narrative. The other two options let you edit existing narratives or upload your own. Neither option makes changes to the original website at this stage.
@@ -51,7 +51,7 @@
\
-10\. The title of your narrative, which is also shown on your hero image, is defined with a single hashtag "#", while each new section in your narrative uses "##". You can add a subheading to a section, by adding another hashtag: "###". In total you can add up to four subheadings, by adding hashtags.
+10\. The title of your narrative, which is also shown on your hero image, is defined with a single hashtag "#", while each new section in your narrative uses "##". You can add a subheading to a section by adding another hashtag: "###". In total, you can add up to four subheadings by adding hashtags.
diff --git a/tutorials/exploring_capabilities/polar_warp.md b/tutorials/exploring_capabilities/polar_warp.md
index d9c30f0cb..3007dcd87 100644
--- a/tutorials/exploring_capabilities/polar_warp.md
+++ b/tutorials/exploring_capabilities/polar_warp.md
@@ -6,22 +6,22 @@
**Before you start:** No Workspace account is required; the example is available through the DESIDE dashboard.
-1\. Navigate to [https://deside.eox.at/](https://deside.eox.at/)
+1\. Navigate to [https://deside.eox.at/](https://deside.eox.at/).
\
-2\. Click "Dashboard"
+2\. Click "Dashboard".
\
-3\. Click "Select indicator"
+3\. Click "Select indicator".
\
-4\. Select "Polar Warp Capability"
+4\. Select "Polar Warp Capability".
@@ -36,22 +36,22 @@
\
-7\. Once preferred location is found, drawing rectangle and selecting additional parameters is needed for triggering process.
+7\. Once the preferred location is found, draw a rectangle and select the additional parameters needed to trigger the process.
\
-8\. Click "Execute"
+8\. Click "Execute".
\
-9\. Running of capability can take couple minutes, depending on the size of the area.
+9\. Running the capability can take a couple of minutes, depending on the size of the area.
\
-10\. Move through predicted images in the left panel
+10\. Move through predicted images in the left panel.
diff --git a/tutorials/getting_started/creating_account.md b/tutorials/getting_started/creating_account.md
index 5c36b5774..5a1de8054 100644
--- a/tutorials/getting_started/creating_account.md
+++ b/tutorials/getting_started/creating_account.md
@@ -1,11 +1,11 @@
-# Create an EOxHub workspaces account
+# Create an EOxHub Workspaces account
**What you’ll accomplish:** Sign in to an EOxHub Workspace using your GitHub account.
**Estimated time:** 5 minutes
**Before you start:** You need a GitHub account and the URL of the EOxHub Workspace you want to access. Some Workspaces require administrator approval before access is granted.
-1\. Navigate to your EOxHub workspace. For example .
+1\. Navigate to your EOxHub Workspace. For example, .
@@ -20,9 +20,9 @@
\
-4\. Sign into your GitHub account. If you do not own one, you will have to create one here.
+4\. Sign in to your GitHub account. If you do not have one, you will have to create one here.
\
-5\. Keep in mind that not all EOxHub workspaces will automatically authorize your account. Sometimes you may have to wait to be approved by an administrator. Once you have completed all of that, you have successfully created an EOxHub account. Feel free to take a look at our other tutorials in order to understand how to utilize our tools.
\ No newline at end of file
+5\. Keep in mind that not all EOxHub Workspaces will automatically authorise your account. Sometimes you may have to wait for approval from an administrator. Once you have completed all of that, you have successfully created an EOxHub account. Feel free to take a look at our other tutorials in order to understand how to utilize our tools.
diff --git a/tutorials/processing_analysis/headless_notebook_execution.md b/tutorials/processing_analysis/headless_notebook_execution.md
index d91c299a5..9a900b8c3 100644
--- a/tutorials/processing_analysis/headless_notebook_execution.md
+++ b/tutorials/processing_analysis/headless_notebook_execution.md
@@ -8,30 +8,30 @@
Learn how to leverage headless notebooks to run your Jupyter notebooks with dynamic parameters. This guide walks you through starting a server, executing a notebook, and managing job outputs for automated analysis.
-1\. Navigate to your workspace - this tutorial is shown on a specific workspace but can be reproduced anywhere where this application is enabled
+1\. Navigate to your EoxHub Workspace - this tutorial is shown on a specific Workspace but can be reproduced anywhere this application is enabled.
\
-2\. Click "Headless Notebook" to verify that the application is enabled. If this icon is missing, please contact our support or your workspace administrator to add it
+2\. Click "Headless Notebook" to verify that the application is enabled. If this icon is missing, please contact our support team or your Workspace administrator to have it enabled.
\
-3\. Now let's start JupyterLab to prepare your notebook
+3\. Now let's start JupyterLab to prepare your notebook.
\
-4\. For the pygeoapi worker to find the correct notebook, it needs to be created in a specific structure within a shared folder. Inside the **shared** **folder**, there is another **folder** **named** **the** **same** **as** **the workspace** - this is the correct location.\
-The shared folder is shared among all users in the workspace and also with pygeoapi. \
+4\. For the pygeoapi worker to find the correct notebook, it needs to be created in a specific structure within a shared folder. Inside the **shared** folder, there is another folder **named the same as the Workspace** - this is the correct location.\
+The shared folder is shared among all users in the workspace and also with pygeoapi.\
\
Inside this folder, the structure can be arbitrary - separated into many other folders or just single notebooks.
\
-5\. Open a notebook and write your code into the cells
+5\. Open a notebook and write your code into the cells.
@@ -54,7 +54,7 @@ Inside the call you can specify:\
\
Optionally, it is possible to include resource limits, like CPU or RAM.\
\
-This request can be sent via any application the user prefers, not just a direct curl call.\
+This request can be sent via any application the user prefers, not just directly with `curl`.\
\
Here is an **example** call using curl:\
\
@@ -101,4 +101,4 @@ All cells will be executed, so opening the notebook can be used for debugging pu
\
14\. Opening the desired job details will show the passed parameters of the call, including the **kernel** and the exact values of the **parameters**. This helps with the reproducibility and traceability of the executed algorithms.
-
\ No newline at end of file
+
diff --git a/tutorials/processing_analysis/qgis_tutorial.md b/tutorials/processing_analysis/qgis_tutorial.md
index 1c2b0e31d..87b8c314c 100644
--- a/tutorials/processing_analysis/qgis_tutorial.md
+++ b/tutorials/processing_analysis/qgis_tutorial.md
@@ -9,37 +9,37 @@
This guide demonstrates the process of accessing a QGIS desktop environment directly within your browser using JupyterLab inside the EOxHub Workspace. It provides simple instructions to configure your server resources and successfully launch a specialized session for your data.
\
-1\. Navigate to your EOxHub Workspace with JupyterLab and QGIS enabled
+1\. Navigate to your EOxHub Workspace with JupyterLab and QGIS enabled.
\
-2\. Open "JupyterLab" application
+2\. Open "JupyterLab" application.
\
-3\. Click "Start My Server"
+3\. Click "Start My Server".
\
-4\. From the dropdown, select QGIS in the workspace profile
+4\. From the dropdown, select QGIS in the workspace profile.
\
-5\. From the second dropdown, multiple resource options can be selected
+5\. From the second dropdown, multiple resource options can be selected.
\
-5.5 \. It can happen that QGIS do not start on a first start - if that happens, click on jupyter icon in the upper left corner. This will refresh the session and fix the issue.
+5.5\. QGIS may not start on the first attempt. If that happens, click the Jupyter icon in the upper-left corner. This will refresh the session and fix the issue.
\
-6\. QGIS then opens inside the JupyterLab app window
+6\. QGIS then opens inside the JupyterLab app window.
diff --git a/tutorials/publishing_data/editors_linking_stories_collections.md b/tutorials/publishing_data/editors_linking_stories_collections.md
index 5babf3df1..df89b3ed6 100644
--- a/tutorials/publishing_data/editors_linking_stories_collections.md
+++ b/tutorials/publishing_data/editors_linking_stories_collections.md
@@ -20,16 +20,16 @@ both can be still a work in progress!
1\. Navigate to a **Narrative Editor**, select an existing working **Session**, where you are creating a narrative and copy the exact narrative file name for reference later. You do not need to open it.\
-In the tutorial it is **hunga_tonga_aerosol_plumes.md**
+In the tutorial it is **hunga_tonga_aerosol_plumes.md**.
2\. Navigate to a **Data Editor**, select a working session and modify the collection file which needs a new story reference.\
-In the tutorial it is **S5P-L3GRD-VOLCSO2-DAY**
+In the tutorial it is **S5P-L3GRD-VOLCSO2-DAY**.
\
-Click **"edit properties"** and check the add the **"Stories"** metadata group
+Click **"Edit properties"** and check to add the **"Stories"** metadata group.
@@ -44,28 +44,28 @@ Click **"edit properties"** and check the add the **"Stories"** metadata group
-5\. Add a new link entry by clicking on the **plus** icon
+5\. Add a new link entry by clicking on the **plus** icon.
-6\. Click **"edit properties"** to add new fields
+6\. Click **"edit properties"** to add new fields.
-7\. Tick checkboxes to enable **"Name"** and **"Id"** properties
+7\. Tick checkboxes to enable **"Name"** and **"Id"** properties.
-8\. The **"Name"** field represents a human readable name for the story link
+8\. The **"Name"** field represents a human readable name for the story link.
-In this tutorial set as **Story on Tracking aerosol plumes from Hunga eruption of 2022**
+In this tutorial set as **Story on Tracking aerosol plumes from Hunga eruption of 2022**.
**"Id"** field should contain the story filename without the .md suffix - can be retrieved from the Narrative Editor Session - opened in another window.
-In this tutorial **hunga_tonga_aerosol_plumes**
+In this tutorial **hunga_tonga_aerosol_plumes**.
@@ -79,11 +79,11 @@ Take note on the value of the **Name** (or **EodashIdentifier** if you are editi
10\. Now it's time to add the link also to the narrative.
-Switch to the **Narrative Editor**, select a working session, open the **narrative** which needs a new reference to a **collection** and update the top frontmatter information, adding a field **collections** with a list of comma-separated **Names** (or **EodashIdentifiers**) of all relevant collections for this narrative.
+Switch to the **Narrative Editor**, select a working session, open the **narrative** that needs a new reference to a **collection**, and update the top frontmatter information by adding a **collections** field containing a comma-separated list of **Names** (or **EodashIdentifiers**) of all relevant collections for this narrative.
-You can also get the collection name from dashboard url in the indicator= part eg. https://gtif-austria.info/explore?x=13.4280&y=47.8056&z=7.9771&template=light&indicator=brownfield_recovery_potential&datetime=2024-01-01 - in this case collection **Name** is brownfield_recovery_potential
+You can also get the collection name from dashboard url in the indicator= part eg. https://gtif-austria.info/explore?x=13.4280&y=47.8056&z=7.9771&template=light&indicator=brownfield_recovery_potential&datetime=2024-01-01 - in this case collection **Name** is brownfield_recovery_potential.
-In this tutorial set as **collections: S5P-L3GRD-VOLCSO2-DAY**
+In this tutorial set as **collections: S5P-L3GRD-VOLCSO2-DAY**.
diff --git a/tutorials/publishing_data/geojson_tutorial.md b/tutorials/publishing_data/geojson_tutorial.md
index 791bd685c..abce25c76 100644
--- a/tutorials/publishing_data/geojson_tutorial.md
+++ b/tutorials/publishing_data/geojson_tutorial.md
@@ -8,12 +8,12 @@
## Integrating a dataset from small GeoJSON file into the gtif-austria.info service
-1\. Navigate to [https://gtif-austria.info](https://gtif-austria.info)
+1\. Navigate to [https://gtif-austria.info](https://gtif-austria.info).
\
-2\. Click "Log in"
+2\. Click "Log in".
@@ -21,27 +21,27 @@
3\. If it is the first time visiting the workspace you will need to register.
\
-4\. After registration you are forwarded to the workspace. Click "Data Editor"
+4\. After registration you are forwarded to the workspace. Click "Data Editor".
\
-5\. If it is your first visit to the data editor it needs to be linked to your github account. Click "Authorize GTIF Austria Data Editor"
+5\. If it is your first visit to the Data Editor, it needs to be linked to your GitHub account. Click "Authorize GTIF Austria Data Editor".
\
-6\. Click on your username
+6\. Click on your username.
\
-7\. Click "Install & Authorize". It is important to select "all repositories" as git-clerk will create fork from existing data catalog.
+7\. Click "Install & Authorize". It is important to select "All repositories" because git-clerk will create a fork from the existing data catalog.
\
-8\. Click "Start New Session"
+8\. Click "Start New Session".
@@ -51,15 +51,15 @@
\
-10\. Type how you want to call your session, e.g. "new_resource_tutorial"
+10\. Type how you want to call your session, e.g. "new_resource_tutorial".
\
-11\. Click "Create"
+11\. Click "Create".
\
-12\. Click "Create Dataset Submission"
+12\. Click "Create Dataset Submission".
@@ -69,10 +69,10 @@
\
-14\. Type name you want to use for your data e.g. "geojson_example"
+14\. Type the name you want to use for your data, e.g. "geojson_example".
\
-15\. Click "Submit"
+15\. Click "Submit".
@@ -82,7 +82,7 @@
\
-17\. Type title you want to give your dataset, e.g. "GeoJSON Example"
+17\. Type the title you want to give your dataset, e.g. "GeoJSON Example".
\
18\. Click here.
@@ -90,7 +90,7 @@
\
-19\. Type identifier you want to appear in the url when selected, e.g. "geojson_example1"
+19\. Type the identifier you want to appear in the URL when selected, e.g. "geojson_example1".
\
20\. Click here.
@@ -98,15 +98,15 @@
\
-21\. Type the description for your dataset, (as markdown) e.g. "# Great description"
+21\. Type the description for your dataset (as Markdown), e.g. "# Great description".
\
-22\. Click on Resources
+22\. Click on Resources.
\
-23\. Activate checkbox
+23\. Activate the checkbox.
@@ -116,7 +116,7 @@
\
-25\. Select type of resource, in this case "GeoJSON Source"
+25\. Select type of resource, in this case "GeoJSON Source".
@@ -126,24 +126,24 @@
\
-27\. Add "GeoJSON source" as Name (this will be autofilled in the future)
+27\. Add "GeoJSON source" as the Name (this will be autofilled in the future).
\
-28\. Add the url of pre-created eodash JSON style file, see also for more information.
+28\. Add the URL of the pre-created eodash JSON style file. See also for more information.
(Dedicated tutorial on style definition being worked on)
\
-29\. If you want the dashboard to zoom to a specific area you can select a bounding box on the map
+29\. If you want the dashboard to zoom to a specific area you can select a bounding box on the map.
\
-30\. The geojson source assignes files to times, click on the plus to create a new time entry.
+30\. The GeoJSON source assigns files to times. Click the plus button to create a new time entry.
@@ -153,20 +153,20 @@
\
-32\. Type a time string in ISO 8601 (), e.g. "2025"
+32\. Type a time string in ISO 8601 (), e.g. "2025".
\
-33\. Add an asset for that time, click on the plus button
+33\. Add an asset for that time; click on the plus button.
\
-34\. Type an identifier for the asset you want to use and add the public url of your geoJSON file in the Field entry
+34\. Type an identifier for the asset you want to use and add the public URL of your GeoJSON file in the field entry.
\
-35\. Disable optional parameters by unchecking them (this step will not be needed in the future, they will be auto disabled)
+35\. Disable optional parameters by unchecking them (this step will not be needed in the future; they will be disabled automatically).
@@ -181,12 +181,12 @@
\
-38\. Click "Save"
+38\. Click "Save".
\
-39\. If the inputs were correct you should see "Preview creation is currently running..."
+39\. If the inputs were correct you should see "Preview creation is currently running...".
@@ -201,12 +201,12 @@
\
-42\. Close the Selection panel by clicking "✕" (you can also use the fullscreen button to change from mobile view mode)
+42\. Close the Selection panel by clicking "✕" (you can also use the fullscreen button to change from mobile view).
\
-43\. Congratulations! You should see your data styled and to the area you selected!
+43\. Congratulations! You should see your data styled and displayed in the area you selected.
diff --git a/tutorials/publishing_data/indicator_tutorial.md b/tutorials/publishing_data/indicator_tutorial.md
index 65a11148f..deb995ebd 100644
--- a/tutorials/publishing_data/indicator_tutorial.md
+++ b/tutorials/publishing_data/indicator_tutorial.md
@@ -3,16 +3,16 @@
**What you’ll accomplish:** Create an indicator that displays several existing collections as layers in one dashboard view.
**Applications used:** [**Data Editor**](../applications/data_editor.md), [**Publishing Dashboard**](../applications/publishing_dashboard.md)
**Estimated time:** 15 minutes
-**Before you start:** You need collection file you want to group. For more information how to create collections see other tutorials: [**add geojson dataset**](../tutorials/publishing_data/geojson_tutorial.md) and [**add WMTS dataset**](../tutorials/publishing_data/wtms_tutorial.md)
+**Before you start:** You need the collection files you want to group. For more information on how to create collections, see the other tutorials: [**Add GeoJSON Dataset**](../tutorials/publishing_data/geojson_tutorial.md) and [**add WMTS Dataset**](../tutorials/publishing_data/wtms_tutorial.md)
This guide provides a step-by-step process for merging multiple datasets into a single display collection using the EOxHub Data Editor.
It documents the task of adding a new Indicator file based on existing Collection files created beforehand. It also documents usage of additional Indicator specific properties Disable and Hidden.
-1\. This tutorial expects already existing **Collection** files in the session, which are supposed to be grouped together in an **Indicator** file. Each collection will be shown as a layer in the final visualisation.
+1\. This tutorial expects **Collection** files to already exist in the session; these collections will be grouped together in an **Indicator** file. Each collection will be shown as a layer in the final visualisation.
-2\. Navigate to **Data Editor** in the workspace page e.g.
+2\. Navigate to **Data Editor** in the workspace page e.g. .
@@ -29,7 +29,7 @@ Notice existing pre-created files in **collections**. Their **filenames** will b
-5\. Click "indicators"
+5\. Click "indicators".
@@ -39,12 +39,12 @@ Notice existing pre-created files in **collections**. Their **filenames** will b
-7\. Select "Edit in current session"
+7\. Select "Edit in current session".
-8\. Type the filename of a new indicator file with .json prefix, e.g. **"testing-indicator-new.json"**.
+8\. Type the filename of a new indicator file with the `.json` extension, e.g. **"testing-indicator-new.json"**.
Click on **Add New File**
@@ -66,7 +66,7 @@ Click on **Add New File**
-12\. Each Item is a filename of a **Collection** without the **.json** suffix e.g. **LULUCF_land_use_copy_test**
+12\. Each Item is a filename of a **Collection** without the **.json** suffix e.g. **LULUCF_land_use_copy_test**.
@@ -81,7 +81,7 @@ Click on **Add New File**
-15\. Metadata fields such as **Themes** defined on the **Collections** are **not** propagated into the **Indicator** so for indicators they must be defined here as well.
+15\. Metadata fields such as **Themes** defined on the **Collections** are **not** propagated to the **Indicator**, so they must be defined here as well.
@@ -121,12 +121,12 @@ Click on the checkbox to activate the field.
-22\. If on a smaller screen, in order to see the preview instance, click on the **"Eye"** icon
+22\. If on a smaller screen, in order to see the preview instance, click on the **"Eye"** icon.
-23\. "Preview creation takes a few minutes to finish"
+23\. "Preview creation takes a few minutes to finish".
@@ -136,7 +136,7 @@ Click on the checkbox to activate the field.
-25\. Click "Select indicator"
+25\. Click "Select indicator".
@@ -161,7 +161,7 @@ Click on the checkbox to activate the field.
-30\. You can then submit the session for review by clicking on the session name e.g. **testing-session**
+30\. You can then submit the session for review by clicking on the session name e.g. **testing-session**.
@@ -171,7 +171,7 @@ Click on the checkbox to activate the field.
-32\. Click "Request button"
+32\. Click "Request button".
@@ -203,6 +203,6 @@ Click on the indicator file if any changes were already done, otherwise use the
-38\. Click "Save"
+38\. Click "Save".
diff --git a/tutorials/publishing_data/publishing-workflow-tutorial.md b/tutorials/publishing_data/publishing-workflow-tutorial.md
index cd9b29e49..348ecfcf4 100644
--- a/tutorials/publishing_data/publishing-workflow-tutorial.md
+++ b/tutorials/publishing_data/publishing-workflow-tutorial.md
@@ -3,23 +3,23 @@
**What you’ll accomplish:** Upload, configure, preview, and submit a geospatial dataset for publication in an EOxHub dashboard.
**Applications used:** [**File Browser**](../applications/file_browser.md), [**Data Editor**](../applications/data_editor.md), [**Publishing Dashboard**](../applications/publishing_dashboard.md)
**Estimated time:** 30–45 minutes, excluding review and approval
-**Before you start:** You need access to an EOxHub Workspace with Dashboard as a Service and a your geospatial dataset.
+**Before you start:** You need access to an EOxHub Workspace with Dashboard as a Service and your geospatial dataset.
-This tutorial explains the complete workflow for preparing, uploading, styling, and publishing datasets in an EOXHub Workspace which includes multiple of the available Applications within EOxHub. It is intended as overview and does not go too deep into the options within the various steps, but provides follow on resources if more information is needed. The same steps apply across all workspace instances (e.g., GTIF Austria, Cerulean, and other environments).
+This tutorial explains the complete workflow for preparing, uploading, styling, and publishing datasets in an EOxHub Workspace, using several of the available applications within EOxHub. It is intended as an overview and does not go into detail on all the options within the various steps, but provides links to further resources if more information is needed. The same steps apply across all workspace instances (e.g., GTIF Austria, Cerulean, and other environments).
-For more information on the dedicated Applications, please further explore this documentation.
+For more information on the dedicated applications, please explore the rest of this documentation.
```{note}
-The Publishing of data in the Dashboard is only available for workspaces that have added the paid option **Dashboard as a Service (DaaS)**
+Publishing data in the Dashboard is only available for workspaces that have added the paid option **Dashboard as a Service (DaaS)**.
```
## Prerequisites
-In order to submit a data publishing request for raw resource, i.e. a data format that can directly be visualized by the dashboard (Cloud optimized GeoTIFF (COG), GeoJSON, FlatgeoBuf) you need following things:
+To submit a data publishing request for a raw resource, i.e. a data format that can be directly visualized by the Dashboard (Cloud-Optimized GeoTIFF (COG), GeoJSON, or FlatGeobuf), you need the following:
-1. **Have a geo file that is accessible through public URL**
-2. **Have a style definition file that is accessible through public URL**
+1. **Have a geospatial file that is accessible through a public URL.**
+2. **Have a style definition file that is accessible through a public URL.**
The tutorial covers how to achieve the prerequisites within an EOxHub Workspace environment and various other aspects of the Data Publishing submission:
@@ -34,18 +34,18 @@ The tutorial covers how to achieve the prerequisites within an EOxHub Workspace
## 1. Uploading Data with the File Browser
-For the first prerequisite (publicly available geo-file) it is possible to use the File browser application. The [**File Browser**](../applications/file_browser.md) allows adding data to a workspace.
+For the first prerequisite (a publicly available geospatial file), you can use the File Browser application. The [**File Browser**](../applications/file_browser.md) allows adding data to a workspace.
A special public folder is available where you can upload the files which are expected to be published.
-You can upload files (Tiff (Cloud Optimized Geotiff - COG), GeoJSON, style files, preview images, etc.) directly in the browser.
+You can upload files (Cloud-Optimized GeoTIFF (COG), GeoJSON, style files, preview images, etc.) directly in the browser.
-Once a file is uploaded it can be accessed through a special URL, similar to following:
+Once a file is uploaded, it can be accessed through a special URL similar to the following:
```text
https://workspace-ui-public..hub.eox.at/api/public/share/public/.tif
```
-The exact url as well as a short description is provided within the README.txt inside the public folder of your workspace.
+The exact URL, as well as a short description, is provided in the README.txt file inside the public folder of your workspace.
Presigned URLs generated from the File Browser are **temporary** and should not be used in the Dashboard configuration. Always use the permanent public URL.
> ⚠️ Upload through the browser to the workspace storage has some size limitations, files over ~100 MB should be uploaded differently.
@@ -55,17 +55,17 @@ Presigned URLs generated from the File Browser are **temporary** and should not
Here is more information on the supported formats:
* Raster Data:
- - Use Cloud-Optimized GeoTIFF (COG)
+ - Use Cloud-Optimized GeoTIFF (COG).
- Ideally in EPSG:3857 projection for best support performance
- - Other projections should also work but have a performance penalty when being visualized
+ - Other projections should also work but have a performance penalty when being visualised.
- Can be a single file or a time series (multiple files).
- Ideally encode the date and time in the filename using ISO format: YYYY-MM-DDTHH:MM:SS.
- Bands:
- RGB bands (already prepared as final visualization), or
- Data bands in which case a style will be needed (see section 3.)
* Vector Data:
- - Use GeoJSON if the file size is under ~10 MB, or FlatGeobuf for larger datasets
- - Even larger datasets should be handled differently, will need dedicated tile server
+ - Use GeoJSON if the file size is under ~10 MB, or FlatGeobuf for larger datasets.
+ - Even larger datasets should be handled differently and will need a dedicated tile server.
- Will need a style definition as described in section 3.
- Files in the **`public` folder** are openly accessible and can be integrated into the Dashboard.
@@ -79,7 +79,7 @@ Additional information on resource properties, such as raw data source can be fo
COGs with numeric values (e.g., temperature) as well as vector data (GeoJSON, FlatGeobuf) require a style definition so that it is clear how they should be visualized.
-This section covers handling the second pre-requisite, creating and making the style available online.
+This section covers handling the second prerequisite: creating the style and making it available online.
### Style creation
@@ -87,7 +87,7 @@ The style is based on [OpenLayers expressions](https://openlayers.org/en/latest/
Further information on styling in the eodash client can be found in the [eodash documentation](https://eodash.org/styling.html).
-An experimental client to help quicker iterate in the style definition is available under https://eodash.github.io/eodash-style-editor/. There you can set a URL for your dataset and work on the style definition live. Please take into account this is not a fully functioning experimental helper tool. A more streamlined integration is envisioned and the deployment of the current tool will probably change.
+An experimental client to help you iterate more quickly on the style definition is available at https://eodash.github.io/eodash-style-editor/. There you can set a URL for your dataset and work on the style definition live. Please note that this is an experimental helper tool and is not fully functional. A more streamlined integration is envisioned and the deployment of the current tool will probably change.
Example: Temperature color scale with no-data handling:
@@ -118,8 +118,8 @@ Example: Temperature color scale with no-data handling:
### Style online deployment
-Using the same logic as making the cloud optimized file available online, we can use the File Browser to upload or directly create the style json file to a location within the public folder.
-If you want to create the style and copy the style configuration content from the style editor, you can click on "New file" 📄, name it for example style.json, and in the opened editor paste your configuration. Make sure to click on save button 💾 once done.
+Using the same approach as making the Cloud-Optimized file available online, we can use the File Browser to upload or directly create the style JSON file in the public folder.
+If you want to create the style and copy the style configuration from the style editor, click on "New file" 📄, name it, for example, style.json, and paste your configuration into the editor. Make sure to click the Save button 💾 once you are done.
Then you can use the public endpoint as explained previously.
There are of course other ways of making a file public, many services exist especially for a json format. Style files can become intricate depending on the use case or done as collaboration activity so it might be beneficial to use a service that provides change tracking.
@@ -132,18 +132,18 @@ The basic steps are:
1. Go to **Data Editor → Start New Session**.
2. Automation → Create Dataset Submission:
- - Enter Data Title and click Submit
+ - Enter Data Title and click Submit.
3. Inside opened form:
- - Make sure identifier has no special characters or white spaces
- - Under **Resources**, click on the plus (+) sign
- - Under item 1 select *Cloud Optimized Geotiff (COG) Source*.
- - Add to the Style field the URL to a style definition (prerequisite 2 - as described in section 2 previously)
- - Draw a bounding box dashboard should zoom to when dataset selected (click → move mouse → click again to define rectangle)
- - Click plus (+) TimeEntries
- - Write a Time string in [ISO 8601](https://en.wikipedia.org/wiki/ISO_8601) format, e.g. YYYY-MM-DD or just year YYYY
- - Click on the plus (+) sign of the Assets field
- - Add an identifier string, e.g. data
- - Paste the URL to your public file into the File field (prerequisite 1 - as described in section 1 previously)
+ - Make sure identifier has no special characters or white spaces.
+ - Under **Resources**, click on the plus (+) sign.
+ - Under item 1, select *Cloud-Optimized GeoTIFF (COG) Source*.
+ - Add to the Style field the URL to a style definition (prerequisite 2 - as described in section 2 previously).
+ - Draw a bounding box that the Dashboard should zoom to when the dataset is selected (click → move the mouse → click again to define the rectangle).
+ - Click the plus (+) button for TimeEntries.
+ - Write a Time string in [ISO 8601](https://en.wikipedia.org/wiki/ISO_8601) format, e.g. YYYY-MM-DD or just year YYYY.
+ - Click on the plus (+) sign of the Assets field.
+ - Add an identifier string, e.g. data.
+ - Paste the URL to your public file into the File field (prerequisite 1 - as described in section 1 previously).
Example entry for a COG resource:
@@ -156,7 +156,7 @@ Example entry for a COG resource:
}
```
-This is intended as short summary, for more detailed guide with screenshots please look at [Integrating GeoJSON dataset using Data Editor](geojson_tutorial), where the shown steps are applicable to all raw resource submissions.
+For a more detailed guide with screenshots, please see [Integrating GeoJSON dataset using Data Editor](geojson_tutorial), where the shown steps are applicable to all raw resource submissions.
---
@@ -233,7 +233,7 @@ If multiple datasets should be shown together in the dashboard, there are mainly
- Combine them under one Indicator definition.
- Update the `catalog.json` to reference the new indicator.
-It is possible to use the "Browse Files" button in the Data Editor to find and modify most text based files. As alternative the changes can be made directly into the github repository if that is considered an easier alternative.
+It is possible to use the "Browse Files" button in the Data Editor to find and modify most text-based files. Alternatively, the changes can be made directly in the GitHub repository if that is considered easier.
Example indicator (simplified):
@@ -310,5 +310,5 @@ Workflow:
---
-This covers the main steps for publishing data by **uploading, styling, combining, and publishing** in an EOXHub Workspace.
-For more information on the used Applications further explore the documentation.
+This covers the main steps for publishing data by **uploading, styling, combining, and publishing** in an EOxHub Workspace.
+For more information about the applications used, please explore the rest of the documentation.
diff --git a/tutorials/publishing_data/wmts_tutorial.md b/tutorials/publishing_data/wmts_tutorial.md
index 94e847fbf..e9f7cd958 100644
--- a/tutorials/publishing_data/wmts_tutorial.md
+++ b/tutorials/publishing_data/wmts_tutorial.md
@@ -3,52 +3,52 @@
**What you’ll accomplish:** Connect a WMTS layer and verify it in the dashboard preview.
**Applications used:** [**Data Editor**](../applications/data_editor.md), [**Publishing Dashboard**](../applications/publishing_dashboard.md)
**Estimated time:** 20 minutes
-**Before you start:** You need WMTS endpoint with its layer identifier. This example uses Copernicus Marine WMTS.
+**Before you start:** You need a WMTS endpoint with its layer identifier. This example uses Copernicus Marine WMTS.
## Integrating a dataset from the Copernicus Marine Data Store into the eodashboard.org service
-1\. Navigate to [https://data.marine.copernicus.eu/products](https://data.marine.copernicus.eu/products)
+1\. Navigate to [https://data.marine.copernicus.eu/products](https://data.marine.copernicus.eu/products).
\
-2\. Search for the dataset you are interested in, for example by using the Click the "Free text" search. (In order for free search to work it seems you need to add also a date range or it will get stuck), for example you can type "chlorophyll a" enter a time range.
+2\. Search for the dataset you are interested in, for example by clicking the "Free text" search. (In order for free search to work it seems you need to add also a date range or it will get stuck), for example you can type "chlorophyll a" enter a time range.
\
-3\. Let us continue the example wit "Global Ocean Colour".
+3\. Let us continue the example with "Global Ocean Colour".
-Click "Global Ocean Colour (Copernicus-GlobColour), Bio-Geo-Chemical, L4 (monthly and interpolated) from Satellite Observations (Near Real Time)"
+Click "Global Ocean Colour (Copernicus-GlobColour), Bio-Geo-Chemical, L4 (monthly and interpolated) from Satellite Observations (Near Real Time)".
\
-4\. Click "Data access"
+4\. Click "Data access".
\
-5\. Click "WMTS"
+5\. Click "WMTS".
\
-6\. Use search within the WMTS xml file to find the [[<Layer]] you are interested in which includes the [[ows:Identifier]] you will need for the form later, as well as valuable information in the [[VariableInformation]] and default style
+6\. Use the search within the WMTS XML file to find the [[<Layer]] you are interested in. It includes the [[ows:Identifier]] you will need for the form later, as well as valuable information in the [[VariableInformation]] and default style.
\
-7\. Go to EO Dashboard workspace and log-in.
+7\. Go to the EO Dashboard Workspace and log in.
-If you do not have an account you need to register. Currently new users need to be manually authorized to get access
+If you do not have an account, you need to register. Currently, new users need to be manually authorised to get access.
\
-8\. Click "Data Editor"
+8\. Click "Data Editor".
\
-9\. Click "Start New Session"
+9\. Click "Start New Session".
@@ -58,15 +58,15 @@ If you do not have an account you need to register. Currently new users need to
\
-11\. Type the session name you want to have e.g. "new_cmems_data"
+11\. Type the session name you want to have e.g. "new_cmems_data".
\
-12\. Click "Create"
+12\. Click "Create".
\
-13\. Click "Add/Edit File Manually"
+13\. Click "Add/Edit File Manually".
@@ -76,18 +76,18 @@ If you do not have an account you need to register. Currently new users need to
\
-15\. Type "col"
+15\. Type "col".
\
-16\. Select the "collections" folder
+16\. Select the "collections" folder.
\
-17\. Type the name to use as collection file name (has to be a JSON file), e.g. "/cmems_data_1.json" (A new button will be introduced to simplify this step in the future)
+17\. Type the name to use as collection file name (has to be a JSON file), e.g. "/cmems_data_1.json" (A new button will be introduced to simplify this step in the future).
\
-18\. Click "Create"
+18\. Click "Create".
@@ -97,52 +97,52 @@ If you do not have an account you need to register. Currently new users need to
\
-20\. Type "cmems_data_chl"
+20\. Type "cmems_data_chl".
\
-21\. Add a title
+21\. Add a title.
\
-22\. Add an Eodashidentifier, it should be unique among the available collection, will be used in the URL to link to it directly e.g: ?indicator=CMEMS_CHL
+22\. Add an Eodashidentifier, it should be unique among the available collection, will be used in the URL to link to it directly e.g: ?indicator=CMEMS_CHL.
\
-23\. Optional properties can be enabled by clicking the check boxes
+23\. Optional properties can be enabled by clicking the check boxes.
\
-24\. Add some description for the dataset as markdown text
+24\. Add some description for the dataset as markdown text.
\
-25\. Click to resources, in principle all other tabs are optional
+25\. Click to resources. In principle all other tabs are optional.
\
-26\. Click on the plus symbol
+26\. Click on the plus symbol.
\
-27\. Select the resource type, in this case "Copernicus Marine Data Store WMTS"
+27\. Select the resource type, in this case "Copernicus Marine Data Store WMTS".
\
-28\. Click on endpoint
+28\. Click on endpoint.
\
29\. Copy the URL from the WMTS tab you opened earlier and remove the section starting from the question mark e.g. from [https://wmts.marine.copernicus.eu/teroWmts/OCEANCOLOUR_GLO_BGC_L4_NRT_009_102/cmems_obs-oc_glo_bgc-plankton_nrt_l4-olci-300m_P1M_202211?request=GetCapabilities&service=WMS](http://wmts.marine.copernicus.eu/teroWmts/OCEANCOLOUR_GLO_BGC_L4_NRT_009_102/cmems_obs-oc_glo_bgc-plankton_nrt_l4-olci-300m_P1M_202211?request=GetCapabilities&service=WMS) to:
-[https://wmts.marine.copernicus.eu/teroWmts/OCEANCOLOUR_GLO_BGC_L4_NRT_009_102/cmems_obs-oc_glo_bgc-plankton_nrt_l4-olci-300m_P1M_202211](http://wmts.marine.copernicus.eu/teroWmts/OCEANCOLOUR_GLO_BGC_L4_NRT_009_102/cmems_obs-oc_glo_bgc-plankton_nrt_l4-olci-300m_P1M_202211?request=GetCapabilities&service=WMS) and paste it into the field
+[https://wmts.marine.copernicus.eu/teroWmts/OCEANCOLOUR_GLO_BGC_L4_NRT_009_102/cmems_obs-oc_glo_bgc-plankton_nrt_l4-olci-300m_P1M_202211](http://wmts.marine.copernicus.eu/teroWmts/OCEANCOLOUR_GLO_BGC_L4_NRT_009_102/cmems_obs-oc_glo_bgc-plankton_nrt_l4-olci-300m_P1M_202211?request=GetCapabilities&service=WMS) and paste it into the field.
\
30\. Click here.
@@ -153,22 +153,22 @@ If you do not have an account you need to register. Currently new users need to
31\. Type "marinedatastore" in the Name field as well as "WMTSCapabilities" in the Type field.
\
-32\. Fill in the LayerID field
+32\. Fill in the LayerID field.
\
-33\. You can enable the time query start and end parameter to only retrieve specific time extent, for example 2024-01-01T00:00:00Z to 2025-01-27T00:00:00Z
+33\. You can enable the time query start and end parameter to only retrieve specific time extent, for example 2024-01-01T00:00:00Z to 2025-01-27T00:00:00Z.
\
-34\. The dimensions specification through the UI is still in progress
+34\. The dimensions specification through the UI is still in progress.
\
-35\. Click "Save"
+35\. Click "Save".
@@ -176,26 +176,26 @@ If you do not have an account you need to register. Currently new users need to
36\. After about 1 minute right-click "on the preview field" (probably in white area on the right side), search for Reload frame option and click it. If not found it is also possible to reload the whole page and navigate back to the file you were editing.
\
-37\. Click to expand the preview (currently an issue that it falls back to mobile view)
+37\. Click to expand the preview (currently an issue that it falls back to mobile view).
\
-38\. Click to select indicator
+38\. Click to select indicator.
\
-39\. You should see the indicator you just added, click on it
+39\. You should see the indicator you just added, click on it.
\
-40\. You should see the preview of your newly integrated indicator
+40\. You should see the preview of your newly integrated indicator.
\
-41\. The elevation should be specified as Dimension (currently not possible through UI) it defaults to some value (not 0) making the data rendering look different then in the CMEMS data explorer)
+41\. The elevation should be specified as Dimension (currently not possible through UI) it defaults to some value (not 0) making the data rendering look different then in the CMEMS data explorer).