Within the Addressing API, the Verify Service provides address validation and standardization capabilities using the specified address processor.
By default, a processor is automatically selected based on the
configured data. If you have configured data for multiple products, the default processing
order is Global Geocoding, Geolocation, and Finalist.
To specify an address processor, set "label" to one of the following values.
Note: Labels
are case-sensitive and must be lowercase.
| Value | Description |
|---|---|
| "ggs" | Available for the whole world. |
| "global_locator" | Available for the whole world. |
| "finalist" | Only processes USA. |
A Verify Request consists of Preferences and Addresses. Below is a sample Verify
Request:
{
"preferences": {
"maxResults": 1,
"returnAllInfo": true,
"factoryDescription": {
"label": "",
"featureSpecific": {}
},
"clientLocale": "",
"clientCoordSysName": "",
"distance": {
"value": 150,
"distanceUnit": "METER"
},
"streetOffset": {
"value": 7,
"distanceUnit": "METER"
},
"cornerOffset": {
"value": 7,
"distanceUnit": "METER"
},
"fallbackToGeographic": false,
"fallbackToPostal": false,
"matchMode": "",
"returnOfAdditionalFields": false,
"originXY": [],
"customPreferences": {}
},
"addresses": [
{
"addressId": "1",
"addressLines": [
"1700 District Ave #300 Burlington, MA"
],
"country": "USA",
"addressNumber": "",
"admin1": "",
"admin2": "",
"city": "",
"borough": "",
"neighborhood": "",
"suburb": "",
"postalCode": "",
"postalCodeExt": "",
"placeName": "",
"street": "",
"building": "",
"floor": "",
"room": "",
"unit": "",
"unitType": ""
}
]
}Preferences
"preferences": {
"maxResults": 1,
"returnAllInfo": true,
"factoryDescription": {
"label": "",
"featureSpecific": {}You can try this in the Geo Addressing SDK Sample application
(http://{server}:{port}/{context}/):
- Click .
- Enter a complete Address and specify a Country.
- If multiline entry is needed, select the Show parsed Fields option.
- In the Request, go to the
"preferences"section and enter a value on the"label"line. - Click Submit and view the response.
Input Address Guidelines
Follow these address guidelines for best performance:
- Ensure that your input addresses are as complete and accurate as possible. If there are errors in your input addresses, the Geo Addressing SDK Spectrum Global GeocodingGeocoding REST API may still be able to geocode those addresses, but there may be more than one possible match.
- Include postal codes in your input addresses if you have them. This is not required, but it allows the Geo Addressing SDKSpectrum Global Geocoding Geocoding REST API to perform postal geocoding. This may give you more accurate results for some addresses, depending on the country and on the completeness and accuracy of other address components.
- Format your input addresses consistently. The Geo Addressing SDK Spectrum Global GeocodingGeocoding REST API can handle input addresses in a wide variety of input formats, or can handle unformatted (single line) input. But you can get more accurate and faster results if your input addresses are consistently formatted and conform to country-specific address conventions.