diff --git a/book/sections/guide_developservice.md b/book/sections/guide_developservice.md index fd8b686..08023da 100644 --- a/book/sections/guide_developservice.md +++ b/book/sections/guide_developservice.md @@ -4,16 +4,16 @@ The following sections are describing how to transfer scientific methods into te ## Get started with the environment -The climate application packages (=birds) are designed to run in their own environment. This is avoiding dependency conflicts, when multiple birds are installed in a Climate Resilience Information System. The enviroments are organized with [conda](https://docs.conda.io/en/latest/) repective [mamba](https://github.com/conda-forge/miniforge#mambaforge). +The climate application packages (=birds) are designed to run in their own environment. This is avoiding dependency conflicts, when multiple birds are installed in a Climate Resilience Information System. The environments are organized with [conda](https://docs.conda.io/en/latest/) repective [mamba](https://github.com/conda-forge/miniforge#mambaforge). ## Set up the skeleton of your new climate application package -The following sections are describing how to transfer scientific methods into technical services which are deployable in climate resilience information systems. This is necessary when appropiate scientific methods are not already available and accessible as technical services. [Birdhouse](http://bird-house.github.io/) organisation lowers the barriers to set up new climate application package by providing tools enable you to build your own customised [OGC API Processes](https://ogcapi.ogc.org/processes/) application in support of web-based geospatial (climate) data analysis. +The following sections are describing how to transfer scientific methods into technical services which are deployable in climate resilience information systems. This is necessary when appropriate scientific methods are not already available and accessible as technical services. [Birdhouse](http://bird-house.github.io/) organisation lowers the barriers to set up new climate application package by providing tools enable you to build your own customised [OGC API Processes](https://ogcapi.ogc.org/processes/) application in support of web-based geospatial (climate) data analysis. -Within the Birdhouse organisation you can find an appropriate utility to set up a seleton for a new climate application package: +Within the Birdhouse organisation you can find an appropriate utility to set up a skeleton for a new climate application package: * A [Cookiecutter template](https://github.com/bird-house/cookiecutter-birdhouse) to create your own [PyWPS](http://pywps.org/) compute service. -The cockiecutter can be installed with: +The cookiecutter can be installed with: ``` conda install -c conda-forge cookiecutter cruft @@ -87,7 +87,7 @@ http://localhost:5000/wps?version=1.0.0&request=DescribeProcess&&service=WPS&ide Once your new climate application package is created, it needs to be filled with scientific algorithms. In contrast to a script that you are running locally in an individual way a service needs to be standardised. -The following figure is illustating the principles design of a technical service. Input data needs to be provided by a given adress to the appropriate resouces and and parameters to modify the execution needs to be provided as well. +The following figure is illustrating the principles design of a technical service. Input data needs to be provided by a given address to the appropriate resouces and parameters to modify the execution needs to be provided as well. On the other side, the number of output files are defined as well. Here number and format will be fixed. ```{figure} /media/guide_processscheema.png @@ -95,7 +95,7 @@ On the other side, the number of output files are defined as well. Here number a Basically your existing code can be integrated by simply taking care of some rules: -* no hard coding of path to local data sources, since the building block should run on all kind of different servers +* no hard coding of path to local data sources, since the building block should run on all kinds of different servers * encapsulating the processing steps in `try` and `exception` brackets with senseful log messages @@ -111,7 +111,7 @@ Basically your existing code can be integrated by simply taking care of some rul ``` --> ### Writing functions -A Process is calling several functions during the performance. Since WPS is a autonom running process several eventualities needs to be taken into account. If irregularities are occurring, it is a question of the process design if the performance should stop and return an error or continue with may be an modified result. +A Process is calling several functions during the performance. Since WPS is a autonom running process several eventualities needs to be taken into account. If irregularities are occurring, it is a question of the process design if the performance should stop and return an error or continue with maybe a modified result. In practice, the functions should be encapsulated in **try** and **except** calls and appropriate information given to the logfile or shown as a status message. The logger has several options to to influence the running code and the information writing to the logfile: diff --git a/book/sections/guide_science-crai.md b/book/sections/guide_science-crai.md index 1f72c25..1b272cf 100644 --- a/book/sections/guide_science-crai.md +++ b/book/sections/guide_science-crai.md @@ -1,4 +1,4 @@ -# transfer scientific algorythems into technical application packages for CRIS +# Transfer scientific algorithms into technical application packages for CRIS ## Example CRAI (Climate Reconstruction AI) diff --git a/book/sections/intro.md b/book/sections/intro.md index be21096..09d1e4d 100644 --- a/book/sections/intro.md +++ b/book/sections/intro.md @@ -2,7 +2,7 @@ The following sections are instructions, guidelines and backgrounds around OGC API based software, which can be used to set up **Climate Resilience Information Systems (CRIS)**. In the following sections we are using the [Duck](https://github.com/climateintelligence/duck) software as example to guide you through the different stepps necessay to set up an application package to be deployed in an CRIS and used for **Climate Services**. -Here we understand **Application Packages for CRIS** as standalone software in line to the [OGC API standards](https://developer.ogc.org). Several of this climate applicaiton packages can be found in the [Birdhouse](http://bird-house.github.io/) organisation which is a collection on OGC Standards based software. These software blocks can be used to build customised Climate Resilience Information System. The building blocks for climate services can be named with birdnames. +Here we understand **Application Packages for CRIS** as standalone software in line to the [OGC API standards](https://developer.ogc.org). Several of this climate application packages can be found in the [Birdhouse](http://bird-house.github.io/) organisation which is a collection on OGC Standards based software. These software blocks can be used to build customised Climate Resilience Information System. The building blocks for climate services can be named with birdnames. The demo web-application has been created by Carsten Ehbrecht and Étienne Plésiat in the framework of the work package 8 of the [CLINT](https://climateintelligence.eu/) H2020 project. Duck provides an AI-enhanced service to infill missing values in climate datasets.