Welcome to OpenStreetMap.

Unfortunately, we cant use Google Maps as a source for OpenStreetMap as it is prohibited by their terms of service. There's more information on the OSM wiki at osm.wiki/Google

Hi and welcome to OpenStreetMap.

Thanks for updating this. I have one suggestion, which is that if the paths are permissive for pedestrians (tagged as foot=permissive), then the same would probably apply for cyclists (bicycle=permissive). Tagging as bicycle=yes implies a legal right of way for cyclists.

access=*

This is the sort of thing where I really should write an OSM diary entry describing what I'm doing and why! When I start adding the actual restrictions, I'll write something.

I think parking:$side:zone probably does have a place even where other parking tags haven't (yet) been set.

Firstly, there's a traffic order which includes that street in a CPZ, which is the only tag we currently have for it. Maybe a relation would be better, but none has yet been proposed for this purpose.

Secondly, when other parking tags are added from StreetComplete survey or aerial imagery, it will make it a lot easier to set and keep up to date the parking conditional access and restriction tags for marked bays (and possibly single yellow lines). I haven't actually started doing this yet, but will do soon.

Finally, even where waiting is prohibited at all times, many parking authorities print the CPZ after the street name on the penalty charge notice.

Waltham Forest recently reissued their parking-related restrictions in a single order, which has allowed me to tag almost all the CPZ streets there. In Newham, it involves a lot more digging around in The Gazette.

(Review requested)

Welcome to OpenStreetMap and thanks for adding your business. I've tweaked the tagging a little to reflect OSM tagging conventions.

No problem, thanks.

Welcome to OpenStreetMap and thanks for adding your business to the map. I've moved the information from the surrounding retail area to a separate POI. You may need to correct the position slightly.

node/13235555192

Thanks! I was expecting to have a few more notes to resolve when I got home.

* source=The Waltham Forest (Parking Places, Loading Places and Waiting, Loading and Stopping Restrictions) Order 2025

* source=The Waltham Forest (Parking Places, Loading Places and Waiting, Loading and Stopping Restrictions) Order 2025

* USRNs, not UPRNs!

Thanks for updating this. Just one thing, please retain crossing_ref=zebra where it's on zebra crossings of public highways in the UK as it conveys additional information to data consumers.

Have all of those trees actually been cut down?

Hi,

Don't worry about the dragged nodes, a lot of people do that while they're getting used to the web-based iD editor. It's usually easy to spot and fix.

Adding the roads from the developer's map is a problem, because it's subject to copyright. There's more information on the OSM wiki at osm.wiki/Don%27t_copy_from_other_maps

There is some aerial imagery available which is more recent than the editor's default "Bing Aerial Imagery". If you click on the map layers selector on the right side of the iD editor's screen, you can change the background to "ESRI World Imagery". This gives you some building/foundation outlines and roads under construction (some of which may be temporary). I've added some of these.

Until the available aerial imagery catches up, there are limited information sources which are covered by the Open Government License (OGLv3). I've added what little was available from the September 2025 releases of Land Registry INSPIRE Polygons and OS Open USRN and will take a look for any changes in the October release. There isn't anything in the April 2025 release of OS Open Roads, but this should also be updated later this month.

I realise that this sounds a little pessimistic, but there are a few things which you can do to get the new streets (and houses) onto the map quickly.

1) Walk the new streets with a GPS tracker like a sport/fitness watch or mobile app like OSMTracker or StreetComplete, then upload the GPX file(s) to OSM. If you click on the map layers selector on the right side of the iD editor's screen, you can select "OpenStreetMap GPS traces" as an overlay and then trace roads from them.

2) When streets have been added, you can use the StreetComplete mobile app (currently Android only) to survey and add details like pavements, surface, street lighting, etc.
https://github.com/streetcomplete/StreetComplete

3) If you want to collect some street level imagery which has a compatible license with OSM (we can't use Google Street View), you could consider using the Mapillary mobile phone app.
https://www.mapillary.com/

I hope that helps, but feel free to ask any more questions. Happy mapping!

Apparently we also delete the correct building=yes tag of Chilton House and replace it with landuse=residential. Fixed in changeset/173027549

Has 99 Bikes moved or closed? Your changeset deleted it, but the comment makes no reference to this.

node/12878802190/history

By deleting the highway=* tag, unfortunately you have effectively made this path invisible to data consumers, including renderers and routing software. The footway=* tag only really makes sense when combined with highway=footway (or similar), see the "requires" section of the infobox at footway=*

Gates and other barrier nodes shouldn't generally be mapped at intersection nodes. Although the sidewalk way is badly aligned, I doubt that anyone walking along the pavement of Harlington Road West between Clymping Dene and Hounslow Road has to pass through it.
barrier=*#How_to_map_barrier_nodes

Would service=alley also apply to these roads?

service=alley

Has the business moved to 176 Westbourne Grove and if so, is Martin Moore still at that address?