Bug 441052 - Missing data using reverse geocoding for specific addresses, subsequent crash
Summary: Missing data using reverse geocoding for specific addresses, subsequent crash
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Geolocation-ReverseGeoCoding (show other bugs)
Version: 7.3.0
Platform: Microsoft Windows Microsoft Windows
: NOR crash
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-08-16 16:45 UTC by Thomas Eisenzopf
Modified: 2023-12-10 07:33 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In: 8.3.0


Attachments
Screenshots with missing information marked yellow (344.62 KB, application/x-zip-compressed)
2021-08-16 16:45 UTC, Thomas Eisenzopf
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Thomas Eisenzopf 2021-08-16 16:45:36 UTC
Created attachment 140777 [details]
Screenshots with missing information marked yellow

SUMMARY
Reverse geocoding does not work for certain addresses: When I call the function, only parts of the address are inserted as a tag (e.g. country and street), other parts are missing (e.g. location). For examples see screenshots, e.g. coordinates geo: 47.7407137878,13.450451314.
Sometimes digikam crashes at such an address after reverse geocoding.

STEPS TO REPRODUCE
1. Select image with problematic address
2. Start reverse geocoding

SOFTWARE/OS VERSIONS
Windows 10 (all updates)
Comment 1 Maik Qualmann 2021-08-16 20:47:45 UTC
It doesn't matter whether all address elements are present or not. I cannot reproduce the problem with the coordinates and address elements either. The crash must have another reason. Possibly the DebugView Log with active debug environment variable will help us, as described here for Windows:

https://www.digikam.org/contribute/

Maik
Comment 2 Maik Qualmann 2021-08-17 13:00:26 UTC
I tested it with your coordinates, if you use the Open Street Map service in reverse geolocation and add all address tags, the missing address entries are also available. The address details dialog comes from the Marble component and the crash also occurs in other programs. I move the bug report to the existing entry.

Maik

*** This bug has been marked as a duplicate of bug 434802 ***
Comment 3 Maik Qualmann 2023-12-10 07:33:57 UTC
Git commit 60de5c83ae6efbf2bcfa7c5464754212f32309ae by Maik Qualmann.
Committed on 10/12/2023 at 08:33.
Pushed by mqualmann into branch 'master'.

fix crash when closing Marble address detail dialog
FIXED-IN: 8.3.0

M  +2    -2    core/utilities/geolocation/marble/osm/OsmPlacemarkData.cpp
M  +2    -1    core/utilities/geolocation/marble/osm/OsmPlacemarkData.h

https://invent.kde.org/graphics/digikam/-/commit/60de5c83ae6efbf2bcfa7c5464754212f32309ae