<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Hi<div class=""><br class=""></div><div class="">From me too a huge thank you to everyone involved!</div><div class=""><br class=""></div><div class="">Regards</div><div class=""><br class=""></div><div class="">Tim<br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On 19 Nov 2017, at 22:00, Giovanni Manghi <<a href="mailto:giovanni.manghi@gmail.com" class="">giovanni.manghi@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div class=""><div class="">congrats! and many thanks for your work!<br class=""><br class=""></div>cheers<br class=""><br class=""></div>-- G --<br class=""><br class=""><br class=""><br class=""></div><div class="gmail_extra"><br class=""><div class="gmail_quote">On Thu, Nov 16, 2017 at 3:59 PM, Régis Haubourg <span dir="ltr" class=""><<a href="mailto:regis.haubourg@gmail.com" target="_blank" class="">regis.haubourg@gmail.com</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr" class="">Hi again, <div class=""><br class=""></div><div class="">As discussed in july, we worked on fixing all issues regarding OGC compliancy with WMS 1.3.0 in QGIS server 3. </div><div class=""><br class=""></div><div class="">Paul Blottiere did great and we reach now a <b class="">100% compliancy</b> on all testing levels (basic, queryable, elevation and recommended ) ! </div><div class=""><br class=""></div><div class="">Here is the proof :)<a href="http://test.qgis.org/ogc_cite/latest_wms_1_3_0.html" target="_blank" class=""> http://test.qgis.org/ogc_<wbr class="">cite/latest_wms_1_3_0.html</a></div><div class=""><br class=""></div><div class=""><span id="cid:ii_15fc57e8498be5c8"><image.png></span><br class=""></div><div class=""><br class=""></div><div class="">Here is the PR log:</div><div class=""><br class=""></div><div class="">- Fix OGC test on legendurl styles : <a href="https://github.com/qgis/QGIS/pull/5044" target="_blank" class="">#5044</a></div><div class="">- Fixes OGC test on getmap:each-format mode for 1bit/8bit/16bit <a href="https://github.com/qgis/QGIS/pull/5084" target="_blank" class="">#5084</a></div><div class="">- Fix OGC test getcapabilities:validate-<wbr class="">using-schemaLocation <a href="https://github.com/qgis/QGIS/pull/5145" target="_blank" class="">#5145</a></div><div class="">- Fix OGC test getfeatureinfo:invalid-info_<wbr class="">format <a href="https://github.com/qgis/QGIS/pull/5150" target="_blank" class="">#5150</a></div><div class="">- Fix OGC test getfeatureinfo:invalid-query_<wbr class="">layers : <a href="https://github.com/qgis/QGIS/pull/5157" target="_blank" class="">#5157</a></div><div class="">- Fix OGC test getfeatureinfo:each-queryable-<wbr class="">layer <a href="https://github.com/qgis/QGIS/pull/5303" target="_blank" class="">#5303</a></div><div class="">- Fix OGC test getmap bbox <a href="https://github.com/qgis/QGIS/pull/5360" target="_blank" class="">#5360</a></div><div class="">- Fix OGC test recommendations <a href="https://github.com/qgis/QGIS/pull/5566" target="_blank" class="">#5566</a></div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">So, now we have a continuous integration in place, what would be nice to do in the <b class="">future</b> is:</div><div class=""><br class=""></div><div class="">- <b class="">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 class=""><br class=""></div><div class="">- <b class="">Start working on other services compliancy.</b> I bet we should start by WFS and WCS. </div><div class=""><br class=""></div><div class="">- <b class="">Get certified by the OGC and make it clearly visible on our website and documentation !</b> </div><div class="">See <a href="http://www.opengeospatial.org/compliance/getCertified" target="_blank" class="">http://www.opengeospatial.org/<wbr class="">compliance/getCertified</a></div><div class="">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 class="">If we agree on that, I can contact the OGC to have a clearer idea of those costs. </div><div class="">Anita, do you know what would be the status of QGIS project as a OGC member through OGC membership?</div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">Many thanks to all of the contributors! (again)</div><div class=""><br class=""></div><div class="">Best regards, </div><div class=""><br class=""></div><div class="">Régis Haubourg and the Oslandia team</div><div class=""><br class=""></div></div><div class="gmail_extra"><br class=""><div class="gmail_quote">2017-07-10 15:17 GMT+02:00 Régis Haubourg <span dir="ltr" class=""><<a href="mailto:regis.haubourg@gmail.com" target="_blank" class="">regis.haubourg@gmail.com</a>></span>:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr" class="">Hi all, <div class=""><br class=""></div><div class="">After getting in sync with 3liz, here is a proposal of task :</div><div class=""><br class=""></div><div class="">C2C: 1 K€ for making automatic reports with the performance benchmark platform</div><div class=""><br class=""></div><div class="">3Liz: 6 K€ for GetPrint refactor, and some new feature (WFS 1.1.0 and some caching improvements)</div><div class=""><br class=""></div><div class="">OSLANDIA : 6 K€ for OGC unconformity checks and fixes</div><div class=""><br class=""></div><div class="">Yves, can you please react upon, that if you have plans to work on png encoder improvements? </div><div class=""><br class=""></div><div class="">Cheers</div><span class="m_7688800563387320557HOEnZb"><font color="#888888" class=""><div class="">Régis</div><div class=""> </div></font></span></div><div class="m_7688800563387320557HOEnZb"><div class="m_7688800563387320557h5"><div class="gmail_extra"><br class=""><div class="gmail_quote">2017-07-07 14:02 GMT+02:00 Yves Jacolin <span dir="ltr" class=""><<a href="mailto:yjacolin@free.fr" target="_blank" class="">yjacolin@free.fr</a>></span>:<br class=""><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 class="">
collegue first.<br class="">
<span class="m_7688800563387320557m_2934375795123958788HOEnZb"><font color="#888888" class=""><br class="">
Y.<br class="">
</font></span><div class="m_7688800563387320557m_2934375795123958788HOEnZb"><div class="m_7688800563387320557m_2934375795123958788h5">On vendredi 7 juillet 2017 13:02:20 CEST Andreas Neumann wrote:<br class="">
> Hi Yves,<br class="">
><br class="">
> What about the idea to speed up PNG encoding? I remember that the C2C devs<br class="">
> found out, that the PNG encoder from qt isn't very efficient and a lot of<br class="">
> time is spent by QGIS server on this PNG encoding. An alternative PNG<br class="">
> encoder could be more efficient. Could we invest some ressources in that?<br class="">
> It wouldn't be as urgent as the refactoring, but performance improvements<br class="">
> are always welcome.<br class="">
> Or is the PNG encoder in qt5 now more efficient than the one in qt4?<br class="">
><br class="">
> Andreas<br class="">
><br class="">
> On 7 July 2017 at 10:58, Yves Jacolin <<a href="mailto:yjacolin@free.fr" target="_blank" class="">yjacolin@free.fr</a>> wrote:<br class="">
> > Hello Régis,<br class="">
> ><br class="">
> > On vendredi 7 juillet 2017 10:47:40 CEST Régis Haubourg wrote:<br class="">
> > > @Yves, please raise the hand if you are willing to take some funds on<br class="">
> > > the<br class="">
> > > speed benchmark platform, this would also be very welcome by dev's and<br class="">
> > > customers.<br class="">
> ><br class="">
> > I was wondering what Camptocamp can do for this as I had confirmation that<br class="">
> > we<br class="">
> > have some resource to work on this part.<br class="">
> ><br class="">
> > About the speed benchmark plateform we can make it automatic (mainly some<br class="">
> > cleanup, create automatic reporting and improving QGIS automatic build<br class="">
> > with<br class="">
> > docker). For these task we won't need more than 1 k€ though.<br class="">
> ><br class="">
> > Finally we can also host this in one of our public server but the deploy<br class="">
> > of<br class="">
> > the project should be easy if you need to test somewhere else.<br class="">
> ><br class="">
> > Y.<br class="">
<br class="">
</div></div></blockquote></div><br class=""></div>
</div></div></blockquote></div><br class=""></div>
<br class="">______________________________<wbr class="">_________________<br class="">
Qgis-psc mailing list<br class="">
<a href="mailto:Qgis-psc@lists.osgeo.org" class="">Qgis-psc@lists.osgeo.org</a><br class="">
<a href="https://lists.osgeo.org/mailman/listinfo/qgis-psc" rel="noreferrer" target="_blank" class="">https://lists.osgeo.org/<wbr class="">mailman/listinfo/qgis-psc</a><br class=""></blockquote></div><br class=""></div>
_______________________________________________<br class="">Qgis-psc mailing list<br class=""><a href="mailto:Qgis-psc@lists.osgeo.org" class="">Qgis-psc@lists.osgeo.org</a><br class="">https://lists.osgeo.org/mailman/listinfo/qgis-psc</div></blockquote></div><br class=""><div class="">
<span style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 18px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;"> </span><span><img apple-inline="yes" id="9DC6A808-61D2-467C-8987-025A89464835" src="cid:B67F6A36-B856-4FD5-91BC-5BDE8990D373" class=""></span><div style="color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: 12px; font-variant-ligatures: normal; font-variant-position: normal; font-variant-numeric: normal; font-variant-alternates: normal; font-variant-east-asian: normal; line-height: normal; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="font-weight: normal;" class=""><br class="Apple-interchange-newline"><br class="Apple-interchange-newline"><br class="Apple-interchange-newline">---</div><div style="font-weight: normal;" class=""><br class=""></div><div class=""><b class="">Tim Sutton</b></div><div style="font-weight: normal;" class="">QGIS Project Steering Committee Chair</div><div style="font-weight: normal;" class=""><a href="mailto:tim@qgis.org" class="">tim@qgis.org</a></div><div style="font-weight: normal;" class=""><br class=""></div></div><br class="Apple-interchange-newline" style="color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: 12px; font-variant-ligatures: normal; font-variant-position: normal; font-variant-numeric: normal; font-variant-alternates: normal; font-variant-east-asian: normal; line-height: normal;"><br class="Apple-interchange-newline" style="color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: 12px; font-variant-ligatures: normal; font-variant-position: normal; font-variant-numeric: normal; font-variant-alternates: normal; font-variant-east-asian: normal;">
</div>
<br class=""></div></body></html>