Two 'surfaces' in point-cloud

lupionpe

I do not know if you had this experience before, but in my processing I got some areas with two different surfaces in the same place in the point cloud.

The flight was done using nadir and oblique images (>80% overlap), I used gcp.txt and geo.txt since my drone has an RTK antenna (Mavic 3M) and the processing flags were:

auto-boundary:true, feature-quality:high, min-num-features:30000, matcher-neighbors:32, gps-accuracy:0.25, pc-quality:high, pc-filter:2, pc-sample:0.05, pc-classify:true, orthophoto-resolution:1, use-3dmesh:true

Any ideas on the why and maybe what I can do to get a more accurate result?

The whole area has vegetation (some dense, some not so much). But this one in particular not so much.

27 Replies

YanNoun

How does the quality report look like ?

YanNoun

One or two flights ?

lupionpe OP

Was a crosshatch flight

YanNoun

The report looks decent although :

  • The pixel residual are skewed are bigger than expected.
  • Did you flight everything at once, or did the drone landed in between ?
  • The GCP residual is what it should be.

But given the two surfaces issues, I’d say it’s more a matching issue. But the residual issue indicates maybe a modeling problem (like we assume one camera model and one shift when maybe with N flight we should consider N).

Do you have/do you know how to find and share with me the config.yaml OpenSfM file ?

lupionpe OP

Landed, i took 4 batteries

lupionpe OP

config.yaml OpenSfM file

pierotofy
/var/www/data/<uuid>/opensfm/config.yaml
lupionpe OP
YanNoun

Great, thanks ! Do you have the log by chance ?

YanNoun Best answer

So there’s 3 reconstructions, so for sure, the results isn’t one continuous chunk, which might explain the double surface :

INFO] Reconstruction 0: 797 images, 834843 points
[INFO] Reconstruction 1: 597 images, 640255 points
[INFO] Reconstruction 2: 139 images, 147306 points
[INFO] 3 partial reconstructions in total.
[WARNING] Multiple reconstructions detected (3), this might be an indicator that some areas did not have sufficient overlap
[INFO] Attempting merge

👍 1
YanNoun

So I’d say the matching wasn’t powerful enough to bridge some gaps (?) Do you have the stats/stats.json somewhere (it’s the quality report raw data).

Otherwise, happy to play with the data if you can share

pierotofy

When your images don't have enough features / overlap, the program fails to create a single reconstruction; instead, it creates multiple disjoint ones. The program later tries to merge those, but large errors and misalignment can be present.

lupionpe OP

I see, is there a 'flag' i can use to try to 'force' into one?
Overlap i know it has, maybe increase feature-quality, min-num-features, matcher-neighbors?

pierotofy

Try: Increase min-num-features,
Change feature-type to akaze.
Lower feature-quality to medium (yes, it's counter-intuitive, but it can help reconstruct certain difficult forest areas)

👍 1
lupionpe OP

Nice, i queu to my node to run:

  1. feature-quality: medium, min-num-features: 60000
  2. feature-quality: medium, min-num-features: 60000, feature-type:akaze

In ~12h we will have the results!

Guys, tks a lot for the help

lupionpe OP

On both (using akaze and not using it) it still gets the 'two layers'.

pierotofy

Was worth a shot, you probably need more overlap, fly at higher altitude, or both

lupionpe OP

i will try on a next survey

lupionpe OP

Tks for the help

GenAnon

Are these flights at different times? Do these flights pause for a battery swap?
I just thought maybe it’s your take off location. If the point you’re taking off between flights is slightly higher or lower it changes your perspective of your camera.
I ran a training flight where I took off from ground first. Swapped a battery and then took off from the top of the case. My gimbal was -45 but my expected agl was off the height of the case; about one foot.
If your mission has locked gimbal angle (obliques) or maybe a locked atl then perhaps a slight change of takeoff height is altering the modeled ground level.

lupionpe OP

They happen sequencially with pause for battery swap; but take off was from the same location.

Need more help?

This discussion happened in the WebODM community Discord. Join and ask your own question.

Join View Original Thread

This page mirrors a public discussion from the WebODM Discord. How to request a removal.