Aperture has generated GPS metadata that doesn't strictly conform to the EXIF standard -- it is missing GPSVersionID. You could fix it up using the free Exiftool. See this thread for more details about the problem and assorted possible workarounds: Re: Aperture importer plugin does not import GPS data
HoudahGeo and exiftool I tested, is not working.
Upload one of the sample JPEGs to Dropbox and we can take a look at what's going on and provide an exact recipe for fixing the file.
Data in exiftool https://www.dropbox.com/s/upvt7rh4f47ay3e/Daten%20im%20Bild.jpg?dl=0
Ah, the problem with the sample JPEG is that Lightroom ignores XMP sidecars for JPEGs -- it expects to find the XMP embedded within the JPEG file itself. I embedded the XMP within the JPEG using this command:
exiftool -tagsfromfile 2014-05-24\ um\ 16-24-19.XMP 2014-05-24\ um\ 16-24-19.JPG
When I then imported the JPEG into LR, it picked up the GPS coordinates. (As a side note for reference by others, it appears that the latest version of LR now accepts EXIF GPS that's missing the GPSVersionId and GPSMapDatum fields.)
How did you generate the XMP sidecar file?
Re HoudahGeo, I don't have any direct knowledge about it -- I can only report what others have said about it. Perhaps someone else here can help you.
This article has a reputation for being authoritative about migrating from Aperture to LR: Moving from Aperture to Lightroom – Lightroom Solutions – John Beardsworth. It links to this article recommended HougahGeo for migrating GPS: Save Aperture and iPhoto Places Geotags to EXIF | PhotoApps.Expert
The xmp is Aperture. Capture One can also read. I have Adobe Support contacted 2 Weeks ago. But there is now hibernating.
It's very unlikely Adobe Support will be able to help on this issue.
From what's reported on other threads, the XMP generated by Aperture will contain GPS coordinates that were embedded with the photo before it was imported into Aperture (e.g. by the camera). But that XMP won't contain GPS coordinates that you added within Aperture. So I think you have two options:
- If you didn't add any GPS coordinates within Aperture itself, you can use Exiftool to copy the XMP from the sidecars generated by Aperture back into the exported JPEGs. Then you can import those JPEGs into Lightroom (or if they are already in Lightroom, you can do Metadata > Read Metadata From File to get Lightroom to read the newly added GPS).
- If you did add GPS coordinates within Aperture, you'll have to use HoudahGeo (and find someone who can help you make it work).
You need to add the GPS data in Aperture, then export the version as a JPEG. Don't export the data separately as a sidecar. I don't think Aperture will include GPS data if you export as original (maybe with DNG or other format, or with RAW with sidecar).
If you export original with the option of adding the sidecar, then use a tool to write the sidecar into the JPEG. exiftool works, as John explained, but you could also use Graphic Converter (which probably uses exiftool, but might be easier to use).
I had to do a bit of a workaround with a similar problem. Instead of using sidcars to the jpegs, I exported jpeg copies of each file, so the jpegs acted as a sort of sidecar to the original jpegs, like img1234.jpg and img1234copy.jpg, and so on. Then I used Syncomatic to move the data from the jpeg copies into the original jpegs, then deleted all the copies. Syncomatic - Sync files with same name or time
Stupid world of Adobe.
When exporting a working copy of Aperture, the GPS data are preserved. Not when exporting the original files.
I think the simple way is to export original with XMP and write back with Graphics Converter. For I have eg. 20000 images mixed in 100 folders with raw and jpg. In the future, I'm just raw images, the works.
I agree; with a ton of images already exported as originals that would work. Or exiftool. But add "stupid Apple" to the list for blame; Aperture's inability to deal with GPS in original files is the source of this problem. See here: https://apertureexporter.com/content/mystery-aperture-not-able-embed-metadata-some-jpegs
Hard to say for me whose fault it. Capture One, the same Photos GPS data read without problems.