[Mapbender-users] problem with wfs search

Verena Diewald verena.diewald at wheregroup.com
Thu Jul 31 04:36:01 EDT 2008

Hello Karsten,

the possibility to choose between different operators like  PropertyIsEqualTo, 
PropertyIsGreaterThan etc. for wfs search will be included in one of the 
upcoming Mapbender versions. Performance of showing the results and 
highlighting them will be improved, too. 
But I agree to you that it would make sense to think about an alternative way 
of highlighting objects when having large polygons with lots of basepoints.



Am Mittwoch 30 Juli 2008 09:46:53 schrieb Karsten Vennemann:
> Thanks Verena,
> I was almost ready to post the params of the requests here when I found out
> that there was a combination of two things that made me think the search
> wasn't configured properly (when it actually kind of worked):
> 1. I checked the Upper box in admin1 that made some of the search strings I
> entered  for debugging not match -> "Kein Ergebnis" (no result)
> 2. The search was just long (not endless) e.g. when entering the string
> "King" in the County search. When clicking on the pop up box (that appears
> during the long search) to either debug, stop, or continue the script,
> after clicking to "continue" 3 times, then King county was found.
> Using firebug I found out what caused this - King county shape polygon has
> about 1200 vertices which where sent to the client and which ( I think)
> caused the delay. At least when I generalized the shape file and loaded it
> into Postgis instead the search was fast.
> Now I have two more questions:
> Is it generally advised to weed polygon features for wfs searches, or would
> server side highlighting do the rick to perform faster. What is recommended
> best practice ?
> Is it possible to configure the gazetteer module to offer searches for
> greater, equal or smaller then searches on numbers? It does a great job
> matching strings. Can I use it to find all areas with an attribute above a
> creatin number using ? The .server site mentions that there are operators
> PropertyIsEqualTo ( = )
> PropertyIsNotEqualTo ( <> )
> PropertyIsGreaterThan ( > )
> PropertyIsLessThan ( < )
> PropertyIsLessThanOrEqualTo ( <= )
> PropertyIsGreaterThanOrEqualTo ( >= )
> PropertyIsBetween
> similar to what is outlined in the Mapserver reference at
> http://mapserver.gis.umn.edu/docs/howto/filterencoding/
> Or do I need to code my own "query builder" module for mapbender in order
> to do that?
> Thanks Karsten


More information about the Mapbender_users mailing list