Supplying U.S. street-level address data
Verisk Synergy Studio now uses the Verisk US GeoPin Geocoder as the default solution for U.S. street address geocoding.
Integration of Verisk US GeoPin geocoder
Verisk Synergy Studio now uses the Verisk US GeoPin Geocoder as the default solution for U.S. street address geocoding. This enhancement replaces the legacy US Census TIGER geocoding service and AIRAddressService database and delivers improved geocoding precision for U.S. exposures, resulting in more reliable catastrophe modeling, aggregation, and underwriting analysis.
As the new default U.S. street address geocoding solution in Verisk Synergy Studio, GeoPin delivers rooftop-level latitude and longitude precision. Exposure must include minimum required details below for Street level address to be eligible for GeoPin geocoding service.
- Country: U.S. or United States.
- Street address.
- State and city, or ZIP code.
For each given location, no user-supplied or existing geocodes are available and preserved.
For street address input data, Verisk recommends: (1) that the input address follows country-specific postal street address standards, and (2) that you limit the input street address field to the primary street address information, such as street #, street name, directional, and street type. In other words, remove any non-street address information, such as PO Box, Rural Route, ATTN, or C/O, from the input street address field; this is because Verisk Synergy Studio does not use them for street address geocoding and their existence in the input address will hinder street address parsing/matching. The postal authorities in all countries provide guidance on the address standards for their specific country.
Verisk Synergy Studio uses two fields in the tLocation table within the VeriskExposure database to store information about the geocode match level when you supply street-level address data. In addition to the GeoMatchLevelCode field, Verisk Synergy Studio also stores finer geocoding match level detail in the EnhancedGeoMatchLevelCode field. This additional field provides a clearer indication of the geocode match level for street-level address information by distinguishing between various Exact and Relaxed Address geocode match levels, as well as by indicating if supplied street-level address data matches at the very high resolution Parcel or Point level.
| GeoPin geocode type | EnhancedGeoMatchLevelCode | GeoMatchLevelCode |
|---|---|---|
| Interior | PT (Point) | POINT |
| Rooftop | PT (Point) | POINT |
| Parcel | PRCL (Parcel) | POINT |
| Address Point | PT (Point) | POINT |
| Street | SEGI | ADDR |
| 3P-Rooftop | PT | POINT |
| 3P-Post-Office | PT | POINT |
| 3P-Street | STRC | RLXA |
GeoPin address service provide Rooftop geocoding and better result in many case than TIGER address service. Change in geocodes may result in loss changes which provide more accurate presentation.
For United States exposures for which you supply street-level address data, Verisk Synergy Studio populates an additional field in the tLocation table. The ValidatorMatchCode field provides information about how Verisk Synergy Studio matched supplied street-level address information to the underlying street-level geocoding data. For a detailed description of each of the validator match codes, please see the tValidatorMatch table in the VeriskReference database.