Separate unnamed waterways (tagged with noname=yes) in River Database

[muralito]

Now unnamed waterways are mixed with named ones, and as they are grouped by name, unnamed ones from a "tree" that push them up in the list. I'm trying to tag names in OSM on the waterways that have one, and this grouping and the unability to filter them makes it harder.

It would be helpful that waterways tagged with noname=yes were in another list or at the end before named ones (or no named but without noname=yes)

[amandasaurus]

(a) I have refactored the code which should produce a lower total for large connected unnamed networks. That has been deployed in the last day. It is still beta quality. Can you please check if what you saw before is still a problem.
(b) I want to add something that, in the website, will show/hide unnamed rivers. I have not worked on that yet. That will hopefuly address a large part of your issue anyway. 🙂

[muralito]

Thank you. I saw it. For me, in the task of trying to complete and review the waterway mapping, its important to make 3 classes, one for named waterways, another one for nonamed waterways (noname=yes), and another class for the rest. This last class is the one I need to check each case, and complete the mapping with the tag name=* or noname=yes.

Right now I'm using a mix of your index and an overpass query.