Apr 09 2021 10:37 AM
Apr 09 2021 10:37 AM
Whether you have a list of addresses or need to collect addresses from customers, the challenge exists that those addresses map to a real location! As you or your company are taking valuable time to collect and likely paying for space to store this information it is important that it be free of misspelling and contain only verified information. With Azure Maps you can create your own address generation experience that covers the world (Geocoding coverage in Microsoft Azure Maps Search service | Microsoft Docs) and tailor it to meet your needs. Here are some ideas how you might power your address collection solution by leveraging Azure Maps Search API.
If you are building an experience that collects address information through a web site or form, you can allow only suggested addresses to be entered by having the client enter their address details and only select from a drop down of addresses choices. The Azure Maps Search API has a parameter, typeahead that when set to true will treat the query value as a partial input and sets the API into a predictive mode, assuming that this is incomplete data. You can try our sample solution yourself at Fill Address Form with Autosuggest - Azure Maps Web SDK Samples (azuremapscodesamples.azurewebsites.... and pull the code from GitHub to modify for use in your solution. Using the samples steps in the Best practices for Azure Maps Search Service | Microsoft Docs you will see the following drop-down experience in the sample:
And each of these choices will have a corresponding address in the Search response. Let’s choose the first one, Charlotte. It has the following address that includes some deeper detail:
"streetName": "Microsoft Way",
"countryTertiarySubdivision": "Township 1 Charlotte",
"countrySubdivisionName": "North Carolina",
"extendedPostalCode": "282738105, 282738106, 282738108, 2827382, 282738200",
"country": "United States",
"freeformAddress": "Microsoft Way, Charlotte, NC 28273"
Once I select that option from the drop down the form can be filled with the values from the Search call response, confident that this is a valid address as shown:
If you are building an experience to validate a physical delivery address, you can use the same method but validate the location against a map instead of entering text in a form. As in the prior sample, the client enters the details of the delivery location but now they can confirm that the correct location by seeing where a pin is placed on the map. If not, they can type more details to change the suggestion options. To try this scenario for yourself, go to Search Autosuggest and JQuery UI - Azure Maps Web SDK Samples (azurewebsites.us)
Last but not least, if you already have a database or collection of addresses you want to check, the same Azure Maps Get Search Address API receives queries that contain location information, and returns results as latitude and longitude coordinates. This API can be called individually or as a batch as documented here Search - Post Search Address Batch (Azure Maps) | Microsoft Docs. By filtering the results, you can identify addresses that failed to resolve and reach out to that client for an update to their address, ensuring that invalid addresses are identified and repaired.
In summary, with Azure Maps, there is a path to only keeping valuable and verified addresses in your solution. Please find these interactive samples and many more to help you with your Azure Maps solution at Azure Maps Web SDK Samples (azuremapscodesamples.azurewebsites.net).