Appreciating Exif
21–30 of 40 posts
Re: Appreciating Exif
#22Re: Appreciating Exif
#23Earlier quoted context omitted.
Conversely, as a hobbyist photographer, I want to do the exact opposite for most photos I take. I would like my camera info, especially the body, lens, focal length, and settings in the image. I recently discovered that software like Darktable can even take a gpx file and photo timestamps to add coordinates to photos taken on a camera without a GNSS receiver.
It's so stupid that we have to do geotagging as a post processing step with separate software. That could be built in to the camera with a GNSS receiver or smartphone Bluetooth link with minimal impact on cost or battery life. And yet even today many high end cameras lack such basic functionality. It's like the camera manufacturers aren't even trying anymore.
Re: Appreciating Exif
#24Wrote a parser to extract image metadata once, and got massively frustrated with the amount of undocumented, semi-documented, wrongly documented, or partially documented attributes. You’ll find references online, but most of them lack half of what you encounter in images. Every image processing app under the sun adds its own range. Some use metric values, some imperial; finding out which can be guesswork. Aperture is…
Happens a lot when standard is not specific enough.
Re: Appreciating Exif
#25Re: Appreciating Exif
#26> The actual behavior depends on the source image, OS, browser, file picker, app, export path, transformation pipeline, and receiving service.
It's a bit hair-pulling that Android now has a filter between the file system and app, that when an app asks for a JPEG file from the filesystem, the filter strips the EXIF. Yes, it's because as Douglas Adams observed, the universe is busy making more and more idiots (for example Zuck's zucking apps might not have location permissions but it can scan the EXIF GPS tags of all your images to determine where you've been), and the solution to that is also idiocy.
Re: Appreciating Exif
#27I wouldnt recommend exiftool in a commercial image pipeline. way too slow compared to libexif or tagging your images with in the image lib. We store everything in tiff tags and exif tags, as our database. But we also embed yaml as comment for everything not covered.
Re: Appreciating Exif
#28Wrote a parser to extract image metadata once, and got massively frustrated with the amount of undocumented, semi-documented, wrongly documented, or partially documented attributes. You’ll find references online, but most of them lack half of what you encounter in images. Every image processing app under the sun adds its own range. Some use metric values, some imperial; finding out which can be guesswork. Aperture is…
As was more or less discussed in the post, EXIF concerns itself more or less with hardware and camera attributes and can be considered authoritative for that domain.
IPTC was added by photojournalism to cover more artistic metadata like a caption, author (photographer), keywords, etc.
Like the one XKCD strip, XMP seems to have come along to try and create a 3rd standard to replace the first two…
Re: Appreciating Exif
#29Earlier quoted context omitted.
Most publication and messaging tools strip exif data, which is incredibly frustrating when friends send you pictures taken together as you no longer have the time stamp, nor GPS coordinate.
Incredibly frustrating but absolutely to be expected.
Re: Appreciating Exif
#30Exif is totally unlike what modern developers would think of as a "file format". It's more like dumping a set of binary block data structures from memory to disk. This was efficient on old digital cameras with minimal hardware resources. But making any significant edits requires doing pointer arithmetic, which can be an alien concept for developers who have only ever used memory-safe programming languages.
That sounds exactly like a file format to me. Are you suggesting that json is the only format developers might be aware of?