Skip to content

How to Perform a Valid Address Check Using a Geocoding API

Whether you need to verify a single address or several, using the best geocoding API can help you do it. The API can return address components, formatted address, report codes, and a list of valid suggestions when the input is ambiguous. You can use the EverythingLocation API if you have an old everythinglocation API key, enough credit, or both. Before you can use the API, you will need to provide a sample JSON input. The API charges for geocode fields and certified fields.

PreferableLabelValues parameter

The Geocoding API supports the use of the PreferableLabelValues (PLV) parameter in a request. This parameter is used to provide the preferred local city when an address does not have a postal city. Some address types have two local city names, and some don’t. In such a case, you can specify either the postal city name or the local city name.

The location parameter in a geocoding request specifies whether the location is local. It may be a street address, administrative place-name, or POI. The location object includes two sets of X/Y coordinates, the X/Y attribute values describing the address along a street, and the DisplayX/DisplayY coordinates indicating the centroid of the building. The default geometry of the geocoded address result represents the location on a rooftop, which is usually acceptable for most map displays and spatial analysis.

The findAddressCandidates operation uses a street address and its intersection. The resulting results are ranked by match accuracy. The match accuracy identifies the optimal results for address searches. The parameters f and p can be passed as a single line, or multiple fields of text. If the address contains a street name, it is likely to be found in an index.

Reverse geocoding

If you use a reverse geocoding API for a valid address check, the process is remarkably simple. You can specify multiple addresses and retrieve results as a list. Then, you can select which ones to return. Once you’ve entered your address and selected a location, you can choose the type of results that will be returned. For example, if you enter “21 Henr St, Bristol, UK” in the location field, you’ll get multiple results for Henry Street and Henretta Street. If you misspell the address, the geocoding service will suggest an alternative, which will also be marked as a partial match.

Using this geocoding API, you can use a variety of filters to search for an address. One filter is known as “range-interpolated” because it returns results that correspond to the smallest number of addresses. A second filter, “geometric-center”, can be used to determine the accuracy of the geocodes. In addition to using a range-interpolation filter, you can also use an approximate filter to return addresses that are only approximations. These three filters are used to find the exact location of an address. If none of these filters are present, the API returns ZERO_RESULTS.

Batch geocoding

The first step when geocoding an address is to divide the input table into record sets and send each set in turn. Geocoding API operations such as Generate and Publish allow you to batch geocode multiple addresses and only return matching addresses within the country you specify. Batch geocoding operations only return results once each address has been successfully geocoded. It is vital to implement error detection logic in the client application to avoid the loss of batches.

The “Street” and “City” fields are optional parameters that you can specify in your geocode request. The preferredLabelValues parameter lets you specify additional values in the output field. This parameter can be empty or a comma-separated list of values. You cannot specify both fields at once. If you only need one or two of them, you can set the output parameter to return only those fields.

Exclusion of candidates that are outside a specified extent

In the context of a geocoding search, you may want to exclude all candidates who are outside a certain extent. This parameter is not designed to handle very large areas, and excessive searchExtent values can reduce the quality of geocoding results. For example, if an input address is ambiguous, a large searchExtent value may result in an excessively large number of matching candidates. Such a large number of candidates can slow down the geocoding service’s response time and result in unexpected results.

Geocoding results are typically ordered based on relevance and importance. Mobile apps prioritize candidates within a certain radius, so that candidates closest to their location receive higher rankings. For example, if a user enters a search string for the name June, the results will only contain candidates within the same radius. However, if the search term category=Ski Resort is used, all candidates in the radius of 50,000 meters will be ignored.