You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
OGC could provide a test-suite with public available OWS web services (WPS, WMS, ...) which can be used for OWS client tests (OWSLib, Birdy, Phoenix, ...):
services could be provides as (docker) containers.
could be hosted in the cloud.
should be reliable.
available for common protocols (WPS, WMS, WFS, WCS, ...) and versions (wps 1.0.0, wps 2.0.0).
Services/Dockerfiles are versioned (public Git repo).
To make the service response more predictable the service URL should also have the version number of the service/container version, something like this:
Not exactly what you propose @cehbrecht , but there is a standard test suite at OGC. I'm not super familiar with this, but we could quite easily get help from an expert to set this up. http://cite.opengeospatial.org/teamengine/
OGC could provide a test-suite with public available OWS web services (WPS, WMS, ...) which can be used for OWS client tests (OWSLib, Birdy, Phoenix, ...):
To make the service response more predictable the service URL should also have the version number of the service/container version, something like this:
http://ogc-testsuite.demo.org/wps/1.0.0/simple/v0.3.5
The text was updated successfully, but these errors were encountered: