The RTree in principle should be generalizable, but the current implementation in neo4j-spatial does make a few assumptions specific to spatial data, and makes use of spatial envelopes for the tree node bounding boxes. It is also specific to 2D. We could make a few improvements first, like generalizing to n-dimensions, replacing the recursive search with a traverser and generalizing the bounding boxes to be simple double-arrays. Then the only thing left would be to decide if it is ok for it to be based on n-dim doubles or should be generalized to more types.
On Tue, Jun 28, 2011 at 11:14 PM, Saikat Kanjilal <sxk1...@hotmail.com>wrote: > I would be interested in helping out with this, let me know next steps. > > Sent from my iPhone > > On Jun 28, 2011, at 8:49 AM, Niels Hoogeveen <pd_aficion...@hotmail.com> > wrote: > > > > > A couple of weeks ago Peter Neubauer set up a repository for in-graph > datastructures: https://github.com/peterneubauer/graph-collections. > > At this time of writing only the Btree/Timeline index is part of this > "component". > > In my opinion it would be interesting to move the Rtree parts of > neo-spatial to neo4j-graph-collections too. > > I looked at the code but don't feel competent to seperate out those > classes that support generic Rtrees from those classes that are clearly > spatial related. > > Is there any enthusiasm for such a project and if so, who is willing and > able to do this? > > Niels > > > > > > > > _______________________________________________ > > Neo4j mailing list > > User@lists.neo4j.org > > https://lists.neo4j.org/mailman/listinfo/user > > > _______________________________________________ > Neo4j mailing list > User@lists.neo4j.org > https://lists.neo4j.org/mailman/listinfo/user > _______________________________________________ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user
