#5353 closed enhancement (wontfix)
Extend EXIF parser to include GPS metadata keys
Reported by: |
|
Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Severity: | normal | Version: | |
Component: | General | Keywords: | |
Focuses: | Cc: |
Description
Request to extend EXIF parser to include GPS metadata keys stored in EXIF/IPTC.
Reference projects are available in relation to PHP, the PHP EXIF Library, and use with WordPress (and web mapping applications).
One example of such project that appears to already have dealt with various camera models' approach to GPS in metadata is the following. This project appears to be a WordPress related development.: PHP Exif-Parser (A request has been sent to that developer to participate and add value in this development, but you may wish to contact him personally to encourage his support and participation.)
Change History (3)
#3
@
16 years ago
I would contest this thinking, as GPS metadata is becoming intrinsic in the practicality of geo-aware position of images and visualization (inherent to the reality of the image taken, if metadata coordinates exist). To not provide the entirety of what's represented in the metadata of an image, is to cut-off the possibilities of developments for future development of plug-ins that can or will use that metadata. (You'd be making it far easier for plug-in developers to create their own methods for using said metadata, making it scalable for all developers.)
Otherwise, by taking the approach you suggest -- would force two chains of metadata sets, limiting methodologies in content and visualization, forcing dependencies on more than one plugin, as well as creating overhead by applying an additional data-chain and plugins.
This sounds like a job for a plugin. The image metadata code has a hook just for that purpose.