Rendering

Rendering is a process to convert map data into map images.

getting data (database to .osm)

Currently, CommonMap is planing to use OSM API 0.6. The API address will be http://.....commonmap.../api/0.6/ .

Making the dump by using osmosis. They will be provided by ftp, http or some BitTorent?

OpenStreetMap and the contributor providing some

Osmarender - It converters .osm to svg. You can use it for CommomMap.
Mapnik - It is huge rendering system. To use it for CommonMap, you need planet dump.
Kosmos - To use it for CommonMap, You need to set some parameter. See Kosmos for CommonMap.

Rendering Rules - CommonMap's Rendering rules. The wiki page is machine readable, then it can be converted into rendering rules for any renderer.

tiles@home for CommonMap - Perl scripts to help you to make map tiles.
cmarender - A distributed tile rendering program for CommonMap. It has a compatibility with tiles@home client but cmarender has many enhancements. It is implemented in Java. It also works as a peer of TurtleEggs.

TurtleEggs - The map image serving grid system. It serves map tiles from distributed peers. This system is constructed by P2P technology like BitTorrent P2P. There are a tracker, a few tile servers and many peers.
TurtleEggs tracker - tracking newest tiles and recodes the tile holders. It has a little compatible with tiles@home server but it is oriented for fully working with cmarender. It works a pseudo tile server for general web browsers.
Tile server - Tile server is one of the most reliable peer. It should hold a assigned region of tiles and be uploaded them from the other peers or download them from peers. It works as backup of the other peers.
TurtleEggs peer - a general peer. It is a program running in the users PC. It serves tiles which it has. Usually, it runs with a associated program and the associated program gives new map tiles to the peer.