Subject: Re: [boost] new library (space partitioning)
From: Barend Gehrels (barend_at_[hidden])
Date: 2010-08-10 03:35:58
Adam Wulkiewicz wrote:
> Mathias Gaunard wrote:
>> Le 08/08/2010 21:32, Adam Wulkiewicz wrote:
>>> It depends, how you see these things. You may want spatial index or
>>> various spacial indexes in Boost.Geometry. But you may also want
>>> multi-purpose space partitioning containers enclosed in separate
>>> library. It's a matter of view. Where user should search this
>>> functionality for? And for what data should these containers work for?
>> Boost.Geometry works with un-intrusive concepts, and allows to use
>> arbitrary types.
> I'm talking about something different. There are many fields where
> spacial indexes are used. Does user who wants to implement an
> algorithm extracting features from the picture or searching data in
> the database should look for needed data structures somwhere deep in
> the geometry library? Or maby, the geometry library should use
> functionality provided by the space partitioning library (both using
> the same concepts)?
I don't think these are structures deep in the geometry library. It can
be the structures of the users, something in a picture or database.
Which is "adapted" to the Boost.Geometry Point Concept (this is normally
done by one Macro call).
The spatial index could then use the Point Concept of Boost.Geometry,
and both libraries will work together happily.