search

mandarons / icloud-docker

Dockerized iCloud Client - make a local copy of your iCloud documents and photos, and keep it automatically up-to-date.
BSD 3-Clause "New" or "Revised" License
1.15k stars 49 forks source link

[FEATURE] Option to download photos/videos with all EXIF information #179

Closed afreuden closed 9 months ago

afreuden commented 11 months ago

Use case As a user that categorizes photos by time/location taken, I want to have the option to download photos/videos with the complete and original EXIF information so in a disaster recovery event all photos and videos have the original metadata.

Describe the solution you'd like An option in the configuration file to include or exclude all EXIF information in downloaded photos/videos. This should be an end user configurable option, acknowledging that other users may prefer to not include this information in photos/videos for privacy reasons.

Describe alternatives you've considered Current alternative is using Synology Drive to backup photo library to a NAS as a secondary backup which includes the EXIF data natively, however this is a manual workaround (a physical schedule to leave my phone unlocked, on and connected to my home WiFi for the backup to complete) rather than being automated on the NAS/Server

Additional context Nil

mandarons commented 11 months ago

Is it possible through icloud.com? Looks like it has three options for downloading photos:

image

afreuden commented 11 months ago

Hi @mandarons, Apologies I believe I have been chasing a red herring. Short hand is I think this is not an issue with icloud-drive-docker but maybe an issue with Synology DSM reading EXIF data. Have spot checked various images that were all downloaded via the following methods:

All contain the correct EXIF data as expected when viewed on Windows 10, however for whatever reason some specific photos report as having no EXIF data when viewed in Synology DSM, however this issue is consistent across icloud-drive-docker and the Synology Drive Client so I suspect this is a DSM issue. I was just really unfortunate with my initial spot checking of images before logging this feature request. Sorry!