Re: [Qgis-user] WFS caching behaviour
> > > 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). > > But if someone starts to fix this, please do not make it to send a new > GetFeature request with every mouse roll step. > With caching off, it's supposed to do that. However, I did report http://hub.qgis.org/issues/9439 yesterday (QGIS sends a request for every scroll, even intermediate scrolls when you do the wheel lots at once!) - maybe that's what you're referring to. > > So bug report it is. > And more to come I bet. > > It keeps me out of trouble! :-) Thanks again, 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@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-user
Re: [Qgis-user] WFS caching behaviour
Jonathan Moules writes: > Hi Jukka, You do seem to like Fiddler! No, the name of the software is not important but I like to know what really happens and with OGC services it means that one must see the messages which client and server are sending. > 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). But if someone starts to fix this, please do not make it to send a new GetFeature request with every mouse roll step. > So bug report it is. And more to come I bet. -Jukka- > Cheers, > Jonathan ___ Qgis-user mailing list Qgis-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-user
Re: [Qgis-user] WFS caching behaviour
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 wrote: > Jonathan Moules 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@... > > http://lists.osgeo.org/mailman/listinfo/qgis-user > > > > > ___ > Qgis-user mailing list > Qgis-user@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. ___ Qgis-user mailing list Qgis-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-user
Re: [Qgis-user] WFS caching behaviour
Jonathan Moules 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@... > http://lists.osgeo.org/mailman/listinfo/qgis-user ___ Qgis-user mailing list Qgis-user@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-user
[Qgis-user] WFS caching behaviour
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? 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@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-user
