User Manual

1. Click anywhere on the map
2. Confirm the messages
3. Stay patient
4. Download the result if you like it

Tipps & Tricks

• Use the rainviewer to see global current radar rain data
• Use fullscreen for better experience

Motivation

Hydrological analyses from DEMs (digital elevation models) for various classic GIS analyses always took plenty of time and resources. This tool is for everyone looking for quick and easy hydrological analysis.

During my study in geosciences, I became a geo-data scientist. Guessing river runoffs for my main hobby river surfing led to the development of this project. Web developments with integrated GIS solutions became my main interest and projects like this give me the opportunity to improve.

HydroSHEDS Dataset

The data behind the scenes

HydroSHEDS (Hydrological data and maps based on SHuttle Elevation Derivatives at multiple Scales) provides consistent hydrographic information on a global scale. It contains various geodata sets including river networks, watershed boundaries, drainage directions, and flow accumulations.

The HydroBASINS product contains a global consistent coverage of nested sub-basins at different scales, which is supported with coding schemes that allow various analyses (Lehner and Grill, 2013).

Pfaffstetter coding

The code behind the scenes

Is a nested coding system for horological river basins. It allows to identify upstream and downstream basins.

Basically, a basin is subdivided into 9 smaller basins and labeled from 1 to 9. Each sub-basin is divided again by 9 and labeled by appending the number to previous code numbers. Like this, the more levels of subdividing the more digits the code will have (Verdin and Verdin, 1999). The HydroBasins dataset comes with 12 levels.

In the context of this project, I wrote a short Python module for decoding, available at github.com/steinmnn/pfafhydrocode.

FAQ

• Why is the watershed polygon not exactly bordering my marker? The algorithm selects basins from a global consistent coverage of smaller sub-basins. The query is limited by the smallest polygon resolution (Pfaffstetter Level 12) of the HydroBASINS dataset. Therefore, the tool is not suitable for smaller streams.
• Why does the download of the rivers as GeoJSON throw an error sometimes? The watershed is too big. The rivers.geojson can become quite big, and the download size is currently limited to a maximum of 5 MB.

Issues

• Slow calculating of watersheds. For big watersheds, computation time is up to 20 seconds. It is questionable that further optimizations will significantly reduce this. Anyway, I want to implement celery workers in the future to have proper asynchronous tasks and provide a smoother user experience.
• Pfaffstetter decoding issue. The Python module I wrote at github.com/steinmnn/pfafhydrocode occasionally misses basins while watershed computations. I present this notebook on my website which discusses the problem and presents a dirty workaround also used in this project.

Roadmap

• Zoom to Watershed Button. A button within the leaflet map to center the watershed.
• Implement historic seasonal data. A option to view historic climate data for the calculated watershed.
• Integrate the HydroWASTE dataset. Another layer that shows all the wastewater plants. Through this, the water quality can be estimated.