Proposal:Consulate general

From OpenStreetMap Wiki
Jump to navigation Jump to search
consulate general
Proposal status: Approved (active)
Proposed by: overflorian
Tagging: consulate=consulate_general
Applies to: node, area
Definition: Let's standardize the tag used for the type of consulate
Statistics:

Draft started: 2021-02-14
RFC start: 2021-02-14
Vote start: 2021-03-03
Vote end: 2021-03-18

Overflorian (talk) 15:25, 8 December 2021 (UTC) Update 8 déc 2021: I just made the change https://www.openstreetmap.org/changeset/114707902 and will update the wiki pages today.

Proposal

I suggest to standardize the tag used for a consulate general (a type of diplomatic office). We can either use :

I suggest

  1. to use only the second proposal. I believe that we should formally deprecate the tag diplomatic=consulate_general and let it die once and for all.
  2. to initiate an automated worldwide edit as detailed over this dedicated wiki page to switch all the diplomatic=consulate_general to diplomatic=consulate combined with consulate=consulate_general.

Rationale

With the recent release of the v5.3.0 of openstreetmap-carto (see https://github.com/gravitystorm/openstreetmap-carto/blob/master/CHANGELOG.md) “amenity=embassy is no longer rendered, and office=diplomatic with diplomatic=embassy or diplomatic=consulate is instead (#4168)”.

Therefore the diplomatic=consulate tag becomes far more important than before.

Also:

Examples

Rendering

Both tags are well interpreted by OpenDiplomaticMap. See https://anders.hamburg/osm/diplomatic

Features/Pages affected

External discussions

After doing the mistake of editing the tags without discussing them (once again, sorry about that guys), I made an initial proposal here https://www.openstreetmap.org/user/overflorian/diary/395647 and launched a discussion over the tagging mailing-list https://lists.openstreetmap.org/pipermail/tagging/2021-February/059180.html

Comments

Please comment on the discussion page.

Voting

Instructions for voting
  • Log in to the wiki if you are not already logged in.
  • Scroll down to voting and click 'Edit source'. Copy and paste the appropriate code from this table on its own line at the bottom of the text area:
To get this output you type Description
  • I approve this proposal I approve this proposal.
{{vote|yes}} --~~~~ Feel free to also explain why you support proposal.
  • I oppose this proposal I oppose this proposal. reason
{{vote|no}} reason --~~~~ Replace reason with your reason(s) for voting no.
  • I abstain from voting but have comments I have comments but abstain from voting on this proposal. comments
{{vote|abstain}} comments --~~~~ If you don't want to vote but have comments. Replace comments with your comments.
Note: The ~~~~ automatically inserts your name and the current date.
For full template documentation see Template:Vote. See also how vote outcome is processed.
  • I approve this proposal I approve this proposal. --S Frantz (talk) 08:51, 3 March 2021 (UTC)
  • I approve this proposal I approve this proposal. --PanierAvide (talk) 09:08, 3 March 2021 (UTC)
  • I approve this proposal I approve this proposal. --Gendy54 (talk) 09:14, 3 March 2021 (UTC)
  • I abstain from voting but have comments I have comments but abstain from voting on this proposal. The proposal is not necessary, there was a clear support for deprecation expressed already --Mateusz Konieczny (talk) 10:04, 3 March 2021 (UTC)
I agree but my previous edits (see this changeset) has been reverted due to a lack of vote. Therefore, let's proceed to this vote before going any further. Overflorian (talk) 10:39, 3 March 2021 (UTC)
Your changeset was reverted because it automatically changed features all over the world without prior discussion. This vote will not change the fact that it is required to discuss automated edits, and also it is recommended to limit the changes to one country or region at a time. --Jeisenbe (talk)
See Automated Edits code of conduct for how to get approval for bot edits. It is not involving proposal process. BTW, I marked this tag as deprecated as there is a clear support to do this Mateusz Konieczny (talk) 23:28, 3 March 2021 (UTC)
  • I approve this proposal I approve this proposal. --zorglubu (talk) 11:25, 3 March 2021 (UTC)
  • I approve this proposal I approve this proposal. --Kjon (talk) 10:53, 3 March 2021 (UTC)
  • I approve this proposal I approve this proposal. --Pogregoire (talk) 11:10, 3 March 2021 (UTC)
  • I approve this proposal I approve this proposal. --Cyrille37 (talk) 11:24, 3 March 2021 (UTC)
  • I approve this proposal I approve this proposal. Although the justifications in the rationale mostly refer to rendering purposes, giving the impression this proposal "is for the renderer", it is clear to me, reading between the lines, it is not the main argument. It is to deprecate a tagging scheme that became less popular over time and improves consistency with other more popular tagging schemes. Good enough for me.--Bert Araali (talk) 11:37, 3 March 2021 (UTC)
  • I approve this proposal I approve this proposal. --Nospam2005 (talk) 12:16, 3 March 2021 (UTC)
  • I abstain from voting but have comments I have comments but abstain from voting on this proposal. The proposal is not necessary, there was a clear support for deprecation due to the approved office=diplomatic proposal --Jeisenbe (talk) 15:53, 3 March 2021 (UTC)
  • I abstain from voting but have comments I have comments but abstain from voting on this proposal. amenity=embassy is already deprecated. From review of comments above, it appears that author is actually seeking permission for mechanical edit to convert remaining tags. While I would probably support that edit, it need be discussed via the talk list or in appropriate local fora. The proposal process is the wrong forum for this ask. --ZeLonewolf (talk) 16:02, 3 March 2021 (UTC)
  • I approve this proposal I approve this proposal. --Mar Mar (talk) 18:40, 3 March 2021 (UTC)
  • I oppose this proposal I oppose this proposal. the proposal is too confusing :

diplomatic=consulate_general has not been formally deprecated and if Floriant wishes, I support his proposal to deprecate it formally since the 2 replacement tags are already approved.
consulate=consulate_general has already been (recently) approved, I don't want to revote to re-approve the same thing
the mass editions procedure have no vote, there is confusion of 2 procedures, which I do not find useful to support.
Pease 1) to stop the current vote 2) to take the AE out of the proposal section 3) better describe that it's not a vote for the approval of consulate=consulate_general but only on the depreciation of diplomatic=consulate_general, point that I support 100% of course it is obvious that it must be seen the approval of the 2 others Marc marc (talk) 11:43, 9 March 2021 (UTC)

  • I approve this proposal I approve this proposal. --Something B (talk) 22:36, 10 March 2021 (UTC)
  • I approve this proposal I approve this proposal. --Mashin (talk) 01:11, 31 March 2021 (UTC)
  • I oppose this proposal I oppose this proposal. reason --Highflyer74 (talk) 12:42, 5 April 2021 (UTC) I second the above comments. This proposal is a mix of two different issues. office=diplomatic and its sub-tags has been approved and is well designed, thus no need to include consulate=consulate_general in this proposal as it is part of office=diplomatic.
  • I approve this proposal I approve this proposal. Eduaddad (talk) 02:45, 26 April 2021 (UTC)