> The problem with "cuisine=all_you_can_eat" is that "All you can eat" is
> a pricing scheme, not a cuisine. This would prevent tagging with the
> actual cuisine, such as "cuisine=Chinese" or "cuisine=Mediterranean".
>+1
> cuisine=* should be reserved for the actual type of food, not the
> prici
It seems I was too brief in my initial email, so let me clarify.
What I am proposing *is not* cuisine=all_you_can_eat.
I am proposing three new tags: all_you_can_eat,
all_you_can_eat:opening_hours and all_you_can_eat:type.
I am in complete agreement cuisine=all_you can_eat and cuisine=buffet are
>
> Reading up on Wikipedia
> (http://en.wikipedia.org/wiki/All-you-can-eat#All-you-can-eat_.28AYCE.29),
> this tag could also be shortened to ayce=yes/no.
I agree all_you_can_eat=* is a little long, however I would like to keep it
that way. Because if another mapper saw a place with ayce=*, he pr
So, what you're proposing are several tags that could be used in
conjunction with amenity=restaurant, correct?
For example:
all_you_can_eat=yes
all_you_can_eat:type=pizza
Fine so far, but I cannot see a need for a separate
all_you_can_eat:opening_hours subtag when the normal opening_hours tag wou
Actually, all_you_can_eat:type=* describes the *way* the food is served. If
the value is buffet, then people go to the food to get it; if the value is
rodÃzio, then waiters go around the restaurant offering samples of food to
each table; if the value is conveyor_belt, then people sit around a
rotat
Hi there,
According to the results of the first RFC on my original proposal
tourism=holiday_flat, I renamed the tag tourism=apartment.
I therefore open a second (short) RFC phase on this:
https://wiki.openstreetmap.org/wiki/Proposed_features/apartment
Many thanks for your inputs.
greetings, n
Hi John,
I do not understand why this is useful.
The suggest tag is too long, to specific.
I do not understand the need for a special all_you_can_eat:opening_hours
> The problem with "cuisine=all_you_can_eat" is that "All you can eat" is
> a pricing scheme,
If you really think the informatio
I would prefer the plural tourism=apartments. In the picture in the
wiki page, you will not tag every individual apartment, but rather the
entire block of apartment, right?
-- Matthijs
On 15 February 2014 20:30, nounours77 wrote:
> Hi there,
>
> According to the results of the first RFC on my or
>I would prefer the plural tourism=apartments.
I prefer singular because the plural term explicitly states that *more than
one unit is available* to rent while the singular implies only that there
is *at least one *unit for rent on a short term basis. Therefore the plural
designation might often b
+1 for pricing_scheme, +1 against the :opening_hours subtag
What nounours77 proposes is simpler, easier to map, easier to
understand and easier to consume in applications.
I also suggest another tag:
serving_system=buffet/smorgasbord/a_la_carte/table_d_hote (read up
that Wikipedia link I've sent
John,
Thanks for the clarification. I reckon I can now agree with your intent and
the wording of this proposal.
As an aside though, I wonder how many mappers will take the trouble to tag
such restaurants with the full compliment of tags you want to provide.
There is a similar type of restaurant q
I sincerely don't think it's length is a problem. There are longer accepted
tags(like parking:condition:right:time_interval), and to shorten it would
make it harder to remember and recognize (i.e. humans would be the ones
paying the price). Tags like addr:* and ele are okay to abbreviate because
th
12 matches
Mail list logo
