Request a new feature, or support for a camera/lens that you would like to use in Capture One.
Currently, Capture One happily displays EXIF metadata - including GPS Latitude, Longitude, Altitude if present - when working with images (CR3s in my case). However, as with all other EXIF fields, they're only displayed as read-only and can't be edited inside Capture One.
https://support.captureone.com/hc/en-us/articles/5333146130845-GPS-location-data
This may be a "philosophical" choice ... that CO does not want to ever modify data that was baked in by the camera/scanner. And for fields relating to camera and exposure, I can even understand that. But GPS information "feels" different, mainly because the vast majority of cameras don't yet have built-in GPS, and because so much other software takes advantage of geolocation information. Even CO itself, if it finds geo data, shows the extra "Open in browser" link.
So, as an ideal first step, I'd love to see the EXIF-GPS fields become editable in the metadata panel, rather than just read-only. And having the ability to apply the same GPS information to a batch of selected images.
A future stretch goal would be to also add this information in some form to the library filters, to be able to find photos near a particular GPS location / within a certain area around a particular place/landmark/set of coordinates.
If this "philosophical" decision can't be changed - if you're unmovable on the "EXIF data must be retained as is, it's not our job to change what the camera/scanner baked in" - then a possible alternative would be to at least include the IPTC Extension schema structure fields for GPS-Latitude, GPS-Longitude, and GPS-Altitude https://www.iptc.org/std/photometadata/documentation/userguide/#_locations - and make these fully editable (like all other IPTC fields in the metadata panel). Add the same "Open in browser" link to them, and let users choose these fields to be used when exporting an image to bake in its GPS coordinates.
Current workaround
Current workaround is to use one of the many (horrid or half-broken, particularly on Windows) third party tools to try and edit EXIF data (like ExifTools, or varying pieces of software like abeMedia that look like they were designed by programmer, straight from the Windows XP days) and inject GPS coordinates into either the source file itself (again, in my case, CR3s) or to some XMP sidecar file, then go back into Capture One and load/sync metadata. This feels like a hacky unnecessary roundtrip that grinds workflow to a halt when you have more than just a handful of images you want to geotag. |
See this: https://captureone.ideas.aha.io/ideas/FR-I-175