geoengine 0.9.2

A package for easy access to Geo Engine instances

Geo Engine Python Package

This package allows easy access to Geo Engine functionality from Python environments.

Test

Create a virtual environment

Create a virtual environment (e.g., python3 -m venv env).

# create new venv
python3 -m venv env
# activate new venv
source env/bin/activate

Re-create virtual environment

# go out of old venv
deactivate
# delete old venv
rm -r .venv
# create new venv
python3 -m venv .venv
# activate new venv
source .venv/bin/activate

Install dependencies

Then, install the dependencies with:

python3 -m pip install -e .
python3 -m pip install -e .[test]

Run tests

Run tests with:

pytest

Test instance

You have to set the environment variable GEOENGINE_TEST_CODE_PATH to the code folder of the Geo Engine instance you want to test against. Dotenv is supported, so you can create a .env file in the root of the project.

Coverage

You can check the coverage with:

pytest --cov=geoengine

Test examples

You can test the examples with:

python3 -m pip install -e .[examples]
./test_all_notebooks.py

Or you can test a single example with:

./test_notebook.py examples/ndvi_ports.ipynb

Dependencies

Since we use cartopy, you need to have the following system dependencies installed.

• GEOS
• PROJ

For Ubuntu, you can use this command:

sudo apt-get install libgeos-dev libproj-dev

Build

You can build the package with:

python3 -m pip install -e .[dev]
python3 -m build

Formatting

This package is formatted according to ruff. You can check it by calling:

python3 -m ruff format --check

Our tip is to install ruff and use it to format the code.

VSCode

If you use VSCode, you can install the ruff extension and set it as the default formatter.

Lints

Our CI automatically checks for lint errors. We use ruff to check the code. You can check it by calling:

python3 -m ruff check

Our tip is to activate linting with ruff in your IDE.

Type Checking

Our CI automatically checks for typing errors. We use mypy to check the code. You can check it by calling:

python3 -m mypy geoengine
python3 -m mypy tests

Using the config file mypy.ini, you can suppress missing stub errors for external libraries. You can ignore a library by adding two lines to the config file. For example, suppressing matplotlib would look like this:

[mypy-matplotlib.*]
ignore_missing_imports = True

If there are typing-stubs packages you can install using pip, you can use these packages instead of ignoring the reported errors. To find out, which packages could be installed you can use the following command:

python3 -m mypy geoengine --install-types
python3 -m mypy tests --install-types

Keep in mind, that you need to add the missing stubs by extending the dependencies in setup.cfg or ignoring them with mypy.ini.

Our tip is to activate type checking with mypy in your IDE.

All checks from above

You can call ./check.sh to run all the checks that are shown above.

Documentation

Generate documentation HTML with:

pdoc3 --html --output-dir docs geoengine

Examples

There are several examples in the examples folder. It is necessary to install the dependencies with:

python3 -m pip install -e .[examples]

Distribute to PyPI

Test-PyPI

python3 -m build
python3 -m twine upload --repository testpypi dist/*

PyPI

python3 -m build
python3 -m twine upload --repository pypi dist/*

Try it out

Start a python terminal and try it out:

import geoengine as ge
from datetime import datetime

ge.initialize("https://nightly.peter.geoengine.io/api")

time = datetime.strptime('2014-04-01T12:00:00.000Z', "%Y-%m-%dT%H:%M:%S.%f%z")

workflow = ge.workflow_by_id('4cdf1ffe-cb67-5de2-a1f3-3357ae0112bd')

print(workflow.get_result_descriptor())

workflow.get_dataframe(ge.Bbox([-60.0, 5.0, 61.0, 6.0], [time, time]))

Authentication

If the Geo Engine server requires authentication, you can set your credentials in the following ways:

1. in the initialize method: ge.initialize("https://nightly.peter.geoengine.io/api", ("email", "password"))
2. as environment variables export GEOENGINE_EMAIL="email" and export GEOENGINE_PASSWORD="password"
3. in a .env file in the current working directory with the content:

GEOENGINE_EMAIL="email"
GEOENGINE_PASSWORD="password"