From afc80a08ceb3a970df233cb288a955500e56027b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?R=C3=A9gis=20Haubourg?= Date: Sun, 13 May 2018 18:25:40 +0200 Subject: [PATCH] Add OGC compliance page --- OGC-compliance-for-QGIS.md | 50 ++++++++++++++++++++++++++++++++++++++ 1 file changed, 50 insertions(+) create mode 100644 OGC-compliance-for-QGIS.md diff --git a/OGC-compliance-for-QGIS.md b/OGC-compliance-for-QGIS.md new file mode 100644 index 0000000..769e15f --- /dev/null +++ b/OGC-compliance-for-QGIS.md @@ -0,0 +1,50 @@ +# What is OGC compliance ? + +The OGC (Open Geospatial Consortium) is an international not for profit organization committed to making quality open standards for the global geospatial community. These standards are made through a consensus process and are freely available for anyone to use to improve sharing of the world's geospatial data. + +http://www.opengeospatial.org/ + +OGC offers an OGC validator here http://cite.opengeospatial.org/teamengine/. +It is an essential tool that helps organizations better implement service interfaces, encodings and clients that adhere to OGC standards. Passing the test and getting OGC certified helps organizations distinguishing their product in the market place. + +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 + +## QGIS server 3.0 status + +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` + +[0] https://github.com/Oslandia/docker-qgis-ogc-cite +[1] http://cite.opengeospatial.org/teamengine/ +[2] http://test.qgis.org/ogc_cite/ + +## QGIS 3.2 plans + +### WFS compliance + +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. + + +**Risks and uncertainties: ** + +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