The end of waterway map

General talk
, , , ,
21

Just a quick note to mention that I opened PR #10283 in the iD repository to add directional rendering for lines tagged with waterway=flowline.

4 Likes
22

More good news! @JesseFTW has submitted a PR to add a preset to iD that will treat flowlines as an entity of its own right, rather than merely as “Waterway feature”. :partying_face:

3 Likes
23

But a river can flow through a canal without docks.

If the only end of the river is the canal, it should be accepted, especially when a relation (here Relation: ‪L'Ill‬ (‪1075766‬) | OpenStreetMap) attests the continuity and direction, shouldn’t it?

Some waterways are completely missing, no idea why. EDIT: today they reappeared.

Having the ends as overlay of the default waterwaymap would be a nice extra.
A nice tool anyway!

1 Like
24

Neither to my knowledge nor according to Tag:waterway=canal - OpenStreetMap Wiki
According to Waterways it’s an end, but at the same time simply a node in the graph.

1 Like
25

Apparently some unwanted changes, maybe due to a new interpretation of waterway=canal?

26

I’ve added some new features! :gift:

Firstly, the method of allocating flow downstream has been improved. Most of the flow follows the way with the same name. This reduces the number of cases of “half the danube is being allocated to this random field”. :rofl: (for more see osm-lump-ways documentation).

Secondly, I now calculate the name (& wikidata & wikipedia) tag value of the last way that flow into the end point. This is a rough way to see the total upstream of every river in the world, by name! This is the “Ends stats CSV“ in osm-lump-ways, see the csv file format. It includes the rank of the end point by total upstream. I’m storing the top 1000 largest rivers into an ever growing CSV file. I ran it for every year since 2006.

The CSV is data.waterwaymap.org/waterwaymap.org_ends_stats.csv.zst.

You can access the CSV on the terminal like this:

$ curl -s data.waterwaymap.org/waterwaymap.org_ends_stats.csv.zst | zstdcat | ...

BTW qsv is a cool CLI CSV tool.

You can do things like:

  • № 1 largest river (by accomuilated upstream legnth) is the Обь (Ob) in Siberia. curl -s data.waterwaymap.org/waterwaymap.org_ends_stats.csv.zst | zstdcat | qsv search -s upstream_m_rank "^1$" | qsv table
  • The longest river in Ireland is the Shannon. With 5,476 km of total upstream, it’s currently the 324th longest river (:exploding_head:). By fixing wrongly connected river segments, I’ve been bringing it up, the leaderboard. I can check my status
    curl -s data.waterwaymap.org/waterwaymap.org_ends_stats.csv.zst | zstdcat | qsv search -s name ".*Shannon.*" | qsv table, and see the upstream_m_rank increase. I can check the next in the leaderboard with curl -s data.waterwaymap.org/waterwaymap.org_ends_stats.csv.zst | zstdcat | grep -C 1 ".*Shannon.*" | tail

Download it and make something cool. :slightly_smiling_face:

🪻ⓐⓜⓐⓝⓓⓐ🪻

7 Likes
27

Thanks for X-Mas one month in advance, however it doesn’t seem to correct the issue mentioned on Sept. 25.
For instance both sides of the Pyrenees are still seen a single basin: WaterwayMap.org - OSM River Basins.

28

see this other thread. :slightly_smiling_face: I think that’s a regular river bifurcation. The map you’re looking at (the default (“Waterways (incl. canals)”) ignores waterway directions. The “ends“ feature, and the “downhills“ map does observe direction, and there you can see the Pyrenees splitting water basins (if you choose 24 colours).

1 Like
29

Wow, I really like the new view! The change in width is great, adding information at a quick glance. Very nice!

30

Thanks Amanda!!
I have been using waterwaymap to fix data during some months, but I didn’t know this view. Amazing improvement in how the data can be quickly analyzed.