Geocoding API

Geocode Quality Code Details

The geocodeQualityCode value in a Geocode Response is a five character string which describes the quality of the geocoding results.

Character Position 1 2 3 4 5
Value G S F A P
Character Meaning
G Granularity Code
S Granularity Sub-Code
F Full Street Name Confidence Level
A Administrative Area Confidence Level
P Postal Code Confidence Level

Geocode Quality Sample


Full Street Level Confidence:

Administrative Area Level Confidence:

Postal Code Level Confidence:


Granularity GeocodeQuality Description
P1 POINT A specific point location.
L1 ADDRESS A specific street address location.
I1 INTERSECTION An intersection of two or more streets.
B1 STREET The center of a single street block. House number ranges are returned if available.
B2 STREET The center of a single street block, which is located closest to the geographic center of all matching street blocks. No house number range is returned.
B3 STREET The center of a single street block whose numbered range is nearest to the input number. House number range is returned.
A1 COUNTRY Admin area, largest. For USA, a country.
A3 STATE Admin area. For USA, a state.
A4 COUNTY Admin area. For USA, a county.
A5 CITY Admin area. For USA, a city.
A6 NEIGHBORHOOD Admin area. For USA, a neighborhood.
Z1 ZIP Postal code, largest. For USA, a ZIP.
Z2 ZIP_EXTENDED Postal code. For USA, a ZIP+2.
Z3 ZIP_EXTENDED Postal code. For USA, a ZIP+4.
Z4 ZIP Postal code, smallest. Unused in USA.


Confidence Description StreetCon AdminCon PostalCon

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.
X [Confidence level has no meaning for this granularity level or was not used.]