I used to find things with the search-function and "search area" of Marble within the Openstreetmap (not the vector-map). E.g. "camping" or "museum" or names. It worked until some weeks ago. Now not anymore. Even if I see the word "camping" on the map, Marble finds nothing. Until then Marble found things without problems even if the area was 50km wide. Spielmops
See bug #394587 for the technical explanation.
*** Bug 394587 has been marked as a duplicate of this bug. ***
Actually, let's repost it here: Nominatim searches in Marble 2.2.20 (KDE Applications 17.12.1) recently stopped working. On the console, the warning: Cannot parse osm nominatim result is printed. No results appear. I suspect that this is because http://nominatim.openstreetmap.org/ now redirects to https://nominatim.openstreetmap.org/ , so the URL fragment at OsmNominatimSearchRunner.cpp:53 needs to be updated. And you probably also want to fix your code to support redirects.
Ping? This is a regression that completely breaks an essential feature of Marble, and it looks like the fix may be trivial (one character), can somebody please look into it? I am setting this to CONFIRMED because we are already at least 2 people seeing it and there is clearly a reproducible bug here.
Count me in! Nominatim search doesn't work for me either. Tested different (older) versions of marble and different users on my computer, and invariably got the same result: apart from city names, nothing is found in searches (e.g. the example in the manual Baker Street, London). This behavior supports Kevin's explanation.
Ping?
Very unusual, that nobody works on this one character ...
I can confirm this as well. Unfortunately changing the url to https inside src/plugins/runner/nominatim-search/OsmNominatimSearchRunner.cpp doesn't change the behavior either - odd. Did they make changes to the user agent testing as well?
> Did they make changes to the user agent testing as well? I don't know. You'd have to ask the OSM admins directly.
Sorry guys, I've just fixed the issue in master and backported the fix to the last few releases. It was indeed just about changing http to https. Can you confirm that it works again as expected? :-)
I can confirm that this is fixed at least in 18.12.0 (I think, in some 18.08.x too, but I went directly from 18.04.3 to 18.12.0). I tested with marble-18.12.0-1.fc28 on Fedora 28. Thanks!