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

@7721513 Nichols: Pro photographers do use Lightroom in the first place as a RAW converter and catalogue application. This has nothing to do with being perfect or not ... Your comment on that is out of line and just shows you have no idea ...
It's not that we respond to every hickup immediately, in fact this is my first contribution whatsoever. If you read well, you'll see I was over many many years a very satisfied Adobe-customer, but it is a stonecold fact that every update comes with NEW flaws over the last two years, that are time consuming, irritating and in some cases cost plain money. For instance buying an expensive new graphic card (recommended by Adobe) that doesn't work well with both Lr and Ps after all and is a waist of money. That is not why you pay for a professional tool, that can be toroughly tested before bringing out. Adobe is no small shop around the corner and their shares are exploding. So can't be a financial problem to do a good job in advance, instead of annoying us with work frustrating issues.
When things get to complicated to have it running stable, one should consider being on the right path. That's what every professional should do ...
I stick to my comment that quality (in stability) has dropped shortly after anybody got neatly caught in cloud construction and one has no longer to convince customers buying new stuff ... That's almost a business rule of thumb and was therefor a predictable development. 
And another rule of thumb in business: If customers complain, they are ALWAYS right. Your product is customer satisfaction after all ....
The least you may expect is a newsletter saying "sorry customers, we have acknowledged a problem, we are on it and we expect to have it fixed by .... "
That's what we pay for 50 bucks month after month, not to be ignored or having to find out in groups like this, that Adobe is working on it (if this information is right).
You know Franz Kafka?? Well, that is exactly what this is all about. Small customer knocking without reaction on the door of a big powerful ruler of the system little man is caught in.

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

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 

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

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.

Me Too, 
Lightroom version: CC 2015.10.1 [ 1117303 ]License: Creative Cloud
Operating system: Mac OS 10
Version: 10.11 [6]
Application architecture: x64
Logical processor count: 8
Processor speed: 2.0 GHz
Built-in memory: 8,192.0 MB
Real memory available to Lightroom: 8,192.0 MB
Real memory used by Lightroom: 2,412.1 MB (29.4%)
Virtual memory used by Lightroom: 4,416.8 MB
Memory cache size: 1,352.0MB / 1,856.4MB (72.8%)
Maximum thread count used by Camera Raw: 8
Camera Raw SIMD optimization: SSE2,AVX
Camera Raw virtual memory: 1291MB / 4095MB (31%)
Displays: 1) 1440x900

Graphics Processor Info: 
Check OpenGL support: Failed
Vendor: ATI Technologies Inc.
Version: 4.1 ATI-1.42.15
Renderer: AMD Radeon HD 6490M OpenGL Engine
LanguageVersion: 4.10

Me Too, 
Lightroom version: CC 2015.10.1 [ 1117303 ]License: Creative Cloud
Operating system: Mac OS 10
Version: 10.11 [6]
Application architecture: x64
Logical processor count: 8
Processor speed: 2.0 GHz
Built-in memory: 8,192.0 MB
Real memory available to Lightroom: 8,192.0 MB
Real memory used by Lightroom: 2,412.1 MB (29.4%)
Virtual memory used by Lightroom: 4,416.8 MB
Memory cache size: 1,352.0MB / 1,856.4MB (72.8%)
Maximum thread count used by Camera Raw: 8
Camera Raw SIMD optimization: SSE2,AVX
Camera Raw virtual memory: 1291MB / 4095MB (31%)
Displays: 1) 1440x900

Graphics Processor Info: 
Check OpenGL support: Failed
Vendor: ATI Technologies Inc.
Version: 4.1 ATI-1.42.15
Renderer: AMD Radeon HD 6490M OpenGL Engine
LanguageVersion: 4.10

😉

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

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.