Use case:

As a tester I need to run the existing examples on my own hardware, so that I can assess the working without worrying about specific hard ware

Example 1 of bow@banff is working. Needs to be checked that it also runs on other's computers

Tasks:

• Run example 1 bow@banff at own computer
• Assign same task to someone else

Use case:

As a browsing hydrologist I want to immediately see that this repo is temporary and to be merged with CWARHM so that I find my way to that actually useful repository

Tasks:

• add CWARHM reference to project description

use case:

As a team member I want to have a clear overview of the available data so that I can plan my model runs or add data when needed
As a coder I want to have a clear overview of the available data so that I can link my code to the right data

tasks:

• go through data folder and start an online document with data descriptions and paths

use case:

As a globally cooperating hydrological modeller I want that CWARHM and hydromt share the same data interface, so that future efforts on workflows can be combined

discussion:
One way to organize data for hydrological models is explored in hydromt. This has several advantages:

1. it utilizes the full ability of gdal (through conda python) to read raster and shapefile formats into xarray or geopandas objects: this is the programming solution to the whole data-specific interface of CWARHM!
2. It is a form of self-documenting data archive: the datacatalog file (or multiple) show clearly which data is available for a project, where it is stored etc.
3. There is a clear In/Out requirements for workflows: not file paths, but xarray and geopandas objects - this is in line with the Single Responsibility Principle as reading of data is no longer part of the workflow function.