This article is within the scope of WikiProject Greater Manchester, a collaborative effort to improve the coverage of Greater Manchester 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.Greater ManchesterWikipedia:WikiProject Greater ManchesterTemplate:WikiProject Greater ManchesterGreater Manchester
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
The article on River Goyt is supported by the Derbyshire WikiProject, which is a collaborative effort to improve the quality and coverage of Derbyshire-related articles on Wikipedia.DerbyshireWikipedia:WikiProject DerbyshireTemplate:WikiProject DerbyshireDerbyshire
This article is within the scope of WikiProject Cheshire, a collaborative effort to improve the coverage of Cheshire 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.CheshireWikipedia:WikiProject CheshireTemplate:WikiProject CheshireCheshire
It is not clear where the current text has come from but the River Goyt does not rise on Axe Edge but, if the longest headwater stream is followed, then rather on the east side of a 547m high hill un-named on the OS map but just to the north of Whetstone Ridge at OS grid ref SK 0035 7099. The length of the river from that point to its confluence with the Tame where their combined flow forms the Mersey is 39.9km or 24.8 miles. I'd be confident of the accuracy of the figure to within 1%. This is of course original research on my part so cannot be included in the article but it does at least give an idea of what a true figure should look like if and when an editor finds a suitable reference out there! cheers Geopersona (talk) 21:06, 11 January 2022 (UTC)[reply]