Skip to main content
https://readthedocs.org/projects/dask-geomodeling/badge/?version=latest https://github.com/nens/dask-geomodeling/actions/workflows/test.yml/badge.svg https://badge.fury.io/py/dask-geomodeling.svg https://anaconda.org/conda-forge/dask-geomodeling/badges/version.svg

Dask-geomodeling is a collection of classes that are to be stacked together to create configurations for on-the-fly operations on geographical maps. By generating Dask compute graphs, these operation may be parallelized and (intermediate) results may be cached.

Multiple Block instances together make a view. Each Block has the get_data method that fetches the data in one go, as well as a get_compute_graph method that creates a graph to compute the data later.

Read the docs for further information.

## Development on this project itself

The standard command to setup your project using [uv](https://docs.astral.sh/uv/) is:

uv sync –dev # ‘uv.lock’ is git-ignored, because this is a library

This project uses GDAL, which requires additional system packages to be available on your system. On Ubuntu, you can install them with:

sudo apt-get install gdal-bin libgdal-dev

Then, installation of the GDAL python module is done as follows:

source .venv/bin/activate pip install GDAL[numpy]==$(gdal-config –version) –no-build-isolation

Then run the tests:

uv run pytest

The tests are also run automatically [on “github actions”](https://github.com/nens/dask-geomodeling/actions) for “master” and for pull requests. So don’t just make a branch, but turn it into a pull request right away. On your pull request page, you also automatically get the feedback from the automated tests.

## Release

Make sure you have [zest.releaser](https://zestreleaser.readthedocs.io/en/latest/) installed.

uv run fullrelease

When you created a tag, it will be uploaded automatically [to pypi](https://pypi.org/project/rana-process-sdk/) by a Github Action.

This project is also available on [conda-forge](https://anaconda.org/conda-forge/dask-geomodeling). After a release on PyPI is made, a Pull Request is automatically created on https://github.com/conda-forge/dask-geomodeling-feedstock. Merge this to publish the new version on conda-forge.

Release files for dask-geomodeling 2.8.2

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for dask-geomodeling 2.8.2
File Size Uploaded
dask_geomodeling-2.8.2.tar.gz 136.1 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for dask-geomodeling 2.8.2
File Interpreter ABI Platform
dask_geomodeling-2.8.2-py3-none-any.whl Python 3 none any Details

Total release size: 290.0 kB

Release files / dask_geomodeling-2.8.2.tar.gz

Download URL dask_geomodeling-2.8.2.tar.gz
Size 136.1 kB
Tags Source
SHA-256 checksum
How to use checksums
5122737988ad6a32c8aa63955a3bd975a951b281f326916a8d4083df4067cff9
BLAKE2b-256 checksum
How to use checksums
ac1c3b11e19e1689fb2b09f7f14d431e7f9851aac81ead2f05ac86def1084e19
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

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.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Jun 19, 2026.

Transparency log

Release files / dask_geomodeling-2.8.2-py3-none-any.whl

Download URL dask_geomodeling-2.8.2-py3-none-any.whl
Size 153.9 kB
Tags Python 3
SHA-256 checksum
How to use checksums
94312ac84088ef801782b89e164a9aafabd91e527d7da6e83fc95fdcae4b6bcc
BLAKE2b-256 checksum
How to use checksums
23defecf5ed2c21335809ff6584d4039f8a2069615ac07719b13bf272e129758
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

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.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Jun 19, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

2.8.2 This release

2 release files

2.8.1

2 release files

2.8.0

2 release files

2.7.0

2 release files

2.6.1

2 release files

2.6.0

2 release files

2.5.5

2 release files

2.5.4

2 release files

2.5.3

2 release files

2.5.2

2 release files

2.5.1

2 release files

2.5.0

1 release file

2.4.4

1 release file

2.4.3

1 release file

2.4.2

1 release file

2.4.1

1 release file

2.4.0

1 release file

2.3.13

1 release file

2.3.12

1 release file

2.3.11

1 release file

2.3.10

1 release file

2.3.9

1 release file

2.3.8

1 release file

2.3.7

1 release file

2.3.6

1 release file

2.3.5

1 release file

2.3.4

1 release file

2.3.3

1 release file

2.3.2

1 release file

2.3.1

1 release file

2.3.0

1 release file

2.2.12

1 release file

2.2.11

1 release file

2.2.10

1 release file

2.2.9

1 release file

2.2.8

1 release file

2.2.7

1 release file

2.2.6

1 release file

2.2.4

1 release file

2.2.3

1 release file

2.2.2

1 release file

2.2.1

1 release file

2.2.0

1 release file

2.1.1

1 release file

2.1.0

1 release file

2.0.4

1 release file

2.0.3

1 release file

2.0.2

1 release file

2.0.1

1 release file

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page