How should I tag building that has more than one amenity? For example: in my neighbourhood there is one building used for dentist, veterinarian and pharmacy. I'm sure that all those amenities shouldn't be mixed up in tags for one building because tags like "phone", "opening_hours", or "website" (and many others) would be inaccurate.

So.. my idea was to tag building only with address and "building=yes", and to put separate nodes of these amenities on it with specified data about them.

But there is another question. What to do with addresses? Should I tag all those separate amenities with addresses or the one made for building will suffice? Or my whole idea is wrong? Please help.

asked 23 Sep '13, 00:43

KoyotGamma's gravatar image

KoyotGamma
193356
accept rate: 0%

While not directly applicable to this question specifically, if a building has more than one entrance and each entrance is associated with a different amenity, then I would tag each entrance with the information for the amenity and just leave the building as building:yes with the address information (assuming the address for all parts of the building is the same).

(25 Jul '16, 22:07) zellfaze

I'll split this answer into two parts: How to map the amenities, and how to map the addresses.

Mapping multiple amenities in a building

The easiest and most common solution is to create one node per amenity. As you noticed yourself, using only one element for all of them would cause conflicts between their attributes. Therefore, using one node, way, or relation for each "thing" – no more, no less – is a common principle in OSM tagging known as one feature, one OSM element.

If you want to add more detail, though, you might be interested in concepts from indoor mapping. With a tagging style such as Simple Indoor Tagging (see the overview for alternatives), this can be as simple as adding level tags to each amenity. On the other end of the spectrum, you might see amenities mapped as areas which represent their share of the floor, together with hallways, staircases and other features.

Mapping multiple amenities with the same address

Adding the shared address to the building outline is a good start. Not only does it avoid duplication, it's also entirely possible for programs to find out which amenities are inside the building outline, and conclude that they share the building's address. In practice, however, not many programs actually support that feature, so mappers often decide to tag the address on the amenities as well as the building outline. If there is already a consensus among mappers in your area, it's best to stick to that.

Every now and then, other approaches have been proposed, usually using relations. Those would be able to express very complex address situations. However, they tend to be strongly rejected in votes (example), and none of them has been mature enough to gain significant support yet.

permanent link

answered 02 Aug '16, 18:46

Tordanik's gravatar image

Tordanik
10.3k1294127
accept rate: 34%

Hi, A good question which I hoped someone else might answer before me as I have a similar problem with this building which is a health centre accommodating doctors, dentist, pharmacy & physiotherapist all having different opening hours and contact details http://www.openstreetmap.org/browse/way/223249817

The multiple values in the amenity tag don't really work and I think I will replace them with the single value 'clinic' http://wiki.openstreetmap.org/wiki/Tag:amenity%3Dclinic This would apply to the building which would continue to be tagged with the name Hillcrest Healthcare. I'd also delete the tag 'dispensing=yes' which only applies to the pharmacy part of the clinic.

I'd then put on separate nodes for each of the amenities with specified data about them as you suggest. I'm not sure what to do about addresses – just one for the building or individual ones for each amenity? Perhaps someone can advise.

permanent link

answered 23 Sep '13, 08:03

NZGraham's gravatar image

NZGraham
1.8k122648
accept rate: 17%

4

Following the principle "one feature, one OSM element", I tag the address only once on the building polyogon or on a node attached to the facade. But some people don't think that address is a feature and repeats the same information on all POI's. It's a point of view question : if you are interrested by the dentist, you like to see immediatly his adress attached to its node. If you are interrested by addresses, you don't like unnecessary duplicates.

(23 Sep '13, 14:31) Pieren
-1

In my city ( http://www.openstreetmap.org/#map=17/50.06186/19.93749 ) I see two methods: ignore less important places (Sukiennice are filled with multiple shops, none is marked) or mark amenity as point objects (some buildings have 5 or more amenities).

permanent link

answered 23 Sep '13, 09:59

Bulwersator's gravatar image

Bulwersator
408111624
accept rate: 14%

4

A feature should not get ignored only because there is a more important one next to it.

(23 Sep '13, 14:58) scai ♦
Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:

×76
×53
×41

question asked: 23 Sep '13, 00:43

question was seen: 4,182 times

last updated: 02 Aug '16, 18:46

powered by OSQA