Skip to main content

Welcome to py4dgeo

logo

License: MIT GitHub Workflow Status PyPI Release Documentation Status codecov

py4dgeo is a C++ library with Python bindings for change analysis in multitemporal and 4D point clouds.

Topographic 3D/4D point clouds are omnipresent in geosciences, environmental, ecological and archaeological sciences, robotics, and many more fields and applications. Technology to capture such data using laser scanning and photogrammetric techniques have evolved into standard tools. Dense time series of topographic point clouds are becoming increasing available and require tools for automatic analysis. Moreover, methods considering the full 4D (3D space + time) data are being developed in research and need to be made available in an accessible way with flexible integration into existent workflows.

The main objective of py4dgeo is to bundle and provide different methods of 3D/4D change analysis in a dedicated, comprehensive Python library. py4dgeo is designed as an international open source project that can be integrated into almost any 3D and GIS software in the geodata domain supporting Python, e.g. as plugins.

py4dgeo is under ongoing active development. Below, you find a list of provided methods.

🔨 Methods provided by py4dgeo

  • M3C2 algorithm (Lague et al., 2013) for bitemporal point cloud distance computation.

  • M3C2-EP (M3C2-EP; Winiwarter et al., 2021) for statistical signal-noise separation in change analysis through error propagation.

  • 4D objects-by-change (4D-OBC; Anders et al., 2021) for time series-based extraction of surface activities.

  • Correspondence-driven plane-based M3C2 (Zahs et al., 2022) for lower uncertainty in 3D topographic change quantification [under active development].

  • Point cloud registration using standard ICP by calculating and applying affine transformations to point clouds using a standard ICP implementations.

  • Point cloud registration with automatic determination of stable areas (Yang et al., 2022) for multitemporal change detection.

  • Hierarchical 3D surface change analysis for near real-time 3D surface change analysis of permanent laser scanning point clouds (Tabernig et al., 2025)

🎮 Examples

Demo notebooks using methods provided by py4dgeo

Example 1 Example 2
Example 3 Example 4
Example 5 Example 6
Example 7 Example 8

💻 Installation

Prerequisites

Using py4dgeo requires the following software installed:

  • 64-bit Python >= 3.10 (32-bit installations might cause trouble during installation of dependencies)

In order to build the package from source, the following tools are also needed.

  • A C++17-compliant compiler
  • Doxygen (optional, documentation building is skipped if missing)

Installing py4dgeo

The preferred way of installing py4dgeo is using pip.

Installing the release version using pip

py4dgeo can be installed using pip to obtain the current release:

python -m pip install py4dgeo

Building from source using pip

The following sequence of commands is used to build py4dgeo from source:

git clone --recursive https://github.com/3dgeo-heidelberg/py4dgeo.git
cd py4dgeo
python -m pip install -v --editable .

The --editable flag allows you to change the Python sources of py4dgeo without reinstalling the package. The -v flag enables verbose output which gives you detailed information about the compilation process that you should include into potential bug reports. To recompile the C++ source, please run pip install again. In order to enable multi-threading on builds from source, your compiler toolchain needs to support OpenMP.

If you want to contribute to the library's development you should also install its additional Python dependencies for testing and documentation building:

python -m pip install -r requirements-dev.txt

🪟 Windows-specific Notes

py4dgeo works on Windows, but optimal performance is typically achieved on Linux.

If you want to experiment with performance on your system, you can tune OpenMP using environment variables such as OMP_NUM_THREADS, OMP_PROC_BIND, and OMP_PLACES.

The best settings depend on your system, so there is no single recommended configuration.

Setting up py4dgeo using Docker

Additionally, py4dgeo provides a Docker image that allows to explore the library using JupyterLab. The image can be locally built and run with the following commands:

docker build -t py4dgeo:latest .
docker run -t -p 8888:8888 py4dgeo:latest

🐍 Documentation of software usage

As a starting point, please have a look to the Jupyter Notebooks available in the repository and find the py4dgeo documentation on readthedocs.

🎓 Tutorial of py4dgeo

Explore what py4dgeo can do with the py4dgeo tutorial. It provides an introduction to the methods available in the library, explains when and how to use them, and guides you through practical examples. It is the best way to get started with py4dgeo!

🌐 Published test data

If you are looking for data to test different methods, consider the following open data publications:

Hourly TLS point clouds of a sandy beach


Vos et al. (2022): https://doi.org/10.1038/s41597-022-01291-9.

By-weekly TLS point clouds of an Alpine rock glacier


Zahs et al. (2022): https://doi.org/10.11588/data/TGSVUI.

📑 Citation

If you use py4dgeo in a scientific context, please cite the following article:

@Article{py4dgeo_softwarex,
   author = {Anders, K. and Kempf, D. and Albert, W. and Andriushchenko, P. and Huang, X. and Hulskemper, D. and Isensee, T. and Kapitan, D. and Tabernig, R. and Weiser, H. and Winiwarter, L. and Zahs, V. and Höfle, B.},
   title = {py4dgeo: Open-source scientific software for topographic change analysis in 3D/4D geographic point clouds},
   journal = {SoftwareX},
   volume = {34},
   pages = {102670},
   DOI = {10.1016/j.softx.2026.102670},
   year = {2026},
   type = {Journal Article}
}

As a software citation, please reference the appropriate release version. You can find the Bibtex reference of the latest release via the Cite this repository link on the right side of this website (source: CITATION.cff).

💟 Funding / Acknowledgements

The initial software development was supported by the Scientific Software Center (SSC) in the Open Call 2021. The scientific software project is further supported by the research projects Extract4D, CharAct4D and AImon5.0.

🔔 Contact / Bugs / Feature Requests

You think you have found a bug or have specific request for a new feature? Please open a new issue in the online code repository on Github. Also for general questions please use the issue system.

Scientific requests can be directed to the 3DGeo Research Group Heidelberg and its respective members.

📄 How to contribute

We welcome contributions of new methods and usage demonstrations! Please see the full guidelines in our CONTRIBUTING.md for details on how to get started.

📜 License

See LICENSE.md.

  • Anders, K., Winiwarter, L., Mara, H., Lindenbergh, R., Vos, S.E. & Höfle, B. (2021): Fully automatic spatiotemporal segmentation of 3D LiDAR time series for the extraction of natural surface changes. ISPRS Journal of Photogrammetry and Remote Sensing, 173, pp. 297-308. DOI: 10.1016/j.isprsjprs.2021.01.015.
  • Lague, D., Brodu, N., & Leroux, J. (2013). Accurate 3D comparison of complex topography with terrestrial laser scanner: Application to the Rangitikei canyon (N-Z). ISPRS Journal of Photogrammetry and Remote Sensing, 82, pp. 10-26. DOI: 10.1016/j.isprsjprs.2013.04.009.
  • Tabernig, R., Albert, W., Weiser, H., & Höfle, B. (2025). A hierarchical approach for near real-time 3D surface change analysis of permanent laser scanning point clouds. In: 6th Joint International Symposium on Deformation Monitoring (JISDM). DOI: 10.5445/IR/1000180377
  • Winiwarter, L., Anders, K., Höfle, B. (2021): M3C2-EP: Pushing the limits of 3D topographic point cloud change detection by error propagation. ISPRS Journal of Photogrammetry and Remote Sensing, 178, pp. 240–258. DOI: 10.1016/j.isprsjprs.2021.06.011.
  • Zahs, V., Winiwarter, L., Anders, K., Williams, J.G., Rutzinger, M. & Höfle, B. (2022): Correspondence-driven plane-based M3C2 for lower uncertainty in 3D topographic change quantification. ISPRS Journal of Photogrammetry and Remote Sensing, 183, pp. 541-559. DOI: 10.1016/j.isprsjprs.2021.11.018.

Metadata

Release files for py4dgeo 1.2.1

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

Source distribution (sdist)

Source distribution for py4dgeo 1.2.1
File Size Uploaded Provenance Actions
py4dgeo-1.2.1.tar.gz 24.0 MB With provenance Details for py4dgeo-1.2.1.tar.gz

Built distributions (wheels)

Table of built distributions (wheels) for py4dgeo 1.2.1
File Actions
py4dgeo-1.2.1-cp314-cp314t-win_amd64.whl CPython 3.14 CPython 3.14 free-threading Windows x86-64 Details for py4dgeo-1.2.1-cp314-cp314t-win_amd64.whl
py4dgeo-1.2.1-cp314-cp314t-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl CPython 3.14 CPython 3.14 free-threading Linux glibc 2.27+ x86-64, Linux glibc 2.28+ x86-64 Details for py4dgeo-1.2.1-cp314-cp314t-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
py4dgeo-1.2.1-cp314-cp314t-macosx_14_0_arm64.whl CPython 3.14 CPython 3.14 free-threading macOS 14.0+ ARM64 Details for py4dgeo-1.2.1-cp314-cp314t-macosx_14_0_arm64.whl
py4dgeo-1.2.1-cp314-cp314-win_amd64.whl CPython 3.14 CPython 3.14 Windows x86-64 Details for py4dgeo-1.2.1-cp314-cp314-win_amd64.whl
py4dgeo-1.2.1-cp314-cp314-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl CPython 3.14 CPython 3.14 Linux glibc 2.27+ x86-64, Linux glibc 2.28+ x86-64 Details for py4dgeo-1.2.1-cp314-cp314-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
py4dgeo-1.2.1-cp314-cp314-macosx_14_0_arm64.whl CPython 3.14 CPython 3.14 macOS 14.0+ ARM64 Details for py4dgeo-1.2.1-cp314-cp314-macosx_14_0_arm64.whl
py4dgeo-1.2.1-cp313-cp313-win_amd64.whl CPython 3.13 CPython 3.13 Windows x86-64 Details for py4dgeo-1.2.1-cp313-cp313-win_amd64.whl
py4dgeo-1.2.1-cp313-cp313-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl CPython 3.13 CPython 3.13 Linux glibc 2.28+ x86-64, Linux glibc 2.27+ x86-64 Details for py4dgeo-1.2.1-cp313-cp313-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
py4dgeo-1.2.1-cp313-cp313-macosx_14_0_arm64.whl CPython 3.13 CPython 3.13 macOS 14.0+ ARM64 Details for py4dgeo-1.2.1-cp313-cp313-macosx_14_0_arm64.whl
py4dgeo-1.2.1-cp312-cp312-win_amd64.whl CPython 3.12 CPython 3.12 Windows x86-64 Details for py4dgeo-1.2.1-cp312-cp312-win_amd64.whl
py4dgeo-1.2.1-cp312-cp312-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl CPython 3.12 CPython 3.12 Linux glibc 2.27+ x86-64, Linux glibc 2.28+ x86-64 Details for py4dgeo-1.2.1-cp312-cp312-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
py4dgeo-1.2.1-cp312-cp312-macosx_14_0_arm64.whl CPython 3.12 CPython 3.12 macOS 14.0+ ARM64 Details for py4dgeo-1.2.1-cp312-cp312-macosx_14_0_arm64.whl
py4dgeo-1.2.1-cp311-cp311-win_amd64.whl CPython 3.11 CPython 3.11 Windows x86-64 Details for py4dgeo-1.2.1-cp311-cp311-win_amd64.whl
py4dgeo-1.2.1-cp311-cp311-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl CPython 3.11 CPython 3.11 Linux glibc 2.27+ x86-64, Linux glibc 2.28+ x86-64 Details for py4dgeo-1.2.1-cp311-cp311-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
py4dgeo-1.2.1-cp311-cp311-macosx_14_0_arm64.whl CPython 3.11 CPython 3.11 macOS 14.0+ ARM64 Details for py4dgeo-1.2.1-cp311-cp311-macosx_14_0_arm64.whl
py4dgeo-1.2.1-cp310-cp310-win_amd64.whl CPython 3.10 CPython 3.10 Windows x86-64 Details for py4dgeo-1.2.1-cp310-cp310-win_amd64.whl
py4dgeo-1.2.1-cp310-cp310-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl CPython 3.10 CPython 3.10 Linux glibc 2.27+ x86-64, Linux glibc 2.28+ x86-64 Details for py4dgeo-1.2.1-cp310-cp310-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
py4dgeo-1.2.1-cp310-cp310-macosx_14_0_arm64.whl CPython 3.10 CPython 3.10 macOS 14.0+ ARM64 Details for py4dgeo-1.2.1-cp310-cp310-macosx_14_0_arm64.whl

Total release size: 37.2 MB

Release files / py4dgeo-1.2.1.tar.gz

Download URL py4dgeo-1.2.1.tar.gz
Size 24.0 MB
Tags Source
SHA-256 checksum
How to use checksums
21faa7937af5994ee92844db8f39db76b69b007f6db6961e3d3a9f24ae35e101
BLAKE2b-256 checksum
How to use checksums
a081f271a0414ba88883586093035998134cec312313b0cdf5c58768c3800030
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Oct 29, 2026.

Transparency log

Release files / py4dgeo-1.2.1-cp314-cp314t-win_amd64.whl

Download URL py4dgeo-1.2.1-cp314-cp314t-win_amd64.whl
Size 1.0 MB
Tags CPython 3.14 CPython 3.14 free-threading Windows x86-64
SHA-256 checksum
How to use checksums
9da11544ddfdb50720a26fbf3aef2d97b3190d8a7e220b0e86ec909c647156b3
BLAKE2b-256 checksum
How to use checksums
967cadf29e50096e5cf8fb3489fbdde1d691553e1c6274e80d26da9940b54d1a
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Oct 29, 2026.

Transparency log

Release files / py4dgeo-1.2.1-cp314-cp314t-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl

Download URL py4dgeo-1.2.1-cp314-cp314t-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
Size 589.4 kB
Tags CPython 3.14 CPython 3.14 free-threading Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
c3d3ef2f557c40451e89ecb09e04cf7d3cbeae202ce6f1b33112ac523e738da0
BLAKE2b-256 checksum
How to use checksums
f1b225cbb7b7bdfd401ce1db85cad9239a2d71e2e2f09e4956a9e25c7ac1e6cd
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Oct 29, 2026.

Transparency log

Release files / py4dgeo-1.2.1-cp314-cp314t-macosx_14_0_arm64.whl

Download URL py4dgeo-1.2.1-cp314-cp314t-macosx_14_0_arm64.whl
Size 654.3 kB
Tags CPython 3.14 CPython 3.14 free-threading macOS 14.0+ ARM64
SHA-256 checksum
How to use checksums
7ea92dd1024b4bf61e3977e56d0bffd87b92bc772bbca0b9d018174d7f76722a
BLAKE2b-256 checksum
How to use checksums
404d43539886e2648d9c6bdd223d3d85030972a7a084efaf44e9f53fe4795e48
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Oct 29, 2026.

Transparency log

Release files / py4dgeo-1.2.1-cp314-cp314-win_amd64.whl

Download URL py4dgeo-1.2.1-cp314-cp314-win_amd64.whl
Size 1.0 MB
Tags CPython 3.14 Windows x86-64
SHA-256 checksum
How to use checksums
cdf535e2e9be2bc14296d368da736afcb7fc3769521703e42a22798c8b6bd4ae
BLAKE2b-256 checksum
How to use checksums
815f2cf207c2d537c0ca8d99c4437268e66436ab31ebe6d9d900ed9a3532aaaa
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Oct 29, 2026.

Transparency log

Release files / py4dgeo-1.2.1-cp314-cp314-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl

Download URL py4dgeo-1.2.1-cp314-cp314-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
Size 585.4 kB
Tags CPython 3.14 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
231555848b3042a6b92349efa79810a6a68b3ccde3f1e1ae04e47b6747bd8ed8
BLAKE2b-256 checksum
How to use checksums
20eec9a28a674aebb2524c099f2c1edd64157af6a178ff386d82d23f5927860c
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Oct 29, 2026.

Transparency log

Release files / py4dgeo-1.2.1-cp314-cp314-macosx_14_0_arm64.whl

Download URL py4dgeo-1.2.1-cp314-cp314-macosx_14_0_arm64.whl
Size 635.4 kB
Tags CPython 3.14 macOS 14.0+ ARM64
SHA-256 checksum
How to use checksums
66eaf2e60a1bf8b297888216fb91c0daa37e3fe544a676bd35d4be457d7fc222
BLAKE2b-256 checksum
How to use checksums
06eae6141d82d3ff0a0cd1877f0fcd1097dfe26a9f978ae17c975b5e476656ec
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Oct 29, 2026.

Transparency log

Release files / py4dgeo-1.2.1-cp313-cp313-win_amd64.whl

Download URL py4dgeo-1.2.1-cp313-cp313-win_amd64.whl
Size 975.2 kB
Tags CPython 3.13 Windows x86-64
SHA-256 checksum
How to use checksums
2ef24eb13f0b73921e93d05236511b623e7d8356013579ff39db95e913509f1f
BLAKE2b-256 checksum
How to use checksums
aece179688816586db4c406799e96747d572c8dde8adde5927e0cacd83c2c83e
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Oct 29, 2026.

Transparency log

Release files / py4dgeo-1.2.1-cp313-cp313-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl

Download URL py4dgeo-1.2.1-cp313-cp313-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
Size 584.9 kB
Tags CPython 3.13 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
add160303fd8386c62fcb2f29886be3ee563117884ab4c53cdfdd612b90ca0e9
BLAKE2b-256 checksum
How to use checksums
e4346506cd03bf3f19defffd8968222ed38a6fe03a1fca42fc50a9bfe41c359f
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Oct 29, 2026.

Transparency log

Release files / py4dgeo-1.2.1-cp313-cp313-macosx_14_0_arm64.whl

Download URL py4dgeo-1.2.1-cp313-cp313-macosx_14_0_arm64.whl
Size 634.9 kB
Tags CPython 3.13 macOS 14.0+ ARM64
SHA-256 checksum
How to use checksums
6f93aba04ad1ab314e3882a6dacbe9fb2f6dcfd2e9fe36d301f33f1975549533
BLAKE2b-256 checksum
How to use checksums
32b6bd8821c61dab4381500de6152a1f8e2c499b68dbec06e02d21c73e4de83e
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Oct 29, 2026.

Transparency log

Release files / py4dgeo-1.2.1-cp312-cp312-win_amd64.whl

Download URL py4dgeo-1.2.1-cp312-cp312-win_amd64.whl
Size 975.3 kB
Tags CPython 3.12 Windows x86-64
SHA-256 checksum
How to use checksums
cf9fad2d82b3283102a18e3efc54f94624bdafde13e190626886f59fb0e6552d
BLAKE2b-256 checksum
How to use checksums
501e4e5c85b629c0866e0e9a35d41b9f5f38509e383ee5c0230b6377b954c4a2
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Oct 29, 2026.

Transparency log

Release files / py4dgeo-1.2.1-cp312-cp312-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl

Download URL py4dgeo-1.2.1-cp312-cp312-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
Size 585.2 kB
Tags CPython 3.12 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
d232867462c37ed9648336db902c06368820cce180dba623817ccc43b4fd223e
BLAKE2b-256 checksum
How to use checksums
3f17bf9cdacf7b62e8ea73806349784eba3364147d6b8ef70306fc3b65c3ca3a
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Oct 29, 2026.

Transparency log

Release files / py4dgeo-1.2.1-cp312-cp312-macosx_14_0_arm64.whl

Download URL py4dgeo-1.2.1-cp312-cp312-macosx_14_0_arm64.whl
Size 634.8 kB
Tags CPython 3.12 macOS 14.0+ ARM64
SHA-256 checksum
How to use checksums
5457d85173faae305ea007fc80c5493ca394ebc4735ea739e4773691131d9341
BLAKE2b-256 checksum
How to use checksums
aa505166cbb7cb2ba858df67cd31e6098e7a66b2a0e40f80c8274dbfc617bf05
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Oct 29, 2026.

Transparency log

Release files / py4dgeo-1.2.1-cp311-cp311-win_amd64.whl

Download URL py4dgeo-1.2.1-cp311-cp311-win_amd64.whl
Size 968.9 kB
Tags CPython 3.11 Windows x86-64
SHA-256 checksum
How to use checksums
1d4a20e42887cd8bdb498015f70e24854b2b6fb3344a9dbd534b50cc0cde35e2
BLAKE2b-256 checksum
How to use checksums
e5284bcd4b8b8727a2eed3529ee43bba6df7e9d9d304c314b920cb401fd668c7
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Oct 29, 2026.

Transparency log

Release files / py4dgeo-1.2.1-cp311-cp311-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl

Download URL py4dgeo-1.2.1-cp311-cp311-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
Size 582.4 kB
Tags CPython 3.11 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
da87336383f77a2753c7bc13f7e00dcac2d2a990ff76ed2615136b8db7ae17a9
BLAKE2b-256 checksum
How to use checksums
8c7ec143682d830e928d91a9e8aaf2ed8532ee82a6d33c9964a53af52cb24ebd
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Oct 29, 2026.

Transparency log

Release files / py4dgeo-1.2.1-cp311-cp311-macosx_14_0_arm64.whl

Download URL py4dgeo-1.2.1-cp311-cp311-macosx_14_0_arm64.whl
Size 630.9 kB
Tags CPython 3.11 macOS 14.0+ ARM64
SHA-256 checksum
How to use checksums
88672d95db429d755afc6548009e7a32dcb6ac1bc8afd474f6a952a3554be59c
BLAKE2b-256 checksum
How to use checksums
a3d509467129a98136971cfc629e1cb5e332fa81ce1a0204974f5c0a0eb501e6
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Oct 29, 2026.

Transparency log

Release files / py4dgeo-1.2.1-cp310-cp310-win_amd64.whl

Download URL py4dgeo-1.2.1-cp310-cp310-win_amd64.whl
Size 966.5 kB
Tags CPython 3.10 Windows x86-64
SHA-256 checksum
How to use checksums
94808bac5079911742672beacd8f70f56259ae87be41ccad2eba1bacf4140ced
BLAKE2b-256 checksum
How to use checksums
25f71cdced965e9acc8648d2772b95298149c38dee11a5cdac5b5f718d972a3d
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Oct 29, 2026.

Transparency log

Release files / py4dgeo-1.2.1-cp310-cp310-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl

Download URL py4dgeo-1.2.1-cp310-cp310-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
Size 581.7 kB
Tags CPython 3.10 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
d217968cf7ab8ddcc2fb4d636c7f24d95746792ea6b79b9f657668e9e6caba2a
BLAKE2b-256 checksum
How to use checksums
32abc1b8203af93d336ed26f33287ff70ea88e5d3b83eb3eae6003561e6e44eb
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Oct 29, 2026.

Transparency log

Release files / py4dgeo-1.2.1-cp310-cp310-macosx_14_0_arm64.whl

Download URL py4dgeo-1.2.1-cp310-cp310-macosx_14_0_arm64.whl
Size 629.6 kB
Tags CPython 3.10 macOS 14.0+ ARM64
SHA-256 checksum
How to use checksums
e1eda81a2ed173618b53ed29e685265af7399fca52a4ed750931f2030ef9c5b4
BLAKE2b-256 checksum
How to use checksums
011e3966f9904660c35a33ed0b6ac58e003bac414a61fa9827a49bcaabdfe5a6
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Oct 29, 2026.

Transparency log

Security for py4dgeo 1.2.1

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.

Full provenance

All 19 files in this release have been uploaded with provenance metadata.

Select from 19 files

Attestation for py4dgeo-1.2.1.tar.gz

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 Oct 29, 2026.

Transparency log

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.

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