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

A numbered locality name doesn't autocomplete well when followed by provinceCode (BC) #225

Open
mraross opened this issue Mar 1, 2021 · 1 comment

Comments

@mraross
Copy link

mraross commented Mar 1, 2021

Currently in BC, only IRs are numbered locality names but, in principle, there could be others. Here is an example that doesn't autocomplete well:

Input address Best match
Bear Bay 8 Bear Bay 8 near Bute Inlet, BC
Bear Bay 8 BC 8 BC Mine Rd, Grand Forks, BC
@mraross mraross changed the title A numbered IR doesn't autocomplete well when followed by provinceCode (BC) A numbered locality name doesn't autocomplete well when followed by provinceCode (BC) Mar 2, 2021
@cmhodgson
Copy link
Collaborator

Apparently we have a lot bunch of numbered rds named # BC Mine Rd, where the # is less than about 20, which also seems to correspond to the typical numbering of IR localities. Maybe we can do something to make the words before the number more important - but they could also be garbage, or a site name... part of the problem is that the base score of a locality is much lower than a street match so we will do acrobatics to match to a street even when there is an obvious, perfect, locality match.

Maybe we could adjust the point cost of garbage based on whether or not we find other, cleaner matches. Ideally we might not even consider matches with garbage if there are other perfect or near-perfect matches. Somehow we need to increase the score of a perfect locality match above that of a street match with an unknown site name, missing street name parts, and no locality name.

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

No branches or pull requests

2 participants