Bug 182627

Summary:	Geolocation Tab shows no country/city/town names when a photo is geo-tagged
Product:	[Applications] marble	Reporter:	Ar <ari.reads>
Component:	general	Assignee:	Patrick Spendrin <ps_ml>
Status:	RESOLVED FIXED
Severity:	normal	CC:	rahn
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Ar 2009-01-31 20:52:02 UTC

Version:           Digikam 0.10 SVN 20090130 RC2 (using KDE 4.1.0)
Compiler:          Ubuntu 8.10 
OS:                Linux
Installed from:    Ubuntu Packages

In photo "View Mode" the geolocation tab in the right panel of digikam 0.10 shows a world map with country/city/town names in it (at all varying zoom levels), but only when the photo has not been geotagged.

When the photo selected is geotagged, the worldmap is still shown and the photo location is marked on the worldmap, but all geographical location names (country/city/town) disappear - they are no longer shown.

looks like a small bug.

Comment 1 caulier.gilles 2009-01-31 21:43:43 UTC

Sound like a problem in marble widget. When KML informations are passed to marble, it reset map details. There is no reason for that... or i missing something...

Gilles

Comment 2 Marcel Wiesweg 2009-01-31 22:35:00 UTC

*** Bug 182626 has been marked as a duplicate of this bug. ***

Comment 3 Ar 2009-02-07 23:35:56 UTC

Gilles, it does look like a problem. After geotagging, it would be really nice to see near what city/town/country the photo was taken - displaying the actual coordinates is great but not as important/useful as the city names, IMHO

Comment 4 Torsten Rahn 2009-02-08 10:21:48 UTC

IIRC there's an option in PlacemarkManager to either remove all previous placemarks or let them stay when importing new data. 

Patrick: Is this a regression, or am I wrong or does the API not get used in the way that it could?

Torsten

Comment 5 Patrick Spendrin 2009-02-08 15:43:33 UTC

yes, this is a severe limitation of the current API. It will get hopefully fixed later if I have written that part of the API.

Comment 6 Patrick Spendrin 2009-07-10 02:49:44 UTC

has been fixed long ago already...