Opened 16 years ago
Closed 16 years ago
#419 closed enhancement (worksforme)
too many hits in gazetteer because of built-in *
Reported by: | kolaloka | Owned by: | dev |
---|---|---|---|
Priority: | minor | Milestone: | 2.6 release |
Component: | tools | Version: | 2.6 rc1 |
Keywords: | gazetteer search | Cc: |
Description
Suppose a layer with 100000 polygon features, numbered from 1 to 1000. I want to search for the number 2, (approximately 100 hits if distribution is even) but as search is performed for *2* I get all features whose number contains the digit 2 which is far more than I wanted. Moreover, the old (2.5) Gazetteer had problems even for 700 hits, I don't think the new one would be much more efficient. I suggest to remove those built-in * from the Literal tag. User could put * where and when really needed.
file: http/javascripts/mod_wfs_gazetteer_client.php
Note:
See TracTickets
for help on using tickets.
in Mapbender 2.6rc1 it's possible to define the search operator for every single configured search field in the wfs conf module (column operator at the end of the table). The bothside operator *xx* is only the default value if no option for operator is set in the wfs conf. User can decide whether he wants to use operator like rightside, bothside, equal, greaterThan, lessThan, greaterThanOrEqualTo, lessThanOrEqualTo