Tirex/Backends/WMS

From OpenStreetMap Wiki
Jump to: navigation, search
Available languages — Tirex/Backends/WMS
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 português do Brasil 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 беларуская български қазақша македонски монгол русский тоҷикӣ українська Ελληνικά Հայերեն ქართული नेपाली मराठी हिन्दी অসমীয়া বাংলা ਪੰਜਾਬੀ ગુજરાતી ଓଡ଼ିଆ தமிழ் తెలుగు ಕನ್ನಡ മലയാളം සිංහල ไทย မြန်မာဘာသာ ລາວ ភាសាខ្មែរ ⵜⴰⵎⴰⵣⵉⵖⵜ አማርኛ 한국어 日本語 中文(简体)‎ 吴语 粵語 中文(繁體)‎ ייִדיש עברית اردو العربية پښتو سنڌي فارسی ދިވެހިބަސް

The Tirex tile rendering system can use several rendering backends for creating the tiles. The WMS backend doesn't really do any rendering, it just requests the map image from a WMS server.

The backend doesn't do re-projection, so you have to use it with a WMS server that supports the Google-like Pseudo-Mercator projection. The EPSG code for this was sometimes called 900913, for a short time it was 3785, but the current (May 2010) official identifier is EPSG:3857. The Tirex backend will always request an image the size of a metatile, split it up into tiles and re-assemble them into a metatile.

With Tirex and the WMS backend you can build a WMS-to-tiles converter similar to TileCache. But because of the queue handling, Tirex can make sure that your WMS server is never overloaded.

The WMS backend is contained in the Debian/Ubuntu package tirex-backend-wms.