This article is within the scope of WikiProject England, a collaborative effort to improve the coverage of England on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.EnglandWikipedia:WikiProject EnglandTemplate:WikiProject EnglandEngland-related
This article is within the scope of WikiProject Dorset, a collaborative effort to improve Wikipedia's coverage of topics connected with Dorset. If you would like to participate, you can visit the WikiProject Dorset project page, where you can join the project and see a list of open tasks.DorsetWikipedia:WikiProject DorsetTemplate:WikiProject DorsetDorset
This article is within the scope of WikiProject Rivers, a collaborative effort to improve the coverage of Rivers on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.RiversWikipedia:WikiProject RiversTemplate:WikiProject RiversRiver
This article is about two unrelated rivers that happen to share a name (they are not even within the same watershed), and should be split as such.
How to name the two articles: The Environment Agency (and by extension Dorset Council) consistently uses "River Winterborne" for the northern river and "South Winterborne" for the southern one. Ordnance Survey mapping also uses these names, both currently and historically going back at least as far as the 19th century (see NLS viewer). Note that only the northern river is designated a "main river" by the EA, whereas the southern is just an "ordinary watercourse" which refers to smaller streams and artificial drains.
I propose we use River Winterborne and South Winterborne as the "official" names, which would mean the northern river remains here and the southern river is split off to South Winterborne (or River South Winterborne depending on naming policy). This also negates the need for a disambiguation page as hatnotes would suffice. 86.144.233.203 (talk) 15:42, 4 January 2025 (UTC)[reply]