Add parameter &matchPrecisionNot=street to geocoder request to improve relevance of results

[mraross]

In the TRP app, if you enter:

 west v

as a route point, the app will issue the following request to the geocoder:

https://geocoder.api.gov.bc.ca/addresses.json?minScore=50&maxResults=5&echo=true&brief=true&autoComplete=true&addressString=west%20v

and get the following results:

West Boulevard, Vancouver, BC
East Boulevard, Vancouver, BC
rest area, Vernon, BC
rest area, West Vancouver, BC
West Grant Channel Pitt Lake, Indian Arm, BC

If you add &matchPrecisionNot=street to the geocoder request as follows:

https://geocoder.api.gov.bc.ca/addresses.json?minScore=50&matchPrecisionNot=street&maxResults=5&echo=true&brief=true&autoComplete=true&addressString=west%20v

you will get the following, more relevent results:

West Vancouver, BC
North Vancouver, BC
District of North Vancouver, BC
Villaverde Islands, BC
Viscount Island, BC

We just discovered this trick yesterday.

[mraross]

There is a minor cost; you will no longer be able to find a bridge by its name since a bridge is defined as a street in ITN. We think entering a locality name is much more common than entering a bridge name. If a user needs to locate a bridge, they can still pan, zoom, and click.

In the longer term, we could add all named bridges to the geocoder as non-civic addresses (e.g., Golden Ears Bridge -- Township of Langley, BC)