I fixed them already :)

This is also BBL, not BIN.
---

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

This looks like a BBL (Borough, Block, Lot) number. It's not the same as BIN.
BINs are specifically for buildings, not plots of land.
---

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

Please note that you can NOT take text for description from wikipedia. Their license is incompatible with OSM's license.
---
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/145967163

If this is setup just for xmas trees then that sounds as temporary/seasonal feature and shouldn't be mapped.
osm.wiki/Good_practice#Don't_map_temporary_events_and_temporary_features
Even if it's not temporary feature, description= tag should be about THIS feature, not what they do at 83rd street...
---

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

Hello.
The feature you mapped doesn't match what's visible from any of the available satellite imagery.
Could you please elaborate on what exactly are you mapping here?
---

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

If it's a "proposal", perhaps that's too soon to start tagging? What if the community rejects it or there are changes to the proposal...
---
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/145937747

Hello.
addr:state tag should be the 2 letter abbreviation, so "NY"
---

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

Hello.
addr:country should be 'ISO 3166-1 alpha-2' two letter country code in upper case.
Also that addr:housename should probably be just name=
---

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

What that website shows is the actual separation between hospital and the new development?
---

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

Hello.
There's no need to add tiger:* tags.
They are leftovers from when all these roads were originally imported into OSM. These tags are not used for anything now.
If the normal OSM tags look good, all the tiger tags can be deleted.
---

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

Once again you deleted a lot of legitimate address nodes and all the OSM history with them. 🫤
---

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

Hello.
Is there now no right turn at all from 108th to astoria blvd?
---

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

This was probably supposed to be 25 but snake21 hit wrong row. :)
---

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

Hello.
Why did you delete nycdoitt:bin tag from one of the buildings?
Every single building in NYC is registered with NYC Department of Buildings has a unique ID which allows anyone to look up various metadata about that building.
It has nothing to do with any embassy, so it is wrong to delete it!

General principle of editing in OSM, if you don't know what a given tag is for, you don't touch it.

Also you deleted a number of nodes which contain valid and legitimate address information. Just because an embassy is no longer there doesn't mean that address no longer exist.
When you delete such a node, not only do you make that address no longer searchable and routable, but you also delete OSM history of that object, which can be useful in the future to refer to.
It is much better to use lifecycle prefixes as documented in osm.wiki/Lifecycle_prefix, or at the very least delete POI-specific tags, but leave address tags untouched.
---

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

Generally, location identifier shouldn't be in the hotel's name= tag, but rather moved into branch= tag.
Also I noticed you updated phone number formatting on some of them. Generally, they should be separated either only by spaces or only by - (dash), not mixed. I suggest you install phone number validator from https://github.com/watmildon/josm-validator-rules/tree/main/rules. It can automatically fix phone= and fax= tags.
---
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/145835811

Hello.
Please note that under any circumstances you can NOT use anything from Google Maps to map in OSM. Data in Google Maps is copyrighted to Google and is in incompatible with OSM. It is a copyright violation, and you are breaking ToS you have with Google and OSM.

OSM provides plenty of different satellite imagery and Bing Streetview imagery which you are most welcome to use.
---

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

I updated it to the current biz that's there.

You reported that the existing biz is no longer there. As such this POI was tagged like that, which exposes it to other apps to encourage people to fill in the missing info.

It's not about businesses sharing history it's about preserving a history of the OSM object.
Just because a business is closed doesn't mean that address doesn't exist anymore.
And yes, that is recommended way to handle it, as you can read on osm.wiki/Comparison_of_life_cycle_concepts and osm.wiki/Lifecycle_prefix
Your actions made made this address impossible to search for and route to. If this is unintentional, I'm advising you how to improve your editing. If this is indeed intentional, then it'll be considered as vandalism and your account can be referred to Data Working Ground, which can result in temporary or permanent block.

As for your claim of this being a bad data model, I doubt that somebody with an account that less than 2 years old and made only 3 edits is in any position to judge the nuances of OSM data model. But if you think otherwise, you are welcome to make a proposal to OSMF, DWG and the community at large and offer a better way of handling this.