Project: InaSAFE

Changelog for version: 2.1.0


This is a new feature release for InaSAFE.


Reporting


Feature: Added data driven age postprocessing support

With this new feature you can specify data driven age ratios to use when carrying out aggregation. The ratios for gender and age can be defined per aggregation area using either a global (predefined) value, or by selecting a column in the attribute table. There are also validation checks to ensure that the combined age ratio (when using global default option) does not exceed one.


Impact Functions


Feature: New faster version of raster flood impact on roads

We have added a new faster implementation of 'flood impact on roads' impact function that uses raster hazard data. This improves the performance of the algorithm during the calculation of polygons per raster threshold.


Tools


Feature: Updated keywords editor user interface revised

The keyword editor user interface has been revised, grouping options into tabs in order to improve the layout of the dialog. The Post-processing tab is disabled except when you have defined the current layer to be a post-processing layer.


Feature: Analysis extents pre-and-postview tool

With this hand tool you can see what the next analysis extent will be (based on the intersection of hazard layer, exposure layer and current view extents). This is shown as a green rectangle on the map. When you have completed an analysis, the extents of the last run analysis are show as a red 'postview' rectangle.


Feature: New keywords wizard

This is the first of three wizards that we will be adding to the InaSAFE user interface (the other two will arrive in subsequent releases). The keywords wizard provides an alternative to the keywords editor for creating keywords files for hazard, exposure and post-processing layers. The wizard uses rich new metadata which have been added to each impact function in order to ensure that the keywords assigned to a given layer will always be correct according to their context. For example, the wizard will prevent you from assigning a hazard category to a line layer since there are currently no supported line based hazards.


Comments
blog comments powered by Disqus