Participating Frequently

P: Map markers are not updated when photos are moved in the map module

Forum|Forum|3 months ago
May 21, 2026
47 replies
1056 views

Just starting today the Map module is leaving behind markers for a photo or photos that have been moved. It also continues to show markers for photos that have been opened but are no longer in the directory being worked in. If I leave LRC and come back in, all is well but I've never had to do this before. It is more of an annoyance than a major issue, but it does clutter up my screen while moving things. I am in the process of locating old photos that have inaccurate or no geotagging and this behavior is slowing me down. I’m running 15.3 on a MacBook Air. Has anyone else seen this or have a suggestion of how to fix this behavior?

Pinned Reply By bill_9508

I downloaded 15.5 and the issue appears to solved. Thanks to Adobe and to the kind people in the LRC community who got this into the bug queue.

Show previous replies

J

JOSHUA26056534urbo

Participant

It's honestly so frustrating. I've spent so much money on the annual subscription, yet they’ve let such a basic bug drag on for over a month without any fix. It’s negatively impacting users' workflow and mood, and slowing down everyone's photo processing speed. Truly speechless.

S

SamSegar

Inspiring

I’m seeing the same issue and the markers are usually corrected if Lightroom Classic is re-started, but I’m seeing some markers that stubbornly remain without being associated with an image.

sarurunn

Participant

最近マップの表示がおかしかったのでがそうでしたか・・

早く改善して欲しいですね

P

pitn123

Participant

I’m having the same problem.

ThiLucMic

Participant

Lightroom Classic 15.4

Lorsque je sélectionne une collection dans Library et que je passe au module Map, les éléments de la collection sélectionnée sont affichés, mais les éléments d’une ancienne sélection ne sont pas supprimés. Dit autrement : Map ne synchronise pas les éléments à afficher avec Library, et il accumule les éléments.

dj_paige

Legend

This has been reported and Adobe is investigating this bug. Please go to this thread and vote for it.

martin_4359

Participant

There is a persistent UI refresh/caching bug in the Map module under Windows. When changing from one folder to another, the pins from the previously viewed folder do not disappear. Instead, they remain visible on the map, meaning that pins from multiple folders get stacked or "added up" on the screen.

Even switching to the Library module, selecting a different folder, and going back to the Map module does not clear the old pins. No filters are active, and the single, newly selected folder is correctly highlighted in the panel, but the map rendering is frozen with old data.

Lightroom Classic version: 15.3.1
Camera Raw version: 18.3
OS version: Windows 11 25H2

Steps to reproduce:

Open the Map module and select Folder A (pins are displayed correctly).
Go to the Library module, select a completely different folder (Folder B).
Switch back to the Map module.

Expected result:
The map should refresh and only display the pins belonging to the newly selected Folder B.

Actual result:
The pins from Folder A remain visible on the map alongside Folder B. Triggering a full catalog selection even causes all pins to persist permanently on the map.

W

WDBerlin

Inspiring

I Have the same problem since several days. It’s a severe bug because you can not do any workflow using maps!

johnrellis

Legend

It appears that the Map module was coded against an old, deprecated version of the Google Maps API, and the Google Maps API implementation changed very recently. I’ve tested versions back to LR 12.5 and the Map module misbehaved in the same way, indicating a change on Google’s side.

See this bug report:

Maybe add a precise step-by-step of your symptoms to that bug report and vote for it?

dj_paige

Legend

It appears that the Map module was coded against an old, deprecated version of the Google Maps API, and the Google Maps API implementation changed very recently. I’ve tested versions back to LR 12.5 and the Map module misbehaved in the same way, indicating a change on Google’s side.

See this bug report:

Maybe add a precise step-by-step of your symptoms to that bug report and vote for it?

Thanks, John.

Rikk Flohr_Photography

Thanks for the recipe, @johnrellis I have logged a bug with the team.

Rikk Flohr: Adobe Photography Org

dj_paige

Legend

I am seeing the same bug. It is good that Rikk has logged a bug report.

For me, here are the step-by-step instructions:

Open Lightroom Classic in Lightroom Classic 15.3. (I observe the same problem in Lightroom Classic 15.2.1 and 15.0)
In the Library Module, select a folder (or keyword or collection).
Then switch to the map module. The pins of the photos in the selected folder (or keyword or collection) are in the proper place.
Go back to the Library Module. Select a different folder (making sure that only one folder is selected, and that you have not accidentally chosen two folders)
Go back to the Map module. Observe that photos from both folders are now seen on the map.

Re-starting Lightroom Classic doesn’t always clear the error. Resetting the preference file seems to always clear the error, but after you reset the preference file, and go through the above steps, the problem returns.

Show more replies

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.