I am trying to increase the orthophoto resolution so that the image tiles don’t disappear when zooming in from 5m into 3m. See the video here: https://drive.google.com/file/d/1IsWjSZWIJ3HXYfefp6wsAxb-0svHWfN2/view?usp=sharing
Images were captured with a DJI P4 RTK using the D-RTK 2 base station. This file is a list of GCPs that I want to check accuracy against https://drive.google.com/file/d/18LNqaHege2wEpvxVTgGwV7R3YL_naW-J/view?usp=sharing
The first time I went through the workflow it took about 1.5 hours to process 349 images. I used the default settings for this first run. When I zoomed in on the orthophoto I noticed the disappearing tiles.
I went searching and found this: https://github.com/OpenDroneMap/WebODM/issues/263 (April fix by @pierotofy), which made me think I needed to change an option to increase the resolution of the orthophoto. So I adjusted the options as follows:
- orthophoto-png: true,
- orthophoto-resolution: 1,
- force-gps: true,
- ignore-gsd: true,
- dsm: true,
- verbose: true
The task is now running for more than 31 hours. I can see activity in the logs; therefore, I’m just not sure if I should kill it or just wait until it is done. Below are some screenshots of Docker webodm logs and a link to the task console output in WebODM. It appears to be cranking away towards the finish. It is going through the PIDs one by one with about 6 minutes between each. Is there a way to see how many PIDs there are to process? If so, I could maybe estimate how much more time is needed to finish this task.
It doesn’t look like a memory or disk space issue either…
The image set can be found here: https://drive.google.com/file/d/1odptc1qz4U787JUrYVOuexjv4lYPtIvE/view?usp=sharing
The task console output here: https://drive.google.com/file/d/1QVP-gMEt2JfG5hcJTiijI7OlZr1dEcHo/view?usp=sharing
This is a map of the GCP locations as well: https://drive.google.com/file/d/1iznTmiceNarxdDbAMT61Is1e-gCaU2Zh/view?usp=sharing
Do you think I should let it run or kill it?
Any suggestions or insights greatly appreciated.