Location address fields for import
In ImportExpress, you map .csv import data to valid Touchstone fields for location address fields.
Note: Avoid the following special
characters in your import files, especially in address-related data, such as street,
city, area, etc.: $, +, -, ., \. These special characters may cause geocoding,
validation, and import errors.
Import field | User interface field | Database field | Required |
---|---|---|---|
Street | Street | tLocation.Address | |
City | City | tLocation.City | |
Subarea (County Name) | Sub Area (County) | tLocation.SubareaName | |
Subarea2 (County) | Sub Area2 | tLocation.Subarea2Name | |
Area (State Name) | Area (State Name) | tLocation.AreaName | |
CRESTA Zone | CRESTA Zone | tLocation.CRESTAName | |
Postal | Postal | tLocation.PostalName or tLocation.Zip9 | |
Country (ISO Code) | Country (ISO Code) | tLocation.CountryName | |
Latitude | Latitude | tLocation.Latitude | |
Longitude | Longitude | tLocation.Longitude | |
User Geocode Match Level | User Geocode Match Level | tLocation.UserGeoMatchLevel |
Note:
For detailed information about supplying address data for locations, including the minimum and maximum geographic resolutions that Touchstone supports for each modeled country, see Using Geocoding in Touchstone on the Client Portal.