Project: InaSAFE

Changelog for version: 3.5.0

Release date: 12 August, 2016


This is a feature release in. The major emphasis in this release has been on polishing and improving the quality of analysis and reporting. There has also been a special emphasis on ash related impact functions. Read on for more details! Please note that as of this release we no longer support keywords formats from InaSAFE 3.2 or older. Version 3.3 and 3.4 keywords are still supported. If your keywords are not recognised, please re-run the InaSAFE keyword wizard to update them.


Reporting


Feature: SPHERE based minimum needs

The SPHERE Project provides a Humanitarian Charter and Minimum Standards in Humanitarian Response. InaSAFE 3.5 adds support for the SPHERE minimum needs profile. You can enable this in Plugins -> InaSAFE -> Minimum Needs Configuration then select the SPHERE profile. Note: You need to restart QGIS after updating the active minimum needs profile.

This feature was funded by DFAT/DMInnovation


Feature: Reporting improvements

Work has started in INaSAFE on the definition of formal standards for report generation. The purpose of this work is to ensure consistency and clarity across all the reports produced by InaSAFE. You can find more details about the standards document here. In InaSAFE 3.5 you will notice that all impact functions now have actions and notes defined, and that the terminology used in actions and notes is more accurate and relevant. You will also notice lots of small touches like the titles for map reports and impact layers using a consistent naming scheme. There is more to come on this front in future releases - we encourage you to participate in the discussions around the reporting standards so that the reports produced are meaningful to you!

This feature was funded by DFAT/DMInnovation


Impact Functions


Feature: Volcanic ash on population impact function added

We have added a new impact function for reporting on the potential impact of volcanic ash fall on population. The function requires:

  • a continuous raster layer for the hazard, where the value in each cell represents the average ash depth per square meter of ash that has been predicted or recorded to fall in that cell
  • a continuous raster layer for the exposure where each cell area represents the number of people in that cell.

The resulting impact layer will be a raster layer showing affected population in the hazard areas. The hazard levels are rated according to the following scale:

  • Very Low: 0.01 - 0.1 cm
  • Low: > 0.1 - 2.0 cm
  • Moderate: >2..0 - 5.0 cm
  • High: >5.0 - 10.0 cm
  • Very High: > 10.0 cm

The impact summary will enumerate how many people populate the area for each hazard level (as shown in the accompanying screenshot).

This feature was funded by DFAT/DMInnovation


Feature: Volcanic Ash on Landcover impact function

We have added a new impact function for reporting on the potential impact of volcanic ash fall on landcover. The function requires:

  • a continuous raster layer for the hazard, where the value in each cell represents the average ash depth per square meter of ash that has been predicted or recorded to fall in that cell
  • a polygon vector layer for the exposure where each polygonal area represents a type of landcover

The resulting impact layer will be a polygon vector layer where each area contains one exposure type at one hazard level. The hazard levels are rated according to the following scale:

  • Very Low: 0.0 - 0.1 cm
  • Low: 0.2 - 2.0 cm
  • Moderate: 2.1 - 5.0 cm
  • High: 5.1 - 10.0 cm
  • Very High: > 10.0 cm

This feature was funded by DFAT/DMInnovation


Feature: Volcanic ash on places impact function added

As mentioned below, InaSAFE 3.5 now supports places exposure layers. We have added a new impact function for reporting on the potential impact of volcanic ash fall on places. The function requires:

  • a continuous raster layer for the hazard, where the value in each cell represents the average ash depth per square meter of ash that has been predicted or recorded to fall in that cell
  • a classified point vector layer for the exposure where each point represents a place. Places can have a type (City, Town, Village etc.) and a population count (indicating how many people live in that settlement).

The resulting impact layer will be a vector point layer showing affected places in the hazard areas. The hazard levels are rated according to the following scale:

  • Very Low: 0.0 - 0.1 cm
  • Low: 0.2 - 2.0 cm
  • Moderate: 2.1 - 5.0 cm
  • High: 5.1 - 10.0 cm
  • Very High: > 10.0 cm

This feature was funded by DFAT/DMInnovation


Feature: Added support of new exposure types: Places and populated places

We have added two new variations of exposure data which can be used with volcanic ash impact functions:

  • Places
  • Populated places

Places are classified exposure layers and are mapped to one of the following class mappings:

  • City
  • Town
  • Village
  • Hamlet
  • Airport

Places are point datasets. When creating the keywords for a point layer using the InaSAFE keywords wizard, you can optionally specify a population column which will be used to compute affected population counts in the impact report. Currently only the new ash on populated places impact function can use place exposure data, but expect more impact functions to support it in future releases.

This feature was funded by DFAT/DMInnovation


Tools


Feature: More image formats supported for organisation logo

Previously only PNG images were supported for InaSAFE customisations of the North arrow and Organisation logos used on maps and reports. Now SVG, PNG, JPEG and GIF images are supported.

This feature was funded by DFAT/DMInnovation


Code Internals


Feature: Performance improvements when working with raster hazard and exposure layers in the map view

We found some places where QGIS rendering was very slow after panning and zooming. This was caused by inefficiencies in the way that InaSAFE validates extents to see if they can be used for an analysis. If you experience similar performance issues in other contexts, please let us know so that we can make InaSAFE more responsive.

This feature was funded by DFAT/DMInnovation


Comments
blog comments powered by Disqus