Hello all, The javadocs for FeatureReader (http://docs.geotools.org/latest/javadocs/org/geotools/data/FeatureReader.html) include this note which I assume is ancient history:
"Q: Can we include skip(int) - SeanG A: The order of the contents is not "known" or predicatable to the end user, so skip( int ) would be useless. For random access (a higher order of abstraction then FeatureReader) please look at FeatureList." This caught my attention because I'm presently looking at the gt-swing FeatureCollectionTableModel class, used with a JTable. The current code loads all features into memory, which is fine for tutorial use but not for much else. It would be nice to have paging behaviour so that, for example, given a shapefile with a gazillion features the table only loads and caches a few hundred centred on the current JTable view. The Swing table model side of this straightforward, but while experimenting with it's become obvious that I don't know enough about the GeoTools DataStore / FeatureSource / FeatureCollection API. Is it possible to do sequential access of features from random start points at a high level in the API, or does that require dealing with the specifics of each type of DataStore ? Michael ------------------------------------------------------------------------------ The demand for IT networking professionals continues to grow, and the demand for specialized networking skills is growing even more rapidly. Take a complimentary Learning@Cisco Self-Assessment and learn about Cisco certifications, training, and career opportunities. http://p.sf.net/sfu/cisco-dev2dev _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
