OpenStreetMap displaying slow or not at all

[+RakeInTheCache 18]

Anyone else having a problem with the display of OpenStreetMap in the upper right hand corner of Waymark pages? Sometimes it displays very slowly and sometimes not at all. It wasn't always like this. Seems something may have happened.

 

I find it makes it very difficult to check the accuracy of waymark coordinates when approving waymarks.

[+MountainWoods 25]

I just had to review a bunch of waymarks using Google Earth as a secondary tool because the map was not showing up at all. I often check the map to make sure that the submitter didn't accidentally goof the coordinates (I've done that), but even more important for checking country churches to see if they're really out in the country.

 

I'm using Firefox. I used to use Chrome, but it has waaaay too many issues. After a half an hour of using Chrome, go to your Task Manager (or ps -ef on Linux) and look at how many Chrome processes are running. Which may explain why your Chrome window(s) are suddenly hung. Google products are garbage anymore. So I moved on to Firefox. (Yes, it has its own set of issues; but more manageable to me.)

[+fi67 143]

It's a nuisance. Big, but not a stopper.

 

For a while it did not work sometimes, then usually, recently always.

 

The map tiles not working are (supposed to be) delivered by a subdomain of geocaching.com. If it was Waymarking.com, I would have little hope, but TPTB need a working infrastructure for their core business, so there are maybe some resources to fix the problem. I do not geocache, are there any map problems on that site?

[+Tante.Hossi 10]

The main problem of this map issue is that there are two different domains. First domain name is 'Waymarking.com' delivering everything of the site with the only exception of the maptiles. They come from the second domain name 'geocaching.com'. And this is the problem. It is called Cross Origin or Cross Domain. Modern Webservers (Groundspeak uses IIS) by default prevent such cross origins. The Webserver must be configured to allow it.

[Manville Possum 284]

The main problem of this map issue is that there are two different domains. First domain name is 'Waymarking.com' delivering everything of the site with the only exception of the maptiles. They come from the second domain name 'geocaching.com'. And this is the problem. It is called Cross Origin or Cross Domain. Modern Webservers (Groundspeak uses IIS) by default prevent such cross origins. The Webserver must be configured to allow it.

 

Thanks for explaining. So is this something that is likely to be fixed?

 

The map seems to work when creating a new MW. I'm not very tech savy.

[+Tante.Hossi 10]

Actually the maps are working fine.

I don't know if something has been fixed.

[+MountainWoods 25]

Ditto. It seemed that the map only disappeared for one or two days, then it came back. Makes everything much easier. Thanks to whodunit.

[+RakeInTheCache 18]

Could it be that someone at Groundspeak is actually reading the forums?

[+ToRo61 1]

Actually the maps are working fine.

I don't know if something has been fixed.

 

yes, the usual situation on Waymarking.com ...

no one knows why it started to work

Edited August 31, 2016 by ToRo61

[+RakeInTheCache 18]

I'm still getting bad performance when zooming.

[+T0SHEA 176]

I'm still getting bad performance when zooming.

RakeInTheCache has it right, from this viewpoint. I can get the maps back to life by zooming in and out quickly, but they disappear again when zoomed in a step too far. Oh well...

 

Don't forget that if you're reviewing and need to check the map, the Google Maps link at the bottom of the WM page is always there to bail you out.

[+Tante.Hossi 10]

Yes the map is working - sometimes more and sometimes less.

The maptiles are very slow. Sometimes too slow to be shown.

So this is a different problem to the (maybe fixed) Cross Origin problem.

 

For every maptile which is not shown I get a 'HTTP 407 authenticationrequired' status code.

The other shown maptiles are very slow. They need about 1600-2700 ms. Much too much!

 

So it's time for an admin/developper to take a look at this bad behavior.

PLEASE!!

[+Benchmark Blasterz 65]

The maps are not showing AT ALL for us today This makes it VERY HARD to add new WMs. Thanks