Hello.
You mapped a fire hydrant and indicated its water source is "groundwater". Are you sure about this tag value? "groundwater" means a natural water well. As far as I know McCarren Park doesn't have such a well.
Please see water_source=* for the list of possible values and their meaning.
This should be corrected.
---

Published using OSMCha: https://osmcha.org/changesets/148932955

Hello.
You mapped a fire hydrant and indicated its water source is "groundwater". Are you sure about this tag value? "groundwater" means a natural water well. As far as I know McCarren Park doesn't have such a well.
Please see water_source=* for the list of possible values and their meaning.
This should be corrected.
---

Published using OSMCha: https://osmcha.org/changesets/148932901

Hello.
Please note edits made in this changeset must be fixed.
"leg material=" is not a valid tag for 2 reasons:
1) In OSM must tags must NOT contain space in their name.
2) "leg material=" is simply not a tag that exists in OSM. Please see this article for all the documented tags you can use with benches amenity=bench
---
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/148932734

Which part should be in the wiki?
If you want to find more mistagged features you could use overpass-turbo, which gives you SQL-like interface to get data out of OSM.
Or you could use external tools like Osmose or in iD and RapiD open "Map Data" side panel and turn on Osmose, ImproveOSM and KeepRight validators. (but be careful about fixing some of those problems 😉)

OsmCha uses mapbox imagery, which is iD/Rapid/Josm. while clear, it is rather outdated by now.

What iD shows are just commonly used values. Many of those values can be wrong, such as "tbd" and "90".
Ultimately, you can use any value you want, even "Iras_favorite_lamppost", but no data consumer will know what it is and know how to handle it so it'll be just ignored. So what's the point of putting all this effort if your effort gets thrown out.
"Lamppost" is a plain American English terminology. But as you've seen, OSM uses British English and also certain industry-specific terminology. So words we use in everyday life might be be the same as what's used in OSM.
Lamppost is just a generic word. Is it straight? is it bent? Is it split? Is it double? That's why we have those predefined values that describe different types.

Hello.
Instead of deleting existing features and creating new ones, whenever possible, it's better to update the existing features into their correct state. Doing that preserves history of that object, which can be useful to refer to in the future.
---

Published using OSMCha: https://osmcha.org/changesets/148916137

Hello.
If it's named Baptist Church, why is denomination protestant?
---

Published using OSMCha: https://osmcha.org/changesets/148894278

Hello.
The way you added phone numbers is not outright wrong, but it's more correct when they are separated either by space or -. This format is documented on phone=*#Usage 👍
---

Published using OSMCha: https://osmcha.org/changesets/148878648

What is the current name?
---

Published using OSMCha: https://osmcha.org/changesets/148843520

Hello.
What is the source of these changes?
None of the available satellite imagery matches what you added.
---

Published using OSMCha: https://osmcha.org/changesets/148830301

In my opinion, we should map things only "when the shovel hits the ground" sort of thing, when the actual work that affects people on the ground happens. Using this approach not only eliminates the ambiguity and uncertainty when looking at the map and certain maps/routers don't easily distinguish between existing and planned/proposed features, but also decreases the amount of effort we have to put into keeping the map current. You mapped this proposed plan, but then nimbys will complain and DOT will have to revise that proposal, which you'd have to update once again(?), then update it again when they finalize it and start actually building and then update it again when it's actually done.
On the other hand, map it once when the construction starts and update it once it's live...

Then "straight_mast" or "bent_mast" sounds suitable for whatever shape they are.

I'm still not sure if we should be mapping "proposed" features. They are not even officially approved/planned.. OSM is a map of the world NOW, not some point in the undetermined future...

But at the very least, shouldn't this be mapped with proposed: namespace prefix rather than just putting "proposed" in the route name?
---

Published using OSMCha: https://osmcha.org/changesets/148827340

Well, I don't know what kind of lights they are so I can't tell you what tags to use, but I most definitely know that "lamppost" is not a valid value.
And "lampposthttps://www.mapillary.com/app/user/robinzyxhttps://www.mapillary.com/app/user/robinzyxhttps://www.mapillary.com/app/user/robinzyxhttps://www.mapillary.com/app/user/robinzyx" is not a valid value either.

You mapped the same vent twice with 1263760686 and 1263760685.
Also, when mapping such features you can right-click on them and select "Make Square" to make nice rectangles rather than wonky trapezoids.😁
---

Published using OSMCha: https://osmcha.org/changesets/148819576

Every single streetlight you added in this changeset has wrong lamp_mount= tag value. Please correct them. 👍
---
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/148795710

Then it should be
Fr 12:00-17:00, Sa "by appointment".

I updated it with current height👍

Hello.
Please write more descriptive changeset messages. just pasting wikidata article number doesn't help others understand what you are editing.
---

Published using OSMCha: https://osmcha.org/changesets/148760662