Levenshtein distance

In information theory, linguistics, and computer science, the Levenshtein distance is a string metric for measuring the difference between two sequences. Informally, the Levenshtein distance between two words is the minimum number of single-character edits (insertions, deletions or substitutions) required to change one word into the other. It is named after the Soviet mathematician Vladimir Levenshtein, who considered this distance in 1965.

Levenshtein distance may also be referred to as ''edit distance'', although that term may also denote a larger family of distance metrics known collectively as edit distance. It is closely related to pairwise string alignments.

Definition

The Levenshtein distance between two strings $a, b$ (of length $, a,$ and $, b,$ respectively) is given by $\operatorname(a, b)$ where

: \operatorname(a, b) = \begin
, a, & \text , b, = 0, \\
, b, & \text , a, = 0, \\
\operatorname\big(\operatorname(a),\operatorname(b)\big) & \text a = b \\
1 + \min \begin
\operatorname\big(\operatorname(a), b\big) \\
\operatorname\big(a, \operatorname(b)\big) \\
\operatorname\big(\operatorname(a), \operatorname(b)\big) \\
\end & \text
\end
where the $\operatorname$ of some string $x$ is a string of all but the first character of $x$, and x /math> is the $n$th character of the string $x$, counting from 0.

Note that the first element in the minimum corresponds to deletion (from $a$ to $b$), the second to insertion and the third to replacement.

This definition corresponds directly to the naive recursive implementation.

Example

For example, the Levenshtein distance between "kitten" and "sitting" is 3, since the following 3 edits change one into the other, and there is no way to do it with fewer than 3 edits:
# kitten → sitten (substitution of "s" for "k"),
# sitten → sittin (substitution of "i" for "e"),
# sittin → sitting (insertion of "g" at the end).

Upper and lower bounds

The Levenshtein distance has several simple upper and lower bounds. These include:
* It is at least the absolute value of the difference of the sizes of the two strings.
* It is at most the length of the longer string.
* It is zero if and only if the strings are equal.
* If the strings have the same size, the Hamming distance is an upper bound on the Levenshtein distance. The Hamming distance is the number of positions at which the corresponding symbols in the two strings are different.
* The Levenshtein distance between two strings is no greater than the sum of their Levenshtein distances from a third string (triangle inequality).

An example where the Levenshtein distance between two strings of the same length is strictly less than the Hamming distance is given by the pair "flaw" and "lawn". Here the Levenshtein distance equals 2 (delete "f" from the front; insert "n" at the end). The Hamming distance is 4.

Applications

In approximate string matching, the objective is to find matches for short strings in many longer texts, in situations where a small number of differences is to be expected. The short strings could come from a dictionary, for instance. Here, one of the strings is typically short, while the other is arbitrarily long. This has a wide range of applications, for instance, spell checkers, correction systems for optical character recognition, and software to assist natural-language translation based on translation memory.

The Levenshtein distance can also be computed between two longer strings, but the cost to compute it, which is roughly proportional to the product of the two string lengths, makes this impractical. Thus, when used to aid in fuzzy string searching in applications such as record linkage, the compared strings are usually short to help improve speed of comparisons.

In linguistics, the Levenshtein distance is used as a metric to quantify the linguistic distance, or how different two languages are from one another.. It is related to mutual intelligibility: the higher the linguistic distance, the lower the mutual intelligibility, and the lower the linguistic distance, the higher the mutual intelligibility.

Relationship with other edit distance metrics

There are other popular measures of edit distance, which are calculated using a different set of allowable edit operations. For instance,
* the Damerau–Levenshtein distance allows the transposition of two adjacent characters alongside insertion, deletion, substitution;
* the longest common subsequence (LCS) distance allows only insertion and deletion, not substitution;
* the Hamming distance allows only substitution, hence, it only applies to strings of the same length.
* the Jaro distance allows only transposition.

Edit distance is usually defined as a parameterizable metric calculated with a specific set of allowed edit operations, and each operation is assigned a cost (possibly infinite). This is further generalized by DNA sequence alignment algorithms such as the Smith–Waterman algorithm, which make an operation's cost depend on where it is applied.

Computation

Recursive

This is a straightforward, but inefficient, recursive Haskell implementation of a lDistance function that takes two strings, ''s'' and ''t'', together with their lengths, and returns the Levenshtein distance between them:

lDistance :: Eq a => -> -> Int
lDistance [] t = length t -- If s is empty, the distance is the number of characters in t
lDistance s [] = length s -- If t is empty, the distance is the number of characters in s
lDistance (a : s') (b : t') =
if a

b
then lDistance s' t' -- If the first characters are the same, they can be ignored
else
1
+ minimum -- Otherwise try all three possible actions and select the best one
[ lDistance (a : s') t', -- Character is inserted (b inserted)
lDistance s' (b : t'), -- Character is deleted (a deleted)
lDistance s' t' -- Character is replaced (a replaced with b)
]

This implementation is very inefficient because it recomputes the Levenshtein distance of the same substrings many times.

A more efficient method would never repeat the same distance calculation. For example, the Levenshtein distance of all possible suffixes might be stored in an array $M$, where M j] is the distance between the last $i$ characters of string s and the last $j$ characters of string t. The table is easy to construct one row at a time starting with row 0. When the entire table has been built, the desired distance is in the table in the last row and column, representing the distance between all of the characters in s and all the characters in t.

Iterative with full matrix

(Note: This section uses 1-based strings instead of 0-based strings.)

Computing the Levenshtein distance is based on the observation that if we reserve a Matrix (mathematics), matrix to hold the Levenshtein distances between all prefixes of the first string and all prefixes of the second, then we can compute the values in the matrix in a dynamic programming fashion, and thus find the distance between the two full strings as the last value computed.

This algorithm, an example of bottom-up dynamic programming, is discussed, with variants, in the 1974 article ''The String-to-string correction problem'' by Robert A. Wagner and Michael J. Fischer.

This is a straightforward pseudocode implementation for a function LevenshteinDistance that takes two strings, ''s'' of length ''m'', and ''t'' of length ''n'', and returns the Levenshtein distance between them:

function LevenshteinDistance(char s ..m char t ..n:
// for all i and j, d ,jwill hold the Levenshtein distance between
// the first i characters of s and the first j characters of t
declare int d ..m, 0..n
set each element in d to zero

// source prefixes can be transformed into empty string by
// dropping all characters
for i from 1 to m:
d, 0:= i

// target prefixes can be reached from empty source prefix
// by inserting every character
for j from 1 to n:
d, j:= j

for j from 1 to n:
for i from 1 to m:
if s = t
substitutionCost := 0
else:
substitutionCost := 1

d, j:= minimum(d -1, j+ 1, // deletion
d, j-1+ 1, // insertion
d -1, j-1+ substitutionCost) // substitution

return d, n

Two examples of the resulting matrix (hovering over a tagged number reveals the operation performed to get that number):

:

The invariant maintained throughout the algorithm is that we can transform the initial segment into using a minimum of operations. At the end, the bottom-right element of the array contains the answer.

Iterative with two matrix rows

It turns out that only two rows of the table the previous row and the current row being calculated are needed for the construction, if one does not want to reconstruct the edited input strings.

The Levenshtein distance may be calculated iteratively using the following algorithm:

function LevenshteinDistance(char s ..m-1 char t ..n-1:
// create two work vectors of integer distances
declare int v0 + 1 declare int v1 + 1
// initialize v0 (the previous row of distances)
// this row is A i]: edit distance from an empty s to t;
// that distance is the number of characters to append to s to make t.
for i from 0 to n:
v0 = i

for i from 0 to m - 1:
// calculate v1 (current row distances) from the previous row v0

// first element of v1 is A + 10]
// edit distance is delete (i + 1) chars from s to match empty t
v1 = i + 1

// use formula to fill in the rest of the row
for j from 0 to n - 1:
// calculating costs for A + 1j + 1]
deletionCost := v0 + 1+ 1
insertionCost := v1 + 1
if s = t
substitutionCost := v0 else:
substitutionCost := v0 + 1

v1 + 1:= minimum(deletionCost, insertionCost, substitutionCost)

// copy v1 (current row) to v0 (previous row) for next iteration
// since data in v1 is always invalidated, a swap without copy could be more efficient
swap v0 with v1
// after the last swap, the results of v1 are now in v0
return v0

Hirschberg's algorithm combines this method with divide and conquer. It can compute the optimal edit sequence, and not just the edit distance, in the same asymptotic time and space bounds.

Automata

Levenshtein automata efficiently determine whether a string has an edit distance lower than a given constant from a given string.

Approximation

The Levenshtein distance between two strings of length can be approximated to within a factor

: $(\log n)^,$

where is a free parameter to be tuned, in time .

Computational complexity

It has been shown that the Levenshtein distance of two strings of length cannot be computed in time for any ε greater than zero unless the strong exponential time hypothesis is false.

See also

*agrep
*Damerau–Levenshtein distance
* diff
* Dynamic time warping
*Euclidean distance
* Homology of sequences in genetics
*Hamming distance
* Hunt–Szymanski algorithm
*Jaccard index
* Locality-sensitive hashing
*Longest common subsequence problem
*Lucene (an open source search engine that implements edit distance)
*Manhattan distance
*Metric space
* MinHash
* Optimal matching algorithm
*Numerical taxonomy
* Sørensen similarity index

References

External links

*

Rosseta Code implementations of Levenshtein distance

{{DEFAULTSORT:Levenshtein Distance
String metrics
Dynamic programming
Articles with example pseudocode
Quantitative linguistics