Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Metaphone on import doesn't match metaphone when geocoding #17

Open
peterlandry opened this issue May 10, 2010 · 0 comments
Open

Metaphone on import doesn't match metaphone when geocoding #17

peterlandry opened this issue May 10, 2010 · 0 comments

Comments

@peterlandry
Copy link

After importing tiger data, a feature record for "Dexter St" gets a metaphone value of "TKTR". This is confirmed by manually testing the metaphone library:

$sqlite3 /opt/tiger/geocoder.db
sqlite> .load lib/geocoder/us/sqlite3.so
sqlite> select metaphone('Dexter');
TKTR

This, compared to the results from Text::Metaphone:

$ irb
irb(main):001:0> require 'rubygems'
=> true
irb(main):002:0> require 'text'
=> true
irb(main):003:0> Text::Metaphone.metaphone 'Dexter'
=> "TXTR"

This is preventing valid addresses on Dexter St from being geocoded at the range level.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant