we are encountering rescaling problems with our ODM output orthophotos (1cm GSD), which are shrinked compared to their original size. Our baseline settings use
--gps-accuracy=0.2 (RTK corrected survey, Zenmuse X-7) and
-- skip-3dmodel=TRUE + dem-resolution=2. We are only interested in orthophotos.
After some reading in the forum, we found posts that point out, that the options
--fast-orthophoto mentioned above could cause the rescaling issues. Here a screenshot examplifying the rescaling issue. The image is slightly too small and should in reality scaled to the field boundary (blue line). Our Pix4D ouput scaled correctly to the field boundary:
So we did a test running the default settings, which need longer processing times than our baseline settings, but should be potentially more precise to see if the rescaling issue is solved. The result was actually the contrary.The image was significatly shrinked in comparison to its original size. Pls have a look at the screenshot that shows the scaling problem compared to the field boundary:
Here the tracking deatails for both settings. Why there are some apparently incorrectly calculated camera positions by SFM, when using default settings?:
What went wrong here? Both have the same input images and reconstructed images count:
Both were processed in the same pipeline (scalable VMs in Google Compute Engine) in the cloud. It is very appreciated any information that can help us understand how to deal with the scaling problem in ODM, that we are facing. We need geospatially accurate images for our analyis.