diff --git a/OGC-compliance-for-QGIS.md b/OGC-compliance-for-QGIS.md index 769e15f..bdd33cf 100644 --- a/OGC-compliance-for-QGIS.md +++ b/OGC-compliance-for-QGIS.md @@ -9,42 +9,45 @@ It is an essential tool that helps organizations better implement service interf So in two words, if a server and a client are both certified, it is highly likely that things are going to work smoothly between them. And this is why we love standards for interoperability. -# Status and plans for QGIS server +## Certification process -## QGIS server 3.0 status +The OGC certification must be renewed every year by running the online OGC certification tool against a reference QGIS server url. +The certification - for each version and each service - must be renewed every year. + +Due to the administrative burden, QGIS.org currently only will renew certification for LTR versions. + +A dedicated contact mail has been set up : `ogc at qgis dot org` forwarding mails to 3-4 persons in charge. + + +# Status and plans for QGIS server QGIS server has been fully rewritten for QGIS 3. A lot of efforts have been spent to make it cleaner, easier to maintain, easier to extend with plugins, python services, with better error logs, and faster. The best way to consolidate that and gain the trust in it was to test it every day with the OGC team Engine tools. In 2017, we built up an open source platform that embeds the OGC TeamEngine [1] testing tools, QGIS latest server builds, and a Geoserver reference implementation [2] QGIS.org supported a lot of efforts in progressively fixing platform issues with TeamEngine - which took some time - and then tackling all OGC failures. -In may 2018, an official certification process has been started with the OGC for WMS 1.3.0. - -A dedicated contact mail has been set up : `ogc at qgis dot org` +In may 2018, an official certification process has been successfull with the OGC for WMS 1.3.0. (see [3] ) [0] https://github.com/Oslandia/docker-qgis-ogc-cite [1] http://cite.opengeospatial.org/teamengine/ [2] http://test.qgis.org/ogc_cite/ +[3] http://www.opengeospatial.org/resource/products/details/?pid=1496 -## QGIS 3.2 plans +## QGIS 3.x plans -### WFS compliance +## Service compliance status and history -A grant application is proposed in order to start and hopefully reach the certification for WFS. - -**Implementation plans** - -1. Instantiate a new OGC Team engine Docker with WFS services. We are relying on OGC teamEngine REST API to call the test suite. This step can take some time because we encountered TeamEngine crashes, and we'll work with OGC to fix those issues upstream. -2. Deploy the platform so that it generates nightly reports. This step will give us a clear view of the failing tests and the current degree of compliance. -3. If we get enough time at this step, we'll try to tackle most of the issues and will try to reach the 100% compliance and certification. Some issues might need heavy re factor though, we'll keep that for later work if this occurs. +| QGIS server version | Service | Service version | Statuts | certification date | comment | +|--------------------- |--------- |----------------- |----------------- |-------------------- |--------------------------------------------------------------- | +| 3.0.2 | WMS | 1.3.0 | [Compliant](http://www.opengeospatial.org/resource/products/details/?pid=1496) | 2018-05-03 | First official certification. Reference implementation status | +| 3.4 | WMS | 1.3.0 | To be certified | | 2 | +| | WFS | | | | 3 | -**Risks and uncertainties: ** +## WFS compliance + +A grant application in 2018 allowed to set up a permanent WFS test platform and tackle the first main issues. -Hopefully, OGC platform lets us test several WFS versions. But there is no way to know without to do the real work. -Most unknown issues rely the TeamEngine platform, but we already know we made it for WMS. We are pretty sure we'll make it. -Another # Status and plans for QGIS Desktop client -# Status of know QGIS specific web clients \ No newline at end of file