[Digikam-devel] [Bug 205001] New: MapSearch: Merge overlapping markers to clusters

[Michael G. Hansen]

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

           Summary: MapSearch: Merge overlapping markers to clusters
           Product: digikam
           Version: unspecified
          Platform: Debian testing
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: wishlist
          Priority: NOR
         Component: Map Searches
        AssignedTo: digikam-devel at kde.org
        ReportedBy: mhansen at mghansen.de


Version:           1.0.0-beta3+svn (using KDE 4.3.0)
OS:                Linux
Installed from:    Debian testing/unstable Packages

In the digikam-svn version, the map search tool displays markers for the images
it found on the map. However, the density of the markers can be very high at
times, so you end up with a bunch of markers overlapping which is not very
useful. One solution that I have seen is clustering:

http://googlegeodevelopers.blogspot.com/2009/04/markerclusterer-solution-to-too-many.html

I have made an attempt to apply this clustering to the mapwidget, attached as a
patch. Instead of individual markers, it just shows circles with the number of
images at a particular point.

There are two different ways to form the clusters from the markers, implemented
in MarkerClusterHolder::reorderClustersSimple and
MarkerClusterHolder::reorderClustersPixelGrid, please try both and tell me what
you think. (uncomment the one you want in MarkerClusterHolder::reorderClusters)

What's not implemented but could probably be added:
- highlight clusters when a user selects an image in the album view
- narrow down the search when the user clicks on a cluster
- revert to simple markers for clusters with only one marker
- show clusters when there is no selection on the map to make it easier to
select an area of interest
- make the clusters better looking as in the Google Maps demo

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.