Now then. Having got WebODM running natively in Windows (and loving it!), the next stage, perhaps inevitably, is trying to fine tune some of the settings to get the most out of it - and herein lies my problem.
When I processed a data set with WebODM, the buildings are a bit crinkly round the edges, as compared to the same data set processed in MapsMadeEasy. (see images attached)
Despite reading several threads on similar issues and referring to the most excellent “Missing Guide”, it seems that any tweak I make results in WebODM tripping up and giving an error message that the data set cannot be processed.
Is there anybody who can guide me through the tweaking process to optimize the settings for me, please? And also, why is WebODM tripping up? Is it my set up or am I just pushing it too hard?
Data set is c.550 images from Phantom 4 Pro. Using Intel i9 - 10900K with 128GB RAM on Windows 10 Pro.
Any pointers would be gratefully appreciated.