<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 8/02/2015 11:11 PM, AYTOUN RALPH
wrote:<br>
</div>
<blockquote
cite="mid:CAJHKZiTYk9cG86v4Sbr5y2M+fEHDzN35fq4s_+TmV_a6Db+PiQ@mail.gmail.com"
type="cite">
<div dir="ltr">I have to admit I admire the problem but do not
have an answer.
<div>What I would like to suggest that dropping the "desk" part
and just using "reception" could make it more conducive to the
various applications being discussed.</div>
<div>It could then be added as a subcategory to the
area/building such as
reception=desk...reception=area.......reception=kiosk.. and
would accommodate the problem of more than one type of
reception within a complex such as an hotel </div>
</div>
</blockquote>
I have always come across receptions .. as having a desk. And a
person. Usually with a phone, brochures for information on the
facility they service. <br>
<blockquote
cite="mid:CAJHKZiTYk9cG86v4Sbr5y2M+fEHDzN35fq4s_+TmV_a6Db+PiQ@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>(reception=tourism...reception=hotel). Or at an airport
complex where multiple receptions exist such as hotel, car
hire,etc.</div>
</div>
</blockquote>
<br>
Each of those are in separate places in the airport complex. And are
receptions for different services .. probably indicated by sub tags
.. name= operator=? <br>
<blockquote
cite="mid:CAJHKZiTYk9cG86v4Sbr5y2M+fEHDzN35fq4s_+TmV_a6Db+PiQ@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>Using this would then also not clash with the amenity tag.</div>
</div>
</blockquote>
<br>
Won't they then 'clash' with each other? Whatever sheme is used
there will be clashes, where the clash is by location then simply
separate them by distance - OSM resolution is something like 50mm. <br>
<blockquote
cite="mid:CAJHKZiTYk9cG86v4Sbr5y2M+fEHDzN35fq4s_+TmV_a6Db+PiQ@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>Hope I am not adding more confusion to the problem.</div>
<div>Ralph (RAytoun)</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On 8 February 2015 at 10:33, Andreas
Goss <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:andig88@t-online.de" target="_blank">andig88@t-online.de</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex"><span
class="">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
As<br>
>this tag is always going to be used within another
entity I think we should<br>
>rather look towards something like indoor tagging
or other subtags. In<br>
>addition using amenity for reception desk would
for example prevent you from<br>
>placing it on the node of the amenity and use one
node for both.<br>
</blockquote>
Not to defend the amenity key, but I wonder if there is
a need to tag<br>
the reception if the whole object (including the
reception) deserves<br>
just a single node.<br>
</blockquote>
<br>
</span>
Well, you could have an amenity inside a very large bulding
where you have multiple entrances. Then you could use the
amenity node to indicate that it's actually placed at a
certain spot, because the reception is there. In addition it
makes it clear to which amenity the reception desk belongs,
as a different amenity in the same building could have the
reception desk at the other side of the bulding.<br>
</blockquote>
</div>
</div>
</blockquote>
<br>
Multiple reception desks in the same area would probably be operated
for different businesses .. thus would be identified by the sub tags
of name=, operator= ... ?<br>
<blockquote
cite="mid:CAJHKZiTYk9cG86v4Sbr5y2M+fEHDzN35fq4s_+TmV_a6Db+PiQ@mail.gmail.com"
type="cite">
<div class="gmail_extra">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
__________<br>
<a moz-do-not-send="true"
href="http://openstreetmap.org/user/AndiG88"
target="_blank">openstreetmap.org/user/AndiG88</a><br>
<a moz-do-not-send="true"
href="http://wiki.openstreetmap.org/wiki/User:AndiG88"
target="_blank">wiki.openstreetmap.org/wiki/User:AndiG88</a>
<div class="HOEnZb">
<div class="h5"><br>
<br>
<br>
_______________________________________________<br>
Tagging mailing list<br>
<a moz-do-not-send="true"
href="mailto:Tagging@openstreetmap.org"
target="_blank">Tagging@openstreetmap.org</a><br>
<a moz-do-not-send="true"
href="https://lists.openstreetmap.org/listinfo/tagging"
target="_blank">https://lists.openstreetmap.org/listinfo/tagging</a><br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Tagging mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Tagging@openstreetmap.org">Tagging@openstreetmap.org</a>
<a class="moz-txt-link-freetext" href="https://lists.openstreetmap.org/listinfo/tagging">https://lists.openstreetmap.org/listinfo/tagging</a>
</pre>
</blockquote>
<br>
</body>
</html>