# Approximate string matching

In computer science, **approximate string matching** (often colloquially referred to as **fuzzy string searching**) is the technique of finding strings that match a pattern approximately (rather than exactly). The problem of approximate string matching is typically divided into two sub-problems: finding approximate substring matches inside a given string and finding dictionary strings that match the pattern approximately.

## Overview

The closeness of a match is measured in terms of the number of primitive operations necessary to convert the string into an exact match. This number is called the edit distance between the string and the pattern. The usual primitive operations are:^{}

- insertion:
*cot*→*co***a**t - deletion:
*co*→**a**t*cot* - substitution:
*co*→**a**t*co***s**t

These three operations may be generalized as forms of substitution by adding a NULL character (here symbolized by *) wherever a character has been deleted or inserted:

- insertion:
*co*→*****t*co***a**t - deletion:
*co*→**a**t*co******t - substitution:
*co*→**a**t*co***s**t

Some approximate matchers also treat *transposition*, in which the positions of two letters in the string are swapped, to be a primitive operation.^{}

- transposition:
*co*→**st***co***ts**

Different approximate matchers impose different constraints. Some matchers use a single global unweighted cost, that is, the total number of primitive operations necessary to convert the match to the pattern. For example, if the pattern is *coil*, *foil* differs by one substitution, *coils* by one insertion, *oil* by one deletion, and *foal* by two substitutions. If all operations count as a single unit of cost and the limit is set to one, *foil*, *coils*, and *oil* will count as matches while *foal* will not.

Other matchers specify the number of operations of each type separately, while still others set a total cost but allow different weights to be assigned to different operations. Some matchers permit separate assignments of limits and weights to individual groups in the pattern.

## Problem formulation and algorithms

One possible definition of the approximate string matching problem is the following: Given a pattern string and a text string , find a substring in *T*, which, of all substrings of *T*, has the smallest edit distance to the pattern *P*.

A brute-force approach would be to compute the edit distance to P for all substrings of T, and then choose the substring with the minimum distance. However, this algorithm would have the running time *O*(*n*^{3} *m*).

A better solution, which was proposed by Sellers^{}, relies on dynamic programming. It uses an alternative formulation of the problem: for each position *j* in the text *T* and each position *i* in the pattern *P*, compute the minimum edit distance between the *i* first characters of the pattern, , and any substring of *T* that ends at position *j*.

For each position *j* in the text *T*, and each position *i* in the pattern *P*, go through all substrings of *T* ending at position *j*, and determine which one of them has the minimal
edit distance to the *i* first characters of the pattern *P*. Write this minimal distance as *E*(*i*, *j*). After computing *E*(*i*, *j*) for all *i* and *j*, we can easily find a solution to the original problem: it is the substring for which *E*(*m*, *j*) is minimal (*m* being the length of the pattern *P*.)

Computing *E*(*m*, *j*) is very similar to computing the edit distance between two strings. In fact, we can use the Levenshtein distance computing algorithm for *E*(*m*, *j*), the only difference being that we must initialize the first row with zeros, and save the path of computation, that is, whether we used *E*(*i* − 1,*j*), E(*i*,*j* − 1) or *E*(*i* − 1,*j* − 1) in computing *E*(*i*, *j*).

In the array containing the *E*(*x*, *y*) values, we then choose the minimal value in the last row, let it be *E*(*x*_{2}, *y*_{2}), and follow the path of computation backwards, back to the row number 0. If the field we arrived at was *E*(0, *y*_{1}), then *T*[*y*_{1} + 1] ... *T*[*y*_{2}] is a substring of T with the minimal edit distance to the pattern *P*.

Computing the *E*(*x*, *y*) array takes *O*(*mn*) time with the dynamic programming algorithm, while the backwards-working phase takes *O*(*n* + *m*) time.

Another recent idea is the similarity join. When matching database relates to a large scale of data, the *O*(*mn*) time with the dynamic programming algorithm cannot work within a limited time. So, the idea is, instead of computing the similarity of *all* pairs of strings, to reduce the number of candidate pairs. Widely used algorithms are based on filter-verification, hashing, Locality-sensitive hashing (LSH), Tries and other greedy and approximation algorithms. Most of them are designed to fit some framework (such as Map-Reduce) to compute concurrently.

## On-line versus off-line

Traditionally, approximate string matching algorithms are classified into two categories: on-line and off-line. With on-line algorithms the pattern can be processed before searching but the text cannot. In other words, on-line techniques do searching without an index. Early algorithms for on-line approximate matching were suggested by Wagner and Fisher^{} and by Sellers^{}. Both algorithms are based on dynamic programming but solve different problems. Sellers' algorithm searches approximately for a substring in a text while the algorithm of Wagner and Fisher calculates Levenshtein distance, being appropriate for dictionary fuzzy search only.

On-line searching techniques have been repeatedly improved. Perhaps the most
famous improvement is the bitap algorithm (also known as the shift-or and shift-and algorithm), which is very efficient for relatively short pattern strings. The Bitap algorithm is the heart of the Unix searching utility agrep. A review of on-line searching algorithms was done by G. Navarro.^{}

Although very fast on-line techniques exist, their performance on large data is unacceptable.
Text preprocessing or indexing makes searching dramatically faster.
Today, a variety of indexing algorithms have been presented. Among them are suffix trees^{}, metric trees^{} and n-gram methods.^{}^{}
A detailed survey of indexing techniques that allows one to find an arbitrary substring in a text is given by Navarro *et al.*^{} A computational survey of dictionary methods (i.e., methods that permit finding all dictionary words that approximately match a search pattern) is given by Boytsov^{}.

## Applications

Common applications of approximate matching include spell checking.^{} With the availability of large amounts of DNA data, matching of nucleotide sequences has become an important application.^{} Approximate matching is also used in spam filtering.^{} Record linkage is a common application where records from two disparate databases are matched.

String matching cannot be used for most binary data, such as images and music. They require different algorithms, such as acoustic fingerprinting.

## See also

## References

**^**Baeza-Yates, R.; Navarro, G. (June 1996). "A faster algorithm for approximate string matching". In Dan Hirchsberg; Gene Myers (eds.).*Combinatorial Pattern Matching (CPM'96), LNCS 1075*. Irvine, CA. pp. 1–23. CiteSeerX 10.1.1.42.1593.**^**Baeza-Yates, R.; Navarro, G. "Fast Approximate String Matching in a Dictionary" (PDF).*Proc. SPIRE'98*. IEEE CS Press. pp. 14–22.**^**Boytsov, Leonid (2011). "Indexing methods for approximate dictionary searching: Comparative analysis".*Journal of Experimental Algorithmics*.**16**(1): 1–91. doi:10.1145/1963190.1963191.**^**Cormen, Thomas; Leiserson, Rivest (2001).*Introduction to Algorithms*(2nd ed.). MIT Press. pp. 364–7. ISBN 978-0-262-03293-3.**^**Galil, Zvi; Apostolico, Alberto (1997).*Pattern matching algorithms*. Oxford [Oxfordshire]: Oxford University Press. ISBN 978-0-19-511367-9.**^**Gusfield, Dan (1997).*Algorithms on strings, trees, and sequences: computer science and computational biology*. Cambridge, UK: Cambridge University Press. ISBN 978-0-521-58519-4.**^**Myers, G. (May 1999). "A fast bit-vector algorithm for approximate string matching based on dynamic programming" (PDF).*Journal of the ACM*.**46**(3): 395–415. doi:10.1145/316542.316550.*ACM Computing Surveys*.**33**(1): 31–88. CiteSeerX 10.1.1.96.7225. doi:10.1145/375360.375365.
Navarro, Gonzalo (2001). "A guided tour to approximate string matching". **^**Navarro, Gonzalo; Baeza-Yates, Ricardo; Sutinen, Erkki; Tarhio, Jorma (2001). "Indexing Methods for Approximate String Matching" (PDF).*IEEE Data Engineering Bulletin*.**24**(4): 19–27.**^**Sellers, Peter H. (1980). "The Theory and Computation of Evolutionary Distances: Pattern Recognition".*Journal of Algorithms*.**1**(4): 359–73. doi:10.1016/0196-6774(80)90016-4.**^**Skiena, Steve (1998).*Algorithm Design Manual*(1st ed.). Springer. ISBN 978-0-387-94860-7.**^**Ukkonen, E. (1985). "Algorithms for approximate string matching".*Information and Control*.**64**(1–3): 100–18. doi:10.1016/S0019-9958(85)80046-2.**^**Wagner, R.; Fischer, M. (1974). "The string-to-string correction problem".*Journal of the ACM*.**21**: 168–73. doi:10.1145/321796.321811.**^**Zobel, Justin; Dart, Philip (1995). "Finding approximate matches in large lexicons".*Software-Practice & Experience*.**25**(3): 331–345. CiteSeerX 10.1.1.14.3856. doi:10.1002/spe.4380250307.

## External links

- Flamingo Project
- Efficient Similarity Query Processing Project with recent advances in approximate string matching based on an edit distance threshold.
- StringMetric project a Scala library of string metrics and phonetic algorithms
- Natural project a JavaScript natural language processing library which includes implementations of popular string metrics