|About this wiki||Guidelines||Organisation||Translation||Cleanup||Help||±|
This is the help page for editing the OpenStreetMap wiki. For support related to any other aspect of OpenStreetMap, please see the Main Help Page.
Getting started with wiki editing
We aim to build a user friendly wiki that helps OpenStreetMap contributors and users find the information they need quickly and easily. If you can help, please feel free to edit this wiki. Our general advise is to be bold - if a page can be improved, go forth and do it!
Jump straight in: Click 'Edit' at the top of any page, to edit the contents. You do need to create a wiki account before editing.
For introductory instructions on editing wiki pages, see Help:Wiki-Editing. This explains some of the wiki text syntax for achieving special effects in the text such as bold and italic text. You may also wish to visit Wikipedia's help. Wikipedia is the largest online Wiki, and has detailed articles covering almost every imaginable aspect of editing pages. It also has a group of volunteers who answer questions and provide help with editing. The OpenStreetMap Wiki shares the same platform as Wikipedia (namely Mediawiki), so much of what works there will work here too.
We cannot cover every topic about Mediawiki at https://wiki.openstreetmap.org/. Please refer to MediaWiki main help site.
Remember that anyone can edit anything on the OSM Wiki. This includes you. When adding to the wiki, you should seek to find the correct place within the current structure, to build upon the information we already have. This is better than creating a new page as your page where things are written your way. Also be prepared for others to edit the page after you.
The wiki currently needs some re-organisation, and this effort is being coordinated at WikiProject Cleanup. Large-scale re-arrangements or deletions may be necessary in order to achieve this. Feel free to get involved, but for any change which might be viewed as destructive, you should leave a trail of comments on the associated discussion pages, to explain what you are doing and why. For really big changes which might upset someone, it is best to hold a discussion about it first. Propose the change, discuss it, and reach agreement on the best organisation. Different people have different ideas for how to organise the wiki pages.
History and Discussion
All wiki pages have an associated history page where you can view previous versions of the page. You can also undo a recent edit if you are not happy with the result (although it is always worth previewing any changes before saving an edit). This can be accessed at the top right of each wiki page.
In addition to a history, all wiki pages also include a talk page. This is an ideal place to discuss potential changes to a page, particularly if they are large or could be deemed as controversial. This can be accessed by clicking "Discussion" at the top of each page.
Make a user page
You may want to start by editing your user page. If you wish to tell the OSM community where you are (for example, so neighboring OSM members can collaborate with you to map your locale), place some category links like the following at the bottom of your user page, as necessary to identify the area(s) you want to help map:
[[Category:Users in Country]] [[Category:Users in State/Province]] [[Category:Users in City]]
If you upload images of you or other specific for the user page, place it in Category:User images with code [[Category:User images]].
This is the OpenStreetMap wiki - of course you can insert the OSM's map into any pages. If you want to use static map image, see Simple image MediaWiki Extension. If you want to use dynamic Slippy Map, see Slippy Map MediaWiki Extension.
Include images from Wikimedia Commons
Since April 2009 it is possible to include images from Wikimedia Commons on the OSM wiki.
Short HowTo: look at Wikimedia Commons for the desired picture and embed it here like this:
Options for resizing and placement are
[[Image:image.png|thumb/frame|left/right/center|size in px (e.g. 100px)| alt=text describing picture (useful for people with screenreaders)| description here is displayed below the image]]
[[Image:Dunvegan_Castle_in_the_mist01editcrop_2007-08-22.jpg|thumb|right| 200px|alt=photograph of Dunvegan Castle on the Isle of Skye in the mist| Dunvegan castle on Isle of Skye]]looks like this:
For a more verbose HowTo see theon Wikipedia.
See also Collaboration with Wikipedia.
How to purge cache
Include source code
Surround your code with
where "???" is the programming language, one of (listed below in alphabetic order):
Initially this source code formatting and highlighting extension recognized the languages supported by the GeSHI highlighter; since June 2015 (and its integration in MediaWiki since version 1.26 or later, integrated on this wiki since end of May 2017), the extension uses the Pygments highlighter (bundled version 2.0.2) which is much better performing, and the list of supported languages was largely extended, with a few of them removed (old assembly languages rarely used) or supported under different names; this new list of languages also includes various predefined aliases. Additional aliases have also been added by the Mediawiki syntaxhighlight extension itself, for compatiblity with other MediaWiki extensions in order to help the transition from GeSHI to Pygments, including:
Note: You also can (mis)use other language highlighting if your desired languages is not listed. E.g. for Overpass QL code, "cpp" (or just "c" as it avoids highlighting additional C++ keywords such as operator) is often used and looks fine. For Overpass XML code, the "xml" language is fine of course, and for MapCSS code you'll simply use "css".
For fragments of Mediawiki syntax (including invokation of templates and parser functions or in examples shown in template documentation pages), the "html5" language is frequently the best choice (but it won't highlight the wikikinks, template invokations, parser functions and magic keywords, highlighted as if they were part of standard HTML text elements). If the wiki code is a single template invokation (with only one parameter "| name = value" per source line), you may want to use the "ini" language.
For example the wiki syntax:
<source lang="perl"> #-TEST-------------------------------------------------------------------------- our $help=0; my $coord; print "TEST\n\n"; </source>
will render the embedded Perl source code as:
#-TEST-------------------------------------------------------------------------- our $help=0; my $coord; print "TEST\n\n";