Good spot, so I guess all that's needed is to revise motor_vehicle=no to vehicle=no, with the override more-specific exemptions for psv/bicycle and default UK foot=yes.

DfT "Know Your Traffic Signs" contains "Blue circles generally give a mandatory instruction,such as 'turn left', or indicate a route available only to particular classes of traffic, e.g. buses and cycles only" and "Blue rectangles are used for information signs except on motorways where blue is used for direction signs". Traffic can be understood to include pedestrians, though OED defines as vehicular.

In this case there's separate pavement provision and the sign 'only' implies all except listed mode types, which to me excludes pedestrians. I've been trying to find where in law it's okay for pedestrians to walk in bus lanes or in zones such as this. Am fine with tagging to law, just want to be certain about the legal interpretation.

The pavements are legal for pedestrians of course, but that split-section of road is not legally permitted to walk and has no pavement. The resolution could be to explicitly create a footpath/sidewalk for pedestrian routing while maintaining the correct legal restriction on the road ways.

So are you saying the legal sign bus and cycle blue instruction type means pedestrians are permitted? That seems risky considering it's a bus lane.

It seems you erroneously removed the default access=no from the bus/cycle-only section of road 3 years back linking Clover Hill Road with Earlham Green Lane. Or was there a reason for doing this?

House outlines

I've corrected a typo in store name introduced by this edit all those years ago. It was “Infnity Motorcycles”, now ‘Infinity Motorcycles’.

I note you used highway_ref key instead of highway_authority_ref, has opinion on that changed?

That looks rather like tagging for the routing agent, the map data itself is fine and legally a U-turn if possible at either end of the split road, if inadvisable. The solution here is to adjust the routing agents to weight with penalty turns greater than 270 degrees.

Morrisons is no longer signed there, B&Q has been extended to include it back with similar outside texture/colour. The Computers 4 Africa part has also gone with a Garden Centre canopy making use of the former external space. I've also amended the car park speed limit and added the give ways.

You added " Norwich" suffix to the name tag of one near me, but it's only signed as "carshop" (lower case). The Norwich part is geographical and not necessary for a name tag, nor the address house name. However, I accept it is used on their website, like many, to help distinguish between the national set. So if you must add it, use nat_name key instead?

This looks like tagging for the routing agent to me. There is no legal restriction on turning right into the Loddon Bypass NE exit slip road from A146 westbound. To me this looks you created the no right turn restriction to ensure trucks don't take the shorter but high angle turn (248 degrees). However, the truck/van routing really should take account of the turn angle itself, and not rely on imaginary legal routing restrictions. This is not the truth on the ground.

Table Table is the chain name, this pub is still called Showground per the name on the side of the building and its website. So I'll revert the name change unless you counter otherwise with suitable source.

At time of NaPTAN imports there wasn't a v2 tagging schema, and it was neatly imported overall without highway=bus_stop for those points with customer preference or out-of-use from the services. The v2 schema's design essentially seems to want to remove highway=bus_stop to supersede/replace it with public_transport=platform and bus=yes. I don't really get what's wrong with highway=bus_stop and why that can't be just supported into their platform member picks. What confused me was seeing a highway=bus_stop with public_transport=platform but not bus=yes tag, which also triggered the validator.

I'm not sure why highway=bus_stop really requires additional tags bus=yes and public_transport=platform. It just seems messy and part of the design issues with v2 public transport schema. I suspect the reason all this happened was because of auto-routing picking the nearest road from a bus stop with the wrong outcome, likely because the stop position wasn't positioned well.

Please note that when there is no physical separation of lanes per Dereham Road between Longwater Lane and Longwater Retail Park that it should be mapped using only one way, except for where ways split such as staggered toucan crossing.

There are a few uses of plug in keys per https://taginfo.openstreetmap.org/search?q=plug but none that seem to be Tesla-specific, which in general is a special case with own type value that may be enough for real-world uses.

I've added a bit to the discussions on relevant pages to see if it triggers any desire for more-specific tagging or something additional to give useful info as to whether own cable is required.

Shall keep with socket myself then for time being. Thanks for swift response.

Except they are actually tethered plugs with the socket being on the cars themselves.

Why did you remove the A47 reference tags from the A47 entry/exit slips? It was fine to add destination:ref=A11 to the NW/SE exit slips, however, aren't the underlying link roads part of the A47 bypass build?