OpenNHM

• the AvaFrame QGis Connector is now out of the experimental state, so it is easily installable via the QGis plugins manager. No more need to enable experimental plugins. See QGis plugin directory .

• We had our first webinar with about 15 test users. This group is testing AvaFrame from an operational point of view. The first feedback is already rolling in, and we already discovered some more snags. However, so far nothing too serious. Some, as yet to be solved, problems concern file access rights on windows machines. If you hit a similar problem, we’d be happy to hear from you! (e.g. via a github bug report…)

Version 0.6 , the QGis/pypi and testing - release, was published.

So what is included in this release?

• The installation process was completely changed and (hopefully) made a lot easier for you:

  • installation of AvaFrame is now working via pypi , i.e. through pip install avaframe.
  • the pip install is provided for Windows, Linux and MacOS for python versions > 3.6. Note that we did not test MacOS (anyone got a free Macbook lying around?! :-); seriously: if you work on MacOS we’d be happy about some feedback!)
  • the QGis connector plugin is now in the public QGis plugin directory and installable via the QGis plugin manager. This allows you to run the standard operational workflow from within QGis.
  • see our installation instructions for more information

• Our testing / code coverage has improved considerably. We are still long ways away from perfect, but this is an ongoing process. As a side-note: we switched from codecoverage to codeclimate as service provider, since we felt we gain more insights this way.

We released version 0.5 , our so called public prototype.

So now why is this big? (Apart from being a project milestone, which you couldn’t care less about I guess)

This is the first release that is being tested for application in operational hazard mapping.

To achieve this, quite a few things changed:

via this link: online meeting (bigbluebutton, i.e. in your browser) .

These meetings are meant to allow you to see what is currently going on in our development and we invite you to give feedback or suggestions.

We start with a flash update in which everyone working on the project gives a quick (2min) overview about their current work. Afterwards we go into detailed discussions on agenda topics. Feel free to contribute if you want to!

Documentation regarding our testing is included, see more at the testing page.

• One big focus this months was a refactor of our AIMEC routines. We realised that our functions were still too complex, so we decided to

  • split it into more atomic function to make it easier to access only certain parts of the AIMEC functionalities.
  • make sure no special folder structure is needed anymore.
  • add an option to compare results from two different com modules.
  • improve and develop the AIMEC plots some more.
  • showcase how to use it by including it in the standard tests.

  All this is especially important in light of our submission to the vEGU 2021. See here for more information.