<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
What I really miss in QGIS server compared to UNM mapserver is the possibility to keep a certain space around the edge of the generated output free of labels (UMN Mapserver has had that already in V 5.? or even earlier). This is a must-have if we want to integrate mapcache because otherwise there will be broken labels and tiles will not fit to each other labelwise.<br>
</blockquote><div><br></div><div>I totally agree. As I said in an earlier reply, metatiling and buffering are a must to serve tiled caches.</div><div><br></div><div>giovanni</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
just my 2 ct<br>
<br>
Bernhard<br>
<br>
Am 15.11.2012 08:57, schrieb Andreas Neumann:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5">
Hi,<br>
<br>
For 90% of my projects performance is really good. For the remaining<br>
10%, rather complext projects, I would say it is good enough, but it<br>
could be "snappier".<br>
<br>
I am specifically talking about the "Leitungskataster" project, the<br>
project displaying all supply lines and waste-water lines, containing<br>
cadastral data, electricity, gaz, water, communication, waste-water and<br>
heating.<br>
<br>
These complex projects typically have:<br>
<br>
* a lot of layers (around 70 layers)<br>
* a lot of rules in the layer symbology<br>
* automatically placed labels along lines<br>
* dash patterns - almost all the lines are dashed<br>
* SVG symbols<br>
<br>
I will have to do my own homework. I will probably have to reduce the<br>
number of layers by using views.<br>
<br>
And to be honest, I haven't set up the same project on UMN mapserver to<br>
compare whether it is really faster.<br>
<br>
I don't know yet where the bottlenecks are (too many layers, too many<br>
rules, too many rules, too many labels?).<br>
<br>
Thanks,<br>
Andreas<br>
<br>
<br>
Am 14.11.2012 21:13, schrieb Marco Hugentobler:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi all<br>
<br>
Performance is a complex topic, it essentially depends what you are<br>
testing ( few complex polygons, many small polygons, type of raster,<br>
lots of labels, ...).<br>
I'm regularly profiling some of my important server projects (e.g. WMS<br>
of cadastral survey). One thing that takes up a lot of render time is<br>
the drawing of the labels (only the rendering, not the placement).<br>
I think this is because they are rendered using QPainterPath and not<br>
with QPainter->drawText (but it might be difficult to render the buffer<br>
using drawText).<br>
<br>
And don't forget that normally the transfer of the image over the<br>
internet takes more time than the WMS rendering itself. So don't forget<br>
to use jpg for rasters and the improved png8 for vectors. It can improve<br>
perceived performance by a factor of 3 or 4.<br>
<br>
Regards,<br>
Marco<br>
<br>
On 14.11.2012 19:57, Andreas Neumann wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Lets say that speed of QGIS Server is good enough for most of my<br>
projects. But it could be faster for more complex rendering and labeling.<br>
<br>
UMN feels faster than QGIS Server - but I don't have time for double<br>
configurations for desktop and web. Plus - it is so much easier to<br>
configure QGIS projects compared to editing mapfiles.<br>
<br>
<br>
<br>
"G. Allegri"<<a href="mailto:giohappy@gmail.com" target="_blank">giohappy@gmail.com</a>> schrieb:<br>
<br>
The one thing were UMN Mapserver is a much better is<br>
performance. This<br>
is where we should really catch up.<br>
<br>
<br>
I would put this to the higher position! I don't know where the<br>
effort should be put, because I suppose it's something deep in the<br>
rendering engine of QGis. Do you see bottlenecks at the server level?<br>
<br>
I would also add a point to the whishlist: Qgis Server Python API ;)<br>
<br>
giovanni<br>
<br>
2012/11/14 kimaidou<<a href="mailto:kimaidou@gmail.com" target="_blank">kimaidou@gmail.com</a><<u></u>mailto:<a href="mailto:kimaidou@gmail.com" target="_blank">kimaidou@gmail.com</a>>><br>
<br>
Hi<br>
<br>
2012/11/14 Vincent Picavet<<a href="mailto:vincent.ml@oslandia.com" target="_blank">vincent.ml@oslandia.<u></u>com</a><br>
<mailto:<a href="mailto:vincent.ml@oslandia.com" target="_blank">vincent.ml@oslandia.<u></u>com</a>>><br>
<br>
Hi,<br>
<br>
> * templates for HTML popups (already done this in<br>
Lizmap, but why not<br>
> having it in Qgis)<br>
You mean accessing the templates through QGIS server ?<br>
Because html popups<br>
already are in QGIS :)<br>
<br>
<br>
<br>
I mean through Qgis Server (in respect to this thread title ;)<br>
Just exposing methods for the server must do it, as Andreas<br>
proposed.<br>
<br>
We should have a look at PyWPS too, which could be an easy<br>
way to provide WPS<br>
services around QGIS API.<br>
<br>
<br>
<br>
Yes, pyWPS could help provide this feature, but we still need<br>
a way so that QGIS Server can use python plugins / processes,<br>
etc.. I remember discussion about this during last hackfests,<br>
but I do not know if someone gave it a try.<br>
<br>
Anyway, +10000 for focusing on performance first, which is the<br>
key "feature" for a Server.<br>
<br>
Michael<br>
<br>
<br>
Vincent<br>
<br>
><br>
> Good evening<br>
> Michael<br>
><br>
><br>
> 2012/11/14 G. Allegri<<a href="mailto:giohappy@gmail.com" target="_blank">giohappy@gmail.com</a><br>
<mailto:<a href="mailto:giohappy@gmail.com" target="_blank">giohappy@gmail.com</a>>><br>
><br>
> > > - integrated tiling<br>
> >><br>
> >> Why not integrating mapcache directly to mutualize<br>
effort on this part ?<br>
> >> Mapcache can be used standalone, and could read its<br>
parameters directly<br>
> >> from a<br>
> >> qgis configuration file. No need to reinvent the<br>
wheel here, or would<br>
> >> there be a<br>
> >> good reason to it ?<br>
> ><br>
> > I think that a tile generator from the QGis Desktop<br>
side would suffice.<br>
> > Any other TMS/WMS-T server could use the tile structure.<br>
> ><br>
> >> > - mask layers<br>
> >><br>
> >> That would be great to have in QGIS indeed. It would<br>
mean having for<br>
> >> each layer an attached mask layer, which is not<br>
displayed but only used<br>
> >> to define<br>
> >> hidden places.<br>
> >><br>
> >> > - symbol placement<br>
> >> > - label offsets<br>
> >><br>
> >> That's for qgis symbology, not directly a qgis server<br>
issue. Label<br>
> >> offset in<br>
> >> mapserver definitly looks cool !<br>
> ><br>
> > I agree Vincent.<br>
> ><br>
> >> Vincent<br>
> >> ______________________________<u></u>_________________<br>
> >> Qgis-developer mailing list<br>
> >> <a href="mailto:Qgis-developer@lists.osgeo.org" target="_blank">Qgis-developer@lists.osgeo.org</a><br>
<mailto:<a href="mailto:Qgis-developer@lists.osgeo.org" target="_blank">Qgis-developer@lists.<u></u>osgeo.org</a>><br>
> >> <a href="http://lists.osgeo.org/mailman/listinfo/qgis-developer" target="_blank">http://lists.osgeo.org/<u></u>mailman/listinfo/qgis-<u></u>developer</a><br>
> ><br>
> > ______________________________<u></u>_________________<br>
> > Qgis-developer mailing list<br>
> > <a href="mailto:Qgis-developer@lists.osgeo.org" target="_blank">Qgis-developer@lists.osgeo.org</a><br>
<mailto:<a href="mailto:Qgis-developer@lists.osgeo.org" target="_blank">Qgis-developer@lists.<u></u>osgeo.org</a>><br>
> > <a href="http://lists.osgeo.org/mailman/listinfo/qgis-developer" target="_blank">http://lists.osgeo.org/<u></u>mailman/listinfo/qgis-<u></u>developer</a><br>
______________________________<u></u>_________________<br>
Qgis-developer mailing list<br>
<a href="mailto:Qgis-developer@lists.osgeo.org" target="_blank">Qgis-developer@lists.osgeo.org</a><br>
<mailto:<a href="mailto:Qgis-developer@lists.osgeo.org" target="_blank">Qgis-developer@lists.<u></u>osgeo.org</a>><br>
<a href="http://lists.osgeo.org/mailman/listinfo/qgis-developer" target="_blank">http://lists.osgeo.org/<u></u>mailman/listinfo/qgis-<u></u>developer</a><br>
<br>
<br>
<br>
______________________________<u></u>_________________<br>
Qgis-developer mailing list<br>
<a href="mailto:Qgis-developer@lists.osgeo.org" target="_blank">Qgis-developer@lists.osgeo.org</a><br>
<mailto:<a href="mailto:Qgis-developer@lists.osgeo.org" target="_blank">Qgis-developer@lists.<u></u>osgeo.org</a>><br>
<a href="http://lists.osgeo.org/mailman/listinfo/qgis-developer" target="_blank">http://lists.osgeo.org/<u></u>mailman/listinfo/qgis-<u></u>developer</a><br>
<br>
<br>
<br>
------------------------------<u></u>------------------------------<u></u>------------<br>
<br>
Qgis-developer mailing list<br>
<a href="mailto:Qgis-developer@lists.osgeo.org" target="_blank">Qgis-developer@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/qgis-developer" target="_blank">http://lists.osgeo.org/<u></u>mailman/listinfo/qgis-<u></u>developer</a><br>
<br>
<br>
--<br>
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail<br>
gesendet.<br>
<br>
<br>
______________________________<u></u>_________________<br>
Qgis-developer mailing list<br>
<a href="mailto:Qgis-developer@lists.osgeo.org" target="_blank">Qgis-developer@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/qgis-developer" target="_blank">http://lists.osgeo.org/<u></u>mailman/listinfo/qgis-<u></u>developer</a><br>
</blockquote>
<br>
<br>
<br>
<br>
______________________________<u></u>_________________<br>
Qgis-developer mailing list<br>
<a href="mailto:Qgis-developer@lists.osgeo.org" target="_blank">Qgis-developer@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/qgis-developer" target="_blank">http://lists.osgeo.org/<u></u>mailman/listinfo/qgis-<u></u>developer</a><br>
<br>
</blockquote>
<br>
______________________________<u></u>_________________<br>
Qgis-developer mailing list<br>
<a href="mailto:Qgis-developer@lists.osgeo.org" target="_blank">Qgis-developer@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/qgis-developer" target="_blank">http://lists.osgeo.org/<u></u>mailman/listinfo/qgis-<u></u>developer</a><br>
<br>
<br></div></div>
__________ Information from ESET Mail Security, version of virus signature database 7693 (20121114) __________<br>
<br>
The message was checked by ESET Mail Security.<br>
<a href="http://www.eset.com" target="_blank">http://www.eset.com</a><br>
<br>
<br>
</blockquote>
<br>
-- <br>
Bernhard Ströbl<br>
Anwendungsbetreuer GIS<br>
<br>
Kommunale Immobilien Jena<br>
Am Anger 26<br>
07743 Jena<br>
<br>
Tel.: 03641 49- 5190<br>
E-Mail: <a href="mailto:bernhard.stroebl@jena.de" target="_blank">bernhard.stroebl@jena.de</a><br>
Internet: <a href="http://www.kij.de" target="_blank">www.kij.de</a><br>
<br>
<br>
Kommunale Immobilien Jena<br>
Eigenbetrieb der Stadt Jena<br>
Werkleiter: Dr. Götz Blankenburg<br>
<br>
<br>
__________ Information from ESET Mail Security, version of virus signature database 7693 (20121114) __________<br>
<br>
The message was checked by ESET Mail Security.<br>
<a href="http://www.eset.com" target="_blank">http://www.eset.com</a><div class="HOEnZb"><div class="h5"><br>
<br>
<br>
______________________________<u></u>_________________<br>
Qgis-developer mailing list<br>
<a href="mailto:Qgis-developer@lists.osgeo.org" target="_blank">Qgis-developer@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/qgis-developer" target="_blank">http://lists.osgeo.org/<u></u>mailman/listinfo/qgis-<u></u>developer</a><br>
</div></div></blockquote></div><br>