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

Don't return candidates if there is no match #202

Open
stdavis opened this issue Jun 21, 2024 · 0 comments
Open

Don't return candidates if there is no match #202

stdavis opened this issue Jun 21, 2024 · 0 comments

Comments

@stdavis
Copy link
Member

stdavis commented Jun 21, 2024

Currently, masquerade will return the match address or if that it not defined, then it will return the first candidate as the match. For findAddressCandidates it will return candidates whether a match is defined or not. The problem with this is sometimes, the candidates are bad matches only suitable for the suggest endpoint. For example, they may have high match scores but are located in a different address grid.

suggest

This should probably continue to suggest address point addresses and not hit the web API at all.

findCandidates

This should not return any candidates unless there is a match defined. Even then, perhaps it should filter out candidates that have a mismatched address grid? Or maybe an enhancement to the web API would be to artificially lower match scores if the address grid does not match.

geocodeAddresses

This should only return the match address or nothing.

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