Hi Adam, First I'm very interested in your library. Is it already uploaded into Vault? Could you publish the URL? If you didn't upload it already, you might consider to use the Boost SVN sandbox instead.
I think that the library I'd like to develop don't fit in Boost.Geometry. The purposes of both are different. Space partitioning (in mathematical meaning), is a separate problem. Functionality like this may be used in library like Boost.Geometry but might be used with a large number of different libraries as well. As I see it, it should be a set of general, n-dimensional solutions. Therefore I think, that it should be a separate library.
I probably agree with this. However, I would like to investigate if a coupling of these two libraries is possible, to provide the users of Boost.Geometry with a good spatial index which works for them by default and which can thus also be used for other purposes. So Boost.Geometry might follow your library, or you might use some concepts of Boost.Geometry, but I would like to see the sources to say more about this. Regards, Barend