[Digikam-devel] [digikam] [Bug 328855] New: Manual geotagging unintuitive, misleading
chealer at gmail.com
Mon Dec 16 02:53:13 GMT 2013
Bug ID: 328855
Summary: Manual geotagging unintuitive, misleading
Platform: Debian testing
Assignee: digikam-devel at kde.org
Reporter: chealer at gmail.com
Digikam supports geolocation. In the ideal case, the device exporting photos
already has the images geotagged.
When a photographer without a GPS device wants to use geolocation, manual
geotagging needs to be done. I tested this use case today and had the
impression I was using some advanced photography software for a while. The
interface is highly unintuitive and even misleading, as reported in bug 275180.
(However, FWIW, I use digikam about once every 2 years and do not master it at
The user trying to understand how geotagging works will likely try tagging a
single photo to start. He will likely click the globe at the left, the globe at
the top or the globe at the right. These are all useless for geotagging. The
top one in particular got yours truly truly confused - having tried the 3, I
ended up with 3 maps displayed, and not seeing how to "exit", I resorted to
restarting Digikam to go back to the pictures list! The right panel is
particularly confusing too. Rather than saying the image is not tagged, it
suggests that geolocation is broken. The early stage of my confusion is pretty
well explained in the question from John Stumbles:
At this point, I had installed documentation and found some documentation about
sidebars, which didn't help. I went to Google and found
Although the menus changed since then, I finally managed to reach the
geotagging dialog. That wasn't the end of the story though...
In the dialog, I was able to move the map and "select" a location. But after
applying the changes, nothing changed. The final enlightenment only came after
more Googling and reading rawi's reply to the above digikam-users post. The
whole process must have taken more than half an hour, for a seasoned KDE user.
Finding http://userbase.kde.org/Digikam/Geotagging_in_digiKam_2.0 at the start
would have helped.
Lots of usability improvements to geolocation could be made. Bug 299827
requests an improvement specifically for bookmarks. My specific problem had 2
parts: reaching the geotagging interface and managing to use it. Bug 184833 has
suggestions helping with the former. This ticket should deal more specifically
with the latter.
The problem with the geotagging interface has 2 sides:
1) Nothing says how it should be used.
2) A couple of problems suggest the interface should be used in a way it cannot
Because of 2), users are likely to conclude that geotagging is broken rather
than trying to cope with 1). Therefore, the core of this ticket shall be 2).
All maps in Digikam (left pane, center, right pane and geotagging dialog)
display a crosshair in the center. For the right pane, this crosshair is
justified, helping to locate the precise location. For all other maps, this
crosshair is misleading. This is particularly problematic in the geotagging
dialog, as the user will naturally think the pointed location is the one he is
Secondly, the "Apply" button is always enabled. The user can therefore conclude
that merely moving the crosshair at the desired location constituted a change
which can be applied.
These 2 problems are truly misleading and should be fixed first.
For completeness, I come back to the first side of the geotagging interface's
problem. When you selected a single image, you may find it surprising that you
have to effectively re-select which images you want to tag. Drag and drop is
handy but not discoverable. There could be text explaining how to use. I think
it is legitimate that the primary mouse button is dedicated to map navigation
and cannot be used to locate a photo. However, the menu brought up with the
secondary button could offer more than Copy coordinates. It could offer, say,
directly setting these coordinates for all images, or for all selected images.
Finally, there should be a section dedicated to geotagging/geolocation in the
I did not notice much change on this between 3.5.0 and 4.0.0-beta1.
You are receiving this mail because:
You are the assignee for the bug.
More information about the Digikam-devel