![]() Long story short: I'm not specifically trying to update GPS metadata from an XMP to a JPG where the data already exists (why would you? ) This situation is a bit of an edge case of the process I used to extricate ourselves from Apple Photos. The truncation does not occur in versions 12.13, 12.30, and 12.35 (not an exhaustive list). I have seen this truncation occur in versions 12.36, 12.37 and 12.38. (I am wondering whether the comma in the GPS coordinates is confusing these later versions of ExifTool.) The XMP file has its GPS coordinates formatted as below: the GPS coordinates have been truncated to just their degree values. Inspecting the metadata with ExifTool (truncated results, actual GPS coordinates obfuscated): Using ExifTool 12.36, 12.37 and 12.38 (the latest at time of writing), the same command line run against a folder with a single JPG/XMP file pair results in: Using ExifTool 12.13 at the time, this resulted in the GPS metadata being shuffled around a little, but the GPS coordinates were correct after the write. I bulk-updated images in a folder using this command line:Įxiftool.exe -tagsfromfile "%d%f.XMP" -all:all -ext jpg -ext JPG -ext jpeg -ext JPEG -r Some of these XMP files contain GPS metadata. ![]() I have some JPG and XMP files originally exported from Apple Photos circa 2019. ![]() I think I have found a bug in ExifTool versions 12.36 through 12.38 concerning writing GPS coordinates to an image from an XMP sidecar file. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |