Closed (fixed)
Project:
Exif
Version:
7.x-1.2
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Reporter:
Created:
24 Sep 2011 at 23:35 UTC
Updated:
11 Feb 2016 at 14:24 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
jphautin commentedComment #2
asb commentedActually some formats store more than this:
...and there's more, e.g.:
... or
As the tool
exifprobeshows, it is a bit more complicated than the parsed listings above might suggest (see attachment); isn't there a more generic way to access the data actually stored? Helper tools likeexiftoolseem to do the heavy lifting (parsing data structures, independent from maker specific programs), and appear to extract a lot more data from image files than currently is possible. E.g., a file dumped withexifprobe(like in the attachement) maps to a clean output like this:An external dependency - like on exiftool - wouldn't hurt as the program is free software (license), and it is available for *nix, Windows, and Mac OS X. At least to me it seems that the benefits would significanty overweight the drawbacks...
Comment #3
mastermirko commentedAny update for this?
I still can't select the exif lens data...
Thanks!
Comment #4
andrebonfanti commentedI noticed "focal length in 35mm" is missing in 7.x-1.2 selecting options.
Any update? Thanks!
Comment #5
shawn dearmond commentedHere's a patch that works for me.
Comment #6
firfin commentedHi,
Besides lens(id) I also found copyright missing. Even after replacing sample.jpg with an image that DOES contain this value. So I added this (computed_copyright) and re-rolled patch from #5 so that it applies cleanly.
So this patch adds:
@hohl not really related to this issue, but are you sure your source image has this exif field?
Please test and/or commit.
Comment #7
firfin commentedPatch from #6 still applies cleanly on a current dev version (30 september). Please somebody test and review.
Comment #8
jphautin commentedintegrated in branch 7.x