Hello.
Just like in the previous edit, please don't abbreviate names. They should be fully spelled out. You can read more about this at osm.wiki/Abbreviations
---

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

Hello.
Other than proper names, tag values in OSM should always be in the lower case. Instead of "Black" it should "black".
---

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

Hello.
When adding proper names to OSM, and otherwise, please don't abbreviate them. Instead of "dep" it should be "Department".
---

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

Steps shouldn't have name of sidewalk... It's perfectly fine if some features don't have names. You don't have to try to name everything.
---

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

Hello.
Please pay closer attention to where exactly you place features. In this edit you glued benches to the perimeter of a grass lawn. That's technically incorrect. Benches should be separate nodes. You can right-click on each bench and select "Extract". That will disconnect that node from the way and you can reposition them exactly where they should be.
Additionally instead of name= tag, perhaps those names are better suited for inscription= tag as documented on inscription=*
---

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

Hello.
Please try to position stairs exactly where they start/end, and not to extend them beyond.
---

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

This edit has similar issues to the previous one. Instead of drawing a new path on top of the existing one, you should split it where conditions are different and mark only that section.
---

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

Hello.
Please be careful when you pan the map around. It looks like you accidentally dragged parking lot node a block away.

Additionally, when you added that trash can, you glued it to the outline of the parking lot, which is obviously incorrect.
Please pay closer attention to not to accidentally damage existing feature and to place new features where they actually are..

I'll fix these issues for you.
---

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

Hello.
Rather than drawing new way on top of existing one, you should split the current way where conditions change and apply relevant tags only on that section. Otherwise when navigation routers look at this section and see 2 overlapping ways with different tags, routers won't know which way to consider valid.
---

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

Hello.
Please note that incline=up/down is an invalid tag value. It should be either up OR down relevant to the direction in which the way was drawn (you can tell the direction by the small triangular arrow in the middle of the way).
Additionally, this path should be connected to the rest of the pedestrian network in the area, otherwise navigation routers won't be able to use it.
---

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

Hello.
Could you please elaborate on your edit here? Satellite imagery doesn't match to the feature that you mapped here.
---

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

Hello.
description tag is not intended for documenting temporary road conditions, which can change as soon as the surface repaved. The description tag is intended for a neutral tone description of a given feature.
---

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

Hello.
Please note that in OSM other than proper names, all values must be in the lower case. So instead of "Black" it should be "black".
---

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

Hello.
Please note that OSM is a live database used by thousands of data consumers with millions of users. It is inappropriate to create test or "demo" edits in the live database.
---

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

Hello.
None of the features you mapped here are correct.
The closest tag to what you are trying to do is perhaps leisure=garden with location=rooftop.
If you continue to ignore my comments and incorrectly map these features, your account will be referred to Data Working Group, which can result in temporary or permanent account ban.
---
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/165290426

Hello.
I'm not sure if it's correct to tag this as a single building with building:parts, since according to NYC's building database on this plot there are 2 buildings: https://zola.planning.nyc.gov/l/lot/4/09301/0024#19.14/40.6956767/-73.8358081
"Number of Buildings: 2"
Additionally, BISWEB database shows 2 BIN numbers on this plot: 4194848 and 4440557
https://a810-bisweb.nyc.gov/bisweb/PropertyBrowseByBBLServlet?allborough=4&allblock=9301&alllot=24&go5=+GO+&requestid=0
You can use https://jmapb.github.io/nycaabs/ to look up BIN numbers and see where they are positioned.
---

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

Hello.
Please put some effort into *accurately* mapping buildings. None of those buildings are crooked triangles that you drew, or other weird trapezoid shapes.
---
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/165250588

Also, while you are looking at those, some of they even have disparity in the actual name= tags.. Perhaps it's a matter of name= vs official_name=

However, some of your changes created disparity between the nodes you updated and actual boundaries.
For example, node/158915196 vs relation/175510, or node/12643982969 vs relation/1839631, and others.
---

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

You can use https://jmapb.github.io/nycaabs/ created by another nyc mapper. This site can quickly search nyc building database and extract relevant metadata, like BIN, height, address, age, and plenty of other useful links like to ZoLa and different building work order permits.
Right-click on the minimap for more features.