Skip to content

Instantly share code, notes, and snippets.

Show Gist options
  • Save georgiee/db724761b0e85ef4e87e5068a810fc03 to your computer and use it in GitHub Desktop.
Save georgiee/db724761b0e85ef4e87e5068a810fc03 to your computer and use it in GitHub Desktop.
google photos takeout, dsm synology photos, exiftool DateTimeOriginal & PhotoTakenTimeTimestamp

What

After a takeout with Google Photos any file taken with your own device should contain the correct time. But photos sent from other people, created with Lightroom or very old files might have a stripped date field. Google Photos usually adds a date from the date it was uploaded. You want to have at least that date from Google, otherwise all files you import to Synology Photos will clump together at the date of the indexation.

That's also what most people are doing but they think Google stripped the date from their files during the Takeout. Most files should be fine though, depending on your specific photo collection of course.

My current takeout size is 100GB and I didn't have that much space left while I have plenty of disk space on my synology.

In addition the Synology DSM File Downloader wasn't able to download the temporary links from Google (or they prevented it for some technical reason)

I therefore created the takeout, stored in on my (free) drive with a temporay Google One subscirption to get 100GB of space. I then synced the drive to my synology and got the two 50GB tgz files.

Extract and then run the following exitfool commands. Then copy it to your Photos folder the Synology Photos app created before. The indexing will then happen. I ignored the google json files beforeo (as I thought all my files were good) but there have been too many files from other people or from the past so I did all steps again and overwrote all files. I guess the index will find them due to the slightly changed size (changed exif header).

The script will read PhotoTakenTimeTimestamp from the json (which is guaranteed to exist for every file from Google Photos and write it into DateTimeOriginal which is then read by Synology Photos during the index.

Prepare

wget https://exiftool.org/Image-ExifTool-11.88.tar.gz
# unpack and use it
gzip -dc Image-ExifTool-12.29.tar.gz | tar -xf -
cd Image-ExifTool-12.29
 
# Check version (optionally)
perl exiftool -v

via https://qrys.ch/using-the-exiftool-on-a-synology-nas/

Commands

Prepare some temporary alias.

alias exif='perl ~/Image-ExifTool-12.29/exiftool'

#  info  about a single file
alias infoDate='exif -T -DateTimeOriginal'

# for a single  file update to test (hence the `%F.json` for file + ext without dir)
alias updateSingle='exif -tagsfromfile "%F.json" "-DateTimeOriginal<PhotoTakenTimeTimestamp" -d %s -overwrite_original'


# usage. 

# output the date from a given file so you can check if it's missing and too check after the update
infoDate some-file.jpg

# will look for some-file.jpg.json to fetch the  `PhotoTakenTimeTimestamp` and copy it into the exif field `DateTimeOriginal`
updateSingle some-file.jpg



# actual update of an entire folder (hence the %d/%F placeholder)
# --ext is excluding (json) and -ext is including extensions (any)

exif -r -d %s -tagsfromfile "%d/%F.json" "-DateTimeOriginal<PhotoTakenTimeTimestamp" -ext "*" -overwrite_original -progress --ext json <folder-name>

@georgiee
Copy link
Author

Synology Photos reads the file modification date for PNG files 😑
This means you can do this "touch " and synology show immediately the updated time in the web view.

But if you do some exif update like I tried for the png files you get nothing. I also checked the files most of them already have the correct Creation Date stored in the meta data section. So I should not even need this. It's a bug or missing feature in Synology Photos and I'm not willing to update the file attributes because that's unreliable. So I'm going to wait and let google photos and synology photos coexist and cosync from my device for now.

exif -tagsfromfile "%F.json" "-alldates<PhotoTakenTimeTimestamp" -d %s -overwrite_original

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment