digiKam › digikam-devel

[Bug 271489] New: Repeated reverse geotagging may duplicate /location tags

Classic

List

Threaded

7 messages Options

Milan Knizek

[Bug 271489] New: Repeated reverse geotagging may duplicate /location tags

https://bugs.kde.org/show_bug.cgi?id=271489

Summary: Repeated reverse geotagging may duplicate /location
tags
Product: digikam
Version: 2.0.0
Platform: Compiled Sources
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: Geolocation
AssignedTo: [hidden email]
ReportedBy: [hidden email]

Version: 2.0.0 (using KDE 4.6.2)
OS: Linux

New /location tags do not replace the existing ones and a repeated reverse
geotagging is applied.

Reproducible: Always

Steps to Reproduce:
Open MyBestImage.jpg in Geolocation plugin, set GPS coordines to CityA, apply
reverse geotagging.
Either close Geo-location plugin or even keep it open and change the GPS
coordinates for MyBestImage.jpg to CityB and apply new reverse geotagging.

Actual Results:
MyBestImage.jpg has two locations in tags: /location/blabla/blabla/CityA and
/location/blabla/blabla/CityB.

Expected Results:
Only the last /location/blabla/blabla/CityB is set. Any prior /location/...
shall be removed.

Further, if an image, which already has /location/.... set, is opened in
Geo-location plugin, the /location/... should be shown in the plugin's Tag
column as well.

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

Michael G. Hansen

[Bug 271489] Repeated reverse geotagging may duplicate /location tags

https://bugs.kde.org/show_bug.cgi?id=271489

Michael G. Hansen <[hidden email]> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |[hidden email]

--- Comment #1 from Michael G. Hansen <mike mghansen de> 2011-04-22 16:01:01 ---
Hi Milan,

the problem here is that we don't store that some tags are 'location' tags,
they are just regular tags once stored in the database or in the image. To do
something as you propose, we would either have to start noting the 'location'
type in the database, or also allow the user to specify a pattern of tags which
should be removed once new geotags arrive. Maybe one could let the user mark
one tag as the 'location' tag, instead of creating patterns.

Michael

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

Michael G. Hansen