-
Notifications
You must be signed in to change notification settings - Fork 89
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
near_dupe_hashes returns empty list #49
Comments
Same here getting the same issue |
I solved this by adding the address_only_keys flag to the call. It would be nice if this API had ANY documentation. |
I submitted an issue for documentation as well, but it does not seem like anyone monitors this page. |
Hi all, I did some digging and it looks like actually This issue can be closed |
The near_dupe_hashes function from the module postal.near_dupe seems to invariably return an empty list.
Here are some examples of US addresses I have tried. The tokens and labels were obtained with parse_address. The parameters do not change the output, but I have included them just in case
near_dupe_hashes(['house_number', 'road', 'city', 'state', 'postcode'],['209', 'st michaels circle', 'odenton', 'md', '21113'], with_city_or_equivalent=True, with_postal_code=True)
near_dupe_hashes(['house_number', 'road', 'city', 'state', 'postcode'],['1', 'six flags blvd', 'jackson township', 'nj', '08527'])
near_dupe_hashes(['house_number', 'road', 'city', 'state', 'postcode'], ['1313', 'disneyland dr', 'anaheim', 'ca', '92802'])
The text was updated successfully, but these errors were encountered: