You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When you utilize google takeout to collect your Google Photos content you end up with a number of JSON files. It appears that if you have edited things that would normally be in the EXIF on google photos instead of updating the file they updated a JSON sidecar. This means that when I imported into NextCloud/Memories I have a large number of photos that have ended up being dated incorrectly where I have corrected a date. The JSON file is named exactly what the image file is with an extension of .json.
Specifically I would be happy to just see Date retained from this file if it is present, but think others might find the people or geo encoding useful as well.
Honestly this is the kind of thing that could be done as a batch job, and I would be happy to take a stab at at least getting the date into the database even if the files themselves were not updated. If you could point me in the right direction database wise I would be happy to post back the script I end up with.
When you utilize google takeout to collect your Google Photos content you end up with a number of JSON files. It appears that if you have edited things that would normally be in the EXIF on google photos instead of updating the file they updated a JSON sidecar. This means that when I imported into NextCloud/Memories I have a large number of photos that have ended up being dated incorrectly where I have corrected a date. The JSON file is named exactly what the image file is with an extension of
.json
.Specifically I would be happy to just see Date retained from this file if it is present, but think others might find the people or geo encoding useful as well.
Here is an example JSON from google takeout.
The text was updated successfully, but these errors were encountered: