Andrea Aime wrote: > I have the exactly opposite impression? FeatureCollection is confusing > and breaks normal way of doing things, FeatureReader and Writer and > simple and straightforward. Having to throw runtime exceptions because > you had an internal probelm in an iterator is what I call error prone > and hard to deal with. You expect it to be a normal collection, then > it starts throwing exception here and there. It could be Collection is not the right fit, Bryce and Justin were working through that and I am waiting to see what comes of it. What FeatureCollection represents however is spot on and much easier to both use and develop against. > I do... I'm not interested in FeatureCollection at the moment, find it > confusing and out of place, can't we have a wrapping mechanism so that > your collections call that method when they need a sorter writer? I am trying take away the wrappings and make the collections the real implementation, so far everything seemed a lot more straight forward when done this way. As opposed to nested decorators of the single use FeatureReader classes, we ended up with nested multi use FeatureCollection classes each one of which accounted for multiple use, feature type (schema) and iterator<feature> (data access) and a few metadata things (count, bounds).
Since each on of these ideas gets mangled when doing a transformation, and must be accounted for, having the accounting for each transformation all done in a single class made things much easier to understand. And also easier to optimize. > Well, I'd really like to have that one as an addition to the DataStore > interface, although it breaks compatibility. Maybe as a subinterface? Provide it in your implementation, make it available via the previously mentioned call. I really want a FeatureList implementation that is good, and specific to your DataStore. > I see. I'll keep on using my loved feature readers :-p > No suprises, no hidden costs... Andrea there are also FeatureReader / FeatureWriter implementations that wrap over and around a normal Iterator (so costs are always hidden on you by the implementor of a DataStore). I for one and am not writing a FeatureReader/FeatureWriter again ... trying to actually use what is there and make it good :-D Jody ------------------------------------------------------------------------- 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-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
