Bug 400376

Summary: Picture with wrong GPS value -> better to display "Unavailable"
Product: [Applications] digikam Reporter: Nicofo <nicofo>
Component: Metadata-GpsAssignee: Digikam Developers <digikam-bugs-null>
Status: RESOLVED INTENTIONAL    
Severity: minor CC: caulier.gilles, metzpinguin
Priority: NOR    
Version First Reported In: 6.0.0   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed/Implemented In: 7.5.0
Sentry Crash Report:
Attachments: Digikam Screenshot with invalid GPS values

Description Nicofo 2018-10-27 19:23:54 UTC 
Created attachment 115925 [details]
Digikam Screenshot with invalid GPS values

SUMMARY
I have some pictures with no valid GPS data (latitude out of [-90 +90] ; longitude out of [-180 +180]).
These invalid GPS data are displayed in the MetaData Panel (Exif part) of Digikam (Right Panel) - see attachment.
Should be better to display "Unavailable" (or "Invalid" ...)

See an example of picture with invalid GPS data:
http://nicofo.tuxfamily.org/tmp/panasonic-tz40-GPS-ACTIVE-BUT-NO-SIGNAL.JPG


Note: is someway related to bug #326406 : such image is now no more geolocalised (good) but invalid GPS data is still displayed in Metadata panel.
Comment 1 Maik Qualmann 2018-10-27 19:38:26 UTC 
These values show the actual contents of the metadata fields and are encoded by Exiv2. Exiv2 would have to print here then "invalid". Exiftool also showed a completely wrong value. I think so, that the user should see the numerical value here and not just an "invalid" hint.

Maik
Comment 2 Maik Qualmann 2018-10-27 19:43:08 UTC 
Thats a camera write such impossible values should be reported to the manufacturer as an error and corrected with a firmware update.

Maik
Comment 3 caulier.gilles 2018-10-27 21:02:31 UTC 
I agree with Maik. 

Metadata viewer show tags contents as well without any interpretation. It's voluntary.

The Geolocation view is dedicated to interpret the metadata tags. So for me this file is won't fix.

Gilles Caulier
Comment 4 Nicofo 2018-10-28 21:33:19 UTC 
OK agreed.
Thanks for explanations.