Hello there I was playing around with a bigger shapefile (200MB for the .shp, 815MB for all files), made of lots of small features for streets and roads.
First of all, rendering is quite good and fast, congratulations (and poor ArcExplorer couldn't even open it!). But for other operations that's not quite the case. I attempted to query the FeatureSource with a spatial filter, and wanted to know if it intersected anything. For shapefiles 10 times smaller, it works like a breeze. However, for the big one, it is still quite fast if the query envelope is big (covers most of the features in the shapefile), but absurdly slow if it covers only a handful of features. My guess is that this is related to the .qix quad-tree index. I read Andrea's comments when fixing the memory issues in index generation ( http://jira.codehaus.org/browse/GEOT-1498), and I think it may be the reason (by the way, it's now quite fast and with a very low memory footprint, congratulations again!). So, maybe creating a deeper tree would solve this? Andrea, you mentioned that the "command line tool is still available". Could you explain how to get it? Thanks again Milton -- Milton Jonathan Grupo GIS e Meio Ambiente Tecgraf/PUC-Rio Tel: +55-21-3527-2502 ------------------------------------------------------------------------------ Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
