You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
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.
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:
The text was updated successfully, but these errors were encountered: