<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><br><br><div id="AppleMailSignature" dir="ltr">sent from a phone</div><div dir="ltr"><br>On 27. Oct 2018, at 06:50, Allan Mustard <<a href="mailto:allan@mustard.net">allan@mustard.net</a>> wrote:<br><br></div><blockquote type="cite"><div dir="ltr"><font face="Helvetica, Arial, sans-serif">So here is where I sense
we are 24 hours later, on Day 6:</font><br>
<font face="Helvetica, Arial, sans-serif">a) consulates are not
embassies;<br>
</font><font face="Helvetica, Arial, sans-serif"><font face="Helvetica, Arial, sans-serif">b) neither embassies nor
consulates are amenities;<br>
</font>c) embassies and consulates are government offices, but
there is a trend toward thinking office=diplomatic is a better
choice than office=government; and<br>
d) the office=diplomatic tag in tandem with diplomatic=* would
meet OSM guidelines and support more accurate mapping.<br>
<br>
If my sense of growing consensus is correct, I suggest that
diplomatic=* would include only [embassy, consulate,
non-diplomatic]. </font></div></blockquote><br><div><br></div><div>I am not an English native speaker, but from the dictionary reading I did not get the impression amenity is very far fetched for embassies, certainly less than for prisons.</div><div><br></div><div>From a data structure perspective, for certain applications (e.g. osm-carto) a “main” key must be present in order to have the object not filtered out during database import. As I believe embassies should be in our “standard set” of data, a main key is desirable.</div><div>I would see embassies as a good fit for osm amenity (indeed it is already there), they are different to other offices because of their particular status, and “office” is also not in the very core.</div><div><br></div><div>Cheers, Martin </div></body></html>