Location Address Fields for Import |
The table below lists the Touchstone address fields to which you can map comma-separated values (CSV) import data for primary or facultative property locations. In addition, this table lists the Touchstone user interface field and database field that correspond to each import field and provides a link to the description of and validation rules for each import field.
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 |
tLocation.Address |
|
|
City |
tLocation.City |
|
|
Subarea (County Name) |
tLocation.SubareaName |
|
|
Subarea2 (County) |
tLocation.Subarea2Name |
|
|
Area (State Name) |
tLocation.AreaName |
|
|
CRESTA Zone |
tLocation.CrestaName |
|
|
Postal |
tLocation.PostalName or tLocation.Zip9 |
|
|
Country (ISO Code) |
tLocation.CountryName |
|
|
Country (CLASIC/2 Code) |
Converted to Country (ISO Code) during geocoding process |
tLocation.CountryName |
|
Latitude |
tLocation.Latitude |
|
|
Longitude |
tLocation.Longitude |
|
|
User Geocode Match Level |
tLocation.UserGeoMatchLevel |
|
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 AIR Client Portal. |
© 2020 AIR Worldwide. All rights reserved. Touchstone 7.0 Updated September 03, 2020 |