and I think it's big 20/20 aftersight mistake at this point... Perhaps someone who views this as important to maintain needs to think of a better system so that it's less of a maintenance issue going onwards, for both editors and software. I can definitely see people accidentally adding businesses to buildings when they should be nodes (since the buildings in NYC are all multi-use) and people will keep extracting them to fix this, pulling building specific data over and over again... then who knows if Washington, DC or Tokyo also has a system like this and end up with their own washdchud:bin tag...
Just saying...

TBH tags like this that are specifically related to buildings should have a building:xyz tag so that they can more easily be known by software they should be for the building instead of related to the contents/use of the building like a shop or residential.
Perhaps a new system should be made so that it does not depend on the user editing to maintain these, the way I see it now is that it's both hard for a person and a computer to maintain these.

oops yeah that is too easy to miss unfortunately, I guess this requires someone real familiar to the buildings around here to know about that. Alas the extraction was needed, seems all these buildings have apartments on the upper floors and businesses on the ground level.
Then again what about the buildings like 69 MalcomX, not sure what the nycdoitt:bin should be for this building? (not sure why it was not there in the first place...)

nevermind, looks like you fixed it, thanks
---

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

crap. That was just a silly mistake, thanks for catching it. i'll fix it.
---

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

The note had a streetcomplete photograph of the banner, and based on that information I was able to search remainder of information via orthogonal internet searches.
---

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

why didn't you close note/3576986
Sorry just pulling your chain and giving you a hard time: :)

BTW,
relation/4091841 and
way/266674149 also did not spell it out.
However relation/4260277 spelled it out
so we have some inconsistency, technically speaking. Also TPC seems to have at least 12 golf courses in the USA so some remain unmapped ...

Tournament Players Club, apparently I think. I don't think they use the full name at all (did you have a fun time searching for the acronym? was a nasty search) hence leaving it as such, along with the fact that TPC Parkway was used for the road in TIGER and most other references - all for consistency.

I ended up reverting your changes in changeset/132954918 and readded some of it, sorry about this but needed to fix that gap.

Hi, I see there was a warning in your changeset that was flagged and it looks like you removed a section of south college avenue making it impossible to go south on college through horsetooth road. Could you fix this?

Thanks for fixing/reverting to fix that nasty overlap, I didn't feel like fixing the other errors that were partially or fully related to the overlap :D

ugh thanks. Wasn't sure what to do with it but the overlaps were annoying.

Thanks for fixing this, at least we don't have a spurious road caused by another mapper marking the road inadvertently as I first detected and noted in note/3537377 ... while I think the error is gone, did we lose information that used to be in the map, I was hesitant at fixing this because I didn't know what the original design was and feared something would have been removed by the previous changeset... any opinions?

Hi, thank you for your contributions as there's no way for me to tell things like this happening. However, this isn't the right way to denote that a road is (temporarily) no longer accessible. Basically what you did is made a road into a wall (and it looks like you dragged a node by mistake.) Will need to change these back into roads as they are real roadways, just inaccessible at the time...

Thanks for looking into this. I think when you uploaded the changes in JOSM it broke up the changes to several 10000-change blocks, so the other related changesets also need to be reverted. I'm not sure if you got a chance to take a look at exactly what these changesets did, hence the concern about them. again thanks for looking into this and keeping the map clean.

bad changesets are (2 groups): 132020418 132020411 132020405 132020398 132020394 132020392 132020388 132020383 132020379 132020374 132020370; 132015965 132015950 132015943 132015939 132015930 132015920 132015915 132015903 132015891 132015884 132015874 132015865 - I'm still awaiting confirmation that this is okay to do but would like to see it fixed sooner than later. I think I can do the revert but prefer someone else do it.

This changeset appears to add duplicate ways on top of existing ways, may need to revert this

this changeset appears to add a bunch of ways that do not exist in imagery.

This changeset adds a lot of dubious nodes that don't seem to match anything in imagery, please check, may need to revert this changeset.