Data

Tools

Indexes

Applications

Experiments

Open Sustainable Technology

A curated list of open technology projects to sustain a stable climate, energy supply, biodiversity and natural resources.

Recent Releases of InaSAFE

InaSAFE - InaSAFE 5.0.3

This is a bug fix release which ensures InaSAFE continues to work on the latest QGIS versions (currently up to QGIS 3.22).

Work funded by Kartoza and DHI Group.

Climate Change - Natural Hazard and Storm - Python
Published by timlinux over 3 years ago

InaSAFE - Version 5.0.1

This is a bugfix release for InaSAFE 5.

Changelog version 5.0.1:

  • Fix contour calculation in QGIS 3.4
  • Fix inconsistent aggregation count behaviour
  • Fix hazard preparation geometries. Now automatically validate hazard geometries
  • Fix wrong clipping dtype for raster hazard
  • Fix minimum needs value reports

Climate Change - Natural Hazard and Storm - Python
Published by lucernae over 5 years ago

InaSAFE - Version 5.0.0

This release includes support for QGIS 3.x.

QGIS 3.2 is required as a minimum, but we recommend that you use QGIS 3.4.1 or greater.

This release is a direct port of the 4.4.0 codebase with the following additional features added:

Version 5.0.0:
* QGIS3 port with Python 3 and Qt 5
* Enable line for structure exposure
* Add Tonga and Fiji currency and administration boundary definition
* Possibility to simply add postprocessors only for a certain combination of hazard and exposure

Climate Change - Natural Hazard and Storm - Python
Published by timlinux over 6 years ago

InaSAFE - Version 5.0.0-alpha-2

Changelog Version 5.0.0-alpha

  • Port InaSAFE to use QGIS3
  • Set minimum QGIS version to 3.2

Climate Change - Natural Hazard and Storm - Python
Published by ismailsunni almost 7 years ago

InaSAFE - Version 5.0.0-alpha

Changelog Version 5.0.0-alpha

  • Port InaSAFE to use QGIS3

For the better usage, please use it with the latest QGIS available (3.2 or newer)

Climate Change - Natural Hazard and Storm - Python
Published by ismailsunni almost 7 years ago

InaSAFE - Version 4.4.0

Version 4.4.0:

  • Add Geonode uploader
  • Add back Sentry configuration (need to be enabled in your settings)
  • Set precision to 6 decimal for minimum needs.
  • Add expressions for retrieving each section of the report (#4986)
  • Update to support InaSAFE run in headless mode

See more at http://changelog.inasafe.org/en/inasafe/version/4.4.0/

Climate Change - Natural Hazard and Storm - Python
Published by ismailsunni almost 7 years ago

InaSAFE - Version 4.3.4

This is a bug fix only release:

  • Add template extent setting as a property of Impact Report.
  • Fix no expressions on infographic on multi-exposure analysis.

Climate Change - Natural Hazard and Storm - Python
Published by timlinux about 7 years ago

InaSAFE - Version 4.3.3

This is a bug fix release which fixes some expressions when using multi-exposure analysis.

Climate Change - Natural Hazard and Storm - Python
Published by timlinux about 7 years ago

InaSAFE - Version 4.3.2

Changelog version 4.3.2:

  • Run the impact function if we have 0 feature exposed
  • Fix multiexposure dialog when you launch it twice
  • Add more extra keywords for flood hazard

Climate Change - Natural Hazard and Storm - Python
Published by ismailsunni about 7 years ago

InaSAFE - Version 4.3.1

Changelog version 4.3.1:

  • Add version number in the help doc #4872.
  • Enable Earthquake MMI scale for place exposure #4875.
  • Fix the behaviour of batch runner output directory.
  • Fix missing earthquake extra keywords in wizard.

Climate Change - Natural Hazard and Storm - Python
Published by ismailsunni over 7 years ago

InaSAFE - Version 4.3.0

Version 4.3:

  • New multi exposure tool where you can run one hazard on many exposures at the same time and get a combined report
  • New dam break hazard
  • Add metadata converter tool to version 3.5 to make it work with GeoSAFE
  • Add InaSAFE Profile to set custom affected and displacement rate
  • Add a warning if another plugin is conflicting with InaSAFE on the file system
  • Special tool for reporting in the multi exposure dialog to set a custom layer order
  • Add InaSAFE welcome message
  • Add a warning if another plugin is conflicting with InaSAFE on the file system
  • Tidy up settings dialog
  • Support population count in place exposure
  • Use percentage for ratio in the GUI
  • Add total exposed field
  • Add Evacuation centres in buildings and places classifications
  • Add bearing, distance and cardinality postprocessors if we run an earthquake on places
  • The impact layer from an earthquake on places is ordered by distance
  • Add new QGIS expressions to fetch information in QGIS Impact layers or keywords
  • HTML expressions for reporting usage.
  • Impact Function and Multi-Exposure Impact Function serialization
  • Add new method to generate a report in ImpactFunction object
  • Bring back the old behaviour of generating report. (option to choose custom template)
  • Map report and general report for Multi-Exposure Impact Function.
  • Use aggregation CRS instead of exposure CRS or map canvas CRS if no aggregation layer is provided
  • Add extra keywords for supporting rich reporting (e.g. earthquake's epicenter location, volcanic ash location)
  • Tidy up metadata (remove unused properties)
  • Creating contour for earthquake as preprocessor.
  • Improve code layout (Flake8, PEP 257, PEP8, SideCI ...)
  • Fix various bugs, like in summary calculation, keyword wizard, productivity post processors, dock

For a detailed overview of these new features please see: http://changelog.inasafe.org/en/inasafe/version/4.3.0/

Climate Change - Natural Hazard and Storm - Python
Published by ismailsunni over 7 years ago

InaSAFE - Version 4.2.5

This is a bug fix release and also adds the metadata convertor:

  • Fix bug Exception reading keywords #4632
  • Fix bug ratio = 0 when the data is integer #4669
  • Fix using custom disclaimer, north arrow, and logo #4671
  • Fix bug when population == 0 #4659
  • Add metadata converter from metadata version 4.x to version 3.5

Climate Change - Natural Hazard and Storm - Python
Published by timlinux over 7 years ago

InaSAFE - Version 4.2.4

This is a bug fix release:

- Move resources and translation to safe package.
- Fix bug Analysis Detail from Landcover Impact Report not shown in Bahasa version #4487
- Fix several typos and translation issue in Bahasa Indonesia
- Cleaning up code in the wizard #4485

Climate Change - Natural Hazard and Storm - Python
Published by timlinux over 7 years ago

InaSAFE - Version 4.2.3

This bug version release fixes these issue:

  • Fix failed to assign keyword by using IFCW
  • Fix wrong layer intersection checking in IFCW
  • Earthquake fatality model selection
  • Update definition for Petabencana flood class "use caution"
  • Fix wizard layout
  • Fix CRS helper expression

Climate Change - Natural Hazard and Storm - Python
Published by ismailsunni over 7 years ago

InaSAFE - Version 4.2.2

This is a bug fix release that fixes the error when trying to install InaSAFE from the plugin manager.

Climate Change - Natural Hazard and Storm - Python
Published by ismailsunni over 7 years ago

InaSAFE - Version 4.2.1

This is a bug fix release that fixes missing translations for French and fixes an issue with CRS not being displayed properly in the map pdf's produced by InaSAFE.

Climate Change - Natural Hazard and Storm - Python
Published by timlinux over 7 years ago

InaSAFE - Version 4.2.0

Minor release:

  • Reporting : Expose provenance; as project variables for easy reporting
  • Reporting : Re-implemented infographics as composer templates
  • Reporting : Enable atlas generation on reporting
  • Reporting : Added many custom InaSAFE specific QGIS Expressions to make reporting easier.
  • Reporting : Fixed bug where maps in report were blank when using OTFP
  • Impact Functions : Support for Land Cover economic impact calculations
  • Impact Functions : Added support for working with multi-band rasters
  • Impact Functions : Removed separate workflow for Earthquake impact functions
  • Impact Functions : Allow exposure data driven classification
  • Tools : PR #4379 Show uniquness in the aggregation ID field in keyword wizard
  • Documentation : Wizards now have context sensitive help
  • Code Internals : Command line and 'headless' code moved to their own repos

For a detailed overview of these new features please see: http://changelog.inasafe.org/en/inasafe/version/4.2.0/

Climate Change - Natural Hazard and Storm - Python
Published by ismailsunni over 7 years ago

InaSAFE - Version 4.1.3

This is a bug fix release only:

  • Added a small improvement to support user templates in their home directory

Climate Change - Natural Hazard and Storm - Python
Published by timlinux almost 8 years ago

InaSAFE - Version 4.1.2

This is a bug fix release only:
- Avoid recomputing analysis extent when we pan/zoom with an aggregation layer
- Fix issue when using a continuous hazard dataset (#4289)
- Fix for cases where a pie chart slice calculation has a divide by zero error (#4289)
- Fix issue where Keywords Wizard is not enabled if old keywords exist (#4284)
- Fix python exception when using InaSAFE in French

Climate Change - Natural Hazard and Storm - Python
Published by timlinux almost 8 years ago

InaSAFE - Version 4.1.1

This is a bug fix release that addresses the following issues:

835bb9b05 (HEAD -> develop, upstream/develop, origin/develop, origin/HEAD) Use QGIS user directory for metadata.db
d493337de Fix failed unit test.
bc6da7d21 Remove unused method in KeywordIO.
bc9a13b6f Fix #3751. Set to use default db path from definition.
74ea18b28 Rename metadata for output layer. Add other output explicitly to metadata mapping.
9c03d75d5 Remove unused code in metadata utilities.
9eaf61650 Update translation.
69d6a70bd update translations
d89e5efde Fix #3857. Ignore filter in path.
75741ab65 Fix #4248. Expression.
db20d143e Update for Badan Geologi landcover classification
e9a01d79c update metadata
ba172848e update French Translations
4214562c1 fix some strings in Python
fe39d1614 add pregnant and lactating displaced to the count fields (#4244)

Climate Change - Natural Hazard and Storm - Python
Published by timlinux almost 8 years ago

InaSAFE - Version 4.1.0

This is a feature release that builds on the work we have done in version 4.0, adding features including (but not limited to):

  • Reporting : Improved action and checklist reporting
  • Reporting : Quick save as pdf
  • Reporting : Detailed demographic breakdowns
  • Reporting : Inclusion of concept definitions under tables
  • Reporting : New provenance report
  • Impact Functions : Standardised Tropical Cyclone wind speed averaging time periods
  • Impact Functions : Improvements to earthquake options panel
  • Impact Functions : Options for demographic breakdowns
  • Impact Functions : Fatalities calculations in earthquake on vector population
  • Tools : Help system improvements
  • Documentation : Developer guide for adding a new hazard
  • Issues : Bug fixes and improvements

For a detailed overview of these new features please see: http://changelog.qgis.org/en/inasafe/version/4.1.0/

Please note: The experimental infographic reports included in version 4.0 have been temporarily removed while we work on a better implementation.

Climate Change - Natural Hazard and Storm - Python
Published by timlinux almost 8 years ago

InaSAFE - Version 4.0.2

Small bug fix release to resolve an issue with 4.0.1 not installing on 2.18.5

Climate Change - Natural Hazard and Storm - Python
Published by timlinux about 8 years ago

InaSAFE - Version 4.0.1

Changelog

  • Fix SSHWS classification
  • Add option to launch keyword wizard on shakemap importer
  • Change fallback font to Arial in Windows
  • Create fallback header if affected field not found
  • Match petabencana's keyword with its classification (#4056)
  • Fix #4049. Handle more types in metadata copying.
  • Change calculation of additional rice #3607
  • Improve translation for IF name
  • Add translated analysis question support
  • Add sum ratio checker in option dialog.
  • Fix issue #3887: Add ordering for exposure classes in aggregation
  • Fix issue #3998: update qgis report templates
  • Improvement in infographic
  • Disable GDAL bash window on windows
  • Fix hazard with many units
  • Enable the displaced raster to be the impact layer
  • Fix title and displaced raster
  • Add missing notes for EQ impact function
  • Enable inasafe for QGIS 2.14, 2.16 and 2.18
  • Generate map report in IFCW too
  • Fix unicode issue in layer title

Climate Change - Natural Hazard and Storm - Python
Published by ismailsunni about 8 years ago

InaSAFE - Version 4.0.0 Final

This is a new major version release of InaSAFE.

2017-03-06 00_33_28-inasafe

Changelog

  • Complete overhaul of the InaSAFE code base
  • Deprecated numpy / matrix based geometry manipulation
  • New reporting system including Jinja2 support
  • Experimental support for Infographics
  • Removed all impact functions in favour of a shared workflow for all hazards
  • Added support for exposure specfic thresholds in hazard metadata
  • Produce rich data outputs instead of simple HTML reports
  • Added new hazard support for Tropical Cyclone
  • Extensive updates to the help reference and a new help browser
  • Removal of all logic that uses interpolation to assess impact level
  • Application of standards to reporting and calculations for more consistent presentation
  • Ability to work with larger datasets in many cases (just be patient while analysis runs)
  • Speed ups and improvements to many parts of the code base
  • Improvements to the batch runner tool
  • Improvements to the shake grid importer tool
  • Port of the minimum needs tool to use our new architecture
  • Added support for analysis of irregular areas (as defined by aggregation layer)
  • Features or population outside of aggregation areas are no longer counted as part of the total exposure count
  • Added support for working with data subsets
  • Analysis no longer works only with local file sources
  • All geometry operations are performed using the QGIS API now
  • QGIS layers list items now have a context menu for InaSAFE
  • Input layers no longer need to be in EPSG:4326
  • Moved realtime code to its own repository
  • Improved error handling system
  • Added profiling for all analysis steps so we can easily identify performance bottlenecks
  • Improved how partial overlaps with a hazard are managed (feature is assigned highest impact zone)
  • Generate rich provenance for use in reporting
  • Generate multiple sub products (impact layer, aggregation by hazard layer)
  • PDF Reports are generated directly once analysis completes
  • Earthquake sub-algorithm selection has been moved to the InaSAFE options dialog
  • ITB Bayesian algorithm is now default for earthquake
  • Earthquake analysis map output is now a boolean layer indicating if a cell contains displaced people
  • Many, many more improvements...

Known Issues

  • Infographics may in some cases exceed the space provided on a landscape A4 page. We recommend for now that you use the HTML infographic rather.
  • Some standards are still being developed and applied, we will be continually improving on this in upcoming releases.
  • Whilst we have made every effort to ensure that all reports produce accurate and reliable information, we encourage you to validate the results if at all possible.
  • Some analysis results may differ from those of previous versions of InaSAFE since the underlying methodology has changed.
  • Displacement rates are generalised estimates. Please help us to refine these rates if you have expert knowlege on the displacement rates that result when a particular hazard type occurs.

Climate Change - Natural Hazard and Storm - Python
Published by timlinux about 8 years ago

InaSAFE - Version 4.0.0beta3

This release fix issue when InaSAFE can not be loaded to QGIS in the previous release InaSAFE Version 4.0.0 Beta 2!

Climate Change - Natural Hazard and Storm - Python
Published by ismailsunni about 8 years ago

InaSAFE - Version 4.0.0 Beta2

This release is an interim build on the way to version 4.0.0

There are many fixes in this release over the previous beta including:

  • Earthquake support is back
  • Reports for table and map are working
  • Detailed help and review of definitions
  • Batch runner improvements
  • Many wizard improvements
  • Stripped out almost all legacy code (numpy geometric code, safe_layer etc.) and we exclusively use QGIS for analysis now (with a dollop of GDAL)
  • Analysis against remote datasets (PostgreSQL tested)
  • Removal of realtime logic to its own repo
  • Disabled some impact functions that don't make sense
  • Many other tweaks and improvements to InaSAFE

Note that this release is not production ready and in particular the numerics have not been well tested and verified. Please do not deploy in any real world work yet.

Climate Change - Natural Hazard and Storm - Python
Published by timlinux over 8 years ago

InaSAFE - Version 4.0.0 Beta

This is the second preview release for InaSAFE 4.0.0. It adds (among other things):

  • many fixes to the analysis workflow
  • reinstated support to the Impact Function centric wizard workflows
  • reinstated print generation using our new reporting architecture
  • fixes and improvements to the batch runner tool

Climate Change - Natural Hazard and Storm - Python
Published by timlinux over 8 years ago

InaSAFE - Version 3.5.4

  • Fix error when multipart to single part produces none geometries.

Climate Change - Natural Hazard and Storm - Python
Published by ismailsunni over 8 years ago

InaSAFE - Version 3.5.3

This is a bug fix release to resolve an issue with reporting in Earthquake impact calculation. See issue #3489

Climate Change - Natural Hazard and Storm - Python
Published by timlinux over 8 years ago

InaSAFE - Version 4.0.0.alpha

Changelog for InaSAFE 4.0.0.alpha

  • Implementation of the new architecture for InaSAFE v4.0
  • Use can select some aggregation areas (Irregular clipping). Do not forget to enable this option in inasafe settings (use selected features only)
  • Not truncated field names (geojson), geopackage soon
  • Set the keywords from a right click on the layer in the legend
  • QGIS layer with rich attribute table
  • Many outputs : exposure, aggregate hazard, aggregation, analysis, exposure breakdown
  • Profiling table
  • Debug mode
  • New inputs : raster landcover for instance and more I think
  • New fields (rate, absolute values)
  • Classify continuous layer using threshold
  • One and only one IF !
  • Wizard support extra post processor and we can add easily a new one

Known Issues

  • No minimum needs support yet
  • Reporting summary calculation not working for counts and ratios (so not working well for population reporting yet)
  • Union algorithm is broken and can produce incorrect results or python errors (problem is upstream in QGIS too)
  • No support yet for Earthquake on population
  • User extents not yet supported
  • Continuous raster population does not show breakdown of population by hazard class for each aggregation area
  • No densities supported
  • Hazard modeling tool
  • Impact function wizard still not working
  • Keywords need to be redefined for v4.0
  • Translations don't exist yet
  • Minimum needs implementation needed for post processors

Switching Tag or Branch

In this version, we introduce git submodule to manage parameters package easier. This will affect on how you switch from non-submodule branch / tag to branch / tag with submodule or vice versa.

Switch from non-submodule branch / tag to branch / tag with submodule

  • delete safe_extras/parameters directory
  • switch branch or tag (e.g. by using git checkout or other usual way)
  • run git submodule init
  • run git submodule update

Switch from branch / tag with submodule to non-submodule branch / tag

  • delete safe_extras/parameters directory
  • switch branch or tag (e.g. by using git checkout or other usual way)

Anytime you switch to branch / tag with submodule, it's recommended to run git submodule update to make sure you have the latest submodule package. We don't update this package frequently, so you don't need to do it often.

Climate Change - Natural Hazard and Storm - Python
Published by ismailsunni over 8 years ago

InaSAFE - Version 3.5.2

Changelog:

  • Fix TypeError when running volcanic ash in Bahasa Indonesia in QGIS (#3164)

Climate Change - Natural Hazard and Storm - Python
Published by ismailsunni over 8 years ago

InaSAFE - Version 3.5.1

Changelog:

  • Better Zero Impact message in Impact Function Centric Wizard (#3151)
  • Handling NULL value in exposure layer (#3153)

Climate Change - Natural Hazard and Storm - Python
Published by ismailsunni over 8 years ago

InaSAFE - Version 3.5.0

Changelog for InaSAFE 3.5.0

  • Tools : More image formats supported for organisation logo
  • Impact Functions : Volcanic ash on population impact function added
  • Impact Functions : Volcanic Ash on Landcover impact function
  • Impact Functions : Volcanic ash on places impact function added
  • Impact Functions : Added support of new exposure types: Places and populated places
  • Reporting : SPHERE based minimum needs
  • Reporting : Reporting improvements
  • Code Internals : Performance improvements when working with raster hazard and exposure layers in the map view
  • Many bug fixes and improvements

Climate Change - Natural Hazard and Storm - Python
Published by timlinux over 8 years ago

InaSAFE - Version 3.4.2

This is a bug fix release:

  • fixed regression with legacy keywords not being migrated
  • fixed tests failing because of gdal python exception handler

Climate Change - Natural Hazard and Storm - Python
Published by timlinux almost 9 years ago

InaSAFE - Version 3.4.1

Version 3.4.1 of InaSAFE is now available. This is a bug fix release only:

3.4.1 - Speed improvements for tsunami and flood impacts on roads
3.4.1 - fix #2884 mistake in the tsunami legend
3.4.1 - fix #2899 impact layer should draw over the hazard layer
3.4.1 - remove 'by each hazard zone'
3.4.1 - fix #2927 enable lineEdit if the checkbox is toggled in settings
3.4.1 - fix #2925 set the layer visible when we add it the map canvas
3.4.1 - remove empty lines from postprocessing outputs #2318
3.4.1 - update notes about no data and 0
3.4.1 - add setLayerVisible to the fake qgis legend interface
3.4.1 - fix sentence about no data in the report
3.4.1 - add missing thousands separator
3.4.1 - fix legend order when layer is None
3.4.1 - Fix wizard compatibility with recent QGIS versions. Issue #2906
3.4.1 - Handle KeyError in keywords. Issue #2908
3.4.1 - Handle special character in XML. Issue #2898
3.4.1 - Fix failing dock test on QGIS 2.15 (and possibly earlier versions)
3.4.1 - Fix mistake in the tsunami legend. Issue #2884
3.4.1 - Fix the impact layer should draw over the hazard layer. Issue #2899
3.4.1 - Remove 'by each hazard zone' in the legend
3.4.1 - Fix enable lineEdit if the checkbox is toggled in settings #2927
3.4.1 - Fix set the layer visibility when we add it the map canvas #2925
3.4.1 - Remove empty lines from postprocessing outputs #2318
3.4.1 - Update notes about no data and 0
3.4.1 - Add missing thousands separator in the building report

Please note that support for old .keywords files was also removed in this bug fix release.

Climate Change - Natural Hazard and Storm - Python
Published by timlinux almost 9 years ago

InaSAFE - Version 3.4.0

We are pleased to announce the release of InaSAFE 3.4. This release has the following highlight features:

  • Raster tsunami on landuse polygons
  • Generic hazard classes on landuse polygons
  • Value mappings in keywords wizard for building and roads attribute classes
  • Storage of analysis report outputs in JSON rather than HTML
  • Tidy up of context help text
  • Various bug fixes

Changelog is here: http://changelog.inasafe.org/en/inasafe/version/3.4.0/

Climate Change - Natural Hazard and Storm - Python
Published by timlinux almost 9 years ago

InaSAFE - Version 3.3.3

This is a bug fix release:

  • 3.3.3 Fix issue #2724 - InaSAFE Intermediate Ex. errors: Python error
  • 3.3.3 Fix issue #2759 - Exception when keyword missing from keywords

Climate Change - Natural Hazard and Storm - Python
Published by timlinux almost 9 years ago

InaSAFE - Version 3.3.2

  • Fix issue #2720 - Fix incorrect keyword requirements for tsunami impact on roads
  • Fix if the OSM downloader issue - if request is cancelled, the http response is none
  • Handle HTTP 509 if the overpass is busy
  • Fix #2722 fix QGIS 2.14 issue with delete network reply after a download

Climate Change - Natural Hazard and Storm - Python
Published by timlinux about 9 years ago

InaSAFE - Version 3.3.1

  • Fix issue with PetaJakarta downloader

Climate Change - Natural Hazard and Storm - Python
Published by timlinux about 9 years ago

InaSAFE - Version 3.3.0

Code Internals

Feature: Deep support for ISO19115 metadata

Metadata is a core part of the way we manage data and understand capabilities in InaSAFE. Metadata is used to indicate if a layer is hazard, exposure, aggregation or an impact layer. In the past, we used our own internal system for maintaining this metadata, using simple text files to hold key-value pairs. Using our own metadata system has a number of issues - it means that we can't easily interchange metadata with other GIS systems, and it means we spend effort re-inventing the wheel for recording basic metadata elements. We also encounter some technical limitations when using our home rolled metadata format - especially for our future plans where we intend to provide rich data for analysis results.

Thus InaSAFE 3.3 introduces a change from the .keywords format used in the past to the ISO19115 metadata format. As a user of InaSAFE, we have tried to keep this transparent to you. When you first load an InaSAFE layer created with an older InaSAFE version your .keywords file will be automatically converted to a .xml metadata file. This new file should be readable by online metadata tools and tools such as ESRI's ArcCatalogue.

Impact Functions

Feature: Classified polygon hazard on polygon people

This new experimental impact function can be used when you have people represented as census areas and wish to understand how many people may be affected. For example you may have flood polygons classified as 'wet' and 'dry' and then compute the number of people affected by 'wet' polygons. We consider this impact function as experimental and welcome your feedback with suggestions and proposed improvements.

Feature: New tsunami specific building impact function

Now we have a specific impact function for tsunami on buildings. The key difference for this IF compared to flood is that Tsunami impact on buildings now has 3 classes (1,3 and 8 metres).

Feature: New tsunami specific roads impact function

We have added a specific impact function for tsunami on roads. The key difference for this IF compared to flood on roads is that a tsunami on roads uses multiple thresholds (to classify road sections as dry, low, medium and high impact), and that reporting is tsunami specific.

Feature: Bayesian ITB Earthquake impact function

This new Impact Function uses Bayesian Fatality curves to provide a more realistic interpretation of how many people might be affected per raster cell at each MMI level. This model was developed by Institut Teknologi Bandung (ITB) and implemented by Dr. Hyeuk Ryu, Geoscience Australia.

Reference:

An Empirical Fatality Model for Indonesia Based on a Bayesian Approach
by W. Sengara, M. Suarjana, M.A. Yulman, H. Ghasemi, and H. Ryu
submitted for Journal of the Geological Society

Tools

Feature: New tool to add an OSM tile layer

Having a standard contextual backdrop layer in InaSAFE can make it easier to see what the surrounding area and infrastructure consists of when doing an analysis. Many people use the OpenLayers plugin to add a Google Maps layer as a backdrop for this purpose. However there is an issue with the OpenLayers plugin in that it does not lend itself to printing very well due to its underlying architecture (this is also one of the reasons it is not shipped as a 'core' plugin in QGIS). For this release we have added a new tool that will load an OpenStreetmap layer as a backdrop layer in your project. This map layer should be fully printable. Please note that for best results you should use the OSM tile layer at the standard OSM scales (see this article for details).

Feature: PetaJakarta Flood Download Tool

This tool will allow you to fetch a live snapshot of the PetaJakarta.org flood status and save it as a shapefile (complete with keywords ready for use in InaSAFE). The downloaded layer can automatically be named to include the date and time of the download - useful for comparing flood affected areas over time. PetaJakarta provides a number of different downloadable products. For this tool we use the areas [officially considered flooded[(https://petajakarta.org/banjir/en/data/v2/#flooded), where each polygon is rated according to this table:

State Description
0 Not flooded
1 Use caution
2 Water depth from 0-70cm
3 Water depth from 71-140cm
4 Water depth > 140cm

InaSAFE can use flooded areas either as 'wet/dry' areas or as 'high/medium/low' hazard areas. We have opted to provide metadata using the second scheme with the following mappings:

State Hazard level
0 Low
1 Low
2 Low
3 Medium
4 High

You can adjust these classifications as needed by using the InaSAFE keywords wizard. Lastly note that the PetaJakarta tool is specific to Jakarta. It can be found in plugins -> InaSAFE -> Add PetaJakarta Flood Layer

Feature: General fixes

  • The default threshold for impact on people is now 0.7m. This is because the force of the water is much greater and so can cause substantial damage even if the water height is lower than a normal flood.
  • Add parameter for minimum number to create group of building #2468
  • New default parameter for IF Tsunami Raster for Building (New IF) #1237
  • Use affected building value in action checklist #2410
  • Fix result on detail table in Earthquake population IF #2235
  • Make raster cell with zero value transparent #2529
  • Fix small bug showing QDateTime #2585
  • Add unaffected population in impact report #2530
  • Fix small bug showing QUrl #2569
  • Fix typo (apostrophes) in action check list #2571
  • Round number in action check list #2570
  • Fix InaSAFE OpenStreetMap Downloader cannot download relation #2576
  • Create a uniform order in impact report #2545
  • Update action check list #2389
  • Sort hazard classification on impact report (And make IF uses vector classification from hazard layer properly) #2385
  • Better impact report for IF volcano point #2390
  • Add unit in radius for IF Volcano point #2425
  • Migrating to metadata 3.3

Installation

  • This plugin will be published in the QGIS Plugin repository.
  • You can also install this plugin using the windows installer provided below. Please note that uninstalling the exe based plugin will overwrite any data that exists in the InaSAFE plugin directory. Thus we do not recommend using it if you have a git checkout in your QGIS plugins directory.

Climate Change - Natural Hazard and Storm - Python
Published by timlinux about 9 years ago

InaSAFE - Version 3.2.6

This is a bug fix release to improve compatibility with keywords created in InaSAFE 3.2.x and those created in the upcoming 3.3.x releases.

  • Add handler if found invalid xml file for version 3.2
  • Add test data for layer with keyword version 3.3 and add unit test for it.

Windows users can install using the attached executable installer. Users on other systems will find the upgrade available in the QGIS plugin manager shortly.

Climate Change - Natural Hazard and Storm - Python
Published by timlinux over 9 years ago

InaSAFE - Version 3.2.5

Fixes / changes in this release:

  • Adds data source and CRS to the keywords list in dock
  • Wizard: ged rid of eval() statements #2329
  • Use Date Picker in Keywords Wizard #2499
  • Fix Keywords Wizard crashes on repeated use #2514
  • Fix Crash Minidump when try to use InaSAFE keyword editor twice #2467
  • Fix #2515 BUG : Can Not Use the Wizard (because No module named qgsdatetimeedit)
  • Fix serializing classified raster values
  • Fix #2504 - exception raised when messaging cell contains nested table or bullet list due to slashes param not being accepted by table class to_html() method.
  • Fix Python error in PDF generator and Open in Composer using IFCW #2532
  • Fix Python bug when creating a pdf map #2523

Climate Change - Natural Hazard and Storm - Python
Published by timlinux over 9 years ago

InaSAFE - Version 3.2.4

  • Working implementation of on-the-fly-projection for polygon flood on building points/polys. fix #2475
  • [Wizard] Add Keywords Creation Wizard confirmation step. Fixes #2422
  • [IFCW] After registering keywords in the KW sub-thread, don't display again the step from where it was called. Fixes #2347
  • New windows installer for the plugin (see downloads below)
  • Fix some translation issues

Climate Change - Natural Hazard and Storm - Python
Published by timlinux over 9 years ago

InaSAFE - Version 3.2.3

This is a bug fix release - it adds missing support for polygon flood on building points.

Climate Change - Natural Hazard and Storm - Python
Published by timlinux over 9 years ago

InaSAFE - Version 3.2.2

This is a patch level release that adds:

  • Added context help for all dialogs
  • Added Thailand profile to OSM downloader
  • Fixed issue with pushing python faults to sentry

Climate Change - Natural Hazard and Storm - Python
Published by timlinux over 9 years ago

InaSAFE - Version 3.2.1

This is a patch level release that adds:

  • Global clean up of reports for consistency, terminology and style
  • Nicer formatted message in dock when no impact function is available
  • Bugfix: Don't show impact layers in wizard chooser

Climate Change - Natural Hazard and Storm - Python
Published by timlinux over 9 years ago

InaSAFE - Version 3.2.0

|image0|

Changelog for InaSAFE 3.2.0

In this release we have made over 1200 commits to our code base, making
improvements to almost every part of InaSAFE. Whilst some of these
improvements are visible through the user interface and reports we
generate, the vast majority of the changes in this release are
architectural improvements, bug fixes and improvements to the speed and
quality of the code that underlies InaSAFE. This release has also been
subject to a large Quality Assurance review - we are working very hard
to improve the quality and consistency of analysis results with each
release.

|Validating reports for InaSAFE 3.2|

We have not only been working hard on the main InaSAFE plugin, but also
in revamping the InaSAFE.org <http://inasafe.org>__ web site, building
a new InaSAFE realtime <http://realtime.inasafe.org>__ web site,
sprucing up our user map <http://users.inasafe.org>__ (please add
yourself there if you use InaSAFE!), overhauling the documentation.

InaSAFE is an Open Source project and we would like to encourage
organisations and individuals interested in the project to get involved.
Visiting our chat room <https://gitter.im/AIFDR/inasafe>__ or
contacting us via [email protected] is a good place to start the
conversation!

|image2|

Impact Functions

Feature: Impact functions


In InaSAFE 3.2 we have not added any new Impact Functions but we have
made many refinements and improvements to the existing ones. We have
also removed one Impact Function
(``inundation/flood_raster_road_qgis_gdal``) to remove duplication and
renamed one (``inundation/flood_raster_road`` renamed to
``inundation/flood_raster_road_qgis``) to make the nomenclature more
consistent. As of version 3.2 we have 19 impact functions covering
**generic**, **inundation** (flood and tsunami), **earthquake** and
**volcano** hazards (see image for a complete list or `this
gist <https://gist.github.com/timlinux/5a5391c7edf004e587a8>`__ for the
text version).

We have put a lot of work into improving the underlying architecture of
Impact Functions so that code reuse is maximised and that they are
described with rich, expressive metadata.

|image3|

Issues
------

Feature: Known issues for 3.2 release

InaSAFE is a work in progress. We are trying to make the best and most
robust software possible, whilst still making regular incremental
improvements available to you our beloved user. The following issues
should be borne in mind whilst using InaSAFE 3.2:

  • In some cases the reported numbers for the entire analysis may
    differ from aggregation totals     due to the fact that the entire
    analysis may include data not covered by any aggregation area.
  • In some cases the report table may be truncated if it includes
    too many categories to fit within the width of the page. We are
    working on ways to resolve this issue in the future by for example,
    reducing the number of classes reported on, presenting data in other
    ways such as charts / infographics etc.
  • Keywords created in older versions of InaSAFE will not be
    compatible with InaSAFE 3.2     - you will need to recreate your
    keywords using the keyword wizard.
  • On the fly reprojection of data is not yet reliable / usable.
  • Some Impact Functions make use of interpolation to determine e.g. the
    flooded status of a building. This interpolation may make the
    results difficult to interpret     in some cases. For example, a
    building may be marked as flooded on the map even though it appears
    to not be overlaying a flooded data cell in the flood raster.
  • Map legends do not remove outliers. In some cases a single high
    value pixel (e.g. number of people affected by flood in a cell) may
    cause the scaling of the legend to be skewed in a way that makes it
    difficult to discern localised minima / maxima.

Reporting

Feature: New print templates


For this release, we have added several new print composer templates
that you can use to generate reports after an impact function has run.
We welcome additional contributions of templates, so please share your
templates with us if you made new ones! For advanced users, we have also
added more ``composer elements`` and ``replacement tokens`` in our
templating system. Please see `our templating
guide <https://github.com/AIFDR/inasafe/wiki/Map-Composer-Templating>`__
guide for more details. Here is a list of the default templates shipped
with InaSAFE as of version 3.2:

Blue variants
  • A4 Landscape - Blue Variant
  • A4 Portrait - Blue Variant
  • A3 Landscape - Blue Variant
  • A3 Portrait - Blue Variant

Orange variants


-  A4 Landscape - Orange Variant
-  A4 Portrait - Orange Variant
-  A3 Landscape - Orange Variant
-  A3 Portrait - Orange Variant

|image4|

Tools
-----

Feature: Impact function options dialog improvements

Users who need to adjust the parameters of impact functions prior to
running their analyses will be pleased to note that we have overhauled
the InaSAFE Options dialog. Not only have we improved the visual
representation of Impact Function paramters for Options, Postprocessors
and Minimum needs, we have also also taken a lot of effort to simplify
things, reduce confusion and improve consistency and efficiency. For
example where impact function options can be gleaned from the input
layer keywords (e.g. which field in a flood layer marks a feature as
flooded), we use the layer keyword rather than asking users to enter
duplicate information. We have also removed potentially harmful
parameters that could cause our users to create poor analysis results if
changed.

|image5|

Feature: Improved wizards


The Impact Function wizard has been improved. It has been themed to
match the theming updates made elsewhere in the application. In addition
the following tweaks have been made:

#. Removed Single/Multi Event radiobuttons
#. Provided an explanation why when a layer is not selectable
#. The browser no longer displays the tons of .xml files in a directory
#. Layers with obsolete keywords are treated like they were keywordless,
   with
    one difference: the description says the keywords are obsolete, not
    missing. The text is based on that one from the dock - see
   attachment.

|image6|

Feature: OSM Downloader improvements

InaSAFE 3.2 introduces a new and improved OpenStreetMap data downloader.
We have added support for dowloading potential Internally Displaced
Persons (IDP) camps and for downloading political boundaries.

|image7|

Feature: New extent selector


In previous versions of InaSAFE, the options that governed the
definition of analysis extents were spread across different dialogs and
it was not intuitive to understand how the various options
interoperated. With InaSAFE 3.2 we present a new analysis extents
definition tool that addresses these issues. In addition, the new extent
selector allows you whether to enable notifications which will inform
you when the extents are suitable for use in an analysis - and when they
aren't.

|image8|

Feature: New look and feel for reports and dock

We have systematically revised the theming of the InaSAFE user
interface, reports generated, dock reports etc. We have also revised
many of the textual elements that are presented at different points
through the InaSAFE workflow in order to make the experience of using
InaSAFE more consistent and clear. The new modern look is also crisper
and provides a more modern look and feel.

|image9|

Feature: Changes to the keywords system


InaSAFE 3.2 introduces keyword versioning. If you have used previous
versions of InaSAFE to define keywords for your layers, you will need to
update the keywords before you can use those layers in InaSAFE 3.2.
InaSAFE will now automatically add a version keyword to your layer
keywords. In future versions this will help us to automatically migrate
your keywords to new keyword formats if needed, and alert you if your
keywords are too old to be used with the InaSAFE version you have.

We have spent some time polishing the experience of creating the
keywords using the keywords wizard, and improving the presentation of
keywords in the dock when a layer is highlighted. We have also hidden
away the internal keyword names and added functionality to present the
keyword names in a more human and understandable way.

In previous versions certain configuration options for impact functions
were configured directly on the impact functions dialog. This approach
was cumbersome as repeated use of the same impact function required
re-setting the same options each time. With 3.2 we have moved many of
the configuration options to the keywords system For example setting the
floodprone attribute for a polygon flood layer in the layer keywords
will automatically cause the impact function to recognise that attribute
in the keywords.

|image10|

Feature: Menu and toolbar tidy ups

We have tidied up the InaSAFE menu (Plugins -> InaSAFE) to make the
menu organisation more logical. We have also remove items from the
InsSAFE toolbar and improved the order of toolbar items so that they
options are arranged more logically. You will notice that the
iconography for all menus and toolbar buttons has been overhauled for
consistency and clarity. Menu items are arranged using the following
groupings:

  • Configuration related options
  • Wizards
  • Tools for adding data to InaSAFE
  • Miscellaneous helper utilities

|image11|

Website

Feature: Overhauled documentation


We have completely reviewed the documentation for this release. The
documentation team has been working hard to freshen up the documentation
to make it more consistent with the new features in InaSAFE. The
training materials are also being updated to emphasis use of the
keywords and Impact function wizards. The new curriculum will be used as
the basis for future training courses. The socialisation documentation
(which is intended to provide an introductory overview of the InaSAFE
project and its capabilities) has also been completely overhauled.

|image12|

Feature: New Realtime website

We have completely overhauled the InaSAFE Realtime <http://realtime.inasafe.org>__ web site. The previous version
of the web site provided a simple static list of earthquake impact
reports. With the new version of the realtime web site, you can now
browse, filter and query shake events both in a dynamically updating
table, and by interactively viewing the events on a map. Having a map of
events provides spatial context making it possibly to better understand
the spatial component of historical earthquake events around Indonesia.
For developers, the new web site also provides a REST API so that third
party applications can consume and public realtime disaster events to
and from the web site.

|image13|

Feature: Update user map


We have updated the `user map <http://users.inasafe.org>`__, making it
more attractive and more in line with our web presence overhaul. Please
take a moment to add yourself to our map if you are a not yet on it!

|image14|

Feature: New website for InaSAFE.org

We are pleased to present our brand new web site at
InaSAFE.org <http://inasafe.org>__. The new web site sports a new
theme which is consistent with our efforts to present a unified branding
throughout the InaSAFE project. We have also tried to group the content
in a clear, logical way. We hope the overhauled web site provides a
better first impression for new users to the InaSAFE project and makes
it easier for existing users to find the information they need.

|image15|

.. |image0| image:: images/projects/57a3157367fa1c37a324af520ac8fac0b7e98544.png
.. |Validating reports for InaSAFE 3.2| image:: https://cloud.githubusercontent.com/assets/178003/9974557/7ff9c170-5ebe-11e5-8625-a0ecdd9464d1.jpg
.. |image2| image:: images/projects/a21de91ef6a48028c0d0f874357c85a0b8908499.png
.. |image3| image:: images/entries/361eece669dedb378675e88182f5d98e26c4ed41.png
.. |image4| image:: images/entries/7c56d05313558757a0915a5d6dcb1c7a9a897d1b.png
.. |image5| image:: images/entries/4bc00d5bf7a5ff80b30b17fb0e1f64afc165f25e.png
.. |image6| image:: images/entries/779c5f309e80ec53c102d28c1cda0cccbbcdd22c.png
.. |image7| image:: images/entries/7269d5a91d76acf1c7ce676b8220914cb553bb23.png
.. |image8| image:: images/entries/445c5420ecaf7dcca414afb3814be682554a023b.png
.. |image9| image:: images/entries/a38268fa7434f4a8bef28faea12666cc673b5a7e.png
.. |image10| image:: images/entries/04bd5be083b8a53cadcabd3a58ef9c1fc7b3a15c.png
.. |image11| image:: images/entries/121027d08962eaad5044981a3e042170461599e3.png
.. |image12| image:: images/entries/c75c5e08c65e580397e842cbe4fdb75590612907.png
.. |image13| image:: images/entries/0b87573a25ba2c568dd39a369f5eb54ffe78468f.png
.. |image14| image:: images/entries/e486c4cf8f595cb5a69cf4968e8e56e1a8350ea0.png
.. |image15| image:: images/entries/fdf24c0b04828c94b6745eb7491c2daf95f165ef.png

Climate Change - Natural Hazard and Storm - Python
Published by timlinux over 9 years ago

InaSAFE - Version 3.1.3

This is a bugfix release. The following changes were made:

  • Added Tanzanian minimum needs file
  • Fix: Show building aggregation in volcanic ash impact function (#2105)
  • Fix: Totals of affected buildings in aggregation regions now calculated correctly (#2144)
  • Fix: Show building aggregation in volcano impact functions (#2103 #2104)
  • Fix: Prevent hazard attribute names from masking exposure names during interpolation (#2090)

Climate Change - Natural Hazard and Storm - Python
Published by timlinux almost 10 years ago

InaSAFE - Version 3.1.2

This is a bug fix release. The following changes were made:

  • Fix: Issue parsing minimum needs - see #2132
  • Fix: Error in Keywords creation wizard for flood raster layer (using meters as unit) #2111
  • Fix: Error when open Set InaSAFE Analysis Area #2045

Climate Change - Natural Hazard and Storm - Python
Published by timlinux almost 10 years ago

InaSAFE - Version 3.1.1

This is a bugfix release - it fixes an issue with resizing of the minimum needs configuration dialog.

Climate Change - Natural Hazard and Storm - Python
Published by timlinux almost 10 years ago

InaSAFE - Version 3.1.0

We are pleased to announce the availability of InaSAFE 3.1.0. This release includes a huge amount of polishing and cleaning in the InaSAFE code base. Many of these improvements are not things that you will immediately notice in the user interface, but rather represent incremental refinements to the software. There have been over 725 changes made in the code since 3.0 was released. The most fundamental change has been the implementation of a new architecture for impact functions. We have added two new impact functions and polished the user interface in various places. In particular the OSM downloader has been improved to give better feedback during downloads and to provide more flexible options. Read on in our change log below to see the highlights of this release!

For more information on how to participate in the InaSAFE project, please contact us at [email protected] - and visit our home page at http://inasafe.org. We would like to thank all the developers, funders, stakeholders and interested people for the great contributions they have made to InaSAFE thus far!

Key changes:

Unicode support

InaSAFE 3.1 is now Unicode compliant. That means that if you have accented / special characters in your file names, InaSAFE should deal with them gracefully instead of raising an error when you try to use them.

Improvements to Impact Functions that deal with polygon hazards and raster exposure

All impact functions that work on polygon hazard and raster exposure will return the raster exposure. These are:

  • Classified Polygon on Population
  • Volcano Point on Population
  • Volcano Polygon on Population
  • Flood Polygon on Population

The impact layer will return the population layer with some modifications:

For Classified Polygon on Population, Volcano Point/Polygon on Population, the impact layer grids values will follow this rule: If the grid covered by polygon, the grid will be assigned the pops grid value. If it's not covered, the grid will be assigned no data value (see interpolate_polygon_on_raster)

For Flood Polygon on Population, the impact layer grids values will follow this rule: If the grid covered by polygon AND match the parameters (value in the affected field == affected value), the grid will be assigned the source population grid. If it's not covered, the grid will be assigned no data value. If it doesn't match the criteria in the parameter, it will be assigned 0

Support for setting the analysis extents from a QGIS bookmark

You can now set the analysis extents using a QGIS bookmark. This makes it easy to create a collection of well defined, named analysis areas and then run impact assessments on them as needed.

Saving a layer now also saves layer keywords to the destination

In previous versions of InaSAFE, if you used the QGIS 'save as' feature on an impact layer, the keywords and other associated files were not transferred. In InaSAFE 3.1 these files are now correctly transferred to the new destination, ensuring that when you create copies of your data, their metadata are propagated too.

Note: You need version 2.8 or better of QGIS in order for this feature to work.

Option to specify where impact results are saved

You can now specify a directory that will be used when saving analysis results. In previous versions it was not obvious where InaSAFE would save its output data. Now you can provide a directory explicitly so that you can easily find your analysis results again in the future.

Improved menu layout

We have improved the menu layout so that items listed are more logically consistent using this logic:

  • first items relating to setup of the analysis environment
  • then items relating to performing the analysis
  • then items relating to downloading and transforming datasets
  • then items relating to post-processing and analysis replication

OSM Downloader can now use user defined extents

Now when you download data using the OSM Downloader tool, you can specify the extents of the data to be downloaded, either by entering specific coordinates, or by dragging a rectangle on the map canvas in QGIS. You can also now specify if you want the downloader to overwrite existing files, or to save the downloaded files with a unique filename on each download.

Support for downloading building point data

The OSM Downloader tool can now download buildings as points (based on point-on-surface centroids). This makes it easy to use InaSAFE for doing hazard on point analyses such as flood on building points, earthquake on buildings points etc.

Improvements to OSM Downloader progress feedback

The OSM downloader now gives more useful progress feedback, showing the elapsed and total download sizes in megabytes.

Climate Change - Natural Hazard and Storm - Python
Published by timlinux almost 10 years ago

InaSAFE -

We are pleased to announce the availability of InaSAFE 3.0.0. This is a major new release. The 3.0 designation is because we have made major changes to the underlying code architecture which will break existing applications that used the 2.x InaSAFE API. We have also added new features and tools to make the process of contingency planning more efficient and configurable.

For more information on how to participate in the InaSAFE project, please contact us at [email protected] - and visit our home page at http://inasafe.org. We would like to thank all the developers, funders, stakeholders and interested people for the great contributions they have made to InaSAFE thus far!

Key changes:

Impact summary reporting improvements

The impact summary table that accompanies the graphical report created by InaSAFE has been updated so that the output matches the styling of the rest of InaSAFE and is much more pleasing and easy to read.

New wizard for carrying out impact assessments
Our new wizard has the following goal: providing a guided, logical path through the process of carrying out an impact assessment. The new impact function centric wizard presents a series of questions in a very easy to use manner that will step you through the process of carrying out your assessment. Rather than requiring the user to first load their data and then discover which kinds of assessments can be carried out (as the prior versions of InaSAFE only supported), the new wizard lets the user first select what kind of analysis they would like to carry out and then lets them select the data from the set of layers that are currently open in QGIS, or by loading a layer from the file system via a user friendly data browser interface.

Code

This is the main reason for the 3.0.0 desigation - we have done a major overhaul of the code, merging the safe and safe_qgis packages and allowing the use of Qt4 and QGIS API calls throughout the codebase.

Climate Change - Natural Hazard and Storm - Python
Published by timlinux about 10 years ago

InaSAFE - Version 2.2.3

This is a minor bugfix release which corrects a problem in the QGIS plugin manager that was caused by our designation of the maximum QGIS allowable version of 2.99.999 - we updated this to 2.99 in this bugfix release.

Climate Change - Natural Hazard and Storm - Python
Published by timlinux over 10 years ago

InaSAFE - Version 2.2.2

  • Bug fix: Make legend work with QGIS 2.6, removes requirement to use QGIS 2.4
  • Bug fix: Fixed issue with batch runner not working properly

Note: This release is now compatible with QGIS 2.6

Climate Change - Natural Hazard and Storm - Python
Published by timlinux over 10 years ago

InaSAFE - Version 2.2

We are pleased to announce the availability of InaSAFE 2.2. This is a feature release, adding a number of new features and tools to make the process of contingency planning more efficient and configurable. For more information on how to participate in the InaSAFE project, please contact us at [email protected] - and visit our home page at inasafe.org. We would like to thank all the developers, funders, stakeholders and interested people for the great contributions they have made to InaSAFE thus far! The image on the right (click for a larger view) features participants at the InaSAFE workshop held in Jakarta over the period 22 September - 30 September 2014.

Important note: InaSAFE 2.2 does not support QGIS 2.6. Please ensure you have QGIS 2.4 in order to be able to download and use this plugin. This is addressed in the 2.2.3 Bugfix release above.

Preliminary support for ISO19115 metadata

Until version 2.2 of InaSAFE, our (keywords system)[http://inasafe.org/en/user-docs/application-help/keywords.html] has relied on a simple text file format for representing the various properties about GIS layers - for example whether they are hazard, exposure or impact layers. As of InaSAFE 2.2 we will be shifting towards using the industry standard ISO19115 file format in order to facilitate data interchange with other GIS users.

For technical users, note that keywords will be represented in the gmd:supplementalInformation element of the ISO19115 document and still adhere to our key : value pair format within the CDATA block as per the example below.

<gmd:supplementalInformation> <inasafe_keywords> <![CDATA[

And then in the nested CDATA block:

category: exposure
source: OpenStreetMap
subcategory: structure
title: Essential buildings
datatype: osm

And then the supplemental information block is closed:

]]> </inasafe_keywords> </gmd:supplementalInformation>

In future versions the keywords will be represented as JSON within the CDATA block.

Improvements to the clipping logic for rasters

In many cases, previous versions of InaSAFE were clipping raster layers sub-optimally. The resulting layers were not aligned with either the hazard or exposure layers. This affected the interpolation routines that are used during pixel lookups, resulting in less accurate analysis results. Here is a typical example of what you would see in the impact layer when extents were poorly aligned:

In version 2.2 of InaSAFE we have improved the algorithm used for clipping so that the clipping area will expand / contract as needed to the nearest pixel edge as per the diagram shown here. We also improved the numerical precision for clipping operations in order to ensure that edges are aligned as closely as possible.

Remaining Problem: Please note there is one remaining problem with clipping that we hope to address in a future version - it relates to raster datasets that have non-square pixels. In these cases currently only one edge is currently used for calculating clipping boundaries. See issue #1301 for more details. As a work around in the interim, we advise our users to try to use square pixel raster datasets whenever possible.

New volcano OpenStreetMap buildings impact function

InaSAFE 2.2 introduces the ability to assess buildings affected by volcano hazard zones. The buildings should be obtained using the OpenStreetMap downloader tool in InaSAFE. The impact report will break down the number of buildings per hazard zone, as shown in the screenshot here.

Raster flood on OSM buildings

As of InaSAFE 2.2 you can now produce an impact scenario assessment for a raster flood layer on OSM buildings. The impact function will break down the number of inundated (considered flooded), wet (may be flooded) and dry buildings. The building summaries are done by usage classes: Clinic/doctor, Commercial, Government, Office and so on.

Generic / categorical impact function

InaSAFE 2.2 introduces a new class of Impact Function: Generic Impact Functions. Generic impact functions treat exposure as a series of categories representing level of risk. This is extremely useful for developing scenarios based on a wide range of risks from flooding to fire to chemical hazard etc. Basically anything that can be quantified into three risk categories can now be used as the hazard for an impact assessment. These categories are defined according to the following classes in your hazard data raster layer:

1 : low risk
2 : medium risk
3 : high risk

Furthermore, the hazard layer should have these keywords:

  • Category: hazard
  • Subcategory: generic
  • Unit: categorised

Currently categorised impacts can be calculated for population and OSM building exposure layers.

Extent selector tool

The new extent selector tool lets you define where the analysis extent should be explicitly. In previous versions, the determination of the analysis area was either the intersection of:

  • the current viewport display area in QGIS
  • the hazard layer extent
  • the exposure layer extent

or (when 'clip datasets to visible extents' option is disabled in InaSAFE settings):

  • the hazard layer extent
  • the exposure layer extent

In 2.2 a new permutation allows you to define (by dragging a rectangle or by entering coordinates manually) the maximum analysis extent explicitly. The effective analysis area in this mode then becomes the intersection of:

  • the user defined analysis maximal extent
  • the hazard layer extent
  • the exposure layer extent

To disable this behaviour simply open the new tool dialog and press the 'Clear' button, then close the window.

A new marquee / rubber band on the canvas display indicates where the user defined extent is by means of a blue rectangle.
As in previous versions, the effective analysis extent is defined by means of a green rectangle.
When an analysis is completed a red rectangle indicates the last completed analysis.

New minimum needs manager

This release adds a new minimum needs manager with support for regional minimum needs profiles. Minimum needs is a critical component of InaSAFE that is used to calculate the requirements (e.g., food & shelter) of displaced or affected people after a disaster. Up until now the values used to determine minimum needs in InaSAFE have been based on Indonesian national guidelines. This made it somewhat cumbersome to deal with regional variations in requirements, or to deploy InaSAFE into other regions which use substantially different guidelines for human needs in the event of a disaster.

With the new minimum needs manager in InaSAFE 2.2, you can define a 'profile' (e.g. Jakarta Needs) and then use specific defaults for e.g. daily rice requirements for that profile. By default we ship with standard profiles for Indonesia and the Philippines, and more profiles can easily be defined using the needs manager tool (pictured here).

Climate Change - Natural Hazard and Storm - Python
Published by timlinux over 10 years ago

InaSAFE - Version 2.1

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.

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.

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.

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.

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.

Climate Change - Natural Hazard and Storm - Python
Published by timlinux over 10 years ago

InaSAFE - Version 2.0

Training materials updates

We have been hard at work to improve our documentation on http://inasafe.org. The tutorials section has been overhauled at http://inasafe.org/en/training/index.html. We have also added an archive section which you can use to fetch older versions of our documentation (see http://inasafe.org/pdf/). We have also added a new download section to our web site http://data.inasafe.org/ which contains the sample data used in the training materials. We have made many other improvements to the documentation - we hope you find the information you need to be productive with InaSAFE!

Polygon flood impact on roads impact function added

Our first demonstrator impact function that uses the native QGIS geoprocessing functionality is included in INaSAFE 2.0. The function takes as input a polygon flood layer (category: hazard, subcategory: flood [wet/dry]) and a roads layer (category: exposure, subcategory: road). It will return a new roads layer where each road segment is classified as inundated or not inundated. You can download suitable roads data using the OSM Downloader tool roads fetcher as mentioned below.

Report view in your web browser

If you find the dock panel too small to show all the report details, or if you want to open it in your browser to quickly print the tabular report, you can now do so by right clicking on the report area of the InaSAFE dock and choose Open in web browser.

Custom logo selection

As well as the new report template capabilities, you can now also set your organisation logo in the InaSAFE options dialog. This logo will then be used for any of the built in InaSAFE templates that you use, or anywhere in your own templates if you use the element id safe-logo. Click image on right to see an example of how the organisation logo is placed in the bottom right of the template.

Template based reports

Another key new feature in InaSAFE 2.0 is the ability to define and use custom print templates (using the built in QGIS composer templating system) for your reports. This new feature means that you can now place your own logos in the report and customise the arrangement of the various report elements on the page. You can also print onto different page sizes (e.g. A3, A2) and in different layouts (portrait, landscape). You can find more details about this functionality at http://inasafe.org/en/user-docs/application-help/reports.htm.

Impact merge tool

This tool will allow you to merge the output from two impact assessments covering the same geographic extent and aggregated by the same areas. For example if you run a flood analysis on Kapubaten (districts) in Jakarta for both impact on people and buildings, you can generate a report that combines these two exposures into a single report.

The generated report combines the result of post-processing analysis on each area, for example generating totals for each type of critical building affected, age and gender breakdowns etc.

OSM Roads downloader

In InaSAFE 1.2 we introduced the new OSM downloader tool for buildings data. As well as making some improvements to the way that the downloaded buildings are categorised, we have also added a new tool that will allow you to download roads data. When the data is downloaded, it is automatically assigned the correct keywords to be usable in QGIS (see separate changelog entry on impact on roads) and assigned a style.

Options dialog overhaul

We have overhauled the options dialog to make it easier to navigate and hide away advanced options into their own panel.

New User Map

We have added a community map to our web site. Please take a moment to register yourself there as an InaSAFE User, Developer or Trainer! It will help us a lot to see who our users are and where they are located. The map is built using the opensource Leaflet javascript library and uses the OpenStreemap.org Humanitarian Openstreetmap Style. See http://users.inasafe.org

Climate Change - Natural Hazard and Storm - Python
Published by timlinux over 10 years ago

InaSAFE - Version 1.2.0

This release represents a major step forward in the InaSAFE project with key new features being added to support aggregation and post processing (for demographic breakdowns). InaSAFE has also received an interface and error messaging makeover and have had a number of useful new tools for scenario assessment added. There are also many changes you can't see easily - including a major revision to the source code to improve its consistency and organisation.

We've also been hard at work to support multiple languages in every part of the project - our website, the application user interface, help documentation etc. If you have any questions or want to contribute to the project, please don't hesitate to contact us at our new email address: [email protected]

Key updates:

Improvements to InaSAFE panel

We have overhauled the InaSAFE panel in QGIS. The question area hides itself away based on the context of what you are doing so that you have more space to view the report in. The report area has been spruced up with our new messaging system with a clearer layout and the inclusion of InaSAFE branding at the top of the report area.

Icon and branding overhaul

We have updated the branding of InaSAFE to reflect the new logo that will be used in the software, web site and promotional materials. At the same time we tried to make the icons clearer and more recognisable.

Aggregation and post-processing

A major new enhancement in this release it support for aggregated results. Aggregation allows you to specify an additional layer when defining the analysis criteria. This layer will be used to provide a by-area breakdown of the results of the analysis. For example if you are carrying out an analysis for a city, you can use district areas within the city to provide per-area results. In the absence of an aggregation layer, the analysis extent is used as the aggregation unit.

The new post-processing support provides an extensible framework for computing at-risk population demographics per aggregation area. For example, in this image you can see the impact summary report provides a break down of the gender and age demographics for 'kapubaten' in Jakarta (using a flood scenario). In the gender report you can see that based on the standard female / male population ratio, the assessment suggests extra food provisions should be made available to cater for lactating women.

Post processors are configurable (by pressing the button next to the impact function chooser). For example in the image here we can see options (highlighted in red) for adjusting the age ratios used for the age breakdown post-processor.

Minimum needs

All impact functions which use population for exposure will now compute minimum needs based on standard 'Perka 7' guidelines. In addition, these guideline daily requirements can be overridden in the new impact function configuration options dialog (accessed by clicking the button to the right of the impact function combo as shown in the image here).

New configuration options

We have added two new options (for developers / power users) in the configuration panel.

  • The first lets you choose which backend to use when computing zonal stats - the QGIS native implementation or our InaSAFE implementation. Note: This is an advanced feature added due to limitations with the QGIS Zonal Stats implementation in QGIS 1.8.
  • The second option lets you enable developer mode which is used to view source output in the dock reporting area. Note: This is an advanced option intended for use by developers.

Minimum needs tool

We have added a new tool for computing minimum needs. Using this tool you can compute Perka 7 requirements for displaced people. The tool requires a QGIS polygon layer loaded with an attribute column containing the number of displaced people per area. When the tool is run, a new layer will be added which contains the original polygons and new attributes giving the weekly requirements of drinking water, clean water, rice, toilets and family kits.

Shakemap Importer

Shakemaps are useful for carrying out contingency planning for the event of an earthquake. Normally these are distributed as grid.xml files which are not usable in InaSAFE or QGIS. We have added a new tool that will import a grid.xml file as a GEOTIFF file from where it can be used within InaSAFE. Two different interpolation algorithms can be used during the import process - nearest neighbour and Inverse Distance. After the conversion, the tool automatically creates InaSAFE keyword metadata for the layer so that it can be used immediately for analysis.

Save scenario

We have added a new tool which lets you save the current scenario as a scenario text file. Used in conjunction with the Batch Runner tool, you can use this tool to easily define a list of scenarios for the batch runner to use.

OSM Buildings Downloader

InaSAFE supports the use of building data in various impact functions. In particular we support building footprints sourced from the OpenStreetMap project (OSM). However, there hasn't thus far been an easy way to import OSM into InaSAFE. With version 1.2.0 of InaSAFE we now provide a simple tool to facilitate this. The tool requires internet connection as it fetches the data via a web service running on Linfiniti's OSM Reporter web site.

The data, once downloaded will be available to you as a shapefile. A style file is automatically created so that it symbolises nicely in QGIS. In addition, the correct keyword metadata is created for the downloaded dataset so that it can be used directly in InaSAFE impact scenario analyses.

Note: The building downloader service has limitations as to the size of datasets that can be retrieved. As such you may experience issues trying to fetch e.g. country wide building footprint data. Generally datasets at a city level and below should work well.

Batch Runner

We have added a new batch runner tool to InaSAFE. With this tool you can setup numerous scenarios and run them all in one go. A typical use case may be where you define a number of e.g. flood impact scenarios all using a standard dataset e.g. flood.shp. As new flood data becomes available you replace flood.shp and rerun the scenarios using the batch runner. Using this approach you can quickly produce regional contingency plans as your understanding of hazards changes. When you run the batch of scenarios, pdf reports are generated automatically and all placed in a single common directory making it easy for you to browse and disseminate the reports produced.

When the batch process completes, it will also produce a summary report like this:

InaSAFE Batch Report File
-----------------------------
P: gempa bumi Sumatran fault (Mw7.8)
P: gempa di Yogya tahun 2006
P: banjir jakarta 2007
P: Tsunami di Maumere (Mw 8.1)
P: gempa Mw6.5 Palu-Koro Fault
P: gunung merapi meletus
-----------------------------
Total passed: 6
Total failed: 0
Total tasks: 6
-----------------------------

For advanced users there is also the ability to batch run python scripts using this tool, but this should be considered an experimental feature still at this stage.

New website launched

We are pleased to announce our new website at http://inasafe.org which is a substantial overhaul of our old site. The new site sports our new project branding and is fully translatable so that in the future we can offer it in many languages. Currently English and Bahasa Indonesia are supported. The site also tries to present information in a clear consistent way and we have made many updates to the content throughout the site.

Climate Change - Natural Hazard and Storm - Python
Published by timlinux over 11 years ago