<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">Hi QGIS Server devs,</div><div class=""><br class=""></div><div class="">I’m using QGIS server and find it quite convenient, since I can author map projects with powerful QGIS gui and get them published as OGC services right on-the-fly. I don’t think any other FOSS OGC servers out there can boast the same functionality. I’m not a QGIS Server committer, but I’d be happy to help testing new versions and providing feedback - like testing master builds and reporting bugs, regressions, etc.</div><div class=""><br class=""></div><div class="">One thought about the future improvements: most webmaps and GIS software utilise vector tiles now and Mapbox Vector Tiles (MVT), recently adopted by ESRI, really became a de-facto standard. But unfortunately QGIS Server lacks implementation of vector tile creation and serving.<br class="">While QGIS has bleeding-edge desktop functionality, QGIS Server sadly stays behind progress here. IMHO adopting vector tiles (reading and most importantly creation) should be one of top priorities for future versions.<br class="">I know QGIS depends on GDAL mostly in terms of I/O, so it really should be solved on both GDAL and QGIS levels. But as far as I know GDAL dev community doesn’t have any particular plans to implement MVT driver (or, perhaps, they do?:).</div><div class="">Some work is going on the postgis side (<a href="https://gist.github.com/bjornharrtell/7f4b6c030d4faa63f99b1ceb6f3edcef" class="">https://gist.github.com/bjornharrtell/7f4b6c030d4faa63f99b1ceb6f3edcef</a>).</div><div class=""><br class=""></div><div class="">Cheers,</div><div class="">Nick Lebedev</div><br class=""><div><blockquote type="cite" class=""><div class=""><div class="">Date: Fri, 23 Sep 2016 14:45:37 +0200<br class="">From: René-Luc Dhont <<a href="mailto:rldhont@gmail.com" class="">rldhont@gmail.com</a>><br class="">To: qgis-developer <<a href="mailto:qgis-developer@lists.osgeo.org" class="">qgis-developer@lists.osgeo.org</a>><br class="">Subject: [Qgis-developer] [QGIS Server] Maintain it and create a team<br class="">Message-ID: <<a href="mailto:25bba341-9db8-40eb-7bda-8918c76f72a7@gmail.com" class="">25bba341-9db8-40eb-7bda-8918c76f72a7@gmail.com</a>><br class="">Content-Type: text/plain; charset=utf-8; format=flowed<br class=""><br class="">Hi devs,<br class=""><br class="">The Qt4 and Python 2.7 is going away from QGIS master, following this PR:<br class="">Require python 3 and qt5 <a href="https://github.com/qgis/QGIS/pull/3510" class="">https://github.com/qgis/QGIS/pull/3510</a><br class=""><br class="">But a part of the project directly suffered of this: QGIS Server. As <br class="">explain on the Pull Request 'Require python 3 and qt5', all the QGIS <br class="">Server tests has been disabled. This means that QGIS Server is not <br class="">maintained with automatic tests for QGIS 3.<br class=""><br class="">So Mathias Khun has opened an issue about QGIS 3 API to remove QGIS <br class="">Server from QGIS master.<br class=""><a href="https://github.com/qgis/qgis3.0_api/issues/63" class="">https://github.com/qgis/qgis3.0_api/issues/63</a><br class="">The discussion is opened but I don't know if all the developpers are <br class="">aware of this.<br class=""><br class="">For our team, 3Liz (Michaël, David and I), the QGIS Server is a big part <br class="">of the QGIS project and it will really be a pitty if it disappears. A <br class="">part of the QGIS users are interesting in it because they can published <br class="">web services directly from their work. So QGIS Server is a reason for <br class="">them to use QGIS. Many users like the part of using QGIS desktop to <br class="">configure easily many options for publication, and use WMS, WFS, WCS and <br class="">event WPS with different clients (one of them is Lizmap).<br class="">We take much time (and about half of it without funds) to keep this <br class="">feature alive and up to date with QGIS improvements, and are willing to <br class="">continue down this path (we believe in it and have many good feedbacks <br class="">from users)<br class=""><br class="">We would like to raise interest around QGIS Server, and report here that <br class="">this part of QGIS is really used in production by companies and research <br class="">centers, and maintained by some devs, and not just a QGIS side project <br class="">"for fun".<br class=""><br class="">We just discussed with Alessandro Pasotti and we would like to create a <br class="">team to maintain and discuss about the evolution of QGIS Server. We <br class="">would like to use this opportunity to improve QGIS Server and make it <br class="">more maintainable and granular.<br class=""><br class="">Some questions to gather reactions :<br class="">* Who is interested in maintaining QGIS Server ?<br class="">* Who is interested in participating in QGIS Server (code, ideas, <br class="">review, tests) ?<br class="">* Please share any ideas to enhance (refactor) QGIS Server<br class=""><br class="">Regards,<br class="">René-Luc D'Hont<br class=""><br class=""><br class="">------------------------------<br class=""><br class="">Subject: Digest Footer<br class=""><br class="">_______________________________________________<br class="">Qgis-developer mailing list<br class="">Qgis-developer@lists.osgeo.org<br class="">List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer<br class="">Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer<br class=""><br class="">------------------------------<br class=""><br class="">End of Qgis-developer Digest, Vol 131, Issue 81<br class="">***********************************************<br class=""></div></div></blockquote></div><br class=""></body></html>