`osm-river-basins`: Website to show how are rivers in OSM connected

As of this writing, there’s a mysterious 7084161-km Endpoint in central Italy north of Florence, on an intermittent stream in an arid-ish area.

RioDiBelvedere

I tried to fix it through changeset 150532208, which involved merging several consecutive segments of the same named straeam. My prime suspect were two overlapping segments (like §) which I properly rearranged. Please check out if this has fixed the problem.

In the “natural” plane, rivers Weichsel and Donau still the same basin – all of the worlds seas :wink: Can this view ever render something like shown here Weichsel – Wikipedia ? The Watershed is so densely mapped, how to spot the culprit(s)?

Forgive me if this has been brought up, but I couldn’t seem to find it by searching: is rendering waterway=seaway intended? It results in some pretty silly “river” systems in Greece for example:

If the wiki is to be believed this tag should be removed on served ferry routes anyways, but irregardless, the tag in general seems to be a probably unwanted rendering for the purposes of the WaterwayMap.

5 Likes

@Hungerburg : I’d say no, OSM is too micro-mapped with real and existing links between ‘natural’ basins to achieve such a representation without some generalisation.

Taking out waterway=pressurized recently helped separate Rhine and Donau in the natural plane. Rendering waterway=seaway reminds on renderers and routers for which a highway=path is always 2m wide and paved. @PeachyOne file a github issue?

OSM tagging is rich vocabulary, it should be capable to distinguish natural from constructed features. Waterwaymap wants to help finding issues with inadequate tagging? I fully understand that it is not trivial to compute those junctions where two basins entangle. Crowd-source that?

Maybe not quite rich enough yet Is there a common tag for underground infiltrated watercourses?

Also, we don’t map aquifers.

oops, that wasn’t intended. I’ve removed excluded it. It’ll be in the next update.

2 Likes

Yeah, that would be cool… :thinking: goes off hackin‘ :woman_technologist:t2: :woman_mage:t2::crystal_ball::magic_wand: New feature time! :partying_face: Go in settings on WaterwayMap.org, and turn on Frames. (direct link :link:)

For each water basin/blob, it chooses a set of points at the edges, and draws a black line from each edge point to every other edge point. This shows how regions of the blob are connected.

It’s only available for the All Waterways and Natural Waterways maps, and only for waterway groups longer than 1,000,000 m long (→ code :scroll:). For my fellow data nerds :1234::nerd_face:: It’s the shortest path between all the convex hull of the points in the graph. I can do algorithms, but graphics are not my strong suit. Here’s the map style if anyone wants to send me a patch :slightly_smiling_face:

I’d love to do a Proper Algorithm™ like Betweenness centrality, but I couldn’t generate it in a sensible time. So I invented this “Frames” idea. Let’s see if it’s useful. Like all WWM data, it’s calculated every day. If you fix one mapping mistake

:national_park: explore the map now!

– ⓐⓜⓐⓝⓓⓐ :sunflower:

7 Likes

Yep, here’s that blob! (w. frames). This map includes canals, You can see many connections through France/Germany, and 2 routes through Poland and Austria.

Here’s that water Vistula-Danube waterbasin, with the “frame”. The Dniester is also connected. Perhaps you can find any mapping mistakes. :slightly_smiling_face:

Hi, look at this stream (see below). The water from it flows to both - southern and northern water basin. It is named “Dividend water”, so it is not necessary a mistake. Anyway it connects Danube to polish Gdansk:)

5 Likes

If nothing else, this update finally got me to properly connect this otherwise unsightly blob in TX into the proper water network
image

2 Likes