Artificially lower match scores for differing suffix directions & address systems

[stdavis]

351 E 850 W, 84701 returns a match score of 92.43 but matches a totally different street: 351 E 850 N.

I would have expected the score to be much lower. I wonder if the API could artificially lower match scores when the suffix (or prefix) directions don't match the input.

We should also do this for candidates/matches that have a different address system.

Possible duplicate of #11

[steveoh]

It is certainly something we should investigate

[steveoh]

I like this idea. We would need to figure out the value to lower the score by or if a default value should be used.

[stdavis]

I'd like to start the bidding at -20 from the original score.

[steveoh]

Typically that would put it at about 72. Would we want it to go below the default match threshold?

[stdavis]

Good point. Is the default match threshold 75? Maybe -15 or -10?

[steveoh]

its 70

[stdavis]

Maybe -15 is the safest? Actually, though, I almost think that I would want it to drop below the match threshold. IMO, that's a bad match that only causes confusion. My vote would be maybe -25.

[stdavis]

Should a similar thing be done for candidates that have mismatching address grids from the input address?

[steveoh]

I like that idea