Open Source Lisflood

Lisflood

LISFLOOD is a spatially distributed water resources model, developed by the Joint Research Centre (JRC) of the European Commission since 1997.

Add-ons

Lisvap

LISVAP is a a pre-processor that calculates potential evapo(transpi)ration grids that can be used as input to LISFLOOD.

Calibration

Calibration tool description

Test Catchments

Documentation is on lisflood-usecases repository, as a README.md file.

Tools

This repository holds a set of NetCDF tools. You will find documentation of each tool as a README file under its dedicated folder on lisflood-utilities repository

Documents

Additional Documents

Users interested in preparing LISFLOOD static data for their AOI can find additional information in this section.

How to contribute

If you find a bug or a way to improve our code, in functionalities, accuracy, or efficency, or you simply found that we missed something, you can either open an issue or submit a pull request. Please follow these guidelines in order to contribute.

Open an issue

Just go on the GitHub repository of interest and open an issue. Have a look at this page to know how to do it: create an issue on GitHub. When opening an issue, please be as more specific as possible. Furthermore, if you are reporting a bug or you are not able to run our software, you should include some information about your environment:

  1. OS (Linux distro, Windows version...)
  2. Python and packages versions
  3. Input data (e.g. specify meteo datasets)
  4. Settings and configuration files in case you use custom versions
  5. Any other information that can be useful to debug or evaluate a feature request etc.
Open an issue

Just go on the GitHub repository of interest and open an issue. Have a look at this page to know how to do it: create an issue on GitHub. When opening an issue, please be as more specific as possible. Furthermore, if you are reporting a bug or you are not able to run our software, you should include some information about your environment:

  1. OS (Linux distro, Windows version...)
  2. Python and packages versions
  3. Input data (e.g. specify meteo datasets)
  4. Settings and configuration files in case you use custom versions
  5. Any other information that can be useful to debug or evaluate a feature request etc.