dan_hartford's profile

524 Messages

 • 

12.6K Points

Fri, Jun 16, 2017 8:03 PM

Lightroom: Map module keeps flashing "map offline" when it's not

Responses

2 Messages

 • 

132 Points

4 y ago

This is incredibly annoying.

 

Lightroom version: CC 2015.10 [ 1111918 ]

License: Creative Cloud

Operating system: Mac OS 10

Version: 10.12 [5]

Application architecture: x64

Logical processor count: 8

Processor speed: 2.6 GHz

Built-in memory: 8,192.0 MB

Real memory available to Lightroom: 8,192.0 MB

Real memory used by Lightroom: 420.7 MB (5.1%)

Virtual memory used by Lightroom: 4,024.3 MB

Memory cache size: 954.7MB / 1,856.4MB (51.4%)

Maximum thread count used by Camera Raw: 8

Camera Raw SIMD optimization: SSE2,AVX

Camera Raw virtual memory: 673MB / 4095MB (16%)

Displays: 1) 1440x900

 

Graphics Processor Info: 

NVIDIA GeForce GT 650M OpenGL Engine

5 Messages

 • 

120 Points

4 y ago

Same issue for me. Every time the map needs a refresh, it goes to the world offline screen.
Here is my dirt. Lightroom 2015.10.1 Camera Raw 9.10.1 MacBookPro9,1, Memory 8GB,  MacOS 10.12.5 on SSD 1TB with 59% available. Plug-ins are disabled in LR also. I seem to recall odd behavior when loading a tract and tagging photos, I may have had to do it twice to get it to tag. Mac OS with two monitors and all of Mission Control turned on.

1 Message

 • 

66 Points

4 y ago

Yep, same here. Incredibly frustrating and renders Map module virtually unusable.  My system is Lightroom 2015.10.1 Release Camera Raw 9.10.1, MacOS 10.12.5, iMac Late 2013, 16GB memory.

1 Message

 • 

64 Points

4 y ago

Same here.

1 Message

 • 

64 Points

4 y ago

Same here 
Mac Sierra 10.12.5
Lightroom 6.10.1
Camera Raw 9.10.1

17 Messages

 • 

280 Points

4 y ago

Same here in Denmark, obviously a adobe cloud issue since all kinds of windows and mac computers from around the world is affected. Would be so much better if Adobe had a user blog with updates on problems, descriping clearly a "Don't panic, this is all our fault on our server, we try to fix it though have no idea when it will be working again, since our lightroom team is currently on vacation..."

5 Messages

 • 

140 Points

or simply "we dont give a fuck about customers complaining from all over the world, keep the money coming ..."

4 Messages

 • 

122 Points

Please don't use offensive language.

Champion

 • 

6.5K Messages

 • 

109.5K Points

aurin r, this is the best place to get updates on problems. A user blog would just end up duplicating everything here. You'll note at the top of the page it says "acknowledged", which means they've been able to reproduce the problem and are working on a solution.

Since it's affected even old versions of Lightroom without Adobe changing anything, this would suggest it's a change on Google's servers, so they'll be working with Google to find a solution (but you know what happens when 2 big companies try to work together...!)

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.

57 Messages

 • 

852 Points

Victoria, your comments are most appreciated, thanks. I would further suggest that (a) knowledge of the bug is circulated among the Helpdesk/support team at the company (which would avoid lengthy and embarrassing discussions) and (b) that Adobe proposes a workaround for the time being. As a customer to some degree I don't really want to depend on whether or not the two companies can get along well or not... just my thoughts.

Champion

 • 

6.5K Messages

 • 

109.5K Points

Unfortunately there is no workaround at the moment, since it's affecting all versions. Either Google will have to make a change on their servers, or Adobe will have to update Lightroom to work with Google's changes. The engineers will be figuring out the quickest solution right now, but I would anticipate it taking a few weeks, to be completely honest with you.

Customer support *should* be aware of it already, but whether the individual members of staff remember what they've been told is always a bit of a lottery. ;)

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.

57 Messages

 • 

852 Points

Ok, thanks for your response. My workaround was to go back to Google Maps in Safari, click on the map, copy the coordinates indicated at the bottom of the page and then paste them into the GPS box in the Metadata panel (to be repeated for each photo with a different location or to be done as a batch for multiple photos). Not very elegant but it does the job for the moment.

Champion

 • 

6.5K Messages

 • 

109.5K Points

That's a good workaround. The alternative would just be to wait till they fix it and then do some catch up tagging.

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.

57 Messages

 • 

852 Points

;-)

77 Messages

 • 

1.9K Points

Since it seems to be an issue with accessing Google Maps, and Adobe is looking at it, perhaps they could consider allowing use of other map servers? Some other applications do this, and it would allow us to use something while the Google Maps issue gets sorted. And it perhaps could allow use of other maps that are better in some situations, like the Open maps, which sometimes show trails and features that Google Maps lacks.

1 Message

 • 

60 Points

Same for me.

Configuration:

MacBook Pro (Retina, 15-inch, Mid 2015)
Processor: 2.8 GHz Intel Core i7
Memory: 16GB 1600 MHz DDr3
Graphics: AMD Radeon R9 M370X 2048 MB, Intel Iris Pro 1536 MB

macOS Sierra 10.12.5

Lightroom version 6.10.1

4 Messages

 • 

112 Points

Ok what has happened is Google changed the API as of June 22nd so the map module is unable to update the Map.

Adobe will not update Lightroom 5.71 to use the new API.

 

However it's not really needed

This plugin Jeffrey Friedl's Blog » Jeffrey’s “Geoencoding Support” Plugin for Lightroom and maybe Jeffrey Friedl's Blog » Jeffrey’s “GPS Proximity Search” Lightroom Plugin still work and gives you many external map viewers as well.

This is great if you have a gpx tracklog to work with.

 

But what if you used the functionality to drop a photo on the map to add gps coordinates.

https://www.snafu.org/GeoTag/  this works for osx select a photo drop a pin on the map (apple maps) and it adds the gps coordinates to the photo. It uses exif tool to write a new file (identical to the old file except for the gps)  you can select the folder with your photos in lightroom and select show in finder start geotag select open and now drag a photo from the finder window to the open dialog box this changes the folder its looking at. hit open all the files are queued up and you can tag. Saving is a bit slow since it recreates the file and puts the old one in trash.  Close GeoTag when finished.  When back in lightroom right click on the photos and select read metadata from file and after a few seconds all the photo's you have added gps coordinates to.

 

Alternatively any mapping app that can give you a gps coordinate can be used, copy the coordinate to the clipboard, paste to the gps field in lightroom. 

 

It may actually be faster to find a coordinate in geotag copy that to the clipboard and paste it in lightroom.

 

You really don't need the actual map tile in lightroom to tag gps data to photos. It would be nice but it's  only a visual aid. Adobe don't want to fix it for Lightroom 5  but as you can see you don't need it.

495 Messages

 • 

10.5K Points

4 y ago

It feels that I am always saying this—when I find a limitation (in this case, a hopefully temporary glitch) in Lightroom, the first thing I do is to search for a plugin that solves or works around the problem. In this case, Jeffrey's Geo-encoding plugin will help you get work done. You can go to a location in Google Earth and move the coordinates to a selected image, or go to the location in Google Earth from an image. For my georeferencing, I need to see overlay maps, which I have in Google Earth, so it is invaluable. But given the current glitch in Lightroom, it might have wider application.

http://regex.info/blog/lightroom-goodies/gps 

16 Messages

 • 

468 Points

4 y ago

From Germany:
For my point of view It is a real Lightroom Problem!
I tried Nikon ViewNXi wich also has a map module , and this does not have the described behavior. Also no problems in Zoner Photo Studio! 
The Problem is Lightroom!!! 

Such big Players as Adobe and Google shold have a direct communication channel to locate and fix this Problem. Why does it take so much Time?! Lightroom is a professional tool, why do users have to spend so much time in looking for a turnaround? 


Regard
Mikel from Germany

77 Messages

 • 

1.9K Points

4 y ago

For those who have macOS and want to geotag whilst Lr is getting fixed, I'd strongly suggest Houdah Geo. It's a dedicated geottagging application. For Lr users it's superb, even if you sometimes use the Map module to tag.

Houdah Geo has a media browser that can access Lr's folders and collections. So if you have imported, all you need to do is select the say dated folder, add the images, and then geotag 'em. You can use GPS tracks, other images, one of three maps, etc. Then have Houdah Geo process the images by writing to the files or sidecars. You can also do soe reverse geocoding, lookup elevation, and even some keywording. Houdah Geo writes the info; then you go back to Lr and do a "read metadata..." or Synchronize Folder and bingo, you're set.

If you use the Map module to find, a bit trickier. I'd suggest when you get Lr's Map to work you set a Location. Then you can  use the "Map Location" criteria in the Filter bar (thanks to Ms. Bampton, our Lr Queen, for pointing this out to me) to get all the images in that place. I have added a request to Adobe to fix Smart Collections so that you could make a Smart Collection with the Map Location as a criteria; for some reason it's missing, and this would then allow access dynamically to images added to an area without having to visit the Map module. https://feedback.photoshop.com/photoshop_family/topics/lightroom-allow-use-of-map-location-in-smart-...

6 Messages

 • 

234 Points

Anyway, I don't want to pay one more time $39 just for a feature included in LR I paid yet !

7 Messages

 • 

308 Points

4 y ago

For me this is probably the most annoying bug in Lightroom I have ever seen. Please fix this asap!

1 Message

 • 

62 Points

4 y ago

+1
Version de Lightroom : CC 2015.10.1 [ 1117303 ]
Licence: Creative Cloud
Système d'exploitation : Windows 10
Version : 10.0

7 Messages

 • 

166 Points

4 y ago

This reply was created from a merged topic originally titled Maps is outstanding.

Hello, when I use the module map of lightroom CC 2015.10.1 modulates it map posts me non-stop " the map is outstanding " when I move on this one.
I verified my internet connection, used another connection (iPhone SE(sharing)), reset my dock, verified the OS permissions OSX sierra, be made the last update of lightroom the problem persists.

I found nothing on the Internet to resolve this dysfunction.

1 Message

 • 

62 Points

4 y ago

Me too.

Lightroom version: CC 2015.10.1 [ 1117303 ]
License: Creative Cloud
Operating system: Windows 10
Version: 10.0
Application architecture: x64
System architecture: x64
Logical processor count: 8
Processor speed: 3.4 GHz
Built-in memory: 16321.4 MB
Real memory available to Lightroom: 16321.4 MB
Real memory used by Lightroom: 1252.4 MB (7.6%)
Virtual memory used by Lightroom: 1565.7 MB
GDI objects count: 726
USER objects count: 3283
Process handles count: 2878
Memory cache size: 0.0MB / 3824.3MB (0.0%)
Maximum thread count used by Camera Raw: 8
Camera Raw SIMD optimization: SSE2,AVX,AVX2
Camera Raw virtual memory: 518MB / 8160MB (6%)
System DPI setting: 96 DPI
Desktop composition enabled: Yes
Displays: 1) 1920x1200
Input types: Multitouch: No, Integrated touch: No, Integrated pen: No, External touch: No, External pen: No, Keyboard: No
Graphics Processor Info:
GeForce GTX 760/PCIe/SSE2
Check OpenGL support: Passed
Vendor: NVIDIA Corporation
Version: 3.3.0 NVIDIA 382.33
Renderer: GeForce GTX 760/PCIe/SSE2
LanguageVersion: 3.30 NVIDIA via Cg compiler

9 Messages

 • 

326 Points

4 y ago

Me too and it's driving me batty as I have so many images to geoencode at this time of year. Here's my info: 
Lightroom version: CC 2015.10.1 [ 1117303 ]
License: Creative Cloud
Operating system: Windows 10
Version: 10.0
Application architecture: x64
System architecture: x64
Logical processor count: 8
Processor speed: 3.5 GHz
Built-in memory: 32641.7 MB
Real memory available to Lightroom: 32641.7 MB
Real memory used by Lightroom: 1602.3 MB (4.9%)
Virtual memory used by Lightroom: 1703.4 MB
GDI objects count: 471
USER objects count: 1793
Process handles count: 1722
Memory cache size: 504.6MB / 7904.4MB (6.4%)
Maximum thread count used by Camera Raw: 8
Camera Raw SIMD optimization: SSE2,AVX
Camera Raw virtual memory: 590MB / 16320MB (3%)
System DPI setting: 96 DPI
Desktop composition enabled: Yes
Displays: 1) 2560x1440
Input types: Multitouch: No, Integrated touch: No, Integrated pen: No, External touch: No, External pen: No, Keyboard: No

Graphics Processor Info: 
GeForce GTX 650/PCIe/SSE2

Check OpenGL support: Passed
Vendor: NVIDIA Corporation
Version: 3.3.0 NVIDIA 382.05
Renderer: GeForce GTX 650/PCIe/SSE2
LanguageVersion: 3.30 NVIDIA via Cg compiler


Application folder: C:\Program Files\Adobe\Adobe Lightroom
Library Path: D:\LR Database\Lightroom Database 6.lrcat
Settings Folder: C:\Users\image\AppData\Roaming\Adobe\Lightroom

Installed Plugins: 
1) AdobeStock
2) Canon Tether Plugin
3) Facebook
4) Flickr
5) HDR Efex Pro 2
6) Helicon Focus Export
7) jf PhotoSafe
8) Leica Tether Plugin
9) Nikon Tether Plugin
10) ProShow Producer
11) ProShow Web

Config.lua flags: None

Adapter #1: Vendor : 10de
Device : fc6
Subsystem : 26503842
Revision : a1
Video Memory : 995
Adapter #2: Vendor : 8086
Device : 162
Subsystem : 84ca1043
Revision : 9
Video Memory : 20
Adapter #3: Vendor : 1414
Device : 8c
Subsystem : 0
Revision : 0
Video Memory : 0
AudioDeviceIOBlockSize: 1024
AudioDeviceName: Speakers (Realtek High Definition Audio)
AudioDeviceNumberOfChannels: 2
AudioDeviceSampleRate: 48000
Build: LR5x8
Direct2DEnabled: false

2 Messages

 • 

72 Points

4 y ago

Reminds me of not being able to find a solution for the eyedropper WB sampling cursor not matching up on my 4K monitor to let me see what pixel I am actually picking my balance from.  I just grow weary of concerns posted so long ago not being easily addressed/answers found on leased products.  Not everyone has anywhere near the same hardware/software combos, but some of the stuff is common enough it should become a higher priority than in trying to acquire a massive collection of average quality images to license to commoners in advertising.  No?