improve usability/interface for photos module, use extracted geolocation data in location fallback

[purarue]

See discussion in #262

Possible ideas:

• Let user choose between core/denylist.py (and an inverted version), which only adds items to via_location.fallback if you've 'added' it to an allowlist. This lets you either:
  • automatically allow and filter photos to deny
  • automatically deny and filter photos to allow

https://github.com/karlicoss/HPI/blob/98b086f746fdc519cf0d51b86a777a265c359552/my/core/denylist.py#L102

Could likely add some extra stuff to doctor which prints info about denied paths etc.

• integrate with some other photos CLI tool instead? (dont know which, would appreciate suggestions from anyone who uses something)
• pull geolocation data from the photos and add it as fallback location data (or possibly accurate locations? since I think those are exact -- can let user pick either)

[purarue]

Oh, if it wasnt obvious, I'll work on this, after some experimenting as posted in memex:

https://memex.zulipchat.com/#narrow/stream/279601-hpi/topic/where_db/near/329138872

[karlicoss]

Yeah not really sure what would the best approach with photos be, seems pretty tedious to work with them via CLI, I'm leaning towards having modules for photo management software which does the heavy lifting of managing metadata (and often caching useful metadata). E.g. I've been playing with Digikam lately, it just uses sqlite database one can hook up to directly. But of course if you experiment would be really interested what can you come up with!

[purarue]

Oh yeah, GUI programs work as well, will make the interface agnostic so should be able to write a my.photos.digikam etc.