search

dfandrich / gpscorrelate

C program to match GPS tracks to photographs, and store the matches in the EXIF data in the photographs.
https://dfandrich.github.io/gpscorrelate/
GNU General Public License v2.0
28 stars 8 forks source link

Sony .ARW files geotagged by gpscorrelate rejected by Lightroom #18

Closed fugwort closed 1 year ago

fugwort commented 2 years ago

gpscorrelate V2.0; Lightroom V6.14; .ARW files from RX100M3

I geotagged some .ARW files with gpscorrelate and tried to import them into Lightroom. Lightroom gave the error message "Failed to find a place for the imported file. (3). Included in the same import was an .ARW file not gotagged, which Lightroom accepted. I verified that the .ARW files were correctly geotagged by opening them with nomacs, which can display the photo's locations on a map.

I was able to geotag some .CR2 files from a Canon G12. Lightroom accepted those files.

dfandrich commented 2 years ago

What happens if you manipulate the same files using the exiv2 command-line? Try adding a random tag and see how Lightroom reacts. It may have something to do with libexiv2. Can you supply a file that Lightroom doesn't like?

fugwort commented 2 years ago

Sorry for the delay in responding. My camera is being repaired, so I can't get a picture and corresponding GPS track. It will be several weeks before the camera is fixed. I'll get back to you then.

John Yates

On Thu, May 05, 2022 at 09:24:25PM -0700, Dan Fandrich wrote:

What happens if you manipulate the same files using the exiv2 command-line? Try adding a random tag and see how Lightroom reacts. It may have something to do with libexiv2. Can you supply a file that Lightroom doesn't like?

-- Reply to this email directly or view it on GitHub: https://github.com/dfandrich/gpscorrelate/issues/18#issuecomment-1119248367 You are receiving this because you authored the thread.

Message ID: @.***>

fugwort commented 2 years ago

Sorry for the delay in responding. The camera I used to take the pictures I described in my original post is being repaired, so I cannot get a picture and GPS track to test gpscorrelate.

However, I have another camera. It is fairly new (Sony RX100mM7) and my version of Lightroom (version 6.14) does not import its files even when not modified by gpscorrelate, but I have a demo copy of Capture One 22 Pro. It can import files from the new camera, but cannot import files from the new camera that have been modified with gpscorrelate or exiv2. I have the following files to send, but the .ARW files are too big, even when sent individually. Any suggestions?

DSC00056.ARW - An unmodified file from the camera. DSC00056-exiv2.ARW - A file modified by exev2. DSC00056-gpscorrelate.ARW - A file modified by gpscorrelate. Current.gpx - The gps track used by gpscorrelate. exiv2.sh - A shell script used to invoke exiv2.

John Yates

On Thu, May 05, 2022 at 09:24:25PM -0700, Dan Fandrich wrote:

What happens if you manipulate the same files using the exiv2 command-line? Try adding a random tag and see how Lightroom reacts. It may have something to do with libexiv2. Can you supply a file that Lightroom doesn't like?

-- Reply to this email directly or view it on GitHub: https://github.com/dfandrich/gpscorrelate/issues/18#issuecomment-1119248367 You are receiving this because you authored the thread.

Message ID: @.***>

dfandrich commented 2 years ago

On Tue, May 17, 2022 at 09:32:16AM -0700, fugwort wrote:

It can import files from the new camera, but cannot import files from the new camera that have been modified with gpscorrelate or exiv2.

If the problem shows up with a file modified by exiv2 itself, then the problem is undoubtedly with exiv2 itself and not gpscorrelate. I would open a bug report with that project instead. Can you take a sample picture with the camera in a low resolution mode and of a simple scene (like a completely white wall) to reduce the file size? exiv2 uses Github (https://github.com/exiv2/exiv2) so you should be able to attach even a large file to the bug report.

dfandrich commented 1 year ago

In the absence of a test file to verify the problem, I'm going to assume the issue is related to libexiv2, not gpscorrelate. gpscorrelate leaves all the file handling up to exiv2, so as long as the tags written are correct (and I haven't heard of other programs complainin), an issue with another program opening the file is most likely to do with ARW support in exiv2.