Difference between initial and computed image locations

We are flying a 600 acre graded construction site using a Phase One XM-100… Trimble R10 running RTK corrections to the drone via the DJI controller. We have been having issues over the past 2 weeks with the initial and computed position of one line of imagery varying quite drastically. Pix4d seems to create erroneous tie pts in this area which translate to an inaccurate DSM surface. We started flying the site using 65 forward overlap and only 50 side overlap but have not had issues up until last week with creating enough accurate tie pts with the somewhat low overlap. Is it possible the controller is losing the connection with the sensor and creating erroneous gps data that is incorrectly used in the Pix4d processing. Thanks for any help?

I replied in the ticket you submitted.

Did you find a solution for this? I am having a similar issue. Thanks.

What appeared to fix it was clicking the load optimized parameters button in Edit Camera Model after running the initial process and then either re-running the initial process or reoptimizing the project. The link below explains it. We never increased our side or forward overlap and after using the “Load Optimized Parameters” the project report camera optimization goes from around 3% down to 0.07%.