OpenDroneMap / OpenDroneMap/ODM
Fragmented Point Cloud Issue in WebODM on VPS
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 6.5k
- Forks
- 1.3k
- Avg merge
- 5d 6h
- Merged PRs (30d)
- 4
Description
I have a dataset consisting of 240 images. When processing it on a VPS ( WebODM 2.7.2) with 4 CPUs and 16GB RAM using the following parameters: “auto-boundary:true, rolling-shutter:true, dem-resolution:0.4, dsm:true, feature-quality:high, optimize-disk-space:true, max-concurrency:2, tiles:true, gps-accuracy:0.1, no-gpu:true, orthophoto-resolution:0.2, use-exif:true”, the point cloud appears fragmented.
However, when I run the same process on Desktop WebODM without “no-gpu”, the point cloud is clean. ( WebODM 2.7.2)
If I enable “no-gpu” on Desktop WebODM, the point cloud also becomes fragmented, just like on the VPS. The main issue is that even if I remove “no-gpu” or “max-concurrency:2” on the VPS WebODM, the point cloud still gets generated in a fragmented manner. I would greatly appreciate any help in resolving this issue.
(edit: transfer retired, so link removed -- edit by @smathermather)
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.
Research direction
The issue names no source files, tests, or entry points. Start by reproducing the dataset with the listed WebODM 2.7.2 parameters and compare GPU and no-GPU runs; done means identifying and fixing the cause of the fragmented point cloud, then verifying a clean result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- computer-vision
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100