I’ve come to learn that Pix4D mapper does not correctly process X, Y & Z coordinates in geotag data for Omega, Phi and Kappa values.
I first noticed this when I used a logging device with an IMU. The resulting camera orientations from the geotags were about at right angles to the calibrated orientations. I thought that there might have been a problem with the IMU or the logging device.
On my earlier Pix4D projects, my geotags were using MSL altitudes instead of Ellipsoid altitudes. The MSL altitudes were about 30 meters off from the calibrated altitudes. Perhaps for that reason Pix4D ignored the X, Y & Z values in the geotag.
But when I loaded geotags with proper Ellipsoid geotags, the X, Y & Z were processed - and were again about 90 degrees off from the calibrated camera orientations.
I’m afraid to run steps 2 and 3 with these erroneous camera orientation values. (takes over 24 hours to process.)
All I can think to do is simply remove the X, Y & Z values from the geotags so that Pix4D doesn’t get confused by them.
The best result would be to have Pix4D properly convert the X, Y & Z coordinates to the Omega, Phi and Kappa values.
Is this a known bug? A new bug? Or am I simply making a mistake in my procedures.
I’ve attached two screen shots that illustrate the problem. The first is where the geotag used the MSL altitude - and the X, Y & Z values were ignored.
The second is where the Ellipsoid altitudes were used - and the Omega, Phi and Kappa values are wrong.