According to the ODM Quality Report:
GSD=6.0cm, Altitude 400ft (122m), Mavic 2 Pro (20Mpx images), 2047 images, 354 acres (143 hectares)
10 hrs 54 mins to digest it all, default settings (fast ortho)
Winston it sounds like you are resizing images when you are creating your Tasks, as that should be roughly 4.33cm/px for 12MP at 400ft AGL, which is what I get from my 3DR Solo + GoPro Hero4 Black (12MP).
I’ve never had reason to fly closer as I was doing agricultural field survey exclusively, and a few cm GSD difference in data to make prescriptions on a variable rate implement that is 40m wide is
Edit for clarity:
You can achieve any GSD you want with WebODM provided your input data and processing parameters are appropriate. And your machine has the resources (primarily RAM+swap/page) to do the maths.
Thanks guys.
Saijin, I’ve been leaving the resizing images as the default ‘yes’ 2048 pixels.
I’ve not experimented with turning this off yet, I guess Im expecting a much longer computational time if I do?
Non-georeferenced images mean I don’t see WebODM list a sensible GSD, but for some of the smaller items I make 3D images of with an SLR , the true “GSD” is <0.1mm.
Yes, I did resize them (I actually forgot that I did). I thought about rerunning it without a resize, but the customer was OK with everything as it was.
GSD is actually a combination of the reconstruction and the known points, first when the reconstruction gets the right scale you know the GSD or actually the effect of it.