[Qgis-user] WFS caching behaviour

Jonathan Moules jonathanmoules at warwickshire.gov.uk
Tue Jan 28 00:12:15 PST 2014


Hi Jukka,
  You do seem to like Fiddler!
I was using my web-server logs, however Fiddler is confirming that the WFS
isn't making new requests when I zoom in/our except when I'm at distance
zoom's (it should do it at all zooms).

So bug report it is.
Cheers,
Jonathan


On 27 January 2014 18:05, Jukka Rahkonen <jukka.rahkonen at mmmtike.fi> wrote:

> Jonathan Moules <jonathanmoules at ...> writes:
>
> >
> >
> > Hi List,Before I report this one as a bug, I figured I should check.
> >
> > What's the desired behaviour of the WFS client in QGIS in respect to
> caching results versus making new requests.
> >
> >
> > Example:
> > WFS server only returns 500 results for any given request. There are
> 51639
> features in the layer.
> >
> > - If I load the layer using the "Cached" checkbox as ticked, then QGIS
> only loads 500 features. Fine.
> >
> >
> > - If I then add the layer again, but with "cached" unticked, then QGIS
> only loads 500 features - but they're 500 different features. Fine.
> >
> > Except in both cases when I zoom in/out, the features don't change; QGIS
> doesn't make new requests. I thought it was supposed to, at least with the
> uncached version? Both appear to behaving the exact same way to me.
> >
> > Am I doing something wrong?
>
> Hi,
>
> Made a trial with v. 2.0.1 and checked with Fiddler2 proxy what happens (I
> recommend).
> - With caching a plain GetFeature is sent and you will get the 500 first
> records.
> - Without caching QGIS adds a BBOX filter and applies the extents of the
> current map view. You will get the first 500 records within the box.
> - After zooming/panning a new request with BBOX filter gets fired.
>
> I can't say why QGIS does not send new features for you. But you a the one
> who should absolutely install Fiddler or some other logging proxy and you
> can do loads of wonderful bug reports in the future.
>
> -Jukka Rahkonen-
>
>
> >
> > Thanks,Jonathan
> >
> >
> > This transmission is intended for the named addressee(s) only and may
> contain sensitive or protectively marked material up to RESTRICTED and
> should be handled accordingly. Unless you are the named addressee (or
> authorised to receive it for the addressee) you may not copy or use it, or
> disclose it to anyone else. If you have received this transmission in error
> please notify the sender immediately. All email traffic sent to or from us,
> including without limitation all GCSX traffic, may be subject to recording
> and/or monitoring in accordance with relevant legislation.
> >
> >
> > _______________________________________________
> > Qgis-user mailing list
> > Qgis-user at ...
> > http://lists.osgeo.org/mailman/listinfo/qgis-user
>
>
>
>
> _______________________________________________
> Qgis-user mailing list
> Qgis-user at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/qgis-user
>

-- 
This transmission is intended for the named addressee(s) only and may 
contain sensitive or protectively marked material up to RESTRICTED and 
should be handled accordingly. Unless you are the named addressee (or 
authorised to receive it for the addressee) you may not copy or use it, or 
disclose it to anyone else. If you have received this transmission in error 
please notify the sender immediately. All email traffic sent to or from us, 
including without limitation all GCSX traffic, may be subject to recording 
and/or monitoring in accordance with relevant legislation.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/qgis-user/attachments/20140128/4949d682/attachment.html>


More information about the Qgis-user mailing list