Hi GioHappy,
I Agree that more probably the bottleneck is at provider level,
However just to better understand the question , before start to explore
the spatialite provider level , I like to study well what the
"appendLayerBoundingBoxes" to effectively.
Many thx for pointing me to the right dir
Andrea,
as pointed in the preovious emails, QGIS Server doesn't calculate the BBOX
itself. It gets them from the layer infos:
https://github.com/qgis/QGIS/blob/master/src/mapserver/qgsprojectparser.cpp#L1075
If there's a bottleneck it's ath the provider level.
Giovanni
2014-02-17 9:50 GMT+01:00
Hi,
Yes, it is correctly defined thx.
Also I verified that is used in my compile session.
Now I like to try to do some change to c-code to have , if possible, a
faster bbox calculation on a spatialite 4.1.1.
Please , can pointing me forward the right c file where qgis-server try to
calculate the
Hi Andrea,
On Sun, 16. Feb 2014 at 17:16:39 +0100, Andrea Peri wrote:
>I found it.
>
>It was defined in the cmake section:
>FindSPATIALITE.cmake
>
>Ok, now I procede to understand if it is really checked.
$ grep SPATIALITE_VERSION_GE_4_0_0 $yourbuilddir/CMakeCache.txt
SPATIALITE
Hi,
I found it.
It was defined in the cmake section:
FindSPATIALITE.cmake
Ok, now I procede to understand if it is really checked.
Regards,
A.
2014-02-16 16:58 GMT+01:00 Andrea Peri :
> Hi,
>
> study-ing the qgis code, I see in the spatialite provider there is a
> significative piece of co
Hi,
study-ing the qgis code, I see in the spatialite provider there is a
significative piece of code conditioned by
some
#IFDEF SPATIALITE_VERSION_GE_4_0_0
I don't see any option in cmake setting named like this.
Is this a missing ?
Thx,
A.
2014-02-14 10:54 GMT+01:00 Andrea Peri :
> Hi,
>
2014-02-14 Bernhard Ströbl :
> Marco,
>
> could you fix this until 2.2 release?
It wasn't forgotten.
giovanni
___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-user
Marco,
could you fix this until 2.2 release?
Bernhard
Am 14.02.2014 11:15, schrieb Marco Hugentobler:
Hi Giovanni
Yes, right, it was not forgotten but is really added to the top level group.
Regards,
Marco
On 14.02.2014 11:11, G. Allegri wrote:
Marco, for the root I thought the OWS setting
Hi Giovanni
Yes, right, it was not forgotten but is really added to the top level group.
Regards,
Marco
On 14.02.2014 11:11, G. Allegri wrote:
Marco, for the root I thought the OWS setting was used [1], while it
isn't for the groups/layers childs [2]. Is it right?
giovanni
[1]
https://gith
Marco, for the root I thought the OWS setting was used [1], while it isn't
for the groups/layers childs [2]. Is it right?
giovanni
[1]
https://github.com/qgis/QGIS/blob/master/src/mapserver/qgsprojectparser.cpp#L138
[2]
https://github.com/qgis/QGIS/blob/master/src/mapserver/qgsprojectparser.cpp#L
Hi Bernhard
That option was meant to give the webclient a hint where to zoom first.
But it probably was forgotten in the server and I agree it would be good
to overwrite the calculated box in the toplevel group.
Regards,
Marco
On 14.02.2014 10:58, Bernhard Ströbl wrote:
Hi Marco,
I have a
>
>
> I have a question in this context (I thought I made ticket but cannot find
> it)
> What is the sense of setting the bounding box in OWS tab if it is always
> calculated to the sum of the bboxes of the layers in the project? IMHO
> setting the bbox in the project properties should override any
Hi Marco,
I have a question in this context (I thought I made ticket but cannot
find it)
What is the sense of setting the bounding box in OWS tab if it is always
calculated to the sum of the bboxes of the layers in the project? IMHO
setting the bbox in the project properties should override an
Hi,
thx I now start to understand better the question.
Infact I'm using spatialite db. A 4.1.1 db spatialite.
The spatialite db has an internal statistics table to perform a very fast
resolution of the bboxes of single datasets.
I always update it using the command:
select UpdateLayerStatistics(
Hi Andrea, Giovanni
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).
For a faster startup, having a persistent cache as Giovanni
>
>
> I don't understand why the qgis-server eed to calculate always the bbox.
> In the server project windows,
> qgis ask for the published bbox.
> Why it don't use it as bbox rather than calculate it on every request ?
>
Marco, correct me if I'm wrong.
QGIS Server doesn't calculate the BBOX, it
100 layers are not really many.
As example: you can think to our Land-Usability wms.
It return evenry single code as a layer.
And also grouped layers.
And we have 2 year (2007 and 2010) in the same wms service.
http://www502.regione.toscana.it/wmsraster/com.rt.wms.RTmap/wms?map=wmsucs&service=wm
Hi,
thx for response.
I tested my project with qgis desktop dev version from osgeo4w 32 bit.
AFAIK it is a spatialite 4.1.1.
In my server machine I use still spatialite 4.1.1 compiled from sources.
So I guess the libspatialite version is the same.
But as I report in the qgis compile settings the
2014-02-14 Marco Hugentobler :
> Hi Andrea
>
>
> >I suspect that QS try always to recalc the box of every layer.
>
> 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 r
Hi Andrea
>I suspect that QS try always to recalc the box of every layer.
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).
>Perhaps a
Hi,
I partially resolved.
The framework I sued will allow me bypass the getcapabilities phase and go
directly to the getmap phase.
Initizally also the getmap phase seem to be too slow, but after some try I
notice that a slow bottleneck is the change of SRS.
So fixing the SRS to the same of the dat
Thx giohappy. Please continue in private to avoid noise in list
Il 13/feb/2014 13:02 "G. Allegri" ha scritto:
> I missed your original question: no, QGIS Servet, shouldn't recalc the
> BBOX. In case it recalcs the capabilities but not the layers extents...
> The delay will probably derive from so
The goal of fcgi is storie temporary information. In tthe wms
infrastrutture the bbox is an importante information. Storing it in cache
OS errorbprone. As example think to an editabile continuos s layer. In this
example is good to recalc always this is settable in mapserver or
geoserver. Bit is qgi
I missed your original question: no, QGIS Servet, shouldn't recalc the
BBOX. In case it recalcs the capabilities but not the layers extents...
The delay will probably derive from something else...
Giovanni
Il 13/feb/2014 12:54 "Andrea Peri" ha scritto:
> Storie a bbox in volatile RAM is noto a g
Storie a bbox in volatile RAM is noto a good practice
Il 13/feb/2014 12:46 "Paolo Cavallini" ha scritto:
> Il 13/02/2014 12:44, Andrea Peri ha scritto:
> > THX forma explain.
> > I do noto use fcgi.
> > There is no option to store in project the box ? Afaik gepserver recalc
> > and store in db. M
>
>
>
> AFAIK it is impossible to obtain good performances in QGIS Server
> without FCGI.
> All the best.
>
FCGI should offer better performances becuse the application is retained in
memory. AFAIK QGIS Server with simple CGI cannot mantain a cache...
giovanni
>
> --
> Paolo Cavallini - www.fau
Il 13/02/2014 12:44, Andrea Peri ha scritto:
> THX forma explain.
> I do noto use fcgi.
> There is no option to store in project the box ? Afaik gepserver recalc
> and store in db. Mapserver allow to set manually in mapfile.
AFAIK it is impossible to obtain good performances in QGIS Server
without
THX forma explain.
I do noto use fcgi.
There is no option to store in project the box ? Afaik gepserver recalc and
store in db. Mapserver allow to set manually in mapfile.
Il 13/feb/2014 12:30 "G. Allegri" ha scritto:
> As far as I know QGIS Server should cache the capabilities if you use it
> un
As far as I know QGIS Server should cache the capabilities if you use it
under FCGI. Otherwise every new instance will have to recalc them.
giovanni
2014-02-13 Andrea Peri :
> Yes. Three srs
> Il 13/feb/2014 11:37 "Paolo Cavallini" ha scritto:
>
>> Il 13/02/2014 11:30, Andrea Peri ha scritto:
Yes. Three srs
Il 13/feb/2014 11:37 "Paolo Cavallini" ha scritto:
> Il 13/02/2014 11:30, Andrea Peri ha scritto:
> > Hi I'm trying to publish with qgis.server a project with some huge
> > dayaset. Actually the getcapabilities tale about 40 sec to return. I
> > suspect that QS try always to recalc
Il 13/02/2014 11:30, Andrea Peri ha scritto:
> Hi I'm trying to publish with qgis.server a project with some huge
> dayaset. Actually the getcapabilities tale about 40 sec to return. I
> suspect that QS try always to recalc the box of every layer.
> Is confirmed that qgis.server recompute always th
Hi I'm trying to publish with qgis.server a project with some huge dayaset.
Actually the getcapabilities tale about 40 sec to return. I suspect that QS
try always to recalc the box of every layer.
Is confirmed that qgis.server recompute always the box for every request ?
If confirmed, There is an o
32 matches
Mail list logo
