pyarchinit-photogrammetry
Open-source photogrammetry engine for archaeology and heritage BIM, integrated with PyArchInit.
From photos to georeferenced point clouds, meshes, DEMs and orthophotos, with the tools an excavation needs: coded targets, ground control, sections, pottery profiles, contour lines, cut/fill volumes, point-cloud classification, Segment Anything 2.1, IFC export, and direct publishing into a PyArchInit database. Everything is scriptable in Python and runs on CPU, Apple Silicon included.
Status: alpha (0.1). The Python library and the command line are ready; a desktop GUI built on the same API is the next step. Italian version: README.it.md.
Installation
pip install "pyarchinit-photogrammetry[all]" # mesh (Open3D), IFC, PostGIS
pip install "pyarchinit-photogrammetry[sam]" # optional: Segment Anything 2.1 (PyTorch)
From source:
git clone https://github.com/enzococca/pyarchinit-photogrammetry
cd pyarchinit-photogrammetry
pip install -e ".[all,dev]"
pytest -q
Python 3.10+. Writing geometries into a PyArchInit SQLite database needs mod_spatialite
(found automatically in QGIS, MacPorts, Homebrew and Linux locations, or set
SPATIALITE_LIBRARY_PATH).
Quick start (Python)
import pyarchinit_photogrammetry as ppg
doc = ppg.Document()
chunk = doc.add_chunk("Saggio 1")
chunk.add_photos(["foto/"])
chunk.detect_markers("aruco_4x4_50") # coded targets, decoded automatically
chunk.match_photos(quality="high")
chunk.align_cameras()
chunk.import_reference("gcp.csv", crs="EPSG:3004")
report = chunk.update_transform() # GCP georeferencing + accuracy report
print(report["control_rmse"])
chunk.build_depth_maps(quality="medium")
chunk.build_point_cloud()
chunk.build_model() # Poisson; surface="height_field" for terrain
chunk.build_texture()
chunk.build_dem() # GeoTIFF in the chunk CRS
chunk.build_orthomosaic() # GeoTIFF RGBA, true-ortho with occlusion test
chunk.generate_report("report.html")
doc.save("scavo.ppg")
The same workflow from the command line:
ppg markers sheet targets.pdf --codes 0-23 --size-mm 40 # print the targets
ppg process scavo.ppg foto/ --gcp gcp.csv --crs EPSG:3004 # whole pipeline + report
ppg export scavo.ppg --ortho ortho.tif --dem dem.tif --model model.obj --cloud cloud.las
Scripts can work on an open project, as in the GUI: ppg run myscript.py --project scavo.ppg,
then ppg.app.document inside the script.
What it does
| Area | Features |
|---|---|
| Alignment | SIFT features and matching, incremental SfM (COLMAP via pycolmap), camera calibration, bundle adjustment, tie points, pair selection (exhaustive, sequential, by GNSS position) |
| Dense | Depth maps and fusion on CPU (built-in), COLMAP PatchMatch on NVIDIA GPUs, OpenMVS when installed |
| Products | Point cloud (PLY/LAS 1.4 with classes), mesh (Poisson or 2.5D), texture atlas (OBJ+MTL+JPG), DEM, orthomosaic, hillshade, slope, HTML report |
| Markers | Printable ArUco/AprilTag sheets with scale bar, turntable mats with known layout, sub-pixel detection, triangulation, GCP/check points, scale bars, weighted 7-parameter transformation, any EPSG CRS (geographic GCPs go to the UTM zone) |
| Archaeology | Vertical sections and parallel cross sections, plan slices at a given elevation, DXF/SVG drawings at scale, contour lines, cut/fill volumes, pottery: rotation axis from sherds, profile, rim/base diameter, height, wall thickness, drawing with filled section |
| BIM | IFC4 export with IfcMapConversion + IfcProjectedCRS georeferencing, one element per stratigraphic unit with Pset_PyArchInit_US |
| AI | Rule-based classification (ground, vegetation, masonry, noise) with archaeological LAS classes 64-71; Segment Anything 2.1 on orthomosaics and photos, masks projected to the point cloud, automatic candidate units |
| PyArchInit | Reads config.cfg and the database (SQLite/SpatiaLite or PostgreSQL/PostGIS) without QGIS; publishes orthophotos, DEMs and 3D models as media with PyArchInit thumbnails, documentation records and footprints, US links, US polygons, spot heights, section traces, volumes |
PyArchInit integration
from pyarchinit_photogrammetry.pyarchinit import PyArchInit
pa = PyArchInit.connect() # the database configured in PyArchInit
pa.publish_orthomosaic(chunk, sito="Lagoi", nome_doc="Ortofoto saggio 1",
link_us=[("1", "101"), ("1", "102")])
pa.publish_dem(chunk, sito="Lagoi", nome_doc="DEM saggio 1")
pa.publish_model(chunk, sito="Lagoi", nome_doc="Modello saggio 1")
units = pa.us_polygons("Lagoi") # US polygons as shapely geometries
Conventions follow PyArchInit 5 (branch Stratigraph_00001): media_table,
media_thumb_table ({id}_{name}_thumb.png 150 px, {id}_{name}.png 2008x1417),
media_to_entity_table (US/us_table, REPERTO, CERAMICA, ...), documentazione_table
(Fotopiano, DEM, Modello tridimensionale, source Fotogrammetria), footprints in
pyarchinit_documentazione, polygons in pyunitastratigrafiche, heights in
pyarchinit_quote, sections in pyarchinit_sezioni, volumes in computo_metrico_table.
entity_uuid is filled when the column exists. Rasters are copied next to the thumbnail
folder (<media>/fotogrammetria/<site>/). See docs/pyarchinit.md.
Pottery from a turntable
ppg markers turntable mat.pdf --n 12 --diameter-mm 180 # also writes mat.csv
Photograph the vessel or sherd on the mat, process with --gcp mat.csv (local frame, mm
accuracy), then:
ppg pottery model.obj --out profilo.svg --scale 1 --title "US 101 n. 34"
The axis is estimated from the surface normals (works on sherds); with the turntable you
can impose it with --axis 0,0,0,0,0,1.
Accuracy check
The test suite renders a synthetic trench (4 x 3 m, a wall stub, 8 targets at known EPSG:3004 coordinates, 28 photos with lens distortion) and checks the products metrically: all photos aligned, control RMSE < 2 mm, independent check points < 3 mm, DEM median error < 3 mm, orthophoto target positions < 5 mm.
Architecture
pyarchinit_photogrammetry/
core/ Document, Chunk, Camera, Sensor, Marker, ScaleBar, PointCloud, CRS
engine/ sfm (pycolmap), dense, meshing, texturing, dem, ortho, visibility
markers/ coded targets, GCP import/export, georeferencing
archaeo/ sections, pottery, terrain (contours, volumes), stratigraphy (units)
bim/ IFC export
ai/ classification, SAM 2.1
pyarchinit/ config.cfg, database, media, high-level bridge
io/ EXIF, exports, report
cli.py `ppg` command
Projects are a JSON file (name.ppg) plus a folder (name.ppg.files/) with the data of each
chunk; photo paths inside the project folder are stored relative, so projects can be moved.
License
GNU GPL v2 or later, like PyArchInit. Third-party engines keep their licences (COLMAP BSD, OpenMVS AGPL when used as an external program, SAM 2.1 Apache 2.0).
Author: Enzo Cocca
Metadata
Release files for pyarchinit-photogrammetry 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| pyarchinit_photogrammetry-0.1.0.tar.gz | 102.6 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pyarchinit_photogrammetry-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 215.3 kB
Release files / pyarchinit_photogrammetry-0.1.0.tar.gz
| Download URL | pyarchinit_photogrammetry-0.1.0.tar.gz |
|---|---|
| Size | 102.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
893567885de7313021cd87e981ca3244b08c466a18c4a51e22d9097d3f36e178
|
|
BLAKE2b-256 checksum How to use checksums |
8909c2fa40bb5049b2b057e2353eed494a06a9fa0220714af5be464173a9a9ba
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 15, 2026.
Transparency logRelease files / pyarchinit_photogrammetry-0.1.0-py3-none-any.whl
| Download URL | pyarchinit_photogrammetry-0.1.0-py3-none-any.whl |
|---|---|
| Size | 112.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b5965634a596719aec02590729bbd43bf55d0de12831377a5ac4237c4a755b2b
|
|
BLAKE2b-256 checksum How to use checksums |
1fab0b76930b4b15660d7f4125c161fe9b8151301cb5f9f233fc98f9180e9cd6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 15, 2026.
Transparency logSecurity for pyarchinit-photogrammetry 0.1.0
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 2 files in this release have been uploaded with provenance metadata.
Attestation for pyarchinit_photogrammetry-0.1.0.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 15, 2026.
Transparency logA 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.