(This is a feature request following this Meta Photo-SE post: Is there some way that we can help new users to add EXIF data to their photo?)
At Photography Stack Exchange, when posters ask questions about their photos, we often have to ask them in comments to edit the question to include exposure information (shutter speed, aperture or f-number, ISO), and sometimes camera info (make/model, lens type, focal length). This is a constant dance we have to play with our new posters. Sometimes, the poster never edits the question, so either the answers are stuck speculating about the exposure conditions that could have caused their problems, or we're forced to close the question as unclear / needs details.
Rather than go back and forth with the "please edit and add exposure details" comments, can the image uploader be modified to parse / return exposure information from the image's EXIF data if it exists?
I realize this is a pretty narrow use-case, probably specific to Photo-SE only. I imagine this functionality would be undesirable for every other Stack. And I'm aware that Imgur is against returning or retaining EXIF data broadly and blanketly (ref: Is EXIF data removed from uploaded SE pictures?). But I imagine maybe a few possible approaches to the solution:
Negotiate a modification to the Imgur API to return a defined subset of EXIF data such as
ApertureValue
,ShutterSpeedValue
,ExposureCompensation
,ISO
,MeteringMode
, etc., but certainly no identifying information). Likely? No. But probably the best technical solution.Pre-parse the EXIF information from a SE self-hosted CGI/script using whatever server-side EXIF library is available. This has the downside of requiring a temporary image upload to SE's servers just to get the EXIF data, but otherwise is unchanged with regards to the Imgur uploader process.
Use a 3rd-party EXIF parser service in parallel with the Imgur uploader. Something similar to https://exifinfo.org. This is similar to #2, but is dependent upon a separate service agreement, contract terms, etc. Probably the least desirable option.
Client-side solution. I'm not specifically familiar with Javascript-based EXIF parsers, but there seem to be a few, such as exif.js. I think this is probably the best solution. (thank you @nobody for this suggestion in the comments)