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

JPEG files have GPS metadata stripped at import

Explorer ,
Oct 01, 2024 Oct 01, 2024

Copy link to clipboard

Copied

When I import images into Lightroom Classic from my phone or SD CARD with GPS metadata in the file Lightroom classic actually deletes the GPS information from the JPG file.

 It makes no difference if you ADD or COPY the image except that ADD will destroy the metadata in the image so it will be forever lost.

 

You can recover the GPS data if you copied the JPG image by copying the file to the lightroom stored location and then reread the metadata from the file.

 

I can't use lightroom mobile which syncs with the GPS metadata intact into lightroom classic because i am often doing this in locations with no WiFi or mobile signal to achieve this and to safe guard the images.

 

I have been complaining about this for a long time. I am now about to dump Adobe as they are incapable of fixing minor bugs in the software. I will wait one more month to see if this simple fix can be achieved before going to ON1 where it works.

TOPICS
macOS , Windows

Views

271

Translate

Translate

Report

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

LEGEND , Oct 01, 2024 Oct 01, 2024

First, are you applying a Metadata preset at Import that deletes GPS info? Could you have perhaps accidentally turned this on? Please check. Perhaps that is the problem.

 

Also, photos captured on my phone have a GPS location assigned by the phone, these import properly into my LrC (13.5.1) and Windows 11 and the GPS metadata from the phone appears properly in LrC.

 

So I think you have jumped to an asbolutely unwarranted conclusion that Adobe is incapable of fixing minor bugs. Most likely, because

...

Votes

Translate

Translate
LEGEND ,
Oct 01, 2024 Oct 01, 2024

Copy link to clipboard

Copied

First, are you applying a Metadata preset at Import that deletes GPS info? Could you have perhaps accidentally turned this on? Please check. Perhaps that is the problem.

 

Also, photos captured on my phone have a GPS location assigned by the phone, these import properly into my LrC (13.5.1) and Windows 11 and the GPS metadata from the phone appears properly in LrC.

 

So I think you have jumped to an asbolutely unwarranted conclusion that Adobe is incapable of fixing minor bugs. Most likely, because most people don't see this issue, Adobe does not see this as bug that need to be fixed; they think it is something unique to your LrC. You don't have to like it, you are free to jump to ON1, but I disagree with your statement.

Votes

Translate

Translate

Report

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
Adobe Employee ,
Oct 01, 2024 Oct 01, 2024

Copy link to clipboard

Copied

[Posted in the wrong forum: Moving to Lightroom Classic.] 

Tested:

  • Lightroom Classic 13.5.1 on Mac OS 14.6.1
  • Canon 5D Mark IV with GPS Active
  • Shooting Large JPEGs + Raw

 

  1. Allow GPS to acquire
  2. Shoot images onto an SD Card
  3. Import jpgs into Lightroom via Copy from the SD Card
    4. Interrogate GPS Data in Metadata Panel and the Map Module

    Result: JPEGs have location information for altitude, longitude, and latitude. They show up in the proper location in the Map module.

    I am unable to reproduce your findings using the steps listed above. 

 

Note:
I have searched your forum posts back to 2009 and found no previous mention of this failure mode. 

 

 

Rikk Flohr: Adobe Photography Org

Votes

Translate

Translate

Report

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 ,
Oct 01, 2024 Oct 01, 2024

Copy link to clipboard

Copied

My complaints have been on the chat abnd phone not in the forum. I kept being told it will be fixed in the next update. No suggestions up until now that i am doing something wrong.

Votes

Translate

Translate

Report

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
Adobe Employee ,
Oct 01, 2024 Oct 01, 2024

Copy link to clipboard

Copied

@dj_paige 's suggestion is likely the cause. 

Rikk Flohr: Adobe Photography Org

Votes

Translate

Translate

Report

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 ,
Oct 01, 2024 Oct 01, 2024

Copy link to clipboard

Copied

Rikk,

Well i just tested import without my custom metadata  preset and it worked. Tested it with my custom metadata preset and it fails. So i then created a new custom metadata preset and tested it and it works. So apologies for my rant and the bug report but nobody in adobe chat or on the phone suggested this as an issue.

The custom metadata preset came from V6 catalogue which got upgraded several versions ago. I am now wondering if there are more issues which i think of as bugs with my installation. Is there a safe way of creating a new catalogue and importing all my photos and metadata into this new catalogue?

Votes

Translate

Translate

Report

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
Adobe Employee ,
Oct 01, 2024 Oct 01, 2024

Copy link to clipboard

Copied

Generally, I advise against creating new catalogs unless it is necessary. I'm not hearing anything yet that I would deem 'necessary.' 

The rogue metadata template wiping out data is a process nuance that bites several people (me included). I would consider it an aberration rather than a systemic indicator. I recommend that as you encounter your 'bugs,' you post them here in Lightroom Classic Discussions for the Legends and Community Experts to review. Some of them may have simple, flexible explanations and not require the angst of porting to a new catalog. 

 

Regarding new catalogs, there are some best practices you can follow, and bits of data will be lost (Publish Services collections come to mind). Essentially, there are two paths:

  1.  Export all of your existing catalog to a new catalog
  2.  Create a new catalog and import your existing catalog

    Both would benefit from a prudent clean-up of your existing catalog, and several people here can advise on the best practices.  I think it would be premature to recommend you create a new catalog, but that is a decision your comfort level and current frustration will dictate. 


Rikk Flohr: Adobe Photography Org

Votes

Translate

Translate

Report

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 ,
Oct 01, 2024 Oct 01, 2024

Copy link to clipboard

Copied

LATEST

Thanks for all your help with this problem, I was getting really frustrated with it.

I will take your advice and not change the catalogue and post any issues I get here, if I get any. I checked all my other presets that I had generated for each year I had used lightroom and they were all corrupted. I have now deleted all of them.

Roger

Votes

Translate

Translate

Report

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