<div dir="ltr">Hi again, <div><br></div><div>As discussed in july, we worked on fixing all issues regarding OGC compliancy with WMS 1.3.0 in QGIS server 3. </div><div><br></div><div>Paul Blottiere did great and we reach now a <b>100% compliancy</b> on all testing levels (basic, queryable, elevation and recommended ) ! </div><div><br></div><div>Here is the proof :)<a href="http://test.qgis.org/ogc_cite/latest_wms_1_3_0.html"> http://test.qgis.org/ogc_cite/latest_wms_1_3_0.html</a></div><div><br></div><div><img src="cid:ii_15fc57e8498be5c8" alt="Images intégrées 1" width="413" height="392"><br></div><div><br></div><div>Here is the PR log:</div><div><br></div><div>- Fix OGC test on legendurl styles : <a href="https://github.com/qgis/QGIS/pull/5044">#5044</a></div><div>- Fixes OGC test on getmap:each-format mode for 1bit/8bit/16bit <a href="https://github.com/qgis/QGIS/pull/5084">#5084</a></div><div>- Fix OGC test getcapabilities:validate-using-schemaLocation <a href="https://github.com/qgis/QGIS/pull/5145">#5145</a></div><div>- Fix OGC test getfeatureinfo:invalid-info_format <a href="https://github.com/qgis/QGIS/pull/5150">#5150</a></div><div>- Fix OGC test getfeatureinfo:invalid-query_layers : <a href="https://github.com/qgis/QGIS/pull/5157">#5157</a></div><div>- Fix OGC test getfeatureinfo:each-queryable-layer <a href="https://github.com/qgis/QGIS/pull/5303">#5303</a></div><div>- Fix OGC test getmap bbox <a href="https://github.com/qgis/QGIS/pull/5360">#5360</a></div><div>- Fix OGC test recommendations <a href="https://github.com/qgis/QGIS/pull/5566">#5566</a></div><div><br></div><div><br></div><div>So, now we have a continuous integration in place, what would be nice to do in the <b>future</b> is:</div><div><br></div><div>- <b>Integrate into QGIS travisCI our current gitlab pipeline</b> that produces the OGC compliancy reports. The poor Travis probably has a lot of things on his shoulders by now, but that would be very nice to run those tests on each build concerning the server. </div><div><br></div><div>- <b>Start working on other services compliancy.</b> I bet we should start by WFS and WCS. </div><div><br></div><div>- <b>Get certified by the OGC and make it clearly visible on our website and documentation !</b> </div><div>See <a href="http://www.opengeospatial.org/compliance/getCertified">http://www.opengeospatial.org/compliance/getCertified</a></div><div>as part of the OSGEO, I suppose we probably are considered as OGC members and we probably will need to pay annual fees of 80 $. </div><div>If we agree on that, I can contact the OGC to have a clearer idea of those costs. </div><div>Anita, do you know what would be the status of QGIS project as a OGC member through OGC membership?</div><div><br></div><div><br></div><div>Many thanks to all of the contributors! (again)</div><div><br></div><div>Best regards, </div><div><br></div><div>Régis Haubourg and the Oslandia team</div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">2017-07-10 15:17 GMT+02:00 Régis Haubourg <span dir="ltr"><<a href="mailto:regis.haubourg@gmail.com" target="_blank">regis.haubourg@gmail.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi all, <div><br></div><div>After getting in sync with 3liz, here is a proposal of task :</div><div><br></div><div>C2C: 1 K€ for making automatic reports with the performance benchmark platform</div><div><br></div><div>3Liz: 6 K€ for GetPrint refactor, and some new feature (WFS 1.1.0 and some caching improvements)</div><div><br></div><div>OSLANDIA : 6 K€ for OGC unconformity checks and fixes</div><div><br></div><div>Yves, can you please react upon, that if you have plans to work on png encoder improvements? </div><div><br></div><div>Cheers</div><span class="HOEnZb"><font color="#888888"><div>Régis</div><div> </div></font></span></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">2017-07-07 14:02 GMT+02:00 Yves Jacolin <span dir="ltr"><<a href="mailto:yjacolin@free.fr" target="_blank">yjacolin@free.fr</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Good point, Emmanuel talked me about this. I need to discuss of this with my<br>
collegue first.<br>
<span class="m_2934375795123958788HOEnZb"><font color="#888888"><br>
Y.<br>
</font></span><div class="m_2934375795123958788HOEnZb"><div class="m_2934375795123958788h5">On vendredi 7 juillet 2017 13:02:20 CEST Andreas Neumann wrote:<br>
> Hi Yves,<br>
><br>
> What about the idea to speed up PNG encoding? I remember that the C2C devs<br>
> found out, that the PNG encoder from qt isn't very efficient and a lot of<br>
> time is spent by QGIS server on this PNG encoding. An alternative PNG<br>
> encoder could be more efficient. Could we invest some ressources in that?<br>
> It wouldn't be as urgent as the refactoring, but performance improvements<br>
> are always welcome.<br>
> Or is the PNG encoder in qt5 now more efficient than the one in qt4?<br>
><br>
> Andreas<br>
><br>
> On 7 July 2017 at 10:58, Yves Jacolin <<a href="mailto:yjacolin@free.fr" target="_blank">yjacolin@free.fr</a>> wrote:<br>
> > Hello Régis,<br>
> ><br>
> > On vendredi 7 juillet 2017 10:47:40 CEST Régis Haubourg wrote:<br>
> > > @Yves, please raise the hand if you are willing to take some funds on<br>
> > > the<br>
> > > speed benchmark platform, this would also be very welcome by dev's and<br>
> > > customers.<br>
> ><br>
> > I was wondering what Camptocamp can do for this as I had confirmation that<br>
> > we<br>
> > have some resource to work on this part.<br>
> ><br>
> > About the speed benchmark plateform we can make it automatic (mainly some<br>
> > cleanup, create automatic reporting and improving QGIS automatic build<br>
> > with<br>
> > docker). For these task we won't need more than 1 k€ though.<br>
> ><br>
> > Finally we can also host this in one of our public server but the deploy<br>
> > of<br>
> > the project should be easy if you need to test somewhere else.<br>
> ><br>
> > Y.<br>
<br>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div>