Matching Options
Matching options are used to determine how address searches are performed. They let you set match preferences, criteria and restrictions, and multiple match settings so that the matching can be as strict or relaxed as you need.
Parameter | Description |
---|---|
Option.MatchMode |
Specifies how to determine whether a candidate is a close match. One of these:
|
Option.MustMatchInput |
Specifies whether candidates must match all non-blank input fields to be considered a close match. For example, if an input address contains a city and postal code, then candidates for this address must match the city and postal code to be considered a close match.
|
Option.MustMatchCity |
Specifies whether candidates must match the city. If you do not require exact matches on city, the geocoder searches on the street address matched to the particular postal code, and considers other cities that do not match the name, but do match the postal code.
|
Option.MustMatchHouseNumber |
Specifies whether candidates must match the house number. If the input house number is not within a range from the street, GeocodeAddressCAN selects the nearest range on the street which has the same parity (even or odd house number) as the input address number. GeocodeAddressCAN returns one or more of the closest matches inside this range that preserves street parity. This requires GeocodeAddressCAN to change the house number. The new house number is equal to one of the range's endpoints, possibly plus or minus one to preserve street parity. Note: Even when this option is disabled and an inexact match on the house number is found, GeocodeAddressCAN still returns an error code.
When this option is disabled and no exact matching house number is found, a match code of either E029 (no matching range, single street segment found), or E030 (no matching range, multiple street segment) is returned. GeocodeAddressCAN does not change the house number on the output address. In order to access the inexact address number candidates, you must specify Option.KeepMultimatch=Y. If there are inexact house number candidates returned, the corresponding match codes begin with the letter 'H' indicating that the house number was not matched. Additionally, even when one or more exact candidates are found, inexact matches to the house number are still on the list of possible candidates, and these can be differentiated from the others by their Hxx match codes. For more information about match codes, see Match Codes.. One of these:
|
Option.MustMatchPostalCode |
Specifies whether candidates must match the postal code. If you do not require exact match on postal codes, the geocoder searches a wider area for a match. While this results in slower performance, the match rate is higher because the request does not need to match exactly when it compares match candidates.
|
Option.MustHaveFullPostalCode |
Require full postal code for the close match. Legal Values: Y = Yes, N = No Default Values: N = No |
Option.MustMatchStateProvince |
Specifies whether candidates must match the state.
|
Option.MustMatchStreet |
Specifies whether candidates must match the street name.
|
Option.MustMatchLocality |
Specifies whether candidates must match the locality (or equivalent) to be considered a close match.
If you do not require exact matches on locality, the geocoder searches on the street address matched to the particular postal code, and considers other localities that do not match the name, but do match the postal code. |