Replies: 2 comments 12 replies
-
Hi. This is not a use case supported by osxphotos. osxphotos does have a osxphotos push-exif command that "pushes" (writes) metadata from photos to the original file in the library. This would partially work for step 1 and step 3. I say partially because this command does give some control over the metadata written it does not deal with creator, copyright, etc. You can't specify custom fields (but you can specify custom values for the supported fields). The options, available in the docs are:
There is currently no option to read the EXIF data back into Photos (with exception of date/time/timezone which Photos can sometimes mess up -- see osxphotos timewarp which has a There's also a batch-edit command that allows you to batch edit title, keywords, etc. (and has a template system to dynamically set these) but it does not support some of the fields you want to use. If you know how to write code in python, you could create a scrip to do this exact workflow using the components provided by osxphotos. For example the ExifTool class provides a way to use exiftool to read & write metadata. exiftool can do everything you want if you learn how to use it. Here's a way to get a list of files you just imported into a specific album for example:
Obviously you change the time frame from "2 hours" to whatever makes sense for you and the album name from "YourAlbum" to the album you're working in. This prints a list of all the photo paths to the original files which can then be fed to exiftool to write additional fields. Keep in mind that this is the path to the original referenced photo. When Photos edits a photo, it keeps the edited version in a different path inside the library, not with the original referenced image. It sounds like you're trying to use Photos as a digital asset management tool it isn't designed to be. You might be better off with Lightroom or DigiKam, etc. For reference, these are the EXIF/IPTC/XMP fields that osxphotos writes to which as you can see does not include all the fields you want:
|
Beta Was this translation helpful? Give feedback.
-
@RhetTbull : Thank you for your detailed response. It has given me some way forward. I could have used Lightroom but a) it is an expensive product, b) it does not do Reverse-Geocoding. Are you aware of any tools (GitHub, OpenSource) that could take a photo file as input and reverse-geoencode the GPS location information contained in the photo to location, city, country, etc...? Essentially, what I need is the Location. City, County, Country returned as variables (or in some shape & form) - I am confident that I could do the rest in ExifTool.... and then as you suggest, import the photos after this processing. I am conversant with Exiftool and use it quite often, but I am not great with python. |
Beta Was this translation helpful? Give feedback.
-
My setup:
Workflow:
Requirements (What I need some help for)
For all photos just added to this newly created album
Step 1 - First pass...
Write EXIF data to be written to original files...
Creator: "John Smith"
Copyright: "Copyright © John Smith"
Rights Usage: "All Rights Reserved"
Ensure that this newly written EXIF data is now read back by Photos
Step 2 - I will now manually edit the Titles in macOS Photos(if required and make it more suitable)
Step 3 - Second Pass...
Write EXIF data to be written to original files...
Ensure that this newly written EXIF data is now read back by Photos
I am trying to read the documentation and understand the various command line options, but would appreciate if anyone could provide me the command line options for Step 1 and Step 3.
Thanks...
Beta Was this translation helpful? Give feedback.
All reactions