I removed this as a duplicate of node/4242642657.

It looks like you've changed building=retail to building=yes, if these are shop buildings, then building=retail would be better. Did you want to change it back?

It's okay to map private driveways in OSM, you can use the access=private tag to indicate private access, I've done this in changeset/73993556.

@WoodWoseWulf There is way/544057064 many different kinds of grasses side by side there.

In this context leisure=garden is not talking specifically about the flower bed landuse, it's saying this venue, the Royal Botanic Gardens, is a planned space set aside for cultivation, and enjoyment of plants and other forms of nature.

Those cafes are all part of the gardens venue, since this is not a landuse or landcover tag I think it's fine.

The "woods" inside are all part of the gardens.

You can think of this as a more specific type of park.

Lastly I know the name itself doesn't imply the tags we should use, but it is called Royal Botanic Garden not Royal Botanic Park.

On the other hand... the individual gardens which make up the whole Royal Botanic Gardens are mapped as leisure=garden eg. relation/3625726. So now I'm not sure, I probably still think leisure=garden on the larger area is better.

In my opinion, leisure=garden is correct per leisure=garden. leisure=garden in no way implies that the landuse is all flower beds, so it's okay to have cafes and shops, etc. inside the gardens. You can map out the garden beds individually for more detail as landuse or landcover for more detail.

When did you survey this, it looks like on a weekday this is a highway=living_street, but on the weekend acts more like highway=pedestrian, as it's closed to cars, but still accepts cars at some hours for deliveries.

No idea, I think it's okay to delete.

Looks you you've dropped tourism=hotel from way/426966792 in this changeset. I've added it back, last time I checked it was still a hotel.

The distinction in OSM between bad and horrible is very blurry, keep in mind that trail_visibilty=bad already means "Path sometimes invisible, route partly pathless", which certainly would be almost unusable or completely unusable to some people. That said I'm fine with this change, "horrible" is also appropriate for "Often pathless".

On my hiking map I render bad and horrible the same as a faint dotted line compared to the good or excellent visibility paths, see https://www.beyondtracks.com/map/#13.83/-34.11294/151.03679

Thanks for not just deleting the track, since if there is evidence on the ground of a path and people still use it and follow it, even if it's faint or overgrown, then I think we should still keep it in OSM,

reverted see osm.wiki/Spam#SEO_Spam

is addr:city a new thing, from memory this wasn't in your original imports. I think it's worth having a discussion about addr:city vs addr:suburb.

I'm not sure if there is a best practice. It's certainly much more common to do either a block at a time, or a whole area covering several blocks though. A polygon for each parcel although not that common, I would say is valid.

way/715622438 shouldn't use the name tag for the street address. You can use addr:housenumber for that. osm.wiki/Good_practice#Don.27t_use_name_tag_to_describe_things the name tag should be for the common name of a feature only.

I've deleted node/6723460485 as a duplicate of node/6240817600

Per osm.wiki/Good_practice#Don.27t_use_name_tag_to_describe_things I've changed the "name" to "description"

Cheers, I just did a survey of this area and will upload to Mapillary soon and yes these are really gone.

It looks like you've tagged Emporis.com as a source, could you specify what data was used, and can you point to the licensing etc which backs up why we're able to use this in OSM?

Looking at https://osmlab.github.io/osm-deep-history/#/way/608090448 what's the intention here?

bicycle=no is already the default for highway=footway, and access=private also implies foot=private.