From OpenStreetMap Wiki
(Redirected from Talk:Wiki About)
Jump to: navigation, search

If you have ideas for the wiki, you can generally just do them, by editing the wiki! Big restructuring can be discussed in relation to WikiProject Cleanup, but in general we would encourage you to be bold.

If you have ideas for technical improvements to the way the wiki works, e.g. extensions we should install, you might add them here, and/or raise tickets in trac (raised as 'component=admin'):

Older requests can be found here:


pt and pt-BR namespaces

I have noticed that there are no posibility to search in portuguese pages on the wiki. There have been translated a lot of pages from Map Features into pt-BR, and a few of them have redirects from pt namespace. Since there are no map feature translated to pt, I suggest that pt namespace could be made as an alias to pt-BR namespace, and these two to be allowed on the search page as a pt search. There are a general movement in the Brazilian comunity to get important parts of the wiki translated as an incentive to reqruite more Brazilian mappers, allowing a Portuguese search will be helpful in this process. It is also worth noting that many of the subpages of WikiProject Brazil are only written in Portuguese. --Skippern 12:40, 31 December 2009 (UTC)

Some related discussion about this here: Talk:Searching the wiki
'"pt namespace could be made as an alias to pt-BR namespace". At the moment neither of them are namespaces. They're just page titles with colons in them. I think maybe the best thing would be if we got rid of all pages with pt-BR: prefixes, merging them until we only have PT: prefixs. Clearly that'll involve coming to some transatlantic agreements on wording things though (just as the wikipedia PT community do I believe)
The PT: prefix could be made into a proper searchable namespace either before or after that happens. I think User:Firefishy is doing this on the basis of number of wiki pages already present with prefix, so more likely to happen if progress is made with a merge
-- Harry Wood 15:45, 24 February 2010 (UTC)
Once there are a reasonable number of pages to justify the namespace, send me a request to make the namespace. Creating the namespace requires the wiki to go readonly and could involve minor template + search breakage. -- Firefishy 13:30, 25 February 2010 (UTC)
In my opinion, pt and pt-BR are the same language (with minor orthographic or grammatical differences or more allowances in Brazilian) and do not require separate pages (it is perfectly possible to create versions of pages that can be read and accepted by native Portugueses and Brazilians, just like in Portuguese editions of Wikipedia, or Wiktionary).
The ony justified need for "Brazilian" pages is for the projects related to the mapping of Brazil itself (independantly of the language used for other translations). And even those pages should be translatable to other languages than Portuguese.
Just like in Wikimedia Commons, all page names should be in English (the only difference being the language code prefix used in this wiki, instead of subpage names, a solution that is superior, in my opinion, to language prefixes, when working in the same namespace).
However, it is justified to create a "PT:" namespace (or preferably "pt:" using lowercase) for allowing searches of pages written in Portuguese.
For searching pages related to the mapping of Brazil, or of Portugal, the ideal solution is not the namespaces, but a coherent set of categories and a good starting wikiproject page (which should be translatable).
Verdy_p (talk) 03:37, 19 February 2012 (UTC)

That's an old discussion, but the idea of unifying the PT and pt-BR namespaces has come up again in discussion here: discussão sobre a unificação no prefixo Pt. -- Harry Wood (talk) 04:24, 31 March 2014 (UTC)

Extensions Requests


I'de like to see Extension:InputBox added - This would enable some simple "create" pages that load up a preload edit page. Martin Renvoize 11:02, 5 January 2010 (UTC)

Enabled -- Firefishy 14:47, 15 September 2011 (BST)


I'm thinking Extension:StringFunctions. Use of {{#explode:}} could simplify calling some of the templates: instead of (or making optional) passed parameters, they could be computed from the {{PAGENAME}}. Because Key: and Tag: aren't namespaces, titleparts is less useful than it could be. --goldfndr 11:22, 9 January 2010 (UTC)

I have enabled $wgPFEnableStringFunctions which is part of Extension:ParserFunctions. --Firefishy 14:51, 15 September 2011 (BST)


Please consider adding Extension:FlaggedRevs to OSM wiki, and put me and User:Steve in the 'editor' and 'reviewer' groups. --BrandonSkyPimenta (TalkContribs) 18:58, 29 May 2012 (BST)

There are no need to enable this extention with the current rate of vandalism. This extention will require the administrators to validate all the edits made to the wiki and there are desire to have to do so.
As for the seccond part of the request, no users will be granted any extra powers without proving themselves responsable enough. Gnonthgol 20:45, 29 May 2012 (BST)

Embed Videos on Wiki Pages

Would it be possible to instal the Embed video extension. The main reason I am looking for this is to allow videos illustrating how to use JOSM, JOSM Plugins, Potlatch, iD etc, basically as a training tool integrated into the wiki page itself, rather than just an external link. DaCor (talk) 17:50, 22 April 2013 (UTC)

Using the Wiki from mobile devices

Has there ever been any discussion of adding the Mobile Frontend extension? I'd like to be able to use the resources of the OSM Wiki from a mobile device. --Mnewnham (talk) 04:04, 5 August 2013 (UTC)

Even if it doesn't is my own requirement, I think it's not that a big problem. On another wiki I got good results with a mobile theme and a browser switch. --!i! This user is member of the wiki team of OSM 08:52, 5 August 2013 (UTC)
Note, just discussed there: --Aseerel4c26 (talk) 12:55, 5 August 2013 (UTC)



In a PRE-box, line-height is too low and underscores (_) are cut. In the following example, shop=scuba_diving looks like shop=scuba diving, which is missleading.. Proposed_features/scuba_diving#Dive-Shops

Tested with Opera and FireFox on Windows --t-i 23:27, 23 February 2010 (UTC)

Not just because it's in a pre box. Also a problem here: amenity=dive_center but not here: Tag:amenity=dive_center. Maybe we can fix this in the style definition of Template:Tag. -- Harry Wood 01:01, 11 March 2010 (UTC)

Hidden IFrame for JOSM link

It would be nice to add in the main template, or probably by script, an hidden iFrame as target of http://localhost:8111 links.

I think a global javascript can add the iframe with an id like josmTarget when the page is loaded, and put a target="josmTarget" on each link starting with http://localhost:8111

It would avoid opening a new tab with right click on the link.

--FrViPofm 15:06, 27 February 2010 (UTC)

Something like that :

addOnloadHook(function () {
  var target = "hidenIFrame";
  var frame = document.body.appendChild(document.createElement("iframe"));
  var links0 = document.getElementById('bodyContent');
  var links = document.getElementById('bodyContent').getElementsByTagName('a');
  for(var a in links) {
    if(links[a].href && links[a].host == 'localhost:8111') {

OK. It still open a new tab, but it doesn't replace the current one. I you put this code on your monobook.js, you can check the j link in 207794 b a r j s

--FrViPofm 23:07, 14 March 2010 (UTC)

Any idea how to do this with MediaWiki 1.17? -- Firefishy 14:53, 15 September 2011 (BST)

Install extension for including videos (youtube, etc.)

Could somebody please install an extension for including videos in a OSM wiki page? Or is there already an extension installed? Which one?

Gubaer 10:55, 28 March 2010 (UTC)

you can find all installed extension here. There is no one extension from YouTube extensions --Dnikitin 17:36, 20 April 2011 (BST)

External URL Whitelist

Is it possible to exempt links to well-known OSM tools from the captcha requirement? Even adding Template:KeyDescription to a page results in a captcha right now (because of the osmdoc/tagwatch/tagstats links). --Tordanik 20:00, 1 July 2010 (UTC)

Please add these to the talk page of MediaWiki:Captcha-addurl-whitelist -- Firefishy 20:52, 1 July 2010 (UTC)

Explain it to newbies

What about this clip to show newbies the principals of a wiki? --!i! 08:49, 10 August 2010 (BST)

Request Template development

Hi for refactoring Software we need somebody that is able to build up a clever template. Anybody out there? --!i! 13:44, 12 August 2010 (BST)

Bot flag request: TTTBot

I intend to use a bot for keeping tables such as those on Software/Mobile_phones synchronized with each other and with info boxes on software description pages. For now, I'm planning to only run it once a day after beginning regular operation, and the bot will only perform a few write edits each time - the exact number depends on what tables need to be updated, of course, but there aren't that many pages that contain software overview tables right now, and each such page will be edited at most once per bot run.
It would be useful to have a bot flag for the account User:TTTBot: It's required for history/watchlist bot filters to work properly. And, of course, it could make sense to include external links (e.g. to the projects' websites) in some of the tables - I haven't implemented solving captchas yet. ;-) --Tordanik 21:44, 27 August 2010 (BST)

Bot group added. -- Firefishy 10:44, 23 September 2010 (BST)

Thumbnails Problem

Hi, there seem to be a problem with adding new animated GIF files: The gif works fine on my PC dunno why he reports a "missing thumbnail parameters" :( Anybody an idea how to fix it? --!i! 08:55, 30 August 2010 (BST)

Fixed. HUGE image. 125 frames. It was exceeding mediawiki sanity checks + memory usage limit. I've upped these for now. If it cause problem I'll need to reduce it. --Firefishy 12:31, 23 September 2010 (BST)

Template-based software table generation to go "live" next week

As mentioned previously, we (= User:!i! + me) are trying to replace manually updated wiki tables with similar tables that are created by a bot. You can see a few tests on subpages of my user page, for example: all software, Desktop software only. We intend to place tables like these on pages in the article namespace soon.

I'm announcing this to make sure that no one has objections, especially from a technical POV. The bot software has already been run a few times, and I haven't noticed any significant issues myself.

For more information, see User:TTTBot, Template:Software2 and Template:SoftwareTable. --Tordanik 20:57, 17 October 2010 (BST)

Forming a Wiki Team

  • In order to shorten the following reading: The Wikiteam has been founded. Contact: here and here. Good luck! -- Tirkon 07:10, 7 November 2010 (UTC)

Hi, I got a few times the hint that some people would like to contribute to the wiki but lack of knowledge to change some pages e.g. Tables, Templates usage. They wished some kind of guardian that they could consult if they arent't sure. And they would like to ask somebody where they can find what in the wiki.

What about forming a wiki team that support normal users if they have questions?

The wiki people could benefit in this by coordinating e.g. who is monitoring which pages, working on cleanup, ...

Currently I'm working on a statistic on the wiki usage that shows how little people realy working on updating/refactoring/updating the wiki --!i! 07:20, 2 November 2010 (UTC)

You mean there are other people working on clean ups? :-) Great idea where should they ask questions, on ? Erik Johansson 21:01, 2 November 2010 (UTC)
Yes I made a report on the wiki edits last 3month and send a pm to the most active ones. IMHO it would be cool to form a team to coordinate us and to make it people easy to join :) Your link is very much unknown to my german OSM community. But you are right, there are other channels for support, too. But to make it as easy as possible to new editors we should offer direct contact?--!i! 21:36, 2 November 2010 (UTC)
Hi guys, Yes,its nice to see that I'm not the only one who think documenting is important. Yes I want to put some effort in supporting others. Maybe a Wiki mailinglist will be a great start. ZMWandelaar
Well just another ML is IMHO not a good idea. What will it be for? For internal or external communication? I guess people expect Wiki members right here: at the wiki ;) --!i! 22:20, 2 November 2010 (UTC)
What I understand is that you want to form a group of senior Wiki users contributing in supporting junior or medior Wiki users in contributing to Wiki. Are there more goals? ZMWandelaar
Yes right some guidance to the new ones. As I said it is furthermore a chance for the senios to get better connected and work together on bigger tasks, getting feedback on ideas,...--!i! 08:35, 3 November 2010 (UTC)
To do so in an Geografically difficult team we need a fast and firm communication system. Therefore I proposed a Mailing list cause these TALK pages a highly annoying while discussing a matter. Next to the ML-channel it's maybe good to introduce IRC/MSN for incidential live discussions. Important endresults out of these discussions should be maintained into Wiki pages concerned.--ZMWandelaar 12:06, 3 November 2010 (UTC)
Ah ok I see your point. So lets wait what the others say. --!i! 12:18, 3 November 2010 (UTC)
Yes, Let's wait. I suggest the following first steps:
  • Collect all names of currunt project members
  • Descide what communacation channels will be used
  • Organise primairy channels
  • Start ProjectPage: Static data, Actual "Todo list"
--ZMWandelaar 13:24, 3 November 2010 (UTC)
It makes sense to offer a way for people to ask questions (though already works quite well for the English-speaking community), and for coordination of wiki work. Ideally, it should be an easily useable communication channel. Therefore, it should not be a wiki talk page. While a mailing list is a better choice than a wiki page, these are not considered comfortable by most non-technical users either. If we make sure that there is a web frontend for the mailing list, then it could work. Otherwise, creating a "wiki" sub-forum on would seem a good option. --Tordanik 17:48, 3 November 2010 (UTC)
Agree. Discussions on Forum and Collecting ToDo's on our ProjectWikiPage wil be a strong communication channel. --ZMWandelaar 09:22, 4 November 2010 (UTC)
Agree I preffer a forum cause of the SingleSignon so everybody has a login and can drop us a message. We might think about IRC or if everybody wants to publish a IM account or if we pledge onself to enable the wiki mail function and to monitor our mailbox x times per day? I asked user:Lambertus for a subforum --!i! This user is member of the wiki team of OSM 11:12, 4 November 2010 (UTC)
On what page would you like to discuss Cleanups on bigger pages? What about cleaning up the WikiProject Cleanup page first? I guess this should be the central place? --!i! This user is member of the wiki team of OSM 14:52, 4 November 2010 (UTC)
By the way, I created the draft of a userbox template Template:UserWikiTeam. We can adapt our signatures, too --!i! This user is member of the wiki team of OSM 17:01, 3 November 2010 (UTC)
Now there is a category and Wikiteam page for further informations. Feel free to join or add informations.... --!i! This user is member of the wiki team of OSM 13:13, 4 November 2010 (UTC)
I contacted a lot of people worked/ing on the wiki (sry for the spam folks) hopefully we get some much more :) --!i! This user is member of the wiki team of OSM 16:41, 4 November 2010 (UTC)

I agree to join up. As a former librarian, I get interested in categorizing and namely building a general frame (or tree) with 10 super-categories or so. I can let French users to know what it could have be proposed. Ch. Rogel 21:29, 4 November 2010 (UTC)

Thats cool. I have never thought that much about Categories but recognized they are important to find similar pages. Personaly I focus a bit more on updating/merging pages. --!i! This user is member of the wiki team of OSM 09:09, 5 November 2010 (UTC)

I also agree to work on the Team, though my efforts recently have dwindled somewhat since finally getting a job, as koha developer. Martin Renvoize

Added; I'de better start being useful again then.. Martin Renvoize This user is member of the wiki team of OSM 08:04, 5 November 2010 (UTC)
No problem Martin. Everybody can spend as much time as he personaly has. The only thing is we should coordinate the monitoring on bigger pages and "communication" pages when somebody external adds a request.

Do you agree to continue the team management works on talk:wiki/team?--!i! This user is member of the wiki team of OSM 09:09, 5 November 2010 (UTC)

For your attention, I bloged about the current wiki usage [1] --!i! This user is member of the wiki team of OSM 19:41, 5 November 2010 (UTC)

Ill join this wikiteam... not on osm a supper lot anymore, but Ill try and help out, give ideas, work though solutions where needed. I installed all the wiki templates found on the USA wiki project, and the proposal pages, so I know my way around a wiki.. Ill try and check in every now and then. Check out Blue Ribbon features if you get the chance. Something I'm proposing. --Nickvet419 Flag of United StatesThis user is member of the wiki team of OSM 18:50, 6 November 2010 (UTC)

I'll join this wikiteam. I am one of the main contributor in translating to Brazilian Portuguese (Pt-br namespace). Mainly work on translating tags. Brazilian Portuguese is not my main language, but since I live in Brazil, and hope for the Brazilian comunity to grow, I feel it is better with a page with bad grammar than no page at all. Tag documentation in Brazilian Portuguese is important for reqruiting more Brazilian users to OSM, as English skills usually are very limited. --Skippern 22:31, 7 November 2010 (UTC)

Links: Case Sensitive and Namespace


caused by the new on demand search function some pages hide themself for the user just cause he didn't captitalized the first character. Similar problems on namespaces. Are there any mediawiki extensions that solve this problem by allowing links and searches independent from Namespace or capitalisation? --!i! 12:55, 3 November 2010 (UTC)


Hi! How i can add link to Armenian main page in "Available languages" template? User:Pandukht

Was on my talk page, sorry to complicated for me, anybody with more experience in this templates? --!i! This user is member of the wiki team of OSM 19:01, 8 November 2010 (UTC)
Done. --Mormegil 11:54, 14 November 2010 (UTC)
Great, thank you! --!i! This user is member of the wiki team of OSM 16:04, 14 November 2010 (UTC)
Thanks everybody:)--Pandukht 13:28, 21 November 2010 (UTC)

Reordering Navigation panel

Hi, few weeks ago I read about a user mentioning a better order for the left panel you always see in the wiki. Is there anything happened? --!i! This user is member of the wiki team of OSM 18:08, 9 November 2010 (UTC)

Local groups

Hi, the german divison has a template to branding the local groups that meet regulary: Template:Lokale_Gruppe. That is collected and displayed for example at Would be cool to extend it for a worldwide use, right? Is there anybody that can integrate an OpenLayers map displaying a KML/GML with a listing of all groups? --!i! This user is member of the wiki team of OSM 18:11, 9 November 2010 (UTC)

I create template:user group. Feel free to improve it. I also added an entry to our forum. --!i! This user is member of the wiki team of OSM 12:06, 27 November 2010 (UTC)

Add user group that does not need to enter captchas

When you edit Wiki pages frequently, it gets very annoying that you have to enter a captcha every time you add an external link. This is especially the case when you update pages about external OSM projects, which obviously contain several external links. Also, when you use a template (such as Template:Relation) that links to external tools, a captcha is asked. Sometimes it even happens to me that I close a page after pressing the Save button and the content is lost because I missed the Captcha.

A user group could be added to the Wiki whose users don’t have to enter captchas. Users could be added to this group either automatically (for example when they have made more than 50 edits and the first edit is more than two months ago) or manually on request. --Candid Dauth 18:33, 4 January 2011 (UTC)

Indeed this is very annoying (well I added >160 Software tools pages ;)) but a mechanism might result in Spam. What about creating this group and everybody has to ask the admins to get this flag? --!i! This user is member of the wiki team of OSM 09:10, 5 January 2011 (UTC)
Or, at least, the captcha could be configured so that it is not required for known OSM tools (like those referenced in Template:Relation). --Mormegil 16:58, 4 May 2011 (BST)
Yeah we have that already: MediaWiki:Captcha-addurl-whitelist I just added the known OSM tools referenced in Template:Relation. See any other's we're missing? -- Harry Wood 17:43, 4 May 2011 (BST)
Yep, localhost (for JOSM RemoteControl), even though it would be funny to spam with localhost, captcha is still required for that one. --Mormegil 14:37, 6 May 2011 (BST)
OK added 'localhost'. Again I'm not sure if that works. -- Harry Wood 15:44, 6 May 2011 (BST)
I support the original idea of creating a group of users exempt from captcha solving, with users being added to that group automatically after a small number of edits (20 edits would be enough imo). I don't expect more spam because of that - blatant linkspammers, as many of those blocked previously, seem to be caught quickly anyway.
The whitelist is nice for a few very well-known sites, especially those used in common templates, but I'm still finding myself solving captchas all the time. Links to websites, programs, papers, news articles etc. tend to be pretty unique and make up a large share of the links that are being added manually, i.e. not as part of templates. --Tordanik 15:31, 31 July 2012 (BST)
Whitelisting of domains is a start at least, but I think there are some entries seem to be missing such as (OSM inspector, download of OSM extracts). May I just add it myself (I have not touched any template before)? G0ldfish 11:28, 2 August 2012 (BST) (only 4 reloads to get a fairly readable one this time)
I've asked that question before, see #External URL Whitelist. That being said, whitelisting is not a sufficient replacement for what is being suggested here. The last 5 domains I linked to were,,, and, none of which are good candidates for whitelisting. --Tordanik 16:30, 2 August 2012 (BST)
$wgCaptchaTriggers['addurl'] = false; is now set. Hopefully spam does not become a problem. -- Firefishy 12:17, 16 August 2012 (BST)
Any progress on the original idea? I am getting older and do have a hard time reading these annoying captchas texts :-( -- Dirk 2014-03-17
We have several threads all over the wiki about those annoying captchas (which are bad for many(!) reasons). User group - I found a extension which would help: Talk:WikiProject_Cleanup#Captchas_are_annoying_-_please_switch_off. --Aseerel4c26 (talk) 12:53, 17 March 2014 (UTC)

Problem with template

Hi, can anybody help me fixing an issue why using Template:Countryflag will result in a linebreak Flag of Germany.svg after the flag? --!i! This user is member of the wiki team of OSM 14:23, 7 February 2011 (UTC)

It should be fixed. --Andrew 17:52, 7 February 2011 (UTC)
Thanks Andrew! --!i! This user is member of the wiki team of OSM 20:21, 7 February 2011 (UTC)

help for Template formating

Hi, once again I would need the help of another wiki specialist. Currently my template gets problems, even if you add the attributes but they are empty. So my code surrounding this issue doesn't seem to work :/ Template:User_group. Rome/Incontro is such an example --!i! This user is member of the wiki team of OSM 09:12, 13 February 2011 (UTC)

Thanks to user:Firefishy this was fixed :) --!i! This user is member of the wiki team of OSM 09:43, 15 February 2011 (UTC)

Limiting TOCs

Hi, I putted Template:TOC_limit from mediawiki here to control the depth of TOCs but it doesn't work. Can anybody please take a look if I did something wrong? --!i! This user is member of the wiki team of OSM 08:27, 23 March 2011 (UTC)

The template does not do anything interesting, it only marks your wish. The real work is done by the relevant part of MediaWiki:Common.css (search for toclimit there), which would need to be copied here as well. --Mormegil 16:55, 4 May 2011 (BST)
Ah ok, well I dont think it's not that important. You can tweak the formating using bold lines. --!i! This user is member of the wiki team of OSM 07:50, 7 May 2011 (BST)

PNG size links on SVG pages

Commons and other Wikimedia wikis show links for automatically rendered pngs in various sizes on the image description pages for SVGs. Example: [2] ("This image rendered as PNG in other sizes"). Is there an easy way to implement that feature on our wiki, too? The rendering already works, of course, but links like that would make the functionality more clearly available, especially for people who don't have SVG editors installed. --Tordanik 21:07, 30 April 2011 (BST)

Done - Firefishy 12:53, 1 May 2011 (BST)

User working on established Templates

Hi, as some might notice User:Verdy p is working on a lot of templates that are spread on a lot of pages as languages or Software2. Even he tries to do it well, please let's keep an eye on this, as altering this templates causes a lot of rerendering nested pages. --!i! This user is member of the wiki team of OSM 19:20, 3 January 2012 (UTC)

Sub- and SubSubTags

Hi, i miss some comfort to tag something like this:
I think it make no sense, create a page (by following the red link).
My proposal is, to link the Tag to surface, and Value to wood.
Here some ideas:
cycleway:right:surface=wood because right, left and both belong directly to (cycle)way, its a own way (like right_cycleway:surface=*)
I prefer the second or third one.
It helps to create footway:left:smoothness, parking:left:lane, oneway:bicycle=yes etc.
I fond on other wiki-pages the "subkey=???" and this ":=", but first it does not help (especially for Values), and second i don't found a docu in this wiki.
vehicle:backward=no (Tag|vehicle|:=backward||no)
vehicle:backward=no (Tag|vehicle||no|subkey=backward)
-- MasiMaster 16:26, 10 January 2012 (UTC)

I'm not sure if we have Mediwiki strings extensions, that can deal with this problem (finding ':' and adapt wiki links). Anybody knows? BTW this is a very often used template, so changing it is very fragiles as it needs a lot of page updates :(
I'm not sure if there is some kind of agreement if this kind of subspacing is accepted by the community, as on the other hand we need some more general templates to make a tagging scheme description more machine readable. So templates expressing master keys, enumerated values for subkeys and so on... --!i! This user is member of the wiki team of OSM 16:32, 10 January 2012 (UTC)
You say "this is a very often used template" and "not sure if there is some kind of agreement is accepted by the community". I agree to both, and say: it's a "de facto"-norm. :) Or where/how can we ask the community!? Like a "simple" key or value proposal? ... Additional: I found Proposed: right/left that used :right/:left. More than 66% approve this. -- MasiMaster 20:39, 12 January 2012 (UTC)
IMO the problem is, that we don't have any agrgeement on how I call it 'meta-tagging thigns' like how should we create multi-value pairs, how to use flags and subspacing, guidelines for namespacing and so on and so on. As said beside this 'social' problems there are technical problems. To me it seems to be pretty hard to extend the template in your suggested way, but maybe I'm just not skilled enough. if somebody tries to fix that, please use a new template for testing, to avoid wrong links and stressing the cache, please! --!i! This user is member of the wiki team of OSM 22:40, 12 January 2012 (UTC)
I had done it. It should work good: Template:Testdummy. Some hints and examples are here: Testdummy-Examples -- MasiMaster 13:50, 18 January 2012 (UTC)

Spam user?

I'm not sure if user:Deutsch_und_Stolz does some bad edits, as he adds contgories for german translation, even on pages that are obviously already translated and so on. What does you say? --!i! This user is member of the wiki team of OSM 21:46, 17 January 2012 (UTC)

Yeah User talk:Deutsch und Stolz
Not spam as such. He's clearly not managing to advertise anything. Could be vandalism, but I think it's most likely just somebody who doesn't understand what they're doing. Maybe you could translate my question into german, but to me it looks like all of those edits are wrong and need reverting.
-- Harry Wood 00:21, 18 January 2012 (UTC)
As he noticed this discussion, without any comments, we should revert the changes and maybe bann the user if he still proceeds --!i! This user is member of the wiki team of OSM 06:47, 18 January 2012 (UTC)

MediaWiki:Lang/xx pages

There was some discussion whether the sitenotice (currently license change info) could be translated depending on the user's interface language. However, it seems that neither features such as {{int:lang}} nor branching to MediaWiki:Sitenotice/de work in the OSM wiki. Documentation on Wikimedia Meta seems to indicate that language switches using {{int:lang}} require the existence of MediaWiki:Lang/xx pages such as these. I'm not sure whether that actually works the way I imagine, but it would be useful if it did, imo. --Tordanik 04:14, 22 January 2012 (UTC)

Yes, this is true. I also ask for a wiki administrator to import these small messages. And then we will ease the translation of this wiki, notably in templates, like what is being performed in Wikimedia Commons. This is really a useful thing, and I have asked for this support in several places. — Verdy_p (talk) 03:25, 19 February 2012 (UTC)

per-page usage stats

Hi there. There is an entry about this form 2008 in the Archive, but nobody answered back then. Is it possible to get per page usage statistics for the wiki? Wikipedia has this on some external server: I have no idea about the technical background. This would be immensely useful for directing translation effort as we could tackle popular pages first. --Chaos99 08:10, 15 February 2012 (UTC)

too-many-function-calls warning on a lot of pages

Thousands of sites are listed in the Category:Pages_with_too_many_expensive_parser_function_calls (to which I can generate no wiki link??) for to many expensive parser function calls. I tracked that down to the Template:Language, where too many #ifexists are used. I don't have a solution for this, but if there is none, we can omit all the warnings while editing and the automated categorization, as they don't add any information (and it might save some parser calls by itself).----User:Chaos99 08:00, 15 February 2012 (UTC)

See above, user:Verdy p worked on the corresponding templates but he currently hadn't fixed that bug. I will ask him again :) --!i! This user is member of the wiki team of OSM 11:04, 15 February 2012 (UTC)
I don't thinks that's a bug that can be fixed in the language template. To keep it's functionality, it has to do those #ifexists calls. It's just that we can ditch all the warnings at the edit pages if this really IS unresolvable. --Chaos99 12:16, 15 February 2012 (UTC)
Well sadly this bug occurred since Verdy did the edits. As far as I can understand (I'm not a template expert), the functiaonality is now to modularized. But verdy gives a real detailed explaination at User talk:Verdy p#Too_many_parser_calls and he would like to fix it with the assistance of a Wiki Admin --!i! This user is member of the wiki team of OSM 14:37, 15 February 2012 (UTC)
I've proposed a solution that works more or less for now, but something else must be implemented for the longer term. See my page for the reply and the complete description of the problem and how I solved it (temporarily). There's more work to do, but there's never been any more problem than what there was before, with lany links not appearing properly (I am already performing lots of cleanup within inconsistant links and redirects caused by various renamed pages and a severe lack of maintenance of this wiki for too long).
Yes there remains quirks, but much less than before.
In my opinion, the use of #ifexist should be completely deprecated, and we could avoid having to create many pages for each translation and maintain them, if we could support "autotranslatable templates" like in Wikimedia Commons. This just requires importing a few message resources in the "Mediawiki:" namespace, notably Mediawiki:lang containing "en" (the default language of this wiki) and its subpages (one for each language code, containing exactly the same language codes already listed in the users' Preferences page and supported by MediaWiki's interface translation). With those few small resources the documented wikicode "{{int:lang}}" would work properly instead of returning for now the static string "<lang>" that appears for resources that do not exist in a basepage of the "Mediawiki:" namespace. — Verdy_p (talk) 03:21, 19 February 2012 (UTC)

ParserFunctions version

I have been trying to write a template that formats dates in different languages using the third parameter to the Mediawiki #time function but #time is always returning English names for months. I notice that the language option has only recently been added to the documentation so maybe our ParserFunctions is too old for it to work. --Andrew 09:58, 3 March 2012 (UTC)

Mediawiki extension for inclusion of sections

Hi, could somebody of the Wiki-Team evaluate if this extension can be installed (or maybe is already installed)? It would enable to include sections of a wiki page into another, like a definition table from one language version to another.

This might hit performance do to parser calls, so please take that into consideration.

Thanks --Chaos99 08:30, 19 March 2012 (UTC)

Shorter Wiki URLs

Both and link to the same page, with the longer version currently being the default URL. But since the wiki already has its own subdomain, the "/wiki" path seems redundant, and the shorter URLs are more readable and handy e.g. when pasting them somewhere. Is it possible to configure the wiki to use the shorter URLs by default? --Tordanik 17:09, 6 April 2012 (BST)


Hello, I think that translation on this wiki would use some improvement and I've proposed a new system at Talk:Wiki Translation#Translate extension. Thanks, Nemo 10:24, 16 August 2012 (BST)

The referenced discussion ended with the announcement that the extension would be installed during the next MediaWiki upgrade. It seems that a software upgrade has happened yesterday, but the extension is not currently installed. Is this topic still on the admins' roadmap? --Tordanik (talk) 19:28, 31 January 2013 (UTC)

Magic prefix for links

Links to certain external sites can be created using the syntax for internal links with magic prefixes. One popular example is wikipedia:, and I guess we all agree that this one is useful. However, there is also the wiki: prefix for creating links to the obscure site of the Cunningham & Cunningham, Inc. consultancy (specifically, the links point to their "ContentCreationWiki") that has no obvious connection to OSM. Is there a reason why that site gets special treatment? --Tordanik 08:59, 3 September 2012 (BST)

WikiWikiWeb is the first wiki in history and that's been MediaWiki's interwiki map default since the beginning of time, that's it. --Nemo 09:03, 3 September 2012 (BST)
Interesting, I've never heard of it for some reason. I just wondered because I've not seen these particular interwiki links used much except by accident. If people want to keep that interwiki prefix for historical reasons, that's fine I guess. --Tordanik 09:20, 3 September 2012 (BST)

Missing lines in diffs

I've noticed that there are often blank lines in diffs where there should be text. This seems to be particularly prevalent with (or even limited to?) templates that have one parameter per line, e.g. [3] and [4]. The yellow and green lines should contain the old and new text in that line, respectively, but appear blank. Can others confirm this? --Tordanik 15:36, 2 October 2012 (BST)

Yes I spotted that recently in this edit. As shown, I changed description on the page, but I also changed the version number within the template fields. -- Harry Wood 15:43, 2 October 2012 (BST)
Should be fixed. -- Firefishy (talk) 12:05, 1 February 2013 (UTC)
Unfortunately not fixed: [5] --Tordanik 17:54, 26 February 2013 (UTC)

Fighting spam tips

Hi, over at the navit wiki we had to restrict edits/signups to manual confirmation, as a lot of hand made spam was entered. Can anybody give us tipps, how we can keep the wiki open, while avoiding spam attacks? How we does it here at OSM?
What we already tried is:

  • making links no_follow
  • captchas from different providers

Would be nice to hear your suggestions :) --!i! This user is member of the wiki team of OSM 10:36, 5 December 2012 (UTC)

This wiki has sufficient editing activity, and sufficient number of users watching changes happening, that spam gets squashed quite quickly when it arrives. There is actually a background level of spam occurring on this wiki. (see the block log) , so it's not like we actually have a killer solution, other than having lots of active users. Lots of users means that A) spam gets noticed and removed quickly and B) wiki edits related to spam and spam cleanup will disappear off the radar quickly without irritating people too much.
On a less busy wiki it's harder. I was helping out the guys running wiki which has very little editing activity. I found the only way to kill off spam to a reasonable level was to put a captcha on all edits (not just those containing a link). Even then some spammers will come along and fill in the captcha every few weeks. Very irritating. I guess on a medium-active wiki you might try to put the captcha just on edits containing links, but spammers will come along and add content even if it doesn't contain links, just because they're annoying like that.
I think an important thing to realise with spam fighting is that you need to clean up spam quickly and completely. If you leave spam lingering on your site, then google indexes it, and this encourages more spammers to come along. If you have a wiki riddled with spam, you need to use Extension:Nuke to get rid of it all, then after that, whatever solution you go for, you need to keep an eye on it, and aim to revert spam within a few hours when it comes.
No silver bullet solution sadly
-- Harry Wood 12:29, 5 December 2012 (UTC)
Interesting experiences, thanks for your answer Harry! Will do our best :) --!i! This user is member of the wiki team of OSM 21:27, 5 December 2012 (UTC)
OSM wiki uses...
$wgSpamRegex = "/bunch of words I cannot save on the wiki here/i";
$wgDnsBlacklistUrls = array( '', '' );
require_once( $IP.'/extensions/ConfirmEdit/ReCaptcha.php' );
$wgCaptchaClass = 'ReCaptcha';
require_once( $IP.'/extensions/TorBlock/TorBlock.php');

-- Firefishy (talk) 12:04, 1 February 2013 (UTC)

Invert translated local pages

In France, all the regional or departmental pages have the prefix France: and the name of the region, but in french - I think, it's logical. My deparment have a (older) english page as main page, and a "translation" in french - I means, this don't is systematicly. I will restructure the page in french, with subpages etc., and actualize the content. Can someone change the addresses, so that the main page is now french (and the history is'nt deleted) ?

Actualy, the two pages are here : - [6] - [7]

I think, the english page can be moved on the address, then move the french page on the main page,, and then I can add a redirect for olds bookmarks and links, and create my subpages. --CepVingraunais (talk) 15:32, 18 February 2013 (UTC)

I think this should not be done. It probably breaks templates - and possibly parsers - that rely on the convention that non-English pages will use the language prefix if the page exists in more than one language (as I've already said here). --Tordanik 15:50, 18 February 2013 (UTC)
actualy, is not a prefix there (:fr is a suffix). (And the France: prefix already indicate that this is a "french" page...). Then, I have a problem with the subpages. Probably is the hierarchy false, when I put a french page like .../France:Pyrénees_Orientales/subpage -- But all subpages in a very complicated address, where the english page stay the unique english page of this theme ?... The convention, that all region pages of France have the form .../France:region_name is broken too. (sorry, my english is very very bad...) --CepVingraunais (talk) 09:29, 19 February 2013 (UTC)

Countdown clock template

D'you think this coundown clock template would work if we copied it here to use on the State Of The Map 2013 page? I'll give it a try some time, unless someone beats me to it. -- Harry Wood (talk) 15:20, 17 May 2013 (UTC)

Incorrect license information for wiki

The text "Creative Commons Attribution-ShareAlike 2.0 license" wiki's footer links to OpenStreetMap License, which is wrong. Same for the redirect in OpenStreetMap:Copyrights, which is shown to the user when editing a page. --Tordanik 11:44, 1 July 2013 (UTC)

Oh yeah. Of course OpenStreetMap License page used to mention the wiki content ([8]), but the page got removed as duplicate of the website page, which I guess is fair enough.
So now the link in the footer needs fixing. I don't think we can do this through edits to mediawiki message pages. Maybe a server admin needs to look at what we have set for $wgRightsUrl and change it to
-- Harry Wood (talk) 17:00, 5 May 2015 (UTC)
Thanks for your reply. Any server admin reading this? --Tordanik 16:30, 7 May 2015 (UTC)

This issue was fixed at some point. The CC icon in the footer now links

We also now have a Wiki content license page which gives some more details (e.g. about image licenses). That is linked to when you're editing (under the edit box)

-- Harry Wood (talk) 12:41, 10 January 2018 (UTC)

Searching templates

This is an improvement for the search box in the upper right of the page. I extensively use this functionality to check for tags existence. Current search settings do not look into templates. IMO this is problematic as mappers can miss pages when searching tags. I know I can go to Special:Search, click Advanced and check Template checkbox, but it's a pain (and average mapper won't do it). Example of non-matching searches (you need to check the Template checkbox in advanced search to have a pertinent result):

Would it be possible to also search in templates by default? --Oligo (talk) 21:13, 11 July 2013 (UTC)


Wikimedia Commons has just rolled out the new, easy to use editor to EN pages of Wikipedia. This new editor (know as Visualeditor) is really simple to use [1] and will lower the entry to editing the wiki.

Following wikipedia's lead we should prepare to roll this out on our wiki (Wikipedia intends to complete their roll out within 1 month!). It installs as an extension [2] however currently requires a more up to date version of Mediawiki.

I have also created a Trac ticket [3]

--RobJN (talk) 17:33, 26 July 2013 (UTC)

wiki dump

Is wiki dump service still available? This link is already dead. Kcwu (talk) 08:38, 17 January 2014 (UTC)

It *still* isn't available. Who can get this fixed? --Tordanik 23:21, 2 April 2014 (UTC)

Navigation by use cases

I proposed a reorganisation of the wiki navigation, which is also somehow a larger restructuring project. I would be happy to get your opinions about it. --Cantho (talk) 05:22, 28 January 2014 (UTC)

The logo in this project's user box, {{UserWikiTeam}}, is a Wikipedia-style Serif "W", which, I understand, is a Wikimedia Foundation trademark. It should probably be changed to something more neutral or OSM related. Andy Mabbett (User:Pigsonthewing); Andy's talk; Andy's edits 21:39, 2 April 2014 (UTC)

No response, so I've removed it. I suggest replacing it with the "magnifying glass" OSM wiki icon. Anyone know the file name? Andy Mabbett (User:Pigsonthewing); Andy's talk; Andy's edits 11:39, 19 April 2014 (UTC)
The logo with the word Wiki on it seems not to be in the File: namespace, certainly there is no osm_logo_wiki.png (using the name from the HTML) or osm_logo_wiki.svg, the plain logo is at File:Public-images-osm_logo.svg. --Andrew (talk) 12:28, 19 April 2014 (UTC)

wiki search

The search results that drop down from the search box while you type don't include redirecting pages anymore. Who can change that? --LordOfMaps (talk) 08:22, 22 April 2014 (UTC)

Double redirects

I'm just fixing these, do let me know if there are any problems, or indeed any similar tasks that would be useful to the OSM wiki. Rich Farmbrough (talk)

Thank you, Rich, and welcome to the OSM wiki! Andy Mabbett (User:Pigsonthewing); Andy's talk; Andy's edits 07:53, 5 June 2014 (UTC)
A lot of wiki tasks can lead you down rabbit holes of increasing complexity/controversy, but yes, fixing double-redirects is a nice easy one. I tried list some similar nice easy tasks here: WikiProject Cleanup#Ongoing simple cleanup tasks. You're very welcome to get stuck in! -- Harry Wood (talk) 14:06, 5 June 2014 (UTC)

On a more general note, does this wiki allow bots freely, or is there an approval process? Andy Mabbett (User:Pigsonthewing); Andy's talk; Andy's edits 10:32, 8 June 2014 (UTC)

ORCID identifier template

I created {{User ORCID}}.

ORCIDs (Open Researcher and Contributor IDentifiers) disambiguate people - like an ISBN or DOI, but for humans.

Any OSM editor may register, free, for an ORCID identifier, at the ORCID website.

If you have an ORCID identifier, please use the template on your user page. And please feel free to improve the template! Andy Mabbett (User:Pigsonthewing); Andy's talk; Andy's edits 11:10, 8 June 2014 (UTC)

Increase standard thumbnail size from 180 to 220 px

default / your user setting
set to 180 px (current default)
set to 220 px (proposed default)

Currently our standard thumbnail size is only 180 px (width) which is very small for today's screen resolutions. I frequently see thumbnails manually increased in size by our wiki page authors. Sadly, this usually is done by specifying a width in "px" which leads to ignoring of per-user settings and to ignoring of future default thumbnail size changes.

Logged-in users can set their custom size (if they are aware of this setting), but others get the default. For example, Wikipedia has a default of 220 px. I suggest to increase to 220 px. This would be a moderate increase by 22 % (leads to circa 50 % more image area) compared to our current setting. --Aseerel4c26 (talk) 14:18, 3 September 2014 (UTC)

Should the default width depend on the proportions of the picture? A fixed width makes portrait images much bigger than landscape ones.--Andrew (talk) 10:32, 6 September 2014 (UTC)
example (1) "portrait" image with "upright" (and default / your user setting of the width)
Thanks for your comment, Andrew. You are right, basically. And this is the way it is currently (because Media is made that way). However, that's only the half truth. In fact there is a very simple solution to this: portrait images (I guess you mean ones which are higher than wide) should get the parameter "upright" in addition to "thumb". That is: |thumb|upright. That way they are automatically made smaller. See my example (1) image on the right side. If it really is needed the parameter upright can be specified so it takes the user setting (or the Wiki's default) as basis and multiplies this according to the parameter. This is in most cases much more flexible, user friendly and work-saving than specifying fixed pixel widths/heights. For more info see for example Wikipedia's Manual or Wikipedia's picture tutorial. --Aseerel4c26 (talk) 21:47, 6 September 2014 (UTC)
  • I approve this proposal I approve this proposal. I agree the thumbnails are too small and following wikipedia's default size sounds good to me. --Cantho (talk) 14:54, 14 September 2014 (UTC)
  • note the standard seems to have been changed to 300 px in the meantime (if I checked correctly). --Aseerel4c26 (talk) 22:08, 20 February 2016 (UTC)

Add link for Ukranian locale

Can anyone of admins also add some Ukranian translations below?

   MediaWiki:Mainpage-url/uk (
   MediaWiki:Mapfeatures-url/uk (Uk:Map Features)
   MediaWiki:The map/uk (Мапа)
   MediaWiki:Map Features/uk (Об’єкти мапи)
   MediaWiki:Shop/uk (Магазин)
   MediaWiki:Donations/uk (Допомога проекту)
   MediaWiki:Portal/uk (Проекти)

Now we have link to the Russian userlang :( --Andygol (talk) 19:17, 27 October 2014 (UTC)

As far as I know, all locales have the same translation, but I also would love to have these menu itens translated. I tried to contact a wiki admin by email a few weeks ago, with no success. I hope this message reaches the admins --Jgpacker (talk) 19:35, 27 October 2014 (UTC)
Thanks for the translations guys. I've just put them in place for you. How does that look? -- Harry Wood (talk) 12:26, 28 October 2014 (UTC)
Thanks Harry. It looks good!--Andygol (talk) 15:57, 28 October 2014 (UTC)
Cool! I also would like an update to the brazilian portuguese locale :-). See below (not sure if I wrote the code correctly though). --Jgpacker (talk) 13:22, 28 October 2014 (UTC)
   MediaWiki:Mainpage-url/pt-br (
   MediaWiki:The map/pt-br (O mapa)
   MediaWiki:The map-url/pt-br ( 
   MediaWiki:Map Features/pt-br (Características do mapa)  
   MediaWiki:Mapfeatures-url/pt-br (Pt-br:Map Features) 
   MediaWiki:Contributors/pt-br (Contribuidores)
   MediaWiki:Help-url/pt-br (Pt-br:Help:Contents)
   MediaWiki:Shop/pt-br (Loja)
   MediaWiki:Shop-url/pt-br (Pt-br:Merchandise)
   MediaWiki:Donations/pt-br (Doações)

OK done those these pt-br ones too. Obrigado! -- Harry Wood (talk) 14:46, 28 October 2014 (UTC)

Thanks! It seems the links for The map, Shop and Map Features did not change. Could you take a look at that?
One other thing: Could you add a line-break in Características do mapa after the word do? It's a bit too big right now. It's in MediaWiki:Mapfeatures/pt-br. --Jgpacker (talk) 16:25, 28 October 2014 (UTC)
The page titles you're listing are not quite right. It's de-referenced several levels in a confusing way for some reason. Starting from Mediawiki:Sidebar, you can see that MediaWiki:Map is the correct page which sets the message, not "MediaWiki:The map". Likewise some of the other links given above are not quite right. Hopefully I've put the translations all in place correctly though (?) -- Harry Wood (talk) 01:46, 29 October 2014 (UTC)
Yes, I had no idea how to get the correct page names. The titles I said above are the ones that are shown in the english locale. The code I put above was based on Andygol's code (that's why I said I wasn't sure if it was correct).
Looking at MediaWiki:Sidebar, I can see that the URLs I want to set are MediaWiki:shop-url/pt-br to Pt-br:Merchandise, MediaWiki:map-url/pt-br to and MediaWiki:mapfeatures-url/pt-br to Pt-br:Map Features
When I was in another computer the phrase "Características do mapa" had an automatic line-break (in a monitor with a lower resolution), so perhaps it isn't needed to add a manual one.
Thanks for your help!
--Jgpacker (talk) 10:36, 29 October 2014 (UTC)

Account clean-up


I'm using a new account (pmailkeey_still) as I can't access my normal one (pmailkeey). I tried logging in on that one even going through password reset and got a message stating no e-address logged with the account! Anyone here sort this out for me ?

Hmm, your old user account never did add anything to this wiki. Is this right? Did you spell it differently maybe? Note that the wiki account is completely separated from your account.
And regarding email address: maybe you really did not specify one? I guess admins cannot do anything for you as you cannot prove that you are the right account owner.
And you (new account) can "add stuff" at your old user page because everybody can edit everybody's user page. You also could edit mine. --Aseerel4c26 (talk) 02:56, 4 December 2014 (UTC)

Add support for OverpassQL in Wiki_Help#Include_source_code

We need syntax highlighter for our main API language. Xxzme (talk) 17:36, 17 January 2015 (UTC)

Well, then somebody needs to program this ;-) Try another "lang" parameter. Some may look okay. --Aseerel4c26 (talk) 18:01, 17 January 2015 (UTC)
I have added a sentence at Wiki help. … Developing a dedicated syntax highlighter is not really needed! --Aseerel4c26 (talk) 15:29, 22 January 2015 (UTC)

Request for namespace with machine-readable definitions (XSD:)

Since required tags and regexes for values were requested, we can skip this step and use xsd definitions directly at wiki. Obviously this namespace is not translatable.

Right now we use wiki as knowledge base for OSM (proposals, external references to wikidata), so code snippets will not harm IMO. Probably we can use more generic name "formal:":

Formal definitions will be limited per their scope:

  1. formal:Key: will cover single key
  2. formal:Tag: will cover single value
  3. formal:Proposed features/Animal_breeding may cover entire tagging schema as described in Proposed features/Animal_breeding

1 and 2 are hard to formalize correctly if there multiple overlapping schemes (see type=*). Formalization of 3 looks more promising.

This namespace should be excluded from search results (see [9][10] and relevant settings).

Actually this idea not so crazy, many authors of validators invent their own checks instead of reusing common knowledge. Xxzme (talk) 04:14, 23 February 2015 (UTC)

If we go the machine readable route, then I would prefer having a Wikibase instance for the OSM wiki, ideally with one Wikibase item matched to each key (and software etc.). That way, we could e.g. also store information for the infoboxes in a central location, and re-use them across language versions and even for lists such as taginfo. --Tordanik 11:28, 23 February 2015 (UTC)

Wiki admin

How does one become an admin on this wiki? I'd like to do help out with routine cleanup, etc.

You don't need to be an admin to help with cleanup, just start editing! To get started, read up on Wiki Help and Wiki guidelines. Lightsider 11:18, 1 April 2015 (UTC)

Supporters probably outdated or incomplete

This page linked at but it almost empty/silent about companies who help OSM. We should be more verbose and give credit to supporters.

  1. We need to mention: ~15 companies who host tile servers (see Servers).
  2. Probably many other companies who help OSM by providing ready-to-use services (recent example will be routing results provided by multiple vendors at frontpage). Xxzme (talk) 04:54, 28 April 2015 (UTC)

Editing policy

The intro at the top of this page says If you have ideas for the wiki, you can generally just do them, by editing the wiki! ...we would encourage you to be bold.

My experience is that does not reflect current practice; I've had edits reverted by others, despite their being no objection in in preceding discussion (and by editors who were in the minority when they subsequently raised one), and by an admin 'who immediately protected the page to prevent anyone else from editing it.

More generally. there seems to be a very conservative ethos, resistant to any change, especially with regard to the functionality or style of the wiki (rather than to content discussing mapping standards, which is a separate issue).

How can we return to the situation described in the intro? If we cannot, should we not have a more honest statement of policy?

-- User:Pigsonthewing 18:01, 30 April 2015

I partially agree. I'm not sure how to word it, but I would say the policy in practice is "be bold, except on well-established pages, significant change of tag definitions and templates in widespread use; these cases should be handled more carefully because there aren't many people available to review". Personally I'm a bit resistant against change in functionality or style of the wiki, because I believe it should be reasonably simple, since it's far from being the focus of OSM. --Jgpacker (talk) 20:44, 30 April 2015 (UTC)
It's true that the simple statement doesn't really represent reality with all its nuances. In the past, I assumed that people would naturally know that "being bold" has its limits, but I'm not so sure about that anymore. In addition to what you said, I would like to add that actions which are hard to undo (especially deletions, but also e.g. moving a page and changing dozens of links leading to it) really should be discussed beforehand except in the most obvious circumstances. The Delete template already contains a similar statement, by the way. --Tordanik 17:09, 4 May 2015 (UTC)
Exactly. Too bad there persons who mess up wiki by "reverting" edits without beforehand discussion. Including text in wiki that that contradicts Main Page and
I not surprised why some communities decided to created theirs own learning materials outside wiki and not to deal with issues like this. Xxzme (talk) 05:26, 5 May 2015 (UTC)
Reverts are a natural occurrence in a wiki. Wikipedia calls this the "BOLD, revert, discuss cycle". Basically, it describes a common practice where users can freely make changes ("be bold"), but if the edit is seen as a bad idea by another user, it can also easily be reverted. The differences then need to be resolved in a discussion
What is problematic, though, is reverting a revert. That simply constitutes an edit war and imo justifies admin intervention. --Tordanik 12:42, 5 May 2015 (UTC)
Even Wikipedians state that this optional method ("optional method of reaching consensus. It can sometimes be useful for identifying objections"). They also refer to Revert only when necessary at this page.
I was placing cross-link and you revert my edits as "incorrect spelling"? How this valid reason to revert all of my edits? Why your revert with invalid reason cannot be reverted? Correct spelling instead of reverting everything if I missed notice from the spell-checker. I don't edit wiki just to see my edits reverted due to some imperfection. Xxzme (talk) 13:51, 5 May 2015 (UTC)
Of course there are other methods of reaching consensus. One example would be starting a discussion before making far-reaching changes, as I said before. Perhaps you can consider using that method in the future? And no, an "invalid reason" (aka a reason you don't agree with) does not justify starting an edit war. If you don't agree with the reason given for a revert, then please offer counter-arguments in a discussion on the talk page.
As for that spelling revert you bring up repeatedly, I did not revert all your edits, as you claim, but put the extra effort in to only edit the problematic changes. --Tordanik 16:29, 7 May 2015 (UTC)
Problem is you ignore talk pages anyway [11] - I changed "map">"geo data" and placed explanation at talk page [12] but you removed my work [13] without prior discussion (as you insist) winch I stared already Talk:What_is_OpenStreetMap?#.22free.2C_editable_map.22_vs_.22free_geographic_data.22_at_this_page.3F. Xxzme (talk) 16:40, 7 May 2015 (UTC)

Beginers' guide vs Beginners' guide?

Personally I don't see why we should repeat almost same job twice. After it was done at wiki. By introducing multiple "beginner guides" we increase out work to: maintain guide, translate in 20(?) languages + maintain 20 translations.

I have nothing against LearnOSM but IMO we confuse wiki readers when refer to 2 different guides. Wiki is more complete than LearnOSM. At wiki reader can get more cross-links and useful categories (even for Category:JOSM).

Personally I see solution in main beginner guide at wiki (simplified, but with references to big topics like "JOSM" and "GPS") and additional guide from groups: We are cyclists, here is Beginners' guide and here is Guide:How to map features for cyclists

My personal opinion about learnosm materials even they are good and well designed, they lack cross-links from wiki. Wiki depth evident: simple link Contributors will lead to 60K page and more importantly, well maintained page!

And no, I don't expect to hear "our territories are different" "our infrastructure is different", "our workflows are different", "our interest are different". Yes they are.

  1. we can use
  2. we can write
List of features common in savannah (empty list? two links to Buildings and Key:natural?)
List of features relevant in crisis situation X
List of features relevant in crisis situation Y and show these links after reader finishes Beginners' guide.

There 52 references to "learnosm" keyword, most of them refer to "good resource to learn about OSM". What should we do? Isn't wiki enough? If not then why?

Just numbers:

Xxzme (talk) 07:03, 3 May 2015 (UTC)

Delete DE:Bicycle_use_sidepath

Dear Teamers, please delete the page DE:Bicycle_use_sidepath. It had a redirection from Proposed_features/use_sidepath to bicycle=use_sidepath (de). But that tag description page is not a translation of the proposal. The redirect target is the German version of bicycle=use_sidepath (en) and accessible from there. Hb (talk) 10:36, 10 May 2015 (UTC)

Add visible links for the "wiki" page (aka this exact page)


I've been searching around the last couple of days on how to find information about this wiki and how to contact the wiki community. Problem is: All the "About" or "Help" pages you find on the right sidebar / the Main Page are related only to mapping. I finally found this page by searching for "wiki" (I know, could've done this earlier). Nevertheless, I think it might be a good idea to include a link to this page either in the right sidebar and/or the Main page to give a good starting point for people who want to contribute not only to maps, but also to this wiki.

cheerio, Charel (talk) 09:01, 5 April 2016 (UTC)

The link is displayed as "Documentation" directly from the top bar of the site. May be you'd like "Wiki" but this site is a documentation site.
Not all wikis have "wiki" in their sitename. — Verdy_p (talk) 11:40, 5 April 2016 (UTC)
Thanks for answering, but I'm sorry I can't find it. You sure mean the top bar where the "Talk" "Preferences" "Watchlist" "Contributions" etc. are? I don't have it there. Neither do I find it on the main page nor any other.
I don't care if the link is named "documentation", "help", "readme" or whatever, I just want to be able to see it right away. Charel (talk) 15:46, 5 April 2016 (UTC)
The link from the top page (or hamburger menu on some devices) is called “help” on English language computers, with an onwards link to this site.--Andrew (talk) 15:52, 5 April 2016 (UTC)
Oh, you mean that tiny link in the "available languages" box that links to Wiki_Translation? You're right, I didn't see that.
I just think that this may not be the place where you go looking for general Information about how to edit the wiki (considering the plentiness of help / about / how to contribute pages and considering that most wikis have some information on how to contribute to the wiki itself on their sidebar / main page), but that may be only me.
btw, thanks Andrew for the clarifications. Cheers, Charel (talk) 18:13, 5 April 2016 (UTC)
I guess the "help" link in the top bar menu of is meant by Verdy p. Charel, do you mean the "right sidebar" here on wiki pages? I only have one on the left?! --Aseerel4c26 (talk) 19:53, 5 April 2016 (UTC)
Ouch, touché! Of course I mean the left sidebar :)
As far as I can see, the link at leads to But anyway, I just wanted to point out that as a wikipedia-used OSM newbie it has been difficult for me to find the Wiki page, and that I think it would be sensible if everybody who wants to contribute to the OSM wiki would read these few pages. If now I'm the only one who had problems finding it, then -hooray- I have found it now, problem solved :) Charel (talk) 21:35, 5 April 2016 (UTC)
Okay, fine, at least we see the same sidebars. ;-) Yes, and lists the wiki ... which is, as far as I understand, not the thing you are looking for. I understand the problem and agree. Will think about it the next days. --Aseerel4c26 (talk) 05:23, 6 April 2016 (UTC)
Right, I see now how I wasn't exactly clear. Yes, I meant links from the wiki's Main Page/sidebar to this exact wiki page ( Thanks Aseerel4c26! Charel (talk) 08:21, 6 April 2016 (UTC)

Bug: "type the two words you see in the box below" but no box

A user is breaking character encoding when editing, so I want to let them know. I wrote a message on their talk page, but I can't save.

I am told "To protect the wiki against automated page creation, we kindly ask you to type the two words you see in the box below".

PROBLEM: There is no box. See screenshot. This bug is not new, it has already been talked about here.

Note: My account has existed for a long time but I only confirmed an email address today in order to create that talk page.

Nicolas Raoul (talk) 07:24, 6 April 2016 (UTC)

Hmm. That's strange. You're not seeing the captcha properly. You should be seeing an old-style google reCaptcha
It look like you're looking at a mobile version of the site? What kind of device are you using? Can you try going to your preferences of wiki appearance. Normally that should be set to "Vector". Is it set that for you? Maybe you could experiment with the older "MonoBook" and see if that gets it show the captcha.
-- Harry Wood (talk) 10:49, 18 April 2016 (UTC)
Do you use third-party content blocking? Disabled JavaScript (NoScript)? Disabled cookies (not sure if this could interfere here)? Which browser do you use? --Aseerel4c26 (talk) 20:22, 18 April 2016 (UTC)
Not mobile, just Firefox 45 on Ubuntu 2016.04 with JavaScript enabled (only Adblock installed) and Vector setting. Nicolas Raoul (talk) 03:29, 19 April 2016 (UTC)
It could be possible that you have a privacy-centered blocklist loaded in adblock, which blocks stuff from google. If it still happens for you, try without adblock. It might also be worth to inspect the HTML source (right click on the area where the captcha should be and then the "inspect entry (Q)"). The wiki refuses to register a new test account for me - with a junk mail address... so, sorry, I cannot try it. I saw a captcha on the registration page. Do you see one there (on bottom)? (log out first, of course) --Aseerel4c26 (talk) 18:32, 19 April 2016 (UTC)
My Adblock has the out-of-the-box setting of only EasyList. Yes, I can see the captcha on the "Create account" page. The missing captcha is the new page creation step. Thanks for trying to reproduce it! Nicolas Raoul (talk) 00:55, 20 April 2016 (UTC)
Hi, I encountered this problem too. Strangely, after clicking "Save page" 2-5 times in a row, the captcha always finished by showing up on top of the page. It also somtimes showed up below the editing window, but didn't work in that case. I'm also using Firefox (64bit with AdBlock,on Windows 7) Charel (talk) 08:40, 20 April 2016 (UTC)

-one solution. I restored all default settings (in all sections), then the box came up. - Ching_mtn

Anything new here? I'm facing the exact same issue. User:Anttit 12:43, 16 July 2016 UTC
Seems a few people were hitting this, perhaps related to a slow connection failing to load the javascript in the expected order or something, but anyway...
We've just updated to the new type of ReCaptcha on here. Hopefully that will solve this issue (and hopefully it will be prompting people to help google maps read addresses less often!)
Let us know if you're still not seeing the ReCaptcha
-- Harry Wood (talk) 16:29, 20 September 2016 (UTC)

Semantic MediaWiki

Hi all,

I want to bring up an old topic again, namely how you feel about adding the Semantic MediaWiki extension to this wiki. It seems that this has already been a topic in 2009, wich found neither strong opposition nor wide support in the OSM wiki community. Since the focus in 2009 was rather about machine-readability than maintenance facilitation on the one hand, and on the other, we are now 2016, and both OSM wiki and SMW have come a long way since 2009,

I want to ask anew what you think about installing SMW on this Wiki?

Some points I see speaking in favor of SMW are:

  • It can be used to automatically update lists (e.g. map features like Template:Map_Features:shop, user lists, etc.)
    • (As usual, those lists could use templates for styling & layout through the template format output, this was not possible in 2009 as it seems)
  • It can make maintenance tasks much easier because it allows to query for combinations of categorisations and other page properties (even complex queries for tracking things like localised pages which do not have the same property x as page <pagename> could be made possible without further workarounds!)
    • Tailormade maintenance ToDo lists
  • Other possibilities include:
    • A {languages} template setting & using a common page property for translations of an article -> no need for redirects anymore, works across all namespaces
    • A single, common database for tag descriptions to which new tags can easily be added from every language
    • Many useful things which I don't know about...

Please tell me what you think!

Cheers, Charel (talk) 13:51, 29 April 2016 (UTC)

I think some semantic support for the wiki content would be very useful, for automatic list generation, easier access to tag data via queries/api and so on. Since you seem knowledgeable about the topic, how do you feel about the relative merits of SMW and a Wikibase installation for this purpose? --Tordanik 13:42, 5 May 2016 (UTC)

Wiki bugs: map display, OpenLayers.Control.Button error, ResourceLoader deprecations

Hi, something on the wiki suggested I report issues in git, so I did at , but Tom Hughes closed the issues saying they're not with the skin. So here they are. This is all visiting South Bay (SF), California in chromium and Firefox Nightly (49.0a1 (2016-05-30)) running on my Kubuntu desktop.

If they are all bugs in the SlippyMaps extension, I guess they can be filed in the Phabricator extension-SlippyMaps project.

-- Skierpage (talk) 00:19, 2 June 2016 (UTC)

Bug: map appears below map div at normal desktop window sizes

No map appears "above the fold" in the space for the map (<div id="map" class="olMap">) unless I resize my browser really wide. Instead the map displays partway through the first paragraph, obscuring several paragraphs and headings.

This page specifies <slippymap h=480 w=720 z=11 lat=37.35 lon=-121.98 layer=cycle></slippymap> and in most portrait windows there isn't room for a 720-pixel wide map alongside the place table. You could move the {{Place}} template invocation below this to avoid the problem, or insert a <div style="clear:both;"></div> between them, or rethink the CSS of Slippymap and the {{Place}} template.

Bug: JavaScript error

If I turn on my browser's JavaScript console, I see

 TypeError: OpenLayers.Control.Button is not a constructor
  slippymap_init()      South_Bay_(SF),_California:87:1096 [in the page HTML]

Mr. Hughes comments this is probably a bug in the SlippyMap extension.

The slippymap extension is full of bugs, including with very bad HTML/CSS layout. In addition it can only be used only ONCE per page. Trying to display two maps on the page will incorrectly place the children elements or will cause the interaction with one map to affect another map due to collision (no unicity of the generated "id" attributes per slippymap instance).
This local gadget on this wiki is in fact unmaintained since long and nobody seems to be working on it (and it is not part of the standard MediaWiki distribuion, not used by Wikimedia on its sites that uses other extensions and is developing new ones for integrating maps in Wikipedia: for now there's a couple of extensions used to render maps in a popup that you open by clicking on a "map" icon at top of page at end of the title bar.).
Probably it will be replaced later using a new installed gadget or extension. But for now, if you need several maps, use separate wiki pages.
Additionally the slippymap also uses deprecated features of MediaWiki and unsupported internal features that no longer exist. And yes the use of the OpenLayers framework is also non-conforming (as it also uses internal variables in a non-clean way not matching the documentation). slippymaps on this wiki have very limited usage, just to show a basic locator map for the country, region or city which is the main topic of the page. In most cases one one map may be useful; for the rest, create directly a link to the OSM site to render maps in a separate page: you can use templates like {{Node}}, {{Way}}, {{Relation}} to create such links to the OSM map or to a few other tools with specific renderings. — Verdy_p (talk) 15:57, 12 June 2016 (UTC)

ResourceLoader warnings

I also see in the console the warnings

 Use of "addOnloadHook" is deprecated. Use jQuery instead.
 Use of "wgNamespaceNumber" is deprecated. Use mw.config instead.
 Use of "addOnloadHook" is deprecated. Use jQuery instead.

Probably some extension is calling these. The ResourceLoader Migration guide has advice on updating to avoid these deprecation warnings. In some future MediaWiki release they will all become errors.

This has been signaled already, and simple to solve:
  • addOnloadHook(function) must be replaced by $(document).load(function) (this will effectively use the resource loader in a predictable load order to avoid collisions of scripts, or bad effects produces by browser and proxy caches where the order of loading defpendant scripts is unpredictable: a dependant script may not be loaded when another script needing it will start referencing a feature)
  • wgNamespaceNumber must be replaced by mw.config.get('wgNamespaceNumber') (this nas no relation to the resource loader but to a more modern use of the global variables (keeping only "mw" as a global for the builtin MediaWiki environment, it becomes much simpler to isolate only this one to sandbox some behavior, without having to rebuild long lists of variables in the environment; notably using the get() method allows simpler overrides, that will be consistant across extensions or for custom plugins, without causing plugins to have side effects, as all that will be needed is to override the get() method to define a specific behavior; this is needed for the various editoes or for helping the development of betters skins, or better tune the interface for mobiles, or to simplify the work in customized user-specific behavior and preserving a wider compatibility with other skins or between the modile and desktop version of the wiki, by using more selecting remappings, easier to define).
Verdy_p (talk) 10:13, 3 June 2016 (UTC)

Profiling Map Features

Would it be possible to profile the Map Features page in several languages where it is slow to respond, including Japanese, Russian and Ukrainian where it doesn’t render completely?--Andrew (talk) 11:09, 12 June 2016 (UTC)

It's not a reason of performance but simply of volume of this page that has accumulated too many things, by transcluding multiple levels of complex templates.
The generated page is also very huge.
There's only a solution: split its content into more relevant pages. A single page to host all features is not sustainable. We need a better navigtion system than this old unstructured page, that was designed in a time where there were still not a lot of things documented.
The issue is not specific to some languages but general for all languages (including English). We've hit the Mediawiki limits for a single page (see the statistics in the HTML comments at end of the generated "content" div) — Verdy_p (talk) 15:43, 12 June 2016 (UTC)

Is the searching engine still alive?

Hello all, Since a few days I noticed that I can't find anything using the search engine. No result is provided, whatever I type. Example : "tree_row", "natural=tree_row", nothing works, even to look for pages that I know to exist. I checked all the check-boxes but nothing shows up. Do you guys have the same problem please? Thanks. --Thaïti Bob (talk) 21:55, 27 February 2017 (UTC)

the wiki had technical problems in the last days (not available at all). PLease just wait a few days. I have the same problem, yes. . Typing Tag:natural=tree_row works - sends me to --Aseerel4c26 (talk) 22:14, 27 February 2017 (UTC)
There are other problems such as several javascripts no longer working since the recent (unannounced and untested) upgrade of the MediaWiki version which no longer supports several old MEdiaWiki functions that were deprecated several years ago (such as "onLoadHook".
Those javascript must use now jQuery event handler, and must use the ordered "resource loader" of MediaWiki. Various globals javascript variables are also disappeared, and are isolated in their namespace (no logner replicated at the global scope.
You can see those many errors that this upgrade ahas caused: open your browser's javascript console and look for the various exceptions caused now by undefined objects (all of them were deprecated and their depracation was announced since long and documented in MediaWiki).
Upgrading MediaWiki without performing some minimum compatibily test, and not taking care about deprecations signaled for months or years is the cause of these problems.
Unfortunately this wiki had not any upgrade since very long, and all deprecations were constantly ignored (and the fixes for preventing errors after upgrades could not even be implemented early as this wiki was really very late).
I think this wiki was upgrade only in emergency, possibly for security reasons, but stepping through many several major versions and changes that have been ignored since years, for lack of maintenance or because admins still did not care about why it was important to follow the upgrades and monitor all warnings or errors in the Javascript console of browsers !
This new version of MEdiaWiki also changes several CSS classes that may be expected by existing javascripts. jQuery being itself upgraded too, as well as the look and feel of the UI in the "Vector" layout, and many changes for improving the accessibility of for adding support for the new visual editor, and support for rendering on mobile devices. — Verdy_p (talk) 02:41, 28 February 2017 (UTC)

Proposal for creating group categories

Hello, I would like to propose to start creating group categories for tags and keys as it was intended while adopting a new {{Description}} template. Actually it the process of creating group categories is working since rolling out this template but the destination categories were mostly not created so the groups were missing or were almost empty and when the category for the given group does not exist it won't be created automatically and tag/key is not included in it and stays in parent category.

These are the groups I am talking about:

There is one problem however which needs to be sorted out before I or anyone else can start creating the missing categories for tags/keys. The problem is with the group= parameter of {{Description}}. As you might know the parameter in the current version of the template is displayed with the initial letter capitalized. Therefore it does not matter if you add group=Highways or group=highways it gets displayed as Highways. The problem is that the same logic was not applied when sorting the tag/key into appropriate group. The is no capitalization applied and therefore group=Highwasy and group=highways tend to end up in two different categories which is undesirable.

Unfortunatelly there was no standard for case of this group= parameter clearly defined. Therefore we have a mixture in the wiki of both styles. I have done some counting and the statistics is:

  • 12 244 tag/key pages in total in all languages
  • 5 055 has a group= group filled in
  • 4 109 are starting with capital letter - group=Highways
  • 895 are lower case - group=highways

Now there is a lengthy and heated discussion between User:Verdy p and User:chrabros how to solve this and proceed with categories creation. The discussion starts here and continues here and you are welcome to join it. My conclusion of this debate is that we have several options how to proceed and those are:

Option 1 - Capitalize first letter of Group

  • + it is a simple change of {{Description}} template
  • - we need to recreate 10 categories in Category:Tag descriptions by group and 71 categories in Category:Key descriptions by group
  • + we do not have to edit any tag/key pages
  • + the value of group displayed in right hand side infobox will be the same as category name which are users used to for a long time now
  • + group=Highways and group=highways will end up in the same category automatically
  • - we cannot have any category name starting with first letter lowercase (I cannot think of an example where it matters)

Option 2 - Make the first letter of group lowercase

  • + it is a simple change of {{Description}} template
  • - we need to recreate the existing group categories
  • + we do not have to edit any tag/key pages
  • - the value of group displayed in right hand side infobox will be different to the name of a category name, but it is just a cosmetic problem
  • + group=Highways and group=highways will end up in the same category automatically
  • - some users (for example Germans) will not be happy as they like their capitals in words

Option 3 - standardize group parameter as lower case for English, any case for other languages

  • + no change of {{Description}} template
  • + no need to recreate the existing group categories
  • - we need to edit 1 040 English tag/key pages from group=Highways to group=highways and up to 4 109 tag/key pages in other languages depending on their choice.
  • - the value of group displayed in right hand side infobox will be different to the name of a category name, but it is just a cosmetic problem
  • - group=Highways and group=highways will try end up in different categories. This means that we will have to watch out all the time in the future that new edit/additions are adhering to the standard.
  • + users of other languages (for example Germans and Czechs) can name their categories as they like with upper or lower case

Option 4 - standardize group parameter with first letter upper case for English, any case for other languages

  • + no change of {{Description}} template
  • - we need to recreate the existing 81 group categories
  • - we need to edit 84 English tag/key pages from group=highways to group=Highways and up to 938 tag/key pages in other languages depending on their choice.
  • + the value of group displayed in right hand side infobox will be the same as category name which are users used to for a long time now
  • - group=Highways and group=highways will try end up in different categories. This means that we will have to watch out all the time in the future that new edit/additions are adhering to the standard.
  • + users of other languages (for example Germans and Czechs) can name their categories as they like with upper or lower case

Option 5 - automatic, but different standards based on language

We could change the {{Description}} template to automatic capitalization based on language so we can use group=highways in English and group=Highways for some other languages if they want to do so.

  • - {{Description}} template needs to be adjusted by someone experienced accordingly, but it is not a huge change
  • + no need to recreate the existing group categories in English
  • + we do not have to edit any tag/key pages
  • - the value of group displayed in right hand side infobox will be different to the name of a category name for some languages, but it is just a cosmetic problem
  • + group=Highways and group=highways will end up in the same category automatically
  • + users in different languages will be able to decide on capitalization as they want

Those are the five options I can think of. I would like to ask you to think about them and state your opinion here. I believe that the group categories are quite useful and it is a pity we don't use them so far. I personally would like to go on with Option 1 or Option 5. Thank you very much for your opinion. Chrabros (talk) 04:26, 16 March 2017 (UTC)


You also note that whever you use group=highway (initial version used since the begining) or group=Highway (used to fill various tag/key pages later, without knowing the effect) this displayed the same thing in the infobox as "Highway" was capitalized. This forced capitalisation is not desirable for all languages (e.g. English frequently uses a capital after a colon in "Group: Highways", but French wants to keep lowercase after the colon, and capitalize only proper names). for infoboxes, this forced capitalization shjould be removed (but kept only for English or the few languages that want it). It has no effect on Japanese where non-proper names will be translated there.
Initially group names were intended to be lowercase including in English, just because it would frequently (but not always) match some OSM tag key names. Note that tag key names are generally using a singular name, while groups are intended to be larger and will typically use plural forms, and don't have to be limited to the same OSM tag key. Groups are intended to be translatable (unlike OSM tags which are unified in British English as much as possible and use sometime a specific OSM "technical jargon" or abbreviations, including the fact that it uses underscores instead of spaces that would be used in group names)
So we must think about group names to use regular linguistic rules.
The discussion here is only about how to write the category names: Category:(Tag|Key) descriptions for group "groupname" which in normal English would also be written normally using lowercase (which I don't think should ever need to be changed to use capitalized group names here). This discussion has no effect when there's a matching "Category:Groupname where it is capitalized by default like every page in any namespace (even if this group name is translated and occurs after a language code prefix). Since the begining these categoies were using lowercase and this was never contested by anyone, even when they started being translated. Some of them were initially correctly filled. Errors started later because there was initially a correct example in the documentation page (for group=shop), followed then by a new added example (group=Historic) using another case convention (at that time the categories for this second example did not even exist: this example was not properly tested and duplicate categories were created later for this example group!). At that time, groups were still experimental (and I think they are still experimental, no one has seriously thought about how to organize these groups, this is only initial setup waiting for more organization)
The statistics above are not very relevant: initially they were completely reversed. Confusion about lettercase started to occur because some people have not cared at all about group names but just wanted to categorize their tags in other categories (Category:Groupname) and make this visible directly in the infobox. Note also that the chosen name Category:(Tag|Key) descriptions for group "groupname" is probably overlong but this was not really discussed. But as they are transaltable, some languages use another scheme (e.g. Japanese): all is translatable, including the surrounding quotation marks.
Note: the statistics have also been largely skewed by Chrabros silently adding group parameters in many key/tag pages using capitalized initials in Czech and English pages and some others (even replacing those that were correctly setup initially with lowercase)! So Chrabros has emptied silently some categories and argues now that they are empty and unused (this was wrong, this was an error by Chrabros himself) !
The name was first specified in Template:DescriptionCategoryLang (which has only been tuned and used for a few languages: cs de es fr ja, other languages using the same English default): none of these are using groupnames, this was the initial setup. This template is still used but not with the "group" parameter, but instead with the "status" parameter (also using lowercase in its English value...).
Then Template:DescriptionCategoriesLang came to replace it, in order to add support for the new experimental "groups" (and conditional use of groups): groups were activated only in English, French, Japanese, German, Spanish, Greek (still not used), and Czech (in that order, Czech being the last one added a fews days ago by Chrabros making the proposal above), all other languages having groups disabled by default (knowing the fact it was still experimental and requried active contributors to follow the tracks). That template came after a long discussion above to unify the various translation schemes to allow for simpler start for languages that have few pages translated (without having to force them to create many subcategories, just a few basic parent categories: navigation in subcategories in this case requires visiting the matching English category to find relevant subcategories). That template documents this warning:
"Note: There is no recommendation to use all of these categories. Just use those which you think make most sense to you and your local community"
Note also that sometimes it will be needed to add support for a second group when tags are not strictly organized as a pure hierarchy. we can see that in some tags that use additional categories at end of their description page: these categories are translated as well, but less visible there than in the infobox. It would be cool to add a second group.
Finally note that organizing tags in groups isnot easy: these will likely change as most tags are still not correctly sorted. In summary all statistics above will likely change to adopt a better structure. Changing tag pages or key pages is easy, but renaming categories is much more complex and requires moving all its members and redirecting them correctly. Such operations should be minimized (notably when these categories are highly populated, but it is still long to do when there's just three/fours members. And remember as well that all translated must also be checked: a single change on a category name often requires updating several dozens of pages (this does not occur for the current state of the recently created 5000 pages that are in fact speciofying groups for non-existing categories, it's not a problem of renaming categories, but still a problem to fix ALL these Tag/Key pages, independantly of the decision to this topic! — Verdy_p (talk) 09:50, 16 March 2017 (UTC)


I Voting for Option 5 or Option 1. Lenochod (talk) 07:19, 17 March 2017 (UTC)

Relation multipolygon and onRelation=no?

Discussion moved to Template talk:ValueDescription#Relation multipolygon and onRelation=no?

[snip] ... there is a more serious issue here: a comment on a high-profile talk page has gone unanswered for more than a day and this says that the community is losing its grip on the wiki, which needs to be answerable to the community if we are to have it at all.--Andrew (talk) 20:57, 15 May 2017 (UTC)
Where is the debate? I don't really understand why we'd discuss this here on Talk:Wiki (In general it seems we're discussing too many different things on this page) -- Harry Wood (talk) 22:31, 15 May 2017 (UTC)
The debate is in the edit comments here. I did not know where else I should raise this issue. This question is raised repeatedly and it seemed to me that we need a clear consensus on this issue for those who disagree. Chrabroš (talk) 05:37, 16 May 2017 (UTC)
You should raise the issue... well I'll do it for you.
Discussion moved to Template talk:ValueDescription#Relation multipolygon and onRelation=no?. ...and crosslinked from Talk:Tag:building=office
Please always go to the Talk page for discussion especially if you're reverting for a second time.
If you need to flag something for urgent attention of wiki admins then I suppose this page might be a place to do that, however there generally needs to be a trail of discussions forming evidence of clear demonstrable misbehaviour before any heavy blocking action would be taken. Basically... always try to have a discussion first. So head on over there now
-- Harry Wood (talk) 14:46, 21 May 2017 (UTC)


Hi all,
after having read this discussion (about machine-readability), and this one (about semantic wiki), this tagging mailing list thread (about tags organization, and specially this response) and after having found the interesting Taginfo/Taglists/Wiki project, what do we think about using Wikibase as a database for tags?

For example the Taglists project is really useful, but the lacking of a common database caused the not-so-stright Wiki -> Taginfo -> Wiki workflow... --NonnEmilia (talk) 21:11, 4 September 2017 (UTC)

I think it's a great idea to have a Wikibase instance for tags, to replace the current template-based content. Another possible use case for Wikibase would be content such as Template:Software that is intended to be machine-readable. Using this at the moment relies on hacks like my TTTBot (which is currently broken anyway, although that's pretty much my fault). A clean solution for this kind of semantic data, and replacing the need to manually synchronize wiki content with queries, would be amazing. While the Taginfo solution is alredy a big step forward, Wikibase seems like it could be a very good choice. --Tordanik 16:32, 7 September 2017 (UTC)
I have linked your word "Wikibase" - I hope the right target. I did not not know about this project before. --aseerel4c26 (talk) 08:00, 14 April 2018 (UTC)
I undid your edit to comment of other person. Link is Wikibase Mateusz Konieczny (talk) 04:56, 15 April 2018 (UTC)
Support as long as we don't duplicate efforts with Wikidata. Non-mission critical semantic data should be offshored to Wikidata as much as possible. Pizzaiolo (talk) 10:32, 15 April 2018 (UTC)
Support with Pizzaiolo's caveat; scope creep is to be avoided, as is duplicating the efforts another open community project. Andy Mabbett (User:Pigsonthewing); Andy's talk; Andy's edits 10:44, 15 April 2018 (UTC)
Note "However, due to complexity and dependencies, it requires some additional steps." and that Wikidata is quite hard to edit. Can you provide some examples how Wikibase would be useful, providing benefits that are larger than drawbacks? Mateusz Konieczny (talk) 15:52, 15 April 2018 (UTC)
I strongly support using structured data to organize OSM tags, assuming this is a machine-readable tag metadata effort, and not a tag storage replacement. Wikibase can be hosted here, on this wiki, alongside the rest of content, but in separate namespaces (e.g. T for tag, and V for value). A few challenges/thoughts:
  • Tags are strings (e.g. "name:en"), not integers (e.g. Q42). Wikibase needs to be customized to support that - to use a string as a primary key (and corresponding foreign keys), or have a "magical" property whose whose value must be set during creation, must be unique, and can never be changed. I do not know how difficult it would be to modify Wikibase for this (see [phabricator ticket)
  • Storing "enum" values: For many tags, e.g. "religion", values are not arbitrary, but rather have a list of values. These values have similar requirements as tags above, but should exist in a separate namespace. NOTE: many of the values would simply be a redirect to Wikidata, e.g. each individual religion string should be mapped to it.
  • Set up query service (similar to WDQS), allowing complex lookups into that data. Sophox is a good fit here, it can import this data relatively easily using existing tools.
  • Modify main editing tools (iD, JOSM) to do lookups, fetch localized descriptions, and also get value suggestions and other recommended tags.
P.S. I created a task for Wikibase to figure out the immutable keys.
--Yurik (talk) 00:33, 16 April 2018 (UTC)