Hi again, if I don't hear back from you I'm inclined to revert this changeset, as it's currently a map error.

Hi yonatanlivney, can you clarify this changeset? You've created a new building (way 66794170) overtop of three existing buildings. Have these old buildings been demolished? Are the old addresses (1 Bond, 7 Bond, and 350 Lafayette) no longer in use?

Hi -- This office is tagged with address 4910 but the node is placed in the building 4908. Is it possible that the node is positioned incorrectly?

Hi Shane-Lester 99, welcome to OSM!

It looks like you've added a building here ( osm.org/way/667064179 ) overtop of an existing building ( osm.org/way/241845016 ). This is considered a mapping error. It's probably better to just draw a node for St Johns and put it inside the existing building, rather than creating a new one. It would also be good to tag it with some basic info, like "amenity=college" and "website=https://www.stjohns.edu/campuses/manhattan"

I'd be happy to assist with this if you have any questions.

Thanks for your contributions, jmapb

Hi -- Looks like you changed the name= but there's still a name:en= with the old name -- is this intentional? (Also guessing that this node should be moved inside the building perimeter...) Thanks, J

Well, looks like you accidentally removed the entire building. I reverted all these changes so you should be able to start over and try again. Good luck, J

Hi Daniel, OSM uses the traditional European definition of "deli", not the American one. See osm.wiki/Tag:shop%3Ddeli

Hi mdroads -- Any particular reason to remove the cuisine=italian tag from Vapiano?

Hi Paldesk -- I'm inclined to revert these changes if I don't hear back from you. J

Hi Paldesk -- unless you're the only tenant in this building, please represent your office with a node instead of tagging the entire building.

Regardless, it's wrong to delete the "height" and "nycdoitt:bin" building property tags from the building way.

Thanks, your pal. jmapb

Aha -- I see my mistake! If you click on the profile photo on Facebook (in the circle), you can see "Unnameable" on the large sign over the window, but the hanging shingle sign says
UNMAL
NAEBE
and I read it straight across. Silly me.

Hi red_clover -- check again! I thought the sign said "Unnameable" at first but I"m pretty sure that "Unmalnaebe" is, in fact, the spelling on the sign.

Revered in changeset 66173284

I like to keep the map and the database as simple as possible, so I'll prefer to add the POI (shop/restaurant/etc) tags to the building itself -- IF, big if, it's the sole tenant of the building. I tagged the post office at osm.org/way/248179013 this way, for example. But in NYC this is rarely the case -- most buildings have multiple tenants. If a building has a separate residential entrance, or multiple commercial units, then I'll generally use a node for the POI.

Similarly with addresses -- if a building has only one address, then the address tags go on the building. If it has more than one, then we use nodes for the various addresses, ideally located near the entrance in question.

This is the addressing method that was used during the NYC building shape import that happened in 2013, so it's best to follow that standard. In Brooklyn it was also decided in most cases to tag the addresses with house number, street name, and zip code only -- the zip code and geographical location both unambiguously put the address in Brooklyn NY USA, so it's not necessary to add the city, state, and country fields. Saves a little time.

Another shortcut is that when placing a POI node in a building that has only one address, there's no need to add the address tags to the POI at all. It will inherit from the building it's in. Though some people do like to add the extra tags anyway. See https://help.openstreetmap.org/questions/48735/address-information-in-poi-and-building for a discussion of pros and cons.

Happy mapping, jmapb

Hi Alon_Av, please take a look at these items. If I don't hear back from you, I'll be inclined to revert this changeset which appears to be erroneous. Thanks, jmb

Hi hshore29, thanks for your updates in Clinton Hill.

Regarding this closed restaurant: In cases like this it's preferable not to delete the node, but rather just to change or remove the tags that no longer apply. The node still represents the premises in question and can be re-tagged with new information when a new tenant moves in, allowing us to preserve a richer history of the location.

This is especially important in a building like this one that has multiple addresses -- this node was the only place in the database that held the address 980 Fulton Street, so when it was deleted, we lost the fact that this address exists at this building.

I've already reverted this changeset and restored this node to the database with changeset 66144616. I surveyed and found that it's now a hairdresser, so I've tagged it accordingly.

Please let me know if you have any questions about this or anything else with the map -- I'll try to help best I can.

Thanks, jmapb

Hi Brett, thanks for keeping the map up to date.

Nb, when a restaurant (etc) closes it's better to add the "disused:" prefix to the amenity key, instead of deleting the node altogether. This indicates that the premises in question is still there, with the same address, and can be reused for future tenants, giving us a richer history. It's especially important in buildings with multiple addresses (like this one) to make sure we don't lose the node in that location with the correct address tags.

(I already undeleted the node and set the "disused:" prefix in changeset 66109774.)

Thanks, jmb

Reverted in changeset 66107808. Elinorzag, please feel free to comment or message me to discuss what you're trying to do here. Offhand I don't think a multipolygon is needed here; in fact I'm not sure it's even appropriate to tag either of these buildings with name=Google's NYC HQ as these are buildings with many diverse tenants.

Reverted in changeset 66107569 (hospital name change makes no sense)

Reverted in changeset 66107520 (hospital name change makes no sense)