Several of these crossings are only half crossings, with a lowered kerb and tactile paving (which you didn't add, despite it being obvious in the aerial imagery). The fictitious parts of the crossings have been deleted following a survey on 2024-09-18.

Mapping for the renderer/router is generally discouraged. Adding fictitious crossings which involve traversing an unmodified kerb and obstruction by parked cars are NOT helpful for real world pedestrian navigation.

It's in the wiki:
access= yes "The public has an official, legally-enshrined right of access; i.e., it's a right of way."
access=*#List_of_possible_values

The motor_vehicle=private tag which was there looks dubious to me.

I would suggest either access=destination (you can only use it to get there, but not use it as a through route/short cut) or access=permissive (no right of way, but nobody signed or physical restriction).

The bits of road behind ExCeL which are unadopted probably ought to have at least access=permissive + ownership=private

If there's a signed diversion of National Cycle Route 13 along Sandstone/Seagull while the dock side is closed in front of the ExCeL extension, they might need bicycle=permissive as well

Why do you believe that there is now a legal right of way (which is what access=yes means) over this section of the privately owned and maintained Seagull Lane? Have London Borough of Newham adopted the road(s)?

That's great, done. changeset/156723183

If you want to add other details to streets locally, like surfaces and cycle lanes, with less pain than the iD editor, it's worth taking at look at the StreetComplete app.

I can't find the actual traffic order or any recent imagery with an OSM-compatible licence, but if the scheme was implemented as proposed on the consultation you would need to do the following:

1) split Wheelers lane near its junction with Redehall Road
2) make the split segment one way by adding oneway=yes (you might need to reverse the direction of the segment)
3) if contraflow bicycle access is allowed, add oneway:bicycle=yes

If you wanted to upload street view imagery of all the highway changes made in this scheme, you could use the Mapillary mobile app.

Thanks for the explanation, that makes sense. I only noticed it because someone keeps adding fantasy power line nearby.

Thanks for confirming - I've updated the speed limit. It may take a couple of weeks before it "works" on Plotaroute. I'll take a look at the entry restriction later.

Welcome to OpenStreetMap and thanks for adding surface information to the road. That's useful information which some routing software will use.

I noticed that the road is tagged (not by you) with a maximum speed of 3 mph. Unless it's a privately owned road with a very low advisory limit, can I assume that this is a typo for 30 mph? This may be the reason some routing software could apply a high cost to this road and prefer an alternative.

Reverted in changeset/156673796

Are crossings like node/12156384359 really crossings in any meaningful sense, because the Bing imagery shows nothing: no lowered kerb, no tactile paving, etc.
https://www.bing.com/maps?cp=51.540076%7E0.007217&lvl=22.0&mo=om.1&pi=-22.2&style=x&dir=60.8

If there are residential streets where separate sidewalks only "work" when fictitious crossings are mapped for the renderer/router, that is a good argument not to map them. For routing purposes, tagging with sidewalk=both and mapping only the real crossings as nodes should suffice.

Is substance=gas_topology here a typo/autocomplete error?

way/1117703091

As you added sidewalk=yes to the parent roadand removed the information about a shared cycle route on the sidewalk you deleted, I fear your understanding may need a little refreshment from the wiki.

Separate sidewalks are mapped in a lot of places on OSM. The one you deleted had been there since 2014. People generally add them because they're useful for pedestrian an cycle routing. Knowing on which side of the road these features are is useful, as is the detailed information about accessibility like tactile paving and lowered kerbs.

You may think they map the mapping look messy. I would remind you that you should not map for the renderer. Deleting a feature which exists in order to "improve" the appearance of a particular map rendering is vandalism and likely to be escalated to DWG if it is repeated.

Of course I wouldn't add separate sidewalks to every street, I add the appropriate sidewalk=* tags to the parent street if mapping separate sidewalks is inappropriate. If you take a look at the streets around the roundabout, you will see that most of the available ways of tagging sidewalks have been added. On a lot of residential streets, which generally don't have crossings, they're effectively useless decoration, often added as a result of ill-advised projects using a tasking manager.

A shared pedestrian and cycle track on the sidewalk of a main road is commonly mapped as a separate way and the only justification to delete it is that it does not exist.

It does seem very odd that a mapper who spends so much time correctly adding access tags to non-public highways should be so ready to break cycle routing.

Really? What is sidewalk=yes supposed to mean? Don't break pedestrian and cycle routing just because you don't understand it, or you think the dotted red lines make the map rendering look untidy. It;s vandalism.

Also, I notice that you did not take the trouble to add tags to the parent highway to preserve the information you deleted. Adding undocumented nonsense like sidewalk=yes in a later changeset suggests that you don't know what you're doing.

Reverted, obviously.

Mapping separate cycleways and pavements is allowed and documented in OSM. Please don't delete other people's mapping just because you don't see the point.

Please revert your edit.

Thanks - I didn't realise I'd left that stub connected.

No problem. Where cycling is allowed, just adding bicycle=yes can be enough (or permissive, if that's the value already present for foot). You could also add segregated=no where it's a shared path.

If there's a circular blue sign explicitly permitting cycling, you could change it to highway=cycleway and add segregated=yes/no and foot=yes (this isn't strictly necessary, but someone will eventually add it anyway).

Please don't change highway=footway or highway=cycleway to footway=path. The default access assumptions for footway are unambiguous, those for path are not. Where ways were mapped as cycleways and had access tags (which you should not have removed), this would also break cycle routing.

Unfortunately, the names of some OSM tags are a little unhelpful and counter-intuitive, but for historical reasons we're stuck with them. If it looks like a path, it's probably highway=footway. What the law defines as a footway and everyone in the UK calls a pavement is usually tagged highway=footway + footway=sidewalk.

The mappers who added these features to the map almost certainly chose footpath for a reason.

In my opinion (and other will differ here), the only good use for highway=path is for desire-line paths also tagged with informal=yes, because no access values can safely be inferred in these cases.

I have reversed your changes because it is important that cycle routes are restored before the OSM daily extracts used by routing engines are produced.

Hi, thanks for updating this.

If a footway or road goes through a building, you can split the section where it intersects the building and tag it with tunnel=building_passage. You don't need layer=-1 here.

tunnel=building_passage

You have also tagged ways with foot=designated + bicycle=designated, which is unlikely to be the case. An access value of yes or designated implies a legal right to use a path, and designated is slightly stronger in the UK (used for public rights of way). In these cases the value is more likely to be destination (you can use it to get to the property), permissive (you can use it as a short-cut, but that permission could be withdrawn), or private (residents only, you could also add private=residents).

access=*#List_of_possible_values

Already mapped as way/204068874