Bug 515564

Summary: Reverse geolocation process gets stuck or is extremely slow when fetching address data
Product: [Applications] digikam Reporter: 1234destiny1234 <1234destiny1234>
Component: Geolocation-ReverseGeoCodingAssignee: Digikam Developers <digikam-bugs-null>
Status: RESOLVED NOT A BUG    
Severity: normal CC: metzpinguin
Priority: NOR    
Version First Reported In: 9.0.0   
Target Milestone: ---   
Platform: Microsoft Windows   
OS: Microsoft Windows   
Latest Commit: Version Fixed/Implemented In: 9.0.0
Sentry Crash Report:
Attachments: debug log

Description 1234destiny1234 2026-02-05 17:38:56 UTC
Created attachment 189249 [details]
debug log

When attempting to perform reverse geocoding on a selection of images with valid GPS coordinates, the process either hangs indefinitely  or proceeds at an unusable speed.

STEPS TO REPRODUCE:
Open the Geolocation Editor (Ctrl+Shift+G).
Select a group of images with existing GPS coordinates.
Navigate to the Reverse Geocoding tab.
Select a service (e.g., Nominatim) and click Apply Reverse Geocoding

OBSERVED RESULT:
The progress bar remains stationary or moves extremely slowly (e.g., one image every few minutes). The application may become unresponsive ("Stuck") during the network request phase.
Comment 1 Maik Qualmann 2026-02-05 18:14:13 UTC
The speed depends on your internet connection and the load on the service you're using. We have no control over this. Remember, you're using a free online service.
All the "fail" messages are not from digiKam, check your system.

Maik
Comment 2 1234destiny1234 2026-02-05 18:18:32 UTC
(In reply to Maik Qualmann from comment #1)
> The speed depends on your internet connection and the load on the service
> you're using. We have no control over this. Remember, you're using a free
> online service.
> All the "fail" messages are not from digiKam, check your system.
> 
> Maik

i do have good broad band internet connection , however the ui seems to be unresponsive , i tried to do it for small number of images , like 2 or 3 pics , it takes a bit of time with the ui being irresponsive