Bug 251420

Summary: Map Search : Restrict to an album, filter for a time period, and include map search in Advanced Search tool
Product: [Applications] digikam Reporter: Jon Eliot Strømme <jon.stromme>
Component: Searches-MapAssignee: Digikam Developers <digikam-bugs-null>
Status: REPORTED ---    
Severity: wishlist CC: caulier.gilles, mike
Priority: NOR    
Version: 1.2.0   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:

Description Jon Eliot Strømme 2010-09-16 10:34:16 UTC
Version:           1.2.0 (using KDE 4.4.2) 
OS:                Linux

Thank you for Map search, it is awesome for viewing. One can proceed to any found album and view it, but I would rather stay in Map search and use the thumbnails' location to choose pictures from a given spot.
When there are many albums from the same place, the view becomes cluttered. I would love to preselect a period to restrict the search, for instance this year's trip to Crete, not the trip in 2008. A simple year widget would be nice, a date range widget would be even better.
An alternative, or addition, would be to select just one album from the available albums in the map search. Then the Map widget would effectively provide a virtual tour of the album, just as it does now when there is only one album with location data from a given area.
A very general and powerful solution would be to restrict the Map search to the pictures within the current search, whatever that might be. 

Reproducible: Always
Comment 1 Michael G. Hansen 2010-09-16 20:56:11 UTC
Hi Jon,

thanks for your comments! For the next big digikam release, Version 2.0, we have implemented a map view which can replace the icon view in the center of digikam. With this tool, you can display any images that you have in an album/ a saved search on a map.

We have also thought about extending the advanced search to include a map, but this has not been implemented yet.

Michael
Comment 2 Justin Zobel 2021-03-09 05:51:45 UTC
Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.