Hi,

You don't need to exclude mopeds from motorways in the UK, as moped=no is the implicit default.

osm.wiki/OSM_tags_for_routing/Access_restrictions#United_Kingdom

In any case, adding moped=no to the route relation rather than highway segments is unlikely to have any effect.

If you're having a problem with routing software choosing UK motorways as appropriate routes for mopeds, you may need to raise a bug report with the provider.

Please stop deleting and replacing objects, as this not only loses the object's edit history, but also the tags any tags which you haven't copied over.

osm.wiki/Keep_the_history

Reverted in osm.org/changeset/142488342

Original track relation restored, along with its history and original tags in osm.org/changeset/142486297

Hi, welcome to OpenStreetMap and many thanks for adding this path.

As you asked for a review, I have a couple of comments. I hope you find them useful and please don't hesitate to ask for help if you need it. These aren't critical enhancements, so it should be recognised by your routing software next time it updates (varies, can be weeks).

The name tag should only be used for the name, not a description.
osm.wiki/Key:name

In order to make routers aware of the opening hours for the path, you could do it with a conditional restriction, like:

foot=permissive
foot:conditional=no @ 17:00-07:00

You could also add the gate as a barrier=gate node and the same access tags. I've assumed that it's not a public right of way, hence the permissive access. It may also be better to change it from highway=path to highway=footway, as that implies bicycle=no, horse=no, etc. by default.

There's a ford=yes tag applied to the whole length of the path, which might deter routers from using it. If there is a ford, it would be better to map it as a ford=yes node at its position. Alternatively, if the path is prone to flooding, you could add the flood_prone=yes tag.
osm.wiki/Tag:ford%3Dyes
osm.wiki/Key:flood_prone

Why have you replaced the amenity=parking polygon (representing the entire car park, if you care to read the wiki) with two amenity=parking polygons (which should be amenity=parking_space). Discarding the object history, along capacity and operator information, was less than helpful.

Incidentally, what makes you think that the high jump mats are a building?
osm.org/way/1214812417

You appear to have deleted several existing features in Mile End Park, together with their associated history and replaced them with similar geometries, but with fewer tags.

Please explain and revert.

OpenStreetMap is a live map and database, not the place for you to do test edits. The place for those is /dev/null or your own GIS.

Reverted in osm.org/changeset/142393551

No problem, updated in osm.org/changeset/142385424

Welcome to OpenStreetMap and thanks for adding the address.

As you asked for a review, I have one suggestion and a question.

If you want to include the full postal address in a single tag, you need addr:full rather than addr:housename.
osm.wiki/Key:addr:*#Commonly_used_subkeys

Are you sure that you have added the address tags to the right object, as this appears to be the main building of Alfred Salter Primary School? There are already two objects named Scape Canada Water on the other side of Quebec Way:
osm.org/way/1213007571
osm.org/node/11252485981

Thanks.

Google Maps is not a permitted source for OpenStreetMap, so this changeset may need to be reverted or redacted.

osm.wiki/Google

Welcome to OpenStreetMap.

I'm not sure what you were trying to map, but there isn't a disconnected residential road in the back garden of a house on Kingsley Way. I have deleted it.

Please make relevant changeset comments, as a hashtag produced by Humanitarian OSM (HOTOSM) is gibberish when not used in its intended context.

osm.wiki/Good_changeset_comments

Feel free to delete the *_link ways, but please update the lanes=*, turn_lanes=*, sidewalk*=* and cycleway*=* tags on w1194242332 and w1194242339

Yes, the tagging should have been amended. As you didn't see fit to do that, it was quicker to undelete.

@Sandal man The size of the changesets made by a StreetComplete user is unlikely to be under their direct control. There's a description of the problem at https://github.com/streetcomplete/StreetComplete/issues/4582

I have prefixed the tags on the pontoon with removed:* in case you need to re-use the alignment for a future event.

Why would an alpine refuge in Iceland have names in English and Spanish, names which look more like descriptions?
osm.org/node/11188849137

Thanks for updating these.

This isn't an error by you, but unfortunately the iD editor presents the general access=* key as if it were likely to be relevant to a highway=footway. This is very rarely the case. Setting access=yes theoretically means that all transport modes can use the footway. Setting access=no in combination with other tags which override it has no effect on routing, but unhelpfully causes the standard OSM Carto tile layer to render the footway in faint grey dots instead of the usual red.

There's some detail on public rights of way in your area, which you might find useful, at https://osm.mathmos.net/prow/progress/herts/dacorum/hemel-hempstead/

Sorry for the delay, I got sidetracked by other things.

I've made a couple of tweaks around the Buxton Road/Leytonstone Road junction, including adding bicycle=yes (which shouldn't be necessary) to the section of road which also has separate cycleways.

osm.org/changeset/141069078