| Summary: | GPS Longitude Decimalisation Appears Incorrect In Map | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | hardy.public |
| Component: | Geolocation-Workflow | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | metzpinguin |
| Priority: | NOR | ||
| Version First Reported In: | 5.8.0 | ||
| Target Milestone: | --- | ||
| Platform: | Microsoft Windows | ||
| OS: | Microsoft Windows | ||
| Latest Commit: | https://commits.kde.org/digikam/bac54a7834064573946a3c380be77b0e3f076e53 | Version Fixed/Implemented In: | 5.8.0 |
| Sentry Crash Report: | |||
|
Description
hardy.public
2017-11-16 19:48:01 UTC
Send me the image by email. Maik It comes with the seconds part of the longitude to an incorrect conversion into a rational number by Exiv2. The rational values are completely wrong. Since we need the number as a floating-point number and the toFloat() function returns correct value, this problem can be circumvented in Exiv2. Maik Git commit bac54a7834064573946a3c380be77b0e3f076e53 by Maik Qualmann. Committed on 17/11/2017 at 17:49. Pushed by mqualmann into branch 'master'. fix possible wrong return value from Exiv2 toRational() function FIXED-IN: 5.8.0 M +2 -1 NEWS M +32 -57 libs/dmetadata/metaengine_gps.cpp https://commits.kde.org/digikam/bac54a7834064573946a3c380be77b0e3f076e53 Many thanks Maik! Note: re-reading the metadata from images with GPS information must be done. Maik Thank you very much. Works perfectly in 2-Dec 5.8.0 build. |