openeo_processes is a Python representation of the openEO processes.
The list supported here tries to be as complete as possible, but some processes (typically the ‘cube’ ones) are intrinsically connected to the back-end implementation and data model, and therefore are omitted here. Examples of missing processes are ‘load_collection’ or ‘merge_cubes’.
Processes are currently aligned with openEO API version 1.0.
Installation
At the moment, this package is only installable from source. So start with cloning the repository:
git clone https://github.com/Open-EO/openeo-processes-python.git cd openeo-processes-python
It is recommended to install this package in a virtual environment, e.g. by using venv (from the Python standard library), virtualenv, a conda environment, … For example, to create a new virtual environment using venv (in a folder called .venv) and to activate it:
python3 -m venv .venv source .venv/bin/activate
(You might want to use a different bootstrap python executable instead of python3 in this example.)
Install the package in the virtual environment, preferably through pip of your virtual environment:
pip install .
If you plan to do development on the package itself, install it in “development” mode with:
pip install -e .
If plan to process xarray or dask arrays, you probably have the corresponding libraries already installed in your virtual env, and openeo_processes will handle them appropriately out of the box. You can however also explicitly pull these libraries in as “extra” dependencies when installing openeo_processes. For example with one of the following install commands:
pip install .[dask] pip install .[xarray] pip install .[dask,xarray]
Optionally run the tests:
python setup.py test
Note
This project has been set up using PyScaffold 3.0.3. For details and usage information on PyScaffold see http://pyscaffold.org/.
Metadata
Release files for openeo-processes 0.0.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| openeo_processes-0.0.4-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details |
Release files / openeo_processes-0.0.4-py2.py3-none-any.whl
| Download URL | openeo_processes-0.0.4-py2.py3-none-any.whl |
|---|---|
| Size | 33.1 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
7d2d0debe01225450618275df82455eccb97c3b9c71e4049f5ace1d16d45ec2d
|
|
BLAKE2b-256 checksum How to use checksums |
08a83d4c12ab6945c3cd2871f94a0bbd8a222315480ef813c3201304dc7e0d6e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.5.0.1 requests/2.24.0 setuptools/50.3.2 requests-toolbelt/0.9.1 tqdm/4.50.1 CPython/3.7.3
|
Security for openeo-processes 0.0.4
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.