Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
  • 한국 커뮤니티
0

Lightroom is not correctly adding GPS data

Explorer ,
Nov 09, 2017 Nov 09, 2017

I only have altitude data on my imported files and not the coordinates.  I am a CC subscriber and using Lightroom Classic CC on a 2016 MacBook Pro, but this issue has existed with every version of Lightroom I have had since I got my camera in July.

I am geotagging from my Olympus Em-1 Mk2.  I have worked through this extensively with Olympus and DPReview forums, and we have proved the issue is with Lightroom, but I am the only Lightroom user experiencing this, to the best of my knowledge.

I shoot RAW plus JPG and use the Olympus share App on my phone to tag the images.  Once tagged my SD card has the .ORF and .JPG files in one folder and the .LOG file in a separate folder.  If I look at the JPG file in Preview this file has the correct GPS coordinates.

When I import to LR, the JPG file is treated as a sidecar file, and an XMP file of metadata is created.  This XMP file contains 3 entries only for GPS information, and these entries do not exist on the XMP file of an image I have not previously geotagged.  They look like this:

   exif:GPSAltitudeRef="0"

   exif:GPSAltitude="38/1"

   exif:GPSStatus="A"

The log file created by the Olympus Share app looks like this, but the act of applying the geotagging in camera is supposed to render the file unnecessary and in any case it can't be read by LR if I try to add it manually as a tracklog:

$GPGGA,102840.86,5045.227534,N,00154.356330,W,1,00,00.00,40.216339,M,0.0,M,,*46

$GPRMC,102840,A,5045.227534,N,00154.356330,W,000.0,000.0,091117,*22

$GPGGA,102851.99,5045.234609,N,00154.366720,W,1,00,00.00,42.296082,M,0.0,M,,*48

$GPRMC,102851,A,5045.234609,N,00154.366720,W,000.0,000.0,091117,*2b

$GPGGA,102904.99,5045.231539,N,00154.358598,W,1,00,00.00,40.605408,M,0.0,M,,*4a

$GPRMC,102904,A,5045.231539,N,00154.358598,W,0.210583,176.132812,091117,*25

$GPGGA,102926.99,5045.226278,N,00154.360595,W,1,00,00.00,38.997192,M,0.0,M,,*45

$GPRMC,102926,A,5045.226278,N,00154.360595,W,0.102592,140.976562,091117,*20

$GPGGA,104535.99,5045.226034,N,00154.359956,W,1,00,00.00,37.005127,M,0.0,M,,*4d

$GPRMC,104535,A,5045.226034,N,00154.359956,W,000.0,289.335938,091117,*1e

Iphone operating system, Olympus App and Mac operating system are all up to date, as well as Lightroom.

From what I can interpret, the import module is reading the GPS information from the JPG sidecar to create the XMP.  I don't know how to prove if the ORF (Olympus Raw File) has anything written to it. 

If nothing else, I'd love a technical explanation of the steps a working version of Lightroom should take in the instance descibed above, to help me investigate further. 

Thanks for reading

1.1K
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 1 Correct answer

Explorer , Nov 10, 2017 Nov 10, 2017

iThanks for getting back to me

finally fixed this yesterday. I am using an import preset to add copyright and other metadata

For reasons I can’t explain, the GPS box was checked but since there was nothing in the value field the coordinates were being overwritten on import.

Once unchecked, I successfully reimported a tagged file and located it on the map.

Translate
LEGEND ,
Nov 10, 2017 Nov 10, 2017

The most efficient way to troubleshoot this is to upload a sample .orf and .jpg taken directly from the card to Dropbox or similar and post the sharing link here.  We can then see directly what's going on.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Nov 10, 2017 Nov 10, 2017

iThanks for getting back to me

finally fixed this yesterday. I am using an import preset to add copyright and other metadata

For reasons I can’t explain, the GPS box was checked but since there was nothing in the value field the coordinates were being overwritten on import.

Once unchecked, I successfully reimported a tagged file and located it on the map.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
Nov 10, 2017 Nov 10, 2017
LATEST

That's a common mistake that the user interface fools people into making.  Glad you got it resolved.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines