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

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.

I also have this problem

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!

Does it work when you manually add the GPS data in the panel?

Having same issue in last day. Was working fine and then not. Cannot drag and drop pins onto map.

Below is copy of version. Running catalogue of USB. Have tried installing previous version. Not good sometimes allows me to drop one photo then stops again. Can move pin around map but does not affect GPS coordinates. 

As stated elsewhere, far too many bugs! Please. Project effectively stopped by this until another programme can be found.

Thank you,

R

Lightroom Classic version: 9.3 [ 202005281810-476e492c ]
License: Creative Cloud
Language setting: en
Operating system: Windows 10 - Home Premium Edition
Version: 10.0.18362
Application architecture: x64
System architecture: x64
Logical processor count: 4
Processor speed: 2.4 GHz
SqLite Version: 3.30.1
Built-in memory: 8057.5 MB
Real memory available to Lightroom: 8057.5 MB
Real memory used by Lightroom: 628.2 MB (7.7%)
Virtual memory used by Lightroom: 593.2 MB
GDI objects count: 821
USER objects count: 2282
Process handles count: 2071
Memory cache size: 72.6MB
Internal Camera Raw version: 12.3 [ 493 ]
Maximum thread count used by Camera Raw: 3
Camera Raw SIMD optimization: SSE2,AVX
Camera Raw virtual memory: 35MB / 4028MB (0%)
Camera Raw real memory: 35MB / 8057MB (0%)
System DPI setting: 96 DPI
Desktop composition enabled: Yes
Displays: 1) 1920x1080
Input types: Multitouch: No, Integrated touch: No, Integrated pen: No, External touch: No, External pen: No, Keyboard: No

Interesting, Jerome - although when I switched off GPU acceleration it also let me place items on the map, so I'm not sure how any issue with catalogue corruption would be obviated by that sort of switch.

This is good information Jérôme Caron thanks for posting the result of your interaction with Lightroom Engineering.  It is possible to repair corrupt catalogs but I am not certain if that will work for your issue.  It might get you past the unknown error you are seeing.

Ladies and gentlemen,

I have very good news for you.

After many months waiting for a solution, asking assistance from Adobe with no luck, I finally was able to definitively solve this issue with an Adobe engineer.

I hope my solution will solve your issue as well, I'm confident it will 🙂

Basically, root cause of this issue is catalog corruption.
And this is a form of unknown corruption ; at least the integrity control that is done when doing a backup doesn't detect it.

What you have to do :

* Create a new catalog
* Use the import from existing catalog option and select your current catalog (no impact on this catalog, don't worry)
* if you are like me, you will face an unknown error somewhere during the import. This is expected. Stop the process and check what has been imported in your folder list ; it will give you an indication of where the corruption is located in your catalog.
* restart the import catalog but this time, select only folders after the corrupted part in order to import a maximum of pictures.
* now test the Map module and... tell me if this is working for you !

Hello, still not fixed with latest version of Lightroom classic. Amazing !

Still not working for v.9.1 for me - has anyone found a solution for this? I can't believe this major part of functionality has been broken for so long.