[Tagging] Feature Proposal - RFC - (consulate)-->(office=diplomatic)

Warin 61sundowner at gmail.com
Mon Nov 12 21:00:23 UTC 2018

On 13/11/18 01:07, Allan Mustard wrote:
> Not contrived at all in these days of tight budgets. I see no reason 
> the inverse would not work. I’ll add it.

I think there are too many things in the proposal. Keep it simple. Yes 
the 'extras' might sound nice but they add complexity and each one is a 
point that can lead to someone objecting to that specific thing and 
leading to enough no votes that it fails.

Make the proposal on office=diplomatic only and it should pass.

Then, if you want pursue the other items individually. Personally I 
don't like lumping things together and then separating them at a lower 
level when it was separated before - I refer to the diplomatic=* tag 
that is in use now compared to the proposed diplomatic=embassy(includes 
high commission etc)/consulate (includes consulate general)/and some 
other thing that I don't recall.

> Sent from my iPhone
> On Nov 12, 2018, at 12:31 PM, Colin Smale <colin.smale at xs4all.nl 
> <mailto:colin.smale at xs4all.nl>> wrote:
>> On 2018-11-11 21:51, Graeme Fitzpatrick wrote:
>>> Just for the sake of asking a theoretical question that I know would 
>>> probably never appear in real life :-)
>>> Would / could you also use the multi-letter codes as you show eg 
>>> & a mixture of them, so the British Ambassador to Belgium, who is 
>>> also the delegate / representative to NATO (if there is such a 
>>> thing?), would be
>>> country=GB
>>> target=BE;NATO
>> It's possible I guess to have the inverse of that as well, where the 
>> embassy of e.g. France also houses the ambassador of e.g. Monaco, 
>> both being accredited to the same receiving nation? (contrived example)
>> If a mission "represents" multiple countries, and the services 
>> offered are different, how could that be tagged? Something like the 
>> full Embassy of A also housing consular services for B.
>> Possibly two OSM objects, one for the embassy of A and a separate 
>> node for the services on behalf of B?
>> _______________________________________________
>> Tagging mailing list
>> Tagging at openstreetmap.org <mailto:Tagging at openstreetmap.org>
>> https://lists.openstreetmap.org/listinfo/tagging
> _______________________________________________
> Tagging mailing list
> Tagging at openstreetmap.org
> https://lists.openstreetmap.org/listinfo/tagging

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/tagging/attachments/20181113/b15d0167/attachment.html>

More information about the Tagging mailing list