He:Component overview

From OpenStreetMap Wiki
Jump to: navigation, search
שפות זמינות — Component overview
Afrikaans Alemannisch aragonés asturianu azərbaycanca Bahasa Indonesia Bahasa Melayu Bân-lâm-gú Basa Jawa Baso Minangkabau bosanski brezhoneg català čeština dansk Deutsch eesti English español Esperanto estremeñu euskara français Frysk Gaeilge Gàidhlig galego Hausa hrvatski Igbo interlingua Interlingue isiXhosa isiZulu íslenska italiano Kiswahili Kreyòl ayisyen kréyòl gwadloupéyen kurdî latviešu Lëtzebuergesch lietuvių magyar Malagasy Malti Nederlands Nedersaksies norsk norsk nynorsk occitan Oromoo oʻzbekcha/ўзбекча Plattdüütsch polski português română shqip slovenčina slovenščina Soomaaliga suomi svenska Tiếng Việt Türkçe Vahcuengh vèneto Wolof Yorùbá Zazaki српски / srpski беларуская български қазақша македонски монгол русский тоҷикӣ українська Ελληνικά Հայերեն ქართული नेपाली मराठी हिन्दी অসমীয়া বাংলা ਪੰਜਾਬੀ ગુજરાતી ଓଡ଼ିଆ தமிழ் తెలుగు ಕನ್ನಡ മലയാളം සිංහල ไทย မြန်မာဘာသာ ລາວ ភាសាខ្មែរ ⵜⴰⵎⴰⵣⵉⵖⵜ አማርኛ 한국어 日本語 中文(简体)‎ 吴语 粵語 中文(繁體)‎ ייִדיש עברית اردو العربية پښتو سنڌي فارسی ދިވެހިބަސް

This page is to give Developers a technical overview of logical system/components of OpenStreetMap.


OSM Components.png

בסיס נתונים

בסיס הנתונים מחזיק את כל נתוני המפה בצורת נקודות, קטעים ודרכים

ראה: סכמת בסיס הנתונים


The OSM Protocol (AKA "the API") is a REST web service interface for reading and writing to the database. Other OSM components access the database via this interface. It is also available to the outside internet.

OSM Front End

The front-end website is written in Ruby on Rails (see The Rails Port). It presents user log-in options, using a direct connection to a user database (not shown on the diagram above). The website's main function though is to display the Slippy Map ("view" tab), and, for logged-in users, the online editor Potlatch ("edit" tab)

מפת סליפי

See Slippy Map. This is the what displays the maps! It's a AJAX interface letting you zoom and pan ("slippy" draggable panning).


Potlatch is the online editor appearing on the 'edit' tab. It's a flash object embedded on the web page.

Java יישומון

The java applet has been retired. Replaced by Potlatch. See Java Applet Development.

Tiles and tile rendering

There is an ongoing process of fetching map data via the API, and rendering maps as raster images known as tiles. Many new tiles need to be rendered to achieve full (global) coverage, but also updates to the underlying map data will mean that existing tiles need to be re-rendered.


Mapnik is a rendering system which powers the display which is currently the Slippy Map default. The rendering process runs on the 'tile' server, and Mapnik tile images are served from that machine. This renderer takes its data from the weekly Planet.osm dump.


Tiles@home is a distributed tile rendering system. It uses the Osmarender rendering system (XSLTs) running on many different client machines. It takes live data over the protocol, and rendered images are uploaded back to the dev server.


As mentioned above, we use rendering software called Mapnik and Osmarender to create raster images for the slippy map tiles. Renderers can also be used on an ad-hoc basis for creating map images from our data. There's limitless potential to develop new ways of rendering our data.


Along with the edit tab on the website (Potlatch) there are other tools, both offline apps and other websites, which allow you to edit the OSM data via the API.