Piero Toffanin
Piero Toffanin
Hello :hand: This PR proposes the addition of a second attempt in order to fix faulty XML in XMP tags from cameras that have malformed/invalid XML. It doesn't change the...
Hey all :hand: I've been looking at the possibility to implement scale constraints for datasets that have no georeferencing information (no GPS and no GCPs). The use case is that...
Currently outputs from ODM have slightly uneven cell raster sizes: ``` >>> import rasterio; rasterio.open("/datasets/brighton2/odm_orthophoto/odm_orthophoto.tif").transform Affine(0.04999088883357982, 0.0, 576647.5603842067, 0.0, -0.0499903086638842, 5188220.140716478) >>> ``` This could be improved.
Since Ubuntu 21.04 has reached end of life and it's starting to show some update issues during build.
Allow boundaries to define areas which should not be included (e.g. outline of a building) instead of defining the boundaries which should be included.
We should be able to trim shots before densification if a shot's triangulated points fall outside of the defined boundary, thus speeding up reconstruction.
Improves multispectral calibration / processing. TODO: - [ ] Improve parameter passing (JSON file instead of multiple command line parameters) - [ ] Testing
It has been suggested that the software could add scale constraints as described here https://community.opendronemap.org/t/scale-constraint/3622/4 This might need a different type of annotation file (similar to GCPs).
Currently ODM does not generate PDF reports when using split-merge. It could be possible to generate them by: - Recomputing/aggregating stats from submodels - Write a new report generation code...