Troubleshooting location information input

Potential causes of geocoding errors.

To ensure the best results for supplying location information, geocoding, and back filling and forward filling location information, it is imperative to make sure that your input data is as accurate as possible. You might still, however, get unexpected results. When preparing location information for input into Verisk Synergy Studio, be aware of the following potential causes of geocoding errors:

• If you supply an address or geocode that Verisk Synergy Studio cannot locate in the database, Verisk Synergy Studio returns a geocode match level of "None." Alternately, this situation can result in issues with the back filling of the corresponding area information.
• If you supply postal or administrative codes that Verisk Synergy Studio does not support, then Verisk Synergy Studio either returns lower resolution geocodes or may be unable to geocode the corresponding locations.
• If you supply a geocode for a location and choose to preserve this geocode during the location data import, Verisk Synergy Studio back fills area information based on this geocode. Therefore, if the geocode that you supply is incorrect, the information that Verisk Synergy Studio back fills for this location is also incorrect.

• If you supply and preserve a geocode for a location, and you map additional geographic fields (in addition to country, latitude, and longitude) in your CSV import file to Verisk Synergy Studio exposure database fields during the location data import, Verisk Synergy Studio might retain any CRESTA, area, subarea, postal, subarea2, city, and street address information that you have supplied. Based on the geocode that you provide, Verisk Synergy Studio also performs a country-specific look-up for the closest supported postal or other centroid to back fill any required or supported location data for model use. In this case, Verisk Synergy Studio might use the looked-up data instead of the geographic fields you provided, but always uses the latitude/longitude that you provide.

  Consequently, if you suspect that data quality issues may exist in your area, postal, and/or other data, you can choose not to map any geographic fields other than country, latitude, and longitude. In this case, Verisk Synergy Studio back fills the other geographic fields based on the geocode that you have supplied. Further, inconsistencies between the user-supplied geocode for a location and the user-supplied area, subarea, street address, and other information for the same location can result in skewed loss results. Therefore, either confirm the consistency between user-supplied geocodes and other geographic information or only map the country, latitude, and longitude geographic fields, thereby enabling Verisk Synergy Studio to back fill geographic data based on the geocode that you have supplied.

• Verisk Synergy Studio supports many different combinations of geographic data for locations. This document details a series of specific location information schemes for each supported country. However, the data that you receive for input into Verisk Synergy Studio may not adhere exactly to a single location information scheme. If you have location data that differs from the schemes that this document presents, or if you encounter import/geocoding issues, please contact Verisk for assistance.
• Country-specific rules vary regarding conflicts between geocodes that you provide and other available input fields, such as CRESTA, area, subarea, postal, subarea 2, and city information. Some countries may adjust the back fill, some may generate errors, and some may store all the data as entered (with no back fill or validation adjustments). Import validation rules in the newer model updates, such as South America and Southeast Asia, have become more consistent. Import validation rules for older models will likewise become more consistent as these models are updated.