If a boundary is defined, the model becomes distorted.

Open
#1,937 4 comments 0 reactions 0 assignees View on GitHub

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

Start by reproducing the issue in WebODM 2.5.6 with 300–400 images, a GeoJSON boundary, and both auto-boundary and rolling-shutter enabled; compare it with the auto-boundary-only result and earlier versions if available. Done means the bounded configuration produces an undistorted model, or the cause and required fix are clearly identified.

Written by the indexing model from the issue text.

Description

I have identified an issue in WebODM version 2.5.6 that was not present in previous versions. In a project consisting of 300-400 images, I can generate the model without any issues when using the auto-boundary and rolling-shutter options. However, when I define a boundary using a GeoJSON polygon while both auto-boundary and rolling-shutter are set to true, the model becomes distorted. Has anyone else encountered this issue?

Dominant language
Python
Stars
6.5k
Forks
1.3k
Avg merge
5d 6h
Merged PRs (30d)
4

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from OpenDroneMap/ODM

All issues in OpenDroneMap/ODM

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.