You have some jpegs that have a HEIC extension rather than jpg. For the GPS coordinates, you can use a wildcard to shorten the command. You seem to have it covered, but here's a couple of suggestions. Quoteexiftool -r -d %s -tagsfromfile "%d/%F.json" "-GPSAltitude However, since you've spend a long time adding/correcting data through the website, you have the exact case that this was made for. I've been told before that I have a huge amount of patience, but I've reached my end on this subject. Side Rant: I tend not to help with the Google takeout anymore because I've spent the last year arguing with people about how Google does not strip any metadata. Took the Takeout route (because during the years I edited/corrected descriptions, dates, etc. Do I need to improve my command line instructions to prevent all the other issues? (Or any other ideas?)Īny input would be immensely helpful at this point!Ī little late, but here are my suggestions How do I prevent exiftool errors? Renaming files could be the answer to the 'Error opening file' and 'maker notes could not be parsed' errors, but what about the 'Not a valid HEIC' ones? So the only logic I've found in these problems is: if exiftool outputs an error, no metadata is edited (which makes sense of course). Time taken (corrected in Google Photos) not updated Timezones were never taken into account when updating the metadata Sometimes 'title' and 'description' was updated (with the same data), sometimes only 'description' Videos never had their metadata updated (missing gps location and description/title) Sometimes nothing was edited (the files where the error 'Not a valid HEIC' or 'Warning: error opening file' was produced) "Warning: (minor) Maker notes could not be parsed" > this happened to files with long filenames such as "IMG_20190418_212211.jpg "Įven so, I imported the new files to the Photos app on my Macbook. "Warning: Error opening file" > this happened to files with filenames ending with (1), (2). "Error: Not a valid HEIC (looks more like a JPEG)" > no idea why this happened This got me a LOT of errors (probably like 5 to 10% of all files), saying either one of these: Then I found out about ExifTool and used (found on the web) this command line in Terminal (and used correct obv) as a test on one of the Takeout folders:Įxiftool -r -d %s -tagsfromfile "%d/%F.json" "-GPSAltitude By now spent quite some nights figuring out how to correctly export/import my precious pictures. So that got me a lot of json files accompanying my photos. Total newbie at using ExifTool here, wanting to migrate from Google Photos to iCloud.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |