dstenger
commented
5 years ago The example Capabilities document is no actual WMS server but just an example for this document. E.g. if you take a look at the DCP URLs it is obvious that those URLs are not valid but just an example.
In general, please be aware that the test suite requires certain test data (see [1]). So, not all public WMS 1.3 services can be tested with this test suite (just the data independent tests work then).
Yes, there are several services passing all tests of the test suite. Please take a look at the official reference implementation [2]. A complete list of all reference implementations can be found here [3].
Please be aware, if you use OGC TEAM Engine production [4] or beta [5], your service must be accessible via the web. Otherwise, you must setup TEAM Engine by yourself (can easily be done with Docker).
Services using HTTPS with server authentication are supported by the test suite. If you have any problems with HTTPS services, please create a new issue.
[1] https://opengeospatial.github.io/ets-wms13/index.html [2] http://cite.deegree.org/deegree-webservices-3.4.0/services/wms130?service=WMS&request=GetCapabilities [3] https://github.com/opengeospatial/cite/wiki/Reference-Implementations [4] http://cite.opengeospatial.org/teamengine/ [5] http://cite.opengeospatial.org/te2/
joel1451
the OpenGIS WMS implementation specification here http://portal.opengeospatial.org/files/?artifact_id=14416 on heading H.1 provides a sample XML capabilities URL which is valid. the URL is here: http://schemas.opengis.net/wms/1.3.0/capabilities_1_3_0.xml when you paste this url in the OGC testing validator online, the test shows that this fails with 6 errors. Some of the errors are that there are no images returned with errors, the getCapabilities request made without a version number fails, getCapabilities made for version 1.3.0 fails, request for version 100.0.0 fails, request for version 0.0.0 fails, etc. Moreover, although, a message states that the server can handle reserved characters in http get urls properly there is more errors for escaped chars, basic_elements and data-independent failure errors. I also used the online validator tool to test some getCapabilities URL for existing certified companies and their URLs also fail in the OGS testing site.
My concern is that I get the same 6 errors as the sample valid OGC XML in the link above but for my own URL. I would like to know if there is a bug with the online validator that it fails all the time no matter what URL is being used. Is there a sample valid getCapabilities XML URL that I can try to test the validator to see if it passes at least one URL?
Could I also get a validation if the online OGC validator is capable of handling https urls? I read the closed issues about this topic but didn't get a concrete yes or no answer, it looks some https work some don't, what are the requirements for the https to work?