Using the H2DB format - Latest

Wildfire Risk Extreme Product Guide

Product type
Data
Portfolio
Enrich
Product family
Enrich Boundaries > Risk Boundaries
Product
Wildfire Risk Extreme
Version
Latest
Language
English
Product name
Wildfire Risk Extreme
Title
Wildfire Risk Extreme Product Guide
Copyright
2024
First publish date
2024
Last edition
2024-08-12
Last publish date
2024-08-12T13:47:50.481457

This product's GeoEnrichment module for Spectrum functions as a delivery mechanism for accessing a data source and returning data Using a lookup key value as an input, the GeoEnrichment module accesses a registered database and returns additional attribute data for the referenced record. The type of attribute data returned is determined by what databases are installed.

The GeoEnrichment module is delivered as a Spectrum module and can be built into Spectrum's stages. In order to do this, the Spectrum Technology Platform must already be installed.

When new database resources are installed, or when existing database resources are modified, they must be defined in Spectrum's Management Console in order to be made available. The following steps describe the process for adding or modifying a GeoEnrichment module database resource:

  1. Install the database files on your system. Refer to the Spectrum Technology Platform Installation Guide for instructions on database installation.
  2. Open the Management Console and click Resources > Spectrum Databases.
  3. Use the following buttons to add, modify, or delete database resources –
    1. To add a database resource, click the Add button
    2. To modify an existing database resource, click the Edit button
    3. To delete an existing database resource, click the Delete button
  4. If you are creating a new database resource, enter the resource name in the Name field on the Add Database page.
  5. In the Pool Size field, specify the maximum number of concurrent requests you want the database to handle.

    Optimal pool size varies by module. Best results are generally seen when pool size is set to between one-half and twice the number of CPUs on the server, with optimal size for most modules being equal to the number of CPUs. Thus, if your server has 4 CPUs, the pool size range will be between 2 and 8, with 4 possibly being the optimal size. Performance testing using various settings should be conducted to determine optimal pool size and runtime instance settings for your environment.

  6. Select GeoEnrichment Lookup in the Module field. The same value is selected by default in the Type field.
  7. To add a database file, click Data Source, then click the Add button. Specify a unique name in the Dataset Name field, and the full path and database name in the Dataset Path field (example: D:\gem\usa_databases\apen_elevation\apn_elevation\apn_elevation.h2.db).

    You can type the full path and filename, or you can click the Browse button, locate the appropriate file, then click OK.

  8. Click the Add button to add additional databases.
  9. To edit a database path, select the database and click the Edit button.
  10. To remove a database, select it and click the Delete button.
  11. Click Save when you are finished.