# Segment tree

In computer science, a **segment tree** also known as a statistic tree is a tree data structure used for storing information about intervals, or segments. It allows querying which of the stored segments contain a given point. It is, in principle, a static structure; that is, it's a structure that cannot be modified once it's built. A similar data structure is the interval tree.

A segment tree for a set I of *n* intervals uses *O*(*n* log *n*) storage and can be built in *O*(*n* log *n*) time. Segment trees support searching for all the intervals that contain a query point in *O*(log *n* + *k*), *k* being the number of retrieved intervals or segments.[1]

Applications of the segment tree are in the areas of computational geometry, and geographic information systems.

The segment tree can be generalized to higher dimension spaces.

## Structure description

*This section describes the structure of a segment tree in a one-dimensional space.*

Let *S* be a set of intervals, or segments. Let *p*_{1}, *p*_{2}, ..., *p _{m}* be the list of distinct interval endpoints, sorted from left to right. Consider the partitioning of the real line induced by those points. The regions of this partitioning are called

*elementary intervals*. Thus, the elementary intervals are, from left to right:

That is, the list of elementary intervals consists of open intervals between two consecutive endpoints *p _{i}* and

*p*

_{i+1}, alternated with closed intervals consisting of a single endpoint. Single points are treated themselves as intervals because the answer to a query is not necessarily the same at the interior of an elementary interval and its endpoints.[2]

Given a set I of intervals, or segments, a segment tree *T* for I is structured as follows:

*T*is a binary tree.- Its leaves correspond to the elementary intervals induced by the endpoints in I, in an ordered way: the leftmost leaf corresponds to the leftmost interval, and so on. The elementary interval corresponding to a leaf
*v*is denoted Int(*v*). - The internal nodes of
*T*correspond to intervals that are the union of elementary intervals: the interval Int(*N*) corresponding to node*N*is the union of the intervals corresponding to the leaves of the tree rooted at*N*. That implies that Int(*N*) is the union of the intervals of its two children. - Each node or leaf
*v*in*T*stores the interval Int(*v*) and a set of intervals, in some data structure. This canonical subset of node*v*contains the intervals [*x*,*x′*] from I such that [*x*,*x′*] contains Int(*v*) and does not contain Int(parent(*v*)). That is, each node in*T*stores the segments that span through its interval, but do not span through the interval of its parent.[3]

## Storage requirements

*This section analyzes the storage cost of a segment tree in a one-dimensional space.*

A segment tree *T* on a set I of *n* intervals uses *O*(*n* log *n*) storage.

** Lemma** — Any interval [

*x*,

*x′*] of I is stored in the canonical set for at most two nodes at the same depth.

**Proof**

Let *v*_{1}, *v*_{2}, *v*_{3} be the three nodes at the same depth, numbered from left to right; and let p(*v*) be the parent node of any given node *v*. Suppose [*x*, *x′*] is stored at *v*_{1} and *v*_{3}. This means that [*x*, *x′*] spans the whole interval from the left endpoint of Int(*v*_{1}) to the right endpoint of Int(*v*_{3}). Note that all segments at a particular level are non-overlapping and ordered from left to right: this is true by construction for the level containing the leaves, and the property is not lost when moving from any level to the one above it by combining pairs of adjacent segments. Now either parent(*v*_{2}) = parent(*v*_{1}), or the former is to the right of the latter (edges in the tree do not cross). In the first case, Int(parent(*v*_{2}))'s leftmost point is the same as Int(*v*_{1})'s leftmost point; in the second case, Int(parent(*v*_{2}))'s leftmost point is to the right of Int(parent(*v*_{1}))'s rightmost point, and therefore also to the right of Int(*v*_{1})'s rightmost point. In both cases, Int(parent(*v*_{2})) begins at or to the right of Int(*v*_{1})'s leftmost point. Similar reasoning shows that Int(parent(*v*_{2})) ends at or to the left of Int(*v*_{3})'s rightmost point. Int(parent(*v*_{2})) must therefore be contained in [*x*, *x′*]; hence, [*x*, *x′*] will not be stored at *v*_{2}.

- The set I has at most 4
*n*+ 1 elementary intervals. Because*T*is a binary balanced tree with at most 4*n*+ 1 leaves, its height is O(log*n*). Since any interval is stored at most twice at a given depth of the tree, that the total amount of storage is*O*(*n*log*n*).[4]

## Construction

*This section describes the construction of a segment tree in a one-dimensional space.*

A segment tree from the set of segments I, can be built as follows. First, the endpoints of the intervals in I are sorted. The elementary intervals are obtained from that. Then, a balanced binary tree is built on the elementary intervals, and for each node *v* it is determined the interval Int(*v*) it represents. It remains to compute the canonical subsets for the nodes. To achieve this, the intervals in I are inserted one by one into the segment tree. An interval *X* = [*x*, *x′*] can be inserted in a subtree rooted at *T*, using the following procedure:[5]

- If Int(
*T*) is contained in*X*then store*X*at*T*, and finish. - Else:
- If
*X*intersects the interval of the left child of*T*, then insert*X*in that child, recursively. - If
*X*intersects the interval of the right child of*T*, then insert*X*in that child, recursively.

- If

The complete construction operation takes *O*(*n* log *n*) time, *n* being the number of segments in I.

**Proof**

- Sorting the endpoints takes
*O*(*n*log*n*). Building a balanced binary tree from the sorted endpoints, takes linear time on*n*. - The insertion of an interval
*X*= [*x*,*x′*] into the tree, costs O(log*n*).

**Proof**

Visiting every node takes constant time (assuming that canonical subsets are stored in a simple data structure like a linked list). When we visit node *v*, we either store *X* at *v*, or Int(*v*) contains an endpoint of *X*. As proved above, an interval is stored at most twice at each level of the tree. There is also at most one node at every level whose corresponding interval contains *x*, and one node whose interval contains *x′*. So, at most four nodes per level are visited. Since there are *O*(log *n*) levels, the total cost of the insertion is *O*(log *n*).[1]

## Query

*This section describes the query operation of a segment tree in a one-dimensional space.*

A query for a segment tree, receives a point *q _{x}*(should be one of the leaves of tree), and retrieves a list of all the segments stored which contain the point

*q*.

_{x}Formally stated; given a node (subtree) *v* and a query point *q _{x}*, the query can be done using the following algorithm:

- Report all the intervals in
*I*(*v*). - If
*v*is not a leaf:- If
*q*is in Int(left child of_{x}*v*) then- Perform a query in the left child of
*v*.

- Perform a query in the left child of
- If
*q*is in Int(right child of_{x}*v*) then- Perform a query in the right child of
*v*.

- Perform a query in the right child of

- If

In a segment tree that contains *n* intervals, those containing a given query point can be reported in *O*(log *n* + *k*) time, where *k* is the number of reported intervals.

**Proof**

The query algorithm visits one node per level of the tree, so *O*(log *n*) nodes in total. On the other hand, at a node *v*, the segments in I are reported in *O*(1 + *k _{v}*) time, where

*k*is the number of intervals at node

_{v}*v*, reported. The sum of all the

*k*for all nodes

_{v}*v*visited, is

*k*, the number of reported segments.[4]

## Generalization for higher dimensions

The segment tree can be generalized to higher dimension spaces, in the form of multi-level segment trees. In higher dimensional versions, the segment tree stores a collection of axis-parallel (hyper-)rectangles, and can retrieve the rectangles that contain a given query point. The structure uses *O*(*n* log^{d} *n*) storage, and answers queries in *O*(log^{d} *n*).

The use of fractional cascading lowers the query time bound by a logarithmic factor. The use of the interval tree on the deepest level of associated structures lowers the storage bound by a logarithmic factor.[6]

## Notes

A query that asks for all the intervals containing a given point is often referred as a *stabbing query*.[7]

The segment tree is less efficient than the interval tree for range queries in one dimension, due to its higher storage requirement: *O*(*n* log *n*) against the O(*n*) of the interval tree. The importance of the segment tree is that the segments within each node’s canonical subset can be stored in any arbitrary manner.[7]

For *n* intervals whose endpoints are in a small integer range (e.g., in the range [1,…,*O*(*n*)]), optimal data structures exist with a linear preprocessing time and query time *O*(1 + *k*) for reporting all *k* intervals containing a given query point.

Another advantage of the segment tree is that it can easily be adapted to counting queries; that is, to report the number of segments containing a given point, instead of reporting the segments themselves. Instead of storing the intervals in the canonical subsets, it can simply store the number of them. Such a segment tree uses linear storage, and requires an *O*(log *n*) query time, so it is optimal.[8]

Higher dimensional versions of the interval tree and the priority search tree do not exist; that is, there is no clear extension of these structures that solves the analogous problem in higher dimensions. But the structures can be used as associated structure of segment trees.[6]

## History

The segment tree was invented by Jon Louis Bentley in 1977; in "Solutions to Klee’s rectangle problems".[7]

## References

- (de Berg et al. 2000, p. 227)
- (de Berg et al. 2000, p. 224)
- (de Berg et al. 2000, pp. 225–226)
- (de Berg et al. 2000, p. 226)
- (de Berg et al. 2000, pp. 226–227)
- (de Berg et al. 2000, p. 230)
- (de Berg et al. 2000, p. 229)
- (de Berg et al. 2000, pp. 229–230)

## Sources cited

- de Berg, Mark; van Kreveld, Marc; Overmars, Mark; Schwarzkopf, Otfried (2000). "More Geometric Data Structures".
*Computational Geometry: algorithms and applications*(2nd ed.). Springer-Verlag Berlin Heidelberg New York. doi:10.1007/978-3-540-77974-2. ISBN 3-540-65620-0. - http://www.cs.nthu.edu.tw/~wkhon/ds/ds10/tutorial/tutorial6.pdf