Possible Bug: pc-geometric breaking reconstruction on non-georeferenced data
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- python
- Domain
- computer-vision
Research direction
No source files, tests, dataset, or task log are identified in the issue. Start by reproducing reconstruction with non-georeferenced data and the default --pc-geometric setting, then trace the reconstruction stage that emits “Type 1 / Strange Values”; done means the failure is fixed or the option is disabled there with a log warning.
Written by the indexing model from the issue text.
Description
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
- Dominant language
- Python
- Stars
- 6.5k
- Forks
- 1.3k
- Avg merge
- 5d 6h
- Merged PRs (30d)
- 4
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from OpenDroneMap/ODM
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
OpenDroneMap/ODM#2031 · 6 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
OpenDroneMap/ODM#2073 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 65/100
OpenDroneMap/ODM#2068 · 4 comments · 1 reaction ·
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
OpenDroneMap/ODM#2043 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 52/100
OpenDroneMap/ODM#2034 · 1 comment ·
All issues in OpenDroneMap/ODM
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
bancolombia/sentinel#23 ·
-
test md OpenCI
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
bug client
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100