pyarchinit-photogrammetry 0.2.0__tar.gz → 0.3.0__tar.gz

{pyarchinit_photogrammetry-0.2.0 → pyarchinit_photogrammetry-0.3.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: pyarchinit-photogrammetry
-Version: 0.2.0
+Version: 0.3.0
 Summary: Open-source photogrammetry engine for archaeology and BIM, integrated with PyArchInit
 Author-email: Enzo Cocca <enzo.ccc@gmail.com>
 License-Expression: GPL-2.0-or-later
@@ -30,7 +30,7 @@ Requires-Dist: laspy>=2.4
 Requires-Dist: sqlalchemy>=2.0
 Requires-Dist: typer>=0.9
 Provides-Extra: mesh
-Requires-Dist: open3d>=0.18; extra == "mesh"
+Requires-Dist: open3d!=0.20.0,>=0.18; extra == "mesh"
 Provides-Extra: bim
 Requires-Dist: ifcopenshell>=0.8; extra == "bim"
 Provides-Extra: postgis
@@ -41,16 +41,22 @@ Requires-Dist: sam2>=1.1; extra == "sam"
 Provides-Extra: gui
 Requires-Dist: PySide6>=6.6; extra == "gui"
 Requires-Dist: pyvista>=0.43; extra == "gui"
-Requires-Dist: pyvistaqt>=0.11; extra == "gui"
+Requires-Dist: pyvistaqt>=0.13; extra == "gui"
+Requires-Dist: qtawesome>=1.3; extra == "gui"
 Provides-Extra: all
-Requires-Dist: open3d>=0.18; extra == "all"
+Requires-Dist: open3d!=0.20.0,>=0.18; extra == "all"
 Requires-Dist: ifcopenshell>=0.8; extra == "all"
 Requires-Dist: psycopg2-binary>=2.9; extra == "all"
 Requires-Dist: PySide6>=6.6; extra == "all"
 Requires-Dist: pyvista>=0.43; extra == "all"
-Requires-Dist: pyvistaqt>=0.11; extra == "all"
+Requires-Dist: pyvistaqt>=0.13; extra == "all"
+Requires-Dist: qtawesome>=1.3; extra == "all"
 Provides-Extra: dev
 Requires-Dist: pytest>=7; extra == "dev"
+Provides-Extra: build
+Requires-Dist: pyinstaller>=6.10; extra == "build"
+Requires-Dist: pyinstaller-hooks-contrib>=2024.8; extra == "build"
+Requires-Dist: pillow>=9.1; extra == "build"
 Dynamic: license-file
 
 # pyarchinit-photogrammetry
@@ -64,51 +70,128 @@ cut/fill volumes, point-cloud classification, Segment Anything 2.1, IFC export,
 publishing into a PyArchInit database. Everything is scriptable in Python and runs on CPU,
 Apple Silicon included.
 
-> Status: **alpha (0.2)**. Python library, command line and desktop interface (on the same API,
-> with a built-in Python console). Italian version: [README.it.md](README.it.md).
+> Status: **alpha (0.3)**. Python library, command line and desktop application (on the same
+> API, with a built-in Python console). Italian version: [README.it.md](README.it.md).
 
-## Installation
+## Desktop application (no Python needed)
+
+Download the build for your system from the
+[Releases](https://github.com/enzococca/pyarchinit-photogrammetry/releases) page:
+
+| Platform | File |
+| --- | --- |
+| macOS 15 or newer (Apple Silicon) | `PyArchInit-Photogrammetry-<version>-macos-arm64.dmg` |
+| Windows 10/11 (64 bit) | `PyArchInit-Photogrammetry-<version>-windows-x64.zip` |
+
+Open the disk image and drag the app to *Applications* (macOS), or unzip and run
+`PyArchInit Photogrammetry.exe` (Windows). The application starts on a page with *Nuovo
+progetto*, *Apri progetto* and *Progetto demo*: the demo creates a synthetic trench and a
+bowl on a turntable and processes them in a few minutes. If PyArchInit 5 is installed
+(`~/pyarchinit_5`), the interface connects to its database at start and the demo database is
+written inside `pyarchinit_DB_folder` so that QGIS can open it too; PostgreSQL/PostGIS servers
+are reachable from *PyArchInit > Connetti*. The builds are unsigned: on macOS right-click > *Open*
+the first time (or `xattr -dr com.apple.quarantine "/Applications/PyArchInit Photogrammetry.app"`),
+on Windows choose *More info > Run anyway*. Details in [docs/packaging.md](docs/packaging.md).
+
+## Installation with pip
+
+Use a dedicated virtual environment (not the Anaconda `base` environment, see
+*Troubleshooting*). With [uv](https://docs.astral.sh/uv/):
+
+```bash
+uv venv --seed --python 3.12 ~/venvs/ppg && source ~/venvs/ppg/bin/activate
+uv pip install "pyarchinit-photogrammetry[all]"      # engine, mesh (Open3D), IFC, PostGIS, desktop GUI
+```
+
+With the standard tools:
 
 ```bash
-pip install "pyarchinit-photogrammetry[all]"      # mesh (Open3D), IFC, PostGIS, desktop GUI
-pip install "pyarchinit-photogrammetry[sam]"      # optional: Segment Anything 2.1 (PyTorch)
+python3 -m venv ~/venvs/ppg && source ~/venvs/ppg/bin/activate   # Windows: ~\venvs\ppg\Scripts\activate
+pip install -U pip && pip install "pyarchinit-photogrammetry[all]"
 ```
 
+Optional: `pip install "pyarchinit-photogrammetry[sam]"` adds Segment Anything 2.1 (PyTorch).
+A global `ppg`/`ppg-gui` without activating anything: `uv tool install "pyarchinit-photogrammetry[all]"`
+(or `pipx install`).
+
 From source:
 
 ```bash
 git clone https://github.com/enzococca/pyarchinit-photogrammetry
 cd pyarchinit-photogrammetry
-pip install -e ".[all,dev]"
+uv venv --seed --python 3.12 .venv && source .venv/bin/activate
+uv pip install -e ".[all,dev]"
 pytest -q
 ```
 
-Python 3.10+. Writing geometries into a PyArchInit **SQLite** database needs `mod_spatialite`
+Python 3.10-3.12. Writing geometries into a PyArchInit **SQLite** database needs `mod_spatialite`
 (found automatically in QGIS, MacPorts, Homebrew and Linux locations, or set
-`SPATIALITE_LIBRARY_PATH`).
-
-On headless Linux servers Open3D needs the EGL/GL libraries:
+`SPATIALITE_LIBRARY_PATH`). On headless Linux servers Open3D needs the EGL/GL libraries:
 `sudo apt-get install libegl1 libgl1 libgomp1`.
 
-## Try it with the demo data
+## Start
 
 ```bash
-ppg demo ~/ppg_demo --process     # synthetic trench photos + 8 targets, pottery meshes, PyArchInit DB
-ppg-gui ~/ppg_demo/scavo.ppg      # open the processed project in the interface
+ppg doctor                        # checks the environment and says what to fix
+ppg demo ~/ppg_demo --process     # synthetic trench + 8 targets, bowl on a turntable, pottery meshes, PyArchInit DB
+ppg-gui ~/ppg_demo/scavo.ppg      # open the processed trench in the interface
+ppg-gui ~/ppg_demo/ceramica/ceramica.ppg   # the bowl (local metric frame from the turntable targets)
+ppg-gui                           # start page: new, open, demo, recent projects
 ```
 
-Or from the interface: **File > Crea e apri progetto demo**. `LEGGIMI.txt` in the folder lists
-what to try (sections, contours, pottery profile of the sherd, publishing to PyArchInit).
+`ppg-gui` is the same as `ppg gui` and `python -m pyarchinit_photogrammetry.gui`. The
+interface writes a log in `~/Library/Logs/pyarchinit-photogrammetry` (macOS),
+`%LOCALAPPDATA%\pyarchinit-photogrammetry\logs` (Windows) or `~/.local/state/pyarchinit-photogrammetry/logs`
+(Linux); *Aiuto > Apri cartella dei log* opens it.
+
+## Troubleshooting
+
+* **`ppg-gui` does nothing, or crashes on start.** Run `ppg doctor`. A frequent cause is an
+  old copy of the package installed in another Python (for example Anaconda's `base`) that
+  comes first on `PATH`: activate the right environment (`which ppg-gui` must point inside it)
+  or uninstall the other copy (`/opt/anaconda3/bin/python -m pip uninstall pyarchinit-photogrammetry`).
+* **Anaconda `base` environment**: its SciPy wheels may not load on recent macOS
+  (`ImportError ... __thread_bss ... zero-fill section`) and its PROJ data is picked up by
+  rasterio. Use a dedicated virtual environment; `PROJ_LIB`/`PROJ_DATA`/`GDAL_DATA` exported
+  by Anaconda or QGIS are redirected to the data bundled with rasterio.
+* **The mesh step says "Poisson reconstruction failed... height field instead".** Poisson
+  reconstruction runs in a separate process because PoissonRecon (Open3D) can crash on some
+  clouds; the pipeline retries and then builds a 2.5D surface. Open3D 0.20.0 crashes
+  systematically on macOS and is excluded (`open3d!=0.20.0`); 0.19 works.
+* **Native dialogs crashing on macOS 26/27** (`NSInternalInconsistencyException ...
+  targetSizeInPoints`): the interface uses Qt's own message boxes, no action needed.
+* **The 3D view hangs on macOS**: pyvistaqt older than 0.13 hangs on start; `pip install -U pyvistaqt`.
+
+## Screenshots
+
+| | |
+| --- | --- |
+| ![Start page](docs/img/gui-start.png) | ![Layers, sections and PyArchInit](docs/img/gui-layers.png) |
+| ![Connection to PyArchInit](docs/img/connect.png) | ![IFC elements per stratigraphic unit](docs/img/ifc-units.png) |
+| ![Bowl from the turntable demo](docs/img/gui-pottery.png) | ![Profile drawing of the bowl](docs/img/demo-profile.png) |
+
+Top right: the orthomosaic/DEM view with the US polygons loaded from PyArchInit, contour lines
+and a section trace as layers, the *Sezioni* pane with the drawing, and the PyArchInit pane.
+Middle right: the IFC export opened with IfcOpenShell, one element per unit. Bottom: the bowl
+of the turntable demo reconstructed from 32 synthetic photos and its profile drawing (rim
+16.0 cm measured against 16.0 cm true).
 
 ## Desktop interface
 
-`ppg-gui` (or `ppg gui`) opens the desktop application (Italian UI): workspace with chunks,
-cameras, markers and products; 3D view (VTK, with a software fallback renderer); orthomosaic
-and DEM view with drawing tools (stratigraphic units, section traces, measurements, spot
-heights, SAM 2.1 prompts); photo view with manual marker placement; reference pane with
-GCP and check point errors; Python console bound to the project (`doc`, `chunk`); background
-processing with progress and cancel; a PyArchInit menu to connect, publish orthophotos, DEMs
-and models, and write unit polygons and spot heights. See [docs/gui.md](docs/gui.md).
+`ppg-gui` opens the desktop application (Italian UI): start page with recent projects; a
+toolbar with the workflow (photos, markers, alignment, references, dense cloud, model,
+texture, DEM, orthophoto, *Elabora tutto*); workspace with chunks, cameras, markers and
+products; 3D view (VTK, with a software fallback renderer); orthomosaic and DEM view with
+drawing tools (stratigraphic units, section traces, measurements, spot heights, SAM 2.1
+prompts); photo view with manual marker placement; reference pane with GCP and check point
+errors; Python console bound to the project (`doc`, `chunk`); background processing with
+progress, cancel and a status-bar indicator; a drawing toolbar and a *Layer* pane (show/hide,
+zoom, attributes on click) for units, sections, contour lines and spot heights; a *Sezioni*
+pane with the drawings; a log pane with level filter, search, copy and
+save; error windows with a hint, the traceback and a *Copia* button; light and dark themes;
+*Aiuto > Diagnostica ambiente* (the same checks as `ppg doctor`); a PyArchInit menu to
+connect, publish orthophotos, DEMs and models, and write unit polygons and spot heights.
+See [docs/gui.md](docs/gui.md).
 
 ## Quick start (Python)
 
@@ -152,7 +235,7 @@ then `ppg.app.document` inside the script (in the GUI: **Strumenti > Esegui scri
 | --- | --- |
 | 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 |
+| Products | Point cloud (PLY/LAS 1.4 with classes), mesh (Poisson in an isolated process with automatic fallback, 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` |
@@ -209,16 +292,18 @@ median error < 3 mm, orthophoto target positions < 5 mm.
 ```
 pyarchinit_photogrammetry/
   core/        Document, Chunk, Camera, Sensor, Marker, ScaleBar, PointCloud, CRS
-  engine/      sfm (pycolmap), dense, meshing, texturing, dem, ortho, visibility
+  engine/      sfm (pycolmap), dense, meshing, isolate (crash-proof workers), texturing, dem, ortho
   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
-  gui/         desktop interface (PySide6, pyvista)
+  gui/         desktop interface (PySide6, pyvista, qtawesome icons, themes, log, start page)
+  doctor.py    environment diagnosis (`ppg doctor`)
   demo.py      demo data set
   cli.py       `ppg` command
+packaging/     PyInstaller spec and build script for the desktop application
 ```
 
 Projects are a JSON file (`name.ppg`) plus a folder (`name.ppg.files/`) with the data of each

pyarchinit_photogrammetry-0.3.0/README.md

@@ -0,0 +1,256 @@
+# pyarchinit-photogrammetry
+
+Open-source photogrammetry engine for archaeology and heritage BIM, integrated with
+[PyArchInit](https://github.com/pyarchinit/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.3)**. Python library, command line and desktop application (on the same
+> API, with a built-in Python console). Italian version: [README.it.md](README.it.md).
+
+## Desktop application (no Python needed)
+
+Download the build for your system from the
+[Releases](https://github.com/enzococca/pyarchinit-photogrammetry/releases) page:
+
+| Platform | File |
+| --- | --- |
+| macOS 15 or newer (Apple Silicon) | `PyArchInit-Photogrammetry-<version>-macos-arm64.dmg` |
+| Windows 10/11 (64 bit) | `PyArchInit-Photogrammetry-<version>-windows-x64.zip` |
+
+Open the disk image and drag the app to *Applications* (macOS), or unzip and run
+`PyArchInit Photogrammetry.exe` (Windows). The application starts on a page with *Nuovo
+progetto*, *Apri progetto* and *Progetto demo*: the demo creates a synthetic trench and a
+bowl on a turntable and processes them in a few minutes. If PyArchInit 5 is installed
+(`~/pyarchinit_5`), the interface connects to its database at start and the demo database is
+written inside `pyarchinit_DB_folder` so that QGIS can open it too; PostgreSQL/PostGIS servers
+are reachable from *PyArchInit > Connetti*. The builds are unsigned: on macOS right-click > *Open*
+the first time (or `xattr -dr com.apple.quarantine "/Applications/PyArchInit Photogrammetry.app"`),
+on Windows choose *More info > Run anyway*. Details in [docs/packaging.md](docs/packaging.md).
+
+## Installation with pip
+
+Use a dedicated virtual environment (not the Anaconda `base` environment, see
+*Troubleshooting*). With [uv](https://docs.astral.sh/uv/):
+
+```bash
+uv venv --seed --python 3.12 ~/venvs/ppg && source ~/venvs/ppg/bin/activate
+uv pip install "pyarchinit-photogrammetry[all]"      # engine, mesh (Open3D), IFC, PostGIS, desktop GUI
+```
+
+With the standard tools:
+
+```bash
+python3 -m venv ~/venvs/ppg && source ~/venvs/ppg/bin/activate   # Windows: ~\venvs\ppg\Scripts\activate
+pip install -U pip && pip install "pyarchinit-photogrammetry[all]"
+```
+
+Optional: `pip install "pyarchinit-photogrammetry[sam]"` adds Segment Anything 2.1 (PyTorch).
+A global `ppg`/`ppg-gui` without activating anything: `uv tool install "pyarchinit-photogrammetry[all]"`
+(or `pipx install`).
+
+From source:
+
+```bash
+git clone https://github.com/enzococca/pyarchinit-photogrammetry
+cd pyarchinit-photogrammetry
+uv venv --seed --python 3.12 .venv && source .venv/bin/activate
+uv pip install -e ".[all,dev]"
+pytest -q
+```
+
+Python 3.10-3.12. Writing geometries into a PyArchInit **SQLite** database needs `mod_spatialite`
+(found automatically in QGIS, MacPorts, Homebrew and Linux locations, or set
+`SPATIALITE_LIBRARY_PATH`). On headless Linux servers Open3D needs the EGL/GL libraries:
+`sudo apt-get install libegl1 libgl1 libgomp1`.
+
+## Start
+
+```bash
+ppg doctor                        # checks the environment and says what to fix
+ppg demo ~/ppg_demo --process     # synthetic trench + 8 targets, bowl on a turntable, pottery meshes, PyArchInit DB
+ppg-gui ~/ppg_demo/scavo.ppg      # open the processed trench in the interface
+ppg-gui ~/ppg_demo/ceramica/ceramica.ppg   # the bowl (local metric frame from the turntable targets)
+ppg-gui                           # start page: new, open, demo, recent projects
+```
+
+`ppg-gui` is the same as `ppg gui` and `python -m pyarchinit_photogrammetry.gui`. The
+interface writes a log in `~/Library/Logs/pyarchinit-photogrammetry` (macOS),
+`%LOCALAPPDATA%\pyarchinit-photogrammetry\logs` (Windows) or `~/.local/state/pyarchinit-photogrammetry/logs`
+(Linux); *Aiuto > Apri cartella dei log* opens it.
+
+## Troubleshooting
+
+* **`ppg-gui` does nothing, or crashes on start.** Run `ppg doctor`. A frequent cause is an
+  old copy of the package installed in another Python (for example Anaconda's `base`) that
+  comes first on `PATH`: activate the right environment (`which ppg-gui` must point inside it)
+  or uninstall the other copy (`/opt/anaconda3/bin/python -m pip uninstall pyarchinit-photogrammetry`).
+* **Anaconda `base` environment**: its SciPy wheels may not load on recent macOS
+  (`ImportError ... __thread_bss ... zero-fill section`) and its PROJ data is picked up by
+  rasterio. Use a dedicated virtual environment; `PROJ_LIB`/`PROJ_DATA`/`GDAL_DATA` exported
+  by Anaconda or QGIS are redirected to the data bundled with rasterio.
+* **The mesh step says "Poisson reconstruction failed... height field instead".** Poisson
+  reconstruction runs in a separate process because PoissonRecon (Open3D) can crash on some
+  clouds; the pipeline retries and then builds a 2.5D surface. Open3D 0.20.0 crashes
+  systematically on macOS and is excluded (`open3d!=0.20.0`); 0.19 works.
+* **Native dialogs crashing on macOS 26/27** (`NSInternalInconsistencyException ...
+  targetSizeInPoints`): the interface uses Qt's own message boxes, no action needed.
+* **The 3D view hangs on macOS**: pyvistaqt older than 0.13 hangs on start; `pip install -U pyvistaqt`.
+
+## Screenshots
+
+| | |
+| --- | --- |
+| ![Start page](docs/img/gui-start.png) | ![Layers, sections and PyArchInit](docs/img/gui-layers.png) |
+| ![Connection to PyArchInit](docs/img/connect.png) | ![IFC elements per stratigraphic unit](docs/img/ifc-units.png) |
+| ![Bowl from the turntable demo](docs/img/gui-pottery.png) | ![Profile drawing of the bowl](docs/img/demo-profile.png) |
+
+Top right: the orthomosaic/DEM view with the US polygons loaded from PyArchInit, contour lines
+and a section trace as layers, the *Sezioni* pane with the drawing, and the PyArchInit pane.
+Middle right: the IFC export opened with IfcOpenShell, one element per unit. Bottom: the bowl
+of the turntable demo reconstructed from 32 synthetic photos and its profile drawing (rim
+16.0 cm measured against 16.0 cm true).
+
+## Desktop interface
+
+`ppg-gui` opens the desktop application (Italian UI): start page with recent projects; a
+toolbar with the workflow (photos, markers, alignment, references, dense cloud, model,
+texture, DEM, orthophoto, *Elabora tutto*); workspace with chunks, cameras, markers and
+products; 3D view (VTK, with a software fallback renderer); orthomosaic and DEM view with
+drawing tools (stratigraphic units, section traces, measurements, spot heights, SAM 2.1
+prompts); photo view with manual marker placement; reference pane with GCP and check point
+errors; Python console bound to the project (`doc`, `chunk`); background processing with
+progress, cancel and a status-bar indicator; a drawing toolbar and a *Layer* pane (show/hide,
+zoom, attributes on click) for units, sections, contour lines and spot heights; a *Sezioni*
+pane with the drawings; a log pane with level filter, search, copy and
+save; error windows with a hint, the traceback and a *Copia* button; light and dark themes;
+*Aiuto > Diagnostica ambiente* (the same checks as `ppg doctor`); a PyArchInit menu to
+connect, publish orthophotos, DEMs and models, and write unit polygons and spot heights.
+See [docs/gui.md](docs/gui.md).
+
+## Quick start (Python)
+
+```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:
+
+```bash
+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 (in the GUI: **Strumenti > Esegui script Python**).
+
+## 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 in an isolated process with automatic fallback, 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
+
+```python
+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](docs/pyarchinit.md).
+
+## Pottery from a turntable
+
+```bash
+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:
+
+```bash
+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, isolate (crash-proof workers), texturing, dem, ortho
+  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
+  gui/         desktop interface (PySide6, pyvista, qtawesome icons, themes, log, start page)
+  doctor.py    environment diagnosis (`ppg doctor`)
+  demo.py      demo data set
+  cli.py       `ppg` command
+packaging/     PyInstaller spec and build script for the desktop application
+```
+
+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

{pyarchinit_photogrammetry-0.2.0 → pyarchinit_photogrammetry-0.3.0}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "pyarchinit-photogrammetry"
-version = "0.2.0"
+version = "0.3.0"
 description = "Open-source photogrammetry engine for archaeology and BIM, integrated with PyArchInit"
 readme = "README.md"
 license = "GPL-2.0-or-later"
@@ -37,14 +37,15 @@ dependencies = [
 ]
 
 [project.optional-dependencies]
-mesh = ["open3d>=0.18"]
+mesh = ["open3d>=0.18,!=0.20.0"]
 bim = ["ifcopenshell>=0.8"]
 postgis = ["psycopg2-binary>=2.9"]
 sam = ["torch>=2.3", "sam2>=1.1"]
-gui = ["PySide6>=6.6", "pyvista>=0.43", "pyvistaqt>=0.11"]
-all = ["open3d>=0.18", "ifcopenshell>=0.8", "psycopg2-binary>=2.9", "PySide6>=6.6", "pyvista>=0.43",
-       "pyvistaqt>=0.11"]
+gui = ["PySide6>=6.6", "pyvista>=0.43", "pyvistaqt>=0.13", "qtawesome>=1.3"]
+all = ["open3d>=0.18,!=0.20.0", "ifcopenshell>=0.8", "psycopg2-binary>=2.9", "PySide6>=6.6", "pyvista>=0.43",
+       "pyvistaqt>=0.13", "qtawesome>=1.3"]
 dev = ["pytest>=7"]
+build = ["pyinstaller>=6.10", "pyinstaller-hooks-contrib>=2024.8", "pillow>=9.1"]
 
 [project.scripts]
 ppg = "pyarchinit_photogrammetry.cli:main"

{pyarchinit_photogrammetry-0.2.0 → pyarchinit_photogrammetry-0.3.0}/src/pyarchinit_photogrammetry/__init__.py

@@ -19,13 +19,20 @@ Quick start::
     chunk.build_orthomosaic()
     doc.save("scavo.ppg")
 """
-from .app import app
+from ._env import load_open3d_first as _load_open3d_first
+from ._env import use_bundled_proj_data as _use_bundled_proj_data
+
+_load_open3d_first()  # Open3D's OpenMP runtime must be bound before rasterio/scipy (see _env.py)
+
+_use_bundled_proj_data()  # before anything opens a CRS (see _env.py)
+
+from .app import app  # noqa: E402
 from .core import (ARCHAEO_CLASSES, ASPRS_CLASSES, Camera, Chunk, Document, Marker, PointCloud, Projection,
                    Reference, ScaleBar, Sensor)
 from .core.progress import Cancelled, Progress, print_progress
 from . import demo  # noqa: E402  (ppg.demo.create_demo)
 
-__version__ = "0.2.0"
+__version__ = "0.3.0"
 
 __all__ = ["app", "Document", "Chunk", "Camera", "Sensor", "Marker", "Projection", "Reference", "ScaleBar",
            "PointCloud", "ASPRS_CLASSES", "ARCHAEO_CLASSES", "Progress", "Cancelled", "print_progress", "__version__"]

pyarchinit_photogrammetry-0.3.0/src/pyarchinit_photogrammetry/_env.py

@@ -0,0 +1,62 @@
+"""Process-level fixes for mixed installations (Anaconda, QGIS, Homebrew).
+
+Anaconda and QGIS export ``PROJ_LIB``/``PROJ_DATA`` (and ``GDAL_DATA``) pointing at
+their own ``proj.db``. The rasterio wheel bundles a newer PROJ, which then refuses that
+database ("proj.db contains DATABASE.LAYOUT.VERSION.MINOR = 2 whereas a number
+>= 3 is expected") and every EPSG lookup fails. When rasterio ships its own PROJ
+data, point its GDAL/PROJ at it *and* rewrite the environment variables: PROJ
+creates one context per thread and each new context reads ``PROJ_DATA`` from the
+environment, so without the rewrite every EPSG lookup in a worker thread (all the
+background tasks of the interface) would still fail. pyproj wheels already prefer
+their bundled data. Nothing happens when rasterio has no bundled data (conda-forge
+or QGIS builds, whose PROJ matches the environment).
+"""
+from __future__ import annotations
+
+import os
+from pathlib import Path
+
+
+def use_bundled_proj_data() -> str | None:
+    """Return the directory now used by rasterio, or ``None`` when nothing changed."""
+    env = os.environ.get("PROJ_DATA") or os.environ.get("PROJ_LIB")
+    if not env:
+        return None
+    try:
+        import rasterio
+        from rasterio.env import set_proj_data_search_path
+    except Exception:  # pragma: no cover - rasterio missing or very old
+        return None
+    bundled = Path(rasterio.__file__).parent / "proj_data"
+    if not (bundled / "proj.db").exists():
+        return None  # conda-forge rasterio: its PROJ matches the environment
+    try:
+        if any(Path(p).resolve() == bundled.resolve() for p in env.split(os.pathsep) if p):
+            return None
+    except OSError:
+        pass
+    set_proj_data_search_path(str(bundled))
+    os.environ["PROJ_DATA"] = str(bundled)
+    os.environ["PROJ_LIB"] = str(bundled)
+    gdal_data = Path(rasterio.__file__).parent / "gdal_data"
+    if gdal_data.is_dir() and os.environ.get("GDAL_DATA"):
+        os.environ["GDAL_DATA"] = str(gdal_data)
+    return str(bundled)
+
+
+def load_open3d_first() -> None:
+    """Import Open3D before any other native library.
+
+    Open3D ships its own OpenMP runtime. When it is loaded after the ones that come
+    with rasterio, SciPy or scikit-learn, PoissonRecon (``create_from_point_cloud_poisson``)
+    crashes the process on macOS (segmentation fault or a silent ``exit(0)``).
+    Importing it first, in every process that imports this package, keeps the
+    reconstruction stable. Costs under a second; nothing happens without Open3D."""
+    import os
+
+    if os.environ.get("PPG_NO_OPEN3D"):
+        return
+    try:
+        import open3d  # noqa: F401
+    except Exception:  # pragma: no cover - optional dependency
+        pass

{pyarchinit_photogrammetry-0.2.0 → pyarchinit_photogrammetry-0.3.0}/src/pyarchinit_photogrammetry/bim/ifc.py

@@ -50,7 +50,9 @@ def export_ifc(path: str | Path, elements: list[IfcElement], crs: str | None = N
 
     model = ifcopenshell.file(schema="IFC4")
     proj = ifcopenshell.api.root.create_entity(model, ifc_class="IfcProject", name=project)
-    ifcopenshell.api.unit.assign_unit(model)
+    ifcopenshell.api.unit.assign_unit(model, length={"is_metric": True, "raw": "METERS"},
+                                      area={"is_metric": True, "raw": "METERS"},
+                                      volume={"is_metric": True, "raw": "METERS"})  # coordinates are metres
     ctx = ifcopenshell.api.context.add_context(model, context_type="Model")
     body = ifcopenshell.api.context.add_context(model, context_type="Model", context_identifier="Body",
                                                 target_view="MODEL_VIEW", parent=ctx)

{pyarchinit_photogrammetry-0.2.0 → pyarchinit_photogrammetry-0.3.0}/src/pyarchinit_photogrammetry/cli.py

@@ -264,14 +264,17 @@ def run(script: Path, project: Optional[Path] = None, args: list[str] = typer.Ar
 
 @app.command()
 def demo(folder: Path = typer.Argument(Path("ppg_demo"), help="destination folder"),
-         process: bool = typer.Option(False, help="also run the whole pipeline (about two minutes)"),
-         pyarchinit: bool = typer.Option(True, help="create the demo PyArchInit database")):
-    """Write demo data: trench photos + GCPs, a ready project, pottery meshes, a PyArchInit database."""
+         process: bool = typer.Option(False, help="also run the whole pipeline (about three minutes)"),
+         pyarchinit: bool = typer.Option(True, help="create the demo PyArchInit database"),
+         pottery: bool = typer.Option(True, help="also the turntable photos and project of the bowl")):
+    """Write demo data: trench photos + GCPs, a ready project, pottery meshes and turntable photos, a PyArchInit database."""
     from .demo import create_demo
 
-    d = create_demo(folder, process=process, with_pyarchinit=pyarchinit, progress=print_progress)
+    d = create_demo(folder, process=process, with_pyarchinit=pyarchinit, with_pottery=pottery, progress=print_progress)
     typer.echo(f"Project:    {d.project}")
     typer.echo(f"Pottery:    {d.vessel}  {d.sherd}")
+    if d.pottery_project:
+        typer.echo(f"Turntable:  {d.pottery_project}" + (f"  profile: {d.pottery_profile}" if d.pottery_profile else ""))
     if d.pyarchinit_home:
         typer.echo(f"PyArchInit: export PYARCHINIT_HOME={d.pyarchinit_home}")
     typer.echo(f"Read {d.folder / 'LEGGIMI.txt'}; open it in the interface with: ppg-gui {d.project}")
@@ -285,6 +288,14 @@ def gui(project: Optional[Path] = typer.Argument(None)):
     raise SystemExit(gui_main([str(project)] if project else []))
 
 
+@app.command()
+def doctor():
+    """Check the environment (libraries, known pitfalls) and print what to fix."""
+    from .doctor import main as doctor_main
+
+    raise SystemExit(doctor_main())
+
+
 # ------------------------------------------------------------------ markers
 @markers_app.command("sheet")
 def markers_sheet(out: Path, target_type: str = "aruco_4x4_50", codes: str = "0-11", size_mm: float = 40.0,