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?

Rather amusing to see myself, as the JOSM tiles at the time I noticed it wasn't resulted in that. Presumably when downloading the area I managed to miss all the vertices!

I've checked with the county council FOI request for list of streets and matched up the names and ways for Bawburgh Road, which didn't include the one in question. So I've removed the name and source:name tags now and still suspect it's a historic name that OS has kept but that the council no longer recognises.

It's quite a few years ago I made that edit and I suspect I was going through public notices in the EDP24 newspaper. Interestingly the OS detailed map still shows it as Bawburgh Road. You're right in that both ends now have private gates and there is the disused village of Algarsthorpe between the two other Bawburgh Roads. I can imagine the road from Algarsthorpe through to Bawburgh probably did take a SE path to join to the current southerly one, so it's likely a historic leftover.

There was no need to add an additional node point of interest as nearly all your tags were already on the building closed way. It is up to the various renderers in terms of how they display the data. It is considered a bad thing to map specifically for a particular renderer. It is more useful to tag an area than a point on the ground in terms of dealership retail building.

If you wish to add post codes to roads could you please add only postal_code=tag? The addr:* tags are appropriate for deliverable properties only, per Royal Mail addressing.

Indeed, which is why I opted for a reasonable self-made suffix in the hope that software displaying opening hours my be able to parse out the variants for the end-user to comprehend when they apply. Ideally it would all be exact, but real world and all.

Whenever the local operator determines essentially, as I was surprised to find they had changed on last survey. In this case, the season is what is commonly known as Christmas, but others could be Easter, New Year's Eve/Day, bank/public holidays, who knows.

That they do, but due to the government funding for the NDR the A1194 is actually funded and operator by the county council, so from their point of view not trunk. Much like the Western end of the NDR itself.

Have been for a quick drive with dash-cam to confirm and have updated using Esri imagery. Node removed too.

https://www.norfolk.gov.uk/roads-and-transport/major-projects-and-improvement-plans/norwich/city-centre-improvements/improvement-projects/recently-completed/hall-road

If you are sure that Hall Road is currently 30 mph then that will need revising as it is all 40 mph between the two roundabouts, and in that case the note node can be removed fully.

I'm not sure why you removed my note. It was beside Sandy Lane, that throughout lack of the 30 mph sign at junction with Hall Road will be interpreted by drivers as 40 mph initially, contradicted by the 30 mph sign at the southern end of Bessemer Road. So it is indeed likely a missing 30 mph road sign, that the council have yet to fix even after I told them years ago.

There's already a source:name=OS_OpenData_Locator for where the name came from. It's not an official council one, and OS' is indeed more a description than an actual signed name, but it's the nearest thing to a name for it in that case. Could add a signed=no tag perhaps.