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

Prefix suffix direction match enforcement #11

Closed
steveoh opened this issue Feb 11, 2016 · 1 comment
Closed

Prefix suffix direction match enforcement #11

steveoh opened this issue Feb 11, 2016 · 1 comment
Assignees
Labels
question service - api geocoding the geocoding endpoint of the api

Comments

@steveoh
Copy link
Member

steveoh commented Feb 11, 2016

if input address is based a numeric streetname formatted address do not return a match where the found address has a different prefix direction or suffix direction (even from acs alises)

example:

677 E 1600 N Centerville should not return a match but currently returns: 677 W 1600 N, 84014 (input and result prefixes do not agree)

BUT allow for reversals

@steveoh
Copy link
Member Author

steveoh commented Sep 7, 2022

duplicate of #117

@steveoh steveoh closed this as completed Sep 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question service - api geocoding the geocoding endpoint of the api
Projects
None yet
Development

No branches or pull requests

2 participants