At some point should we rewrite the ESRI Shapefile I/O code in OpenJUMP to provide an indexed FeatureCollection by default? I'm thinking this could be used to speed up rendering of Layers, and I know it would speed up my processing of object snaps in the new CursorTool stuff.
Has this already been done? If not, would there be any serious performance penalties for making this change? I'm just curious as I was looking at the Quadtree class in JTS this morning. (I'll be working with the ESRI Shapefile code from GeoTools or Deegree as part of the FeatureCache. I don't think it would be too much of a stretch to revamp the "regular" Shapefile driver in OpenJUMP while I am at it. If I do this I could make the change described above.) Thanks for the thoughts. The Sunburned Surveyor ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
