Project: InaSAFE

Changelog for version: 4.1.0

Release date: 12 May, 2017

This release introduces new functionality for dealing with population vulnerability. It also adds further polish to the reporting outputs and help documentation of InaSAFE.


Feature: Reports are relocatable

In previous versions of InaSAFE it was difficult to take a QGIS project containing analysis results to another computer since the html reports contained fixed paths to the InaSAFE plugin directory on the computer where the reports were generated. In InaSAFE 4.1 the images and styles used in the analysis report are copied into the working directory so that copying the whole working directory to another PC will allow you to open and view the html reports (e.g. by clicking on an impact layer in QGIS) and see the reports with their original formatting.

This feature was funded by DFAT/DMI

This feature was developed by Kartoza

Feature: Improved action and checklist reporting

We have updated the generated report for actions and checklists to make it easier to read. Items are now grouped by topics with subheadings as illustrated in the screenshot here.

This feature was funded by DFAT/DMI

This feature was developed by Kartoza

Feature: Quick save as pdf

It is now possible to generate a quick PDF from any of the report and help dialogs by using the right click menu as illustrated in the screencast here.

This feature was funded by DMI

This feature was developed by Kartoza

Feature: Detailed demographic breakdowns

In InaSAFE 4.1 we introduce new capabilities for rich reporting of displaced people. The new field mapping tool allows you to identify attributes in your exposure population dataset that represent specific vulnerability attributes e.g. infants, disabled people etc. These attributes will then be used to provide detailed breakdowns of the different vulnerable groups, by aggregation area in the final report. In cases (e.g. raster population data) where these attributes are not available as part of the exposure dataset, ratios can be defined in the aggregation layer keywords to specify which proportion of the population in each area comprises each vulnerable group.

There are several components to this new functionality:

  • a new tool on the InaSAFE toolbar called the 'Field Mapping Tool' which can be used with an aggregation or exposure layer that already has InaSAFE keywords defined. This tool lets you quickly adjust the field mappings, ratios etc. that are used for calculating vulnerability report.
  • a new step in the keywords wizard that integrates the Field Mapping Tool described above
  • A new tab in the InaSAFE options dialog that allows you to define the defaults that should be used for ratios.
  • New reporting elements in the reports generated by the InaSAFE analysis that report on the vulnerable groups per aggregation area.

We have made a detailed walk through of this new functionality in the video provided below.

This feature was funded by DFAT

This feature was developed by Kartoza

Impact Functions

Feature: Standardised Tropical Cyclone wind speed averaging time periods

Description : Standardise wind speed averaging time period, per comments in #3802. All wind speed classifications now assume the winds are representative of a 0.2 second gust wind speed. Users will need to convert TC hazard layers to this wind speed averaging time period before importing into InaSAFE. Recommend there be a pre-processor that converts between different wind speed averaging time periods in future releases.

This feature was funded by Geoscience Australia/PacSAFE

This feature was developed by Craig Arthur


Feature: Help system

We have made further improvements to the help system with better indexing of topics and improved visual appearance.

This feature was funded by DFAT/DMI

This feature was developed by Kartoza


Feature: Bug fixes and improvements

  • Fixed an issue where InaSAFE options for organization etc. were not being correctly written to ISO metadata (#3878)

This feature was funded by DFAT/DMI

This feature was developed by Kartoza

blog comments powered by Disqus