You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
How did you install ODM? (Docker, installer, natively, ...)?
Any
What is the problem?
Users are reporting that reconstruction can fail with Type 1 / Strange Values when --pc-geometric (default on, now) is used against datasets without georeference information.
What should be the expected behavior? If this is a feature request, please describe in detail the changes you think should be made to the code, citing files and lines where changes should be made, if possible.
If --pc-geometric can be used without georeference, it needs to be fixed. If it can not, it needs to be disabled during the appropriate stage with a log warning.
How can we reproduce this? What steps did you do to trigger the problem? If this is an issue with processing a dataset, YOU MUST include a copy of your dataset AND task output log, uploaded on Google Drive or Dropbox (otherwise we cannot reproduce this).
Pending
The text was updated successfully, but these errors were encountered:
The issue with pc-geometric causing problems is probably unrelated to the non-georeferenced nature of datasets, but more likely to the shape of the subjects in the scene.
How did you install ODM? (Docker, installer, natively, ...)?
Any
What is the problem?
Users are reporting that reconstruction can fail with Type 1 / Strange Values when
--pc-geometric
(default on, now) is used against datasets without georeference information.https://community.opendronemap.org/t/better-results-on-surfaces-with-pre-odm-3-0-0/15547/12?u=saijin_naib
What should be the expected behavior? If this is a feature request, please describe in detail the changes you think should be made to the code, citing files and lines where changes should be made, if possible.
If
--pc-geometric
can be used without georeference, it needs to be fixed. If it can not, it needs to be disabled during the appropriate stage with a log warning.How can we reproduce this? What steps did you do to trigger the problem? If this is an issue with processing a dataset, YOU MUST include a copy of your dataset AND task output log, uploaded on Google Drive or Dropbox (otherwise we cannot reproduce this).
Pending
The text was updated successfully, but these errors were encountered: