ES:Representación

The process of rendering a map generally means taking raw geospatial data and making a visual map from it. Often the word applies more specifically to the production of a raster image, or a set of raster tiles, but it can refer to the production of map outputs in vector-based formats. "3D rendering" is also possible taking map data as an input. The ability to render maps in new and interesting styles, or highlighting features of special interest, is one of the most exciting aspects having open access to geodata. Developers in and around the OpenStreetMap community have created a wide variety of software for rendering OpenStreetMap data. The data can also be converted to other data formats for use with existing rendering software.

Rendering on OpenStreetMap servers

The most obvious examples of rendering OpenStreetMap data, are those found on the openstreetmap.org homepage. Click the layer picker button on the right to switch between layers showing different rendering styles. There are several layers created using Mapnik software including the default 'Standard' layer. To understand more about the infrastructure involved in rendering and serving these tiles' map styles, see Component overview and Mapnik Rendering.

There are limitless dimensions of flexibility involved in rendering. Most rendering software supports some kind of stylesheet for controlling things like colour, line widths, text orientation, icons for points of interest, and many very subtle visual factors.

Server and command line tools

Client-side GUI applications

Client-side libraries

Artículo principal: Frameworks

Historical

The following renderers are no longer maintained but are of historical interest:

• Kosmos – local file (.osm) rendering engine based on GDI/.NET (Windows), with rendering rules defined on a wiki page. Not designed for high performance rendering or huge volumes of data, but very flexible, and good option for one-off rendering. Superseded by Maperitive
• Mapweaver - Successor of mapgen.pl Perl rendering, OSM to SVG and with Inkscape to PNG or PDF, automatic map key. Supports street and POI lists, grids and coordinate overlays. Automatic extraction of desired place out of OSM file. Not running under Windows.
• Memphis – a map-rendering application and a library for OpenStreetMap written in C using eXpat, Cairo and GLib. It's licensed under the terms of the GNU Lesser General Public License.
• Osm2pov - Tool for creating isometric maps from OSM data
• Osmarender - XSLTs which does OSM XML to SVG transformation. tiles@home was a project which uses Osmarender to create a tile set for serving a map layer alongside Mapnik's, but Osmarender can also be a good option for doing one-off renderings. SVG format allows you to do post-processing tidy up tweaks (see other options below). It was withdrawn from the main map at osm.org on 1th March 2012.
• osmbrowser – can load large areas of OSM data and render them in vector graphics.
• osmrender.pl - simple maps easily drawn with a Perl program. Uses *.osm as input.
• Pyrender – a collection of ideas, and some code in Python for various rendering server steps
• TileMill is a frontend solution to handle a user defined rendering of Mapnik. Uses the simpler CartoCSS language instead of Mapnik XML.
• V^TM – cross-platform vector tile renderer developed by the OpenScienceMap project

See also

• Creating your own tiles - Various options with quick descriptions
• List of OSM based Services - mainly a list of different map renderings
• Category:Renderers - wiki category for pages about renderers
• 3D Development
• OpenWhateverMap, a map with a patchwork of different rendering styles, suitable for demo and fun!
• OSM on Paper