Qgis-epanet for GIS/Simulation interaction

Hello all,

First, let me introduce myself quickly. I am founder at Oslandia, a company specialized in OpenSource GIS for more than 6 years now. We are developers, and very active in the OpenSource GIS community, especially PostGIS ( Spatial Database) and QGIS ( Desktop GIS).

We are currently working more and more on water-related subjects, and especially water distribution network management and simulation.
One of our goals is to better integrate the GIS world and the simulation world, especially in the field of water ( distribution, wastewater, hydrology).

We developped qgis-epanet which is a plugin for QGIS to let the user drive Epanet simulations, get results, and visualize these results directly in QGIS.

The source code is here :

And you can see a demo video here :

The plugin has a basic feature set for now, but will probably be extended in the future, according to our client’s needs. Everyone is welcome to contribute to this.

We also gather documentation and use cases for water-related topics here :
LINK EDITED

Aside from the simulation part, we also started to work heavily on qWAT, which is a QGIS plugin dedicated to network management. It is based on a PostGIS spatial database data model, and provides a GUI for these objects, so as to be able to manage the network from within QGIS. Of course all features of QGIS for cartographic exploration and production are available.

LINK EDITED

There are already some users with qWAT deployed for production use, and we have funding for industrialization and more features for next year.
qWAT like other QGIS plugins is opensource. One of the next step, already easily done, is to provide the ability to directly run simulations with qgis-epanet on a qWAT model.

Note that QGIS and all (Python) plugins are based on the QT framework, which is a very good library for GUI development. Should you wish to create a new multi-platform GUI for Epanet, QT would probably be a good choice, and we may mutualize things with QGIS too.

We are really glad to see EPANET going to a full opensource project and organization. This has been a stopper for us for a while, not having enough visibility on the project, with duplication of efforts and code balkanization. It seems to be on the right tracks now.

We hope we will be able to help the Epanet project directly at some point, by improving the code, features, or providing help for any OpenSource-related issues, since we have a good knowledge in this, be it on the licence side, business models, project organization and dynamics…

Meanwhile, we wanted to thank you for this good simulation tool, which really helps us being relevant for a full GIS/water simulation integration.

Regards,
Vincent

Edit : a dumb rule of this forum does not want me to include more than 2 links in the message. Other links in answers to this message.

2 Likes

Missing links :

Qgis water use cases :

The qWAT project :

@vpicavet Thanks for the introducing the qgis-epanet plugin. My group is aware of your work, and in fact we are also using qgis to connect with EPANET; however in our case, we have prepared a software in python to translate the PostGIS network stored by QGIS into an EPANET file, and use that to process the network, externally.

What I believe is important in what you describe, is to see if it is possible to “standardize” the format of the network in QGIS. For instance, specifying the layers, their type and their minimum parameters, what to do with the nodes (e.g create automatically), how to properly import an INP file into the network etc.

There is also another QGIS related plugin, the http://epanet.de/ghydraulics/index.html.en. There are some differences, but it would be great if there was a discussion/comparison and if possible to finally agree on some common characteristics (or even adopt one as standard).

Note that some users will be interested in using epanet as a plugin on qgis, others to use qgis/postgis as a module in their system. Also some will want to use different DLLs of EPANET to make the analysis. So these need to be considered.

So, this is an interesting discussion to have, and it’s great to have you onboard!

Demetrios

Hi @demetrios, all

The network “standard” relational model is the one used in qWAT. It is pretty stable, even if it will probably still evolve in next versions. qWAT is expected to be released with a production ready version mid-2016.
It is oriented towards network management though, which may be a bit different from what is required on the simulation side.

We have SQL views to translate from the qWAT network model to epanet data format. They have to be improved a bit though, this work will be achieved in the next months.

qgis-epanet also has some additional tables to handle simulation history, parameters and more. There is a tool to import existing INP files to these tables.

As for GHydraulics, we are aware of it and discussed with Steffen before creating qgis-epanet. GHydraulics is not well maintained any longer, mainly for personal reasons on Steffen’s side. It is also “just” an INP file exporter, whereas qgis-epanet is more integrated into QGIS.
An INP file is already generated by qgis-epanet when launching a simulation. We could add an export feature to just output the INP file without running the simulation, this would be trivial.

If you have the same Epanet interface as the standard executable, you can specify which one you want to use with qgis-epanet. As qgis-epanet is a QGIS Processing module, you could also use it outside of the QGIS interface with some Python code, and even as a WPS web service if you want with recent QGIS server developments.

I see that it still lacks some GUI and work on ergonomics, do not hesitate to add issues in qgis-epanet github repository or qwat repository, we like to have feedback from users !

Vincent