Geocode quality Index
|Full Street Name Confidence Level
|Administrative Area Confidence Level
|Postal Code Confidence Level
|Administrative Area Confidence
|Match locations that exactly correspond to the input location, as defined by the address elements specified.
|Exact matches, although the geocoding engine allows standard variations of road types, directionals, numbered roads, and common abbreviations. Examples include Road vs. RD, North vs. N, Second vs. 2nd, and Mount vs. MT.
|Exact matches, although common abbreviations are acceptable. For instance, "Mount View" is the same as "Mt. View."
|The postal code matches at the granularity of the input. The matched postal code may be even more precise than the postal code specified in the input.
|Matches should be fairly similar, even if not exactly as specified.
|Good matches, ignoring differences in road type and directionals. EG: Road vs. Street,North vs. South. Includes matches where type & directional are supplied but not found, or found but not supplied.
|Good matches, even if administrative area names do not exactly match. This includes sound-alike matches, partial, slight misspellings, or other fuzzy matching. Details vary by geocoding data.
|Postal code does not exactly match at the granularity of the input. However, the postal code likely matches the input address at a lower granularity level than at the requested granularity.
|Matches should be somewhat similar to the input location as specified.
|Sound-alike matches, partial matches, slight misspellings, and fuzzy matching. Details vary by geocoding data.
|Matched administrative areas do not match the input administrative areas. This may occur when the postal code input determines the match.
|Postal codes do not match. This may occur when the administrative area input determines the match.
|[Confidence level has no meaning for this granularity level or was not used.]