From OpenStreetMap Wiki
Jump to navigation Jump to search


What about having the tag: buffet = yes ? in case that the type of restaurant has a buffet option? --Capiscuas (talk) 20:44, 23 October 2013 (UTC)


Might be interesting to know in advance if they have restrooms or not.

See the amenity=toilets wiki page which suggests to use a simple toilets=* key which is already quite common. --Scai (talk) 16:42, 20 October 2013 (UTC)


How about a price tag? something similar to what I suggested for the Hotel. This ould be handy for travellers on a budget. I would suggest three categories (price=budget/middle/high) which should be used in the context of the country/region.


I would like to see a delivery=yes/no key added to help distinguish between those restaurants that will deliver and those that won't. --Elsaturnino 03:47, 27 June 2008 (UTC)

I second. I tagged a few places delivery=yes when they have a delivery option. In Amsterdam where I live and map, there is quite a few restaurants that do delivery exclusvely. there might also be a counter where you can order for takeout. They are definitely not always fast food operations though, so how to tag these? amenity=restaurant is misleading, but amenity=fast_food as well.. --Martijn van Exel 09:37, 18 August 2010 (BST)

Something like a phone_number key? In future it could be implemented in pocket navigators in order to e.g. reserve a table--SteveVG 17:56, 23 April 2009 (UTC)

phone=[number] will do I believe --Martijn van Exel 09:37, 18 August 2010 (BST)
Having a phone is nothing that leads to delivering food... use delivery=yes. Lulu-Ann

Please add a type= tag, like explained on . Values could be: "fast_casual", "family", "casual_dining", "fine_dining".--mixmaxtw 15:02, 17 January 2010 (UTC)

Don't reuse "type", use "restaurant=*" instead. Another value is "canteen". --Lulu-Ann 13:37, 16 November 2010 (UTC)

Take away

I would like to add a tag to normal restaurants which also have take away service. According to Taginfo usage is: takeout=* used 6 times, take_out=* 3, take_away=* 63, takeaway=* 304. So I propose to go along with the most used one: takeaway=yes/no (even if I think the right spelling should be take_away). --Oligo 17:51, 7 November 2010 (UTC)

Sounds fine to me --Pobice 19:42, 28 November 2010 (UTC)

Extending this tag to areas

I think this tag should apply to areas too, so when buildings are drawn from aerial images the building can be tagged instead of first tagging the building and then adding a node to tag the restaurant. JOSM already handles this, but no renderer supports it.--R2D2 01:11, 14 September 2008 (UTC)

Apparently Osmarender and Mapnik are rendering this tag on areas correctly, so no (more) need to add an extra node to the building explicitly for this. --Quini 08:28, 15 October 2009 (UTC)

bar and restaurant

what should i do when a place is a sushi-restaurant and a bar at the same time?--Shmias 13:06, 3 June 2009 (UTC)


It would be good to know if a restaurant serves alcohol or if you are allowed to bring your own. Possibly alcohol=no/yes/byo/wine/beer/spirits/full. Brianegge (talk) 22:25, 4 October 2014 (UTC)

See if the key drink=* does what you want. --Jgpacker (talk) 22:52, 4 October 2014 (UTC)

drive-in vs. drive-through?

I have heard about drive-in cinemas, but never a drive-in restaurant. I have seen several drive-through restaurants and fast-food (specially fast-food). Should drive-in be changed to drive-through=*? --Skippern 19:54, 16 September 2010 (BST)

Unfortunately many fast food places call themselves having a "drive-in", when all they have is a window where you can order and get the food to go. Most have at least some parking spaces for customers to consume their meal in, though. Apparently, per the linked articles, some places have drive-in restaurants ("served by staff who walk out to take orders"), yet what we have is a mixture of both: cars form a line to order the food, yet they are encouraged to park there, too. Mappers will find it nitpicking if they don't find their local "drive-in" under "drive-in". Is there any chance of confusion? Users are, IMO, likely to think along the lines of "I want food without leaving my car" - and one can "drive through" a drive-in, that is, leave as soon as they get their food. Alv 18:43, 5 October 2010 (BST)
Drive-in restaurants do exist, not as common as they used to be. The food is ordered from a parked car, brought to the car by a  carhop, and generally consumed in the parked car. Sonic and A&W are two large chains of drive-in fast food in the USA. Jmapb (talk) 17:41, 6 May 2018 (UTC)

Page 'Key:amenity:restaurant' created March 2010

This page was created and it contains elements of this page, Tag:amenity=restaurant, and some aspects of Tag:amenity=fuel#Additional services:. See page @ Key:amenity:restaurant. Suggestions on what to do with this page (and the tag description) would be appreciated. --Ceyockey 16:49, 24 October 2010 (BST)

add plates?

like for hotel where we add rooms= we maybe can add the maximum place number. We can use plates=X? -Yod4z 16:11, 9 October 2012 (BST)

Pizza places

There are a lot of pizza places where

 (a) you can order a pizza from home and they will deliver it
 (b) you can order a pizza from home and pick it up yourself
 (c) you can walk in off the street, order a pizza, they will make it, then you can take it away

These are not restaurants as because you cannot eat there since there are no tables or plates. Also, they would not be considered fast food since they only make whole pizzas to order, which takes about twenty minutes. If anybody has any ideas about how these businesses should be tagged, it would be appreciated. —Preceding unsigned comment added by TristanA (talkcontribs) 16:13, 22 May 2013‎

State of keys

Taking a look at amenity=* where the value search was "pizza" turned up a set of uses:

Term Count
pizza 3
Pizza␣and␣Tacos 1
Pizza␣Delivery 1
Pizza/Pasta 1
Pizza␣Malibu 1
pizza␣delivery 1
pizza␣shop 1

Taking a look at shop=* where the value search was "pizza" turned up two uses:

Term Count
pizza 5
pizza_service 1

There is a shop=delivery (5 instances) which shows no 'combinations' values.

Personally, I'm thinking that commercial entities should be covered by shop=*, but this is not consensus. There is a discussion item above about "takeaway" (a term I take to be the British equivalent of "takeout" ... or "takehomasack" if you remember that) and another (from 2010) about "delivery". It would make sense to include an additional qualifier of deliver=* (not "delivery" in order to avoid confusion with access=delivery) and dinein=* and pickup=* ... with the suggestions that the only values allowable for these keys would be Yes, No, Y and N. If the delivery has an hours of operation associated with it, then that should be covered by a compound key rather than expansion of the value set.

Hope this helps. --Ceyockey (talk) 03:01, 23 May 2013 (UTC)

Thanks for this. I like the idea of using shop=*. Theoretically this isn't limited to pizza though. I think I'll tentatively use shop=food as a store that sells prepared or cooked food as opposed to a supermarket. Any objections?
Quite OK. You could use cuisine=pizza if the shop is primarily a pizza shop; this key-value pair happens to be the 2nd most popular, the 1st and 3rd being "regional" and "burger", respectively. --Ceyockey (talk) 02:23, 26 May 2013 (UTC)

Kitchen open until

Sometimes the establishment will be open but does not take orders for food after a certain time. The opening hours of the kitchen differs from that of the place as such. Could that be solved like attempted in this example  : Mo-Fr 08:00?-?2?1:00, Sa-Su 09:00-2?1:00,Mo-Su 21:00-23:00 Open "Kitchen closed"

There's a tag for this purpose: opening_hours:kitchen=*. (Although the namespace seems backwards to me; kitchen:opening_hours=* or even just kitchen_hours=* would make more sense.) Jmapb (talk) 15:01, 22 August 2018 (UTC)


I am suggesting to add a tag allowing to have the information: can I bring my own lunchbox to fill it? Important subject when trying to avoid using plastic lunchbox, and more and more used. What about the tag "LUNCHBOX = yes"?

Adding undefined tags service_times=* / service_times:=*

It is not clear how service_times=* or service_times:=* would be used with restaurants, or if they are even being used for this purpose. How would this be different than the common, "de facto" key opening_hours=*?

Feature pages, like this one, are supposed to give the most commonly used tags. If anyone wishes to propose a new tagging method, there is a Proposal_process available, or it is possible to start mapping with the new tag and then document it at it's own wiki page. But it is not appropriate to add links about new tags to existing pages. --Jeisenbe (talk) 13:58, 13 March 2020 (UTC)

How to Tag in Combination with a Building

Do I tag a building=commercial when it’s a restaurant? IanVG (talk) 18:18, 5 May 2021 (UTC)

building=commercial or building=retail is fitting for buildings constructed to house restaurants (note that restaurant may be also in building constructed for other purposes and clearly retaining it, there are for example restaurants in building=industrial or building=church) Mateusz Konieczny (talk) 13:34, 19 May 2021 (UTC)
Can add building:use=retail to the latter. ---- Kovposch (talk) 06:32, 20 May 2021 (UTC)

surcharge days

I'm finding it more common that some places will have Sunday and/or Public Holiday surcharge. Perhaps we could use surcharge=10% @ (Su,PH) indicates 10% surcharge applies on Sundays and Public Holidays. --Aharvey (talk) 02:47, 7 March 2023 (UTC)

I would prefer *:conditional=110% @ (Su,PH) to allow discounts by <100%. For surcharge=*, it could be charge:total=* or charge:final=* to indicate the bill is to be multiplied by this. --- Kovposch (talk) 04:38, 7 March 2023 (UTC)
I like that, great suggestion. I'll use charge:conditional=110% @ (Su,PH). I can't see any documentation on the wiki for charge:total=* or charge:final=* so I'm unsure what the difference is and how they differ from charge=*. --Aharvey (talk)
Only hypothetical suggestions. The issue would be fitting in with others. Eg maxcharge=* and charge:max=* have been used for some price cut-off. To go with the 1st format, total_charge=* (full percentage) or charge_modifier=* (percentage change) may be suggested alongside, which avoids affecting other charge:*=* for vehicles modes. --- Kovposch (talk) 03:34, 8 March 2023 (UTC)
Taking this further we could use similar to tag places that provide a discount for cash and/or a surcharge for credit cards. 10% discount when paying with cash: charge:conditional=90% @ (payment:cash). 2% surcharge when paying with credit card: charge:conditional=102% @ (payment:cards).
That would need some coordination with payment:*=* for where to put it. Talk:Key:payment:*#*=surcharge (as you, and others, have raised in the past)
Besides, it could be argued to turn this into charge:*=* method suffix. charge:cash=* and charge:credit_card=* would be simpler.
--- Kovposch (talk) 03:28, 8 March 2023 (UTC)
Yes charge:cash=* and charge:credit_card=* would be simpler than something like charge:conditional=X% @ (payment:cards). is one example where I've tagged charge:conditional=10% @ (Su); 15% @ (PH) to imply a 10% surcharge on Sundays and 15% surcharge on public holidays, then charge:credit_cards=1.5% to imply a 1.5% surcharge when paying via credit cards. --Aharvey (talk) 02:56, 30 March 2023 (UTC)

Perhaps also we should just do 2% for surcharge and -10% for discount, that would be simpler and less confusing than 90% / 102%. --Aharvey (talk) 05:58, 7 March 2023 (UTC)

Restaurants and cafes won't have a single charge=* amount so tagging the % implies it's a surcharge, but for other features that do have a single charge=*, then charge:payment_method=X% would imply this payment method is % times the charge=* value. So mappers have a choice tagging specific payment methods a % or a $ value. --Aharvey (talk) 03:00, 30 March 2023 (UTC)
That depends on the syntax and semantics. I mentioned the full percentage under those charge:*=* suffixes. Percentage change might use eg charge:modifier=* (stealing from modifier=* ). --- Kovposch (talk) 03:29, 8 March 2023 (UTC)