For clarity absent in the first post...: The Headwaters Project is a concerted effort to support critical libraries and software projects upstream of our project.

This is a great reminder of a thoroughly written and thoughtful workflow. Thanks for the reminder!

I also wrote a post on this very topic!

jakecoppinger.com/2022/12/crea...

That'd do it. Biggest challenge might be quality of the GNSS/GPS data, but it'll stitch, just need to choose the right camera type, and probably defaults otherwise. And join us at community.opendronemap.org if you get stuck or when you succeed!

BTW, the model in the upper left of this sequence is the Honda crest from Himeji Castle, in Japan. Watch for a future post where we debadge a Honda and add a crest tile from Himeji Castle, reconstructed from photos last summer.

And we'd be remiss if we didn't mention the other feature this brings in: you can download the camera locations as a text file now (geo.txt), meaning you can edit it and upload it again in another task with corrections to your camera locations, e.g. adjust your Z to a local datum.

Right?! Didn't know how needed it was until it was right there.

The align interface allows alignment of a dataset with another: think ensuring adjacent datasets align, or multi-temporal datasets need to be well aligned geographically.

Previews allow you to (ahem) preview the project orthophoto without opening it.

Introductory thread of GeoDeep here:
community.opendronemap.org/t/geodeep-li...

Also, with an update independent of release you get this cool new feature too!
bsky.app/profile/pier...