K Trackers

As a update to my previous post, I now have the same problem when I used my map link as previous mentioned. It would appear this problem is persistent (I've had this problem for years) and cuts across all maps and methods to get to the map. It is time for Groundspeak to address this issue. Thanks.

I just wanted to chime in that I have the same problem and have a little more information that may be helpful. In my case, the error seems to crop up when going to the map from the cache description via the "View Larger Map" link on the cache description page. I've had the problem on both the Google and Leaflet maps. I tried multiple map selections on the Leaflet maps as well. The problem occurs as soon as the map is open using Windows 10 and IE 11.545 I have a link on my desktop to the geocaching map that starts at my home location. I built this link using "Map this Location" after using the "near your home location" search function on my profile page. This method of getting to the map seems unaffected. However, this is cumbersome technique when try to access the map in areas far from Home. I noted FB_Flupo's suggested work around via the PQ panel. However, this work around is not effective when trying to log caches based upon a route you already took...in which case you need to see a map. This is my current predicament, trying to backlog caches from a hike I took. V/R, K Trackers