charlie_ping's profile

37 Messages

 • 

810 Points

Tue, Mar 5, 2019 12:36 AM

Lightroom Classic: Drag and drop GPS tagging not working. Right click on map also not working

I cannot geotag photos in the 'Maps' module of Lightroom 8.2. Drag & Drop does nothing, and right click 'set selected photos GPS coordinates' does nothing. There is no error, no message, no metadata is updated at all. 

On initial startup, if I am very quick, I can drag & drop a photo successfully. But ~15 seconds after startup it stops working. 

My issue is identical to those posted here. https://feedback.photoshop.com/photoshop_family/topics/lightroom-8-latest-update-win10-drag-and-drop...

v8.2 seemed to solve the problem for many, but it did not help me. 

I have provided sample photos and logs to Adobe staff already and communicated with them, but as the original thread is now marked 'solved' I have created a new one. 

I have address book enabled. I am on OS Windows 7 Ultimate.

Responses

14 Messages

 • 

376 Points

9 m ago

Since the LrC 9.3 Update, this geotagging no longer works for me now.

For years geotagging my photos has been a critical part of my workflow. I accomplish that by highlighting my photos, adding the address to the Map view, and then right clicking on the map to add the coordinates to the selected photos. Since the 9.3 update, right clicking on the map still produces the "Add GPS Coordinates to Selected Photos" popup dialog, but selecting it does nothing. Very frustrating as this is a critical part of my workflow!

37 Messages

 • 

810 Points

The issue is that LR always populates place names using Address Lookup when you use the GPS tagging feature. Sometimes that gets stuck, and it crashes GPS tagging. Unfortunately, you can't disable the Address Lookup feature that is causing the issue.

A new catalog can help, because it might not include the photos that don't work with Address Lookup, but once those photos are back it crashes again.

Adobe knows about the issue and has for a long time, I spent many hours with their engineers reproducing it. But they won't fix it. They don't care. 

9 Messages

 • 

204 Points

9 m ago

I also have this problem

20 Messages

 • 

414 Points

9 m ago

To solve this issue, you need to fix your catalog that is certainly corrupted.
Use the import catalog feature to evaluate if all your photos can be imported. When your catalog corruption will be fixed, the GPS geotagging will be OK.
Trust me. I had this issue for 2 years.

9 Messages

 • 

204 Points

Hi Jerome, thank you for your reply. I had run a support ticket after I posted and we tried the following steps:

1. Set up test catalog with 10 images to test gps drag and drop (map module works fine with no issues on drag and dropping images to map or adding selected images by right clicking location)

2. import my primary catalog (of 18,529 images) to the test catalog as part of troubleshooting. The import took a long time but seemed to end prematurely. The customer service agent dialled off the session so I don’t know what he would have recommended as next steps but it hasn’t fixed the issue. Drag and drop won’t work. I can’t write GPS details to the selected images using map module at all.

Adobe - can you help? I really need this workflow for my project

20 Messages

 • 

414 Points

Hi, you're on the good way.
What you have to do is to restart the import several time and identify where the import process fail (during a specific folder processing). During next import, exclude the portion of your catalog which is corrupt.
After you have re-run the import, you will have a fresh non-corrupted catalog and you will be able to use the GPS again.
Good luck !

9 Messages

 • 

204 Points

Thanks Jérôme - once I identify the offending folder, I need to exclude that folder from the import?

20 Messages

 • 

414 Points

Correct.

9 Messages

 • 

204 Points

Hi Jérôme - how do I identify the folder that was being imported when the corruption occurs? What happens to me is the import takes a very long time (seems abnormally long for 18,500 images) and gets to about 70% progress before changing to a “stacking images” message. I don’t get an actual error message .

9 Messages

 • 

204 Points

Jerome - your solution sounds the most promising/closest to what I am experiencing, I am not sure I am following your steps quite correctly though

2 Messages

 • 

70 Points

9 m ago

Hello
I'm still facing this issue. 
I opened a ticket and a support team had a look. After several weeks, support team sent me an email as they wanted I test and send back the log file. They ask me to use a config.lua file but it was not sent to me as attached in the email. Then, 1min after, my ticket was closed ! 
I was upset and I call support. The guy was not able to find the file and told me he would have a look. 
Finally, they closed the ticket 1 day after ! 
This is just unbelievable ! 

Then, the workaround I found is to use prefered location. Using this, it works, and GPS details can be added. But it takes so much time every time...
Creating a new catalog did not work for me...

37 Messages

 • 

810 Points

Find a new product. They don't care about us. 

20 Messages

 • 

414 Points

Did you try the steps I explained in this thread ? Are you successfull when you try to import your current catalog ? In other words, are you sure it is not corrupt ?

37 Messages

 • 

810 Points

Yes. I have tried them.

At least in my case (and my case is the original from 2 years ago!) the root cause is not a corruption issue. It is photos that Address Lookup can't handle. Photos off-shore, for example. Or sometimes, just really far from a road. 

I have identified with Adobe that these photos break GPS tagging due to Address Lookup hanging on them. And yes, the catalog becomes corrupted. If I make a new catalog, and exclude these photos, it works again. Of course, that's a huge pain in the ass, because I never know which photo has broken the catalog. But inevitably, another photo breaks it again. And we start over. 

It's a known issue. it's solvable. They just don't care. 

Adobe Administrator

 • 

10.1K Messages

 • 

135.8K Points

Catalog corruption is normally a result of hardware failure, power failure or accidental disconnections of data cables. If you have a catalog that is repeatedly corrupting, it might be prudent to test hard drive, RAM, etc.  Have you done this?

Have you ever had your catalog repaired?
Adobe Photography Products

Quality Engineering - Customer Advocacy

9 Messages

 • 

204 Points

Adobe took my lcat. catalog for repair but it hasn’t solved my issue. The speed or the import is improved on the repaired catalog but I still can’t add GPS information to any images once the import completes.

Works fine for 10 test images but the GPS completely stops working once I import from the repaired catalog

27 Messages

 • 

400 Points

@Rick Flohr - from the other posts it sounds more like it is due to GPS tagging being broken due to address lookup - would you please comment on that more pressing issue?

37 Messages

 • 

810 Points

@Rikk thank you for your response. The first official response in almost a year. I hope you won't disappear on me now...

Maybe 'corrupt' is the wrong word. But I have had this issue on multiple machines now, and a fresh catalog always fixes it, temporarily until I import photos that cause Address Lookup to hang. Unfortunately, I can't tell which photos these are without a very arduous process. 

Yes I have tested hardware, RAM, replaced RAM, and even replaced my machine. The last thing I heard, 18 months ago from Adobe engineers, was that they understood the problem, and it wasn't my hardware. Then they vanished. 

ALLOW US TO DISABLE ADDRESS LOOKUP please! Surely we don't need LR to require this option to fill in the county or city name in Metadata, at the expense of GPS tagging functionality for some users. 

Adobe Administrator

 • 

10.1K Messages

 • 

135.8K Points

"       The last thing I heard, 18 months ago from Adobe engineers, was that they understood the problem, and it wasn't my hardware. Then they vanished. " 

Can you provide me with information about this interaction? I would like to review it. 
Adobe Photography Products

Quality Engineering - Customer Advocacy

37 Messages

 • 

810 Points

Your very own post in this thread, from 1 year ago, says you were in contact with the engineers. (?) I interacted directly with you and then silence until now...

In May 2019, I met on 'bluejeans' to share my computer with engineers 'Gopinath Srinivasan' and 'Smit Keniya'. Most of what was discussed was verbal. But here is their email response after the meeting: 

"Unfortunately, the requirement to have Address Lookup enabled is mandatory now. From the logs, it appears that there are sign-in issues that cause the Map Service to be blocked initially for certain Locations, and then the geocoding intermittently gets a chance to succeed."

4 Messages

 • 

112 Points

9 m ago

I have the same issue.
When I click on the Map module; it loads the map on the right bottom of the window and dropping a picture on the map does not work.

4 Messages

 • 

112 Points

I tried to disable the GPU acceleration in the Performance Tab in LR Preferences and it didn't work.

4 Messages

 • 

112 Points

I have Lightroom Classic 9.3 Release (subscription).
WIN 10 version 2004.

Champion

 • 

5.8K Messages

 • 

100.4K Points

More troubleshooting steps:

- Update your graphics driver directly from the manufacturer's web site, rather than relying on Windows Update:
https://helpx.adobe.com/lightroom-classic/kb/troubleshoot-gpu.html#solution-4

- Set the option Edit > Preferences > Interface > Font Size to Automatic (or 100%, if that appears as an option).  Restart LR.

- Reset LR's preferences: 
https://www.lightroomqueen.com/articles-page/how-do-i-reset-lightrooms-preferences/

LR sometimes soils its preferences file, and resetting it can fix all sorts of wonky behavior in the user interface.

37 Messages

 • 

810 Points

It isn't a preferences file issue. It's when Lightroom tries to lookup place names using Address Lookup and gets stuck. I went through it with the engineers months (years?) ago. 

'Preferred Location' workaround is tedious, but has always worked. That proves that it is possible to fix this issue.

If you could disable the Address Lookup autofill feature, it would fix the problem. But they won't do that. 

The simple fact is, they don't care about us. They don't even bother to respond any more. My suggestion, is to find a new product.

Champion

 • 

5.8K Messages

 • 

100.4K Points

"It isn't a preferences file issue."

I don't think you can conclude that with Antonio's issue, which may not be "the same issue". Rereading all the posts in this thread and the one one two years ago, it appears Antonio is the only one who reports a seriously corrupted display of the map, which is why I suggested the troubleshooting steps above (update graphics driver, set Font Size, reset preferences).

Note that the preferences file stores a lot more than than just the user settings of options in the user interface. It stores a lot of the application's internal state. LR has a serious architectural flaw that allows the preferences file to get corrupted, and this has been shown to cause a wide range of LR misbehavior.

37 Messages

 • 

810 Points

Fair enough. For me, it does not appear to be a preferences file issue.

4 Messages

 • 

112 Points

TO ADOBE:

My Map still not working properly.

I tried everything suggested in this board and the issue is still there.
Please, understand that some of the suggestions presented here takes a long time to implement due to the size of my catalog. So, that means I have spent a great deal of my personal time to fix the issue to no success.

I urge some tech guru at ADOBE Corporation to please look into the Map issue and if necessary release a software update with a fix. We are loyal subscription customers for years.

Thank you,
Sincerely,

Frustrated Adobe customer somewhere in the old' USA.
  

37 Messages

 • 

810 Points

8 m ago

Nobody at Adobe cares about this. It's fixable, but they don't care. 

9 Messages

 • 

204 Points

I went all the way through troubleshooting with Adobe customer service agents (including seniors). After three or four weeks of emails, calls, uploading catalogs, screen grabs and video captures of the fault they called me to say they can’t fix the fault and it will be resolved in the next release

20 Messages

 • 

414 Points

Did you try the steps I explained previously ? Are you sure your catalog is not corrupt ? To check, just try to import it in a new catalog first.

37 Messages

 • 

810 Points

Yes. 

At least in my case (and my case is the original from 2 years ago!) the root cause is not a corruption issue. It is photos that Address Lookup can't handle. Photos off-shore, for example. Or sometimes, just really far from a road. 

I have identified with Adobe that these photos break GPS tagging due to Address Lookup hanging on them. And yes, the catalog becomes corrupted. If I make a new catalog, and exclude these photos, it works again. Of course, that's a huge pain in the ass. But inevitably, another photo breaks it again. And we start over. 

It's a known issue. it's solvable. They just don't care. 

Adobe Administrator

 • 

10.1K Messages

 • 

135.8K Points

8 m ago

Updates to Camera Raw, Lightroom Classic, and the Lightroom Ecosystem were released yesterday evening and contain a fix for this issue.  Please install the appropriate update and see if it solves this problem. 

You can read more about the updates here: https://feedback.photoshop.com/photoshop_family/topics/lightroom-and-camera-raw-february-2020-release

Thank you for your patience.
Adobe Photography Products

Quality Engineering - Customer Advocacy

37 Messages

 • 

810 Points

Thank you Rikk, I am confused as your link is a February update. Which version of LR has the fix?

27 Messages

 • 

400 Points

I'm a bit confused too, the link is for February 2020 and the link in there to other updates from August doesn't mention this issue? https://helpx.adobe.com/lightroom-cc/...

Champion

 • 

6.5K Messages

 • 

109.6K Points

It's a mistake, looks like a text expander snippet. 

Victoria Bampton a.k.a. The Lightroom Queen

www.lightroomqueen.com

Author of Adobe Lightroom Classic - The Missing FAQ and Adobe Lightroom - Edit Like a Pro books.

Adobe Administrator

 • 

10.1K Messages

 • 

135.8K Points

Yep - copy/paste mistake
Adobe Photography Products

Quality Engineering - Customer Advocacy

27 Messages

 • 

400 Points

OK, might be worth asking them to update the changelog for the Aug 2020 release that I linked to above to mention this too? Definitely be glad to have this finally sorted though!

2 Messages

 • 

70 Points

8 m ago

Personnaly, the new release LRC 9.4 has solved the issue. 

9 Messages

 • 

204 Points

Also resolved the issue for me - thanks for sorting it Adobe and thanks for all the guidance on this thread

20 Messages

 • 

414 Points

Considering this issue is there for more than 2 years, I don't really think it is appropriate to thanks Adobe for fixing it today...

9 Messages

 • 

204 Points

Fair point! :)

27 Messages

 • 

400 Points

Sadly hasn't fixed it for me. I can use tracklogs OK but then if I try and manually place some photos onto the map with tracklog turned off it's still doing nothing :(  Eventually after dragging about 6 times it places them (this is on 100MB broadband too, so not an internet connection issue)

1 Message

 • 

60 Points

1 m ago

Got the same problem with tagging. When I place a point manualy, Lightroom sets the point a few meters away. Got LR 10.11.

Any solution in sight?

Champion

 • 

5.8K Messages

 • 

100.4K Points

Your issue is different. If you're on Windows, see this bug report:

https://feedback.photoshop.com/conversations/lightroom-classic/lightroom-classic-mapping-errors-windows-10/5f5f46024b561a3d426e1b6c 

The first reply in that thread contains two workarounds for this bug.