[OSM-talk] Fw: calling all python coders for slippy map help

Nick Whitelegg Nick.Whitelegg at solent.ac.uk
Thu Nov 16 17:34:18 GMT 2006


Sent by:        talk-bounces at openstreetmap.org
To:     SteveC <steve at asklater.com>, Nick Whitelegg 
<Nick.Whitelegg at solent.ac.uk>
cc:     talk at openstreetmap.org 
Subject:        Re: [OSM-talk] Fw:  calling all python coders for slippy 
map help

>This is my understanding, from Artem's explanations..

>Mapnik is using PostGIS, with the schemas optimized for rendering.
>For instance, a way is fully represented in a single row .. both its 
geometries and tags.
>In a sense, the additional joins currently employed to get renderable 
data are done offline,
>by the load scripts.

>For the full, editable, revisionable database, mysql is suited fine to 
the task.

>Once planet.osm is loaded, daily (or weekly) changes will be loaded much 
quicker,
>since it only requires production of the diff of planet.osm.

OK I see. I thought the idea was to re-render a tile when someone made a 
change, but obviously I got that wrong. If this is the case, the tile 
server will essentially have purely static tiles, so there will be no need 
for a caching system. So is there really a lot else to do regarding 
development on the tile server?

Apologies if I've misunderstood.

Nick






More information about the talk mailing list