I have a payload system that automatically tags image geolocation and orientation (Roll, Pitch, Yaw).
I’ve noticed that when I use images from this system in Pix4D, the initial orientation values depicted in the rayCloud view are not as expected - the images are all pointing forward and oriented incorrectly, as though the values are in a different reference frame.
Reviewing the Gimbal angles in the EXIF data, however, it seems that the embedded data makes sense.
The camera is pointed toward nadir, the aircraft has a slight downward pitch angle, is pointed at 283.290 degrees (relative to magnetic north), and has a slight roll angle.
The initial orientation shown by Pix4D “flips” in yaw for upwind and downwind segments, so there is at least some correlation in yaw.
XMP Toolkit : XMP.Core.5.5.0
About : DJI Meta Data
Format : image/jpg
Latitude : [Redacted]
Longitude : [Redacted]
Absolute Altitude : 120.272
Relative Altitude : 120.272
Gimbal Roll Degree : 5.891
Gimbal Yaw Degree : 283.290
Gimbal Pitch Degree : -6.015
Flight Roll Degree : 0000000000
Flight Yaw Degree : 0000000000
Flight Pitch Degree : 0000000000
Cam Reverse : 0
Gimbal Reverse : 0
What might be wrong at the EXIF data level, that the developer of the system might tweak to make it interpret correctly in Pix4Dmapper?