<!DOCTYPE html>
<html data-lt-installed="true">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body style="padding-bottom: 1px;">
<p>Hi Günter,<br>
</p>
<div class="moz-cite-prefix">On 19/01/2024 12:59, G. Wagner,
Wagner-IT via Lizmap wrote:<br>
</div>
<blockquote type="cite"
cite="mid:027401da4ace$eab24140$c016c3c0$@wagner-it.de">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<meta name="Generator"
content="Microsoft Word 15 (filtered medium)">
<style>@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}@font-face
{font-family:"ITC Avant Garde Std Bk";
panose-1:2 11 5 2 2 2 2 2 2 4;}@font-face
{font-family:"ITC Avant Garde Std Md";
panose-1:2 11 6 2 2 2 2 2 2 4;}p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}span.E-MailFormatvorlage20
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
mso-ligatures:none;}div.WordSection1
{page:WordSection1;}ol
{margin-bottom:0cm;}ul
{margin-bottom:0cm;}</style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">Hi,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">Firstly,
many thanks to the entire Lizmap development team for the
very active further development of the client.</span></p>
</div>
</blockquote>
<p>Thanks a lot for your positive feedbacks. It's really appreciated
! Your message has been forwarded to the team ;-)<br>
<br>
In open source, we don't know too much our users, and sometimes,
we don't have too many feedbacks when it's working nicely :) (but
we have bug reports on GitHub... :) )<br>
<br>
We spent indeed a lot of times for releasing Lizmap Web Client 3.7
(polish, bugfix etc), we are glad we could make it after a "long
tunnel" of internal refactoring etc<br>
<br>
The work done on the plugin side was also unexpected and not
planned. It was just a "need" from our internal feedbacks.<br>
</p>
<p><br>
</p>
<blockquote type="cite"
cite="mid:027401da4ace$eab24140$c016c3c0$@wagner-it.de">
<div class="WordSection1">
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p>Even
if the background and the advantages are not visible at
first glance (is there any help for this?), it certainly
does no harm and does not cause any extra work.</span></p>
</div>
</blockquote>
<p>Maybe indeed for some checks, it's not obvious, but as you said,
"it does not harm" to make it.<br>
<br>
For now, we have "blocking" rules only if the issue is a "less
than 1 minute to fix", we do not block suddenly our users in their
workflow.<br>
<br>
But some checks, tagged "Important" (so not "blocking" the CFG
file generation), are sometimes leading to poor performance of the
project. Because it's not "quick" to fix, we decided to not block
users.<br>
</p>
<p> I'm thinking about the "Invalid field for QGIS server", this one
is an important check to fix, but it takes more than a minute...<br>
We are still not sure how we will enforce this rule in the
future... If you have ideas ? :)<br>
<br>
<br>
These checks are coming from our internal feedbacks on our Lizmap
Cloud hosting solution. We are monitoring a lot of customers
having various projects (various layers, use case, different
situations etc.). So these checks in the plugin are bottlenecks we
could identify on projects we are hosting.</p>
<p>Some bottlenecks are very "project specific" sometimes, or too
long to code for now :) So it won't land in the plugin for now.<br>
</p>
<p>Feel free to provide some ideas if needed, in the Lizmap plugin
repository.<br>
</p>
<blockquote type="cite"
cite="mid:027401da4ace$eab24140$c016c3c0$@wagner-it.de">
<div class="WordSection1">
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p>But
a question about the warning in the backend if the number of
layers is too high:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">Is
the absolute number of layers in the project a problem or
only the number of active layers that also need to be
rendered?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">In
my experience, it is only the active layers.</span></p>
</div>
</blockquote>
<p><br>
</p>
<p>Hum, for now, there isn't any check about the number of layer in
the plugin, right ?</p>
<p>The performance of a project about the number of layer is very
project specific.</p>
<p>Some projects with a dozen of layers can work with difficulties
(because covering a whole country, with a lot of features, with
very precise geometry at high-scale), and some projects with a lot
of layers can work nicely.</p>
<p>On our
hosting infrastructure, we are monitoring projects having more
than 100 layers (with another threshold at 200 layers as well).</p>
<p><br>
</p>
<p>When doing a GetMap request, QGIS server loads the whole project
by default (like all QGIS print layouts, with all logos/pictures
included in these layouts, all layers and relations between
layers...).</p>
<p>That's why some QGIS settings can be tuned to skip some parts
when loading a project (skip layouts, force readonly on layers...)<br>
</p>
<p>Back to your question, so I guess not only "active" layers, but
also others layers.</p>
<p>Of course, the number of "rendered" layers in a GetMap request is
important (like complexity in the symbology, the precision of the
geometry rendered etc).</p>
<p><br>
</p>
<p>I hope I understood your question ;-)<br>
</p>
<p><br>
</p>
<p>Regards,</p>
<p><br>
</p>
<p><br>
</p>
<p><br>
</p>
<blockquote type="cite"
cite="mid:027401da4ace$eab24140$c016c3c0$@wagner-it.de">
<div class="WordSection1">
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p></o:p></span></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Regards<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Günter Wagner<o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:8.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:8.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span
style="font-family:"ITC Avant Garde Std Bk",sans-serif;color:#E36C0A">WAGNER-</span></b><span
style="font-family:"ITC Avant Garde Std Md",sans-serif;color:#1F497D">IT</span><b><span
style="color:#1F497D"><o:p></o:p></span></b></p>
<p class="MsoNormal">Ingenieurbüro für Geoinformatik<b><span
style="font-size:12.0pt;color:#1F497D"><br>
</span></b>Carl-Orff-Weg 7<br>
79312 Emmendingen<br>
Tel.: 07641/9621668<br>
Fax: 07641/915599<br>
<a href="http://www.wagner-it.de/" moz-do-not-send="true">www.wagner-it.de</a><o:p></o:p></p>
</div>
</div>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
Lizmap mailing list
<a class="moz-txt-link-abbreviated moz-txt-link-freetext"
href="mailto:Lizmap@lists.osgeo.org">Lizmap@lists.osgeo.org</a>
<a class="moz-txt-link-freetext"
href="https://lists.osgeo.org/mailman/listinfo/lizmap">https://lists.osgeo.org/mailman/listinfo/lizmap</a>
</pre>
</blockquote>
<div class="moz-signature">-- <br>
<p> <span style="font-weight:bold;color:#9ACD32;">Etienne
Trimaille</span> <br>
Géomaticien <br>
<a href="http://www.3liz.com"
style="text-decoration: none; color: #9ACD32;">www.3liz.com</a>
<br>
<span style="font-size:0.8em;"> <br>
<b>Tel.</b> 06 12 93 11 39 <br>
<b>Bureau</b> <br>
31, rue de l'Argenterie <br>
34000 Montpellier <br>
<b>Siège social</b> <br>
73, allée Kleber <br>
Boulevard de Strasbourg <br>
34000 Montpellier </span> </p>
<p><br>
</p>
</div>
<lt-container></lt-container>
<div id="grammalecte_menu_main_button_shadow_host"
style="width: 0px; height: 0px;"></div>
</body>
</html>