Bug report #8406
WMTS Connection is not working
|Category:||Web Services clients/WMS|
|Affected QGIS version:||1.8.0||Regression?:||No|
|Operating System:||Windows||Easy fix?:||No|
|Pull Request or Patch supplied:||No||Resolution:||worksforme|
|Crashes QGIS or corrupts data:||No||Copied to github as #:||17178|
I have not been able to get a WMTS server to work with either the stable version of QGIS 1.8.0 or the current development version of 1.9
This is the WMTS connection :
which is an OGC compliant WMTS server.
(the GetCapabilities request is at: http://nis.cubewerx.com/cubewerx/cubeserv?CONFIG=OIM_MB_-_Orthophoto-WMTS&SERVICE=WMTS&REQUEST=GetCapabilities )
this is part of our NIS pilot project and will be available for another 3 months.
I am able to get this WMTS server to work with OpenLayers though through a web page that I have created. This page is attached to this bug report.
Do you know how QGIS detects that this is a WMTS connection since we are using the WMS connection dialog? I am seeing error messages that keep saying that a WMS connection could not be established, is that because the error message is currently not specific to the type of connection (WMS or WMTS) or because it didn't try and make a WMTS connection?
#7 Updated by Bob Bruce over 7 years ago
Thanks everybody for your help with this.
Today I (finally) managed to get my QGIS master copy updated. I tried this connection with the additional strings &SERVICE=WMTS&Request=GetCapabilities and it worked. So I'm closing this bug report.
Tomorrow I will add a comment to the listserv message to let everyone know that they have to add those strings.
As an additional note: when I get the properties of the layer in QGIS and go to Metadata and go to server properties it shows the label WMS Version rather than WMTS Version.
#10 Updated by Jonathan Moules over 7 years ago
I'm not sure this should have been closed.
Consider it from a users perspective - They wouldn't expect to add SERVER and GetCapabilities. Myself I expect QGIS to either:
a) Figure it out automatically.
b) Have a separate button for WMTS.
It shouldn't silently fail as it does now. Documenting this limitation won't fix it - you'll still get lots of confused people and posts to the mailing list.
Especially as you don't require those parameters for WMS.