I am trying to create a filter to show only specific features based on an attribute query within a WFS using QGIS. This works fine when using the standard WFS loader and creating a filter (based on the type "attribute"='value'). However this only works when the features are cached.
I want to be able to use a filter like this for an uncached WFS layer. Does anyone have any idea how to do this?
Example using the BGS public WFS.
A standard cached query would look like this:
http://ogc.bgs.ac.uk/cgi-bin/BGS_Be...ENAME=GBR_BGS_625k_SLS&SRSNAME=CRS:84&FILTER= LEX_ROCK_D PEAT When I untick the cached option, the layer source is as follows:
http://ogc.bgs.ac.uk/cgi-bin/BGS_Be...4851240830698069,57.42328922738386154&FILTER= LEX_ROCK_D PEAT The main difference is the bounding box. What happens with the second layer definition is that the layer loads but has no features within it.
I am able to create a geoserver layer within my WFS that meets this query, but I am trying to find a way that users will be able to replicate without intervention at the geoserver end.
أكثر...
I want to be able to use a filter like this for an uncached WFS layer. Does anyone have any idea how to do this?
Example using the BGS public WFS.
A standard cached query would look like this:
http://ogc.bgs.ac.uk/cgi-bin/BGS_Be...ENAME=GBR_BGS_625k_SLS&SRSNAME=CRS:84&FILTER= LEX_ROCK_D PEAT When I untick the cached option, the layer source is as follows:
http://ogc.bgs.ac.uk/cgi-bin/BGS_Be...4851240830698069,57.42328922738386154&FILTER= LEX_ROCK_D PEAT The main difference is the bounding box. What happens with the second layer definition is that the layer loads but has no features within it.
I am able to create a geoserver layer within my WFS that meets this query, but I am trying to find a way that users will be able to replicate without intervention at the geoserver end.
أكثر...