Hello.
When adding bus stops, please make sure to fully spell out their names, ie without street abbreviations like "St" or "Ave".
Additionally, when adding colour tag to objects, please make sure that the value of that tag is always in lower case.
---

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

Hello.
As documented in website=*#Privacy_and_security, please do not add tracking tags to urls. Furthermore, the official website has menu on it. Why link to some 3rd party website?
---

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

Should way/225868289 be a cycleway or a pedestrian path or both?
---

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

Hello.
Could you please explain why did you tag this as multipolygon?
---

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

Hello.
Just because something is not a public area doesn't mean it shouldn't be mapped/deleted.
Access= tag is the correct way to indicate that it's not open to public.
---

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

Hello.
If a business doesn't exist at a given location, it's much better to use lifecycle prefixes as documented in osm.wiki/Lifecycle_prefix rather than just outright delete the whole node. When you do that not only are you deleting that address information, making it unsearchable, but also you are deleting history of that object which can be useful to referred to in the future.
---

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

Hello.
If a business doesn't exist at a given location, it's much better to use lifecycle prefixes as documented in osm.wiki/Lifecycle_prefix rather than just outright delete the whole node. When you do that not only are you deleting that address information, making it unsearchable, but also you are deleting history of that object which can be useful to referred to in the future.
---

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

Hello.
I'm not sure this relation has correct tags..
building=roof means a building is open at least at two sides. This is most definitely not the case here.
Also unless I'm mistaken, the way you tagged inner and outer means that the building is just a narrow sliver around the perimeter rather than the whole building..
---

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

What are these garbage tags?!
---
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/130880133

Hello.
OSM is a live database used by thousands of people. It is inappropriate to perform "test" here. If you want to test something, point your editor to the sandbox instance!
---
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/130087634

Why was this feature not removed?! There's blatantly no parks here!
---
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/130130051

Hello.
If we have a fully structured street address tagged, addr:full is rather unnecessary, especially since that's not the official, full address of that library.
---

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

Hello.
If this is a street/road crossing, it has to be tagged as such...
If this is not an actual crossing, it shouldn't be mapped.
---

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

Hello.
tobacco shop with tex-mex cuisine and no smoking?🤔 Is that accurate?
---

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

What kind of osmose correction?

Hello.
Could you please elaborate what are you trying to map here? Archeological site in the middle of East River?🤨
---

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

Hello.
There's bitcoin atm inside of costco?🤨
paydepot's website doesn't show this location. As a matter of fact their website doesn't show ANY locations in NYS, so where is this data coming from?
---

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

Hello.
Could you please elaborate on this edit? Your changeset shows that you used Bing imagery to map it, however, this building doesn't appear on it on any zoom level..
---

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

"not:" prefix is a completely different thing. Same with lifecycle prefixes.
However here they just straight up invented a new category and used this prefix to define that category. That is wrong. This is now how features are tagged in OSM. If it works as a shop only during certain season then it should be tagged with correct opening_hours, not with xmas:.

A business that functions 2 months out of 12 is temporary business. A business that doesn't have a permanent physical presence in a given location and dependant on a whim of the city during that season is not a permanent feature.

I'm well aware of the xmas: prefix and I find it ridiculous. I think making xmas: prefix on every single tag is redundant, unnecessary and even detrimental. This only complicates object parsing for data consumers to handle yet another edge case for a small number of another type of POIs.

Putting xmas: prefix in front of other tags makes them invisible to data consumers.

What benefit does it give to put these features behind this namespace?! Just to get around the rules of not allowing temporary features? Any data consumer that doesn't know to support this prefix will simply ignore it and not use it. This prefix actually hides the data and makes it less discoverable.

The fact that there are maps specifically to display these Xmas: objects only further confirms that this is nothing but osm.wiki/Tagging_for_the_renderer Intentionally using nonstandard tagging for specific renderers.

What's the point of having "xmas:feature:shop=christmas_tree" instead of just "shop=christmas_tree"? And the same with all the other tags that wiki says to use. They should be standardized and be in schema with rest of OSM tags. Just because it's old doesn't mean it should exist and be in use.
With this kind of misguided prefix tagging we might as well have school: prefix for everything education-related. And have retail: prefix for everything related to stores. How about street: prefix for every road?
It is ridiculous and unnecessary. It doesn't add anything to the map that can't be expressed using existing tagging styles.

Somebody invented this Xmas: prefix 10+ years ago without putting much thought into it and it is most definitely not how people map in OSM now. Continuing to use it only does disservice to the OSM data integrity.