Restrict a WFS request to the current map extent

251 views
Skip to first unread message

Andy Bates

unread,
Aug 29, 2012, 11:43:53 PM8/29/12
to australian-qg...@googlegroups.com
In response to Noli's post about the WFS 2.0 plugin (I thought we should take the WFS thing out of the intros and into the main discussion if that's cool?!)

Does anyone know of a WFS 1.0.0 plugin that would allow us to restrict a WFS request to the current map extent? I'm sure QGIS used to do it, but not in 1.8! That WFS 2.0 plugin appears to have it too, but it doesn't work with WFS 1.0.0 (obviously!).

Or is it getting fixed in the trunk, Nathan?

In WA we get our cadastre, etc via WFS 1.0.0 from Landgate's SLIP (https://www2.landgate.wa.gov.au/web/guest/home) but there is a 10,000 feature limit for each request, so if you open the WFS in QGIS it tries to download the whole thing, hits the feature limit and stops.

Is there a way to limit the features in the request through QGIS, ideally automatically, or using the filter in the "add WFS layer from a server" dialog? Maybe I'm missing something...

Cheers

Andy

Nathan Woodrow

unread,
Aug 30, 2012, 2:26:06 AM8/30/12
to australian-qg...@googlegroups.com
Andy,

There seems to be a ticket opened for it on the bug tracker http://hub.qgis.org/issues/4604.

It might just need to a poke to see if the patch can be applied, people might have just forgot about it or not had the time to apply and test it ( I still have tickets against my name due to lack of time :S )

- Nathan

Andy Bates

unread,
Sep 5, 2012, 12:49:10 AM9/5/12
to australian-qg...@googlegroups.com

Hey Nathan,

I noticed on the bug tracker that the status changed today, Paolo Cavallini changed it to :

"Target version changed from Version 1.8.0 to Version 2.0.0"

so I guess we have a while to wait yet... do you know roughly when 2.0 will be out, bearing in mind 1.9 is still in dev/uat?!

At least it's getting fixed though!


Cheers

Andy

Nathan Woodrow

unread,
Sep 9, 2012, 6:42:18 PM9/9/12
to australian-qg...@googlegroups.com
There is no ETA on the 2.0 release at the moment I don't think.  I would like to see next year sometime in order to give us time to clean up everything.

I would still add a comment on the bug if you think that feature is important report, having it's target version changed doesn't mean it will make it into the next release only that it's not going to be included in a 1.8 release.

- Nathan
Reply all
Reply to author
Forward
0 new messages