Version: 0.10 (using KDE 4.2.2) OS: Linux Installed from: Ubuntu Packages I would like to have a Place Finder sidebar tool which will work with standard IPTC/XMP Origin set of data. This is different and in many cases more practical approach than geolocation. The idea behind is that IPTC/XMP contains heirarchical set of data for: County or Country code < Privnce/State < City < Sublocation This four predefined hierarchical levels are unfortunately still just loosely used in Digikam (even batch assigning is impossible). Though can be very beneficial. Actually many people are probably using similar hierarchy using tags/keywords. Employing this existing IPTC/XMP fields will be more valid approach allowing much easier and transparent interchangeability. The idea of Place Finder Sidebar is just it will allow to browse images in similar way as Tags sidebar jut only employing this Origin tags instead. So list of the countries at first level, Privince/State on second, then City and Sublocation. If i.e. there are images wihtough Province/State tag set, the City or Sublocaton will be dsplayed directly under Country. (Or another approach display "Undefined" category). The Microsoft's MediaExpression (formerly iView Media Pro) has Place Finder Sidebar and I was using that extensively on many projects. In future I can imagine procedures which will automatically fill these metadatas to images according to geolocation tags and vice versa will fill geolocation to images according to this origin metadata (though not accurately).
This is a job for : 1/ Template metadata manager to fill these info (under construction by me) 2/ Advanced search tool to query DB about this info (Marcel ?). 3/ A tool to sync XMP using GPS info (already reported in other file). Gilles Caulier
Michal, accordingly with #1, in digiKam 1.2.0 : 1/ is done. 2/ I don't know. 3/ is done. Please update digiKam, kipi-plugins, libkexiv2, and exiv2 to last satble, and try again Gilles Caulier
Hi, 1/ Template engine is there for some time. I did make good use of that adding author's copyright data, though it's not solution for this issue. Creating template for every place is simply impossible given the number of sublocations, cities and countries needed. It should be possible to set Country,State,City and Sublocation values directly and separately and in batches. 2/ The search tool won't allow to search in the location fields. Anyway my idea was not simple search though some kind of "location browser" similar to Tag browser sidebar. Though according to this node (http://www.digikam.org/drupal/node/515) I believe the development is going on... 3/Couldn't test as I don't have any geotagged images to try, unfortunately. Anyway I'm very excited with the development the digikam is taking!
ad 3/ I tried now with Correlator plugin though it seems that this reverse geotaging is still not in my version and I need to upgrade...
Hello, As you found out eariler, reverse geotaging is under development. I don't know when it will be included in a digiKam/kipi release. Place finder tool is already implemented but is not added in advanced search tool, as Marcel Wiesweg said. My task is to integrate it. Gabriel Voicu You can follow here more details: community.kde.org/Digikam/GSoC2010/ReverseGeocoding On Thu, Jun 10, 2010 at 4:57 AM, Michal Thoma <michal@thoma.cz> wrote: > https://bugs.kde.org/show_bug.cgi?id=199157 > > > > > > --- Comment #4 from Michal Thoma <michal thoma cz> 2010-06-10 03:57:43 --- > ad 3/ I tried now with Correlator plugin though it seems that this reverse > geotaging is still not in my version and I need to upgrade... > > -- > 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 > Digikam-devel@kde.org > https://mail.kde.org/mailman/listinfo/digikam-devel >
Michal, This file still valid using digiKam 3.5.0 Gilles Caulier
I believe it is. Still digikam doesn't allow easily browse or write XMP dedicated origin fields (country > state > city > location). These fields are actually present in templates, but I believe these fields should not be there - it should be possible to fill these fields through the description/keywords sidebar. For browsing, I suggest, that these could be treated as special type of the keywords with predefined hierarchy... Quite a big effort though. Anyway this allows some standardization to the location tagging. With keywoards people tend to to do unsystematic location tags which results in less semantically understandable and less universal metadata.