Reverted in changeset/144397714

If you don't like the tag, there's nothing to stop you creating a proposal to deprecate it.

St Katharine's Way restored to highway=unclassified in changeset/144396708#

Original version of "Girl with a dolphin" reinstated in changeset/144396518

The edits to Tower Bridge North and South Towers were reversed by @Cebderby in changeset/144380733

Whether or not a mapper based in Vietnam likes or dislikes the documented and correctly used tourism=attraction tag is irrelevant. Please revert and don't inflict your personal tastes on local OSM contributors.

What makes you think that St. Katharine's Way is a residential street?

Have you ever been there?

Why did you delete "Girl with a dolphin" and its associated history and recreate it as a new object?

The footway area which you deleted still exists, although there might be a justification to change it to area:highway=footway.

Please use meaningful changeset comments - "fix track" does not adequately describe what you did, or why you did it.

I'm pretty sure that the towers on Tower Bridge were still there - and still buildings, not just bridge piers - when I ran across it last night.

Hi, thanks for updating this.

addr:postcode was actually the correct tag for the postcode as part of an address, postal_code is generally used on streets (often as just the first half of the postcode).

Thanks - StreetComplete is generally a great tool and really helps to enrich and improve the map. It's just that one quest which tends to trip people up in the UK.

Reverted in changeset/144040774

You appear to have tagged a section of Hartmann Road as foot=no in response to a StreetComplete task asking "Are pedestrians forbidden to walk on this road here?"

I cannot find any evidence in Bing street side imagery, or from my recollection of surveying this street, that there really is a (signed) pedestrian prohibition here. I cannot see any TSRGD diagram 625.1 "pedestrians prohibited" signs on the imagery, so do not believe that a prohibition exists.

The wiki states that access tags reflect legal access. Subjective opinions about whether it would be pleasant, a good idea, safe, etc. for a particular transport mode are not relevant to legal access.
foot=*

As real pedestrian prohibitions on public roads other than those tagged as highway=motorway or motorroad=yes in the UK are quite rare and are always signed, this quest is probably better left disabled.

Reverted in changeset/144040534

Welcome to OpenStreetMap and many thanks for adding these.

If the buildings you have added are seating for spectators, they might be better tagged as leisure=bleachers and building=grandstand.

The documentation for these two tags is linked below.

leisure=bleachers

building=grandstand

If this is a cannon, then historic=cannon is correct and documented.

historic=cannon

Many thanks for updating the speed limit. Could I just make one request - please include the unit e.g. "50 mph", as OpenStreetMap defaults to metric units.

Thanks. I'm not sure how you would do it using OsmAnd, so I've deleted it in changeset/143887506

Is this already mapped as node/2918084488

A quick though about roads signed as Quiet Lanes before I start the weekend...
You could add note="Quiet Lane" and/or something like designation=quiet_lane (but this could conflict with PRoW tagging) or the undocumented traffic_intervention=quiet_lane (tag used for some school streets and LTNs). That way, it's clear to other mappers why it's been tagged as a highway=living_street.

Have a good weekend.

I am no fan of "satnav idiots" either and will do what I can to help, but within OSM's rules.

Some of these problems are very difficult or impossible to solve, unless Cornwall CC bring in additional restrictions with traffic orders.

There is no street side imagery of the affected roads available with an OSM-compatible licence. If you or other local residents are able to capture and upload imagery with the Mapillary app, that could be very helpful.

For narrow roads, you can use narrow=yes and lane_markings=no. If possible, add est_width=*, or better still width=* (but this requires using a tape measure) with a single value at the narrowest point. You may need to split the road if there's a distinct narrow section. Adding lanes=1 and passing_places=yes or passing_places=no (as appropriate) may help, together with the positions of passing places as highway=passing_place nodes.

Capturing the smoothness=* values for potholed sections may help. I find the StreetComplete app (Android only) is very good for this. You can split a road in the app if the smoothness changes significantly along the road.

If there are red triangular warning signs (and I appreciate that there may not be, due to Cornwall CC's budget constraints), you can tag both the sign and use the appropriate hazard=* tag on the affected section of road. See:
https://www.legislation.gov.uk/uksi/2016/362/schedule/2/made
hazard=*#Traffic_hazards

If the three parish councils in this area write to some of the satnav providers like TomTom, that might help.

I understand the frustration caused by rat running traffic. The street on which I live was a rat run until a Low Traffic Neighbourhood modal filter, with a signed prohibition of motor vehicles was introduced.

However, we can only record facts in OpenStreetMap. Adding fictitious access restrictions and reclassifying highways in an attempt to break satnav routing is likely to be considered vandalism.

Of particular concern in this changeset, but not an exhaustive list:

way/146337398 - this is a highway=unclassified, changing it to service would imply that it is an access road and probably not a public highway. I do not believe this to be the case.

highway=living_street - unless it is explicitly signed as a Home Zone (TSRGD diagram 886) or a Quiet Lane (diagram 884), then it is a highway=residential or highway=unclassified

Private roads should generally be access=private (often gated), or access=destination + ownership=private (not gated, open and routeable for deliveries, taxis, visitors, etc.). Neither should be treated as through routes by routers.

est_width - metres are the default unit, so need not be included. Using a tilde for a range of widths is undocumented and will result in the field being ignored as unparseable. I am not convinced that these roads are at any point as narrow as 1.5 metres.

You added access=destination to a BOAT (Byway Open to All Traffic). It's a public *right* of way, which already had the correct access tags.

Use of discouraged as an access tag - hgv=discouraged is fine if (and only if) it is signed as "unsuitable for HGVs" (TSRGD diagram 820A).

You can find the road signs referred to above in Schedule 11 TSRGD 2016. These signs can also be added to OSM as nodes on the highway at the point closes to the actual sign, e.g. "Unsuitable for HGVs" would be traffic_sign=GB:820A + hgv=discouraged
https://www.legislation.gov.uk/uksi/2016/362/schedule/11/made
traffic_sign=*