Balancing Match Rate and Precision

You may want to use a balanced strategy between match rate and geographic precision. That is, you may want to geocode as many records as possible automatically, but at the same time want to minimize the number of weaker matches (false positives). For example, false positives can occur when the geocoder:

  • finds a street that sounds like the input street.
  • finds the same street in another city (if postal code match is not required).
  • finds the street but with a different house number (if house number is not required).

The following settings may achieve a good balance between match rate and precision:

  • CloseMatchesOnlySpecify "Y".
  • MustMatchHouseNumber—Specify "Y".
  • MustMatchStreet—Specify "Y".
  • FallbackToPostalSpecify "N".