<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 24/10/18 20:50, Martin Koppenhoefer
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CABPTjTBWFQ3j+Go=env3L1d2hksrw7+rs4_OK_=qwuORAahb6w@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=utf-8">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr"><br>
<br>
<div class="gmail_quote">
<div dir="ltr">Am Mi., 24. Okt. 2018 um 03:48 Uhr schrieb
Allan Mustard <<a href="mailto:allan@mustard.net"
moz-do-not-send="true">allan@mustard.net</a>>:<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 bgcolor="#FFFFFF">
<p>One of the commenters has suggested an additional
tag indicating what services a consulate or embassy
provides, and that is one option. Not all
consulates or consular sections of embassies offer
all visa types, for example. The existent service=*
tag could possibly be used. For example, one could
add to either a consulate or an embassy the tag
service=[citizen services; notarials; apostiles;
immigrant visas; non-immigrant visas]. Thoughts?<br>
</p>
</div>
</blockquote>
<div><br>
</div>
<div>the service tag is already used for several different
purposes (e.g. subtype of service road, subtype of
service rail), which creates some inconvenience for data
consumers (it is not necessarily a big problem, but some
people have denounced this in the past) and as the
services offered by a consulate will likely be more than
one, I would suggest using a scheme like we use for
payment or available fuels, i.e. a property list of
yes/no (no is usually omitted), see here for reference:
<a
href="https://wiki.openstreetmap.org/wiki/Key:payment"
moz-do-not-send="true">https://wiki.openstreetmap.org/wiki/Key:payment</a></div>
<div><br>
</div>
<div>For consulates, using the examples you gave, this
would translate to:<br>
</div>
<div>service:notarials=yes</div>
<div>service:apostiles=yes</div>
<div>service:immigrant_visas=yes</div>
<div>
<div>service:non-immigrant_visas=yes</div>
</div>
<div>etc.</div>
<div><br>
</div>
<div>Or (if there are only two types of visas), you could
also combine the latter two to <br>
</div>
<div>service:visas=immigrant / non-immigrant / both / yes
(if you don't know which types) / no (no visas at all)</div>
<div><br>
</div>
<div>These headstands are applied to avoid multiple values
for the same key, and are required because keys must be
unique in OSM.<br>
</div>
<div><br>
</div>
<div>You can add these suggested properties to your
proposal, but you could also put them in another
proposal (if you believe there is support for
amenity=consulate but the tags about offered services
could be disputed).<br>
</div>
</div>
</div>
</div>
</div>
</blockquote>
<br>
As these services are also available at some other 'embassies' they
should get there own proposal so they can be used in things like
'consulate_general', 'mission' etc.<br>
<br>
For visas I'd go simple .. service:via=yes/no/* There will be
multiple types for different countries .. sorting through them will
be too much for most, yes and no will probably be the most popular
and useful. <br>
<br>
<blockquote type="cite"
cite="mid:CABPTjTBWFQ3j+Go=env3L1d2hksrw7+rs4_OK_=qwuORAahb6w@mail.gmail.com">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div class="gmail_quote">
<div><br>
</div>
<div>___<br>
</div>
<div>As a slightly offtopic hint, by looking at the
proposal page discussion, I got the impression you are
using the digest mode for emails, which seems convenient
at first (because you don't get your email account
crammed with a plethora of mails), but the convenience
is traded off for making it much harder to reply to the
mails (you must adjust the subject every time and cannot
reply to individual mails). Just in case you would want
to change this, it can be set here: <a
href="https://lists.openstreetmap.org/listinfo/tagging"
moz-do-not-send="true">https://lists.openstreetmap.org/listinfo/tagging</a>
"Would you like to receive list mail batched in a daily
digest?".</div>
</div>
</div>
</div>
</div>
</blockquote>
<br>
It can be handy to set up your mail client to separate out the
various things into folders - you can have one for the tagging
group, one for general osm stuff etc.<br>
<br>
----------------<br>
Still think best to have all these embassies/consulates/etc under
one tag - the renders can then use the same symbol for all of them
.. like they did for shops until they got inventive. The same will
happen here, eventually consulates will be separated from embassies.<br>
</body>
</html>