> As a result, and to my surprise, I found we can sort on geometries
> as well, since they implement Comparable.
lol - that was un expected.
> This means that if someone has a very large dataset in a DBMS
> and sorting on the geometry is requested, we'll end up dumping everything
> to file and perform the merge-sort... ugh... probably not a good idea?
>
> I'm inclined to treat geometry as a special case and declare we cannot
> actually sort on it, what do you think?
I am trying to sort out what sorting on geometry means? Would that end up being
kind of like a spatial index? Suppose I would need to look what the geometry
compare does.
The case I have in mind for this functionality is simply as a backup plan for
to allow a general case FeatureCollection.sort method to work - so that we can
do a good dissolve. Avoiding sorting geometry will not effect this case one way
or another.
If I understand your statement earlier; for the DBMS case the sorting would be
done by the database and the case you describe would not come up?
Jody
------------------------------------------------------------------------------
Special Offer -- Download ArcSight Logger for FREE!
Finally, a world-class log management solution at an even better
price-free! And you'll get a free "Love Thy Logs" t-shirt when you
download Logger. Secure your free ArcSight Logger TODAY!
http://p.sf.net/sfu/arcsisghtdev2dev
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
