Sebastian, I am not sure what your filter actually is, but I can tell you a few things for sure: - if it is an attribute filter then it will be slow, because there is no leverage at all available from indexing attributes in shape files - if it is a spatial filter, then you might need to reconfigure it a bit to ensure that it makes use of the spatial index on the shape file, at which point it should work a little better - in general, even a spatially indexed filter query on shape file might underperform a non-indexed query in memory, if only due to the massive disparity in access time overhead, as Andrea has discussed (though filesystem caching at the operating system level might make second and third runs through the filter faster as portions of the index and file get pulled into the filesystem memory cache) I am guessing that since your use case is geocoding you are doing lots of attribute comparisons. In order to make those fast, if you insist on keeping your data in shape files, you will need to enhance the shapefile datastore to support attribute indexes. I am pretty sure that this is what ArcView does, for example, in its geocoding routines. Paul On 21-Sep-06, at 8:13 AM, [EMAIL PROTECTED] wrote: Hi all! |
------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________ Geotools-gt2-users mailing list Geotools-gt2-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users