It isn’t called Twitter any more. National news here talks about 'posts on X'. It's taken time, but people are learning its actual name, like its app title. “formerly known” is key there. The OSM wiki standard simple is outdated. In a way I don't care if tags are standardised to a single value so in future they can be mass updated. There needs to be a proposal in the wiki for those like yourself who strictly adhere to that.

It’s a stupid convention to document an outdated name. The discussion there hints to the desire to fix it.

Thing is the tag currently documented is simply outdated. x.com is currently working on stripping the servers with 'twitter' in them too. It has been X for quite some time now. I am free to use whatever tag I feel best describes the data. You just override that choice to please existing data consumers.

Have they all been relabelled as 'Bring Bank's?

I’m sure Unicode support in OSM tagging is widely supported.

"addr:street"="Rawley Road. old people’s home" does not look valid Royal Mail line.

Thanks!

Noticed that Royal Mail only has postal city for these, but county council addressing includes Thorpe St. Andrew as suburb district.

You really can’t rely on years out of date proprietary Google StreetView as your primary source.

Thanks for pointing that out. Have corrected the tagging.

There’s no need to suffix node type ' Village Sign' in the name key for man_made=village_sign. Some visiting it only sees 'Hethersett' inscribed into the woodwork.

The loss of car driveable space by a 24/7 bus lane. You/your bot set busway:right=yes, which could have been busway:right=lane. So busway key deprecated, but cycleway=share_busway still a thing? How to explicitly state that bus lane in 24/7?

Thanks for that informational loss…?

Agreed, done.

That's the wiki for you. However, I was right about no unit being an increase in ambiguity for the casual mapper. With time, someone will inevitably come along and add the ' km/h' back in by bot. Essentially, was just questioning the necessity of data removal that was already correct, which you have yet to respond to. It’s something to do, I guess.

Removing explicit unit from maxspeed tagging only introduces ambiguity and little benefit other than a few bytes per text record in a database.

Default power unit is kW for that tag. You can add it explicitly if you like with a single white space separator.

Think about the 'dual' bit. They come in pairs. Individual way tagging can be done of course, but then which is the paired carriageway? Fetch all dual_carriageway ways then correlate by name/ref/geography? What if those aren’t consistent/cross boundaries? Did you know that carriageways in the UK typically have ref A and B? For Away from London, Back to London, usually. Can be seen from the emergency layby phone refs. Just because something is more frequently used, doesn't mean it is best. Plus mappers are free to tag as they see fit. My point about inferring from maxspeed=GB:nsl_dual remains. Are you thinking about urban dual carrigeways too with limit under national?

The southern bypass is already part of a dual_carriageway type relation, with GB:nsl_dual maxspeed, so is it really necessary to explicitly add way tags too?

If you remember/have photo, could add post_box:type and royal_cypher tags perhaps?