[Geoserver-users] Whitespace in Value Passed to Filter

Jerome_A_Wendell · April 10, 2013, 7:19pm

I am using GeoServer and OpenLayers. I have an OGC filter setup to be used on a WMS layer. The filtered features are being placed on a vector layer. As long as the value that I pass to the filter does not contain any whitespace, the filter works fine, and the features are returned by GeoServer. If the value passed to the filter contains whitespace within it, nothing is returned by GeoServer. I am using Firefox with Firebug to test the map, and all of the values that are passed to the filter are shown correctly in the POST command. I know the features exist on the layer that is being filtered, so the problem is with the filter when the value contains whitespace. Is there anything that I can do to the filter so that the whitespace doesn’t cause the search to fail?

Any suggestions would be greatly appreciated.

Thanks.

Jerome_A_Wendell · April 11, 2013, 8:17pm

I am using GeoServer 2.2.4 and OpenLayers 2.12. I have not found any explanation documented as to why having whitespace within the value passed to the filter would cause the filter to fail. Could this be a bug?

Thanks,

Jerome Wendell

From: Jerome A. Wendell [mailto:jawendell@anonymised.com…]
Sent: Wednesday, April 10, 2013 3:20 PM
To: geoserver-users@lists.sourceforge.net
Subject: [Geoserver-users] Whitespace in Value Passed to Filter

I am using GeoServer and OpenLayers. I have an OGC filter setup to be used on a WMS layer. The filtered features are being placed on a vector layer. As long as the value that I pass to the filter does not contain any whitespace, the filter works fine, and the features are returned by GeoServer. If the value passed to the filter contains whitespace within it, nothing is returned by GeoServer. I am using Firefox with Firebug to test the map, and all of the values that are passed to the filter are shown correctly in the POST command. I know the features exist on the layer that is being filtered, so the problem is with the filter when the value contains whitespace. Is there anything that I can do to the filter so that the whitespace doesn’t cause the search to fail?

Any suggestions would be greatly appreciated.

Thanks.

Ben_Caradoc-Davies · April 12, 2013, 1:31am

Jerome,

can you please provide us with the exact request including filter? Note that if this is a GET request, the path must be correctly encoded.

Kind regards,
Ben.

On 12/04/13 04:17, Jerome A. Wendell wrote:

I am using GeoServer 2.2.4 and OpenLayers 2.12. I have not found any
explanation documented as to why having whitespace within the value
passed to the filter would cause the filter to fail. Could this be a bug?

Thanks,

Jerome Wendell

*From:*Jerome A. Wendell [mailto:jawendell@anonymised.com]
*Sent:* Wednesday, April 10, 2013 3:20 PM
*To:* geoserver-users@lists.sourceforge.net
*Subject:* [Geoserver-users] Whitespace in Value Passed to Filter

I am using GeoServer and OpenLayers. I have an OGC filter setup to be
used on a WMS layer. The filtered features are being placed on a vector
layer. As long as the value that I pass to the filter does not contain
any whitespace, the filter works fine, and the features are returned by
GeoServer. If the value passed to the filter contains whitespace within
it, nothing is returned by GeoServer. I am using Firefox with Firebug to
test the map, and all of the values that are passed to the filter are
shown correctly in the POST command. I know the features exist on the
layer that is being filtered, so the problem is with the filter when the
value contains whitespace. Is there anything that I can do to the filter
so that the whitespace doesn’t cause the search to fail?

Any suggestions would be greatly appreciated.

Thanks.

--
Ben Caradoc-Davies <Ben.Caradoc-Davies@anonymised.com>
Software Engineer
CSIRO Earth Science and Resource Engineering
Australian Resources Research Centre

Jerome_A_Wendell · April 12, 2013, 2:37am

Ben,

Thank you very much for your reply. Below is the portion of my code used to make the request:

var filter = new OpenLayers.Filter.Comparison({
                type: OpenLayers.Filter.Comparison.EQUAL_TO,
                property: 'myproperty',
                value: ‘myvalue’
  });
wfsProtocol = new OpenLayers.Protocol.WFS({
                version: "1.1.0",
                url: "http://myserver:8080/geoserver/mystore/wfs",
                featureType: "mylayer", //name of the geoserver layer
                featureNS: "mystore", //name of the geoserver store
                geometryName: "the_geom",
                srsName: "EPSG:4326",
                scope: strategy
});
var strategy = new OpenLayers.Strategy.Fixed();
var response = wfsProtocol.read({
                filter: filter,
                callback: processWFSQuery
});
function processWFSQuery(response) {
try {
                                var gmlParser = new OpenLayers.Format.GML.v3();
                                var features = gmlParser.read(response.priv.responseXML);
                                vectorLayer.destroyFeatures();
                                if(features.length > 0) {
                                                for(var i = 0; i < features.length; i++) {
                                                                var feature = features[i];
                                                                feature.geometry.transform(new OpenLayers.Projection('EPSG:4326'),this.map.getProjectionObject());
                                                                vectorLayer.addFeatures(feature);
                                                }
                                layextent = vectorLayer.getDataExtent();
                                map.zoomToExtent(layextent);
                                }else {
                                                alert("Not found!");
                                                if (popup){
                                                                popup.destroy();
                                                }
                                }
                } catch(e) {
                                alert("Error: " + e);
                }
}

If you need additional information, please let me know. I appreciate your help.

Thanks,

Jerome Wendell

-----Original Message-----
From: Ben Caradoc-Davies [mailto:Ben.Caradoc-Davies@anonymised.com]
Sent: Thursday, April 11, 2013 9:31 PM
To: jawendell@anonymised.com
Cc: geoserver-users@lists.sourceforge.net
Subject: Re: [Geoserver-users] Whitespace in Value Passed to Filter

Jerome,

can you please provide us with the exact request including filter? Note that if this is a GET request, the path must be correctly encoded.

Kind regards,
Ben.

--
Ben Caradoc-Davies <Ben.Caradoc-Davies@anonymised.com> Software Engineer CSIRO Earth Science and Resource Engineering Australian Resources Research Centre

Andrea_Aime4 · April 12, 2013, 7:29am

On Fri, Apr 12, 2013 at 4:37 AM, Jerome A. Wendell <jawendell@anonymised.com

wrote:

Ben,

Thank you very much for your reply. Below is the portion of my code used
to make the request:

var filter = new OpenLayers.Filter.Comparison({
                type: OpenLayers.Filter.Comparison.EQUAL_TO,
                property: 'myproperty',
                value: ‘myvalue’
  });
wfsProtocol = new OpenLayers.Protocol.WFS({
                version: "1.1.0",
                url: "http://myserver:8080/geoserver/mystore/wfs",
                featureType: "mylayer", //name of the geoserver layer
                featureNS: "mystore", //name of the geoserver store
                geometryName: "the_geom",
                srsName: "EPSG:4326",
                scope: strategy
});
var strategy = new OpenLayers.Strategy.Fixed();
var response = wfsProtocol.read({
                filter: filter,
                callback: processWFSQuery
});
function processWFSQuery(response) {
try {
                                var gmlParser = new
OpenLayers.Format.GML.v3();
                                var features =
gmlParser.read(response.priv.responseXML);
                                vectorLayer.destroyFeatures();
                                if(features.length > 0) {
                                                for(var i = 0; i <
features.length; i++) {
                                                                var
feature = features[i];

feature.geometry.transform(new
OpenLayers.Projection('EPSG:4326'),this.map.getProjectionObject());

vectorLayer.addFeatures(feature);
                                                }
                                layextent = vectorLayer.getDataExtent();
                                map.zoomToExtent(layextent);
                                }else {
                                                alert("Not found!");
                                                if (popup){

popup.destroy();
                                                }
                                }
                } catch(e) {
                                alert("Error: " + e);
                }
}

Can you use Firebug/Chrome dev tools to capture the exact POST request
being made?
Also, what data store are you using? Shapefiles, Oracle, PostGIS,....

Cheers
Andrea

--

GeoServer training in Milan, 6th & 7th June 2013! Visit
http://geoserver.geo-solutions.it for more information.

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

-------------------------------------------------------

Eduard_Natale · April 12, 2013, 7:36am

I suggest to use Wireshark to capture GET/POST request and OK reply from the server. Using filter ‘http’

···

Ben,

Thank you very much for your reply. Below is the portion of my code used to make the request:

var filter = new OpenLayers.Filter.Comparison({
type: OpenLayers.Filter.Comparison.EQUAL_TO,
property: ‘myproperty’,
value: ‘myvalue’
});
wfsProtocol = new OpenLayers.Protocol.WFS({
version: “1.1.0”,
url: “http://myserver:8080/geoserver/mystore/wfs”,
featureType: “mylayer”, //name of the geoserver layer
featureNS: “mystore”, //name of the geoserver store
geometryName: “the_geom”,
srsName: “EPSG:4326”,
scope: strategy
});
var strategy = new OpenLayers.Strategy.Fixed();
var response = wfsProtocol.read({
filter: filter,
callback: processWFSQuery
});
function processWFSQuery(response) {
try {
var gmlParser = new OpenLayers.Format.GML.v3();
var features = gmlParser.read(response.priv.responseXML);
vectorLayer.destroyFeatures();
if(features.length > 0) {
for(var i = 0; i < features.length; i++) {
var feature = features[i];
feature.geometry.transform(new OpenLayers.Projection(‘EPSG:4326’),this.map.getProjectionObject());
vectorLayer.addFeatures(feature);
}
layextent = vectorLayer.getDataExtent();
map.zoomToExtent(layextent);
}else {
alert(“Not found!”);
if (popup){
popup.destroy();
}
}
} catch(e) {
alert("Error: " + e);
}
}

Can you use Firebug/Chrome dev tools to capture the exact POST request being made?
Also, what data store are you using? Shapefiles, Oracle, PostGIS,…

Cheers
Andrea

–

==
GeoServer training in Milan, 6th & 7th June 2013! Visit http://geoserver.geo-solutions.it for more information.

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

Jerome_A_Wendell · April 12, 2013, 12:44pm

Andrea,

Thanks for your reply, I really appreciate it. I am using a shapefile data store. The post request for the feature that is found is as follows:

XML

<wfs:GetFeature xmlns:wfs=“http://www.opengis.net/wfs” service=“WFS” version=“1.1.0” xsi:schemaLocation=“http://www.opengis.net/wfs http://schemas.opengis.net/wfs/1.1.0/wfs.xsd” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”>

<wfs:Query typeName=“feature:wv_mineral_tracts” srsName=“EPSG:4326” xmlns:feature=“wv_data”>

<ogc:Filter xmlns:ogc=“http://www.opengis.net/ogc”>

<ogc:PropertyIsEqualTo matchCase=“true”>

ogc:PropertyNameROOTID</ogc:PropertyName>

ogc:Literal01-01-9999-0100-0990-0000</ogc:Literal>

</ogc:PropertyIsEqualTo>

</ogc:Filter>

</wfs:Query>

</wfs:GetFeature>

Source

<wfs:GetFeature xmlns:wfs=“http://www.opengis.net/wfs” service=“WFS” version=“1.1.0” xsi:schemaLocation=“http://www.opengis.net/wfs http://schemas.opengis.net/wfs/1.1.0/wfs.xsd” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”><wfs:Query typeName=“feature:wv_mineral_tracts” srsName=“EPSG:4326” xmlns:feature=“wv_data”><ogc:Filter xmlns:ogc=“http://www.opengis.net/ogc”><ogc:PropertyIsEqualTo matchCase=“true”>ogc:PropertyNameROOTID</ogc:PropertyName>ogc:Literal01-01-9999-0100-0990-0000</ogc:Literal></ogc:PropertyIsEqualTo></ogc:Filter></wfs:Query></wfs:GetFeature>

And the response for the above request is below:

<?xml version="1.0" encoding="UTF-8"?>

<wfs:FeatureCollection numberOfFeatures=“1” timeStamp=“2013-04-12T12:32:44.975Z” xsi:schemaLocation=“http://www.titlemaps.com/wv_data http://www.titlemaps.com:8080/geoserver/wv_data/wfs?service=WFS&version=1.1.0&request=DescribeFeatureType&typeName=wv_data%3Awv_mineral_tracts http://www.opengis.net/wfs http://schemas.opengis.net/wfs/1.1.0/wfs.xsd” xmlns:ogc=“http://www.opengis.net/ogc” xmlns:gml=“http://www.opengis.net/gml” xmlns:wv_data=“http://www.titlemaps.com/wv_data” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance” xmlns:xlink=“http://www.w3.org/1999/xlink” xmlns:ows=“http://www.opengis.net/ows” xmlns:wfs=“http://www.opengis.net/wfs”>gml:featureMember<wv_data:wv_mineral_tracts gml:id=“wv_mineral_tracts.57”><wv_data:the_geom><gml:MultiSurface srsDimension=“2” srsName=“http://www.opengis.net/gml/srs/epsg.xml#4326”>gml:surfaceMember<gml:Polygon srsDimension=“2”>gml:exterior<gml:LinearRing srsDimension=“2”>gml:posList-79.91917805223417 38.99168620084022 -79.91775518812635 38.99146850204535 -79.9159418034612 38.98777276004835 -79.91486534977649 38.988193573320714 -79.91450162234823 38.98868830854628 -79.91353024036711 38.98818853580909 -79.91308215154596 38.98832832930842 -79.9077928103966 38.98476003091119 -79.91022019770175 38.98328188522186 -79.90963054816243 38.98245500701079 -79.91073246547312 38.98169203909736 -79.9116146582654 38.98156225053195 -79.91292513862976 38.981165179028835 -79.91344347967444 38.982230841650555 -79.91271894124013 38.98300726263689 -79.91209214827362 38.98321836175092 -79.91288307485652 38.98385944136893 -79.91260656668068 38.98449696878364 -79.9138493929973 38.98478611867047 -79.91529727270267 38.98337388110928 -79.91670959318768 38.984159812343385 -79.91796931267791 38.983383826308994 -79.9175439067215 38.98785006863406 -79.91822241655356 38.99012226609006 -79.91917805223417 38.99168620084022</gml:posList></gml:LinearRing></gml:exterior></gml:Polygon></gml:surfaceMember></gml:MultiSurface></wv_data:the_geom><wv_data:ROOTID>01-01-9999-0100-0990-0000</wv_data:ROOTID></wv_data:wv_mineral_tracts></gml:featureMember></wfs:FeatureCollection>

The post request for the feature that is not found is below:

XML

<wfs:GetFeature xmlns:wfs=“http://www.opengis.net/wfs” service=“WFS” version=“1.1.0” xsi:schemaLocation=“http://www.opengis.net/wfs http://schemas.opengis.net/wfs/1.1.0/wfs.xsd” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”>

<wfs:Query typeName=“feature:wv_mineral_tracts” srsName=“EPSG:4326” xmlns:feature=“wv_data”>

<ogc:Filter xmlns:ogc=“http://www.opengis.net/ogc”>

<ogc:PropertyIsEqualTo matchCase=“true”>

ogc:PropertyNameROOTID</ogc:PropertyName>

ogc:Literal01-01- 17-0012-0000-0000</ogc:Literal>

</ogc:PropertyIsEqualTo>

</ogc:Filter>

</wfs:Query>

</wfs:GetFeature>

Source

<wfs:GetFeature xmlns:wfs=“http://www.opengis.net/wfs” service=“WFS” version=“1.1.0” xsi:schemaLocation=“http://www.opengis.net/wfs http://schemas.opengis.net/wfs/1.1.0/wfs.xsd” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”><wfs:Query typeName=“feature:wv_mineral_tracts” srsName=“EPSG:4326” xmlns:feature=“wv_data”><ogc:Filter xmlns:ogc=“http://www.opengis.net/ogc”><ogc:PropertyIsEqualTo matchCase=“true”>ogc:PropertyNameROOTID</ogc:PropertyName>ogc:Literal01-01- 17-0012-0000-0000</ogc:Literal></ogc:PropertyIsEqualTo></ogc:Filter></wfs:Query></wfs:GetFeature>

The response for the request above is below:

<?xml version="1.0" encoding="UTF-8"?>

<wfs:FeatureCollection numberOfFeatures="0" timeStamp="2013-04-12T12:38:05.961Z" xsi:schemaLocation="http://www.titlemaps.com/wv_data http://www.titlemaps.com:8080/geoserver/wv_data/wfs?service=WFS&amp;version=1.1.0&amp;request=DescribeFeatureType&amp;typeName=wv_data%3Awv_mineral_tracts http://www.opengis.net/wfs http://schemas.opengis.net/wfs/1.1.0/wfs.xsd" xmlns:ogc="http://www.opengis.net/ogc" xmlns:gml="http://www.opengis.net/gml" xmlns:wv_data="http://www.titlemaps.com/wv_data" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:ows="http://www.opengis.net/ows" xmlns:wfs="http://www.opengis.net/wfs"/>

I get the same type of response for any features that have whitespace within the value passed to the filter. Both of the features in the requests above exist in the shapefile. In the layer preview of GeoServer I can perform the search and both features are found.

If you need any additional information, please let me know.

I appreciate your help.

Thanks,

Jerome Wendell

Jerome_A_Wendell · April 12, 2013, 12:49pm

Eduard,

I am not familiar with Wireshark, but I will check it out. Thanks for the suggestion.

Jerome Wendell

Jerome_A_Wendell · April 15, 2013, 4:10pm

Andrea,

I just wanted to follow-up to see if any additional information is needed pertaining to the problem that I am having with filters. Please let me know.

Thanks,

Jerome Wendell

From: Jerome A. Wendell [mailto:jawendell@anonymised.com]
Sent: Friday, April 12, 2013 8:45 AM
To: ‘Andrea Aime’
Cc: ‘GeoServer Mailing List List’
Subject: Re: [Geoserver-users] Whitespace in Value Passed to Filter

Andrea,

Thanks for your reply, I really appreciate it. I am using a shapefile data store. The post request for the feature that is found is as follows:

XML

<wfs:GetFeature xmlns:wfs=“http://www.opengis.net/wfs” service=“WFS” version=“1.1.0” xsi:schemaLocation=“http://www.opengis.net/wfs http://schemas.opengis.net/wfs/1.1.0/wfs.xsd” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”>

<wfs:Query typeName=“feature:wv_mineral_tracts” srsName=“EPSG:4326” xmlns:feature=“wv_data”>

<ogc:Filter xmlns:ogc=“http://www.opengis.net/ogc”>

<ogc:PropertyIsEqualTo matchCase=“true”>

ogc:PropertyNameROOTID</ogc:PropertyName>

ogc:Literal01-01-9999-0100-0990-0000</ogc:Literal>

</ogc:PropertyIsEqualTo>

</ogc:Filter>

</wfs:Query>

</wfs:GetFeature>

Source

<wfs:GetFeature xmlns:wfs=“http://www.opengis.net/wfs” service=“WFS” version=“1.1.0” xsi:schemaLocation=“http://www.opengis.net/wfs http://schemas.opengis.net/wfs/1.1.0/wfs.xsd” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”><wfs:Query typeName=“feature:wv_mineral_tracts” srsName=“EPSG:4326” xmlns:feature=“wv_data”><ogc:Filter xmlns:ogc=“http://www.opengis.net/ogc”><ogc:PropertyIsEqualTo matchCase=“true”>ogc:PropertyNameROOTID</ogc:PropertyName>ogc:Literal01-01-9999-0100-0990-0000</ogc:Literal></ogc:PropertyIsEqualTo></ogc:Filter></wfs:Query></wfs:GetFeature>

And the response for the above request is below:

<?xml version="1.0" encoding="UTF-8"?>

<wfs:FeatureCollection numberOfFeatures=“1” timeStamp=“2013-04-12T12:32:44.975Z” xsi:schemaLocation=“http://www.titlemaps.com/wv_data http://www.titlemaps.com:8080/geoserver/wv_data/wfs?service=WFS&version=1.1.0&request=DescribeFeatureType&typeName=wv_data%3Awv_mineral_tracts http://www.opengis.net/wfs http://schemas.opengis.net/wfs/1.1.0/wfs.xsd” xmlns:ogc=“http://www.opengis.net/ogc” xmlns:gml=“http://www.opengis.net/gml” xmlns:wv_data=“http://www.titlemaps.com/wv_data” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance” xmlns:xlink=“http://www.w3.org/1999/xlink” xmlns:ows=“http://www.opengis.net/ows” xmlns:wfs=“http://www.opengis.net/wfs”>gml:featureMember<wv_data:wv_mineral_tracts gml:id=“wv_mineral_tracts.57”><wv_data:the_geom><gml:MultiSurface srsDimension=“2” srsName=“http://www.opengis.net/gml/srs/epsg.xml#4326”>gml:surfaceMember<gml:Polygon srsDimension=“2”>gml:exterior<gml:LinearRing srsDimension=“2”>gml:posList-79.91917805223417 38.99168620084022 -79.91775518812635 38.99146850204535 -79.9159418034612 38.98777276004835 -79.91486534977649 38.988193573320714 -79.91450162234823 38.98868830854628 -79.91353024036711 38.98818853580909 -79.91308215154596 38.98832832930842 -79.9077928103966 38.98476003091119 -79.91022019770175 38.98328188522186 -79.90963054816243 38.98245500701079 -79.91073246547312 38.98169203909736 -79.9116146582654 38.98156225053195 -79.91292513862976 38.981165179028835 -79.91344347967444 38.982230841650555 -79.91271894124013 38.98300726263689 -79.91209214827362 38.98321836175092 -79.91288307485652 38.98385944136893 -79.91260656668068 38.98449696878364 -79.9138493929973 38.98478611867047 -79.91529727270267 38.98337388110928 -79.91670959318768 38.984159812343385 -79.91796931267791 38.983383826308994 -79.9175439067215 38.98785006863406 -79.91822241655356 38.99012226609006 -79.91917805223417 38.99168620084022</gml:posList></gml:LinearRing></gml:exterior></gml:Polygon></gml:surfaceMember></gml:MultiSurface></wv_data:the_geom><wv_data:ROOTID>01-01-9999-0100-0990-0000</wv_data:ROOTID></wv_data:wv_mineral_tracts></gml:featureMember></wfs:FeatureCollection>

The post request for the feature that is not found is below:

XML

<wfs:GetFeature xmlns:wfs=“http://www.opengis.net/wfs” service=“WFS” version=“1.1.0” xsi:schemaLocation=“http://www.opengis.net/wfs http://schemas.opengis.net/wfs/1.1.0/wfs.xsd” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”>

<wfs:Query typeName=“feature:wv_mineral_tracts” srsName=“EPSG:4326” xmlns:feature=“wv_data”>

<ogc:Filter xmlns:ogc=“http://www.opengis.net/ogc”>

<ogc:PropertyIsEqualTo matchCase=“true”>

ogc:PropertyNameROOTID</ogc:PropertyName>

ogc:Literal01-01- 17-0012-0000-0000</ogc:Literal>

</ogc:PropertyIsEqualTo>

</ogc:Filter>

</wfs:Query>

</wfs:GetFeature>

Source

<wfs:GetFeature xmlns:wfs=“http://www.opengis.net/wfs” service=“WFS” version=“1.1.0” xsi:schemaLocation=“http://www.opengis.net/wfs http://schemas.opengis.net/wfs/1.1.0/wfs.xsd” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”><wfs:Query typeName=“feature:wv_mineral_tracts” srsName=“EPSG:4326” xmlns:feature=“wv_data”><ogc:Filter xmlns:ogc=“http://www.opengis.net/ogc”><ogc:PropertyIsEqualTo matchCase=“true”>ogc:PropertyNameROOTID</ogc:PropertyName>ogc:Literal01-01- 17-0012-0000-0000</ogc:Literal></ogc:PropertyIsEqualTo></ogc:Filter></wfs:Query></wfs:GetFeature>

The response for the request above is below:

<?xml version="1.0" encoding="UTF-8"?>

<wfs:FeatureCollection numberOfFeatures="0" timeStamp="2013-04-12T12:38:05.961Z" xsi:schemaLocation="[http://www.titlemaps.com/wv_data http://www.titlemaps.com:8080/geoserver/wv_data/wfs?service=WFS&amp;version=1.1.0&amp;request=DescribeFeatureType&amp;typeName=wv_data%3Awv_mineral_tracts http://www.opengis.net/wfs http://schemas.opengis.net/wfs/1.1.0/wfs.xsd](http://www.titlemaps.com/wv_data%20http:/www.titlemaps.com:8080/geoserver/wv_data/wfs?service=WFS&amp;version=1.1.0&amp;request=DescribeFeatureType&amp;typeName=wv_data%3Awv_mineral_tracts%20http://www.opengis.net/wfs%20http://schemas.opengis.net/wfs/1.1.0/wfs.xsd)" xmlns:ogc="[http://www.opengis.net/ogc](http://www.opengis.net/ogc)" xmlns:gml="[http://www.opengis.net/gml](http://www.opengis.net/gml)" xmlns:wv_data="[http://www.titlemaps.com/wv_data](http://www.titlemaps.com/wv_data)" xmlns:xsi="[http://www.w3.org/2001/XMLSchema-instance](http://www.w3.org/2001/XMLSchema-instance)" xmlns:xlink="[http://www.w3.org/1999/xlink](http://www.w3.org/1999/xlink)" xmlns:ows="[http://www.opengis.net/ows](http://www.opengis.net/ows)" xmlns:wfs="[http://www.opengis.net/wfs](http://www.opengis.net/wfs)"/>

I get the same type of response for any features that have whitespace within the value passed to the filter. Both of the features in the requests above exist in the shapefile. In the layer preview of GeoServer I can perform the search and both features are found.

If you need any additional information, please let me know.

I appreciate your help.

Thanks,

Jerome Wendell

Andrea_Aime4 · April 15, 2013, 7:37pm

On Mon, Apr 15, 2013 at 6:10 PM, Jerome A. Wendell <jawendell@anonymised.com

wrote:

Andrea,****

** **

I just wanted to follow-up to see if any additional information is needed
pertaining to the problem that I am having with filters. Please let me
know.

Looking at bug reports on the mailing list is the lowest priority among the
things I do for the community in my spare time.
Roughly speaking (it's my spare time, so I still retain the right to do
what I feel like doing),
first come looking into contributions (patches) incoming as pull requests
on github, then patches attached to jira,
then the stuff I want to contribute myself, then bug reports that seem to
affect several people, on jira.

So my suggest would be, open a bug report on jira.codehaus.org and add all
the information you provided here
over there, if there is enough interested in it (e.g.. people commenting
that they are affected too)
I'll likely be able to look into it during the next month or two (spare
time == weekends).
Ah, if you don't have an account you might have to register at
xircles.codehaus.org (they recently upgraded
jira and up until a week ago it was not possible to register there directly
anymore).

For more information about what you can expect to get out of this mailing
list, see here:
http://geoserver.org/display/GEOS/GeoServer+user+list+posting+guidelines

Cheers
Andrea

--

GeoServer training in Milan, 6th & 7th June 2013! Visit
http://geoserver.geo-solutions.it for more information.

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

-------------------------------------------------------

Jerome_A_Wendell · April 15, 2013, 7:47pm

Andrea,

Thanks for your reply. I appreciate the information.

Jerome Wendell

From: andrea.aime@anonymised.com [mailto:andrea.aime@anonymised.com] On Behalf Of Andrea Aime
Sent: Monday, April 15, 2013 3:37 PM
To: jawendell@anonymised.com
Cc: GeoServer Mailing List List
Subject: Re: [Geoserver-users] Whitespace in Value Passed to Filter

On Mon, Apr 15, 2013 at 6:10 PM, Jerome A. Wendell <jawendell@anonymised.com> wrote:

Andrea,

I just wanted to follow-up to see if any additional information is needed pertaining to the problem that I am having with filters. Please let me know.

Looking at bug reports on the mailing list is the lowest priority among the things I do for the community in my spare time.

Roughly speaking (it’s my spare time, so I still retain the right to do what I feel like doing),

first come looking into contributions (patches) incoming as pull requests on github, then patches attached to jira,

then the stuff I want to contribute myself, then bug reports that seem to affect several people, on jira.

So my suggest would be, open a bug report on jira.codehaus.org and add all the information you provided here

over there, if there is enough interested in it (e.g… people commenting that they are affected too)

I’ll likely be able to look into it during the next month or two (spare time == weekends).

Ah, if you don’t have an account you might have to register at xircles.codehaus.org (they recently upgraded

jira and up until a week ago it was not possible to register there directly anymore).

For more information about what you can expect to get out of this mailing list, see here:

http://geoserver.org/display/GEOS/GeoServer+user+list+posting+guidelines

Cheers

Andrea

–

==

GeoServer training in Milan, 6th & 7th June 2013! Visit http://geoserver.geo-solutions.it for more information.

Ing. Andrea Aime

@geowolf

Technical Lead

GeoSolutions S.A.S.

Via Poggio alle Viti 1187

55054 Massarosa (LU)

Italy

phone: +39 0584 962313

fax: +39 0584 1660272

mob: +39 339 8844549

http://www.geo-solutions.it

http://twitter.com/geosolutions_it

Jerome_A_Wendell · April 17, 2013, 8:45pm

Andrea,

I opened a bug report as you suggested. It can be viewed at https://jira.codehaus.org/browse/GEOS-5778. For now, I have setup an alternate solution using a cql filter on a WMS layer.

Thanks for your help. I appreciate it.

Jerome Wendell

From: andrea.aime@anonymised.com [mailto:andrea.aime@anonymised.com] On Behalf Of Andrea Aime
Sent: Monday, April 15, 2013 3:37 PM
To: jawendell@anonymised.com7…
Cc: GeoServer Mailing List List
Subject: Re: [Geoserver-users] Whitespace in Value Passed to Filter