Hi Andrea,
The bug has now been filed in JIRA
http://jira.codehaus.org/browse/GEOS-5124
<http://jira.codehaus.org/browse/GEOS-5124>I've also provided a patch to
fix the issue.
Cheers,
Gerson
On Wed, May 23, 2012 at 7:39 PM, Andrea Aime
<[email protected]>wrote:
> On Tue, May 22, 2012 at 2:04 AM, Gerson Galang <[email protected]>wrote:
>
>> Hi,
>>
>> I've been trying to get geotools' WFS client to work with the WITHIN
>> filter for a couple of days now but it just kept on giving an invalid
>> FeatureCollection size. I've done a bit more digging in the geotools' WFS
>> client code and found that it was actually geoserver that is preventing it
>> from giving me the correct info.
>>
>> If you send Geoserver a getCapabilities request (this defaults to version
>> 1.1), it won't list WITHIN filter as a supported spatial operator. On the
>> other hand, if you explicitly request that version 1.0.0 be used, it will
>> list WITHIN as a supported spatial operator.
>>
>> http://e1.newcastle.edu.au/geoserver/wfs?request=GetCapabilities <--
>> this doesn't list WITHIN as a supported spatial operator
>>
>> http://e1.newcastle.edu.au/geoserver/wfs?request=GetCapabilities&version=1.0.0
>> <--
>> this has WITHIN in the spatial operator list
>>
>> I have a feeling that it might just be configuration somewhere that needs
>> to be switched on to include WITHIN operator in the supported list.
>> Running an actual GetFeature query against a WFS 1.1 service I have below,
>> I get back the information I needed.
>>
>> http://e1.newcastle.edu.au/**geoserver/wfs?request=**
>> GetFeature&typeName=cfer:**AusBySLA&propertyName=Area_**
>> Code,SLA_Id,SLA_Name&cql_**filter=WITHIN%28the_geom,%**
>> 20POLYGON%20%28%28-33.**980647586%20140.961681984,%20-**
>> 39.159189527500004%20140.**961681984%20,%20-39.**159189527500004%20149.**
>> 976679008,%20-33.980647586%**20149.976679008,%20-33.**
>> 980647586%20140.961681984%29%**29%29<http://e1.newcastle.edu.au/geoserver/wfs?request=GetFeature&typeName=cfer:AusBySLA&propertyName=Area_Code,SLA_Id,SLA_Name&cql_filter=WITHIN%28the_geom,%20POLYGON%20%28%28-33.980647586%20140.961681984,%20-39.159189527500004%20140.961681984%20,%20-39.159189527500004%20149.976679008,%20-33.980647586%20149.976679008,%20-33.980647586%20140.961681984%29%29%29>
>>
>> Should I add an entry to JIRA about this issue?
>>
>
> Yep.
> Just looked, the code in the capablities transformer just misses that
> filter, but I don't see any good reason why it should,
> I tend to believe it's just an oversight.
>
> A patch with a test checking the spatial filters are all there would be
> nice too :-p
>
> Cheers
> Andrea
>
>
> --
> Ing. Andrea Aime
> GeoSolutions S.A.S.
> Tech lead
>
> Via Poggio alle Viti 1187
> 55054 Massarosa (LU)
> Italy
>
> phone: +39 0584 962313
> fax: +39 0584 962313
> mob: +39 339 8844549
>
> http://www.geo-solutions.it
> http://geo-solutions.blogspot.com/
> http://www.youtube.com/user/GeoSolutionsIT
> http://www.linkedin.com/in/andreaaime
> http://twitter.com/geowolf
>
>
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Geoserver-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users
