# DBSCAN

Machine learning and data mining |
---|

Problems |

Template:Longitem |

Clustering |

Dimensionality reduction |

Structured prediction |

Anomaly detection |

ANN |

Theory |

Template:Navbar |

**Density-based spatial clustering of applications with noise** (**DBSCAN**) is a data clustering algorithm proposed by Martin Ester, Hans-Peter Kriegel, Jörg Sander and Xiaowei Xu in 1996.^{[1]}
It is a density-based clustering algorithm because it finds a number of clusters starting from the estimated density distribution of corresponding nodes. DBSCAN is one of the most common clustering algorithms and also most cited in scientific literature.^{[2]} OPTICS can be seen as a generalization of DBSCAN to multiple ranges, effectively replacing the ε parameter with a maximum search radius.

In 2014, the algorithm was awarded the test of time award (an award given to algorithms which have received substantial attention in theory and practise) at the leading data mining conference, KDD.^{[3]}

## Preliminaries

DBSCAN's definition of a cluster is based on the notion of *density reachability*. Basically, a point is *directly density-reachable* from a point Template:Mvar if it is not farther away than a given distance Template:Mvar (i.e., is part of its Template:Mvar-neighborhood) and if Template:Mvar is surrounded by sufficiently many points such that one may consider Template:Mvar and Template:Mvar to be part of a cluster. is called *density-reachable* (note the distinction from "*directly* density-reachable") from Template:Mvar if there is a sequence of points with and where each is directly density-reachable from .

Note that the relation of density-reachable is not symmetric. Template:Mvar might lie on the edge of a cluster, having insufficiently many neighbors to count as dense itself. This would halt the process of finding a path that stops with the first non-dense point. By contrast, starting the process with *would* lead to Template:Mvar (though the process would halt there, Template:Mvar being the first non-dense point). Due to this asymmetry, the notion of *density-connected* is introduced: two points Template:Mvar and Template:Mvar are density-connected if there is a point Template:Mvar such that both Template:Mvar and Template:Mvar are density-reachable from Template:Mvar. Density-connectedness *is* symmetric.

A cluster, which is a subset of the points of the database, satisfies two properties:

- All points within the cluster are mutually density-connected.
- If a point is density-reachable from any point of the cluster, it is part of the cluster as well.

The variation DBSCAN*^{[4]} does not distinguish border objects and noise objects. Clusters consist of mutually density-connected objects only, which is closer to the statistical interpretation of density connected components. The resulting clustering will, however, usually contain more noise objects.

## Algorithm

DBSCAN requires two parameters: ε (eps) and the minimum number of points required to form a dense regionTemplate:Efn (minPts). It starts with an arbitrary starting point that has not been visited. This point's ε-neighborhood is retrieved, and if it contains sufficiently many points, a cluster is started. Otherwise, the point is labeled as noise. Note that this point might later be found in a sufficiently sized ε-environment of a different point and hence be made part of a cluster.

If a point is found to be a dense part of a cluster, its ε-neighborhood is also part of that cluster. Hence, all points that are found within the ε-neighborhood are added, as is their own ε-neighborhood when they are also dense. This process continues until the density-connected cluster is completely found. Then, a new unvisited point is retrieved and processed, leading to the discovery of a further cluster or noise.

In pseudocode, the algorithm can be expressed as follows:

DBSCAN(D, eps, MinPts) C = 0 for each unvisited point P in dataset D mark P as visited NeighborPts = regionQuery(P, eps) if sizeof(NeighborPts) < MinPts mark P as NOISE else C = next cluster expandCluster(P, NeighborPts, C, eps, MinPts) expandCluster(P, NeighborPts, C, eps, MinPts) add P to cluster C for each point P' in NeighborPts if P' is not visited mark P' as visited NeighborPts' = regionQuery(P', eps) if sizeof(NeighborPts') >= MinPts NeighborPts = NeighborPts joined with NeighborPts' if P' is not yet member of any cluster add P' to cluster C regionQuery(P, eps) return all points within P's eps-neighborhood (including P)

## Complexity

DBSCAN visits each point of the database, possibly multiple times (e.g., as candidates to different clusters). For practical considerations, however, the time complexity is mostly governed by the number of regionQuery invocations. DBSCAN executes exactly one such query for each point, and if an indexing structure is used that executes such a neighborhood query in O(log *n*), an overall runtime complexity of O(*n* log *n*) is obtained. Without the use of an accelerating index structure, the run time complexity is O(*n*²). Often the distance matrix of size (*n*²-*n*)/2 is materialized to avoid distance recomputations. This however also needs O(*n*²) memory, whereas a non-matrix based implementation only needs O(*n*) memory.

## Advantages

- DBSCAN does not require one to specify the number of clusters in the data a priori, as opposed to k-means.
- DBSCAN can find arbitrarily shaped clusters. It can even find a cluster completely surrounded by (but not connected to) a different cluster. Due to the MinPts parameter, the so-called single-link effect (different clusters being connected by a thin line of points) is reduced.
- DBSCAN has a notion of noise, and is robust to outliers.
- DBSCAN requires just two parameters and is mostly insensitive to the ordering of the points in the database. (However, points sitting on the edge of two different clusters might swap cluster membership if the ordering of the points is changed, and the cluster assignment is unique only up to isomorphism.)
- DBSCAN is designed for use with databases that can accelerate region queries, e.g. using an R* tree.

## Disadvantages

- DBSCAN is not entirely deterministic: border points that are reachable from more than one cluster can be part of either cluster. Fortunately, this situation does not arise often, and has little impact on the clustering result: both on core points and noise points, DBSCAN is deterministic. DBSCAN*
^{[4]}is a variation that treats border points as noise, and this way achieves a fully deterministic result as well as a more consistent statistical interpretation of density-connected components. - The quality of DBSCAN depends on the distance measure used in the function regionQuery(P,ε). The most common distance metric used is Euclidean distance. Especially for high-dimensional data, this metric can be rendered almost useless due to the so-called "Curse of dimensionality", making it difficult to find an appropriate value for ε. This effect, however, is also present in any other algorithm based on Euclidean distance.
- DBSCAN cannot cluster data sets well with large differences in densities, since the minPts-ε combination cannot then be chosen appropriately for all clusters.

See the section below on extensions for algorithmic modifications to handle these issues.

## Parameter estimation

Every data mining task has the problem of parameters. Every parameter influences the algorithm in specific ways. For DBSCAN, the parameters ε and *minPts* are needed. The parameters must be specified by the user. Ideally, the value of ε is given by the problem to solve (e.g. a physical distance), and *minPts* is then the desired minimum cluster size.Template:Efn

*MinPts*: As a rule of thumb, a minimum*minPts*can be derived from the number of dimensions*D*in the data set, as*minPts≥D+1*. The low value of*minPts=1*does not make sense, as then every point on its own will already be a cluster. With*minPts=2*, the result will be the same as of hierarchical clustering with the single link metric, with the dendrogram cut at height ε. However, larger values are usually better for data sets with noise and will yield more significant clusters. The larger the data set, the larger the value of*minPts*should be chosen.- ε: The value for ε can then be chosen by using a k-distance graph, plotting the distance to the
*k=minPts*nearest neighbor. Good values of ε are where this plot shows a strong bend: if ε is chosen too small, a large part of the data will not be clustered; whereas for a too high value of ε, clusters will merge and the majority of objects will be in the same cluster.

OPTICS can be seen as a generalization of DBSCAN that replaces the ε parameter with a maximum value that mostly affects performance. *MinPts* then essentially becomes the minimum cluster size to find. While the algorithm is much easier to parameterize than DBSCAN, the results are a bit more difficult to use, as it will usually produce a hierarchical clustering instead of the simple data partitioning that DBSCAN produces.

Recently, one of the original authors of DBSCAN has revisited DBSCAN and OPTICS, and published a refined version of hierarchical DBSCAN (HDBSCAN*),^{[4]}^{[5]} which no longer has the notion of border points.

## Extensions

Generalized DBSCAN (GDBSCAN)^{[6]}^{[7]} is a generalization by the same authors to arbitrary "neighborhood" and "dense" predicates. The ε and minpts parameters are removed from the original algorithm and moved to the predicates. For example on polygon data, the "neighborhood" could be any intersecting polygon, whereas the density predicate uses the polygon areas instead of just the object count.

Various extensions to the DBSCAN algorithm have been proposed, including methods for parallelization, parameter estimation and support for uncertain data. The basic idea has been extended to hierarchical clustering by the OPTICS algorithm. DBSCAN is also used as part of subspace clustering algorithms like PreDeCon and SUBCLU. HDBSCAN^{[4]} is a hierarchical version of DBSCAN which is also faster than OPTICS, from which a flat partition consisting of most prominent clusters can be extracted from the hierarchy.^{[5]}

## Availability

An implementation of DBSCAN as well as GDBSCAN and other variants are available in the ELKI framework. This implementation can use various index structures for sub-quadratic runtime and supports various distance functions and arbitrary data types, but it may be outperformed by low-level optimized (and specialized) implementations on small data sets. The implementation of the HDBSCAN is made available by the authors.

scikit-learn includes a Python implementation of DBSCAN for arbitrary Minkowski metrics, which can be accelerated using kd-trees and ball trees.

GNU R contains DBSCAN in the "fpc" package with support for arbitrary distance functions via distance matrices. However it does not have index support (and thus has quadratic runtime and memory complexity).

Weka contains (as an optional package in latest versions) a basic implementation of DBSCAN that run in quadratic time and linear memory.

## Notes

## References

- ↑ {{#invoke:citation/CS1|citation |CitationClass=conference }}
- ↑ [1] Most cited data mining articles according to Microsoft academic search; DBSCAN is on rank 24, when accessed on: 4/18/2010
- ↑ Template:Cite web
- ↑
^{4.0}^{4.1}^{4.2}^{4.3}Template:Cite doi - ↑
^{5.0}^{5.1}Template:Cite doi - ↑ {{#invoke:Citation/CS1|citation |CitationClass=journal }}
- ↑ {{#invoke:citation/CS1|citation |CitationClass=book }}

### Further reading

- {{#invoke:citation/CS1|citation

|CitationClass=conference }}

- {{#invoke:Citation/CS1|citation

|CitationClass=journal }}