Milton Jonathan wrote: > Hey there Andrea > > Thanks for the tip. Found the ShapeFileIndexer main() and ran it. > > By the way, the little program worked like a breeze, very easy to use, > fast and with nice feedback. The normal QIX tree was being generated > with a depth of 10 for my shapefile. I then forced it to generate a tree > with a depth 20, which gave a 64MB QIX file instead of an 8MB one. > > Unfortunately, I got NO performance increase with all that.. :( > > It seems to me that the issue is that, when performing a spatial query, > GeoTools ends up creating a FilteringFeatureReader. And merely asking > featureCollection.isEmpty() leads to a call to reader.hasNext(), which > ends up in the loop at FilteringFeatureReader.java, lines 127-134 - > basically, calling the internal featureReader's next() and checking to > see if the filter applies.
That needs to be done in any case. The QIX index just returns a set of candidate, by the way quadtree indexing works some will lie outside of the requested area. The question is, what is below the filtering feature reader? An indexed reader, or a plain one? I don't have big shapefiles with me now so I cannot check. If you have a sample app with your data and could made them available to me it would speed up looking into this Cheers Andrea ------------------------------------------------------------------------------ Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
