Japan location information schemes
Japan location information schemes.
| Element | Description |
|---|---|
| Country code | 21 |
| ISO country abbreviation | JP |
| Required location fields |
|
| Geocode matching level (user interface) | AREA |
| GeoMatchLevelCode (in tLocation database table) | AREA |
| Enhanced GeoMatchLevelCode (in tLocation database table) | AREA |
| Verisk Synergy Studio location processing | Verisk Synergy Studio does not back fill or forward fill any additional data for this scheme. |
| Element | Description |
|---|---|
| Country code | 21 |
| ISO country abbreviation | JP |
| Required location fields |
|
| Geocode matching level (user interface) | County (subarea) centroid |
| GeoMatchLevelCode (in tLocation database table) | CNTY |
| Enhanced GeoMatchLevelCode (in tLocation database table) | SUBA |
| Verisk Synergy Studio location processing | Verisk Synergy Studio updates or back fills the area (prefecture) information as appropriate. |
| Element | Description |
|---|---|
| Country code | 21 |
| ISO country abbreviation | JP |
| Required location fields |
|
| Geocode matching level (user interface) | Postal Code centroid |
| GeoMatchLevelCode (in tLocation database table) | POST |
| Enhanced GeoMatchLevelCode (in tLocation database table) | POST |
| Verisk Synergy Studio location processing | Verisk Synergy Studio updates or back fills the area (prefecture) and subarea (municipality) information as appropriate. |
| Element | Description |
|---|---|
| Area scheme after transformation | 1048 |
| Country code | 21 |
| ISO country abbreviation | JP |
| Required location fields |
|
| Geocode matching level (user interface) | Postal centroid, County (subarea) centroid, or Area centroid, depending on the level of the Sompo code. |
| GeoMatchLevelCode (in tLocation database table) | POST, CNTY, or AREA, depending on the level of the Sompo code. |
| Enhanced GeoMatchLevelCode (in tLocation database table) | POST, SUBA, or AREA, depending on the level of the Sompo code. |
| Verisk Synergy Studio location processing | Verisk Synergy Studio remaps Sompo location information to the corresponding Prefecture, Municipality, or Yubin location information scheme. See "Japan Sompo import look-up logic" for more details. |
Japan Sompo import look-up logic
When importing exposure data with Sompo codes into a CSV file, always import Japan Sompo codes into Verisk Synergy Studio as Subarea2 data for field mapping. If you use the automapping feature, use a Subarea2 header for the Sompo code column.
- Verisk Synergy Studio does not support gun-level boundary resolution. Therefore, Verisk Synergy Studio remaps 543 gun-level Sompo codes to town or village based on the Ssrea boundary in which the Sompo latitude and longitude fall. If you want to use a different subarea/JIS code in place of the gun-level Sompo code, update the location to be geocoded using the subarea/JIS code.
- Do not import Sompo codes as postal data. The Sompo format will not match the expected postal code formats.
- When inputting Sompo and postal codes into CSV files, enter the codes in separate columns, one column for Sompo code data and a separate column for postal code data. Do not combine different data resolutions, such as Sompo and postal codes in the same column; this is because the rules and logic are different for each supported data resolution.
-
This section describes the geocoding process used when importing Japan Sompo
codes or when manually editing location details for an existing single
location in Verisk Synergy Studio, in the
Location Details pane. The source Sompo
code refers to the Sompo code entered in the user's exposure
data. The Sompo records refer to the Verisk Synergy Studio-supported Sompo codes that
are matched in the tGeography table.
- If a Sompo code has been provided with a pair of latitude and longitude values, then the latitude and longitude will take precedence over the Sompo code.
-
This is the look-up logic that Verisk Synergy Studio uses when Sompo
codes are entered without entering of latitude/longitude values.
- 10-digit code: The Sompo look-up logic will first try to match 10-digit source Sompo codes. When a match is successful, the logic will back fill Postal information. If a match to 10-digit Sompo codes is unsuccessful, the logic will first use the 7-digit Sompo code and then follow the next step in the logic.
-
7-digit code: If a 7-digit Sompo code is provided or if a
match to a 10-digit Sompo code is unsuccessful, the logic will
first use the 7-digit Sompo code and add 3 trailing 0s to make
it a 10-digit Sompo code. The Sompo look-up logic then tries to
find an exact match using the 10-digit Sompo code. If an exact
match to the 10-digit Sompo code is unsuccessful, the logic will
remove the trailing zero and then search for a match with only
the leading 7-digit Sompo codes.
- If the source Sompo code has a match to multiple Sompo records that have the same postal codes, the logic will back fill postal information.
- If the source Sompo codes has matches to multiple records with multiple postal codes, then the logic will use the first 4-digits and then follow the next step in the logic.
- 4-digit code: If a 4-digit Sompo code is provided or if a match to a 7-digit Sompo code is unsuccessful, the Sompo logic will try first to match the 4-digit Sompo code and add 6 trailing 0s. If there is a successful match, the logic will back fill subarea information.
- 2-digit code: If a 2-digit Sompo code is provided or if a match to a 4-digit Sompo code is unsuccessful, the Sompo logic will try first to match the 2-digit Sompo code and add 8 trailing 0s. If there is a successful match, the logic will back fill area (prefecture) information.
-
Sompo data provided with any other
data: The process will find the highest
possible resolution. For example:
- A 10-digit Sompo code has been provided along with a postal code. The look-up logic will try to find a match to the 10-digit Sompo code. If the match is unsuccessful, it will use the 7-digit Sompo code logic and will search for a postal code before applying the 4-digit Sompo code logic.
- A 2-digit Sompo code has been provided along with municipality (subarea) information. The process will look-up subarea information before applying the 2-digit Sompo code logic.
-
The following are assumed to be Sompo code formats where the input
CSV file suppressed a single leading zero.
- 1-digit subarea2 code. It is assumed to be a 2-digit Sompo code and should be padded with a single leading zero and 8 trailing zeroes.
- 3-digit subarea2 code. It is assumed to be a 4-digit Sompo code and should be padded with a single leading zero and 6 trailing zeroes.
- 6-digit subarea2 code. It is assumed to be a 7-digit Sompo code and should be padded with a single leading zero and 3 trailing zeroes.
- 9-digit subarea2 code. It is assumed to be a 10-digit Sompo code and should be padded only with a single leading zero.
- Verisk Synergy Studio does not retain Sompo information.
