locality qualifier in locality name is distorting match scores

[mraross]

 Johnson BC

scores the same as:

 Johnson Bay Indian Arm, Indian Arm, BC

because

 Johnson BC

is penalized for only making a partial match to:

 Johnson BC near Indian Arm

when, in fact, it is a perfect match to:

 Johnson BC

because:

 near Indian Arm

is just a qualifier and not part of the official locality name.

Here's the geocoder query:

https://geocoder.api.gov.bc.ca/addresses.xhtml?locationDescriptor=parcelPoint&echo=true&brief=true&minScore=50&maxResults=5&autoComplete=true&matchPrecisionNot=&addressString=Johnson%20bc

[mraross]

If the localityName (Johnson) and the localityQualifier (near Indian Arm) were kept separate for the purposes of locality name comparison, this situation would be avoided. localityQualifier should be included in match results as well.

[mraross]

Heres another example:

 Kitsilano

matches the following with the same score and in the order given:

 Kitsilano 6 in Vancouver, BC
 Kitsilano in Vancouver, BC

[BK01]

Propose adding a zero-point fault for a missing qualifier. The aim is to not penalize or reduce the score of an addressString for a missing locality qualifier, if it is still valid without it.

[BK01]

Validated in geocodertst (Geocoder 4.3). A zero point penalty is applied as a partial locality match in the examples above.