Bug 338388 - digiKam doesn't translate GPSAreaInformation metadata character codes to string
Summary: digiKam doesn't translate GPSAreaInformation metadata character codes to string
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Metadata-Gps (show other bugs)
Version: 4.3.0
Platform: Ubuntu Linux
: NOR minor
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-08-19 20:36 UTC by Daniel Duris
Modified: 2020-08-30 15:51 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In: 7.1.0


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Daniel Duris 2014-08-19 20:36:55 UTC
Digikam does not translate GPSAreaInformation metadata character codes to string, although it is easy to do so - this is just an array of ASCII character codes (with first character being encoding, if I am not mistaken).

Could this be implemented?
Comment 1 caulier.gilles 2014-08-19 20:43:47 UTC
It could be by 2 way :

- by digiKam into libkexiv2 interface.
- by Exiv2 shared lib directly.

What's this kind of tags must store exactly as information ?

Note : I CC Exiv2 Coordinator to see which is the best way to use...

gilles Caulier
Comment 2 Daniel Duris 2014-08-19 20:52:58 UTC
Sorry, if I wasn't clear - this stores GPS location info in human readable format and differs from camera manufacturer, but usually:
area, district, county, region, country

where some of these could be blank if not known, e.g. if area is known then:
National Gallery, Kensignton, London, London, United Kingdom
(I just made that up)
but it could be also just:
Lome, Togo
for places, where it doesn't have more info.

I think Didikam should translate this rather than the lib... But as a user I don't care either way :-)
Comment 3 caulier.gilles 2014-08-20 13:41:34 UTC
Can you share some image with GPSAreaInformation tag filled ?

Gilles Caulier
Comment 4 caulier.gilles 2014-08-29 11:55:49 UTC
Please continue to talk about this file in bug #335256

Gilles Caulier

*** This bug has been marked as a duplicate of bug 335256 ***
Comment 5 caulier.gilles 2020-08-30 15:51:19 UTC
Fixed with #335256