Back

This is made 100% from OpenStreetMap data, for the whole world, updated daily, without any human intervention. This sort of data can be generated, today, from pure OpenStreetMap.

This map is rendered client side, in your web browser. You can change the colours, or filter out small bits via the “Settings” button.

You can run this yourself, for an area you're
You need `cargo install` the `osm-lump-ways` tools ( src: <https://github.com/amandasaurus/osm-lump-ways>), and checkout the config files for WWM, you really just need the definition of flowing water: <https://github.com/amandasaurus/waterwaymap.org/blob/main/flowing_water.tagfilterfunc>. Then just `osm-lump-ways-down -i INPUT.osm.pbf -F @flowing_water.tagfilterfunc --flow-follows-tag name --grouped-ends ends.geojson --grouped-ends-max-distance-m 10e3`, and boom, you've got something you can open & style in QGis.

The rivers' colour is based on where they flow into. If you see a colour abruptly stop or change, it's probably that.

The upstream flow follows the OSM `name` tag when a waterway splits. If there's funny results, check how it's mapped (maybe there's something not connected?)

@amapanda so this is a bug in the data? Such a cool map!

@grischard the little stubby peach bit? hmmm. It's a different colour because (I presume) there's an outward flow into the riverbank.

But hmmm, why is it so big?

@grischard congrats on finding a bug.

The issue is n8936587888, which is part of w242165569 (name=La Meuse), but across the river (west→east) goes w242395286 (name=Barrage de Vannes Alcorps). There are 2 in segments & 2 out segments (both w. name). Since that's more complicated than simple approaches, I just allocate the flow equally, hence half the Meuse going to the eastern end of that weir.