google-photos-exif VS cli

Not right now, sorry!

There's this tool that can fix capture times: https://github.com/mattwilson1024/google-photos-exif

There are perhaps more that I'm unaware of.

This guide tells you to delete the JSON file that are crucial for both geotag info and in general EXIF.

I don’t recall the script I used last time, but GitHub is pretty full of good Samaritans, eg: https://github.com/mattwilson1024/google-photos-exif

I'm doing the same thing right now. To get the metadata from the JSON files applied to the photo's EXIF data, I'm using this: https://github.com/mattwilson1024/google-photos-exif

A couple of GitHub repos have helpful tools to assist with EXIF data. In particular, I used https://github.com/mattwilson1024/google-photos-exif which worked for me, but YMMV.

If it is a single backup. Just use Google Takeout and tools like google-photos-exif.

No kidding! I was trying to fix them all manually (48GB worth) using https://github.com/mattwilson1024/google-photos-exif, and exiftool.

I did google takeout to download all originals. A lot of the photos had json files that contained the exif data. I used this tool to merge the metadata into the image files. Once done, I dragged all the photos into the photos app on Mac and let it do its thing

Google takeout, then use this tool to sort out the json files with the images, transfer to iPhone then just wait for iCloud to upload

Hey!

> data out

You can use our Desktop app[1] or CLI[2] to export your data, incrementally. There's a toggle within our Desktop app that will perform this operation continuously into a directory of your choosing. You can of course script the CLI however you'd like.

> clients are not open source

Our clients have always been open source. You can find them within our monorepo here[3]. Currently you'll have to pass a flag at build time to configure the endpoint, but there's a discussion[4] to add an option in-app instead.

> Immich and Photoprism

Ente comes with e2ee[5] and replication strategies[6]. The former means that we've to run ML on the Edge, while Immich and Photoprism can run ML on their servers. If your primary use case is self-hosting, Immich is the more "intelligent" option. If you value convenience, Ente is the one.

[1]: https://ente.io/downloads/desktop

[2]: https://github.com/ente-io/cli

[3]: https://github.com/ente-io/ente

[4]: https://github.com/ente-io/ente/discussions/504

[5]: https://ente.io/architecture

[6]: https://ente.io/reliability