Hi, I'm trying to use my Mini3 with Pix4d for mapping. But there is missing metadata/EXIF in my mini 3.


This is a typical extract of the metadata from my mini3:

About	DJI Meta Data
AbsoluteAltitude	70.21
Aperture	1.7
ApertureValue	1.7
BitsPerSample	8
CamReverse	0
CircleOfConfusion	0.008 mm
ColorComponents	3
ColorSpace	sRGB
ComponentsConfiguration	Y, Cb, Cr, -
CompressedBitsPerPixel	3.346286222
Compression	JPEG (old-style)
Contrast	Normal
CreateDate	2024-01-04 15:11:47 +0000
CustomRendered	Normal
DateTimeOriginal	2024-01-04 15:11:47 +0000
DependentImage1EntryNumber	0
DependentImage2EntryNumber	0
DigitalZoomRatio	2
EncodingProcess	Baseline DCT, Huffman coding
ExifByteOrder	Little-endian (Intel, II)
ExifImageHeight	2250
ExifImageWidth	4000
ExifVersion	0230
ExposureCompensation	0
ExposureIndex	undef
ExposureMode	Auto
ExposureProgram	Program AE
ExposureTime	1/15
FNumber	1.7
FOV	73.7 deg
FileAccessDate	2024-01-17 16:10:17 +0000
FileInodeChangeDate	2024-01-17 16:10:17 +0000
FileModifyDate	2024-01-17 16:10:17 +0000
FilePermissions	prw-------
FileSize	0 bytes
FileSource	Digital Camera
FileType	JPEG
FileTypeExtension	jpg
Flash	No flash function
FlashpixVersion	0100
FlightPitchDegree	5.7
FlightRollDegree	4.9
FlightYawDegree	-10.7
FocalLength	6.7 mm
FocalLength35efl	6.7 mm (35 mm equivalent: 24.0 mm)
FocalLengthIn35mmFormat	24 mm
Format	image/jpg
GPSAltitude	70.2 m Above Sea Level
GPSAltitudeRef	Above Sea Level
GPSLatitude	21 deg 2' 6.96" N
GPSLatitudeRef	North
GPSLongitude	0 deg 1' 3.47" E
GPSLongitudeRef	East
GPSPosition	21 deg 2' 6.96" N, 0 deg 1' 3.47" E
GPSVersionID	2.3.0.0
GainControl	None
GimbalPitchDegree	0.0
GimbalReverse	0
GimbalRollDegree	0.0
GimbalYawDegree	0.0
HyperfocalDistance	3.16 m
ISO	100
ImageDescription	DCIM\100MEDIA\DJI_0035.JPG
ImageHeight	2250
ImageSize	4000x2250
ImageUIDList	Binary data 66 bytes
ImageWidth	4000
InteropIndex	R98 - DCF basic file (sRGB)
InteropVersion	0100
LightSource	Fine Weather
LightValue	5.4
MIMEType	image/jpeg
MPFVersion	0010
MPImageFlags	Dependent child image
MPImageFormat	JPEG
MPImageLength	268665
MPImageStart	3801650
MPImageType	Large Thumbnail (VGA equivalent)
Make	DJI
MaxApertureValue	1.7
Megapixels	9.0
MeteringMode	Center-weighted average
Model	FC3682
ModifyDate	2024-01-04 15:11:47 +0000
NumberOfImages	2
Orientation	Horizontal (normal)
Pitch	5.7
PreviewImage	Binary data 268665 bytes
RelativeAltitude	30.0
ResolutionUnit	inches
Roll	4.9
Saturation	Normal
ScaleFactor35efl	3.6
SceneCaptureType	Standard
SceneType	Directly photographed
SensorTemperature	27
SerialNumber	53HQL6J0M503F9
Sharpness	Normal
ShutterSpeed	1/15
ShutterSpeedValue	1/15
Software	v01.64.0122
SpeedX	0.0
SpeedY	-0.1
SpeedZ	0.0
SubjectDistance	0 m
SubjectDistanceRange	Unknown
ThumbnailImage	Binary data 10310 bytes
ThumbnailLength	10310
ThumbnailOffset	18432
TotalFrames	1
Version	7.0
WhiteBalance	Auto
XPComment	Type=N, Mode=P, DE=None
XPKeywords	v01.64.0122;UnKnown;v1.0.0
XResolution	72
YCbCrPositioning	Centered
YCbCrSubSampling	YCbCr4:2:2 (2 1)
YResolution	72
Yaw	-10.7

GimbalPitchDegree down to GimbalYawDegree are all 0 for every picture I have taken.
And there is not the typical CameraYaw CameraPitch etc.


Can anyone confirm that their mini3 is also missing this data?
This is a handy website for checking the data https://jimpl.com/


I checked my first pics taken on an earlier firmware and those contain CameraPitch, CameraRoll and CameraYaw but again they are all 0.

Seems weird they wouldn't include this information so I'm wondering if there's a fault with my Mini3?

Edit//

Here you can see the much older Mini1 had all this information:

https://mavicpilots.com/threads/wrong-dates-saved-into-videos-and-photos-metadata.92411/

Camera Pitch                    : -11.80
Camera Yaw                      : +1.20
Camera Roll                     : +0.00

So come on DJI.. What has happened did you remove this information from the later Mini series drones or is my one faulty?

My friend pointed me towards the 360 photos that the mini3 takes, and those contain all the EXIF data you would expect, CameraPitch etc.

So it's only when taking single photos that it doesn't save that information.

Can any other Mini3 pilots please check their EXIF/METADATA information in a picture they take with the drone to see if they have anything in the GimbalPitchDegree Entry or the CameraPitch Entry (If it even exists)?
The CameraPitch entry only exists on older Firmware.

Cheers.

My Mini 3 Pro is recording

Gimbal Roll Degree              : +0.00
Gimbal Yaw Degree               : -2.20
Gimbal Pitch Degree             : -9.40
Flight Roll Degree              : -13.50
Flight Yaw Degree               : -54.90
Flight Pitch Degree             : +2.30

I discovered a week or so ago that this data was missing from photos taken with the Mini 2 as well. So this likes like it dropped off at some point.

I haven't checked pano images on the mini 2 (I suspect that the missing data may be in those as stitching software seems to work automatically work things out well with pano images), but I may take a look a bit later.

No Original Thought Posted at 1-18 01:25
I discovered a week or so ago that this data was missing from photos taken with the Mini 2 as well. So this likes like it dropped off at some point.

I haven't checked pano images on the mini 2 (I suspect that the missing data may be in those as stitching software seems to work automatically work things out well with pano images), but I may take a look a bit later.

Gimbal data isn't necessary to stitch panoramas.
The software matches adjacent images optically rather than from metadata.

Thanks for replying guys.
I was afraid this was the answer, that they had removed it.
It has led to a few errors in model scans with Pix4d for me, the program is pretty good at figuring it out itself but some pics end up all over the place, I'm certain that if the correct camera angle data was in there it wouldn't be making those errors as much.

If anyone with the base Mini3 (non pro) reads this, it would be nice to get confirmation, although it certainly looks like the data is simply not there.

Cheers everyone.

As usual nothing from DJI....

Labroides Posted at 1-18 02:31
Gimbal data isn't necessary to stitch panoramas.
The software matches adjacent images optically rather than from metadata.

AutoPanon Giga reads the gimbal etc data and if you tweak those values then the resulting panorama changes - so APG does use that info.

APG also does a visual assesment of the image and uses that to line things up as well.

I don't know the full process that's used in APG, but I suspect that the meta data in the images is used to 'arrange' the images in a rough order and then the algorithms look for matching elements to adjust the images for more accurate line up. Not only would that sort of process save time in processing the images because the overlaps would already be roughly known saving having to compare every image, but it would avoid mistakes whereby similar objects existing in multiple frames cause severely misplaced images.

No Original Thought Posted at 1-19 01:19
AutoPanon Giga reads the gimbal etc data and if you tweak those values then the resulting panorama changes - so APG does use that info.

APG also does a visual assesment of the image and uses that to line things up as well.

But good stitching software has no problems assembling complex panoramas from images I shoot with an SLR that doesn't have any pitch, roll and heading data.