Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The Evasuite allows for calculation of different statistics in different subregions. The shape of this subregions is treated by the Evasuite using so-called geopackage files which is an extension of the former known shape files. If you want to execute perform the Evasuiteevaluation in SPICE, you need to specify a geopackage file and the ID name of the attribute used to identify (column of attribute table), which contains the names of the shapes used for evaluation. Both settings are done already pre-specified during the SPICE installation and can be found in the general configuration (an automatic process within the SPICE installation).One can start with the geopackage file received template of the Evasuite: ${SPDIR}/src/eva-suite/config_SUITEgeneral_TEMPLATE.yaml . See there the option polyfile , which is defined in eva-suite_settings, and the option attribregion, which is fixed to NAME_0.

It makes sense to start with the inspection of the geopackage file shipped with the installation of SPICE. It is should be located in ${SPDIR/src/eva-suite/geodata/EvaSuite_PRUDENCE.gpkg. Type the following

...

The output gives you exactly the regions which can be handled by the EvaSuite Evasuite using the SPICE geopackage file of SPICE. This And exactly this subregions can be used to specify the option SUBREGIONS in the https://hereon-coast.atlassian.net/wiki/spaces/SPICE/pages/983205.

If you want to handle more regions, you need to do two steps:

  1. extend the existing geopackage file and write to a new geopackage file

  2. specify the new geopackage file in the SPICE-environment.

...

Step 1: Extend geopackage file by user-specified subregions

There are two possibilities to extend the geopackage file delivered with SPICE.

...

Code Block
evasuite --addpolygondb ${newgeopackage} ${newattrib} ${newregionnames} ${oldgeopackage} ${oldattrib} ${resultresgeopackage}

The old geopackage file oldgepackage with regions stored under the attribute oldattrib is extended by the content of the new geopackage file newgeopackage. With respect to the content of the new geopackage file, one has to specify the attribute newattrib and the values of the attribute newregionnames, which are simply the names of the regions stored in the new geopackage file. You can specify a single string or a list of strings separated by a comma. The final file is stored in result and the final attribute is the same as oldattrib.

After successful execution of the command above, you get a list of all polygons stored in the result file. The names can then be used as subregions in the https://hereon-coast.atlassian.net/wiki/spaces/SPICE/pages/983205. resgeopackage file.

B) Add subregions using a simple ascii file

...

Code Block
evasuite --addpolygonascii ${newwktfile} ${newattrib} ${oldgeopackage} ${oldattrib} ${resultresgeopackage}

It is the nearly the same procedure as for case A), but the final file is extended by ALL regions stored in newwktfile under the attribute newattrib.

After successful execution of the command above, you get a list of all polygons stored in the result resgeopackage file.

Step 2: Define a new geopackage file for SPICE-enviroment

The names can then of new shapes stored in the new geopackage file (see Step 1) can be used as subregions in the https://hereon-coast.atlassian.net/wiki/spaces/SPICE/pages/983205. Moreover, the new geopackage file has to be defined in eva-suite_settings too.