Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't load WMS basemap #4057

Closed
danicarrion opened this issue Jun 15, 2015 · 6 comments
Closed

Can't load WMS basemap #4057

danicarrion opened this issue Jun 15, 2015 · 6 comments
Assignees
Milestone

Comments

@danicarrion
Copy link
Contributor

I can't add this WMS basemap to a visualization:

http://api.maps.vic.gov.au/geowebcacheWM/service/wms

I can select the layer, but no basemap is loaded after that. I can see the basemap without problems in http://mapviewer.org/

@jsanz
Copy link

jsanz commented Jul 23, 2015

I can't add also this other WMS server as a basemap

http://maps.six.nsw.gov.au/arcgis/services/public/NSW_Imagery/MapServer/WMSServer

This one is not even recognised so I can't select a layer but it works without problems in QGIS.

Worth to note that the first one reported comes from a GeoWebCache service and mine is an ArcGIS Server one so different implementations of the WMS standard.

cc. @viddo @javisantana

@viddo
Copy link
Contributor

viddo commented Aug 24, 2015

@jsanz that one works for me™, so perhaps is the circumstances you describe, I'm not familiar with that setup:
screen shot 2015-08-24 at 16 08 39

@viddo
Copy link
Contributor

viddo commented Aug 24, 2015

@danicarrion the URL provoks 503 errors on the WMS proxy, need to investigate further.

@jsanz
Copy link

jsanz commented Aug 25, 2015

@viddo thanks yeah, now it's working that Australia WMS, thanks for re-chekcing 🙏

@viddo
Copy link
Contributor

viddo commented Aug 27, 2015

@danicarrion so now it seems to work for the reported URL to:
screen shot 2015-08-27 at 12 53 06 so it seems like the service is not returning a correct layer URL.

The problem was that the mapproxy cached the first result (the internal IPs), so following requests were not going to work obviously. The solution was to remove the cached result and restart the service. While that solved this particular case it's possible that this happens again in the future, we'll continue the discussion in the reported issue @jsanz created

Re-open the issue if this still fails.

@danicarrion
Copy link
Contributor Author

thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants