Translation

English
English Polish
Administrative city required Wymagane jest miasto z granicą administracyjną
Error with osm city: %s Błąd z miastem w osm: %s
Required Wymagane
Same latitude Taka sama szerokość geograficzna
Same longitude Taka sama wysokość geograficzna
Bounding Box too large Wybrany obszar zbyt rozległy
%(title)s %(format)s Map Mapa: %(title)s Format: %(format)s
%(title)s %(format)s Index Indeks ulic: %(title)s Format: %(format)s
Invalid layout '%s'
Invalid style '%s'
Administrative area too big for rendering Granica administracyjna zbyt duża do wyrenderowania
No administrative boundary details from GIS Brak szczegółów granicy administracyjnej z GIS
No administrative boundary Brak granicy administracyjnej
About Informacje
This is a fork of the original <a href="http://maposmatic.org">MapOSMatic</a> service. The source for this fork can be found on GitHub:
The forked MapOSMatic web frontend
The forked Ocitysmap rendering backend
If you want to try to run your own instance you may want to check out my <a href='https://github.com/hholzgra/maposmatic-vagrant'>Vagrant test setup</a> as a starting point
Below you'll find the "About" text of the original MapOSMatic project.
History Historia
MapOSMatic has been started thanks to an idea of
Gilles Lamiral, an <a
href="http://www.openstreetmap.org">OpenStreetMap</a> and free
software contributor of Rennes area, France. From his idea, a group of
crazy <a
href="http://en.wikipedia.org/wiki/Hacker_(programmer_subculture)">hackers</a>
met together during a one-week <em>Hackfest</em> in August 2009 and
brought the idea of Gilles Lamiral to life by writing the code and
named the project <strong>MapOSMatic</strong>. The group of crazy
hackers would like to thank Gilles for sharing his bright
idea!
Of course, MapOSMatic is fully free software,
licensed under the <a
href="http://www.fsf.org/licensing/licenses/agpl-3.0.html">AGPLv3</a>.
How does it work? Jak to działa?
On our server, we run a <a
href="http://www.postgresql.org">PostgreSQL</a> server, with the <a
href="http://postgis.refractions.net">PostGIS</a> extension. In this
PostgreSQL server, we have loaded the <a
href="http://wiki.openstreetmap.org/wiki/Planet.osm">OpenStreetMap
data for the whole world</a> using the <a
href="http://wiki.openstreetmap.org/wiki/Osm2pgsql">osm2pgsql</a>
tool. The same tool is also used to apply <a
href="http://planet.openstreetmap.org/daily/">daily differences</a> of
the database, which allows to keep it up to date with the new
contributions of OpenStreetMap users.
For the map rendering, we use the
famous <a href="http://www.mapnik.org">Mapnik</a> with the OpenStreetMap
stylesheet
available <a href="http://svn.openstreetmap.org/applications/rendering/mapnik">in
OpenStreetMap Subversion repository</a>. Using Mapnik
and <a href="http://cairographics.org/pycairo/">Cairo</a>, we
built <i>OCitySMap</i>, a Python module that:
Renders the map using OpenStreetMap data and the
OpenStreetMap Mapnik stylesheet;
Renders on top of the map, using Mapnik, the grid
of 500 meters squares, the labels of the squares, and some more
information on the map (copyright, scale,
etc.);
Greys out all the area outside the city if we find
its administrative boundary;
Renders an index of the streets, based on
OpenStreetMap data and the intersection of the streets with the
squares on the map.
This Python module can be used through a command-line
tool provided with OCitySMap, so everyone can run its own city-map
rendering suite. However, as the installation of the different
components is quite complicated, a small web service has been created
on top of it so that end-users can easily generate and use
OpenStreetMap city maps.
This web service has been called <i>MapOSMatic</i>,
like <i>map-o-matic</i> but with a reference to OpenStreetMap (OSM). The
web service is written in Python
using <a href="http://www.djangoproject.com">Django</a>. It is
responsible for storing the rendering requests and displaying the result
of these requests. The rendering itself takes place asynchronously
through the <i>maposmaticd</i> daemon. This daemon does only one
rendering at a time, which is very important because of the CPU and I/O
intensive nature of the map rendering process.

Loading…

No matching activity found.

Browse all component changes

Glossary

English Polish
No related strings found in the glossary.

String information

String age
2 years ago
Source string age
2 years ago
Translation file
www/locale/pl/LC_MESSAGES/django.po, string 33