I would agree, although I wouldn’t base that agreement mainly on either Google Maps or OpenStreetMap.
I suspect that, at least in part, Google Maps checks/derives street names from GSV images - so if a street name sign is missed, GM may extend an existing name further than it should. They do also have a tendency to extend names from parts of a road that are officially named further along parts of the same road that don’t officially have a name.
OSM derives their information in much the same way we do - by volunteer effort from the OSM community. So they often have no more valid information than we do.
In either case, use of Google Maps or OSM as a primary data source is strictly forbidden because of copyright issues. Whilst it might be acceptable to look at either to confirm something you have identified yourself, you cannot copy information like street names directly from them.
However, there is a primary data source that we can use - Ordnance Survey OpenData. The OSM link you provided is actually Musical Chairs. That uses the OSM map as a background layer (which you can’t copy) and lays green bounding boxes over the top. Those boxes are the information from OS OpenData, showing the locations of official street names. That is data we can use.
In practice, though, getting that data from Musical Chairs is not the best way to do it. If you use Twister-UK’s WME OpenData script, that will overlay the bounding boxes directly on the WME map. An additional advantage is that Twister updates his script for new OpenData releases far more promptly than Musical Chairs, which I have seen to be several months out of date at times.
Anyway, all that aside, you’re right! The road was incorrectly named and I’ve corrected it. :mrgreen:
[EDIT] I also did the original join :lol:
Thanks Iain, and for the info and explanation 