Hi Andreas,<br><br>Thanks for your answer. <br><br><br><div class="gmail_quote">2011/11/14 Andreas Neumann <span dir="ltr"><<a href="mailto:a.neumann@carto.net">a.neumann@carto.net</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
Many of the issues you raise here were also identified before or at the recent developer meeting. See also <a href="http://www.qgis.org/wiki/QGISWebClientIdeas" target="_blank">http://www.qgis.org/wiki/<u></u>QGISWebClientIdeas</a><br>
<br>
</blockquote><div><br><br>I have read this page quite "live" during the hackfest (it was a rainy week-end down here in Montpellier). It has some very interesting things<br><br> </div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
The issue with the different scales are really annoying, so why dont we make the 96 dpi the default? Do you really think it is much slower? </blockquote><div><br><br>Much slower, no, but I know for sure that decreasing tile sizes in one of the first optimisation you do when you deliver map on the web. But I am not sure decreasing DPI Tto 72 will make a big change though...<br>
<br> </div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">BTW - we already get 96dpi images, only OL seems to calculate the scale with 72dpi. We even try to detect the dpi when loading the client. Not sure if this works properly ... Thanks anyway for the hint. I will test it.<br>
</blockquote><div><br><br>We spend half a day to understand why the layers did not have the correct behaviour regarding min and maxScale. After some deep thinking, it appeared it was relative to DPI . I can confirm for sure that using the OL option OpenLayers.DOTS_PER_INCH = 96 and asking tiles in 96 DPI works. No more problems (we tested it on a very complete and complex Qgis project)<br>
<br> </div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
An improved GetLegendGraphics with user configurable sizes is already requested and will be a paid development/improvement from Sourcepole.<br></blockquote><div><br><br>Great news.<br><br> </div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
GetCapabilities improvements: at the meeting we decided to use a web map context (similar to GetCapabilities) but more configurable to transport settings we want, e.g the initial layer visibility, etc.<br></blockquote><div>
<br><br>I think it is a good idea :)<br><br><br>Regards,<br>Michael<br></div></div>