Hello OSGeo community,

I'm Enzo Cocca, the developer of PyArchInit Photogrammetry. I'd like to introduce the application and its separate plugin repository, and get feedback on how the workflows fit into open-source GIS practice.

The application produces georeferenced point clouds, meshes, digital elevation models and orthophotos from photographs. It provides a Python API, CLI and desktop interface, with CPU photogrammetry processing and optional Rust kernels. Its archaeological workflows connect survey products with PyArchInit records, stratigraphic units, sections and IFC exports.

The README documents a live QGIS workflow for the orthophoto, DEM and drawn layers, plus importing existing Metashape projects and WebODM/ODM outputs.

The plugin repository currently documents 12 extensions. Four particularly relevant to geospatial work are:

  • GIS archive: export survey layers and products to GeoPackage, PostgreSQL/PostGIS or SpatiaLite.
  • Terrain: WhiteboxTools-based hydrology and geomorphometry on a project's DEM, with GeoTIFF and GeoPackage outputs.
  • Geoarchaeology: borehole and trench logs, stratigraphic surfaces and sections, including kriging and GIS exports.
  • Geophysics: import, georeference, filter and overlay magnetometry, resistivity, GPR time-slice and electromagnetic grids.

Other extensions cover underwater surveys, point-cloud interoperability, Blender/Extended Matrix and optional AI workflows. Dependencies vary by extension: the core's CPU processing does not mean every optional integration has the same hardware requirements. In particular, the Gaussian-splatting extension uses Spirula Studio and Vulkan-capable graphics hardware.

Extensions are Python packages that register actions, commands or export formats. They can be maintained independently and proposed for the shared plugin index. The repository includes a template and documents ppg plugins new NAME for generating a starting project.

I'd particularly welcome feedback on GeoPackage/PostGIS interoperability, coordinate-system handling and reproducible field-to-GIS workflows. Which exchange or validation steps would make this easier to evaluate alongside the tools you already use?

Disclosure: this English introduction was prepared with AI assistance from the project documentation.



Discuss this on our forum.