WebODM 1.9.14 fails where an Old Version had success.Is it possibile to disable GPS position during the reconstruction?

Not using GPU feature extraction is likely to give a slightly better result, but it will take a bit longer with CPU.

I did see that same group of incorrectly placed camera positions on my first attempt with default settings.
How many features are you finding with those settings?

1 Like

WebODM on PC With GPU enabled Version 1.9.18
Load and prepare mesh:
Reading PLY: 57466 verts… 113966 faces… done.
Generating texture views:
NVM: Loading file…
NVM: Number of views: 200
NVM: Number of features: 235962

[Pieve di San Lorenzo a Monte - 6/2/2023](javascript:void(0):wink:

202

00:39:22

Completato

Creato il: 14/2/2023, 12:11:05
Nodo di elaborazione: node-odm-1 (manuale)
Opzioni: auto-boundary: true, bg-removal: true, mesh-octree-depth: 12, mesh-size: 500000, min-num-features: 20000, pc-filter: 0, pc-quality: high, sky-removal: true, sm-no-align: true, use-hybrid-bundle-adjustment: true
GSD medio: 0,11 cm
Superficie: 122,12 m²
Punti ricostruiti: 21.717.931
Output attività: OnOff
1 Like

This dataset tends to create unmatched reconstructions. Besides the matching issue that leaves a hole in the model, there is another issue related to merging reconstructions.
Previously, only the largest reconstruction will be used for following processing, but in newer ODM, it will try to merge all reconstructions into a single one and will cause noise especially when GPS is inaccurate. Trying to delete those misplaced cameras(images) could be helpful.

2 Likes

I removed DJI_0219 and DJI_0220. Using feature-quality:medium, sky-removal:true and keeping all the others default can get good results

1 Like

Oh… The newer version keep anything! I don’t know if Is a good chioce, but thx ti solve the mistery.

1 Like

It was a tough choice, but people consistently asked for us to return as much as we can, and sometimes there are downsides, it seems.

Great job pruning the bad cameras, Thor.

3 days to understand the issue is always a good chioce to help the community.
I’m running the pruned dataset… Wait some minutes and I’ll be back.
Finger cross!

2 Likes

Is this type of work something you do often? A multichannel GPS (often RTK) would likely help a lot with reducing multipath interference, which likely lead to some of the readings being so off.

Increasing GPS_accuracy may help too, say to 15 or 20m, to cater for the images with bad positions.

1 Like

We’re testing speed works with mavic mini, only with GPS of the smartphone.

1 Like

The EXIF file locations are spot on nadir shots and positions listed in EXIF, indicate straight down, where there are objects I can use to determine thusly … A QUESTION, for WebODM, is there a computational difference using a drone that records an absolute flight elevation as opposed to a flight Height over ground?

I have stayed on this site, simply because I have accurate GPS locations throughout, have surveyed in the area with RTK and this property was surveyed by another surveyor whom I worked with often. Pin locations are marked for aerials, and with NO CONTROL, more often than not, agree within 0.3 feet per hundred for the front and back pins(no more off than a foot in 155’). In ODM3, the locations vary greatly … 3 or more feet off, and with control sometimes 6 or 7 feet off. Same control in #2, and I’m back to about 1/2’ in 155 feet.

The middle 550 feet or so, is very brushy with a few large trees. I am considering clearing a few areas, and placing random TARGETS(not GCP), just targets for WebODM to get some computational footing(?).

Until I can decide I have the stamina to start a new business, I’m not about to play out the few thousand, for a single used RTK. I’m even less inclined to foot a $4000 plus cost of a low end RTK Drone.

So, right now this is a form of therapy … recreation … and sorry to say, after 10 years, re-learning everything … it’s all subtly different.

Here’s to lifetime learning and the ODM community​:beer::+1:

1 Like

I HAVE run a project on WebODM2, which looks awfully good … it’s the second or third time I have done so … sometimes with no control, then with control … differences are minimal.

The EXACT same data in WebODM3, present differences that are drastic and in obvious error.

The last ODM2 data, was placed in ODM3 and the results are that 1/3 of the project is very good, but 2/3 of the project are atrocious and, of my runs of photos, it appears that about 100 or so photos have become clustered in a 10’ diameter space(2d view). Seven GCP’s appear to be shown correctly, but not a single photo is shown with the south 2/3 of this project.

In 3d view this group of photos appear to make the southern 2/3 of the project project incoherently on the side of a mountain. While 6 of my control points have minimal error, my south control point shows errors of 220 metersH and 119netersV … but the control point is good.

It seems to me that there a difference in the ODM2 and ODM3, that causes these issues. While ODM2 is rather consistent in results, ODM3 is “additionally”, inconsistent, with it’s differences.

My site is far from ideal, and is probably the cause of the bad results in ODM3.

The big issue I perceived in ODM3 was the better and correct representation of items, such as cars, etc… In those projects that work, or those parts of projects that worked, this is evident, and the reason why I’d like to pursue ODM3 … a specific flag or setting?

Achieving good results all the time can be frustrating. The community may be better able to help if you can post your console output log and quality report.

2 Likes

INTERESTING Results … importing of “All Assets”, from WebODM2 to WebODM3 …

A project in WebODM2, that looks about as good as it gets, with full coverage of the flown zone, and extremely close to good scaling, suddenly looks terrible in WebODM3 from an import of All Assets from ODM2 …

Photos in ODM2 are shown in the proper locations and drone “Elevation”, not the EXIF height from ground, but seemingly the same elevation given the takeoff height over ground elevation. In ODM3, the locations of these photos are terribly displaced …

It’d be really great if you could provide these data in an Issue on our GitHub so we can investigate further and try to reproduce the behavior you’re experiencing.

You can store the data anywhere you have sufficient space that is publicly accessible, like OneDrive, Google Drive, etc.

1 Like

I do not use cloud storage …

I can send you the “All Assets”, from #2 and the subsequent “All Assets”, from #3.

You might consider asking someone, that has experienced the same issues, using both #2 & #3, that also uses cloud service to repeat my actions(their data), and ask them to send you their data.

Are you aware of someone else who has, or is that a supposition?

If you need a link to post to (someone else’s cloud storage), that could probably be arranged and sent via direct message (not to speak for Brett).

Unfortunately, it is quite hard to test issues you might see without the data that triggers that issue.

Possibly both … there has been postings within this forum about the very same or very similar problems(WebODM2 correctly completing tasks/WebODM3 incorrectly completing the same tasks).

I don’t know of any others that might have saved “All Assets”, from WebODM2 and imported said zip file into WebODM3, resulting in errors, similar to errors similar the actual task as run in WebODM3.

Might you want to see the “All Assets”, if I can send them?

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.