Hi all,
One possible “pain point” that might fit this list is georeferencing/CRS consistency in cases where the reported metrics look fine, but the result is clearly off in real-world coordinates.
I ran into a case where the GCP errors looked very good, but the alignment “in reality” was not consistent. The discussion is here: GCP show very good results, but is not what I see in reality
Yann later shared a fix on the OpenSfM side (consistent proj/transform handling), which improved results significantly in that dataset: Commits · YanNoun/OpenSfM · GitHub
And there is also an ODM PR related to this topic: Try to fix georeferencing accuracy by originlake · Pull Request #1851 · OpenDroneMap/ODM · GitHub
My question (mostly to avoid duplicating work): is this class of CRS / proj-transform issue still present in current ODM/WebODM releases, or has it already been integrated somewhere? If it’s not fully merged yet, I’m also curious what the preferred path is (e.g., backporting into ODM, additional validation, test coverage, etc.).
Happy to help test with the same dataset again or provide any reproducible notes if that’s useful.