Drone camera types and lenses added to datebase?

With the popularity of these drones and the cameras they carry I think it would be a great idea to add the camera info and the lens info to the camera and lens databases so that these users can add the metadata to their photos.

If need be, I could go ahead and start collecting data needed to add at least the camera data to the camera database. Since the cameras have fixed lenses the lens data can be either omitted or included with the camera information.

Just a thought... from a new drone owner.

I just uploaded a photo to Pbase from my quadcopter and it identified the camera and the manufacturer (DJI FC6310). And it also had the camera settings. Amass identified the camera settings but no actual camera information.

CameraMan wrote in post #18424443
With the popularity of these drones and the cameras they carry I think it would be a great idea to add the camera info and the lens info to the camera and lens databases so that these users can add the metadata to their photos.

If need be, I could go ahead and start collecting data needed to add at least the camera data to the camera database. Since the cameras have fixed lenses the lens data can be either omitted or included with the camera information.

Just a thought... from a new drone owner.

Sorry for a late reply.

I'm doing the final tweaks on version 2.0, and I will add drone cameras to it. It seems that it is best to add the camera "id" codes to the gear list (even if there are fixed cameras in many models), as often drones can use different cameras, and the EXIF name is always the model name, not drone name. The list from DJI I have now gathered for various sources is:

FC350
FC350H
FC550
FC550RAW
FC1102
FC220
FC300X
FC300XW
FC350Z
HG310
FC200
FC300SE
FC300X
FC300C
FC300S
FC300XW
FC330
FC6310
FC6510
FC6520

Some are fixed lens cameras, some as Micro four thirds mount. Do you know which are mountable? When a camera has a mount, the lens will be required in metadata for gallery adding.

To make selection easier in gear list, I could do a correlation list from actual drone name to compatible camera names, if needed. That needs some further info from those who know.

What about other manufacturers? I have some listed:

PARROT Bebop Drone 2
Yuneex Breeze 4K
Syma X5C Explorers
Ehang Ghostdrone 2.0 VR
UTO Drone U960 Hexacopter
Blade Chroma 4K

and I have no clue what they show in EXIF.

It is very hard to find example photos of drones that include EXIF, it looks like even dng stills from videos are automatically stripped by export tools.

There will also be a generic listing:

manufacturer: Unspecified manufacturer

Drone Camera (fixed lens) FIXED LENS
Drone Camera (mountable lens) LENS REQUIRED

To find exif data I would suggest looking at pbase and try searching for those cameras for the exif data. I think they have a pretty extensive database of drone cameras. As far as fixed and removable lenses are concerned I have no clue which cameras have what. I can better research that this weekend.

So, there's no way to pull the EXIF data from the file here? Even with Windows Picture Viewer and Linux viewers I can see the EXIF data on my computer (Camera Model, Manufacturer, ISO, F Stop, Shutter Speed and in some cases the lens I used). Is it ASCII text with information about the cameras themselves that you're needing? I'm a little confused as to what you need to add cameras and lenses to the Amass Database. I thought all of that information was built into the files themselves and the AMASS Software just pulled that information from the file.

CameraMan wrote in post #18521369
So, there's no way to pull the EXIF data from the file here? Even with Windows Picture Viewer and Linux viewers I can see the EXIF data on my computer (Camera Model, Manufacturer, ISO, F Stop, Shutter Speed and in some cases the lens I used). Is it ASCII text with information about the cameras themselves that you're needing? I'm a little confused as to what you need to add cameras and lenses to the Amass Database. I thought all of that information was built into the files themselves and the AMASS Software just pulled that information from the file.

Not so simple. There would be no point just adding (text) item names as new database items, the list would be endless and impossible to manage/search/sort/man​ipulate.

In short:

Gear database contains gear items, each item is the only ONCE, having a specific id number.

EXIF is read (by ExifTool) and then analyzed by our code, the full EXIF is passed to the code.

If database match is found (by name, EXIF lens id or EXIF camera id) they are stored as said internal id numbers for metadata for that image.

Shutter speed, ISO and aperture are easy: they either are there or are not, and they can be easily parsed to suit our storage format.

I real life the EXIF is very often incomplete, missing data, having overlapping data (like LensIDs which are manufacturer-specific and not governed by anything). Each software suite manipulates and re-saves the EXIF as they will, even if the original image has it in full. Many programs and apps strip EXIF from files altogether.

A Canon 70-200 f/2.8L IS II can be written in EXIF in dozens of ways, and if it is just written as
"70-200 2.8" without manufacturer info, there is no way telling for sure which version of the lens it is.

Using pretty complex guessing and type ranking algorithms (that are vastly improved in next version) AMASS tries to find a potential match from the database when the EXIF info does not contain enough to be sure. If it does not find a very probable match, it does not just guess something.

I have checked tons of examples of DJI images, and very seldom they contain lens or camera info, just the manufacturer: "DJI". There as now 19 DJI cameras listed in AMASS 2.0 gear database, and without camera name like "FC350Z" that gear hit can not be found with just "manufacturer: DJI".

DJI does not add camera/lens ids or names to EXIF, they add sometimes drone names there, not much use there:
https://www.sno.phy.qu​eensu.ca …xiftool/TagName​s/DJI.html

EXIF parsing is really a very complex task when there is a need to do it accurately (and there is). It is surely not just ASCII names added to database, far from it.