mirror of
https://github.com/boostorg/geometry.git
synced 2026-02-13 00:22:10 +00:00
259 lines
8.3 KiB
XML
259 lines
8.3 KiB
XML
<?xml version="1.0" encoding="utf-8"?>
|
|
<!DOCTYPE library PUBLIC "-//Boost//DTD BoostBook XML V1.0//EN"
|
|
"http://www.boost.org/tools/boostbook/dtd/boostbook.dtd">
|
|
<library name="Geometry.Index" dirname="index" id="index"
|
|
xmlns:xi="http://www.w3.org/2001/XInclude">
|
|
<libraryinfo>
|
|
<author>
|
|
<firstname>Federico J.</firstname>
|
|
<surname>Fernandez</surname>
|
|
</author>
|
|
<author>
|
|
<firstname>Adam</firstname>
|
|
<surname>Wulkiewicz</surname>
|
|
</author>
|
|
|
|
<copyright>
|
|
<year>2008</year>
|
|
<holder>Federico J. Fernandez</holder>
|
|
</copyright>
|
|
<copyright>
|
|
<year>2011</year>
|
|
<holder>Adam Wulkiewicz</holder>
|
|
</copyright>
|
|
|
|
<legalnotice>
|
|
<para>Use, modification and distribution is subject to the Boost
|
|
Software License, Version 1.0. (See accompanying file
|
|
<filename>LICENSE_1_0.txt</filename> or copy at <ulink
|
|
url="http://www.boost.org/LICENSE_1_0.txt">http://www.boost.org/LICENSE_1_0.txt</ulink>)</para>
|
|
</legalnotice>
|
|
|
|
<librarypurpose>Spatial indexes for faster spatial and knn queries.</librarypurpose>
|
|
<librarycategory name="category:data-structures"/>
|
|
</libraryinfo>
|
|
|
|
<title>Boost.Geometry.Index</title>
|
|
|
|
<section id="index.intro">
|
|
<title>Introduction</title>
|
|
<para>The Boost.Geometry.Index library is intetended to gather containers
|
|
(spatial indexes) used for speeding spatial queries up. In general, indexes
|
|
stores geometric objects' representations and allows searching for objects
|
|
occupying some space or close to some point in space.
|
|
</para>
|
|
|
|
<para>Currently, only one spatial index is implemented - the R-tree.</para>
|
|
</section>
|
|
|
|
<section id="index.rtree">
|
|
<title>R-tree</title>
|
|
<para>
|
|
R-tree is a self-balancing search tree with nodes stored with their axis aligned
|
|
bounding boxes. Each node's box describes the space occupied by children nodes.
|
|
At the bottom of the structure, there are leaf-nodes which contains values
|
|
(geometric objects representations). Minimal and maximal numbers of values/children
|
|
which may be stored inside the node are user defined.
|
|
</para>
|
|
|
|
<section>
|
|
<title>R-tree creation</title>
|
|
<para>
|
|
R-tree has 4 parameters:
|
|
<programlisting>
|
|
rtree<Value, Parameters, Translator, Allocator>
|
|
</programlisting>
|
|
<itemizedlist>
|
|
<listitem>
|
|
<code>Value</code> - type of object which will be stored in the container.
|
|
</listitem>
|
|
<listitem>
|
|
<code>Parameters</code> - compile-time parameters, e.g. inserting/splitting algorithm with min and max nodes' elements numbers.
|
|
</listitem>
|
|
<listitem>
|
|
<code>Translator</code> - type of object translating Value objects to Indexable objects (<code>Point</code> or <code>Box</code>) which R-tree can handle.
|
|
</listitem>
|
|
<listitem>
|
|
<code>Allocator</code> - the allocator.
|
|
</listitem>
|
|
</itemizedlist>
|
|
</para>
|
|
<para>
|
|
In order to create a R-tree object storing values of type <code>std::pair<Box, int></code> one may use the following code
|
|
<programlisting>
|
|
using namespace boost::geometry;
|
|
typedef std::pair<Box, int> Value;
|
|
index::rtree< Value, index::quadratic<32, 8> > rt;
|
|
</programlisting>
|
|
</para>
|
|
</section>
|
|
|
|
<section>
|
|
<title>Values, Indexables and default Translator</title>
|
|
<para>
|
|
R-tree may store Values of any type as long as there is passed the Translator which knows how to interpret
|
|
those Values and extract an object understandable by the R-tree. Those objects are called Indexables
|
|
and they are simply of type adapted to Point or Box concept. Default translator
|
|
<code>index::translator::def<Value></code> is able to handle <code>Point</code>, <code>Box</code>,
|
|
<code>std::pair<...></code>, pointer, iterator or smart pointer.
|
|
<itemizedlist>
|
|
<listitem><code>Indexable = Point | Box</code></listitem>
|
|
<listitem><code>BasicValue = Indexable | std::pair<Indexable, T> | std::pair<T, Indexable></code></listitem>
|
|
<listitem><code>Value = BasicValue | BasicValue* | Iterator<BasicValue> | SmartPtr<BasicValue></code></listitem>
|
|
</itemizedlist>
|
|
Examples of Value types:
|
|
<itemizedlist>
|
|
<listitem><code>geometry::model::point<...></code></listitem>
|
|
<listitem><code>geometry::model::point_xy<...></code></listitem>
|
|
<listitem><code>geometry::model::box<...></code></listitem>
|
|
<listitem><code>std::pair<geometry::model::box<...>, size_t></code></listitem>
|
|
</itemizedlist>
|
|
</para>
|
|
</section>
|
|
|
|
<section>
|
|
<title>Inserting and splitting algorithms</title>
|
|
<para>
|
|
Values may be inserted to the R-tree in many various ways. Final structure of nodes depends
|
|
on algorithms used in the process, especially nodes' splitting algorithm. Currently, three
|
|
well-known types of R-trees may be created.
|
|
<itemizedlist>
|
|
<listitem>
|
|
Linear - classic R-tree using splitting algorithm of linear complexity
|
|
<programlisting>
|
|
index::rtree< Value, index::linear<32, 8> > rt;
|
|
</programlisting>
|
|
</listitem>
|
|
<listitem>
|
|
Quadratic - classic R-tree using splitting algorithm of quadratic complexity
|
|
<programlisting>
|
|
index::rtree< Value, index::quadratic<32, 8> > rt;
|
|
</programlisting>
|
|
</listitem>
|
|
<listitem>
|
|
R*-tree - splitting algorithm minimizing nodes' overlap with forced reinsertions
|
|
<programlisting>
|
|
index::rtree< Value, index::rstar<32, 8> > rt;
|
|
</programlisting>
|
|
</listitem>
|
|
</itemizedlist>
|
|
</para>
|
|
</section>
|
|
|
|
<section>
|
|
<title>Inserting and removing Values</title>
|
|
<para>
|
|
Create
|
|
<programlisting>
|
|
using namespace boost::geometry;
|
|
typedef std::pair<Box, int> Value;
|
|
index::rtree< Value, index::quadratic<32, 8> > rt;
|
|
</programlisting>
|
|
Insert and remove by method call
|
|
<programlisting>
|
|
Value v = std::make_pair(Box(...), 0);
|
|
rt.insert(v);
|
|
rt.remove(v);
|
|
</programlisting>
|
|
or by function call
|
|
<programlisting>
|
|
Value v = std::make_pair(Box(...), 0);
|
|
index::insert(rt, v);
|
|
index::remove(rt, v);
|
|
</programlisting>
|
|
</para>
|
|
</section>
|
|
|
|
<section>
|
|
<title>Spatial queries</title>
|
|
<para>
|
|
There are three ways to perform a spatial query. Following queries returns
|
|
Values intersecting some box_region.
|
|
<itemizedlist>
|
|
<listitem>
|
|
Method call
|
|
<programlisting>
|
|
std::vector<Value> returned_values;
|
|
Box box_region(...);
|
|
rt.query(box_region, std::back_inserter(returned_values));
|
|
</programlisting>
|
|
</listitem>
|
|
<listitem>
|
|
Function call
|
|
<programlisting>
|
|
std::vector<Value> returned_values;
|
|
Box box_region(...);
|
|
index::query(rt, box_region, std::back_inserter(returned_values));
|
|
</programlisting>
|
|
</listitem>
|
|
<listitem>
|
|
Use of <code>operator |</code> (as with ranges)
|
|
<programlisting>
|
|
Box box_region(...);
|
|
BOOST_FOREACH(Value &v, rt | index::query_filtered(box_region))
|
|
;// do something with v
|
|
</programlisting>
|
|
</listitem>
|
|
</itemizedlist>
|
|
</para>
|
|
</section>
|
|
|
|
<section>
|
|
<title>Spatial predicates</title>
|
|
<para>
|
|
It is possible to define other relations between queried Values and region/regions
|
|
of interest. Names of predicates corresponds to names of Boost.Geometry algorithms.
|
|
<programlisting>
|
|
rt.query(box, std::back_inserter(result)); // default case - intersects
|
|
rt.query(index::intersects(box), std::back_inserter(result)); // same as default
|
|
rt.query(index::covered_by(box), std::back_inserter(result));
|
|
rt.query(index::disjont(box), std::back_inserter(result));
|
|
rt.query(index::overlaps(box), std::back_inserter(result));
|
|
rt.query(index::within(box), std::back_inserter(result));
|
|
</programlisting>
|
|
All predicates may be negated, e.g.:
|
|
<programlisting>
|
|
rt.query(index::not_intersects(box), std::back_inserter(result));
|
|
// or
|
|
rt.query(!index::intersects(box), std::back_inserter(result));
|
|
// the same as
|
|
rt.query(index::disjoint(box), std::back_inserter(result));
|
|
</programlisting>
|
|
It's possible to use some number of predicates by passing <code>std::pair<Pred1, Pred2></code>
|
|
<programlisting>
|
|
rt.query(
|
|
std::make_pair(index::intersects(box1), !index::within(box2))
|
|
, std::back_inserter(result));
|
|
</programlisting>
|
|
or <code>boost::tuple<Pred1, Pred2, Pred3, ...></code>
|
|
<programlisting>
|
|
rt.query(
|
|
boost::make_tuple(index::intersects(box1), !index::within(box2), index::overlaps(box3))
|
|
, std::back_inserter(result));
|
|
</programlisting>
|
|
There is special predicate <code>index::value(Fun)</code> taking user-defined function/functor
|
|
which checks if Value should be returned by the query.
|
|
<programlisting>
|
|
bool fun(Value const& v)
|
|
{
|
|
return v.is_red();
|
|
}
|
|
|
|
// ...
|
|
|
|
rt.query(
|
|
boost::make_pair(index::intersects(box), index::value(fun))
|
|
, std::back_inserter(result));
|
|
</programlisting>
|
|
</para>
|
|
</section>
|
|
|
|
<section>
|
|
<title>Nearest neighbor queries</title>
|
|
TODO
|
|
</section>
|
|
|
|
</section>
|
|
|
|
</library>
|