But `place=district`?
---

Published using OSMCha: https://osmcha.mapbox.com/changesets/80027916

`leisure=swimming_pool` is for the pool of water itself only.
---
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.mapbox.com/changesets/79805833

Are you sure there's no stairs there? At least there is for the retaining wall.
---

Published using OSMCha: https://osmcha.mapbox.com/changesets/79801963

I saw that it is under construction, no?
---

Published using OSMCha: https://osmcha.mapbox.com/changesets/79801963

Since you mentioned namespace and sub-key (excuse my inaccurate language here), I was thinking something as important as the `kitchen=` part of a restaurant deserves to be higher level. This would apply to other parts and attributes of a restaurant as well (eg: bar, drinks, outdoor seating, toilets, etc). It would be clumsy to group all tags for a feature using `opening_hours:*`. To contrast, `opening_hours:url` mentioned on the Wiki page obviously doesn't mean the opening hours of the url, but the url property of the opening hours. If a website is scheduled to be opened (for certain bookings, biddings) or closed (regular maintenance), theoretically `url:opening_hours` (more appropriately, `website:opening_hours`) woud be tagged.
(Writting to illustrate some thoughts only)

Just to clarify, I mean something like `opening_hours:atm=no` would easily show whether a feature opens in the object's opening hours, while not diminishing or duplicating possibly `atm:opening_hours=` under all other `atm:*=` attribute tags.
Like I see someone edited `dinner=`'s Wiki page to include a bunch of `dinner:*` sub-tag ideas.

Yes thanks you reminding. I reviewed that as good already, forgot to "resolved" this.

Please go ahead to add the name of this road if you know.
---

Published using OSMCha: https://osmcha.mapbox.com/changesets/79781776

Please don't delete area from the mini-roundabout. It's a mini-roundabout with no physical separation at center.
---

Published using OSMCha: https://osmcha.mapbox.com/changesets/79772982

Please change it to `=proposed` if construction is not started yet.
---
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.mapbox.com/changesets/79754799

Please don't do this. This was discussed before in osm.org/changeset/77069981
---
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.mapbox.com/changesets/79754757

Please don't delete things that exist. `access=no` suffices.
---
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.mapbox.com/changesets/79754316

As for the editing your own additions (which I'm not sure why you need to bring it up) , it did go through multiple other edits without removal. This removal doesn't look necessary.

If you don't want to do it this way, the "correct" method would be creating a `=stop_area` relation wiith the `stop_position`. However, tagging this address explicitly should be favorable.
For the obvious disadvantage, some software would show address of these bus stops as Tamar St.

What do you mean by incorrect? You haven't understood the warning correctly. `highway=bus_stop` is for compatability reason, not the intention of the JOSM warning.
It is very unprofessional to claim you are correct simply based on experience and time.

Please don't delete `addr:street=` from ` public_transport=platform` simply because JOSM shows you a warning on `highway=bus_stop`
---

Published using OSMCha: https://osmcha.mapbox.com/changesets/79750324

That's unexpected and very inconsistent, when compared with `lunch=`.
"tea service" sounds ambiguous. I haven't heard that used for afternoon tea either.
The problem with key prefix/suffix is they should make sense logically, like I know there are debates on the appropriateness of `opening_hours:kitchen`.
I see that most tags usually are valued after the suffix key. In this case, `opening_hours:*` sounds like describing the value of the suffix key in the parent feature's opening hours. This does not make sense for most if not all restaurants, but this could apply to various other features.
Hypothetically, I could imagine for example an open-door restaurant in a premise that allows people to use a kitchen or cook their own food outside its opening hour. Just a thought experiment, but this also shows an issue with ``:kitchen=`.

Better fix the stop area / private bus area south
---

Published using OSMCha: https://osmcha.mapbox.com/changesets/79714439

Hi, can you explain why `opening_hours:*`= is preferred? I saw the unprefixed keys being more popular. It also occurs to me `*:opening_hours=` would make more sense than `opening_hours:*`
---

Published using OSMCha: https://osmcha.mapbox.com/changesets/79728089

Is this discussed anywhere?
---

Published using OSMCha: https://osmcha.mapbox.com/changesets/79724584