https://bugs.kde.org/show_bug.cgi?id=520038
Bug ID: 520038
Summary: Reverse Geocoding does not erase
XMP-lr:HierarchicalSubject Places before to get the
address elements
Classification: Applications
Product: digikam
Version First 9.0.0
Reported In:
Platform: Manjaro
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Geolocation-ReverseGeoCoding
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
Note: I don't know if the current behavior is a feature or a bug. If it is a
feature, it is not documented and not very intuitive IMHO. If it is not a bug,
you can set the severity to wishlist.
When I run a reverse geocoding, I expect a result according to the address
elements tree set. It is not the way Digikam works with
XMP-lr:HierarchicalSubject Place (I have not tried with others tags) : if the
photo has existing XMP-lr:HierarchicalSubject Places, they are not erased
before to apply the reverse geocoding result so the final result is an OR of
current Places with the new reversed Places. It is a problem when you want
remove some address element types, or when the reverse geocoding source
modifies the available address elements.
--
You are receiving this mail because:
You are watching all bug changes.
