In the case of business branches that people generally distinguish by the name of a place/area or road that is located nearby (for instance, "KFC Downtown" (a specific area), "Starbucks Riverside" (an avenue), "DHL Waterfall Mall" (a place it's in) etc.), which would be the best practice to tag them in a way they can be found by search terms like "starbucks riverside" or "kfc downtown", etc? Please note the name of the place/road/area isn't necessarily part of the "official" name of that specific branch, just how people will call it.

  • One option, the most straightforward one, would simply be using name=KFC Downtown for the element, but the wiki recommends not to put additional information in the name tag.
  • Another option would be using alt_name=KFC Downtown; name=KFC.
  • Tagging name=KFC; branch=Downtown doesn't seem return any hit on both the OSM site and Nominatim for "kfc downtown".

What could be the ideal tag combination to get an accurate lookup?

asked 01 Nov '17, 17:03

Absay's gravatar image

accept rate: 0%

I would use loc_name (local name), since that seems to best describe what you've described. I don't know whether Nominatim uses that tag or not, but really that's beside the point.

permanent link

answered 01 Nov '17, 17:37

alester's gravatar image

accept rate: 30%

Well, a tag being picked up by the search engines is what I'm looking for, so the OMS and Nominatim searches are relevant here, and loc_name seems to be the way to go in this case. Thanks!

(01 Nov '17, 20:07) Absay

The first priority should always be to tag the object as accurately as possible. Anything beyond that, like how it looks in a renderer, how it's found in a search engine, or how a routing engine uses it, are all secondary. If an object is tagged accurately but doesn't work as intended in a data consumer, it's the data consumer that needs to change, not the data.

(01 Nov '17, 20:28) alester

While finding an object in a Nominatim search may indeed be secondary, I think it is still important for users (and mappers) to be able to find it using variations on its name. I have been faced with the same problem many times and honestly don't know the best tags to use either.

(01 Nov '17, 22:45) AlaskaDave

The branch tag was intended to adress this problem, but is a relatively new invention, which maybe hasn't been advertised as much as needed

(01 Nov '17, 23:56) Hjart

I did not know of the "branch" tag, and I like it, but I cannot determine if it is searchable through Nominatim.

(02 Nov '17, 11:46) AlaskaDave

I found the list of names imported and indexed by Nominatim. It's on the Development page:

Branch is not mentioned but old_name, loc_name, alt_name, among others, and their language variations like name:en, are processed

(02 Nov '17, 11:55) AlaskaDave

If branch=* is the correct tag to use (and it's used over 50K times as of today, so it seems likely), then maybe an issue should be entered in the Nominatim github to include branch values in the indexing:

(02 Nov '17, 15:09) neuhausr

God, that page hasn't been updated in more than 2.5 years. One could think new tags have been added but at least from first hand I know "branch" hasn't yet. Maybe raising an issue on GitHub would be helpful? :)

Though to be fair, I don't necessarily care about Nominatim per se, which seems to be what OSM mappers use to "debug" their work. I guess I'm more interested in the most common search egines used by sites an apps that allow people to scout areas. The OSM default page would be one of them. But as far as I can see, this is platform-dependent and subject to separate development, where tags can be imported or left out depending on any given engine.

So as @alester said, accurate information is more important, that's the bottom line, so based on what I'm getting from this answers the combination name=KFC + loc_name=KFC Downtown + branch=Downtown + brand=KFC + operator=KFC <or whatever> seems to be good enough, though certainly a bit repetitive in regards to loc_name and branch. But hopefully this should encompass the majority of common search engines and return valuable hits to the end user.

(02 Nov '17, 15:17) Absay

loc_name is for what local people call the place. It seems that loc_name=KFC Downtown is the exact opposite of that. Perhaps official_name is better

(03 Nov '17, 05:54) escada
showing 5 of 9 show 4 more comments

I would map it as name=KFC Downtown + brand=KFC This is how it is explained on the brand wiki page.

permanent link

answered 02 Nov '17, 07:18

escada's gravatar image

accept rate: 21%

edited 02 Nov '17, 07:22

"but the wiki recommends not to put additional information in the name tag", which is something that makes lots of sense, so adding the place to the name is discarded for me.

(02 Nov '17, 14:40) Absay

If the name on the receipt says "KFC Downtown" which incorrect additional information do you add then ? For me this means that I should e.g. not add "Restaurant' in e.g. "KFC Downtown Restaurant" even though There might be a "Restaurant" sign.

(02 Nov '17, 14:47) escada

I would base what I put in the name tag on signs outside the location.

If it says "KFC Downtown" then put that in the name; if the signs just say "KFC" put that in the name. The name on the receipt will be a short form (because of the allowable character width) of the internal (official name), which will be something like "KFC Downtown Anyplace".

If you are aware that people in the local area use "KFC Downtown" but this is not signed then loc_name is appropriate.

It is always a good idea to add brand=KFC too: this is more likely to be mapped consistently than name.

As other's have said don't map for a specific application such as Nominatim.

permanent link

answered 03 Nov '17, 11:10

SK53's gravatar image

SK53 ♦
accept rate: 20%

Your answer
toggle preview

Follow this question

By Email:

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



Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text]( "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:


question asked: 01 Nov '17, 17:03

question was seen: 658 times

last updated: 03 Nov '17, 11:10

powered by OSQA