<div><div dir="auto">For campgrounds, campsites and tourism=caravan_site the most commonly used tag is camp_site=reception, over 1000 uses but it was only part of an old proposal.</div></div><div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, Apr 13, 2019 at 8:01 AM Warin <<a href="mailto:61sundowner@gmail.com">61sundowner@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
<div class="m_-5419133575584230657moz-cite-prefix">There are 457 uses of booking=* in the
data base. I have used it on camping sites that require seasonal
booking. <br>
<a class="m_-5419133575584230657moz-txt-link-freetext" href="https://wiki.openstreetmap.org/wiki/Key%3Abooking" target="_blank">https://wiki.openstreetmap.org/wiki/Key%3Abooking</a><br>
<br>
Humm reception and checkin as the same? <br>
<br>
I did propose amenity=reception .. failed as some did not want it
as amenity ... I use it. <br>
<br>
Should I use it for check in? Possibly. <br>
So amenity=reception for airport check ins.. ??? Any other ideas?
<br></div></div><div text="#000000" bgcolor="#FFFFFF"><div class="m_-5419133575584230657moz-cite-prefix">
<br>
<br>
On 13/04/19 08:40, Graeme Fitzpatrick wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div dir="ltr"><br clear="all">
<div>
<div dir="ltr" class="m_-5419133575584230657gmail_signature" data-smartmail="gmail_signature">
<div dir="ltr">
<div dir="ltr"><br>
</div>
</div>
</div>
</div>
</div>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Fri, 12 Apr 2019 at
21:49, Paul Allen <<a href="mailto:pla16021@gmail.com" target="_blank">pla16021@gmail.com</a>> wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="ltr">
<div dir="ltr">On Fri, 12 Apr 2019 at 10:13, bkil <<a href="http://bkil.hu" target="_blank">bkil.hu</a>+<a href="mailto:Aq@gmail.com" target="_blank">Aq@gmail.com</a>> wrote:<br>
</div>
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
Also, I was just considering whether we could unite
related features<br>
like ticket booths/ticket
check/vending/reception/information<br>
desk/check-in for various places like camp_site,
hotel, motel,<br>
guest_house, school, office, mall, community_centre,
sports_centre,<br>
events_venue, cinema, theatre, music_venue, nightclub,
public<br>
transport, etc.<br>
</blockquote>
</div>
</div>
</blockquote>
<div><br>
</div>
<div>You could probably get away with classifying almost all
of those as check_in, or maybe reception? For most of those
venues, though,"reception" would be immediately inside the
front door, so there wouldn't really be a need to show where
it is.</div>
<div><br>
</div>
<div>An exception to that would be airports, where your ticket
desk/s can be located almost anywhere, & you'd then also
have to specify that this is the check-in for Airline A,
that one is Airline B & so on</div>
<div><br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="ltr">
<div class="gmail_quote">
<div>Such merging may cause problems for (some)
editors. If you can guarantee that all<br>
</div>
<div>camp sites, hotels, motels, etc. can potentially
have any of ticket booths, vending, check in,</div>
<div>etc. then that's fine. E.g., if A could have any
of X, Y or Z; B could have any of X, Y or Z;</div>
<div>C can have any of X, Y or Z; etc. that isn't a
problem. The editor's code just handles it as</div>
<div>a list of X, Y and Z can apply to A, B and C<br>
</div>
<div><br>
</div>
<div>What would be a problem is if A can only have X or
Y; B can only have Y or Z; and C can only have</div>
<div> X or Z.</div>
</div>
</div>
</blockquote>
<div><br>
</div>
<div>Yes, we see this with some of the camping grounds we
regularly go to. Some have offices / kiosks, where you check
in on arrival; some have no check in requirements at all -
you just arrive, pick a (unmarked) spot & set up; while
others have to be booked online before you go.</div>
<div><br>
</div>
<div>These could probably all be covered by check_in=yes / no
/ online_only, possibly together with a bookings=(url)?</div>
<div><br>
</div>
<div>Thanks
<div><br>
</div>
<div>Graeme</div>
</div>
</div>
</div>
<br>
<fieldset class="m_-5419133575584230657mimeAttachmentHeader"></fieldset>
<br>
<pre>_______________________________________________
Tagging mailing list
<a class="m_-5419133575584230657moz-txt-link-abbreviated" href="mailto:Tagging@openstreetmap.org" target="_blank">Tagging@openstreetmap.org</a>
<a class="m_-5419133575584230657moz-txt-link-freetext" href="https://lists.openstreetmap.org/listinfo/tagging" target="_blank">https://lists.openstreetmap.org/listinfo/tagging</a>
</pre>
</blockquote>
<p><br>
</p>
</div>
_______________________________________________<br>
Tagging mailing list<br>
<a href="mailto:Tagging@openstreetmap.org" target="_blank">Tagging@openstreetmap.org</a><br>
<a href="https://lists.openstreetmap.org/listinfo/tagging" rel="noreferrer" target="_blank">https://lists.openstreetmap.org/listinfo/tagging</a><br>
</blockquote></div></div>