-
Notifications
You must be signed in to change notification settings - Fork 5
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
Score difference #47
Score difference #47
Conversation
and is difficult to make work and not important
Does this seem to answer your problem from earlier @JustinBerger? |
Absolutely. It gives a simple way to do big batches of records, and still know when there are very similar potential matches. Is it possible for 2 different endpoints to return the same geocode? It makes sense to drop those 'ties' since they are really the same. |
On the example I showed the ties are different addresses with the same score so I wouldn't recommend dropping them. The locators themselves would not return the same address unless it is an apartment but we already handle that. The address points could return similar to a range geocode but the address points are weighted in the case of a tie. I'll release this today so you can give it a spin. |
add score difference param to address geocoding api.
closes #34 refs #32