Geocoding Data Extension Overview
  • 16 Jun 2023
  • PDF

Geocoding Data Extension Overview

  • PDF

Article Summary

Geocoding is one of the main entry points to data enrichment. An address is the most common tie point that users have in their data and a good geocoder is paramount when working with address data. One challenge is that some LightBox users of the Geocoding API have addresses before LightBox has them in the system or clients would like to enhance the location with their knowledge of the site and address placement. To solve this common problem we have built a system that allows our clients to add or enhance addresses to be used by the LightBox Geocoder. These addresses or enhancements are stored in a personal data extension catalog that can only be accessed by that same client. 

The geocoding process is simple in that it will first look into the clients dictionary for address candidates then look in the LightBox address universe for candidates. 

Features

  • We support the Search, parsed of unparsed endpoint using the data extension catalog
  • We support the Autocomplete endpoint using the data extension catalog
  • We support the Reverse endpoint using the extension catalog
  • Return the data extension ids that your account has been assigned, Prod and Staging
  • Add an address to a data extension catalog
  • Update an address within a data extension catalog
  • Delete an address within a data extension catalog
Pro Tip
LightBox will catch up to addresses in the future. Candidate addresses look at the precision code to determine what to return. When adding addresses keep that in mind. Say for instance you have a Parcel Centroid placement. In this case you can apply a precision code of 20. If LightBox gets a better placement in the future, a building centroid for instance, the precision code on this address will be 10. Thus returning the better address. You can always force the custom address to be returned using a precision code of 1 or you can make it higher such as 31 so that at anytime LightBox gets a high precision candidate that one is returned. 



Was this article helpful?