Beginners Guide 1.5
From OpenStreetMap Wiki
Available languages
Other languages — Help us translating this wiki
• Afrikaans • አማርኛ • العربية • অসমীয়া • Asturianu • Azərbaycanca • বাংলা • Brezhoneg • Bosanski • Català • Corsu • Dansk • ދިވެހިބަސް • Esperanto • Euskara • فارسی • Frysk • Gaeilge • Kréyòl gwadloupéyen • Gàidhlig • Galego • Alemannisch • ગુજરાતી • هَوُسَ • עברית • हिन्दी • Kreyòl ayisyen • Հայերեն • Interlingua • Bahasa Indonesia • Igbo • Íslenska • Basa Jawa • ქართული • Қазақша • ភាសាខ្មែរ • ಕನ್ನಡ • 한국어 • Kurdî • Lëtzebuergesch • ລາວ • Lietuvių • Latviešu • Malagasy • Македонски • മലയാളം • मराठी • Bahasa Melayu • Malti • မြန်မာဘာသာ • नेपाली • Norsk (nynorsk) • Norsk (bokmål) • Occitan • Oromoo • ଓଡ଼ିଆ • ਪੰਜਾਬੀ • Polski • پښتو • Português • Português do Brasil • Română (Moldova) • سنڌي • සිංහල • Soomaaliga • Shqip • Српски / Srpski • தமிழ் • తెలుగు • Тоҷикӣ • ไทย • اردو • O'zbek • Tiếng Việt • Wolof • isiXhosa • Yorùbá • isiZulu
Render maps!
So you have now added data and tagged it, and uploaded the changes to OSM. To see your changes you can do either of the following, depending on what you want.
- Get the data to appear on the slippy map on OpenStreetMap's main page. The main page contains a '+' on the right side. After clicking the plus you usually get the 'Baselayer' options 'Mapnik' and Both represent a map generated with the above renderers.
- Mapnik: Mapnik baselayer varies in how long it takes to update; the more popular zoom levels are rendered sooner. Expect anything from a few minutes to a few days.
- Generate rendered graphics from the uploaded data yourself using a rendering tool on your computer or smartphone. The OpenStreetMap project has many different rendering tools, including:
- Maperitive : Maperitive (the successor to Kosmos) is a new lightweight OSM map-rendering platform primarily designed to be used by OSM users on their own computers to render maps. Probably the easiest of the three methods.
- Osmarender: A renderer based on Extensible Stylesheet Transformation (XSLT) that is able to create Scalable Vector Graphics (SVG), which can directly be viewed with some web browsers or converted to bitmaps.
- Mapnik: A very fast renderer written in C++, with python bindings, that generates bitmaps (png,jpeg) and styled vector output (pdf,svg,postscript). It requires some skill to set up.
- There are also third-party rendering tools. If you are interested in using your iPhone, iPod Touch or iPad to see OSM-sourced maps and get turn-by-turn directions, try one of the apps listed here.
Use the map
You're probably not only interested in making and extending the map, but using it for your own purposes, depending on the kind of interests you have and the envisaged application of the slippy map. Some of the options listed on this Wiki will get you going:
- When you do not require dynamic maps, based on up-to-date OSM data, exporting an image and using it in your own work is the best option. This is also the option you'll have to choose if you're making static print media (e.g., brochures and posters).
- Embedding the map on your website is likely to be the easiest and is likely to require the least technical knowledge. On the other hand, there are no direct advanced options for representing data and the interface.
- Place the map on your own website by using JavaScript. This option allows you to customize the map, and the interface, to some extent.
- Create your own map based on the OSM data. Possibly the most flexible option in terms of what you can do. It comes at the cost, however, of more specialised technical knowledge and additional requirements for hardware and software.
Developing your own applications is also possible by using and re-using OSM components. An overview of the components is a good place to start when you're interested in making your own advanced, OSM-based, applications.
