[digiKam-users] Open Street Maps query not working

Maik Qualmann metzpinguin at gmail.com
Sun Jul 1 20:13:09 BST 2018


We do not actually use Marble's OSM search. Although in digiKam the menu with 
the right mouse button is again available over the map and the address search 
does not work either. The OSM search (serach tab) in digiKam-6.0.0 is already 
fixed.

Maik

Am Sonntag, 1. Juli 2018, 20:36:51 CEST schrieb Remco Viëtor:
> On dimanche 1 juillet 2018 19:58:59 CEST loup+digikamusers at lo-cal.org wrote:
> > I have not tried it with the pre-release 6.0.0 build, but it used to
> > work fine with both 5.6.0 and 5.9.0 for many months before it broke, so
> > I don't see how the Marble build could affect it. Especially with 5.9.0,
> > which is an appimage on my system (5.6.0 is the Ubuntu package version),
> > so everything should be bundled and static in the 5.9.0, if I understand
> > how appimages work correctly (which I might not).
> > 
> > So can anyone confirm that OSM queries are currently working with the
> > 5.9.0 appimage release of digikam?
> 
> It's perhaps not so much a bug in Marble, as a change at the OSM side
> (switch from http:// to https://), see :
> https://bugs.kde.org/show_bug.cgi?id=394517 But even in that case, it's not
> something the Digikam developers could correct
> > On 07/01/2018 10:15 AM, Remco Viëtor wrote:
> > > On dimanche 1 juillet 2018 15:51:26 CEST loup+digikamusers at lo-cal.org
> 
> wrote:
> > >> I used to use the OSM query in the "Edit Geolocation" feature all the
> > >> time, but sometime around March of 2018 the query stopped returning any
> > >> results.  When I type in a search string, the results box remains
> > >> empty,
> > >> no matter what I search for.  GeoNames search still works.  This is
> > >> occurring in Digikam 5.6.0 and 5.9.0.
> > >> 
> > >> Has anyone else experienced this?  Does anyone know how to solve it?
> > > 
> > > I noticed the same thing in the stand-alone version of Marble (which is
> > > what Digikam uses to display the maps), so my guess is that it is an
> > > upstream problem in Marble.







More information about the Digikam-users mailing list