From OpenStreetMap Wiki
Jump to: navigation, search

Please add your opinion and experience here


This is just an idea: if meals can not be eaten on premises, but they are only offered for takeaway/delivery, it is probably enough to tag the times with delivery=*, and there would be no benefit of adding an extra lunch=*. --Bkil (talk) 10:11, 20 November 2016 (UTC)
Food to take away? You can use takeaway=yes --RoGer6 (talk) 23:01, 19 November 2016 (UTC)
Yes, it is commonly possible to take away a lunch menu offering, we can tag it with takeaway=yes. (Actually, 99.5% of venues offer takeaway around here, so I never map it) What I meant above is that I know a place that could be mapped as takeaway=only, delivery=Mo-Fr 11:00-13:00. Because you can not sit down to eat, it is not a dining POI in the regular sense that you would like to frequent, so adding lunch=* may or may not be feasible. Although, if they are open all day long and offer a special lunch offer, it could make sense. I'm undecided as of now. -Bkil (talk) 10:11, 20 November 2016 (UTC)
My new proposal is to introduce lunch:menu:takeaway=yes/no/only and lunch:menu:delivery=yes/no/only. I've now found a restaurant which only offers a lunch menu for takeaway (and with lunch:menu:subscription=only). It is also possible to find delivery-only variants as well. Both takeaway-only and delivery-only can be set at the same time. This would mean that you could either take away the meal or get it delivered, but you can not eat it in place. Bkil (talk) 18:33, 25 November 2016 (UTC)


Would it make sense to apply lunch=only to an amenity=pub which neither offers a' la carte, nor does it operate a kitchen out of lunch hours? Some apply food=no to pubs lacking a kitchen, while others try to signal this simply by ommitting cuisine=* or giving cuisine=no, however a pub that offers lunch could plausibly have cuisine=* specified, hence some other signaling should be used.
I now see that opening_hours:kitchen=* is much better suited for this task. For such a pub, it needs to be set to the same time range as given for lunch hours. Bkil (talk) 18:28, 25 November 2016 (UTC)


RoGer6, what does 'abo' stand for? How is it different compared to `lunch:menu:subscription=yes/no/only` Bkil (talk) 21:15, 23 October 2018 (UTC)

Okay, Sorry.  That needs to be adjusted. I take care of it. RoGer6 (talk) 19:27, 25 October 2018 (UTC)

No problem. Feel free to propose additions to this draft. I was just curious. It would be great if we could envision what kind of data consumers could exist in the future and what properties they could find use in. Bkil (talk) 19:42, 27 October 2018 (UTC)

For example, it occurs to me sometimes that I need to describe a few attributes in prose, so more structured tags are always welcome. Do you think it would be useful if we could specify whether a full week needs to be subscribed in advance or if it is possible to subscribe for a subset of days? Bkil (talk) 19:42, 27 October 2018 (UTC)

Many venues give a discount if you provide your own food container as an eco-minded measure, similar to owncup=*. Should we tag this? Bkil (talk) 19:42, 27 October 2018 (UTC)

Additionally, I regularly encounter that they stress that subscribing for the next week is only possible up until Friday (or Thursday). At other places, they declare that you need to subscribe for lunch before 11:00 the previous day, for example, if you'd like to eat on Wednesday, you need to phone in before 11:00 on Tuesday. At present I don't have a good suggestion for this one other than typing it in prose in lunch:menu:subscription:description=*. Bkil (talk) 19:42, 27 October 2018 (UTC)

Sometimes they specifically state that subscribing is possible only via e-mail or via phone. This may be conveyed by something like lunch:menu:subscription:email=* and lunch:menu:subscription:phone=*. Bkil (talk) 19:42, 27 October 2018 (UTC)