Hello, I’ve been flying a waypoint mission every week for the last 6 months and uploading 250-275 images taken at 250’ to create an orthomap of a neighborhood under construction.
Every map created was 22817 x 26760 pixels. GREAT.
Last week I updated to the newest version now when I log in I’ve lost all my previous projects and the output is only 9788x10549 pixels.
Any help on how I can get back to the original size? I have never customized any settings. Just uploaded images and hit process.
You probably now have 2 separate installations of the software, as newer versions always default to installing on the drive with the most free space, rather than installing over the previous installation, which is on a drive with less free space.
Your previous projects are not lost, just preserved with the older version.
but now
Check the task console logs to see what has changed, if you run with the same settings the ortho output sizes should be closer
You probably now have 2 separate installations of the software, as newer versions always default to installing on the drive with the most free space, rather than installing over the previous installation, which is on a drive with less free space. Your previous projects are not lost, just preserved with the older version.
I’m not sure how to open the previous installation. I’m on a mac and I only see the 1 webodm icon to click on. There is only 1 HD on my machine so it couldn’t have saved anywhere else. Any tips on how to access the previous installation?
I found the log for my latest smaller process but don’t have anything to compare it to.
I did just find this but can’t figure out how to change the model resolution. I didn’t specify what size I wanted, originally. But now that I’ve already processed multiple months worth of images I’d like to keep the same size as before: 22817 x 26760 pixels
I can’t help with the Mac as to where the installations go, only having experience with PCs. You should be able to find it with a search of your HD though.
You need to download the console logs and look at the start of it where all the parameters are listed to compare tasks, and under that will be:
[INFO] Maximum photo dimensions: (a number)px
That will be a starting point to find the reason for differing output image sizes.
Also note that you may need to tell ODM to make a higher resolution. It seems that the default is often less than the available resolution from your data.
See this discussion for more details
I’ve definitely gotten better results on orthos by setting the ortho resolution to 0.001 as noted by Piero in that post. (and if anyone else has played around with this more, please weigh in, I haven’t had time to test it very much)
We default to 5cm/px for local nodes since, even with such conservative defaults, folks tend to overwhelm their resources and run into errors quite quickly with anything finer as the default.