I've reverted this with changeset/128743390. EnumMapper, please discuss with the local community before changing one well-established accurate tag for another based on a guess. Thanks, J

Hi Mateusz, I appreciate that you've highlighted the possible ambiguity of the term "drinking fountain." I've voted no on this proposal, but I'll cease using this tag for the time being until some consensus can be reached. Thanks, Jason

There's definitely no racetrack here, so I've deleted it (changeset/128104086).

Juanicv -- you appear to have added several other raceways across the globe. It's against OSM best practice to add temporary features to the map, so if any of those other courses are in fact temporary then please remove them. Thanks, J

Hi, I see you've already figured out that this location is not the prospect park YMCA & removed this pool, thanks!

For indicating an indoor pool, I'd suggest tagging "swimming_pool=yes" on the building in question. For the YMCA building ( way/248237259 ) this was already done last month by a different mapper.

Good luck & happy mapping, J

Hello! Can you elaborate on the source of information for this swimming pool?

yes it is... I've updated the optimistic year of completion

oh, you... 🙄🙂

Just so you don't think I'm an illiterate clod, this joint does have a second (smaller) sign that says "Expresso Pizza." 🤷 I added it as an alt_name.

I'd imagine it's just a case of the same name. This one on Court Street is very un-branded -- the current sign is just a handwritten piece of paper hanging in the window.

Howdy, is the 2nd Ave segment in relation/9127857 an error?

Hi Jess, just wondering -- What's the thinking behind changing Building A from a normal building way to a single-member multipolygon?

gift shop, added

Do you know if Doyers is oneway for bikes? I was here yesterday and saw "no entry expect bicycles" signage on the south end, which would seem to suggest that it isn't.

see comments in changeset/20449020

I ran into an odd-looking building in Manhattan (way/247866947 but I've fixed it now so it's not so odd anymore) that led me to this changeset. This comment isn't for ingalls (hi though!) but for anyone else who might find themselves spelunking in this same rabbit hole.

In this changeset, address nodes were merged into address-less buildings. For each building, this involved modification of three different objects: 1) deleting of one node from each building 2) moving the address node into the deleted node's location and removing all the address tags 3) adding address tags to the building, and swapping in the relocated address node for the deleted node in the building's node list.

For reasons unknown (obviously nobody complained here), this changeset was then reverted by the OSM Data Working Group in changeset/22001873. But this reversion was buggy and caused a lot of damage. Most of the buildings went back to their previous state without any problems, but for some, only #1 and #2 (the nodes) were reverted, not #3 (the building). Those buildings kept the address tags that this changeset had added, which isn't a big problem. But they also kept their modified node list, which resulted in seriously distorted building footprints because the address nodes were moved back to their previous locations inside the building perimeter.

Zoom into https://overpass-api.de/achavi/?changeset=22001873 and see all the red outlines for a good illustration of this problem.

It appears most of these distorted footprints have been cleaned up over the last 8 years (see https://overpass-api.de/achavi/?changeset=22340943 for example) but possibly some are still broken, like way/247866947 was.

Happy mapping, J

Hi there. Please consider using geographically smaller changesets! Thanks, J

That's odd... I was sure I'd already fixed this. Looks like I didn't manage to actually hit the upload button? 🤷 Also fixed the phone & changed from fitness_centre to physiotherapist

Hi there -- I and other local mappers would appreciate if you could give accurate changeset descriptions instead of re-using the same one over and over. Thanks, J

Intentional-ish? QAing my own work in the past, I've found that changing an element from one business to another on a mobile device is an error-prone process -- in particular that an old (now incorrect) tag can evade deletion on the small screen and survive in the new POI. To avoid this I'll sometimes simply delete all the tags and start from scratch.

I didn't bother re-adding the address tags because they're not neccessary when a node is inside a correctly tagged single-address building.

Miraculous. I've had such poor luck with DOB NOW (properties I'm interested in never seem to be listed there) that I stopped trying.

I've been using the BIS tool, made a writeup of a simple search at @jmapb/diary/398764 and I'm planning a second post that will show some of the other functionality. In the meantime I'm working on finding as many shortcuts as possible through the public datasets and APIs, because using BIS is tedious.