Overview

Exposure data must be prepared prior data analysis. For location exposures, preparation requires that you run geocoding and hazard lookup jobs. These closely connected processes may be run with a single are known collectively as "geohazarding".

• Geocoding is the process of enriching a location exposure with geolocation data that precisely identifies the global coordinates of a site. Geocoding is a prerequisite for all catastrophe modelling processes.
• Hazarding is the process of enriching a location exposure with risk data drawn from an RMS peril model database, a collection of site hazard values that characterize the vulnerability of a location to a catastrophe event.

A location is a property, building, business, or other asset that may be damaged by catastrophe events. When location coverage is applied to a location, that location is known as a location exposure. Location coverage defines the liability of the underwriter for damages to entities (buildings, building contents, businesses) at a specific location due to catastrophe events. A location is generally tied to an account and a portfolio, which identifies the relevant cedants, underwriters, and policies.

📷

Licensing Restrictions

The Risk Modeler API supports the definition, importation, and geocoding of locations in over 230 countries. Locations may be geocoded in countries that have RMS catastrophe models and countries that have no models. Your ability to geocode locations in specific countries depend on your company’s licensing agreements with RMS.

Geohazard location exposures

The Geohazard account service enables you to geocode account locations and run hazard lookup jobs based on one or more peril models for those locations.

You must specify the ID of an account as a path parameter and an EDM (datasource) as a query parameter.

curl --request POST \
     --url 'https://{host}/riskmodeler/v2/accounts/677/geohaz?datasource=my-edm' \
     --header 'Accept: application/json' \
     --header 'Authorization: XXXXXXXXXX' 

All other parameters are specified in the request body, which specifies an array of jobs. The first object defines the a geocode job. Subsequent objects define hazard lookups.

[
   {
      "name": "geocode",
      "type": "geocode",
      "engineType": "RL",
      "version": "18.1",
      "layerOptions": {
      "skipPrevGeocoded": false,
      "aggregateTriggerEnabled": "false",
      "geoLicenseType": "0"
      }
   },
   {
      "name": "earthquake",
      "type": "hazard",
      "version": "18.1",
      "engineType": "RL",
      "layerOptions": {
      "skipPrevHazard": false,
      "overrideUserDef": false
      }
   }, 
   {
      "name": "windstorm",
      "type": "hazard",
      "version": "18.1",
      "engineType": "RL",
      "layerOptions": {
      "skipPrevHazard": false,
      "overrideUserDef": false
      }
  }
]

For each job, the name, type, engineType, and version parameters are required.

• The name parameter specifies the peril model. A peril model is a computer-based model that estimates losses from natural or man-made hazards, such as earthquakes, floods, hurricanes, and acts of terrorism.
• The type parameter specifies the job type. One of geocode or hazard.
• The version parameter specifies the version of the peril model.
• The engineType specifies engine used to process the job.
• The optional layerOptons object specifies options that apply to that layer. The Boolean skipPrevGeocoded attribute determines whether geocoding is rerun for this layer on previously geocoded locations.

If successful, returns a 202 Accepted HTTP response and initiates a GEOHAZ workflow job on the workflow engine.

📷

Geocode and hazard locations

Risk Modeler offers services that enable you to geohazard locations at the account- or portfolio-level.

• The Geohazard account service geocodes and geohazards locations belonging to a specified account.
• The Geohazard portfolio service geocodes and geohazards locations belonging to a portfolio of accounts. Both services enable you to lookup hazard data for multiple layers.