You may have seen them in other changesets. I have mainly dialogued with you and canfe. I try to accommodate any feedback I receive.
changeset/113434320

I was instructed by local mappers that the original river areas were too wide, and that there is a seasonal flood when water levels are higher. Using this advice, I made the river more narrow and added seasonal river areas to denote the outer boundaries of riverbanks so that no useful terrain data is lost.
Here is the wiki page for more information in this tag: seasonal=*

As per the changeset description, I use Bing as the primary imagery source. If any areas have radically changed since this imagery date, I can make further adjustments to correct this upon request, using fixme=*

Thanks for letting me know about the seasonal fluctuations of this river.

I will fix the geometry of the river area so that year-round sections of the river are distinguished from the rest of the riverbed using seasonal=yes to avoid confusion.
changeset/113962909

Hi there! Nice work with the terrain mapping. Definitely showing this sparse region some much needed love.

Just wanted to offer a tip that the terrain tag natural=riverbed is deemed obsolete on OSM, with nearly all of its remaining cases tracing back to some faulty river imports in Italy. Can see more about this one the wiki page: natural=riverbed

Instead, it would be much more effective to use the standard tags natural=water + water=river + intermittent=yes to map these dry riverbeds. It will be much better for querying (and it also renders very nicely as a bonus).

Best of luck! And feel free to ask any additional questions in this changes thread.

Thank you for the kind clarification! I will Return to these two rivers later this week to add additional tags for certain sections, including intermittent=yes, seasonal=yes, and landcover=* in order to more accurately represent where actual water is located, where the river reaches during annual floods, and the stony terrain on the ground during dry season.

This solution should hopefully help preserve the accuracy of your riverbank contributions without sacrificing consistency with adjacent rivers.

relation/1120336/history
To maintain consistency with tagging schema used on the larger adjacent river Po (linked above), river area tags have been modified. This minor change will improve indexing of water and river areas in northern Italy while rendering the same way as waterway=riverbank on all modern platforms.

If there are any additional concerns, please leave a comment on this changeset.

relation/1120336/history
To maintain consistency with tagging schema used on the larger adjacent river Po (linked above), river area tags have been modified. This minor change will improve indexing of water and river areas in northern Italy while rendering the same way as waterway=riverbank on all modern platforms.

If there are any additional concerns, please leave a comment on this changeset.

Note: The adjacent river Dora Baltea already uses the tags natural=water + water=river to define its corresponding river area. This tagging nomenclature has been applied to the river Chiusella to avoid inconsistency.

The changeset aims to fix a multipolygon river area which was not fully incorporated into a relation (not including its inner areas). If any issues arise with the relation due to these intended fixes, leave a comment.

Hi Andrea. I have been addressing several fixme requests and iD errors for imported landuse polygons. In this case, I made some adjustments to the geometry because it was slightly too wide and erroneously overlapping other landuse areas.

In the iD editor it will sometimes ask to take extra steps like merging duplicate nodes, adding bridges and tunnels, and updating tags before saving changes.

I always make sure to check the surroundings before changing tags like these. If there are two adjacent river areas with different tags in the same town, I believe it is bad to ignore it and not make them consistent so they are easier to index. I also make sure not to add water=river tags for canals and drains.

If I assign an inaccurate water=* tag, I will go back and fix it per request, like I have done with the water=stream areas earlier this week which you pointed out.
changeset/113460519
---

Published using OSMCha: https://osmcha.org/changesets/113636801

I have changed the tagging from water=stream to water=river. Leave a comment on the new changes if there are any further issues.
changeset/113460519

Sorry about the misunderstanding. I will recheck any recent stream areas I have placed.

There are a lot of additional problems in this region with very wide waterways tagged as streams. I left the ways alone and only modified river area and land use polygons. But I believe there is an over-abundance of waterway=stream. This should be checked by locals to prevent future issues from arising.

>"Please not!"
Haha, noted.

And I hope to start using JOSM soon once I acquire better hardware to run it. The steep learning curve is daunting, but it'll really help with adding and fixing relations.

I apologize if I left certain issues unattended. I use the iD editor and would rather not mess with complex broken relations I do not feel qualified to fix.

Aside from standardizing tags with adjacent water features, I also remove duplicate name tags when one is already present on a waterway, extend waterways through river areas when one is not already present, add intermittent tags when rivers appear to be primarily dry, etc.

Thank you for letting me know about this, and I will add Fix Me requests if I encounter further issues of this particular nature.

Hey ftcat. Please try to avoid reverting river areas to waterway=riverbank. This tag is being rapidly phased out globally in favor of waterway=riverbank, with Zambia being the last country in Africa that still primarily uses the older scheme at this time.

Many JOSM users are not aware of the issue, but the iD editor will mark waterway=riverbank as an outdated tag for contributors to fix.

For more information about the global effort to unify river tagging with the use of natural=water + water=river, check out this wiki project page: osm.wiki/WikiProject_Waterways/River_modernization

The only one strong enough to stop ZeLonewolf is ZeLonewolf.

Great work micromapping Mexico's rivers. Just wanted to note a slight issue with the tagging. The JOSM editor currently tags river areas as waterway=riverbank by default, but this tagging scheme is in the process of being phased out globally, especially after the iD editor began marking traditional "riverbank" water areas as outdated tags.
For better consistency with a majority of Mexico's (and the world's) river areas, it is strongly advised to use the modern tagging scheme of natural=water + water=river.
Feel free to message me if you have any questions of concerns, and check out the River Modernization project page for more info about the status and outreach we perform.
osm.wiki/WikiProject_Waterways/River_modernization

Hi Wotan. Thanks for fixing those culvert issues. I think a different water area tag should be used for the canal though.

Waterway=riverbank is a tag previously used for boundaries and areas of rivers, but it was voted to be deprecated in 2011, despite JOSM still having it as a preset (osm.wiki/Proposed_features/Water_details)

It would be more appropriate to tag rivers as natural=water + water=river, as now a vast majority of the world's rivers use this system. It also allowed canal areas like this to be tagged as natural=water + water=canal for better clarity.

For more information about the global efforts to improve and modernize river tagging, there's a wiki page here: osm.wiki/WikiProject_Waterways/River_modernization

Aw no problem. Already fixed the four riverbank tags from yesterday. They're easy to spot because they stick out like a sore thumb in Canada on TagInfo: https://taginfo.openstreetmap.org/tags/waterway=riverbank#map

JOSM has still been slow to adopt the new tagging presets, so it's hardly your fault. For more info on the global phasing-out of waterway=riverbank, there's a wiki page for it here. osm.wiki/WikiProject_Waterways/River_modernization

It also isn't necessary to add a name=* tag for river areas if there is already a waterway drawn though it that has the name. That way the same POI isn't named twice.