See the wiki page on name conventions: osm.wiki/Names The name= field should be for actual proper names, not descriptions.

Please see the guidelines here for naming objects: osm.wiki/Names Names in OSM should refer to the actual proper name to which the items are commonly referred, and should not include any plain descriptions or internal reference units.

Also, you can use level=* to indicate what story of the building something is on: osm.wiki/Key:level

In OSM, accuracy to the real world should always be prioritized over readability of the map. Mapping style over accuracy is called "mapping for the renderer," and there's more explanation here: osm.wiki/Tagging_for_the_renderer . OSM is a spatial database that can be used by lots of different software, so making it look good in one might break another. So as a standard, we make the map as accurate as possible to reality, and let the software figure out how to do things like place labels.

It's still useful to know, for example, whether unit E is towards the north end of the building or the south. There's no such thing as too much detail on OSM! These PoI were added through an import project we've been running, if you like you can try to contribute there as well! https://maproulette.org/browse/projects/42122

Yeah, weird that KeepRight says that. It's fine to remove the redundant tags it's just confusing to call it deprecated.

Where is the key described as deprecated? The wiki has it as "de facto."

Thanks.

As I understand it, the purpose of LAFCO is to resolve contradictions between city boundaries within the county. If Campbell and San Jose both agree where the borders are then that's fine, otherwise defer to LAFCO.

The city boundaries were verified by the Santa Clara LAFCO, the official authority. Please don't change them before checking with SCLAFCO.

Thanks for your contribution! When a business has closed, rather than deleting the node entirely, only remove information that's no longer relevant, and keep the address that still exists. The editor you're using has a "downgrade" option to do this easily. Second, the "name" field should only be used for places that actually have a proper name, not for labels or descriptions. See osm.wiki/Names#Names_are_not_for_descriptions

Please save your changes in one area before moving on to another area, so that the changeset size is small.
Traduction automatique : veuillez enregistrer vos modifications dans une zone avant de passer à une autre zone, afin que la taille de l'ensemble de modifications soit petite.

Please read the documentation on the format of address tags: osm.wiki/Key:addr:* The street name must exactly match the name of the street nearby (so, no abbreviations).

Please use the changeset message to describe what you changed and why, for example "Added building outlines in Cloverdale from aerial imagery." There are more examples here: osm.wiki/Good_changeset_comments Also, please save your changes in one area before moving to another, to keep the changeset box small and easy to review.

I've restored the two trails that this changeset deleted, and added access=no to indicate they're inaccessible. Only objects that have no evidence of existing should be deleted from OpenStreetMap.

Please use the changeset message to describe what you changed and why. For example, "Added an urgent care clinic." See here for more examples: osm.wiki/Good_changeset_comments . Also, when a business location has closed, please only delete the business information from the node without deleting the node, so that the address information is still accurate.

The two bottom parts really lost a lot of roundness…

Thanks!

The original point had a unit number: 5968 Silver Creek Valley Road Unit 20. The location of that unit number within the building is still useful information even if the business at that address has closed.

If a place has closed but the address still exists it's better to keep the object and just remove any business tags, so that the address doesn't have to be re-added