I looked at Postgres log and if I'm not missing something, this is the
query:

SELECT
"gid","name","area",encode(asBinary(force_2d("the_geom"),'XDR'),'base64') as
"the_geom" FROM "states" WHERE "the_geom" && GeomFromText('POLYGON
((-7134402.895051801 -4322800.136486195, -7134402.895051801
-3351652.113513805, -5290601.604948199 -3351652.113513805,
-5290601.604948199 -4322800.136486195, -7134402.895051801
-4322800.136486195))', 900913)

The "name" field should be fetched for labeling. It's required in my SLD to
be done like that.

This case, I think Geoserver does filtering in memory. Doesn't it? Remember
this was the case where the filter was used within a SLD, not in WFS. I
think it's ok that Geoserver behaves this way since it must load all
polygons within the extent anyway.


2011/2/11 Andrea Aime <andrea.a...@geo-solutions.it>

> On Fri, Feb 11, 2011 at 6:01 PM, Fernando Barbat <fbar...@gmail.com>
> wrote:
> > You're right. The column in PostGIS is numeric(10,0) so it is an Integer.
> > However, GeoServer detects it just as a BigDecimal (that's what the admin
> > interface says in the layer configuration) and that's why I was using a
> > non-integer representation to generate the Filter.
> >
> > Anyway, it's odd that Geoserver behaves differently for
> PropertyIsNotEqualTo
> > and PropertyIsEqualTo.
>
> If this is postgis the two, property is equals, and property is not equals,
> should be translated into sql as:
>
> area = 530.0
> and
> area != 530.0
>
> maybe it's PostgreSQL that's treating them differently?
> Would be good to see the actual SQL, if you use the
> "geotools_developer_logging" profile
> you should see the query in the logs
>
> 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 333 8128928
>
> 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
>
> -------------------------------------------------------
>
------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Reply via email to