<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Hi Régis,<br>
</p>
My answers in the body of your email<br>
<br>
<div class="moz-cite-prefix">Le 08/02/2018 à 11:25, Régis Haubourg a
écrit :<br>
</div>
<blockquote type="cite"
cite="mid:CABgOYCcUXY7sqFA9kSJHA90eSj1kXrHu10BBmEu9wOFi1AE6Vw@mail.gmail.com">
<div dir="ltr">
<div>
<div>
<div>
<div>
<div>
<div>
<div>Hi all, <br>
<br>
</div>
As you know, QGIS server has been fully refactored
for QGIS 3. <br>
<br>
</div>
Now some big enterprises are starting to rely on it in
production environment and would like to consolidate
again QGIS server. <br>
<br>
</div>
I have some informations and questions :<br>
<br>
<br>
</div>
# OGC certification<br>
<br>
</div>
I got in touch with the OGC certification team, in the aim
of getting official certification, since we pass all WMS
1.3.0 tests. <br>
If we seek a reference implementation status on behalf of
OSGEO and QGIS.org, there should be no fees, that's great
news. <br>
</div>
The process must be renewed every year. <br>
</div>
<div>We started the online testing process here: <a
href="http://cite.opengeospatial.org/teamengine"
moz-do-not-send="true">http://cite.opengeospatial.org/teamengine</a>.
It's failing currently, probably because of IP redirections we
need to fix in our reference server (the one used by the
continuous integration system)<br>
</div>
<div><br>
</div>
<div>We are asked to start evaluating WFS conformity too, but
that should be a bit painful since there is no API in
TeamEngine to make continuous integration, and online platform
is not responding. So I'm not confident we'll have quick
results here. <br>
<br>
</div>
<div>If everything goes well, I think QGIS can be certified
soon! I think this will be very interesting to advertise in
the doc and website. <br>
<br>
</div>
<div>The OGC team seems really happy to see QGIS getting in the
certification loop, and suggest we also try to certify QGIS as
a client. If anyone has worked in that area, that would be
nice to join efforts. <br>
</div>
<div><br>
</div>
<div><br>
# Performance <br>
<br>
</div>
<div> * We are still interested in having performance measure
reference and ideally have performance driven development with
a continuous integration system. Yves, is there anything new
on your side? <br>
</div>
</div>
</blockquote>
<br>
I have made a first analyse and I will send an email to the
mailing-list.<br>
<br>
<blockquote type="cite"
cite="mid:CABgOYCcUXY7sqFA9kSJHA90eSj1kXrHu10BBmEu9wOFi1AE6Vw@mail.gmail.com">
<div dir="ltr">
<div><br>
</div>
<div> * One blocker for WFS was the performance of spatial
filter, in 2.x, they were not forwarded to the database when
possible, and implied reading the whole layer in memory before
doing the spatial query on the QGIS side. Anyone knows if it's
still the case? <br>
<br>
</div>
</div>
</blockquote>
<br>
No changes here. You just have to specify a QGIS2.ini or QGIS3.ini
to speficy this.<br>
<br>
<blockquote type="cite"
cite="mid:CABgOYCcUXY7sqFA9kSJHA90eSj1kXrHu10BBmEu9wOFi1AE6Vw@mail.gmail.com">
<div dir="ltr">
<div><br>
<br>
</div>
<div>all the best<br>
</div>
<div>Régis<br>
</div>
<div><br>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
QGIS-Developer mailing list
<a class="moz-txt-link-abbreviated" href="mailto:QGIS-Developer@lists.osgeo.org">QGIS-Developer@lists.osgeo.org</a>
List info: <a class="moz-txt-link-freetext" href="https://lists.osgeo.org/mailman/listinfo/qgis-developer">https://lists.osgeo.org/mailman/listinfo/qgis-developer</a>
Unsubscribe: <a class="moz-txt-link-freetext" href="https://lists.osgeo.org/mailman/listinfo/qgis-developer">https://lists.osgeo.org/mailman/listinfo/qgis-developer</a></pre>
</blockquote>
<br>
</body>
</html>