You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Google mistakes things like "Youghiogheny" for "Yakageny" (huh?), and "Haw" for "Hall", which results in matching failures.
Phonetic matching should probably be used here - perhaps something like double-metaphone (npm)?
These words don't directly match though, even with double-metaphone.
So we would need to iterate through every river and pick the best match - probably a one character tolerance (so H vs HL, AKN vs AKJN, etc, work)
This will likely result in matching too many things though - something like "Yadkin" would then match "Youghiogheny". Probably better than the alternative (not matching), however.
The text was updated successfully, but these errors were encountered:
Google mistakes things like "Youghiogheny" for "Yakageny" (huh?), and "Haw" for "Hall", which results in matching failures.
Phonetic matching should probably be used here - perhaps something like double-metaphone (npm)?
These words don't directly match though, even with double-metaphone.
So we would need to iterate through every river and pick the best match - probably a one character tolerance (so H vs HL, AKN vs AKJN, etc, work)
This will likely result in matching too many things though - something like "Yadkin" would then match "Youghiogheny". Probably better than the alternative (not matching), however.
The text was updated successfully, but these errors were encountered: