<div dir="ltr"><div><div><div><div><div><div><div><div>Hi,<br></div>thx I now start to understand better the question.<br><br>Infact I'm using spatialite db. A 4.1.1 db spatialite.<br></div>The spatialite db has an internal statistics table to perform a very fast resolution of the bboxes of single datasets.<br>
<br></div>I always update it using the command:<br><br>select UpdateLayerStatistics();<br><br></div>But the problem is if the client really use that table.<br><br>Infact I guess more probably the qgis-server don't ask to spatialite the box from this table, but instead do a more usual <br>
</div></div>sql to retrieve is.<br><br></div>Hi Sandro,<br>do you know the right query to retrieve the bbox from the statistics table of spatialite 4.1.1 ?<br><br>I guess suspect that qgis (because it like) to be more compatible with all the oldest (arcaic) version of spatialite, simply avoid to use this table.<br>
:)<br><br>Many thx.<br><br><br></div>Andrea.<br><br></div><div class="gmail_extra"><br><br><div class="gmail_quote">2014-02-14 10:34 GMT+01:00 Marco Hugentobler <span dir="ltr"><<a href="mailto:marco.hugentobler@sourcepole.ch" target="_blank">marco.hugentobler@sourcepole.ch</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<div>Hi Andrea, Giovanni<br>
<br>
QGIS Server doesn't calculate the bbox itself, but it queries the
extent from the layers. So it can be that certain providers
calculate the bbox (of course only if the layer / capabilities
document is not cached).<br>
<br>
For a faster startup, having a persistent cache as Giovanni
suggested might help.<br>
<br>
Regards,<br>
Marco<div><div class="h5"><br>
<br>
On 14.02.2014 10:18, G. Allegri wrote:<br>
</div></div></div><div><div class="h5">
<blockquote type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div dir="ltr">
<div>
<div>
<div><br>
</div>
<div>I don't understand why the qgis-server eed to
calculate always the bbox.<br>
In the server project windows, <br>
qgis ask for the published bbox.<br>
</div>
<div>Why it don't use it as bbox rather than
calculate it on every request ?<br>
</div>
</div>
</div>
</div>
</blockquote>
<div><br>
</div>
<div>Marco, correct me if I'm wrong.</div>
<div>QGIS Server doesn't calculate the BBOX, it parses the
layers extents from the .qgs project and then combine them
to obtain the entire BBOX.</div>
<div>The only operation it does is reprojecting the extents
to WGS84 to create the EX_GeographicBoundingBox element.</div>
<div><br>
</div>
<div>Anyway, in case the project advertises and extent, the
combined extent won't be calculated, so in your case this
phase shouldn't be the bottleneck...</div>
<div><br>
</div>
<div>giovanni</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div> </div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div dir="ltr">
<div>
<div>
<div>
<br>
</div>
<div>The FastCGI don't help really.<br>
In a publishing environment every few hour the
instances are restated to removed zombi process.<br>
This mean that every few hours the FastCGI are
emptied and reloaded.<br>
A fastcgi environment mean to load 20 instances of
QGIS-server and every of them do them own
elaboration .<br>
As the bbox calculation for every layer.<br>
<br>
GASP.<br>
The start could ask about one hours and more.<br>
</div>
<br>
</div>
Also another problem with the fastcig is that when <br>
</div>
<div>I change something on a project I need to restart
to Web instances to dismiss the actual project and
reload the new.<br>
<br>
</div>
<div>So every change in a qgis project need a restart of
all proccess (20 and so on in a fastcgi enviroment)
every with a slow bbox calculation phase.<br>
<br>
</div>
<div>mmhh...<br>
<br>
</div>
<div>:/<br>
</div>
<div><br>
</div>
</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">2014-02-14 9:13 GMT+01:00 G.
Allegri <span dir="ltr"><<a href="mailto:giohappy@gmail.com" target="_blank">giohappy@gmail.com</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div>
<div>
<div dir="ltr"><br>
<div class="gmail_extra">
<br>
<br>
<div class="gmail_quote">2014-02-14 Marco
Hugentobler <span dir="ltr"><<a href="mailto:marco.hugentobler@sourcepole.ch" target="_blank">marco.hugentobler@sourcepole.ch</a>></span>:
<div>
<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<div>Hi Andrea
<div><br>
<br>
>I suspect that QS try always
to recalc the box of every
layer.<br>
<br>
</div>
QGIS server caches layers (up to
100, but that can be enhanced
using the environment variable
MAX_CACHE_LAYERS). Furthermore,
the GetCapabilities documents are
cached (so no recalculation if
using FastCGI).
<div><br>
</div>
</div>
</div>
</blockquote>
<div><br>
</div>
</div>
<div>Thanks Marco, you confirmed what I
told Andrea.</div>
<div>It would be a good enhancement if
caching could be done in a persitent
manner (out of memory). We could
consider, in the future, to use memcache
or something similar.</div>
<div><br>
</div>
<div>giovanni</div>
</div>
</div>
</div>
<br>
</div>
</div>
<div>_______________________________________________<br>
Qgis-user mailing list<br>
<a href="mailto:Qgis-user@lists.osgeo.org" target="_blank">Qgis-user@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/qgis-user" target="_blank">http://lists.osgeo.org/mailman/listinfo/qgis-user</a><br>
</div>
</blockquote>
</div>
<div><br>
<br clear="all">
<br>
-- <br>
-----------------<br>
Andrea Peri<br>
. . . . . . . . . <br>
qwerty àèìòù<br>
-----------------<br>
</div>
</div>
</blockquote>
</div>
<br>
<br clear="all">
<div><br>
</div>
-- <br>
<div dir="ltr">Giovanni Allegri<br>
<a href="http://about.me/giovanniallegri" target="_blank">http://about.me/giovanniallegri</a>
<div>Twitter: <a href="https://twitter.com/_giohappy_" target="_blank">https://twitter.com/_giohappy_</a></div>
<div>blog: <a href="http://blog.spaziogis.it" target="_blank">http://blog.spaziogis.it</a><br>
GEO+ geomatica in Italia <a href="http://bit.ly/GEOplus" target="_blank">http://bit.ly/GEOplus</a></div>
</div>
</div>
</div>
</blockquote>
<br>
<br>
</div></div><div class=""><pre cols="72">--
Dr. Marco Hugentobler
Sourcepole - Linux & Open Source Solutions
Weberstrasse 5, CH-8004 Zürich, Switzerland
<a href="mailto:marco.hugentobler@sourcepole.ch" target="_blank">marco.hugentobler@sourcepole.ch</a> <a href="http://www.sourcepole.ch" target="_blank">http://www.sourcepole.ch</a>
Technical Advisor QGIS Project Steering Committee </pre>
</div></div>
</blockquote></div><br><br clear="all"><br>-- <br>-----------------<br>Andrea Peri<br>. . . . . . . . . <br>qwerty àèìòù<br>-----------------<br>
</div>